Cozy35

OK, so my test bed has a runtime of 260 hours since I replaced the cable from the Inverter to the Pi. Sadly, the client site sill resets the runtime after the odd 6 to 18 hours after also replacing that cable. The difference is that the client site has Pylontech batteries with the Centurion Solar RS232 to USB cable.
I suspect that the cable as used on the Pylontech console to Pi cable is also suffering the same issues as the standard Axpert/Volronic USB cable in that it does not have the TXD & RXD wires in a twisted pair, nor is the cable screened from outside interference.
Out of 68 residential installations since January, it is imperative that I get this sorted out in order that I can offer the remote support additionally to my service contract to these clients. I will engineer a proper screened RS232 to USB converter cable to try and come to the bottom of the ICC resets.
More later.
 
 

OK, so my test bed has a runtime of 260 hours since I replaced the cable from the Inverter to the Pi. Sadly, the client site sill resets the runtime after the odd 6 to 18 hours after also replacing that cable. The difference is that the client site has Pylontech batteries with the Centurion Solar RS232 to USB cable.
I suspect that the cable as used on the Pylontech console to Pi cable is also suffering the same issues as the standard Axpert/Volronic USB cable in that it does not have the TXD & RXD wires in a twisted pair, nor is the cable screened from outside interference.
Out of 68 residential installations since January, it is imperative that I get this sorted out in order that I can offer the remote support additionally to my service contract to these clients. I will engineer a proper screened RS232 to USB converter cable to try and come to the bottom of the ICC resets.
More later.
 
 

Since swapping the 1.0 standard Axpert/Voltronic USB cable with the 2.0 cable, the system has been running without incident for 115 hours. It looks like that is what caused the comms/hardware issue as advised by Cent Solar.

The issue at hand is caused by the V1.0 USB cable as supplied by Voltronic.  The Pi 3B has 4 x V2.0 USB ports. V1.0 can transfer at max 12Mb/Sec and the v2.0 at 480Mb/Sec. logic says that the 1.0 cable could have been be the culprit. The 1.0 cable does not have the TxD & RxD wires in a twisted pair nor is there any screening as the case is with the 2.0 cable. This may suffer cross talk or outside interference - my opinion.
I replaced the 1.0 cable as supplied with all Voltronic inverters with a 2.0 cable.
The ICC Runtime is now at 42 hours, the best I have ever seen which never exceeded 6 hours before. I am not holding my breath just yet and I would like to see 72 hours or more before I can make the assumption that it was indeed the USB cable.
I hope I am correct with my finding, because it makes no sense that data rates as low as the Voltronic Inverter uses on the USB console port requires such a high data rate cable.