We have an installation using a CanBMS protocol to send data for display.
On the test bench it works perfectly. In the field on separate machine, we have been banging our heads against the wall.
The system has a MG BMS, Quattro, and BMV use for Solar power generation. That works fine on the Ve.Can. We have another System we want to display in the Device list. Data is sent using the CanBMS protocol. The test bench has a “Old” Cerbo with BMScan port and Ve.Can port. data is displayed as expected on the GX.
In the field we have the same set-up, but no data can be seen. The canbus network is fully terminated, runs at 500kBds. The communication between all the systems nodes is working correctly. On the Cerbo CanBMS Network status page, we could see the Out Packet counter increasing on regular basis but no incoming messages seen. all error counters firmly at 0. On the canbus network, with our canbus monitor, we could see all the Batteries messages but we could not detect any message from the Cerbo.
After replacing the canbus stub cable with a factory made cable we came t the conclusion that the “old” cerbo may be damaged. We purchased a Brand new Cerbo MKII.
Once commissioned with the MG on Ve.can1 running at 250kbs lynx protocol and VE2.can running at 500kBds, CanBMS LV or CanBMS HV, we still see no data…
For both 500 Kbds protocol, the network status page report the STATE: STOPPED Where is the ON/OFF function ???
In all cases, the GX units have been upgraded to the latest V3.52
Kidding apart:
-
what is the difference between Can-bus BMS HV and Can-Bus BMS LV?
-
Why would this application work on Cerbo MK1 and not on cerbo MKII?
-
what does the state STOPPED means? Is this Hardware related, Set-up related or is it triggered by the network side?
-
Could it be that the unit I received has bad VE.Can2 ports (Pylontech BMS Connection Lost - firmware OS 3.51). How to verify?