{"id":3655,"date":"2026-10-29T09:00:00","date_gmt":"2026-10-29T01:00:00","guid":{"rendered":"https:\/\/cnbygele.com\/?p=3655"},"modified":"2026-10-28T19:07:08","modified_gmt":"2026-10-28T11:07:08","slug":"meter-config-backup","status":"publish","type":"post","link":"https:\/\/cnbygele.com\/th\/blog\/meter-config-backup\/","title":{"rendered":"\u0e01\u0e32\u0e23\u0e2a\u0e33\u0e23\u0e2d\u0e07\u0e02\u0e49\u0e2d\u0e21\u0e39\u0e25\u0e01\u0e32\u0e23\u0e15\u0e31\u0e49\u0e07\u0e04\u0e48\u0e32\u0e40\u0e04\u0e23\u0e37\u0e48\u0e2d\u0e07\u0e27\u0e31\u0e14\u0e01\u0e33\u0e25\u0e31\u0e07\u0e44\u0e1f\u0e1f\u0e49\u0e32: \u0e01\u0e32\u0e23\u0e15\u0e23\u0e27\u0e08\u0e2a\u0e2d\u0e1a\u0e01\u0e32\u0e23\u0e40\u0e1b\u0e25\u0e35\u0e48\u0e22\u0e19\u0e2d\u0e38\u0e1b\u0e01\u0e23\u0e13\u0e4c\u0e41\u0e25\u0e30\u0e01\u0e32\u0e23\u0e01\u0e39\u0e49\u0e04\u0e37\u0e19"},"content":{"rendered":"

A power meter configuration backup should preserve the exact settings, device identity, supporting manuals and verification records needed to replace or restore the instrument. A file alone is insufficient: the replacement must accept the settings, represent the same measurement circuit and produce verified readings. Where export software is unavailable, a controlled manual record can provide the configuration baseline. Never assume an apparently identical front panel proves compatibility.<\/p>\n

This guide addresses configuration recovery for industrial monitoring. It separates settings from accumulated energy, historical trends and site security credentials. For communication commissioning, start with power meter Modbus setup<\/a>. Any work affecting energized equipment requires the site’s approved isolation and competent personnel; this article is a planning and documentation procedure, not a live replacement instruction.<\/p>\n

Define what the backup must recover<\/h2>\n

A useful recovery objective states which service must return and which evidence will demonstrate success. A maintenance display, an energy reporting system and a process interlock have different consequences when readings are wrong. Identify those consumers before collecting settings. Record who can approve a temporary loss of monitoring, how gaps will be marked and who owns the final release.<\/p>\n

Separate the instrument configuration from the wider system. A meter may contain circuit type, transformer ratios and communication settings. A gateway may contain register addresses, scaling rules and polling schedules. A historian may contain asset names, calculations and reporting boundaries. Restoring only one component can leave the whole measurement chain incorrect even when every device responds normally.<\/p>\n

NIST’s OT Backup Quick Start Guide<\/a> treats backups as part of change management and recovery exercises. Apply that principle here by capturing an approved baseline before a planned change, documenting the change and testing whether the retained records are actually usable. This does not imply that a particular meter offers a built-in backup function.<\/p>\n

Establish the exact instrument identity<\/h2>\n

Record manufacturer, model, complete order code, serial number, hardware revision and firmware version where accessible through approved documentation or menus. Include installed communication and input options. Link the record to the physical asset number and the panel drawing revision. Photograph accessible labels only under the site’s access rules; do not open a live enclosure just to complete a spreadsheet.<\/p>\n

The CNBYG BY194 product page<\/a> describes a family of multifunctional instruments with optional RS485\/MODBUS communication. That family description does not establish that every unit has identical firmware, register definitions or export capabilities. Obtain the exact variant manual and written compatibility confirmation before selecting a replacement or attempting a restore.<\/p>\n

\"Disconnected
Product-reference illustration of the disconnected BY194 front exterior beside configuration baseline and recovery records. Props illustrate the review process and do not establish installed interfaces, snapshot guarantees, backup functions or gateway features.<\/figcaption><\/figure>\n<\/p>\n

Two instruments can share the same appearance while differing in auxiliary supply, input arrangement or fitted communication options. Conversely, different firmware revisions may remain compatible for some settings but require a revised gateway map. Treat compatibility as a documented decision covering hardware, software and measurement function, rather than as a visual judgement made from the product photograph.<\/p>\n

Build a configuration register that can be reviewed<\/h2>\n

The following table is a suggested record structure. It contains documentation categories, not claimed BY194 menu items. Mark fields as unsupported when the exact instrument does not provide them. A blank field should have an owner and explanation; otherwise the next technician cannot distinguish missing evidence from an intentional default.<\/p>\n

\n\n\n\n\n\n\n\n\n\n\n\n
Record group<\/th>\nWhat to retain<\/th>\nWhat must be checked during recovery<\/th>\n<\/tr>\n<\/thead>\n
Device identity<\/td>\nOrder code, serial, firmware and manual revision<\/td>\nReplacement matches approved compatibility scope<\/td>\n<\/tr>\n
Measurement circuit<\/td>\nCircuit arrangement and documented input configuration<\/td>\nSettings correspond to the approved drawing<\/td>\n<\/tr>\n
Transformer scaling<\/td>\nCT and VT primary\/secondary settings with units<\/td>\nReference measurements use the same scaling boundary<\/td>\n<\/tr>\n
Communications<\/td>\nAddress, interface settings and network path<\/td>\nClient reaches the intended asset without address conflict<\/td>\n<\/tr>\n
Interpretation<\/td>\nRegister-map revision, units, data types and scaling<\/td>\nDisplayed and logged values agree with the approved map<\/td>\n<\/tr>\n
Reporting<\/td>\nAsset name, interval, time basis and counter handling<\/td>\nRecords continue under the correct asset and time boundary<\/td>\n<\/tr>\n
Recovery controls<\/td>\nBackup location, access owner and acceptance record<\/td>\nApproved copy is readable and rollback is available<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n

Write units explicitly. A ratio recorded as a single number may be ambiguous when the original system stored primary and secondary quantities separately. State whether the gateway receives primary-scaled values or applies additional multiplication. The separate voltage transformer ratio guide<\/a> explains why that boundary matters to a measurement comparison.<\/p>\n

Capture the baseline without silently changing settings<\/h2>\n

Use a read-only collection method whenever the documented interface supports it. Record the collection tool and version, operator, time and asset identity. If the tool has both read and write controls, review the procedure in advance and prevent an accidental broad restore operation. A configuration inventory should not become an unplanned production change.<\/p>\n

When manual transcription is necessary, capture each relevant screen or documented value and have a second person compare the record with the source. Group related settings so that a reviewer can follow the circuit and communication path. Retain the original evidence alongside the normalized register; a cleaned spreadsheet is easier to read but can hide a transcription mistake.<\/p>\n

If an export facility exists, save the unmodified export plus the tool version and applicable manual. Do not rename an unfamiliar proprietary file to a common format or edit its contents to force compatibility. A successful download proves only that a file was obtained. It does not prove that another device can safely interpret it.<\/p>\n

Keep settings separate from energy history<\/h2>\n

Configuration restoration is not the same as transferring cumulative energy. Some devices protect totals, some expose separate registers and some require special commissioning procedures. Follow the exact manual. Never write a counter merely to make a dashboard look continuous. Preserve the outgoing final reading and incoming initial reading as distinct records with a documented handover time.<\/p>\n

The historian should identify the replacement event so that reports can distinguish a device change from actual negative consumption, rollover or a gap. Record whether the old counter was read before isolation and whether any interval remained unmeasured. The energy counter rollover guide<\/a> covers a different cause of discontinuity; do not misclassify replacement as rollover simply because the total decreased.<\/p>\n

A practical handover package contains the final accepted configuration, final trustworthy readings, asset identity, change time and rules for reporting incomplete intervals. If contractual billing is involved, obtain the responsible party’s approval of the handover and applicable metering requirements. An engineering backup record does not establish revenue-meter approval or authorize a billing adjustment.<\/p>\n

Protect the backup from the incident it must survive<\/h2>\n

Keep an approved recovery copy outside the single workstation or storage location used for daily configuration work. Choose access and retention controls according to the site’s recovery plan. A copy continuously writable by the same compromised account may be damaged alongside the working files. Avoid putting passwords or sensitive network details into unrestricted maintenance reports.<\/p>\n

NIST SP 800-82 Revision 3<\/a> provides broader OT security and recovery guidance. Use it to coordinate configuration control with plant operations. Meter recovery can depend on gateway configurations, software installers and licenses, so identify those dependencies rather than retaining a lone device file and assuming the rest will remain available.<\/p>\n

The appropriate retention period depends on the change cycle, support arrangements and recovery obligations. Keep enough history to locate a known-good baseline before a fault or unauthorized change. Record why each retained version exists. Repeated copies with unclear dates and no approval trail can make recovery slower because operators cannot confidently choose the right one.<\/p>\n

Rehearse recovery before an urgent failure<\/h2>\n

Where practical, test on a suitable spare or approved isolated environment. Confirm the documented restoration method, required access and time needed to complete it. Verify that recovery materials can be retrieved by the people who will actually be on duty. A successful test performed only by the original author on a personal laptop leaves an avoidable operational dependency.<\/p>\n

Compare recovered settings field by field against the baseline. Then verify communications and measurement interpretation separately. Check a documented reference quantity, units and scaling. Confirm that the historian associates readings with the right asset. Communication success alone cannot expose an incorrect transformer ratio or duplicate asset mapping.<\/p>\n

\"Disconnected
Product-reference illustration of the disconnected BY194 front exterior beside configuration baseline and recovery records. Props illustrate the review process and do not establish installed interfaces, snapshot guarantees, backup functions or gateway features.<\/figcaption><\/figure>\n<\/p>\n

Set acceptance conditions before testing. Record the expected result, actual evidence, reviewer and unresolved discrepancy for each critical field. Do not use an invented universal error tolerance: measurement acceptance depends on the instrument specification, test arrangement and application. If a setting cannot be verified, preserve that uncertainty and obtain technical clarification before releasing the restored service.<\/p>\n

Release, rollback and continuing maintenance<\/h2>\n

A recovery plan needs a rollback decision as well as a restore procedure. Define which observations stop the release, who can authorize further investigation and how reporting will mark data from the test period. If a replacement cannot reproduce an essential function, returning the old instrument may require another approved shutdown; plan that possibility before the work begins.<\/p>\n

After acceptance, make the verified configuration the new controlled baseline and archive the superseded version. Update drawings, asset records, gateway mapping references and support contacts. Schedule a review after future firmware, transformer or reporting changes. The value of a backup comes from its continued agreement with the operating installation, not the date on which someone first created a file.<\/p>\n

Further learning: why isolated recovery copies matter<\/h2>\n

The Computerphile lesson below explains ransomware file encryption. It provides background for protecting recovery materials from a shared compromise; it does not demonstrate meter restoration or specify a backup architecture. The recovery checks in this article remain necessary even when a copy survives an incident.<\/p>\n