# Invalid data Honeywell SX Recorder using Modbus connection to furnace

**URL:** <https://forum.inductiveautomation.com/t/invalid-data-honeywell-sx-recorder-using-modbus-connection-to-furnace/31774>\
**Category:** Ignition\
**Created:** [January 30, 2020, 3:40pm UTC](https://forum.inductiveautomation.com/t/invalid-data-honeywell-sx-recorder-using-modbus-connection-to-furnace/31774 "2020-01-30T15:40:48Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![cathy.m.mccormick](https://avatars.discourse-cdn.com/v4/letter/c/f475e1/32.png) [@cathy.m.mccormick](https://forum.inductiveautomation.com/u/cathy.m.mccormick)\
**Post date:** [January 30, 2020, 3:40pm UTC](https://forum.inductiveautomation.com/t/invalid-data-honeywell-sx-recorder-using-modbus-connection-to-furnace/31774/1 "2020-01-30T15:40:48Z")

</div>

Hello- I am new to using Ignition. We are using 8.0.6 (perspective version) and I am connected to one of our furnace PLCs via a Honeywell SX chart recorder using a Modbus connection. The information that is being shown in Ignition for the furnace temperature is fluctuating in the billions (see attached) and even playing with the different variations with scaling hasn’t helped. We have another Honeywell recorder in another area of our facility that we are reading temperatures from and it seems to be reading accurately without any scaling. Any suggestions on what I need to look at or change?

 ![Honeywell%20Chart%20Recorder](https://us1.discourse-cdn.com/inductiveautomation/original/2X/a/aec8711a2c329b58615f81404432f02a5a90da6c.jpeg)  
Thank you,  
Cathy

---

<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:** [January 30, 2020, 7:12pm UTC](https://forum.inductiveautomation.com/t/invalid-data-honeywell-sx-recorder-using-modbus-connection-to-furnace/31774/2 "2020-01-30T19:12:14Z")

</div>

That usually means you need to change word swapping in the driver settings. Sometimes it could be one-based vs. zero-based addressing.

---

<div class="post-metadata">

**Author:** ![cathy.m.mccormick](https://avatars.discourse-cdn.com/v4/letter/c/f475e1/32.png) [@cathy.m.mccormick](https://forum.inductiveautomation.com/u/cathy.m.mccormick)\
**Post date:** [January 30, 2020, 7:38pm UTC](https://forum.inductiveautomation.com/t/invalid-data-honeywell-sx-recorder-using-modbus-connection-to-furnace/31774/3 "2020-01-30T19:38:29Z")

</div>

Sorry I am new to all of this- what does that mean and is this something that is done in Ignition configuration or at the recorder level?

---

<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:** [January 30, 2020, 9:16pm UTC](https://forum.inductiveautomation.com/t/invalid-data-honeywell-sx-recorder-using-modbus-connection-to-furnace/31774/4 "2020-01-30T21:16:12Z")

</div>

In Ignition, at the OPC Device level. Modbus, at its core, is 16-bit. It doesn’t specify the order for larger datatypes, and everybody and their brother has done it differently. So there’s a setting in the OPC device driver for Modbus in Ignition so that some can be little-endian and others can be big-endian.

---

<div class="post-metadata">

**Author:** ![cathy.m.mccormick](https://avatars.discourse-cdn.com/v4/letter/c/f475e1/32.png) [@cathy.m.mccormick](https://forum.inductiveautomation.com/u/cathy.m.mccormick)\
**Post date:** [February 3, 2020, 7:02pm UTC](https://forum.inductiveautomation.com/t/invalid-data-honeywell-sx-recorder-using-modbus-connection-to-furnace/31774/5 "2020-02-03T19:02:10Z")

</div>

Pturmel- Thank you for your assistance with this. Reversing the word order in the device settings did the trick.