Definition
CJ/T 188 Standard communication protocol for urban gas meters and water meters, used for data exchange between smart water meters, gas meters, and meter reading systems, supporting consumption, tiered pricing, and other data.
Protocol Specification
CJ/T 188-2004 "Technical Conditions for Data Transmission of Household Measurement Instruments" specifies the physical layer (such as M-Bus, RS-485) and data format for water meters and gas meters. Data items include cumulative consumption, instantaneous flow, meter address, valve status, battery level, etc. It adopts a master-slave architecture, with the concentrator or meter reading terminal as the master station and the meters as the slave stations, supporting both unicast and broadcast. The extended version adds more data items and security mechanisms, adapting to IoT remote meter reading scenarios.
Integration with AMI
In the AMI smart metering system, CJ/T 188 meters are directly networked via NB-IoT or LTE Cat.1 modules, or uploaded after aggregation via a concentrator. The module encapsulates CJ/T 188 protocol data into TCP/MQTT formats, communicating with the meter reading platform. It supports scheduled meter reading, event reporting (such as abnormal consumption, low battery), remote valve control, etc., achieving unattended operation and refined management.
Comparison with DL/T 645
DL/T 645 is for electricity meters, while CJ/T 188 targets water and gas meters; both are national standard meter reading protocols with similar structures but different data items. In multi-meter integration scenarios, the same concentrator or gateway may support both DL/T 645 and CJ/T 188 simultaneously, collecting data via separate serial ports or protocol stacks and uploading it to the AMI platform through a unified channel.
Engineering Practice Supplement
Regarding the implementation of "CJ/T 188" in IoT and cellular module projects, it is recommended to document network constraints (target market frequency bands and decommissioning plans, APN and private network strategies, roaming and tariffs, PSM/eDRX and other power-saving modes) and terminal constraints (antenna and RF layout, power ripple and surge, thermal design and derating, EMC/safety regulations) as verifiable acceptance items during the project initiation stage. During the R&D phase, use weak network simulation, high and low temperature, and voltage drift tests to reproduce boundary faults, retaining logs and waveforms; in mass production, establish batch and calibration traceability, and handle component replacements through change reviews. After launch, include connection success rate, reconnection count, latency, and power consumption in the operational dashboard, so anomalies can be traced back to versions and batches.
What happens when polling lands in the meter’s sleep
CJ/T 188 is the frame agreement by which a master exchanges usage, instantaneous flow, valve state, battery, and meter address with a water or gas meter. It governs the question and answer on the meter bus or local interface, not the cellular air interface itself. The conditions are that the protocol stack in the master or the module builds frames for that meter’s version, that the address matches the nameplate, and that the inquiry lands while the meter is awake. To save power the meter turns its receiver off for long periods. If the master polls continuously at an electricity-meter pace, most frames fall into sleep and the platform only sees timeouts.
A directly connected module must collect a complete local frame before wrapping it for upload. It must not treat a half frame as a usage record. Concentrator mode finishes the question and answer on the bus first, then sends the result over cellular. If both modes are mixed in one record, the platform uses the wrong wait time. If an extended data item is beyond the version the other side understands, ignore the unknown item rather than dropping the whole frame.
When the valve status word does not match the actual opening
The status word is the valve position the meter last confirmed, not the real flow under the current water pressure. If the command was sent and the reply was lost, the platform shows “valve closed” while the valve in the field is still open. Confirm with a later status read. Do not treat a successful send as a successful action. At low battery the meter may refuse to move. Report that refusal as its own event, not as a communication failure.
A wrong address copies in a neighbor’s usage, and the curve is still smooth. After a meter is replaced, retire the old address on the platform. If downlink valve control depends on a long sleep, let the meter ask during an agreed window. Do not assume the network can wake it at any time. Cycle choice is in eDRX. Do not put electricity-meter data identifiers into these frames.
Uploading a half frame splits the cumulative reading
A frame on the serial port can be cut in the middle by a transparent buffer. If the platform then slices by a fixed length, cumulative usage jumps and the valve status occasionally shows an illegal value. Assemble the frame in the module or gateway by start character and checksum. Drop a frame that fails the check and count it. Do not upload it and let the platform guess. The assembly timeout must be shorter than the gap before the next frame, or replies from two meters stick together. Report the stuck-frame count with the read success rate. Otherwise the field only sees an occasional absurd reading.