I think you will need to add it in the everest branch here: https://github.com/EVerest/ext-switchev-iso15118 Feel free to make a PR to this branch! Most contributors are on vacation though so there

Is there a way to include optional fields like EVSEMaximumCurrentLimit EVSE>CARV2G CurrentDemandRes? Regards, Alberto

I'm asking it cause after setting device as you suggest I got this error, 2022-12-28 12:15:20.057820 [ERRO] iso15118_charge static void Log::error(const string&) :: ERROR - iso15118.shared.utils (51):

Ipv4 settings don't matter, manual is fine. Iso is using ipv6 link local addresses only. Alberto Merciai <alb3rt0.m3rciai@...> schrieb am Mi., 28. Dez. 2022, 17:59:

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

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

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

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

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

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

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?

Thanks a lot for sharing. Maybe I miss the firmware!! : P Merry Christmas!! Thanks On Fri, 23 Dec 2022, 18:14 Cornelius Claussen via lists.lfenergy.org, <cornelius.claussen=pionix.de@...> wrote:

That means the PLC chip did not accept the NMK key. I saw this when I tried to use a non PLC device for slac. Which PLC chip are you using? Also make sure you run everest as root. Alberto Merciai

Thanks a lot, it works! after that I try to integrate real SLAC implementation (EvseSlac module but I got) that from the PLC. [WARN] slac:EvseSlac

Hi, in the SIL it won't make much difference which ethernet device you are using, you will need to create a config for real hardware if you want to use a real PLC device. In any case, look out for

Hello, suppose I would like to move PLC port from eth0 to eth1. Can you help me understanding which are the proper changes to introduce inside run-sil-dh.sh? Thanks, Alberto

Thanks, Now I have another issue with new release, by running: ./run-sil.sh I got: No module name iso151118 Alberto On Fri, Dec 23, 2022 at 11:22 AM Kai-Uwe Hermann via lists.lfenergy.org

There is the edm git pull command that you can use in your workspace folder. To check the revisions that you have at the moment you can run edm git info as well in your workspace folder. An upcoming

Hi All, I'm trying to update my sources to the latest revision using edm v0.4.0. but command is not recognized, any tip? edm --update usage: edm [-h] [--version] [--workspace WORKSPACE] [--working_dir