# KepserverEX to Ignition mismatch **URL:** \ **Category:** Ignition\ **Tags:** perspective\ **Created:** [June 2, 2025, 3:57pm UTC](https://forum.inductiveautomation.com/t/kepserverex-to-ignition-mismatch/106903 "2025-06-02T15:57:36Z")\ **Posts on this page:** 13\ **Page:** 1
**Author:** ![matt.taheri.ca](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/matt.taheri.ca/32/73540_2.png) [@matt.taheri.ca](https://forum.inductiveautomation.com/u/matt.taheri.ca)\ **Post date:** [June 2, 2025, 3:57pm UTC](https://forum.inductiveautomation.com/t/kepserverex-to-ignition-mismatch/106903/1 "2025-06-02T15:57:36Z")
I have a value in Float that I'm reading from Kep server below picture ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/2/6/261de67af0d51843ffe98b8a50e204e7bd6c1f6c.png) and I configured a tag in ignition with the address provided at OPC UA client , (Below Picture) ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/3/0/30d3e922d230e7e36eadc9b6868f04df514af4e3.png) however rhar number I'm reading in Ignition is 901.00 (See below picture) ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/8/c/8c78186258482f978cc7659f15a0305416a89e6b.png) How should I convert data types toegt correct value ---
**Author:** ![ryan.white](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/ryan.white/32/73193_2.png) [@ryan.white](https://forum.inductiveautomation.com/u/ryan.white)\ **Post date:** [June 2, 2025, 4:01pm UTC](https://forum.inductiveautomation.com/t/kepserverex-to-ignition-mismatch/106903/2 "2025-06-02T16:01:36Z")
~~Preface the address with HRF (drop the R from your current address). ie, HRF10020~~ > **[Modbus Addressing | Ignition User Manual](https://www.docs.inductiveautomation.com/docs/8.1/ignition-modules/opc-ua/opc-ua-drivers/modbus/modbus-addressing#floatdouble)** > > Manually Addressing a Modbus Device edit: whoops, thought you were comparing kepware modbus connection to ignition modbus connection. ---
**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:** [June 2, 2025, 4:01pm UTC](https://forum.inductiveautomation.com/t/kepserverex-to-ignition-mismatch/106903/3 "2025-06-02T16:01:44Z")
You aren't looking at the same address. `R10020` vs `R00120`. ---
**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:** [June 2, 2025, 4:02pm UTC](https://forum.inductiveautomation.com/t/kepserverex-to-ignition-mismatch/106903/4 "2025-06-02T16:02:04Z")
~~He's using Kepware, not our Modbus driver, so not relevant.~~ edit: sorry @ryan.white, looks like I misread that because of the Kepware screenshot. He might be trying to switch from using Kepware to using the Ignition Modbus driver? ---
**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:** [June 2, 2025, 4:14pm UTC](https://forum.inductiveautomation.com/t/kepserverex-to-ignition-mismatch/106903/5 "2025-06-02T16:14:06Z")
> [@Kevin.Herron](#): > > using Kepware No, look at the second screenshot. He appears to be using Kepware with something else, and is trying to switch to a native IA driver. ~~I'd guess that word swapping needs to be changed.~~ ---
**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:** [June 2, 2025, 4:53pm UTC](https://forum.inductiveautomation.com/t/kepserverex-to-ignition-mismatch/106903/6 "2025-06-02T16:53:51Z")
Could still be the same wrong address problem. Given that `R00120` isn't a valid Modbus address for the Ignition driver I can only assume the address map is being used... which is discouraged @matt.taheri.ca ---
**Author:** ![matt.taheri.ca](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/matt.taheri.ca/32/73540_2.png) [@matt.taheri.ca](https://forum.inductiveautomation.com/u/matt.taheri.ca)\ **Post date:** [June 2, 2025, 5:05pm UTC](https://forum.inductiveautomation.com/t/kepserverex-to-ignition-mismatch/106903/7 "2025-06-02T17:05:09Z")
I have kep server installed and OPC UA client would show Kep server tags data, I have changed the address to [HS1]R00120 and the data is changed to -13,107.00 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/d/c/dc9466e1828b41e5b8f72eec7dcb11900bb2b389.png) My PLC device is mitsubishi Q series , ---
**Author:** ![Transistor](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/transistor/32/3380_2.png) [@Transistor](https://forum.inductiveautomation.com/u/Transistor)\ **Post date:** [June 2, 2025, 5:13pm UTC](https://forum.inductiveautomation.com/t/kepserverex-to-ignition-mismatch/106903/8 "2025-06-02T17:13:41Z")
Tip: it's "Kepserver" or "KepserverEx" (not "Kep server"). It may help others find this thread if you fix your question title. ---
**Author:** ![matt.taheri.ca](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/matt.taheri.ca/32/73540_2.png) [@matt.taheri.ca](https://forum.inductiveautomation.com/u/matt.taheri.ca)\ **Post date:** [June 2, 2025, 5:25pm UTC](https://forum.inductiveautomation.com/t/kepserverex-to-ignition-mismatch/106903/9 "2025-06-02T17:25:01Z")
> [@Transistor](#): > > KepserverEx Thanks for the tip ---
**Author:** ![matt.taheri.ca](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/matt.taheri.ca/32/73540_2.png) [@matt.taheri.ca](https://forum.inductiveautomation.com/u/matt.taheri.ca)\ **Post date:** [June 2, 2025, 5:35pm UTC](https://forum.inductiveautomation.com/t/kepserverex-to-ignition-mismatch/106903/10 "2025-06-02T17:35:46Z")
Any suggestion as to what other addresses I cn use ? ---
**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:** [June 2, 2025, 5:46pm UTC](https://forum.inductiveautomation.com/t/kepserverex-to-ignition-mismatch/106903/12 "2025-06-02T17:46:52Z")
> [@matt.taheri.ca](#): > > other addresses Do this: > **[Modbus Addressing | Ignition User Manual](https://www.docs.inductiveautomation.com/docs/8.1/ignition-modules/opc-ua/opc-ua-drivers/modbus/modbus-addressing#manually-addressing-a-modbus-device)** > > Manually Addressing a Modbus Device ---
**Author:** ![michael.flagler](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/michael.flagler/32/26272_2.png) [@michael.flagler](https://forum.inductiveautomation.com/u/michael.flagler)\ **Post date:** [June 2, 2025, 8:49pm UTC](https://forum.inductiveautomation.com/t/kepserverex-to-ignition-mismatch/106903/13 "2025-06-02T20:49:43Z")
If you're using the Mitsubishi driver, you'll want to follow the manual here: > **[Mitsubishi TCP Driver | Ignition User Manual](https://www.docs.inductiveautomation.com/docs/8.1/ignition-modules/opc-ua/opc-ua-drivers/mitsubishi-tcp-driver)** > > The Mitsubishi TCP driver provides a user interface in the Gateway where you can create, import, or export addresses when connected to devices that support the MELSEC protocol. After setup, configured tags will be browsable in the OPC Browser of the... I've never used a Mitsubishi device, but it looks like there are modifiers to specify the data type and also byte ordering. It's possible it needs some form of modification to get it to work properly. ---
**Author:** ![jnqplas](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/jnqplas/32/4054_2.png) [@jnqplas](https://forum.inductiveautomation.com/u/jnqplas)\ **Post date:** [July 10, 2025, 2:51pm UTC](https://forum.inductiveautomation.com/t/kepserverex-to-ignition-mismatch/106903/14 "2025-07-10T14:51:59Z")
Maybe you've already fixed your problem. But from my understanding of your original post, you're trying to use KepserverEX as the OPC Server and Ignition as a client, rather than setting up the native Ignition OPC driver? So you want Ignition reading from Kepware? If that's correct, one thing I see is that your **OPC Server** name looks a lot like the (our?) default Ignition server. When I access KepserverEX tags in Ignition, I need to select the KepserverEX OPC Server. Also, I don't know what your custom parameters look like, but does [HS1] accurately define your HS1.HS1.HS\_ChillerIn path? My **OPC Item Path** in Ignition would look more like: nsu=KepserverEXname;s=HS1.HS1.HS\_ChillerIn or ns=2;s={custom channel/device path parameters}.HS\_ChillerIn Admittedly, I have no idea what the 'nsu' or 'ns=2;s=' means.