# Kepserver/TopServer v6 Boolean addressing

**URL:** <https://forum.inductiveautomation.com/t/kepserver-topserver-v6-boolean-addressing/14023>\
**Category:** Ignition\
**Created:** [April 12, 2017, 2:40am UTC](https://forum.inductiveautomation.com/t/kepserver-topserver-v6-boolean-addressing/14023 "2017-04-12T02:40:18Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![CamJam](https://avatars.discourse-cdn.com/v4/letter/c/3ec8ea/32.png) [@CamJam](https://forum.inductiveautomation.com/u/CamJam)\
**Post date:** [April 12, 2017, 2:40am UTC](https://forum.inductiveautomation.com/t/kepserver-topserver-v6-boolean-addressing/14023/1 "2017-04-12T02:40:18Z")

</div>

Hi,

I have recently upgraded a TopServer from v5 to v6 and am having trouble getting Booleans in Ignition.  
Previously I would address it in the following format:

- ns=2:s=[ChannelDeviceName].[DeviceName].[address]  
e.g ns=2:s=Omron-FINS-Ethernet-1.The Pub.W0.02

now the only way I can get ‘good’ data from TopServer is by taking the .02 out, and looking at words.

- ns=2:s=Omron-FINS-Ethernet-1.The Pub.W0

Has anyone come across this before? Maybe I’m missing something in my TopServer configuration.

---

<div class="post-metadata">

**Author:** ![CamJam](https://avatars.discourse-cdn.com/v4/letter/c/3ec8ea/32.png) [@CamJam](https://forum.inductiveautomation.com/u/CamJam)\
**Post date:** [April 12, 2017, 8:31pm UTC](https://forum.inductiveautomation.com/t/kepserver-topserver-v6-boolean-addressing/14023/2 "2017-04-12T20:31:26Z")

</div>

So the problem was resolved by upgrading from Ignition 7.8.1 to 7.9.1  
Must have been something in the old OPC driver?

---

<div class="post-metadata">

**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:** [April 12, 2017, 8:47pm UTC](https://forum.inductiveautomation.com/t/kepserver-topserver-v6-boolean-addressing/14023/3 "2017-04-12T20:47:28Z")

</div>

Maybe… I can’t really think of anything that would cause that. Especially since it worked in TS v5 and stopped in v6.

But if you’ve got it working now then great 🙂
