News:

  • April 29, 2026, 10:05:12 AM

Login with username, password and session length

Author Topic: BX-P-Ecomex Communications Issues  (Read 68 times)

BTimpson

  • Newbie
  • *
  • Posts: 1
BX-P-Ecomex Communications Issues
« on: April 28, 2026, 05:28:33 PM »
Hello
I am of need some assistance with issues I am having with 2 BRX PLCs communicating using BX-P-Ecomex Modules.
The first PLC is a Bx-DM1E-18ED-D with the On Board IP Address 192.168.1.70 Subnet Mask 255.255.255.0 and the POM module IP address set to 10.10.10.1 Subnet Mask 255.255.255.0
The second PLC is a Bx-DM1E-18AR3 with the On Board IP Address 192.168.1.200 Subnet Mask 255.255.255.0 and the POM Module IP set to 10.10.10.2 and a Subnet Mask 255.255.255.0
I am using an RX (Do-More Network Read) from the first PLC to acquire the desired Elements from the second PLC.
The RX is set to target the 10.10.10.2 IP address and the interval is set to 10 seconds. I have adjusted the ACK Timout up to 1000 ms with no result change.
The problem i am having is it only acquires the information a few times an hour inconsistently.
All cabling has been confirmed good.
I have not wire sharked it yet.
I have pinged both POM Module IP addresses with the same result of 4 sent an only one success and 3 failed.
Any assistance would be greatly appreciated

MikeS

  • Host Moderator
  • Hero Member
  • *****
  • Posts: 261
    • Host Engineering, Inc.
Re: BX-P-Ecomex Communications Issues
« Reply #1 on: Today at 08:46:10 AM »
the RX instruction itself has three optional parameters that can help diagnose what's happening: On Success Counter, On Error Counter, and most importantly Extended Error Information which will tell you which row in the RX instruction is the issue and why.

You might also add a PING instruction before the RX instruction just to confirm the remote ECOMEX is available when you want to execute the RX.

Is your RX's Enable parameter set to 'Once on Leading Edge' or 'Continuous ... at interval' ? If the later, the instruction must stay enabled - I mention this because some customers in the past have placed the RX using 'at Interval' in a code block or Stage that does not remain enabled, so the RX's internal timer doesn't run.
Good design costs a lot. Bad design costs even more.