We have found a possible issue with the max schedule array size with the latest release. According to the 2018 draft of ISO15118, V2G2-ED2-784 and 786 specify 12 entries for the PowerScheduleEntry. I have looked at the code and it specifies the maximum schedule array size as 5 entries. I have attached a PCAP file for the error. When we get to the ChargeParameterDiscoveryRes entry at line 205, the entry is not decoded in wireshark and the TCP connection is aborted by the vehicle. When we look at the same log file using Vector Canoe, we can see the 12 schedule entries.
OpenV2G uses static memory allocation (no malloc is used) with a fixed set of entries for arrays etc.
Everyone using the library (source code) can configure it according to the needs, see
entries in
https://sourceforge.net/p/openv2g/code/HEAD/tree/trunk/src/iso1/iso1EXIDatatypes.h
Defining the possible maximum for each would result in a huge static memory allocation.
I hope this helps to understand the rational.
-- Daniel