A customer has a system comprising a Cerbo GX, 2 x SmartSolar 100/20 (48V) connected individually via VE.Direct with a Quattro 10kVA and Pylontech batteries.
Originally installed with one SmartSolar 100/20 (48V) it operated without trouble. With the second connected, the original SmartSolar flags Error #66 constantly. Both controllers operate correctly and send their respective data to the Cerbo GX so there is no obvious fault, however Error #66 is flagged by the charge controller. The newer charge controller does not seem to have any issue. However the error on the original controller cannot be cleared.
All the firmwares have been updated to the latest (1.56 for SmartSolars, 485 for Quattro, 2.72 for Cerbo) and the settings in both SmartSolars have been reset to default and reconfigured the same for Pylontech batteries (48V LiFePO4 default, then alter Float/Absorption voltages to 51/52V respectively). The Quattro has very simple programming suitable for off-grid Pylontech usage.
The SmartSolar serial numbers are HQ 2044 and 2046 respectively so they are both recent units. The customer has tried to reset the Networked Operation in the Cerbo menu. There is no VE.Smart Networking set up.
Considering there is no way to reorder the communication (like VE.Can controllers) which has been mentioned previously for this issue, and there is no VE.Smart Network, are there any other known issues that may cause this? Would swapping the VE.Direct port alter the VRM Device Instance, or must the devices be removed from the system memory entirely?
Is there a way of rolling back the firmware of the SmartSolars; I don't see older versions on Professional.
