# OPCUA, Kepware, tag quality showing BAD

**URL:** <https://forum.inductiveautomation.com/t/opcua-kepware-tag-quality-showing-bad/57377>\
**Category:** Ignition\
**Created:** [March 18, 2022, 7:47pm UTC](https://forum.inductiveautomation.com/t/opcua-kepware-tag-quality-showing-bad/57377 "2022-03-18T19:47:03Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Douglas\_Rudd](https://avatars.discourse-cdn.com/v4/letter/d/77aa72/32.png) [@Douglas\_Rudd](https://forum.inductiveautomation.com/u/Douglas_Rudd)\
**Post date:** [March 18, 2022, 7:47pm UTC](https://forum.inductiveautomation.com/t/opcua-kepware-tag-quality-showing-bad/57377/1 "2022-03-18T19:47:03Z")

</div>

I am working on a proof of concept project with the demo version to help justify the implementation of ignition in our plant. I have several PLC connected to kepware, I am able to connect and see all the data in all the tags from Ignition. all but two of the channels. the 2 channels that are showing bad in ignition but good in 2 other OPCUA clients happen to be connected to kepware via a serial connection, not sure if this has anything to do with why these 2 channels/plc’s are not picked up by ignition or not. any one else experienced this or can point me in the direction to start looking.  
thanks

---

<div class="post-metadata">

**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\
**Post date:** [March 18, 2022, 7:53pm UTC](https://forum.inductiveautomation.com/t/opcua-kepware-tag-quality-showing-bad/57377/2 "2022-03-18T19:53:29Z")

</div>

Serial channels are fundamentally single-user. But a server could multiplex complete messages on behalf of multiple clients. I would expect to find this in the Kepware docs for that driver.

---

<div class="post-metadata">

**Author:** ![kcollins](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kcollins/32/19646_2.png) [@kcollins](https://forum.inductiveautomation.com/u/kcollins)\
**Post date:** [March 18, 2022, 10:32pm UTC](https://forum.inductiveautomation.com/t/opcua-kepware-tag-quality-showing-bad/57377/3 "2022-03-18T22:32:19Z")

</div>

Typically you’d want to make sure your serial devices are defined under a single “channel” in KEPServerEx, that will make sure that requests across the devices are serialized (I’d typically then use aliases pointed to the various channel.device references so I could rearrange things in KEPServerEx without having to reconfigure clients). There is also a newer construct called “Virtual Network” that achieves the same thing (but can be used to bind together disparate channels). The advice of going to the docs is probably still a good idea–the strategy you use may depend on the KEPServerEx version you’re using. Plus, it has now been a couple years since I did a Kepware configuration… 😃 Only saving grace is that I used to do it a _lot_.

---

<div class="post-metadata">

**Author:** ![Douglas\_Rudd](https://avatars.discourse-cdn.com/v4/letter/d/77aa72/32.png) [@Douglas\_Rudd](https://forum.inductiveautomation.com/u/Douglas_Rudd)\
**Post date:** [March 21, 2022, 5:53pm UTC](https://forum.inductiveautomation.com/t/opcua-kepware-tag-quality-showing-bad/57377/4 "2022-03-21T17:53:57Z")

</div>

Thanks for all the replies, it turned out that I had fat fingers and missed typed the IP address. and it was pointed to the old kepserver and I had removed the serial connection on that server.  
(egg in face).