Update cookies preferences
Promotic

PmModbusSl - Driver for communication by the Modbus Slave protocol

Before using this driver in the PROMOTIC application it is highly recommended to watch "PROMOTIC video tutorial 4 - Communication drivers".

Basic properties of the driver:
- Usage of this driver requires purchase of the PmModbus licence. When developing the application in the freeware mode PmFree, or with development environment and while testing it in runtime, this component is always functional.
- The communication is done for serial link (COM1, COM2 ...).
For TCP/IP communication (Modbus TCP) use:
- PmCharServer - Driver for communication by user defined ASCII/BIN protocol.
See Preconfigurations in group "Modbus-Slave".
- The PROMOTIC application is always the Slave from this communication point of view (i.e. the other side initiates the data transfer). For Master communication see the PmModbusMr communication driver.
- The driver is incorporated into the PROMOTIC system by means of the PmaComm object.
The driver supports the usage of the PmaCommMsg object. The PmaCommGroup object cannot be used.
For easy integration of this driver into the application it is handy to use: Preconfigurations in group "Modbus"
- The driver supports only the RTU mode for the Slave.


The driver supports the following Modbus data types:
- Bit (1Bit): In the PLC device stored on 1 bit. In the PROMOTIC application it is represented by the Boolean data type.
- Word (2Byte Unsigned Integer): In the PLC device stored on 16 bits (value from 0 to 65535). In the PROMOTIC application it is represented by the Long data type.
- Int (2Byte Signed Integer): In the PLC device stored on 16 bits (value from -32767 to +32767). In the PROMOTIC application it is represented by the Integer data type.


The communication description by means of the PmaCommMsg object

The description of the protocol functions:
Each of eight messages can be started only once. It means that in the PROMOTIC system only eight messages can be defined together. If we need to read different memory fields, then the communication proceeds as follows:
- Master sends a query on the memory.
- The communication fills the "Data-received" tab.
- The onDataReceive event is triggered.
- In the onDataReceive event the designer finds out from the "Data-received" tab which address and the data amount are required from the Master and it fills the "Data-sent" tab by them. If it doesn't have the data available, then it sets the "Validity" item to false (invalid data), otherwise it sets this item to true (valid data) on the "Data-sent" tab.
- The communication finds out if the "Validity" differs from false and it sends the appropriate data to the Master.

Note: If the "Validity" is set to true and the "Data-received" tab isn't filled in the onDataReceive event, then the communication sends always the same data to the Master, regardless of the address that is requested by the Master.
Caution! If the "Validity" item is set to false, then the communication DOESN'T ANSWER the request !

List and description of communication messages:
01 - Read Coil Status (Read Output Bits): This message reads n output states (1-bit values)
02 - Read Input Status (Read Input Bits): This message reads n input states (1-bit values)
03 - Read Holding Registers (Read Output Registers): This message reads n output registers (16-bits values)
04 - Read Input Registers: This message reads n input registers (16-bits values)
05 - Force Single Coil (Write 1 Bit): This message writes into one state (1-bit value)
06 - Preset Single Register (Write 1 Register): This message writes into one register (16-bits value)
15 - Force Multiple Coils (Write n Bits): This message writes into n states (1-bit values)
16 - Preset Multiple Registers (Write n Registers): This message writes into n registers (16-bits values)
PROMOTIC 9.0.31 SCADA system documentation MICROSYS, spol. s r.o.

Send page remarkContact responsible person
© MICROSYS, spol. s r.o.