pyPLC/doc/bug_analysis.md

Open issues

Issue 17: Welding detection fails

• WeldingDetectionRes says "failed" on alpitronics, and no response on ABBHPC and ABBTriple
• version v0.4-7-g7cea8b5 (2022-12-21)

Issue15: After end of PreCharging, the log says "re-initializing fsmPev"

• observed with v0.4 on the Compleo charger
• PreCharge target voltage is reached. The fsmPev sends a message 01fe800100000012809a022189cbf75b9625a9513022800a0800 and after one second the state machine seems to run into timeout.
• to be retested. Most likely fixed with with v0.4-7-g7cea8b5.

Closed issues

[Solved] Issue16: First CurrentDemandReq is rejected with FAILED_SequenceError and EVSE_Shutdown

• observed on Alpitronics HPC with version v0.4-6-g257e5af
• log 2022-12-20_alpi_currentDemandSequenceErrorShutdown.pcapng
• same result in two trys
• root cause: In the exi encoder, the PowerDeliveryReq.ReadyToChargeState was treated as enum as in the ISO, but in fact it must be boolean.
• Fixed with a00f1fba87
• Test pass 2022-12-21 with v0.4-7-g7cea8b5 on alpi, ABB HPC and ABB triple charger.

[Solved] Issue14: Connection loss after authorization

• with version v0.4.
• same version works fine on Compleo
• could be also caused by weak power of the powerbank. The TpLink and Dieter made restart from time to time.
• to be retested with better supply and on other chargers.
• Test pass with v0.4-6-g257e5af, with the Intenso two-cell powerbank.

[Solved] Issue12: Alpi reports "sequence error" for CableCheck

• with version v0.3.
• maybe he expects the state C, or something is wrong with the sequence before.
• Test pass with v0.4-6-g257e5af

[Solved] Issue13: Compleo SLAC stops after SlacParamResponse

• Root cause: The Compleo ignores the StartAttenChar, if the timeout field is set to 1000ms instead of the nominal 600ms.
• Solution: implemented the nominal 600ms.
• fixed with commit cf9160c1bc
• Test pass on Compleo with v0.4

[Solved] Issue10: Alpi says SequenceError in ChargeParameterDiscoveryRes

• ServicePaymentSelectionRes says "ResponseCode": "OK", and has no more fields.
• Afterwards we send ChargeParameterDiscoveryReq and get ChargeParameterDiscoveryRes containing "ResponseCode": "FAILED_SequenceError".
• Analysis: In the ISO case, the ChargeParameterDiscoveryReq comes after the AuthorizationRes with EVSEProcessing=Finished. But we are using DIN, and here there is no AuthorizationRes, but ContractAuthentication instead. But, this does not have a field EVSEProcessing. And in DIN, we have dinContractAuthenticationResType, which contains ResponseCode and EVSEProcessing (see OpenV2G, dinEXIDatatypes.h).
• Solution: Send ContractAuthenticationReq after ServicePaymentSelectionRes, and repeat it until it says "finished". Test pass with v0.3.

[Solved] Issue11: TCP connection fails on Alpi

• Observation: On Alpitronics, the SDP works, but the TCP connect fails. The connection is rejected by the charger.
• Root cause: We used fixed port 15118 for the TCP. This is not intended, even it works on other chargers (ABB).
• Solution: use the TCP port, which was announced in the SDP response.
• Test pass with version v0.2-9-ga9b6e82.