conradstone
Lifetime Supporting Member
ArmorBlock 2-Port EtherNet/IP Module
I am working on starting a plant up and we have a tremendous amount of these modules as the plant was designed to be as ¨cost effective¨ as possible. I have had several opportunities working on these gems and we have lost days of production due to problems associated with installation and a few problems with device failures. I am thinking of adding an AOI instruction to help detect their failures. Does anyone have any ideas and does AB have a module already defined and I just have seen it. I am listing the failure modes we have seen below.
1. Unit stops working with a red light on the comms, but no fault on diagnostic and if looking at the IO tree the module did not indicate a fault. Under Major/Minor faults none were listed and Comms showed connected, but no outputs and no change of states on Inputs
2. EtherNet/IP D-Code M12 connector the cables were field assembled using a spring mechanism and the Green Network cable. During a modification some of the cabling was pulled loose inside the strain relief. This caused part of our IO to show the small yellow triangles, but our diagnostics routines did not show a fault with the modules on Panelview.
3. 3. Loss of 24Vdc on DLR setup due to cabling/connector issues
4. Name 1732E-16CFGM12R 16 DC In/Out M12 Product Code 1732E-16CFGM12R this is out standard IO module and we use the Red Armor Safety module similar to this.
I was thinking of adding a simple cable loop where I set an Output On one port and read it on another once a second and if this fails setting my fault. This seems really brute force to me and surely something else is already programmed or setup in AB library, but all of the diagnostics that are supposed to show these errors didn´t work. If I did this it only cost one cable and a few lines of code. We only have 300 to 400 of these modules so my idea is a big undertaking. However we cannot keep losing days of production and bad products.
We use Ethernet IP and 1756-L83 to L85 processors with dedicated IO networks that are completely isolated from any outside network. V28 and couple V30 firmwares.
Thank you for any help. I am only here for a short time and I don´t want to leave my guys in a pickle.
I am working on starting a plant up and we have a tremendous amount of these modules as the plant was designed to be as ¨cost effective¨ as possible. I have had several opportunities working on these gems and we have lost days of production due to problems associated with installation and a few problems with device failures. I am thinking of adding an AOI instruction to help detect their failures. Does anyone have any ideas and does AB have a module already defined and I just have seen it. I am listing the failure modes we have seen below.
1. Unit stops working with a red light on the comms, but no fault on diagnostic and if looking at the IO tree the module did not indicate a fault. Under Major/Minor faults none were listed and Comms showed connected, but no outputs and no change of states on Inputs
2. EtherNet/IP D-Code M12 connector the cables were field assembled using a spring mechanism and the Green Network cable. During a modification some of the cabling was pulled loose inside the strain relief. This caused part of our IO to show the small yellow triangles, but our diagnostics routines did not show a fault with the modules on Panelview.
3. 3. Loss of 24Vdc on DLR setup due to cabling/connector issues
4. Name 1732E-16CFGM12R 16 DC In/Out M12 Product Code 1732E-16CFGM12R this is out standard IO module and we use the Red Armor Safety module similar to this.
I was thinking of adding a simple cable loop where I set an Output On one port and read it on another once a second and if this fails setting my fault. This seems really brute force to me and surely something else is already programmed or setup in AB library, but all of the diagnostics that are supposed to show these errors didn´t work. If I did this it only cost one cable and a few lines of code. We only have 300 to 400 of these modules so my idea is a big undertaking. However we cannot keep losing days of production and bad products.
We use Ethernet IP and 1756-L83 to L85 processors with dedicated IO networks that are completely isolated from any outside network. V28 and couple V30 firmwares.
Thank you for any help. I am only here for a short time and I don´t want to leave my guys in a pickle.