myp-cz
commented
2 years ago Further information:
This happens each every 49.7 days. Seems like a 4294967296 overflow bug somewhere in the software.
Only recovery is to restart the whole rPI platform.
Trying just to shutdown the solpiplog and start it again - does not work/help at all, as it is unable to obtain the usb connection again.
There is no need to restart the PIP inverter, as doing so does not do any difference, the solpiplog stays stuck. The rPI needs to be restarted in order to get it all going again.
Shutting down the solpiplog without rPI restart does not help as well. Even pressing STOP and then START in a running solpiplog (after said 49.7 days once it fails) does nothing to fix it.
It is interesting to note, that once solpiplog breaks, I can still send manual commands via Debug Window, BUT, the response shown by the debug window is completely different than what is expected (example: QID command - when all is OK, the serial number is in the response, but once it breaks, there is a set (long text) of zeros and spaces - too bad I have not captured it this time).
After approx 38 days online, the App got stuck, and had to reboot the rPi. Using single USB for a PIP-5048MK.
This is what have been found in console:
v3.1.0 Nuno Faria (c)2016-2020 nothing to see here ;) [FORMS.PP] ExceptionOccured Sender=EAccessViolation Exception=Access violation Stack trace: $00049D00 $0004AD2C Exception at 00049D00: EAccessViolation: Access violation.
--- Note this is v3.1.1 MAX executable although it writes the older version (3.1.0) to console.