# Yokagawa GX20 Modbus TCP

**URL:** <https://forum.inductiveautomation.com/t/yokagawa-gx20-modbus-tcp/19297>\
**Category:** Ignition\
**Created:** [August 16, 2018, 11:39pm UTC](https://forum.inductiveautomation.com/t/yokagawa-gx20-modbus-tcp/19297 "2018-08-16T23:39:28Z")\
**Posts on this page:** 12\
**Page:** 1

<div class="post-metadata">

**Author:** ![winslow\_352](https://avatars.discourse-cdn.com/v4/letter/w/c2a13f/32.png) [@winslow\_352](https://forum.inductiveautomation.com/u/winslow_352)\
**Post date:** [August 16, 2018, 11:39pm UTC](https://forum.inductiveautomation.com/t/yokagawa-gx20-modbus-tcp/19297/1 "2018-08-16T23:39:28Z")

</div>

Hi all, Im try to set up a Yokagawa GX20 chart recorder to read and write to ignition through modbus TCP. I have no experience with modbus or these chart recorders. I can get ignition to connect to the chart recorders but I can not get any tags to link up. Actually I did but somewhere I changed a setting in either the chart recorder or ignition and now all I get is a a ? mark on the tags.These chart recorders can be setup as either the client/master or server/slave. I am a little confused on the whole client/server master/slave setup but what I understand is that ignition is the client and the chart recorder is the server. Am I correct? I downloaded a modbus scanner onto the ignition server and it pulled all values in that I am looking for so I know i can reach the recorder. Any help is much appreciated.

Thanks

---

<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:** [August 17, 2018, 1:25am UTC](https://forum.inductiveautomation.com/t/yokagawa-gx20-modbus-tcp/19297/2 "2018-08-17T01:25:15Z")

</div>

Now that you know what addresses are valid you just need to make some tags in Ignition.

The address syntax to use in the OPC Item Path is explained [here in the user manual](https://docs.inductiveautomation.com/display/DOC79/Modbus+Addressing).

---

<div class="post-metadata">

**Author:** ![winslow\_352](https://avatars.discourse-cdn.com/v4/letter/w/c2a13f/32.png) [@winslow\_352](https://forum.inductiveautomation.com/u/winslow_352)\
**Post date:** [August 17, 2018, 2:05am UTC](https://forum.inductiveautomation.com/t/yokagawa-gx20-modbus-tcp/19297/3 "2018-08-17T02:05:56Z")

</div>

I have made some tags but they are not connecting. There are 5 int32 tags and i am looking at gathering 300001 through 300010. I have tried addressing them in ignition a couple of different ways start 1 end 10, step is checked, input register(int32), address 1and a couple of different combinations but when i bring the tags in they are dispaying null values but when i run the modbus scanner they do have actual values in them. tags are green with ?marks on them.

any more Ideas? Im assuming its on the chart recorder side of things but not sure what to look for.  
thanks again!!

---

<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:** [August 17, 2018, 2:19am UTC](https://forum.inductiveautomation.com/t/yokagawa-gx20-modbus-tcp/19297/4 "2018-08-17T02:19:54Z")

</div>

Try toggling the one-based addressing setting in the driver.

If that doesn’t work, instead of using the mapping, try creating just one tag manually with an address like `[device-name]IRI1`. Maybe use Wireshark to capture the traffic from Ignition vs the traffic from the scanner.

---

<div class="post-metadata">

**Author:** ![Herbie](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/herbie/32/65288_2.png) [@Herbie](https://forum.inductiveautomation.com/u/Herbie)\
**Post date:** [August 17, 2018, 2:57pm UTC](https://forum.inductiveautomation.com/t/yokagawa-gx20-modbus-tcp/19297/5 "2018-08-17T14:57:49Z")

</div>

Another thing to check is to verify if the High/Low word setting is correct as well. Modbus itself does not define 32-bit data types, but rather 16-bit only. For 32-bit data types, each vendor can implement the High/Low word order and is not consistent.

---

<div class="post-metadata">

**Author:** ![winslow\_352](https://avatars.discourse-cdn.com/v4/letter/w/c2a13f/32.png) [@winslow\_352](https://forum.inductiveautomation.com/u/winslow_352)\
**Post date:** [August 17, 2018, 5:34pm UTC](https://forum.inductiveautomation.com/t/yokagawa-gx20-modbus-tcp/19297/6 "2018-08-17T17:34:58Z")

</div>

Hi guys thanks for your ideas. One quick question. Is ignition a client or is it a server in the modbus world? Thanks

---

<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:** [August 17, 2018, 5:42pm UTC](https://forum.inductiveautomation.com/t/yokagawa-gx20-modbus-tcp/19297/7 "2018-08-17T17:42:31Z")

</div>

It’s a client aka master.

---

<div class="post-metadata">

**Author:** ![winslow\_352](https://avatars.discourse-cdn.com/v4/letter/w/c2a13f/32.png) [@winslow\_352](https://forum.inductiveautomation.com/u/winslow_352)\
**Post date:** [August 17, 2018, 5:47pm UTC](https://forum.inductiveautomation.com/t/yokagawa-gx20-modbus-tcp/19297/8 "2018-08-17T17:47:18Z")

</div>

Hi Kevin, I tried the couple of things you asked. When in wireshark I do not see any modbus requests unless I run the modbus scanner then I see a query from the server ip address and a response from the chart recorder. I was pretty sure that Ignition was client so shouldn’t I see it querying?  
I really appreciate your help.

---

<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:** [August 17, 2018, 5:51pm UTC](https://forum.inductiveautomation.com/t/yokagawa-gx20-modbus-tcp/19297/9 "2018-08-17T17:51:42Z")

</div>

Might be time to call in and let support take a look.

---

<div class="post-metadata">

**Author:** ![winslow\_352](https://avatars.discourse-cdn.com/v4/letter/w/c2a13f/32.png) [@winslow\_352](https://forum.inductiveautomation.com/u/winslow_352)\
**Post date:** [August 17, 2018, 6:07pm UTC](https://forum.inductiveautomation.com/t/yokagawa-gx20-modbus-tcp/19297/10 "2018-08-17T18:07:52Z")

</div>

Great minds think alike I just called them and are waiting for their call back.

Thanks again!!

---

<div class="post-metadata">

**Author:** ![jtorres](https://avatars.discourse-cdn.com/v4/letter/j/c67d28/32.png) [@jtorres](https://forum.inductiveautomation.com/u/jtorres)\
**Post date:** [May 10, 2021, 5:20pm UTC](https://forum.inductiveautomation.com/t/yokagawa-gx20-modbus-tcp/19297/11 "2021-05-10T17:20:01Z")

</div>

Hi winslow , excuse me, Would you have a Modbus TCP mapping register about the GX20?

---

<div class="post-metadata">

**Author:** ![Cullen\_Sloboda1](https://avatars.discourse-cdn.com/v4/letter/c/73ab20/32.png) [@Cullen\_Sloboda1](https://forum.inductiveautomation.com/u/Cullen_Sloboda1)\
**Post date:** [August 14, 2024, 11:04pm UTC](https://forum.inductiveautomation.com/t/yokagawa-gx20-modbus-tcp/19297/12 "2024-08-14T23:04:58Z")

</div>

+1 for how this resolved for you Winslow! I myself am trying to remap an old GX20 (with a connected GM10 underneath) to the newest version of ignition (8.1.42) and since the recent update (6/24) the old (relative) address mapping scheme we used on our old gateway will not work on the new!  
We were able to backup/restore our old gateway to a new server (running 8.1.42) and somehow the address mapping scheme was bypassed from being in the gateway config backup file.

Although this is a major barrier since we are looking to set up a 2 gateway system now parallel to the old (to accommodate more devices/features)
