I know there are lots of topics related to read string tags, I read lots of them, I still cannot not get it to work.
When I read a controllgoix String tag, ignition creates a LEN tag and a DATA folder(PLC a String data type is actually a LEN tag as DINT, and DATA array of 82 SINT).
In the DATA Folder, the data array element is "short" data type, it is actually showing ASCII number.
Why can ignition read PLC String tag as string?
Does anybody know if Ignition has built in tool to read PLC string tag?
Has anybody find a reliable way to convert it into a tag?
Thank you.
Used drag-n-drop, did you? Try creating an OPC tag with datatype = string and configure the OPC Item Path to that string address.
1 Like
On all of the Ignition versions I've worked with, I've never had any issue just using the "browse devices" function to import a string tag. That automatically creates the OPC tag for me and everything. This is on a ControlLogix 1756-L72S:
EDIT: Just tried drag-and-drop (dragging over the entire string) and it worked as well. There may be something weird going on with OP's specific setup.
1 Like
Which driver and what version of Ignition are you using?
1 Like
My does not come in as String single tag. I comes as a folder.
1 Like
Ignition 8.1 and OPC-DA COM. I am reading simulator tag, it should not mater. all other normal data type are OK, except string.
Err, what? Okay so not using one of our drivers at all then?
In this case it's entirely up to the server you are connected to how a String is modeled.
1 Like
The problem is it come in as folder, and breaks array in to tags.
Is there some reason you are unable to use one of the Logix drivers to connect to the PLC? What model and firmware version is it?
I also have connection as device, it is showing the same thing.
It is not a PLC, it is the Emulator, just OPC tags from Emulator.
I might have to give up the idea of passing strings from PLC. I can just type the text in Ignition.
@Simen_Minerd have you tried this yet? It's a little more work but shouldn't be too bad if it works. You should still be able to copy the OPC path from the OPC browser panel, as well.
Unfortunately I'm guessing your options are pretty limited with RSLogix Emulate, see the following post:
I would expect this to work with a direct driver connect, but probably not with the OPC COM connection. With a direct driver connection the String shouldn't show up as a folder in the OPC browse.
2 Likes
I used the Default Loopback driver to connect to Emulator, it shows the same thin. It could be the communication model is use.
It could be the communication model issue.
You're not understanding me.
Ignition's OPC UA server has "drivers" to connect to different PLCs, including Logix.
You are apparently not using one of those, but rather using an OPC COM connection to the RSLinx? OPC server. This is fine, because most people can't seem to get connections to Emulate to work, and it's not clear whether they are even supported (see recent thread about this by @pdixon )
Yes, I am connected to RSLinx OPC server.
Browsing through that thread (I notice you've been on there as well, Simen), I saw that @pturmel and @jlandwerlen managed to get a direct driver to work as long as Emulate was v32 or higher:
If you could get that setup working you'd be in the clear.
Mine is vs32.