Following types of communication transfers are supported:
Caution: This type of communication is too slow for data acquisition (all configured items in the device are received in text form). Sometimes the ammount of data is very large and the transmission may therefore last for several minutes! This is the main reason why this is not suitable regular, fast (e.g. every second) reading of requested data.
Programming mode allows both data reading and writing. Although it is necessary to enter password for data writing. The password is not needed for reading the data.
The serial link is commonly used in these meters as standard interface.
Communication via Ethernet can be implemented in two ways:
Caution: The usage of this communication via Ethernet is technicaly limited. It is not possible to dynamicaly modify the commnication speed, which is required by the standard (see below)! And therefore such solution is suitable only for configurations not using dynamic communication speed modifications.
For example the CU-E22 module for Landis-Gyr meters (E650 or E850) supports the Ethernet protocol IEC62056 on port 12212 (maybe also on port 4059?).
For easy integration of this driver into the application it is handy to use: Preconfigurations in group "IEC62056 communication protocol"
For communication with energy meters mased on the IEC62056-21 standard, the following physical interfaces can be used:
There are two types of optical heads: for connection to the PC serial port (RS232), or for USB.
In order to let the PROMOTIC system communicate with head connected to USB, the host computer must be equiped with a driver that emulates a virtual COM on the USB bus. Majority of the optical heads use circuits manufactured by the FTDI (Future Technology Devices International) company. The OS Windows since version 7 (if connected to the internet) is able to install the corresponding driver without user interaction. If the older OS Windows version is used, it is necessary to download the driver manually from http://www.ftdichip.com/Drivers/VCP.htm.
Sometimes problems may occure while using the optical heads. Some heads return the sent data as received data - in such case it is necessary to set the "Filter ECHO chars" configurator. Before the specific head is used the device-head compatibility must be tested. The declaration od standard comliance is insufficient. Also carefully observe the head orientation (rotation angle). Some heads are functional only in specific angle.
|Baud rate||300 Bd (based on standard). |
During the communication with the device via the computer's serial port 2 different communication speeds may be used. The first (typically 300Bd) is used for estabilishing the connection and for basic information exchange between the device and the driver. Then the devicec "proposes" a new communication speed and the driver conforms to the new speed.
Despite the fact that the standard defines the first speed as 300 Bd, some devices may be configured in order to use another basic speed. For example some Landis+Gyr electricity meters equipped with the Dialog CU-Bx communication unit can be configured in order to use the same speed for the whole communication - this way it is possible to communicate for example via modems and internet tunnels.
|Number of data bits||7 (based on standard).|
|Parity||EVEN (based on standard).|
|Number of stop bits||1 (based on standard).|
|Timeout between receiving 2 chars||100 ms (or more). |
However this number must not be too high. For example for LandisGir meters it must not be higher than 1200 ms.
|Response receipt timeout||20000 ms. Only for serial link. |
The time (in milliseconds) the driver is waiting for the response on sending the message. If no response comes during this time, then the transfer of the message is terminated (the onEndOfTransfer event is triggered with error 24 or 66).
The data exchange via the IEC62056-21 protocol can be quite time-consuming (up to tens of seconds)! Therefore when using the higest communication speed of 9600Bd we recommend to set this timeout to 20000ms. When using the 1200Bd speed, we recommend to set 40000ms.
|Number of Packet Leading Wake-up Zeroes||10. |
It may be necessary to wake up some devices before the communication is estabilished. For this purpose, here you can set how many zero characters are to be sent by the driver before the main communication starts.
|BaudRate Limit||19200. Only for serial link. |
If the connection with the device is done via a physical data interface with limited bandwidth (e.g. Optical head), then this limitation can be defined in this setting. In such case the driver does not comply with the proposed communication speed, but lowers it to the value defined here.
This data type asks the device for data and the device sends a single (often very long) data package in text form. This data ure unprocessed and saved in the "ResultString" variable. The application designer then has to disassemble the text in order to extract the desired values.
In order to create this message type it is recommended to use the "Preconfiguration "PmIEC62056 - Communication set with data and panel"". This preconfiguration also creates the script for disassembling the received text.
Caution: The received text can be very long (even several hundred rows) and if the device supports only slow transmission speeds (300Bd, 600Bd, 1200Bd), then the transmission of a single message may take several minutes! It is sometimes possible to configure the device in order to communicate only the necessary data and optimize the communication.
This communication type is functional only with devices supporting the C mode (but it may not be supported by all such devices).
In theory it is also possibe to write data in this programming mode, but it is mostly used by the PROMOTIC system for reading individual values. The password is not required for data reading, or the password is published (e.g. password is 0000).
The exact syntax of commands (i.e. values to be used in variables Param and Data) may differ for each device type and must be consulted with the documentation (manual) of such device.
This parameter must be entered only if the message is supposed to switch the device into programming mode (i.e. if seq:1; or seq:3;) and if the device requires password (even if the password is e.g. () or (0000)).