This FAQ has been written for NEAL (North East Africa and Levant) region. If you are looking for information for another region, please select the correct country from the top-left dropdown in the page and 'Navigate to Browse FAQs' in the Support menu.
In case you want to implement an IO scanning from the M580 to the M241 then the M580 would be a Modbus TCP client, and the M241 would be Modbus TCP servers that respond to the client's read / write requests.
The physical connection can always be made from the M580 service port. In case the reference of your M580 CPU does not end in "40", then your CPU does not have RIO messaging, implying that you can also use network ports (instead of the service port) to communicate to M241 (DIO messaging) . On the M241 side, it will use its Ethernet port. It will require a switch to build a star-type topology in case there's more than one PLC.
From the M241 side, they simply define their IP configuration (IP address, subnet mask and gateway), leave the Modbus TCP server functionality activated (it is active by default on the M241), and then locate in memory locations % MW the variables that want to read / write from the M580.
From the M580 side, after defining their IP configuration, they must add "modbus device" devices in the DTM browser, in order to implement the IO Scanning to the M241. Kindly check the below Video FAQ explaining how to implement the IO scanning of the M580:
You must add a "modbus device" for each M241, and they must add an IO scanning line for each read / write they want to do to the M241. Each line must point to the IP address of a given M241, and to the modbus indices of the% MW of the M241 to be accessed by the M580. For example, if you want to read the% MW100 of an M241, the "RD Address" of the modbus device should be 100 and the "RD length" should be 1.
Note that the M241 TCP server functionality corresponds to Unit ID = 255. In other words, Modbus TCP requests sent by the M580 must be addressed not only to the fixed IP address of each M241 but also to Unit ID = 255 Unit ID is the second column of the IO Scanning table.
Of course, all IP addresses (M580 + 6 M241) must be on the same network segment.
All of the above are in case there was no NOC card.
In case you want the NOC to be the Modbus TCP client instead of the CPU itself, then the steps are identical to what was previously explained, making the difference that the modbus device DTMs (which point to the M241) must be added to NOC instead of CPU in DTM Browser. If you leave the backplane port of the NOC disconnected from the backplane (default), then the Ethernet network of the NOC and the M241 is independent of the ETH network of the M580 CPU.
The physical connection can always be made from the M580 service port. In case the reference of your M580 CPU does not end in "40", then your CPU does not have RIO messaging, implying that you can also use network ports (instead of the service port) to communicate to M241 (DIO messaging) . On the M241 side, it will use its Ethernet port. It will require a switch to build a star-type topology in case there's more than one PLC.
From the M241 side, they simply define their IP configuration (IP address, subnet mask and gateway), leave the Modbus TCP server functionality activated (it is active by default on the M241), and then locate in memory locations % MW the variables that want to read / write from the M580.
From the M580 side, after defining their IP configuration, they must add "modbus device" devices in the DTM browser, in order to implement the IO Scanning to the M241. Kindly check the below Video FAQ explaining how to implement the IO scanning of the M580:
You must add a "modbus device" for each M241, and they must add an IO scanning line for each read / write they want to do to the M241. Each line must point to the IP address of a given M241, and to the modbus indices of the% MW of the M241 to be accessed by the M580. For example, if you want to read the% MW100 of an M241, the "RD Address" of the modbus device should be 100 and the "RD length" should be 1.
Note that the M241 TCP server functionality corresponds to Unit ID = 255. In other words, Modbus TCP requests sent by the M580 must be addressed not only to the fixed IP address of each M241 but also to Unit ID = 255 Unit ID is the second column of the IO Scanning table.
Of course, all IP addresses (M580 + 6 M241) must be on the same network segment.
All of the above are in case there was no NOC card.
In case you want the NOC to be the Modbus TCP client instead of the CPU itself, then the steps are identical to what was previously explained, making the difference that the modbus device DTMs (which point to the M241) must be added to NOC instead of CPU in DTM Browser. If you leave the backplane port of the NOC disconnected from the backplane (default), then the Ethernet network of the NOC and the M241 is independent of the ETH network of the M580 CPU.
Released for:Schneider Electric Egypt and North East Africa
