# Problem where Different OPC tags are displaying the same value **URL:** \ **Category:** Ignition\ **Tags:** ignition79\ **Created:** [December 1, 2020, 4:56pm UTC](https://forum.inductiveautomation.com/t/problem-where-different-opc-tags-are-displaying-the-same-value/41094 "2020-12-01T16:56:09Z")\ **Posts on this page:** 15\ **Page:** 1
**Author:** ![paulm1](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paulm1/32/5900_2.png) [@paulm1](https://forum.inductiveautomation.com/u/paulm1)\ **Post date:** [December 1, 2020, 4:56pm UTC](https://forum.inductiveautomation.com/t/problem-where-different-opc-tags-are-displaying-the-same-value/41094/1 "2020-12-01T16:56:09Z")
I have an issue where every onw and then different OPC tags are displaying the same value, even though the actual PLC files contain different values. Another way of describing this issue is the OPC tags are not displaying the correct value. Below is a screen shot of the client display. ![DT tags](https://us1.discourse-cdn.com/inductiveautomation/original/3X/3/7/37308e2a57a10fc577b0851dfeda22249917fcc1.png) Here is one of the OPC tag property definitions. ![DT tags2](https://us1.discourse-cdn.com/inductiveautomation/original/3X/5/9/593b31206d5e926aff68ead7ebc2ccbd9895b399.png) Here is a screen shot of the Label Component’s Text Property Binding. ![DT tags3](https://us1.discourse-cdn.com/inductiveautomation/original/3X/c/6/c694416c7dc050b602f09559c1e4670091c2d8e3.png) The PLC being read is a Allen Bradley 5069-L330ERM CompactLogix 5380 Controller. The tags are DINT. The last time this happened it corrected itself and I was unable to trouble shoot. Anyone else ever encounter anything like this? Here is a screen shot of the PLC controller tags that are being read. It appears that the first address in the array (TimeDisplay[0].Hrs, .Mins and .Secs) is what is being displayed for all other TimeDisplay ignition OPC tags. ![DT tags4](https://us1.discourse-cdn.com/inductiveautomation/original/3X/6/7/67c2173911d3342cd0231f7877f3d0b7c8a659c1.png) ---
**Author:** ![robertm](https://avatars.discourse-cdn.com/v4/letter/r/ea5d25/32.png) [@robertm](https://forum.inductiveautomation.com/u/robertm)\ **Post date:** [December 1, 2020, 5:25pm UTC](https://forum.inductiveautomation.com/t/problem-where-different-opc-tags-are-displaying-the-same-value/41094/2 "2020-12-01T17:25:06Z")
If you go into the tag browser at the time this is happening, do the values match the PLC? Expand the tag to see all the sub members, and see how much is right/wrong. ---
**Author:** ![paulm1](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paulm1/32/5900_2.png) [@paulm1](https://forum.inductiveautomation.com/u/paulm1)\ **Post date:** [December 1, 2020, 5:32pm UTC](https://forum.inductiveautomation.com/t/problem-where-different-opc-tags-are-displaying-the-same-value/41094/3 "2020-12-01T17:32:40Z")
All the tags I am browsing are displaying the same values. They do not match the PLC. Appears that they are displaying the value from first tag in the array. See the screen shot below. ![DT tags5](https://us1.discourse-cdn.com/inductiveautomation/original/3X/b/8/b8d9069fbd23b30c34d2cbe0de545e4ffda6febf.png) ---
**Author:** ![MMaynard](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/mmaynard/32/3366_2.png) [@MMaynard](https://forum.inductiveautomation.com/u/MMaynard)\ **Post date:** [December 1, 2020, 6:59pm UTC](https://forum.inductiveautomation.com/t/problem-where-different-opc-tags-are-displaying-the-same-value/41094/4 "2020-12-01T18:59:05Z")
What firmware version on the PLC? If it is an older firmware the OPC address for those tags should be ns=1;s=[Cartoner]TimeDisplay.TimeDisplay[12].Mins Note the extra TimeDisplay ---
**Author:** ![paulm1](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paulm1/32/5900_2.png) [@paulm1](https://forum.inductiveautomation.com/u/paulm1)\ **Post date:** [December 1, 2020, 7:34pm UTC](https://forum.inductiveautomation.com/t/problem-where-different-opc-tags-are-displaying-the-same-value/41094/5 "2020-12-01T19:34:15Z")
Controller properties says it’s Revision 32.012 ---
**Author:** ![robertm](https://avatars.discourse-cdn.com/v4/letter/r/ea5d25/32.png) [@robertm](https://forum.inductiveautomation.com/u/robertm)\ **Post date:** [December 1, 2020, 7:50pm UTC](https://forum.inductiveautomation.com/t/problem-where-different-opc-tags-are-displaying-the-same-value/41094/6 "2020-12-01T19:50:10Z")
Why are the Tags Float8? I thought you were using Int4 (DINTs) in the PLC? I don’t know enough about Ignition yet to know if that has any effect, but it appears odd. ---
**Author:** ![paulm1](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paulm1/32/5900_2.png) [@paulm1](https://forum.inductiveautomation.com/u/paulm1)\ **Post date:** [December 1, 2020, 8:23pm UTC](https://forum.inductiveautomation.com/t/problem-where-different-opc-tags-are-displaying-the-same-value/41094/7 "2020-12-01T20:23:59Z")
That is what appears when you select “Double” from Data Type drop down list. ---
**Author:** ![paulm1](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paulm1/32/5900_2.png) [@paulm1](https://forum.inductiveautomation.com/u/paulm1)\ **Post date:** [December 1, 2020, 8:27pm UTC](https://forum.inductiveautomation.com/t/problem-where-different-opc-tags-are-displaying-the-same-value/41094/8 "2020-12-01T20:27:47Z")
> [@MMaynard](#): > > ns=1;s=[Cartoner]TimeDisplay.TimeDisplay[12].Mins When I made this change to the Tag's OPC Item path the tag reading faulted / errored. ``` ns=1;s=[Cartoner]TimeDisplay.TimeDisplay[12].Mins ``` ---
**Author:** ![nminchin](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/nminchin/32/6911_2.png) [@nminchin](https://forum.inductiveautomation.com/u/nminchin)\ **Post date:** [December 1, 2020, 8:33pm UTC](https://forum.inductiveautomation.com/t/problem-where-different-opc-tags-are-displaying-the-same-value/41094/9 "2020-12-01T20:33:43Z")
32 isn’t ‘older firmware’, which as Mike said, would require that syntax. ‘older’ is any thing below 21 (or 20.15… I’m still not sure where this line is) that use the older legacy driver ---
**Author:** ![MMaynard](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/mmaynard/32/3366_2.png) [@MMaynard](https://forum.inductiveautomation.com/u/MMaynard)\ **Post date:** [December 1, 2020, 8:42pm UTC](https://forum.inductiveautomation.com/t/problem-where-different-opc-tags-are-displaying-the-same-value/41094/10 "2020-12-01T20:42:14Z")
32 is newer so not the problem. Change each tag to data type Int, the main tag in the PLC is double but the individual tags should be Int. ---
**Author:** ![paulm1](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paulm1/32/5900_2.png) [@paulm1](https://forum.inductiveautomation.com/u/paulm1)\ **Post date:** [December 1, 2020, 8:51pm UTC](https://forum.inductiveautomation.com/t/problem-where-different-opc-tags-are-displaying-the-same-value/41094/11 "2020-12-01T20:51:29Z")
Made the changes to each tag’s Data Type and no change. ---
**Author:** ![paulm1](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paulm1/32/5900_2.png) [@paulm1](https://forum.inductiveautomation.com/u/paulm1)\ **Post date:** [December 1, 2020, 8:55pm UTC](https://forum.inductiveautomation.com/t/problem-where-different-opc-tags-are-displaying-the-same-value/41094/12 "2020-12-01T20:55:26Z")
Now here is something strange. I went into the PLC program and added a rung that moves TimeDisplay[2].Hrs, TimeDisplay[2].Mins and TimeDisplay[2].Secs into separate files. Eaxample: TimeDisplay[2].Hrs into Panel\_dtHrs[2]. I then changed the Tag properties to display the new tag. Not only does the changed tag now read and display properly but all of them (even though unchanged) are displaying properly. Any ideas? ---
**Author:** ![MMaynard](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/mmaynard/32/3366_2.png) [@MMaynard](https://forum.inductiveautomation.com/u/MMaynard)\ **Post date:** [December 1, 2020, 9:17pm UTC](https://forum.inductiveautomation.com/t/problem-where-different-opc-tags-are-displaying-the-same-value/41094/13 "2020-12-01T21:17:13Z")
No idea, sounds like something got stuck in the OPC server? @Kevin.Herron might have some ideas but it’s above my pay grade now. ---
**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\ **Post date:** [December 1, 2020, 9:19pm UTC](https://forum.inductiveautomation.com/t/problem-where-different-opc-tags-are-displaying-the-same-value/41094/14 "2020-12-01T21:19:49Z")
Call support next time you notice this and before you do anything to make the values come in again 🤷‍♂️ I doubt this has anything to do with the datatype in Ignition but to clarify the correct Ignition datatype for a DINT in the PLC would be an Int4 / Integer in Ignition. It should be set to that automatically when you drag and drop it in. As described it sounds like a bug, but without being able to poke around it at I can’t really narrow it down - PLC firmware, OPC, tag system, bindings, who knows… ---
**Author:** ![paulm1](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paulm1/32/5900_2.png) [@paulm1](https://forum.inductiveautomation.com/u/paulm1)\ **Post date:** [December 1, 2020, 9:47pm UTC](https://forum.inductiveautomation.com/t/problem-where-different-opc-tags-are-displaying-the-same-value/41094/15 "2020-12-01T21:47:04Z")
Excellent. I will make sure and contact support when it happens again. Thank you. Worked with Aaron Palas, an Inductive tech. After looking my setup over he suggested trying to upgrade my ignition platform to a higher version of 7.9 to see if the OPC server upgrade will solve the issue. I will try to get this done as soon as I can and let you all know what the results are. Thank you for all your help.