hfiles (Customer) asked a question.
When I change screens in my project it looks as though the registers get reset to some default values even though they are not getting explicitly reset in my codesys project.
I have a cmore EA3-T4CL and a P2CDS-622 controller communicating over modbus. I was using an object to hide all inputs on my main screen during initialization if a variable is false. I have one line that I set to true once and do not reset it anywhere else in my code. When I switch between one screen and another this variable goes false.
The cmore hmi's registers will be updated regardless if the screen / data is hidden or not to my knowledge. I don't think you can reset or control register values via the c-more project.
I would look at the p2cds-622 program behavior to see why the modbus registers values are not what is expected.
It seems like the hmi breifly disconnects to load the next screen.
I am using holding registers, but when the hmi breifly disconnects, it appears that the registers go back to what they were first written as from the P2CDS-622 program.
I have a work around, but it doesn't make sense to me why even if the HMI did disconnect that the register would change.
My work around is basically if there is a bit in the holding registers packet that is false, then that means the hmi is briefly disconnected and the program will write the last written holding registers. Maybe its a problem with how codesys formatted the modbus communications?