[Pieter]

I found the problems.
Communicator had two modbus lines looking at the same device. Thats issue one.
Second. I used the same signal number in my calculated value as in my main channel number. That caused the communicator to change to that signal which never updates again.

[Pieter]

Thank you. I just tested it. Now it works as I expected it to work.
Your formula is 100% accurate.

[Pieter]

I have watched the videos on youtube carefully.
I will start from scratch using only the one register value. Might be something conflicting.

[Pieter]

Arduino library to use arduino as modbus device.

“The library gives the program the possibility to be a master, a slave or both on a TCP network.
The Modbus functions 1, 2, 3, 4, 5, 6 15 and 16 are implemented.”

I have used this library successfully with kepserver enterprise and Kepware to communicate with Rockwell Factory talk view SE and panel views.

[Pieter]

Thank you manjey73. That is the exact formula i added.

It does not crash completely. I just do not get any information from it.
Input channel 23 is my modbus register that contains the byte value.

When I add the input channel to say 203, then I add the formula on 203 to look at 23 to scale the value. The value gets scaled correctly but it never updates again. Some other values in the same scheme is working, but the scaled value is frozen.
Also in the communicator screen the 23 gets changed to 203.

[Pieter]

Download from here

[Pieter]

For anyone that finds this. I use mgsmodbus for arduino. Works great aswell.

[Author]

Posts