Writing the same value to a modbus register using Crimson 3.1

erwilfo

Member
Join Date
Apr 2020
Location
Richmond, TX
Posts
1
All,

I must write the same value to a modbus register using on a Graphite HMI. Crimson prevents this, but according to technical support, the function "Force" should allow me to do it.

If I do a regular assignment (Register := Value;) it works as long as the new number is different to the one is currently store in Register. The device I am communicating with keeps a historic on changes in this register so I need to be able to write the value even if it is the same it is currently stored. I implemented the "force" function, and it is not writing even if the new value if different.

Has anyone dealed with this problem? Any input will be appreciated.

Thanks!
 
Welcome to the PLCTalk Forum community !

What exact Red Lion device are you using ?

Is the protocol Modbus RTU or Modbus/TCP, or something else ? What is the Modbus function code (coil, analog, holding, etc). ?


If you can provide a snippet of the code you're executing, folks might be able to help or test. I don't have any Crimson 3.1 devices but I've got a handful of ordinary 3.0 stuff.
 

Similar Topics

Hi. Not the fist time I'm saying this but just to give a background. 95% of my PLC programming has used Schneider over the last 10 years on...
Replies
66
Views
4,970
Hi, I'm having an issue in crimson 3.0 when I create a programme using a case statement referencing a fault word that each bit needs to change the...
Replies
5
Views
232
Hello all, I'm currently working on a servo motor linear positioning system (ball screw). I'm all set up regarding communication between my HMI...
Replies
1
Views
92
Hello All: I have a Windows 10 PC running a FTView ME Station 10.00. I have a .mer file version 6.00. It has been running well on it for a long...
Replies
1
Views
171
My R55 Ingersollrand is tripping on motor overload and im falling to see the trip history it is writing Acquarring texts
Replies
0
Views
134
Back
Top Bottom