Monnit Dual Pulse Report Times: Check UTC Synchronisation Before Closing a Local Shift
Two pulse counters can use the same Heartbeat interval yet report at different positions within the hour. Before changing a pulse factor or forcing more frequent transmissions, check whether the report sequence follows the previous report or a UTC-aligned schedule. For an ALTA Dual Pulse Counter, Monnit documents a Synchronize setting that changes this behaviour.

The practical answer is to define the reporting boundary first, then verify the installed setting and actual observations. Synchronisation can help align routine reports, but it does not by itself prove a local shift total, simultaneous delivery or an exact consumption boundary. This guide concerns the dual-input model; confirm the supplied hardware and available settings rather than copying them to another counter.
Know what Synchronize changes
Monnit’s configuration guide describes Synchronize Off as placing the next report one Heartbeat after the last report. With Synchronize On, the next report aligns to UTC time instead. Its example uses a 60-minute Heartbeat and a report at 13:47: subsequent reports are 14:47 and 15:47 with synchronisation off, or 14:00 and 15:00 with it on. The guide also states that Aware State transitions can still generate threshold-triggered reports, followed by the next aligned interval.
That distinction explains a schedule pattern, not every late message. If the sensor’s observation time follows the expected schedule but the platform receives it later, investigate delivery separately. Preserve both timestamps when the system exposes them. Do not relabel reception time as measurement time simply to make a chart look aligned.

Translate the reporting requirement into a time reference
Write down the intended local boundary, site timezone and reporting period. “Hourly” is incomplete: the team may mean a UTC hour, a local clock hour or an hour since a process started. These are different requirements. Keep the stored timestamp and its timezone or UTC offset available in exported evidence.
For an Australian site, use the applicable named timezone when interpreting dates. Adelaide has a half-hour offset from UTC, so an hourly sequence on UTC hour marks is not automatically a sequence on Adelaide hour marks. Daylight saving also changes the UTC offset seasonally. Do not apply one fixed offset to the whole year or assume the portal display setting changes the sensor’s documented UTC alignment.
A hypothetical shift-boundary mismatch
Suppose a site closes a report at 08:00 local time, but the available observations fall at 07:30 and 08:30. Labelling the later observation “08:00” does not make its count an exact shift-closing reading. If the count is cumulative, a difference between two valid observations covers their actual observation interval. It cannot establish how many intervening pulses occurred before 08:00 without additional evidence.
The reporting owner could accept the available interval, arrange a supported acquisition method that meets the required boundary, or explicitly approve an estimated allocation with its assumptions. Record which approach is used. Never silently present interpolation as an observed counter value, especially where quantities influence reconciliation or commercial decisions. These times illustrate the reporting problem; they are not a promised schedule for a particular configuration.

Verify on one test device before changing a fleet
First preserve the counter identity, firmware, Heartbeat, Synchronize setting, accumulation mode and relevant event thresholds. Record the two input assignments independently so a correctly timed report is not attributed to the wrong meter. Keep passwords, device security codes and account tokens out of the support record.
Next, use a spare device or an authorised maintenance window. Confirm that the intended configuration has reached the device, then observe several routine reports. Compare the expected sequence with the available device and platform timestamps. Include a permitted threshold-event test if that behaviour matters; do not assume every message belongs to an equal-duration routine interval.
Finally, check the receiving calculation and export. Distinguish interval counts from accumulated values, identify gaps and retain unexpected event reports. Have the integrator demonstrate which observations enter each reporting period. A neat display alone is insufficient acceptance evidence.
Allow for shared-gateway traffic
Monnit warns that excessive synchronised reporting increases congestion and recommends no more than ten synchronised devices per gateway. Treat this as a planning constraint, not a guarantee that ten devices will meet every application’s timing requirement. Review the actual network and reporting needs before enabling synchronisation across a site.
Avoid shortening Heartbeats or disabling event reporting merely to hide a boundary mismatch. Resolve timing, counting mode and communications as separate questions. This monitoring configuration does not establish a certified safety or revenue-metering function.
Prepare the next action
Send ProSense the exact dual-counter model, required local reporting boundary, current settings and a sanitised sequence of observed timestamps. Include the number of devices sharing the gateway and the required tolerance at the boundary. That gives the integration team a concrete requirement to verify before a fleet change.
Need help with your application?
ProSense Instruments - explore instruments, sensors, data loggers and test equipment.
ProSense Solutions - discuss complete monitoring and automation systems.
ProSight Software - explore cloud dashboards, alarms and reporting. Device integration must be confirmed for your application.
Instrument enquiries: sales@prosenseinstruments.com.au | 1800 560 854
Project enquiries: sales@prosense.com.au. Software enquiries: info@prosightsoftware.com.



Comments