A breaker comes into the workshop with two sets of hours attached to it. The carrier's counter says one thing, the SolidTrack figure says another, and the two are not close. The usual first reaction is that something must be broken: a sensor, a setting, the software, or whoever set the software up. It is worth pausing there, because a difference does not necessarily mean anything is broken. The two figures are designed to measure different things, and once you know which is which, the gap between them stops being a fault to reconcile and starts being one of the more useful things you know about that machine.
Most hour meters count availability. On a carrier, the counter typically runs whenever the engine runs, which means it accumulates while the machine idles at the face waiting for a truck, while it warms through on a cold morning, while it sits at the weighbridge, and while it ticks over through a break because switching off and starting again is a nuisance. None of that is a criticism of the meter. It was built to tell you how long the engine has been turning, it does that honestly, and for engine oil and filters it is exactly the right number. It simply never claimed to tell you how much work got done, and it has been quietly asked to answer that question for decades because it was the only number available.
Attachments often have the same problem in a worse form, because many of them have no counter at all. Many breakers, grapples, compactors and shears have no engine or dash of their own, so the hours written against them are often the carrier's hours, or a figure someone reconstructed at the end of the month from what they remembered. If the hammer was on the machine for three hours of an eight-hour shift and the paperwork logs eight, the service interval may be consumed on paper faster than the attachment's recorded activity suggests, and the workshop may bring in a tool earlier than the motion-derived record indicates. If the hammer moves between two carriers and only one of them records anything, the error can run the other way, and it can run in the dangerous direction.
SolidTrack does not read a wired hour-meter feed from the carrier or the attachment. The Field Unit carries a 3-axis accelerometer, and recorded activity hours are derived from its motion telemetry under configured rules. Motion patterns classified as activity are separated from periods classified as inactive. That is a deliberate design decision, and it has a consequence that is better expected than discovered. SolidTrack figures can legitimately differ from a machine's own counter because they come from different signals and serve different purposes.
The direction of the difference is the first thing to read. When motion-derived recorded activity lands well below the engine counter, the engine may have remained running during periods classified as inactive. That gap can raise a scheduling question, a haulage question or a site-flow question rather than a maintenance question alone. The answer may sit in truck cycles and shift planning, not the workshop. When recorded attachment activity comes in above what the paperwork assumed, the service plan may need review. Either way, the gap adds context to your operation. It is not automatically an error to be reconciled away, and the effort usually spent trying to make the two figures agree is better spent asking why they do not.
The gap matters commercially as well as mechanically. Anyone who hires equipment out, or hires it in, eventually has a conversation about reported equipment use, and that conversation often runs on a counter that either side can characterize as it prefers. A motion-derived activity record gives both parties supporting context and gives the owner something to compare with a claimed usage figure. It does not replace the contractual or OEM meter. The same context helps internally between depots and sites, where a machine loaned across a boundary can come back with figures that nobody quite agrees on.
So which number do you service on? Keep the machine's own counter where service, warranty, resale or contract terms require it. The manufacturer wrote its intervals against its own meter, a buyer will read that meter, and there is nothing to be gained from fighting either of them. For wear-related inspection and operational service planning, review SolidTrack recorded activity alongside the configured maintenance requirements and service history. A breaker with forty hours of recorded firing activity in a fortnight and one with four may not deserve the same workshop priority, whatever their carriers' counters have to say about it. Two records, two purposes, and no need to force them into one.
When a figure does look genuinely implausible, read underneath it before escalating. For breakers, every firing burst is classified by how long the tool stayed down, and motion patterns associated with blank firing are reported as a telemetry-derived share of the period. A machine with a high recorded activity figure and a large blank-firing share may therefore carry more classified blank-firing activity than the headline alone suggests. Coverage is a separate matter again. The unit holds three hundred entries by default when it is out of network and uploads retained records once it returns; longer gaps can exceed the available storage. A quiet period on the map can reflect time spent out of coverage rather than a device fault. When conditions permit, the unit reports a GNSS position. Where supported by the modem and network, coarser cellular positioning may supplement it, but it is network-dependent, less precise than GNSS and not guaranteed to produce a position fix.
The practical way to build trust in all of this is to start with one machine everybody already has an opinion about. Take a week, put the counter reading and the SolidTrack figure side by side, and ask the supervisor which version matches the week they remember. SolidAI Hub can compare equipment and sites directly. Operator or shift comparisons are available where those assignments were made in advance; SolidTrack does not identify operators or shifts automatically. It can summarize what the difference consists of if you would rather not do the arithmetic yourself. Run that comparison for a week and you will have your own answer rather than an argument about whose figure is right: engine hours were never the only context anyone wanted, they were just the thing that was easy to count.