Examples of using Pmcommdata object in English and their translations into Czech
{-}
-
Colloquial
-
Official
This type is currently not functional for PmCommData object.
The PmCommData object can be used only for reading the current state" message.
Therefore it is recommended to separate variables into multiple PmCommData object.
The PmCommData object is used for reading current values of selected variables.
This information can be used for compiling the ItemId in the PmCommData object.
For some drivers the PmCommData object cannot be used based on the principles e.g.
Fixed bug: there was sometimes an error when sending values in the PmCommData object.
Fixed bug: the PmCommData object sometimes incorrectly received the bit values.
Data receive: This message is obsolete andit is better to use the PmCommData object instead.
The variables in the PmCommData object can be of arbitrary number, type and order.
If only some selected values are to be received from the meter,then it is handy to use the PmCommData object.
The PmCommData object named data includes a Parameters page where Special Parameters are defined.
Based on this value, the variables from one PmCommData object are separated into the communication messages.
In the PmCommData object, the data items are configured by specifying the item type Temperature, Volume.
That's why it is advisable to create the PmCommData object after the configuration of the PmComm object. .
The variables in the PmData object can use ExtComm andregister itself directly into the PmCommData object.
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.
Then each item of this array represents the"variable object Var" that is defined in this PmCommData object.
In the PmCommData object, the vars identifer is used in order to enables access to the variables(of the Var type) defined on the Data page.
It is designed only for the PmCommMsg object, in the PmCommData object, the message index is defined after the" Ib" identifier.
Therefore the decision to define the number of variables depends on the application designer that can optimize the variable count in PmCommData object to maximum number possible.
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.
Returns an array of all data extensions(of ExtComm objects) registered into PmCommData object all items of this group.
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.
The driver now searches each received message for the desired data that are defined in the PmCommData object or in the ExtComm data extension.
PmS7 communication driver: if the PmCommData object contained many bit( Boolean) variables, then the communication messages were not composed correctly and some variables were unable to transmit.
It allows the identification of for example sending the data,that are not configured in the PmCommData object or in the"Data receive" message.
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.
An extension of the Var variable of the PmData object for connecting to the PmCommData object communication by the PROMOTIC communication drivers.
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.