Examples of using Pmcommdata in English and their translations into Czech
{-}
-
Colloquial
-
Official
PmCommMsg and PmCommData objects comparation.
PmCommData for reading current values from the device.
The address is defined in objects PmCommData and PmCommMsg.
The PmCommData objects can be used for this driver.
Reading such data can be used in both PmCommData and PmCommMsg objects.
People also translate
The PmCommData object can be used only for reading the current state" message.
There can be multiple PmCommData objects in the PmComm object.
Therefore it is recommended to separate variables into multiple PmCommData object.
There can be multiple PmCommData objects in one PmComm object.
PmCommData> Parameters> Special Parameters> Area base addresses.
The system created automatically communication objects PmComm and PmCommData with corresponding settings.
The PmCommData object is used for reading current values of selected variables.
PmModbusMr communication driver: Optimized PmCommData variables assignment into individual communication messages.
In the PmCommData object, the logical addressing is used- the address of the item is the value commonly used by the PLC programmer e.g.
For example the Pm("opcdata/ vars/aaa") method returns the variable aaa data item from the object named commdata that is of the PmCommData type.
An extension of the Var variable of the PmData object for connecting to the PmCommData object communication by the PROMOTIC communication drivers.
The window can be opened by the"Import" button on the" Data" page of the data objects PmData, PmOpcClientData,PmTrend, PmCommData, PmCommMsg.
See: PmCommData- Deatiled object description The object is used to define the data group, that will be read/written via the corresponding communication.
The driver now searches each received message for the desired data that are defined in the PmCommData object or in the ExtComm data extension.
Tha communication data group( PmCommData object) that has this property set to true, requires the ongoing update of all its data from the communication driver.
It allows the identification of for example sending the data,that are not configured in the PmCommData object or in the"Data receive" message.
PmS7 communication driver: Fixed bug:Variables from one PmCommData were sometimes incorrectly distributed among communication messages and then some variables were not transmitted.
The data extensions are created(configuration and source part)in the Var item(variable) of the PmData( PmCommData, PmOpcClientData, PmTrend) object.
Obtains an array of references to all registered ExtComm objects PmCommData of the"/CommData" object with following listig of identifiers of each item into the INFO system.
Then the opposite side starts to send data messages(with"cause of transmission"= 20=inrogen),that will be received into the variables defined in the PmCommData object.
In order to set the ItemId configurator correctly in the variables for the PmCommData object it is necessary to have the information about available objects in the device.
PmABradleyDF1 communication driver: Fixed bug: The communication did not work if there were variables demanding data from different DataFile numbers in in one PmCommData object.
It is used only in special cases- for standard data reading it is better to use the object PmCommData- see The communication description by the PmCommData objects.
PmCommData object: Fixed bug: in the Value recalculation configurator the d constant when converted from older projects was set to(instead of 1)- bug since version Pm8.1.0.
Then each item of this array represents the"data extension ExtComm object" of the variable that is defined either in this PmCommData object or in another PmData object.
