I have found an issue with the “VRM device instances” menu in the new UI Venus OS v3.52. This menu is new to the new user interface and appears to allow the user to change the VRM instance number of a device. I decided to try the functionality by changing the VRM instance number of some Mopeka tank sensors. I was hoping changing the instance number would change the order the devices were displayed on the VRM dashboard. I tried the process several times and did it both from Remote Console and directly through the touch screen of the Cerbo GX (GX Touch 70). Each time it caused VRM to loose real time connection with the GX due to processor overload. I tried the process with both Venus OS v3.51 and v3.52 and got the same results.
The process I followed was:
I opened the VRM device instances menu through Remote Console on VRM
I scrolled to the devices I wanted to change. In my case, I started with my Mopeka Tank sensors. I have three Mopeka tank sensors in my system. The three sensors are labeled LPG Tank 1, LPG Tank 2, and LPG Tank 3. The original VRM instances were 36 for tank 1, 34 for tank 2 and 35 for Tank 3, which caused the sensors to display in a different order than the custom names I assigned. I wanted to change the instances to 34 for Tank 1, 35 for tank 2 and 36 for tank 3 so the tank names would display in the proper order on the VRM dashboard.
I made the VRM instance changes. I did this by manually changing the instance number of tank 1 to 34. The system prompted me that 34 was already in use and asked if I wished to swap the instance. I accepted the prompt to complete the swap. I repeated this process for the next tank and so on until I got the instance numbers where I wanted them to match the order of the tank names.
I then exited the VRM instances menu and was prompted to reboot the Cerbo for the changes to take affect.
I followed the prompt to reboot the Cerbo.
The Cerbo rebooted and I lost the ability to establish a real time connection with the Cerbo via VRM. A pop up menu appeared stating a real time connection was unable to be established due to processor overload.
I checked the VRM dashboard and the tanks were still being displayed in the original order (which was out of order based on the custom names). I checked the VRM device instances menu and the original device instances were still listed. In other words none of the changes I implemented took. I was still able to use Remote Console, but the VRM dashboard would not establish a real time connection.
The only way I could re-establish a real time connection was to physically go to the Cerbo unplug the power wires to complete a hard reset.
I reverted to Venus OS v2.51 and followed the above steps with the same results.
I then went to the touch screen of the Cerbo to remove remote console from the process.
I returned the Cerbo to Venus OS v3.52 and followed the above steps again. I got the exact same results. I lost the ability to establish a real time connection via VRM in the dashboard and the changes I implemented did not take. I did another hard reset of the Cerbo by removing the power wires. After this, I was able to re-establish a real time connection and the changes I implemented in the VRM device instances menu took affect. The new instances were in place and my tanks displayed in the desired order on the VRM dashboard.
Based on my experience, there are two bugs affecting the process. First, the VRM instance changes cause VRM to no longer establish a real time connection with the GX device until a hard reset is performed on the GX. Second, the process to change the VRM instances fails from remote console, but works when performed directly on the device.