# Link tags from Schneider plc to ignition via modbus tcp connection

**URL:** <https://forum.inductiveautomation.com/t/link-tags-from-schneider-plc-to-ignition-via-modbus-tcp-connection/31924>\
**Category:** Ignition\
**Created:** [February 4, 2020, 8:43pm UTC](https://forum.inductiveautomation.com/t/link-tags-from-schneider-plc-to-ignition-via-modbus-tcp-connection/31924 "2020-02-04T20:43:36Z")\
**Posts on this page:** 15\
**Page:** 2

<div class="post-metadata">

**Author:** ![tarcio.sales](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/tarcio.sales/32/4999_2.png) [@tarcio.sales](https://forum.inductiveautomation.com/u/tarcio.sales)\
**Post date:** [December 7, 2020, 2:43pm UTC](https://forum.inductiveautomation.com/t/link-tags-from-schneider-plc-to-ignition-via-modbus-tcp-connection/31924/21 "2020-12-07T14:43:02Z")

</div>

Hi Kevin  
I have tried both ways. Reverse Word Order checked and not checked… same bad reading

---

<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:** [December 7, 2020, 3:16pm UTC](https://forum.inductiveautomation.com/t/link-tags-from-schneider-plc-to-ignition-via-modbus-tcp-connection/31924/22 "2020-12-07T15:16:56Z")

</div>

If you can get a valid reading out of a third party Modbus utility like modscan it’s usually pretty easy to figure out the correct address and settings in Ignition from there.

---

<div class="post-metadata">

**Author:** ![tarcio.sales](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/tarcio.sales/32/4999_2.png) [@tarcio.sales](https://forum.inductiveautomation.com/u/tarcio.sales)\
**Post date:** [December 7, 2020, 5:52pm UTC](https://forum.inductiveautomation.com/t/link-tags-from-schneider-plc-to-ignition-via-modbus-tcp-connection/31924/23 "2020-12-07T17:52:42Z")

</div>

Got it… I will try to do that.  
Thanks.

---

<div class="post-metadata">

**Author:** ![tarcio.sales](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/tarcio.sales/32/4999_2.png) [@tarcio.sales](https://forum.inductiveautomation.com/u/tarcio.sales)\
**Post date:** [December 7, 2020, 6:42pm UTC](https://forum.inductiveautomation.com/t/link-tags-from-schneider-plc-to-ignition-via-modbus-tcp-connection/31924/24 "2020-12-07T18:42:40Z")

</div>

> [@pturmel](#):
>
> IR

Hi Kevin, I was able to get a valid reading using the ShortBus Modbus Scanner.

Main settings:  
Option "0-Based" checked  
Result format: Floating Point

Any idea how could I set it to ignition ? Thanks a lot

See below:

 ![teste3](https://us1.discourse-cdn.com/inductiveautomation/original/3X/c/c/cc992a56aba55266ad262746e28c55bb69790139.gif)

---

<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:** [December 7, 2020, 6:47pm UTC](https://forum.inductiveautomation.com/t/link-tags-from-schneider-plc-to-ignition-via-modbus-tcp-connection/31924/25 "2020-12-07T18:47:07Z")

</div>

I missed this in your original post - you are not using the right address designators.

Try `1.HRF220` and `1.HRF240`, maybe plus 1, maybe with or without the reverse order.

Note the “F” in the address designating it a Float and causing the driver to read 2 registers for each value.

---

<div class="post-metadata">

**Author:** ![tarcio.sales](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/tarcio.sales/32/4999_2.png) [@tarcio.sales](https://forum.inductiveautomation.com/u/tarcio.sales)\
**Post date:** [December 7, 2020, 6:55pm UTC](https://forum.inductiveautomation.com/t/link-tags-from-schneider-plc-to-ignition-via-modbus-tcp-connection/31924/26 "2020-12-07T18:55:46Z")

</div>

Thanks a lot. It worked fine!

![teste33](https://us1.discourse-cdn.com/inductiveautomation/original/3X/2/0/2035167dfcdf7d5a38e32130ec3cdf3f7506fa64.gif)

Using:  
1.HRF\<Address+1\> and checked “Reverse Order”

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:** [December 7, 2020, 6:57pm UTC](https://forum.inductiveautomation.com/t/link-tags-from-schneider-plc-to-ignition-via-modbus-tcp-connection/31924/27 "2020-12-07T18:57:48Z")

</div>

I think you can get rid of the +1 offset by turning on zero-based addressing (or turning off one-based addressing, I forget which way it is displayed) in the Modbus driver settings in Ignition.

---

<div class="post-metadata">

**Author:** ![tarcio.sales](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/tarcio.sales/32/4999_2.png) [@tarcio.sales](https://forum.inductiveautomation.com/u/tarcio.sales)\
**Post date:** [December 7, 2020, 7:00pm UTC](https://forum.inductiveautomation.com/t/link-tags-from-schneider-plc-to-ignition-via-modbus-tcp-connection/31924/28 "2020-12-07T19:00:20Z")

</div>

Yeah! I found it

 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/8/9/8916582bf14caec939fb8aeff7e140153f899b1e.png)

the tag configuration is now: 1.HRF\<_Address_\>

---

<div class="post-metadata">

**Author:** ![tarcio.sales](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/tarcio.sales/32/4999_2.png) [@tarcio.sales](https://forum.inductiveautomation.com/u/tarcio.sales)\
**Post date:** [December 10, 2020, 3:02pm UTC](https://forum.inductiveautomation.com/t/link-tags-from-schneider-plc-to-ignition-via-modbus-tcp-connection/31924/29 "2020-12-10T15:02:31Z")

</div>

Hi Kevin  
One more time I need some help on same topic.  
I have some other tags I would like to retrieve the data, previously I got some %MW tags, now it is: %I and %Q as below:

Do you know how to refer the tag address to Modbus? I0.4.7.0 or Q0.5.4.0

![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/5/c/5c732ea02a1abb354be655879a1b64721323995b.png)

I read some topics as Mr PTurmel mentioned: “%QW as an HR, and the %IW as an IR. %Q is accessible as C, and %I is accessible as DI”

But I did not understand how to refer the address.  
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:** [December 10, 2020, 3:07pm UTC](https://forum.inductiveautomation.com/t/link-tags-from-schneider-plc-to-ignition-via-modbus-tcp-connection/31924/30 "2020-12-10T15:07:31Z")

</div>

No, sorry, I’m not familiar with these Schneider PLCs and I do not know how they map their own addresses into Modbus tables or whether it even happens automatically or not.

---

<div class="post-metadata">

**Author:** ![tarcio.sales](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/tarcio.sales/32/4999_2.png) [@tarcio.sales](https://forum.inductiveautomation.com/u/tarcio.sales)\
**Post date:** [December 10, 2020, 3:22pm UTC](https://forum.inductiveautomation.com/t/link-tags-from-schneider-plc-to-ignition-via-modbus-tcp-connection/31924/31 "2020-12-10T15:22:13Z")

</div>

OK. Thanks. When I figure out how, I will share here

---

<div class="post-metadata">

**Author:** ![brandon1](https://avatars.discourse-cdn.com/v4/letter/b/ea666f/32.png) [@brandon1](https://forum.inductiveautomation.com/u/brandon1)\
**Post date:** [December 11, 2020, 1:07pm UTC](https://forum.inductiveautomation.com/t/link-tags-from-schneider-plc-to-ignition-via-modbus-tcp-connection/31924/32 "2020-12-11T13:07:47Z")

</div>

Hey @tarcio.sales.

I don’t think it is possible with the Ignition Modbus driver. We always have to manually map those addresses to %M addresses. The other option is to set the racks up where they use %I and %M addresses sequentially. Hope this helps!

---

<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:** [December 11, 2020, 1:35pm UTC](https://forum.inductiveautomation.com/t/link-tags-from-schneider-plc-to-ignition-via-modbus-tcp-connection/31924/33 "2020-12-11T13:35:49Z")

</div>

I dug about a bit on the Schneider site and found the M340 manual. Per that manual:

- %Mzzz =\> Czzz
- %MWzzz =\> HRzzz
- %Izzz =\> DIzzz
- %IWzzz =\> IRzzz

It wasn’t clear from the manual if those are one-based or zero-based, but from the other results in this topic, I suspect it is zero-based.

---

<div class="post-metadata">

**Author:** ![tarcio.sales](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/tarcio.sales/32/4999_2.png) [@tarcio.sales](https://forum.inductiveautomation.com/u/tarcio.sales)\
**Post date:** [December 11, 2020, 1:59pm UTC](https://forum.inductiveautomation.com/t/link-tags-from-schneider-plc-to-ignition-via-modbus-tcp-connection/31924/34 "2020-12-11T13:59:58Z")

</div>

Hi @pturmel  
I got it when I read your first post but what I did not understand how to map the address number  
E.g:  
%I0.4.9.0  
You said I have to use: DIzzz but what’s the zzz ? 0490 or 0.4.9.0 or 049.0 etc… That’s my doubt! Thanks for your help.

@brandon1, thanks for your reply. I read some topics that says what you mentioned. I’d have to assign the %I to %M. I will await the Mr Pturmel’s reply to make sure it’s not possible.  
However, could you please tell me how to assign the %I to %M, I’m not familiar with Schneider PLC. Thanks a lot.

---

<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:** [December 11, 2020, 2:11pm UTC](https://forum.inductiveautomation.com/t/link-tags-from-schneider-plc-to-ignition-via-modbus-tcp-connection/31924/35 "2020-12-11T14:11:37Z")

</div>

I don’t know. I don’t use Schneider products. Lack of support for masked writes in current products suggest they’ve gone way downhill since my time working with Modicon processors. (Ancient history).

I gather the format with the dots is expressing rack.slot.word.bit. There must be some configuration in the PLC that associates the starting bit of an input module with a %Izzz, and the rest are sequential. The Modbus specification just uses one number, from 0 to 65535, to identify any given bit or word.

[Previous page](https://forum.inductiveautomation.com/t/link-tags-from-schneider-plc-to-ignition-via-modbus-tcp-connection/31924.md?page=1)
