PmComm - Deatiled object description
See: Object PmComm
object can be used in the application more times, it can be even configured more times with the same protocol (driver).
For serial link each PmComm object must have defined another communication port. For example, when one PmComm object communicates through COM1, then next PmComm object can communicate for example through COM2 (COM3,..) but it mustn't communicate through COM1.
object defines what port and protocol will be used for the data transfer. Data required for the transfer are then defined in the PmCommMsg
PmCommMsg and PmCommData objects comparation:
- The PmCommMsg
- is a "low level" object, meaning that the data format in this object is created depending on the communication message type, defined by corresponding protocol. If you want to receive, for example, both registers and counters, then two PmCommMsg
objects must be created, because the current protocol does not support receiving both registers and counters in one message.
- The PmCommData
- compared to the PmCommMsg
object, it is on a higher level, because the data in this object are not depending on used protocol. It is possible, for example, to define data for both counters and registers and the object will intelligently assemble this data into communication messages.
- so far this object can be used for following drivers: PmModbusMr
. For some drivers the PmCommData
object cannot be used based on the principles (e.g. for the PmChar
driver, because this user defined protocol does not have any general addressing and depends only on the user, what kind of message will be created by the PmCommMsg