Use click plc as a modbus server how to#

The discrete output point used by the display (Counter) is read from %MW0. On this sample, digital input I/O points (sensors) are written to %M0 up to %M16, and digital outputs (actuators) are read from %M17 up to %M29. We are setting an Offset of 17 to Outputs in order to have the first 17 addresses available for Coils (sensors).Īlso, in Schneider Unity pro, both Discrete Inputs and Holding Registers are stored in internal Word memories (%MW). In Schneider Unity Pro, both Coils and Inputs are stored in internal Boolean memories (%M) and share the same memory space. Read operations can be performed on Coils or Inputs according to settings chosen in the CONFIGURATION panel. Modbus TCP/IP clients can only write to Coils. Note that I/O points are already setup with 17 digital inputs (sensors), 13 digital outputs (actuators) and 1 input register (number shown by the display: Counter). Start Factory I/O and open the Sorting by Height (Advanced) scene. Setting up Factory I/O ¶ĭownload the zip archive (top of this page), extract it and open the project in Schneider Unity Pro.

We will be using Unity Pro simulation mode, which simulates an M340 PLC with a Modbus server.įactory I/O will be running as a Modbus TCP/IP client.

Use click plc as a modbus server how to#

This tutorial gives you step-by-step instructions on how to use Schneider Unity Pro SoftPLC to control Factory I/O through Modbus TCP/IP. Schneider Unity Pro Soft PLC through Modbus.zip