{"id":3783,"date":"2026-11-03T13:00:00","date_gmt":"2026-11-03T05:00:00","guid":{"rendered":"https:\/\/cnbygele.com\/?p=3783"},"modified":"2026-11-02T19:16:37","modified_gmt":"2026-11-02T11:16:37","slug":"meter-counter-reset-audit","status":"publish","type":"post","link":"https:\/\/cnbygele.com\/id\/blog\/meter-counter-reset-audit\/","title":{"rendered":"Pengaturan Ulang Hitungan Meter Energi: Pertahankan Total yang Dapat Diaudit"},"content":{"rendered":"

An energy meter counter reset audit preserves the last trustworthy reading before an authorized reset, the first trustworthy reading afterward and the evidence that connects both segments. Treat the reset as a documented discontinuity. Do not subtract across it as though the cumulative register remained continuous, and do not rewrite earlier raw readings to make a dashboard line appear smooth. A defensible total explains which consumption is measured and which interval remains uncertain.<\/p>\n

This guide concerns reporting continuity and evidence. It does not instruct users to reset a particular instrument. Reset availability, permissions, persistence and commands depend on the exact meter variant and its documentation. Electrical work and operational changes require qualified personnel and approved site procedures. Avoid experimenting with write commands on an operating metering system.<\/p>\n

Distinguish a reset from other counter changes<\/h2>\n

A reset intentionally changes the counter baseline through a supported action. Rollover occurs when a finite representation wraps according to documented behavior. Hardware replacement introduces a different physical instrument. A software mapping change can make a different register appear under the same point name. These events can all produce a sudden drop, but they require different evidence and calculations.<\/p>\n

Start by classifying the event as observed, suspected or confirmed. A drop in a graph is an observation, not proof of a reset. Check configuration history, work orders, device identity, raw readings and relevant logs. If the actual cause is uncertain, preserve that uncertainty instead of choosing the explanation that makes reconciliation easiest.<\/p>\n

The article on energy counter rollover<\/a> addresses automatic numerical wrapping. Do not apply its correction to a reset without documentation. Adding an assumed counter maximum can create a very large artificial energy total when the actual event was a replacement or manual zeroing.<\/p>\n

Define counter scope and units first<\/h2>\n

Record the exact quantity: import active energy, export active energy or another documented counter. Identify whether values are primary scaled quantities, secondary quantities or application-transformed values. Preserve the register-map revision and unit. Two values both called total energy may have different directions or scopes and cannot safely be spliced together.<\/p>\n

The Modbus serial line specification and implementation guide<\/a> describes the serial transaction model, addressing and frame handling. It does not define a universal meter reset register or a universal authorization model. A supported write function at protocol level does not mean a particular reset command exists or that a user is authorized to send it.<\/p>\n

A reset may affect one counter, several counters or an application total, depending on the documented system. Record what was actually reset. If only a reporting database value changed, do not describe the event as a physical meter reset. Keep separate records for device behavior and application transformations so later investigators can trace the discontinuity to its correct layer.<\/p>\n

\n\n\n\n\n\n\n\n\n\n\n
Evidence<\/th>\nBefore event<\/th>\nAfter event<\/th>\nWhy it matters<\/th>\n<\/tr>\n<\/thead>\n
Hardware identity<\/td>\nExact installed instrument<\/td>\nSame or replacement instrument<\/td>\nPrevents joining unrelated devices<\/td>\n<\/tr>\n
Counter definition<\/td>\nRegister, direction, unit and scale<\/td>\nConfirmed equivalent definition<\/td>\nPrevents adding unlike quantities<\/td>\n<\/tr>\n
Valid reading<\/td>\nValue and timestamp with quality<\/td>\nFirst valid value and timestamp<\/td>\nDefines supported counter segments<\/td>\n<\/tr>\n
Authorization<\/td>\nApproved purpose and responsible person<\/td>\nActual action and completion record<\/td>\nDistinguishes planned work from unexplained change<\/td>\n<\/tr>\n
Reporting treatment<\/td>\nExisting cumulative method<\/td>\nNew segment or documented offset<\/td>\nPreserves a reproducible total<\/td>\n<\/tr>\n
Unmeasured interval<\/td>\nLast reliable observation boundary<\/td>\nFirst reliable observation boundary<\/td>\nKeeps unresolved energy visible<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n

This is an audit checklist, not a reset procedure or a claim about any meter’s available features.<\/p>\n

Capture a safe pre-event baseline<\/h2>\n

Before an approved event, save the final valid counter reading as close to the action as practical through existing authorized means. Record whether the timestamp belongs to measurement or collection. Include quality state, source route and any delay between the meter observation and report arrival. A stale cached value is not a reliable event boundary.<\/p>\n

Save the relevant configuration and supporting documents. Where several systems consume the reading, identify their internal point keys and report dependencies. An approved meter reset can still cause downstream alarms, negative deltas or incorrect daily totals if applications assume counters are always monotonic. Coordinate those consequences before the event rather than repairing unexplained numbers later.<\/p>\n

The NIST OT security guidance<\/a> supports controlled changes, access management and retained operational evidence. Apply the site’s actual approval process. The reporting analyst should receive an event record, not credentials or unrestricted access to a device’s configuration interface.<\/p>\n

\"BY194
Product-reference illustration of a disconnected BY194 front beside external energy meter counter resets review records. Surrounding records illustrate an engineering workflow; installed functions depend on exact variant documentation.<\/figcaption><\/figure>\n<\/p>\n

Reconcile segments instead of hiding the discontinuity<\/h2>\n

For a continuous segment with valid endpoints, energy is the later cumulative value minus the earlier value, subject to the documented counter scope and behavior. At a reset boundary, close the old segment and open a new one. Add the supported consumption from each segment only after checking that units, boundary and direction remain compatible.<\/p>\n

Consider an illustrative case. The old segment begins at 1,000 kWh and ends at a verified 1,240 kWh before reset, giving 240 kWh. The new segment begins at a verified 0 kWh and later reaches 85 kWh, giving 85 kWh. Supported segment consumption totals 325 kWh. Any consumption between the last pre-reset observation and actual reset remains unresolved unless additional evidence covers it.<\/p>\n

A reporting offset may present a continuous lifetime-style total, but its definition must remain explicit. Preserve the original device readings and the offset version separately. The display should not imply that the physical register itself has always shown that adjusted value. Recomputing the report from raw segments and approved adjustments should reproduce the same result.<\/p>\n

Handle replacement and uncertain event times<\/h2>\n

A replacement instrument may arrive with a nonzero counter. Its first reading becomes the start of its segment; do not assume zero simply because the hardware is new to the site. Record both old and new device identity, installation position and effective time. The circuit can remain the same even though the hardware and counter baseline change.<\/p>\n

If the old meter’s final reading is unavailable, report the resulting evidence gap. A last recorded sample hours before removal does not establish consumption up to the removal instant. Another meter or operational record may support an estimate, but identify the method and approval. Do not silently allocate the gap to the first interval of the new device.<\/p>\n

If timestamps disagree, retain the discrepancy and determine which clock basis governs the report. A work order completion time may follow the physical action, and application logs may use a different zone. Document the supported interval of uncertainty. Precision in the displayed timestamp cannot substitute for evidence about when the event actually occurred.<\/p>\n

Check downstream reports after the event<\/h2>\n

Inspect the first valid raw readings, decoded values, interval deltas and daily aggregate. Confirm that the application did not create a negative consumption interval, apply an automatic rollover correction or double-count a compensating offset. Review related alarms and completeness indicators so the correction does not merely move the error to another report.<\/p>\n

Reopen an exported report using the approved method and compare it with the segment calculation. Keep an acceptance record showing the raw endpoints, adjustments and remaining uncertainty. If multiple systems calculate energy independently, verify each one or explicitly limit the acceptance scope. A corrected dashboard does not prove that a separate monthly export has been regenerated.<\/p>\n

\"BY194
Product-reference illustration of a disconnected BY194 front beside external energy meter counter resets review records. Surrounding records illustrate an engineering workflow; installed functions depend on exact variant documentation.<\/figcaption><\/figure>\n<\/p>\n

Specify product and integration requirements<\/h2>\n

For a BY194 multifunctional power instrument<\/a>, request the exact variant’s counter definitions, persistence behavior and supported reset controls, if any. Do not infer remote reset capability, event logging or access protection from the family name. An unsupported command should never be guessed from another manufacturer’s register map.<\/p>\n

Use the three-phase meter overview<\/a> to establish the broader measurement requirements before specifying counter continuity. Describe whether the project requires non-resettable accounting, authorized maintenance resets, replacement continuity or externally calculated lifetime totals. Provide the reporting interval and evidence expectations. Review power meter configuration backups<\/a> and import versus export energy<\/a> to keep configuration history and energy direction distinct from the reset audit itself.<\/p>\n

A useful acceptance exercise also checks the next report boundary. If the event occurs near midnight or month-end, verify which reporting period contains each supported segment and adjustment. Save the unadjusted export, the approved calculation and the regenerated result. This prevents a correction that balances the lifetime total while shifting consumption into the wrong day or month.<\/p>\n

Educational background<\/h2>\n

The following lesson explains binary addition and overflow. It helps distinguish finite numerical rollover from an authorized reset, which is a different event and must not receive an assumed rollover correction. It is not a device reset tutorial.<\/p>\n