Examples of using Pmcommmsg object in English and their translations into Czech
{-}
-
Colloquial
-
Official
Preset message types for PmCommMsg object.
The PmCommMsg object must be used for reading the history data.
For usual data transmissions it is more favourable than using the PmCommMsg object.
Detects whether the PmCommMsg object is ready to transfer the message.
PmModbusMr communication driver:Can now send broadcast type messages by PmCommMsg object, i.e.
The PmCommMsg object gets in the transfer data state by the Run method.
Further described headers can be created automatically by the" Data setting" button in the PmCommMsg object.
This PmCommMsg object only waits for the message and then answers.
That's why it is advisable to create the PmCommMsg object after the configuration of the PmComm object. .
The PmCommMsg object named Initialize provides the initialization of the communication.
The" Common meter/Reading of generally configurated data" message in the PmCommMsg object is used for common reading of the data.
Creates the PmCommMsg object that allows to read information from the connected PLC.
When this preconfiguration is used the DA(PLCaddress) variable is created in PmCommMsg object on the Data-received page.
The Run method only causes that the PmCommMsg object is"placed" in the queue of messages that have to be just transferred.
The PmCommMsg object supports the following messages: For creating these messages it is handy to use the preconfiguration.
For regular ASDU variable receiving, it is more advantageous than using the PmCommMsg object set for Slave message of the"Data receive" type.
Creates the PmCommMsg object that allow to test the communication, read the names of all variables from the PLC and set PLC time.
For the continuous receiving SMS messages it is necessary to run the PmCommMsg object with this type(by the Run method) regulary, for example, each 10 seconds.
The PmCommMsg object can find itself in two states- the state when the transfer doesn't proceed and the state when the transfer proceeds i.e.
The reason can be incorrect message configuration orvery commonly the reason is that in this PmCommMsg object the transmission from previous Run method calling still continues.
New message type(in PmCommMsg object) has been created in order to read information about which values can be read from the meter.
In the PmCommData object, the meter address can be defined for each variable, in the PmCommMsg object, the address is defined on the Data-sent page in the"Address" variable.
Creates the PmCommMsg object that allows to read the names of all variables from the PLC and saves this list into"ABradleyVarCfg. txt" file.
If you check the" Create PmCommMsg for reading the variables from the PLC" configurator in this preconfiguration,then the correctly configured PmCommMsg object is created together with a panel that can run the message and read the desired information from the PLC.
It is designed only for the PmCommMsg object, in the PmCommData object, the message index is defined after the" Ib" identifier.
The PmCommMsg object is used only for special auxiliary messages that detect the variable names that can be read from device see further.
The PmCommMsg object is used only for special auxiliary message that detects the variable names that can be read from the PLC see further.
The PmCommMsg object is used only for special auxiliary message that detects the variables that can be read from the device see further.
In the PmCommMsg object, the rcvvars and sndvars identificators are used for accessing the variables(of the Var type) defined on Data-received and Data-sent pages.
In the PmCommMsg object, it is possible to define the communication message,that will be sent into the corresponding device and the PmCommMsg object can also process the reply to such message.