EcomEx Issues

[pbw]

Hi, I'm having issues with a EcomEx POM going offline. My setup is as follows....
I have 3 seperate BX-DM1E-M systems that each have 2 BX-DMIO on their Primary Port (Internal Ethernet)....10.10.10.x
So the Internal Port has only the 2 IOs to talk to , nothing else on the network.
I have a EcomEx POM installed which is connected to the company network....which would include a C-More for each PLC Station. The POM is on 192.168.4.x
Initially I had everything running on the Primary Port without issues, but I thought it would be a good idea to segregate the network by adding a EcomEx and leave the slaves on the Primary Port and have everything else on the POM. I installed the POms on Tuesday.
Everything works for roughly 24hrs....then the C-More reports PLC offline....The first day I did a PLC Power Cycle and lost all coms....including Primary port IOs....I had to go online and rescan and configure them. Then all was well for roughly 24 Hrs
Yesterday when the issue reappeared....on all 3 machines, I just reseated the POM and the issue disappeared....Are there any status registers that might give me some insight into what could possibly be happening?
When I installed the Poms, the PLCs where running 2.9.7....after the 1st failure, I was hoping an update would fix it, but I see the same issues with 2.10.3.
Any thoughts?

[pbw]

Could it be Do-More Designer related?
Friday and Saturday....I didn't connect to 2 PLC stations, and they are operating without a problem....I have been connected to the third station on both days and have had the issue surface @ roughly the same time on both days.

[pbw]

Apparently not Designer related....did not connect to the PLCs on Sunday....and all 3 of them are showing unresponsive POMs this morning.
Unplugging the Ethernet cable does nothing, I have to physically reseat the POM for it to recover.

[Greg]

I don't pretend to know why the ECOM-EX is losing comms, unless it is, for whatever reason, running out of resources somehow.

The ECOM-EX and the Built-in port BOTH use the same TCP/IP stack. The Gateway address configured for the Built-in port has priority. There cannot be two Gateway addresses. I mean, you can configure the ECOM-EX and the Built-in to have two different Gateway addresses, but only one will be used, and the Built-in has priority. The best way to think of this is one is a WAN (needs a Gateway) and the other is a LAN (doesn't need a Gateway). So, in my way of thinking of this, I would put the DMIOs on the LAN (no Gateway address needed, or configured), and the office network & HMI on the WAN (Gateway required and configured).

So, delete the Gateway address for the Built-in controlling the DMIOs, if you haven't already done so.

Now, in troubleshooting the issue:

• Monitor DST72 ($FreePackets). The value here should hover around 375. If it starts to trend downward, turn ON ST300. This will then cause DST98-399 to fill with connection data that we can take a look at.
• You can also turn ON ST301, which will cause DST200-205 to fill with values. These values might also tell point us in a particular direction as to what is happening.