Hi all,
Using a raspberry pi 4 to collect data from Victron smart charge controllers using a Victron USB cable and reading with read_single_data from the python package called vedirect (https://github.com/nznobody/vedirect).
There are absolutely no communication errors when connecting to the Victron 100/30 and 150/45 (collecting about 1 data per second). However, when collecting data from 150/60 charge controllers, there are about 40 communication errors for 3 good messages.
Communication errors come from the fact that the collected data are not complete ie some data are missing.
{'PID': '0xA06B', 'SER#': 'HQ2249VPNQD', 'V': 25240, 'I': 0, 'VPV': 0, 'PPV': 0, 'MPPT': 0, 'CS': 0, 'OR': 1} instead of
{'PID': '0xA06B', 'SER#': 'HQ2249VPNQD', 'V': 25360, 'I': 0, 'VPV': 0, 'PPV': 0, 'MPPT': 0, 'CS': 0, 'OR': 1, 'ERR': 0, 'LOAD': 'ON', 'Relay': 'OFF', 'H19': 37, 'H20': 0, 'H21': 0, 'H22': 0, 'H23': 0, 'HSDS': 7}
There are also a lot of HEX messages when talking with 150/60 while none when talking to 100/30 or 150/45.
Wondering if anyone else noticed the differences between charge controller models? Can anyone help explain/fix the many short messages when connecting to the 150/60? Also is there a way to reduce the amount of HEX messages sent by the 150/60 controllers?
.
