Config BMENOC0301 to I/O Scan Another BMENOC0301 with 902-928MHz radio modem

[NickWheeler]

Hello everyone,

Quick rundown of my issue: I currently have two systems (let’s call the 1st “C” and the 2nd “E” for naming purposes). C and E are running M580 (BMEP584040 CPUs) with two NOC modules (BMENOC0301). These NOC modules are connected via Ethernet through the service port to 900MHz radio modems. The purpose of this setup is for system C to communicate with system E using the 900MHz modems. System C will need to read and write to E and vice versa.

Before the new M580 hardware, we used Quantum controllers with the radio modems, and there was PLC logic that used Master blocks to send data between the two systems. That PLC logic still exists, but I’m thinking it will be useless now. Data was packaged and moved from one system to the other via the Master blocks. This was all done in Proworx, and currently, Ecostruxure doesn’t use Master blocks.

My current issue is configuring the NOCs for systems C and E for I/O scanning. I’ve seen a couple of videos on how to do the I/O scanning, but I don’t feel like they were very helpful. I was wondering, do I need to configure the NOCs to look at the modems, or do I need to configure the NOCs to look at each other? I am very new to this hardware, and any help would be greatly appreciated.

[RoozeeR]

Hello Nick,

The advantage of the communication functions is basically they use the TCP timeout and communication scheme, which allow for slow connections with timeouts and retry's. The IO-scanning is normally used for direct connections with a more strict (aggressive) method for timeouts. Specially when using gateways or in your case radio modems this could cause issues. So if you want to try using IO scanning, device the NOC module as type 301.4 (or 311.4) which give the advantage of setting for each connection as a "Gateway/Bridgedevice", which cause a less aggressive (fast) way of retry and reconnections after a communication issue. Also set the "Repetitive Rate" to something reasonable , as the default (is 60 mS) might be to fast for your radio link

The communication status of the IO scanning can be retrieved from the Communication Datastructure "Freshness" bit status.