Still getting '0' with that change. Strangely, I'm getting '0' no matter what number I put after HRF. I even tried 260 which is robot powered on, still getting '0'
You don't Need the node id info in the opc item path [UR3 Modbus]HR255is valid.
This image is reading from port_resgister 128 of the robot with zero based addressing.
I just realized he using HRF. Try HR to verify that you are reading the correct registers.
I'm replying here on behalf of Cody Chamberlain. You were assisting him earlier but he ran out of replies as a new user. I have a meeting to go to, so if there is some way around that restriction, please message him further. If not, you can email him at Cody.Chamberlain@brother.com.
That was due to me recommending that, as they had the tag configured as a Float. I assumed they were attempting to pass a float from the robot to Ignition.
1 Like
I would Try HRI to get two consecutive registers not a HRF.
It was never discussed what the register was actually. So i wasn't sure how big the value would be.
So It turns out the ur robot needs the unsigned conversion [UR3 Modbus]HRUS255 will bring the full 16 bit value.
I tested this on a ursim passing in a value of 65534 to a variable and writing to the port register 128
1 Like