Object PmComm (Communication)

The object enables the communication with other computers (mostly with control computers of PLC type) via Ethernet or via the computer's serial port (COM1, COM2,...).
One or more objects PmCommMsg or PmCommData can be created in the PmComm object. This object can be created in the PmRoot, PmFolder and PmPrototype objects. Multiple objects of this type can be created in such objects.

The PmComm object is bound on the purchase of the license for the appropriate communication driver - see List of communication drivers.

The 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.

The PmComm object defines what port and protocol will be used for the data transfer. Data required for the transfer are then defined in the PmCommMsg or PmCommData nested objects.
PmCommMsg and PmCommData objects comparation:
- The PmCommMsg object:
- 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.
- can be used for all drivers except for the PmS7 driver.
- The PmCommData object:
- 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, PmS7, PmSBUS, PmMBus, PmIEC8705, PmMelsecQA, PmMelsecFXS, PmABradleyDF1, PmFatek and PmTeco. 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 object).
This object adopts properties and methods of object PmObject
Properties and methods:
BaudRate The baud rate of the serial link
ByteSize The number of data bits of the serial link
ClosePort Close the serial/ethernet port
Dtr Value of DTR signal of the serial link
GetCount Number of transmissions
GetProtParam Detects some values of the Protocol parameters configurator
IsConnected Detect whether the Ethernet or serial link is connected
OpenPort Open the serial/ethernet port
Parity Value of the transfer parity of the serial link
Rts Value of RTS signal of the serial link
SetProtParam Sets some values of the Protocol parameters configurator
StopBits The number of stopbits of the serial link
onConnect Fires after the successful connection
onDisconnect Fires after the connection is closed
Configuration windows:
Object General information about the object
Content Content of the object in the XML form
Events Definition of object events algorithms
Parameters Communication protocol and parameter setting
© MICROSYS, spol. s r. o.Tavičská 845/21 703 00 Ostrava-Vítkovice