We need to look why slac times out, I guess it is because you are using a PLC modem with the STM32 in between and it takes a little longer. Maybe we need to increase the timeout settings, as Anton suggested a tcpdump recording would be helpful here. Slac still goes into matched state though, so HLC should be fine with that. The car actually kills the TCP connection after a timeout of >2 seconds as it does not get a response to a request probably. The actual request we cannot see here as maybe the EXI cannot be parsed or something else wrong with the next packet after the SupportedAppProtocolRes (which works fine). 

Try to enable python debugging here:

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

last line change:

log.debug(msg)

change to:

log.info(msg)

 Then you will get the output from the python iso stack. It probably has problems with the next request and we therefore never reply back. 

In the tcpdump we can also see the packet you cannot see in the console log of everest.

Which car are you using?

Thanks

Cornelius

Am Di., 17. Jan. 2023 um 12:10 Uhr schrieb Anton Wöllert via lists.lfenergy.org <anton.woellert=pionix.de@...>:

It looks like, the sounding from the SLAC times out.  After that the HLC won't be able to connect to the EV (connection reset by peer), because the connection is not established via SLAC.  Could you probably record a pcap (tcpdump of the SLAC communication).

Do you use the latest main of everest-core (because there were recent changes in the EVSE Slac driver).

Am Di., 17. Jan. 2023 um 12:06 Uhr schrieb Alberto Merciai <alb3rt0.m3rciai@...>:

Hello,

I'm trying to move build sw into a pi.

Everything is fine but if I try to perform a charging session I got this error:

/usr/bin/manager --conf /home/root/config-sil-dc.yaml
2023-01-16 18:19:46.634886 [INFO] manager          :: 8< 8< 8< ------------------------------------------------------------------------------ 8< 8< 8<
2023-01-16 18:19:46.635226 [INFO] manager          :: EVerest manager starting using /home/root/config-sil-dc.yaml
2023-01-16 18:19:47.634018 [INFO] everest_ctrl     :: everest controller process started ...
2023-01-16 18:19:47.646433 [INFO] everest_ctrl     :: Launching controller service on port 8849
2023-01-16 18:19:54.540675 [INFO] energy_manager:  :: Module energy_manager initialized.
2023-01-16 18:19:54.708625 [INFO] grid_connection  :: Module grid_connection_point initialized.
2023-01-16 18:19:55.159670 [INFO] auth:Auth        :: Module auth initialized.
2023-01-16 18:19:55.473414 [INFO] api:API          :: Module api initialized.
2023-01-16 18:19:55.591248 [INFO] slac:EvseSlac    :: Module slac initialized.
2023-01-16 18:19:55.708490 [INFO] yeti_driver:Yet  :: Module yeti_driver initialized.
2023-01-16 18:19:55.871158 [INFO] evse_manager:Ev  :: Module evse_manager initialized.
2023-01-16 18:19:58.225050 [INFO] token_provider:  :: Module token_provider initialized.
2023-01-16 18:19:58.506605 [INFO] imd:JsIMDSimula  :: Module imd initialized.
2023-01-16 18:19:58.513026 [INFO] iso15118_car:Js  :: Module iso15118_car initialized.
2023-01-16 18:19:58.578473 [INFO] powersupply_dc:  :: Module powersupply_dc initialized.
2023-01-16 18:19:58.593826 [INFO] token_validator  :: Module token_validator initialized.
2023-01-16 18:20:05.360073 [INFO] iso15118_charge  :: Initializing framework for module iso15118_charger:PyJosev...
2023-01-16 18:20:05.396659 [INFO] iso15118_charge  :: Initializing module iso15118_charger:PyJosev...
2023-01-16 18:20:05.647368 [INFO] iso15118_charge  :: Module iso15118_charger initialized.
2023-01-16 18:20:05.681002 [INFO] manager          :: >>> All modules are initialized. EVerest up and running <<<
cobsDecode: Received nothing
cobsDecode: Received nothing
2023-01-16 18:20:22.363394 [INFO] evse_manager:Ev  :: �🌀�🌀�🌀 Ready to start charging �🌀�🌀�🌀
2023-01-16 18:21:24.684860 [INFO] evse_manager:Ev  :: SYS  Session logging started.
2023-01-16 18:21:24.685604 [INFO] evse_manager:Ev  :: EVSE IEC Session Started: EVConnected
2023-01-16 18:21:24.687267 [INFO] evse_manager:Ev  :: EVSE IEC Set PWM On (5.000000074505806%)
2023-01-16 18:21:24.848903 [INFO] token_provider:  :: Publishing new dummy token: { id_token: 'DEADBEEF', type: 'RFID' }
2023-01-16 18:21:24.884363 [INFO] auth:Auth        :: Received new token: {
    "id_token": "DEADBEEF",
    "type": "RFID"
}
2023-01-16 18:21:25.004251 [INFO] token_validator  :: Got validation request for token 'DEADBEEF'...
2023-01-16 18:21:25.293769 [INFO] token_validator  :: Returning validation result for token 'DEADBEEF': { authorization_status: 'Accepted', reason: 'Token seems valid' }
2023-01-16 18:21:25.324475 [INFO] auth:Auth        :: Providing authorization to connector#1
2023-01-16 18:21:25.422809 [INFO] evse_manager:Ev  :: EVSE IEC EIM Authorization received
2023-01-16 18:21:25.423208 [INFO] evse_manager:Ev  :: EVSE IEC Transaction Started (0 kWh)
2023-01-16 18:21:25.423921 [INFO] evse_manager:Ev  :: EVSE IEC DC mode. We are in 5percent mode so we can continue without further action.
2023-01-16 18:21:25.433286 [INFO] evse_manager:Ev  ::                                     CAR IEC Event EnterBCD
2023-01-16 18:21:25.448283 [INFO] auth:Auth        :: Result for token: DEADBEEF: ACCEPTED
2023-01-16 18:21:25.474638 [INFO] evse_manager:Ev  :: EVSE IEC Charger state: WaitAuth->PrepareCharging
2023-01-16 18:21:25.655055 [INFO] evse_manager:Ev  :: EVSE IEC Set PWM On (5.000000074505806%)
2023-01-16 18:21:27.250763 [INFO] evse_manager:Ev  :: EVSE ISO SLAC MATCHING
2023-01-16 18:21:28.014143 [WARN] slac:EvseSlac   EvseFSM::EvseFSM(SlacIO&)::<lambda(EvseFSM::FSMContextType&)> :: Timeout in sounding, send results
2023-01-16 18:21:40.072722 [INFO] evse_manager:Ev  :: EVSE ISO SLAC MATCHED
2023-01-16 18:21:47.437792 [INFO] evse_manager:Ev  ::                                     CAR ISO V2G SupportedAppProtocolReq{
    "supportedAppProtocolReq": {
        "AppProtocol": [
            {
                "Priority": 1,
                "ProtocolNamespace": "urn:din:70121:2012:MsgDef",
                "SchemaID": 1,
                "VersionNumberMajor": 2,
                "VersionNumberMinor": 0
            }
        ]
    }
}
2023-01-16 18:21:48.023132 [INFO] evse_manager:Ev  :: EVSE ISO V2G SupportedAppProtocolRes{
    "supportedAppProtocolRes": {
        "ResponseCode": "OK_SuccessfulNegotiation",
        "SchemaID": 1
    }
}
2023-01-16 18:21:50.907918 [ERRO] iso15118_charge static void Log::error(const string&) :: ERROR - iso15118.shared.utils (51): [Errno 104] Connection reset by peer
Traceback (most recent call last):
  File "/usr/libexec/everest/modules/PyJosev/../../3rd_party/josev/iso15118/shared/utils.py", line 49, in wait_for_tasks
    task.result()
  File "/usr/libexec/everest/modules/PyJosev/../../3rd_party/josev/iso15118/shared/comm_session.py", line 449, in rcv_loop
    message = await asyncio.wait_for(self.reader.read(7000), timeout)
  File "/usr/lib/python3.10/asyncio/tasks.py", line 445, in wait_for
    return fut.result()
  File "/usr/lib/python3.10/asyncio/streams.py", line 669, in read
    await self._wait_for_data('read')
  File "/usr/lib/python3.10/asyncio/streams.py", line 502, in _wait_for_data
    await self._waiter
  File "/usr/lib/python3.10/asyncio/selector_events.py", line 854, in _read_ready__data_received
    data = self._sock.recv(self.max_size)
ConnectionResetError: [Errno 104] Connection reset by peer


Have you already seen this kind of error?

Thanks