# Cannot Read Sensor after adding Ethernet IP Scanner

**URL:** <https://www.wago.community/t/cannot-read-sensor-after-adding-ethernet-ip-scanner/1259>\
**Category:** CODESYS\
**Tags:** how-to, codesys\
**Created:** [October 18, 2024, 9:20am UTC](https://www.wago.community/t/cannot-read-sensor-after-adding-ethernet-ip-scanner/1259 "2024-10-18T09:20:28Z")\
**Posts on this page:** 11\
**Page:** 1

<div class="post-metadata">

**Author:** ![umairyamin](https://avatars.discourse-cdn.com/v4/letter/u/dec6dc/32.png) [@umairyamin](https://www.wago.community/u/umairyamin)\
**Post date:** [October 18, 2024, 9:20am UTC](https://www.wago.community/t/cannot-read-sensor-after-adding-ethernet-ip-scanner/1259/1 "2024-10-18T09:20:28Z")

</div>

Hi all,

I am currently reading modbusTCP sensor using Codesys 3.5.19.2.

 ![image](https://us1.discourse-cdn.com/flex016/uploads/wago/original/1X/fddaebb57cc4438db913918ecaec910ba5030840.jpeg)

However, the value of the sensor somehow cannot be read after i add EthernetIP Scanner as shown picture below.

 ![image](https://us1.discourse-cdn.com/flex016/uploads/wago/original/1X/be546e74d931e63587afe9af612fb356e74bfcc5.jpeg)

Can someone explain to me why is this happening? Thank you in advance !

Best regards,  
Umair

---

<div class="post-metadata">

**Author:** ![MikePsaltis](https://sea2.discourse-cdn.com/flex016/user_avatar/www.wago.community/mikepsaltis/32/47_2.png) [@MikePsaltis](https://www.wago.community/u/MikePsaltis)\
**Post date:** [October 18, 2024, 3:48pm UTC](https://www.wago.community/t/cannot-read-sensor-after-adding-ethernet-ip-scanner/1259/2 "2024-10-18T15:48:24Z")

</div>

Hello,

If these devices are on the same network, and the ethernet bridge is set to switched, please add the EthernetIP scanner to the same Ethernet Device in the tree. It would then appear directly under the Modbus TCP connection, and you wont have “Ethernet\_1 (Ethernet)”.

---

<div class="post-metadata">

**Author:** ![umairyamin](https://avatars.discourse-cdn.com/v4/letter/u/dec6dc/32.png) [@umairyamin](https://www.wago.community/u/umairyamin)\
**Post date:** [October 21, 2024, 5:27am UTC](https://www.wago.community/t/cannot-read-sensor-after-adding-ethernet-ip-scanner/1259/3 "2024-10-21T05:27:54Z")

</div>

Hi,

Is it suppose to be like this? Still, no value appear.

 ![image](https://us1.discourse-cdn.com/flex016/uploads/wago/original/1X/85cfefc64ac48855c219ac3e0ec53a8704990da2.png)

---

<div class="post-metadata">

**Author:** ![WagoIcard](https://sea2.discourse-cdn.com/flex016/user_avatar/www.wago.community/wagoicard/32/1508_2.png) [@WagoIcard](https://www.wago.community/u/WagoIcard)\
**Post date:** [October 23, 2024, 4:19am UTC](https://www.wago.community/t/cannot-read-sensor-after-adding-ethernet-ip-scanner/1259/4 "2024-10-23T04:19:51Z")

</div>

I suppose the wAIx\_IP201 is declared in the Modbus TCP slave configuration ?  
Or is it a local variable using the “AT %IWxxx” ?  
What is the Modbus TCP slave configuration for its register and varaibles ?

---

<div class="post-metadata">

**Author:** ![VegardS](https://avatars.discourse-cdn.com/v4/letter/v/a88e57/32.png) [@VegardS](https://www.wago.community/u/VegardS)\
**Post date:** [October 23, 2024, 7:53am UTC](https://www.wago.community/t/cannot-read-sensor-after-adding-ethernet-ip-scanner/1259/5 "2024-10-23T07:53:32Z")

</div>

I had the same issue and support in Germany wrote the following back in July:

_«…recently we’ve got similar requests like this. In all those tickets two fieldbus systems are used and one of those is EtherNetIP based. It seems that this occurs in the firmware versions 25 and 26. Last week firmware version 27 was published and this version fixed this behaviours. Please let your customer try it with firmware 27. In my opinion this will help your customer….»_

I have not tested FW27 with this setup to see if it actually fixed the behaviour.

I had the EIP Scanner under the same Ethernet driver;

 ![image](https://us1.discourse-cdn.com/flex016/uploads/wago/original/1X/a127e894a57b6c94dbef0a370e1689d0cd93f1f8.png)

My question to support:  
_I want to run a Modbus TCP master and an Ethernet/IP Scanner simultaneously on a PFC 200 (FW25), but as soon as I add the EIP scanner as shown in the image below, without any EIP devices configured under it, the Modbus TCP master stops receiving data._

_Everything seems to be fine with no diagnostic messages, and I can also see the request counter on the MB slaves increasing… However, as soon as I delete the EIP scanner and download the program again, I start receiving data from the MB slaves._

_What is wrong? As mentioned, it’s a PFC200 FW25 (750-8214), using Codesys 3.5.18.4._

I’m not in particular impressed with Wago FW testing recently …

---

<div class="post-metadata">

**Author:** ![umairyamin](https://avatars.discourse-cdn.com/v4/letter/u/dec6dc/32.png) [@umairyamin](https://www.wago.community/u/umairyamin)\
**Post date:** [November 15, 2024, 2:16am UTC](https://www.wago.community/t/cannot-read-sensor-after-adding-ethernet-ip-scanner/1259/6 "2024-11-15T02:16:54Z")

</div>

Hi,

this where the ModbusTCP configured.

 ![image](https://us1.discourse-cdn.com/flex016/uploads/wago/original/2X/e/efe0e13ea533afd9aca22d4145e2d05a40a2fdf7.png)

---

<div class="post-metadata">

**Author:** ![umairyamin](https://avatars.discourse-cdn.com/v4/letter/u/dec6dc/32.png) [@umairyamin](https://www.wago.community/u/umairyamin)\
**Post date:** [November 15, 2024, 2:17am UTC](https://www.wago.community/t/cannot-read-sensor-after-adding-ethernet-ip-scanner/1259/7 "2024-11-15T02:17:28Z")

</div>

Hi,

glad to hear that im not the only one facing this issue. Thanks for the suggestion. will try this method.

---

<div class="post-metadata">

**Author:** ![umairyamin](https://avatars.discourse-cdn.com/v4/letter/u/dec6dc/32.png) [@umairyamin](https://www.wago.community/u/umairyamin)\
**Post date:** [November 19, 2024, 3:04am UTC](https://www.wago.community/t/cannot-read-sensor-after-adding-ethernet-ip-scanner/1259/8 "2024-11-19T03:04:46Z")

</div>

Hi Vegards,

I found the solution for this issue, it seems like mine is not related to firmware. Its just that I chose the wrong Ethernet adapter.

 ![image](https://us1.discourse-cdn.com/flex016/uploads/wago/original/2X/8/890c028321a4bd0573ed62f53de6d35e283fed9f.jpeg)

You have to choose the correct Ethernet Adapter to read both of them at the same time.

---

<div class="post-metadata">

**Author:** ![VegardS](https://avatars.discourse-cdn.com/v4/letter/v/a88e57/32.png) [@VegardS](https://www.wago.community/u/VegardS)\
**Post date:** [November 19, 2024, 8:29am UTC](https://www.wago.community/t/cannot-read-sensor-after-adding-ethernet-ip-scanner/1259/9 "2024-11-19T08:29:43Z")

</div>

Strange, wouldve thought those are identical.

Did you try to upgrade fw? What fw are you using and which fw upgraded from?

---

<div class="post-metadata">

**Author:** ![umairyamin](https://avatars.discourse-cdn.com/v4/letter/u/dec6dc/32.png) [@umairyamin](https://www.wago.community/u/umairyamin)\
**Post date:** [November 19, 2024, 8:41am UTC](https://www.wago.community/t/cannot-read-sensor-after-adding-ethernet-ip-scanner/1259/10 "2024-11-19T08:41:44Z")

</div>

Yes, my firmware previously was 25. Then I upgraded to 27. Then, using same code, im still unable to read ModbusTCP. After looking closely, the WAGO support guy asked me to try change the Ethernet Adapter by using the above one instead of the below one. Then, Im successfully can read both of them at the same time.

---

<div class="post-metadata">

**Author:** ![VegardS](https://avatars.discourse-cdn.com/v4/letter/v/a88e57/32.png) [@VegardS](https://www.wago.community/u/VegardS)\
**Post date:** [November 21, 2024, 9:38pm UTC](https://www.wago.community/t/cannot-read-sensor-after-adding-ethernet-ip-scanner/1259/11 "2024-11-21T21:38:48Z")

</div>

Could it be that after the FW update, when changing the ethernet adapter, a newer version was used compared to previously with FW25?
