I had an issue with this opc tag, this tag as u can see on the screen is the same identical tags with same address, can u explain me wy 1 is on good and the other in on bad_notconnected?
Your screenshot cuts off too early - is the configured OPC Server the same for both tags?
Did you create this tags by drag and drop?
Does it happen every time, for any tag from this server, when creating duplicates?
Tip: resize the window before taking a screengrab. Yours is 95% whitespace with half a screen width between the label and the value making it hard to read. Reducing the window to 50% width would solve this.
1 Like
Yeah every time i create a duplicates on this server
Sounds like a bug with the server then.
If you can get a Wireshark capture with security for the connection disabled we can verify that.
Judging from the timestamps are we even sure the original tag is good? Its last timestamp was a year ago.
1 Like
I noticed that, my assumption is that the OPC server's clock is not set correctly. Since it's an OPC tag we're using the timestamp provided by the server.
I didn’t set up NTP on this PLC. However, after some testing, I discovered that if I change the value after copying the tag, it works. But if the tag value doesn’t change, the copy remains in a bad state.
Can't wireshark
Well, you could turn on the logger for DataValueConsumer to TRACE level and probably see the initial null/Bad_NotConnected come in, and then watch, uh... the absence of values arriving. But it's a little less compelling than something objective like a Wireshark capture when you have to go report a bug.
