Implementation methods and differences between channel following reporting and active reporting in the object-oriented protocol electric energy meter module

The follow-up reporting of the electric energy meter can be implemented on all communication channels of the electric energy meter, such as 485 or Bluetooth channels. The follow-up reporting mainly follows a reporting content (33200201 and 20150200) at the end of the message when passively calling for data. But in the carrier channel, the active reporting function similar to the original 645 protocol can be achieved by cooperating with the module. This article mainly elaborates on the implementation methods of channel following reporting and active reporting in the communication (carrier) module. 1. The channel of the electric energy meter module follows the reporting process. The electric energy meter pulls the EVENT pin, and the module reads 33200201 (newly added event list OAD) and 20150200 (following the reporting status word OAD) to report to the terminal. After receiving them, the terminal reads the corresponding event related object content of the electric energy meter and then reports to the main station. Implementation steps: 1) Trigger: After the energy meter generates an event, actively pull the EVENT OUT hardware pin to high resistance (physical level change). 2). Perception: The module perceives pin actions and reads event identifiers (33200201, 20150200) from the energy meter. 3). Report: The module transmits data to the terminal. 4). Processing: The terminal reads the event content of the electric energy meter or reports it along with 20150200, and then reports it to the main station.

2. The active reporting process of the energy meter module channel involves the active reporting of the energy meter (reporting request service 88 01) 33200200 and 20150200, module forwarding, and the terminal responding to the active reporting message (reporting response service 08 01), reading the corresponding event related object content of the energy meter, and then reporting to the main station. Implementation steps: 1) Initiate: The energy meter detects an event and sends an active reporting request message (88 01) through the module serial port. 2). Forwarding: After receiving the reporting request, the module directly forwards it to the terminal. 3). Response: The terminal responds with a report confirmation (08 01). 4). Reading: The terminal reads the specific event content from the energy meter based on the reported content (such as event records corresponding to 33200200 and 20150200). 5). Reporting: The terminal packages and reports the data to the main station. Proactively report security and provide additional content explanations:

1) The 698 protocol requires that power outages be actively reported in fixed plaintext to record power outage events (after a power outage, ESAM does not work, so fixed plaintext is used); 2). After power on, ESAM can work normally and report 33200200 and 20150200 using plaintext+RN+MAC security method (can report both 33200200 and 20150200 at the same time, or report one of them). The terminal uses plaintext+MAC response, and the energy meter determines the correctness of the MAC in the response message for processing. 3. Report relevant important parameters 1) Reporting channel selection: 43000A00: Specify the physical channel for reporting, including carrier (F2090201), RS485 (F2010201, F2010202, F2010203), Bluetooth (F20B0201), IoT table extension module channel (F20D0201, F20D0202, F20D0203). Total allowable switch: 43000800: Enable active reporting. 43000700: Enable follow-up reporting. 3). Reporting method: Normal 7 types of event attribute 8 Reporting identifier: (0) Do not report (1) Report event occurrence (2) Report event recovery (3) Report event recovery. Attribute 11 reporting method: (0) active reporting (1) follow-up reporting. Common 24 types of event attribute 11 reporting identifier: (0) Do not report (1) Report event occurrence (2) Report event recovery (3) Report both event occurrence and recovery. Attribute 15 reporting method: (0) active reporting (1) follow-up reporting.

Proactively reporting, due to the limitation of carrier communication capability, currently only 33200200 (newly added event OAD list) and 20150200 are reported after the energy meter is powered on, in order to reduce the time occupied by uplink bandwidth. It is said that the latest State Grid has planned to configure all events to be reported as record content (long messages) or event list OAD. In addition, it should be noted that the majority of power outage reporting still relies on the original communication module power outage reporting method, and generally does not use the active reporting method of power outage records through energy meters.