I’m using an Energy Meter VM-3P75CT and have noticed that it does not seem to retain a VE.Can instance number when one is assigned through VictronConnect or an NMEA reader.
The unit shows the assigned instance number correctly in both VictronConnect and the NMEA reader, but once the device is power-cycled it loses the assignment. I can’t read data using the assigned instance number (before or after the power cycle). The only way I can get information is by querying what appears to be its default instance (instance 1).
Is this behavior intentional, or should the meter be able to store and use the reassigned instance number?
Hi @lavajelly ,
We tried to reproduce your issue in the lab, but were unable to. When the VE.Can device instance number is changed and the meter rebooted, the number is the same as for the reboot. I assume your meter is directly connected via VE.Can or is this about the virtual meter for the grid forward via Ethernet? Is this system on vrm?
We tested it on versions, 1.09, 1.1 and 1.11. we have tried multiple ways of changing the number using an Actisense on a NMEA bus and Victron connect over ethernet.
I was able to reproduce this issue now as there is a difference between a power cycle and a reset, like I did. Can you try changing another setting after you’ve changed the device instance? For example the role and then change it back. This should ensure that the device instance is stored to non-volatile memory. We will fix this in the next release.