Powered By E-MOTION
Request for Quantity & Price
CODESYS Modbus Serial Master SL Article no. 2303000014
The CODESYS Modbus Master (RTU) configurator, which is integrated in the CODESYS Development System, expects a license on the device. This license is either already stored in the controller by the device manufacturer* or added afterwards by the end user**. The product is also available for Modbus TCP. Processing requires a protocol stack and CODESYS I/O driver that implements Modbus communication on the configured COM port. This I/O driver is supplied with the license as CODESYS libraries. If a license for the CODESYS Modbus Master (RTU) configurator is available on the device to be programmed, then the device can communicate with connected adapters and read and write their inputs and outputs, respectively. For this purpose, the communication parameters are predefined in the configurator, for example the settings of the serial ports (baud rate, port number). Modbus commands are defined in the configurator and are oriented to a specific Modbus slave. The commands are processed by the device at specific intervals, or triggered programmatically. For predefined commands, I/O channels are generated automatically with variables that can be mapped (I/O mapping).
This license is already included in SoftPLC systems from 3S-Smart Software Solutions (example: CODESYS Control Win or CODESYS Control for Raspberry Pi).
** License saved on the CODESYS compatible device – on CODESYS Runtime Key (hardware device) or CODESYS Soft Key (software license container).
CODESYS Modbus Serial Master SL Article no. 2303000014Modbus Configurator
The CODESYS Modbus Master (RTU) configurator consists of editors for the following COM port device categories that are inserted into the device tree hierarchy: * Modbus: The COM port settings are configured here, such as baud rate and parity. * Modbus master: A Modbus master can be inserted below the COM port. Communication settings can be defined specifically for Modbus RTU, for example “Response Timeout” for defining the time to wait for a response from a Modbus slave. * Modbus slave: Multiple Modbus slave devices can be inserted below a Modbus master. The slave address is defined here, as well as a series of Modbus commands (incl. respective I/O mapping). These are processed by the driver and exchanged with the Modbus slave.
Device description files
Modbus slaves are defined in the CODESYS format “devdesc.xml” because there is generally not native description format, such as GSD or GSDML, for Modbus devices. For example, description texts can be predefined for Modbus registers that are then evaluated by the configurator. Moreover, Modbus commands can be defined that are created automatically when devices are inserted into the project.