How is the maintenance of datalogger devices performed?

Maintain the measurement chain, not just the enclosure

Data logger maintenance protects measurement quality, reliable timestamps and the integrity of stored records. Wiping the case is only one part of it. Check the logger, sensors, supply, connections and recording configuration as a system. Set the schedule around manufacturer guidance, site conditions and the importance of the measurements.

1. Secure the existing records before servicing

Export the latest data and open the file. Check its final timestamp and channel labels. Back up the program, scaling, alarm limits and communication settings. Establish the device's full-memory behavior: it may stop recording or overwrite old records. During data review, note any unexplained gaps before changing anything. A factory reset should not be the first troubleshooting step.

If servicing interrupts measurement, document the start time, end time and resulting gap. Arrange another logger or an alternative recording method where continuous monitoring is required. The application determines how much interruption is acceptable.

2. Inspect the housing, cables and connections

Look for cracks, loose connections, corrosion and moisture around the case, display, connectors, cable glands and seals. Avoid pulling cables or tightening terminals indiscriminately; follow the specified connection and tightening procedure. Enclosure protection depends on intact seals and correct closure. Where opening the housing is necessary, follow the manufacturer's power-isolation and service instructions.

Use only an approved cleaning method and materials. Do not spray liquid directly into the unit. General-purpose solvent is not an appropriate default for sensing elements, filters or ports. Different sensors need different treatment: a humidity-probe filter is not maintained like a pressure port. More aggressive cleaning will not fix an electrical or configuration fault.

3. Identify what each battery actually supplies

The main battery or power supply runs the device. An internal backup battery may support its clock or particular memory areas. The CR350 manual describes clock backup; the CR1000X manual describes clock and SRAM backup. Do not assume all recorded data survives every battery replacement. Check the model's power arrangement and replacement procedure, and export records first.

Inspect supply status, battery warnings, connections and any charging system. Software may report the internal cell and main supply in different fields. Use the specified battery type, chemistry and polarity; do not recharge a non-rechargeable cell. Wireless activity, acquisition frequency and externally powered sensors affect consumption. Follow service requirements for sealed or restricted battery compartments.

4. Verify time and continuity independently

Compare the logger clock with a reliable reference. Check the time zone, clock drift and date after a power interruption. Incorrect timing can mislead an investigation even when the measured values are correct. A live reading does not establish that the historical record is complete. For remote systems, check local recording during a network failure and delivery after reconnection.

Look for timestamp jumps, duplicate entries, missing channels and incorrect units in the exported file. Non-volatile storage does not guarantee preservation of the newest data in every interruption scenario. Conduct any power-loss test under planned maintenance conditions, after backing up records and arranging for the measurement gap.

5. Distinguish calibration, adjustment and fault isolation

Calibration establishes how the measurement relates to a reference, including relevant uncertainty. Adjustment changes the instrument's response. They are different operations. An accuracy check needs a suitable reference, relevant test range and defined acceptance criteria. Agreement at a single point does not demonstrate performance across the entire range.

Check the sensing chain using appropriate methods. With a Pt100, inspect the wire arrangement and connection resistance. With a thermocouple, verify the type, cable and cold-junction compensation. A suitable calibrator can test a 4–20 mA input, but that alone does not validate the transmitter's physical measurement. Separating sensor and logger checks helps locate the source of an error.

There is no single calibration interval for every logger. Consider manufacturer recommendations, previous drift, operating conditions and application requirements. Retain results before and after adjustment or replacement. An out-of-tolerance result should trigger an assessment of which earlier records may have been affected.

6. Verify configuration and alarms after maintenance

Review channel names, scaling, recording intervals and alarm rules in the configuration. Treat a firmware change as a controlled modification: establish its purpose, compatibility, backup and recovery options. In a Modbus system, an address or register change can cause incorrect values to be retrieved even while the logger itself is measuring normally.

Finish with a short recording test using a known input, a suitable alarm test and an exported file. Where SCADA or notification services are involved, check that the alarm reaches its destination. The service record should identify the serial number, date, work performed, reference used, battery changes and next planned check.

Technical references: Campbell Scientific — Calibration · CR350 — Internal battery · CR1000X — Internal battery