I think the title says it all. Any advice?
Your title really doesn’t say it all. Handle it how?
2 Likes
My problem is this tag is acting as two separate datatypes!
The tag needs to be defined as a boolean datatype to write a 1 to the opc tag, but after I write a 1 to it, since the same tag then comes back as a string message, it would have to then be defined as a string. Does that clear up my question?
Where are you using this tag? Geez, give some real details.
In the designer.
Dude. Show your code. Show your tag configuration. Show your UI or however you are triggering the write. So far, you have provide zero information that would allow us to help you. ):
1 Like
What device are you talking to? And what data type is the tag in the device itself? It sounds like the raw data type in the end device is a string, so why are you reading it into ignition as a bool? Can you not write “1” to it? In which case, if it truly is meant to be a bool, why is it not a bool in the end device?
Here’s the tag configuraiton:
Here’s what I’m using in the tag browser:
Before I write
During write
Reading after I write
Info on the device/driver:
https://autosoln.atlassian.net/wiki/spaces/ACMDOCS/pages/215842828/ROC+Commands
Thanks a bunch
That link is to a boolean-driven command, which would usually result in the remote system doing something when you pulse that tag, then presenting the results on a different tag, not on the same tag replacing your boolean value.
You probably need to talk to the developer of that software and ask them to explain what should happen when you write a true to that tag. I’m guessing it updates this one:
https://autosoln.atlassian.net/wiki/spaces/ACMDOCS/pages/215875607/ROC+OPC+Items
1 Like