Hi All,

I successfully solved the issue related to NMK, the problem was that Everest was trying to interact with PLC after reset but PLC was not ready yet.

Now I'm blocked here.

Any tips? 

Regards,
Alberto

Hi,

Can you attach your config? Looks like it does not authorize the charging session. Make sure you have a dummy token provider module connected correctly as well as an tokenvalidator

Best

Cornelius 

Alberto Merciai <alb3rt0.m3rciai@...> schrieb am Mi., 28. Dez. 2022, 16:05:

Hi All,

I successfully solved the issue related to NMK, the problem was that Everest was trying to interact with PLC after reset but PLC was not ready yet.

Now I'm blocked here.

Any tips? 

Regards,
Alberto

Hello Cornelius,

attached my config.

Thanks a lot,

Alberto

On Wed, Dec 28, 2022 at 5:09 PM Cornelius Claussen via lists.lfenergy.org <cornelius.claussen=pionix.de@...> wrote:

Hi,

Can you attach your config? Looks like it does not authorize the charging session. Make sure you have a dummy token provider module connected correctly as well as an tokenvalidator

Best

Cornelius 

Alberto Merciai <alb3rt0.m3rciai@...> schrieb am Mi., 28. Dez. 2022, 16:05:

Hi All,

I successfully solved the issue related to NMK, the problem was that Everest was trying to interact with PLC after reset but PLC was not ready yet.

Now I'm blocked here.

Any tips? 

Regards,
Alberto

  token_provider:

    module: JsDummyTokenProviderManual

Change that to JsDummyTokenProvider without the manual. Normal config-sil can be used as an example. It has a dependency to evsemanager. When evsemanager emits a plugged in event, dummy token provider swipes a simulated RFID card and outputs a token to auth manager. Auth manager validates it and validates the session with evsemanager.

With that one change you should get one step further. However the car did not start iso communication. I saw that the device for iso15118_charger is still set to auto. Set that to the same as in the slac module (the PLC device)

Best

Cornelius 

Alberto Merciai <alb3rt0.m3rciai@...> schrieb am Mi., 28. Dez. 2022, 16:32:

Hello Cornelius,

attached my config.

Thanks a lot,

Alberto

On Wed, Dec 28, 2022 at 5:09 PM Cornelius Claussen via lists.lfenergy.org <cornelius.claussen=pionix.de@...> wrote:

Hi,

Can you attach your config? Looks like it does not authorize the charging session. Make sure you have a dummy token provider module connected correctly as well as an tokenvalidator

Best

Cornelius 

Alberto Merciai <alb3rt0.m3rciai@...> schrieb am Mi., 28. Dez. 2022, 16:05:

Hi All,

I successfully solved the issue related to NMK, the problem was that Everest was trying to interact with PLC after reset but PLC was not ready yet.

Now I'm blocked here.

Any tips? 

Regards,
Alberto

Hello Cornelius,

I'm stuck with the same problem after your suggestions.
By looking at wireshark logs I think that Everest needs to reply to SSDP broadcast message (SECC Discovery Protocol)

but I cannot see this response.

How can I debug this part?

Thanks

On Wed, Dec 28, 2022 at 5:46 PM Cornelius Claussen via lists.lfenergy.org <cornelius.claussen=pionix.de@...> wrote:

  token_provider:

    module: JsDummyTokenProviderManual

Change that to JsDummyTokenProvider without the manual. Normal config-sil can be used as an example. It has a dependency to evsemanager. When evsemanager emits a plugged in event, dummy token provider swipes a simulated RFID card and outputs a token to auth manager. Auth manager validates it and validates the session with evsemanager.

With that one change you should get one step further. However the car did not start iso communication. I saw that the device for iso15118_charger is still set to auto. Set that to the same as in the slac module (the PLC device)

Best

Cornelius 

Alberto Merciai <alb3rt0.m3rciai@...> schrieb am Mi., 28. Dez. 2022, 16:32:

Hello Cornelius,

attached my config.

Thanks a lot,

Alberto

On Wed, Dec 28, 2022 at 5:09 PM Cornelius Claussen via lists.lfenergy.org <cornelius.claussen=pionix.de@...> wrote:

Hi,

Can you attach your config? Looks like it does not authorize the charging session. Make sure you have a dummy token provider module connected correctly as well as an tokenvalidator

Best

Cornelius 

Alberto Merciai <alb3rt0.m3rciai@...> schrieb am Mi., 28. Dez. 2022, 16:05:

Hi All,

I successfully solved the issue related to NMK, the problem was that Everest was trying to interact with PLC after reset but PLC was not ready yet.

Now I'm blocked here.

Any tips? 

Regards,
Alberto

It should do that once the device for iso15118_charger is correct and josev starts correctly. Did you install all python deps for josev? You can also turn on debugging for josev, but I need to check on my laptop later on how to do that. Also make sure you plugin cars only after it prints ready for charging, never before.

Alberto Merciai <alb3rt0.m3rciai@...> schrieb am Mi., 28. Dez. 2022, 17:08:

Hello Cornelius,

I'm stuck with the same problem after your suggestions.
By looking at wireshark logs I think that Everest needs to reply to SSDP broadcast message (SECC Discovery Protocol)

but I cannot see this response.

How can I debug this part?

Thanks

On Wed, Dec 28, 2022 at 5:46 PM Cornelius Claussen via lists.lfenergy.org <cornelius.claussen=pionix.de@...> wrote:

  token_provider:

    module: JsDummyTokenProviderManual

Change that to JsDummyTokenProvider without the manual. Normal config-sil can be used as an example. It has a dependency to evsemanager. When evsemanager emits a plugged in event, dummy token provider swipes a simulated RFID card and outputs a token to auth manager. Auth manager validates it and validates the session with evsemanager.

With that one change you should get one step further. However the car did not start iso communication. I saw that the device for iso15118_charger is still set to auto. Set that to the same as in the slac module (the PLC device)

Best

Cornelius 

Alberto Merciai <alb3rt0.m3rciai@...> schrieb am Mi., 28. Dez. 2022, 16:32:

Hello Cornelius,

attached my config.

Thanks a lot,

Alberto

On Wed, Dec 28, 2022 at 5:09 PM Cornelius Claussen via lists.lfenergy.org <cornelius.claussen=pionix.de@...> wrote:

Hi,

Can you attach your config? Looks like it does not authorize the charging session. Make sure you have a dummy token provider module connected correctly as well as an tokenvalidator

Best

Cornelius 

Alberto Merciai <alb3rt0.m3rciai@...> schrieb am Mi., 28. Dez. 2022, 16:05:

Hi All,

I successfully solved the issue related to NMK, the problem was that Everest was trying to interact with PLC after reset but PLC was not ready yet.

Now I'm blocked here.

Any tips? 

Regards,
Alberto

https://github.com/EVerest/ext-switchev-iso15118/blob/everest/iso15118/shared/logging/everesthandler.py

Change last line to log.info instead of debug

Then you see python output on console

Cornelius Claussen via lists.lfenergy.org <cornelius.claussen=pionix.de@...> schrieb am Mi., 28. Dez. 2022, 17:20:

It should do that once the device for iso15118_charger is correct and josev starts correctly. Did you install all python deps for josev? You can also turn on debugging for josev, but I need to check on my laptop later on how to do that. Also make sure you plugin cars only after it prints ready for charging, never before.

Alberto Merciai <alb3rt0.m3rciai@...> schrieb am Mi., 28. Dez. 2022, 17:08:

Hello Cornelius,

I'm stuck with the same problem after your suggestions.
By looking at wireshark logs I think that Everest needs to reply to SSDP broadcast message (SECC Discovery Protocol)

but I cannot see this response.

How can I debug this part?

Thanks

On Wed, Dec 28, 2022 at 5:46 PM Cornelius Claussen via lists.lfenergy.org <cornelius.claussen=pionix.de@...> wrote:

  token_provider:

    module: JsDummyTokenProviderManual

Change that to JsDummyTokenProvider without the manual. Normal config-sil can be used as an example. It has a dependency to evsemanager. When evsemanager emits a plugged in event, dummy token provider swipes a simulated RFID card and outputs a token to auth manager. Auth manager validates it and validates the session with evsemanager.

With that one change you should get one step further. However the car did not start iso communication. I saw that the device for iso15118_charger is still set to auto. Set that to the same as in the slac module (the PLC device)

Best

Cornelius 

Alberto Merciai <alb3rt0.m3rciai@...> schrieb am Mi., 28. Dez. 2022, 16:32:

Hello Cornelius,

attached my config.

Thanks a lot,

Alberto

On Wed, Dec 28, 2022 at 5:09 PM Cornelius Claussen via lists.lfenergy.org <cornelius.claussen=pionix.de@...> wrote:

Hi,

Can you attach your config? Looks like it does not authorize the charging session. Make sure you have a dummy token provider module connected correctly as well as an tokenvalidator

Best

Cornelius 

Alberto Merciai <alb3rt0.m3rciai@...> schrieb am Mi., 28. Dez. 2022, 16:05:

Hi All,

I successfully solved the issue related to NMK, the problem was that Everest was trying to interact with PLC after reset but PLC was not ready yet.

Now I'm blocked here.

Any tips? 

Regards,
Alberto

Cool,

I install all josev modules and I will check if logs say something more about this issue.

What about your eth interface, which are your ipv4 and ipv6 settings?
I'm using the same iface used for PLC as you suggest before.

is it ok?

Thanks

On Wed, Dec 28, 2022 at 6:38 PM Cornelius Claussen via lists.lfenergy.org <cornelius.claussen=pionix.de@...> wrote:

https://github.com/EVerest/ext-switchev-iso15118/blob/everest/iso15118/shared/logging/everesthandler.py

Change last line to log.info instead of debug

Then you see python output on console

Cornelius Claussen via lists.lfenergy.org <cornelius.claussen=pionix.de@...> schrieb am Mi., 28. Dez. 2022, 17:20:

It should do that once the device for iso15118_charger is correct and josev starts correctly. Did you install all python deps for josev? You can also turn on debugging for josev, but I need to check on my laptop later on how to do that. Also make sure you plugin cars only after it prints ready for charging, never before.

Alberto Merciai <alb3rt0.m3rciai@...> schrieb am Mi., 28. Dez. 2022, 17:08:

Hello Cornelius,

I'm stuck with the same problem after your suggestions.
By looking at wireshark logs I think that Everest needs to reply to SSDP broadcast message (SECC Discovery Protocol)

but I cannot see this response.

How can I debug this part?

Thanks

On Wed, Dec 28, 2022 at 5:46 PM Cornelius Claussen via lists.lfenergy.org <cornelius.claussen=pionix.de@...> wrote:

  token_provider:

    module: JsDummyTokenProviderManual

Change that to JsDummyTokenProvider without the manual. Normal config-sil can be used as an example. It has a dependency to evsemanager. When evsemanager emits a plugged in event, dummy token provider swipes a simulated RFID card and outputs a token to auth manager. Auth manager validates it and validates the session with evsemanager.

With that one change you should get one step further. However the car did not start iso communication. I saw that the device for iso15118_charger is still set to auto. Set that to the same as in the slac module (the PLC device)

Best

Cornelius 

Alberto Merciai <alb3rt0.m3rciai@...> schrieb am Mi., 28. Dez. 2022, 16:32:

Hello Cornelius,

attached my config.

Thanks a lot,

Alberto

On Wed, Dec 28, 2022 at 5:09 PM Cornelius Claussen via lists.lfenergy.org <cornelius.claussen=pionix.de@...> wrote:

Hi,

Can you attach your config? Looks like it does not authorize the charging session. Make sure you have a dummy token provider module connected correctly as well as an tokenvalidator

Best

Cornelius 

Alberto Merciai <alb3rt0.m3rciai@...> schrieb am Mi., 28. Dez. 2022, 16:05:

Hi All,

I successfully solved the issue related to NMK, the problem was that Everest was trying to interact with PLC after reset but PLC was not ready yet.

Now I'm blocked here.

Any tips? 

Regards,
Alberto