Problem between BRX and CMore EA9

[Watermark_JS]

We've got a BRX CPU connected with a CMore EA9 via Ethernet.  The network traffic runs consistently around 100kbps with Do-More Status turned on. 

The CMore is using a tri-state switch to set two bits (values: 00, 01, 10).  The bits are evaluated in the PLC to set an Integer value (V5202) to either 1 (00), 2 (01), or 4 (10).  V5202 is then used by the CMore to set the state of a Multi-State Text Indicator, which uses bit positions to set the text value (hence, setting the Integer to 1, 2 or 4).

We noticed that changing the Tri-State Switch value to set the Multi-State Text object state did not always work properly.  Changing between the switch states that resulted in an Integer value of 1 or 2 always work, but once the input condition results in an Integer value of 4, the Multi-State Text indicator gets "stuck." 

We added a numeric display to observe the value of V5202 directly and, as expected, it was "sticking" with a value of 4, causing the issue with the Multi-State Text object.  However, using either the Tri-State Switch or controls in our SCADA system to update V5202 work -- as the value correctly updates in a data view and on our SCADA system (which is communicating with the BRX over ModBus/TCP, regardless of whether V5202 is updating correctly in the CMore or not. 

V5202 is only "sticking" on the CMore side, and only when the value is set to 4.

We assumed the problem was isolated to the CMore but after messing with it for about half the day, we discovered that turning off Status in Do-More Designer causes the problem to go away.   

Thoughts...? 

[rlp122]

It is due to the way that Cmore handles certain data.  The data write attempt for some things only happens a single time.  If the PLC is busy and the packet gets dumped, then it never tries to update the object again.  Right, wrong or indifferent, this is how nearly every HMI handles certain tasks.  It's one reason I never use a One shot push button in an HMI, they just are not reliable.  Seems the multi-state falls into this same boat.

[Watermark_JS]

It is due to the way that Cmore handles certain data.  The data write attempt for some things only happens a single time.  If the PLC is busy and the packet gets dumped, then it never tries to update the object again.  Right, wrong or indifferent, this is how nearly every HMI handles certain tasks.  It's one reason I never use a One shot push button in an HMI, they just are not reliable.  Seems the multi-state falls into this same boat.

The issue is definitely with the Multi-State Text object, but not in the way we expected.  It finally occurred to us that the text was set to blink when V5202 was loaded with a value of 4.  Turning off the blink option solved the problem.

Anyway, the fact that turning Status on/off in DoMore Designer changed our troubleshooting results confused us for a bit.

I'm off to the AutomationDirect forum to complain about the Cmore!