Construction sample validation

Engine Hours vs Powered-On Time: Validate the Source on One Construction Sample

A buyer method for separating true engine hours from powered-on time when a CAN/J1939 gateway sample is checked on a real powered machine — before any bulk decision.

Keep three records separate
01SOURCEName how hours are produced.
02PLATFORMConfirm the field on the receiving system.
03MACHINECompare against the cab meter when possible.
Illustration of an excavator service compartment where machine interfaces may be checked

Illustration for this article; it does not show a customer deployment, measured result or certified installation.

On this page
Key takeaways
  • Powered-on time and engine hours answer different questions; do not merge the labels.
  • A CAN/J1939 gateway sample is useful only when the project has a machine field to validate on a powered asset.
  • Leave unsupported hours unavailable; a map pin alone is not bulk acceptance.

Imagine a plant manager reviewing one excavator after a sample install. The platform shows “hours,” the cab meter shows another figure, and the office cannot tell whether the number came from the machine bus, an ignition wire or motion. This article is a buyer method for keeping those sources separate on one construction sample. It reports no customer result, measured accuracy or inventory claim.

Why hours labels get mixed

On construction machinery, three common “hours” ideas often share one UI label:

Label often usedTypical sourceWhat it can support
Engine hoursA verified machine interface (often CAN / J1939) mapped into the receiving platform.Maintenance or utilisation records only after the field is confirmed on that machine and firmware.
Powered-on timeAn agreed ignition, ACC or permanent-supply signal configured in the terminal.Key-on or supply-present time. It is not automatically work time.
Motion / vibration proxyMovement or vibration events used as a rough activity estimate.At most a utilisation hint. Do not treat it as the system of record for engine hours.

Published construction guidance on this site is explicit: true engine hours need a verified machine interface and platform mapping; an agreed ignition signal may provide powered-on time; without a verified source, hours may be unavailable. Keep that distinction in the sample record instead of forcing a single number.

Decide whether you need a gateway

Not every construction tracker question needs a CAN / J1939 industrial gateway. Use the project question first:

  • Location and movement only: a location-capable powered unit may be enough if the office does not need machine fields.
  • Machine fields on a powered excavator, agricultural machine, mining unit or generator: a gateway such as A300 is in scope when CAN / J1939, and often RS485 / RS232 / TTL, belong in the agreed wiring path.
  • No fixed power: pause on A300-class gateways. Unpowered trailers, containers and many attachments need a different device class — see the no-fixed-power guidance.

A300 product copy states the same pause rule: pause when the asset has no fixed power, or when the project only needs a basic location record with no machine field to validate. Platform connection depends on the selected protocol, fields and receiving system and is confirmed per project.

Write the acceptance question first

A sample that draws a map pin shows one observed location event in that setup. It does not establish long-term behavior, machine suitability, platform field mapping or production consistency. Before paying for or evaluating a sample, lock a one-page brief that the buyer, installer and platform owner can share:

  1. Machine type, make/model family if known, and whether fixed power is available.
  2. Whether the office needs engine hours, powered-on time, location only, or named CAN fields.
  3. Mounting position, voltage expectation and weather / vibration exposure.
  4. Receiving platform, protocol or endpoint, and the exact field names that must appear.
  5. Destination market and which manufacturer-issued documents must be checked for the exact model.

If a value is unknown, write UNKNOWN with an owner and a date. Do not silently turn an assumption into an acceptance criterion. For the wider China-sample workflow, use how to validate a China GPS tracker sample before a bulk order.

Five sample records to keep

During the sample stage, agree who supplies the machine, wiring map, protocol and field definitions; who configures the terminal; and who verifies each record on the receiving platform. Keep at least these five records for a construction gateway sample:

#RecordPass condition (method)If missing
1Hours source statementWritten note of CAN / J1939, ignition/ACC, vibration proxy, or unavailable — plus firmware / configuration ID.Do not use the UI “hours” label for maintenance or billing decisions.
2Platform field mappingNamed platform field, unit, timestamp meaning and who approved the mapping.Treat the value as unmapped raw data, not an accepted business record.
3Power and mount notesSupply tap, voltage observation method, antenna / enclosure position and service access.Retest before comparing candidates; table power-on is not site proof.
4Location path checkSeparate position fix, device transmit (if exposed), platform receipt and UI time — same discipline as the construction accuracy method.Leave delay claims unavailable when clocks or event meanings are mixed.
5Sample identity lockExact model, BOM notes if provided, firmware version and configuration snapshot retained with the decision.Do not assume the next production unit matches the sample.

Use the blank machinery installation data record (CSV) to capture mounting and data notes while the sample is on the machine.

Compare against the cab meter

When the project claims true engine hours, plan a same-machine comparison:

  1. Photograph or note the cab hour meter at the start of the observation window.
  2. Run the machine under the agreed duty for a defined period owned by the installer or site lead.
  3. Record the platform cumulative hours field at the end of the same window.
  4. Record the cab meter again, with the same person confirming both readings when practical.

Agree the acceptance condition before the run. This article does not publish a universal percentage threshold, a measured LEXUNYU field result, or a ranked product claim. If the machine bus is not reachable, or the field is not mapped, mark engine hours UNAVAILABLE and decide whether powered-on time is an acceptable substitute for that workflow.

Attachments are a separate decision

Buckets, breakers and other attachments often have no permanent supply. A battery unit can give position and movement; it does not inherit engine hours from the host excavator. Powered attachments need their own electrical and data-source check. Do not assume one gateway on the host machine proves attachment utilisation.

For plant mechanics and device-class context, see how plant machinery trackers work. For installation traps that appear before any platform review, see five heavy-equipment installation mistakes.

What a sample order does and does not prove

An evaluation sample is useful when it forces the machine, wiring, fields and receiving platform into one check. Commercial starting points published for A300 include: samples and small pilots available; customisation typically from 100 units; 12-month limited warranty from the commercial-invoice shipment date. For the current A300 sample offer, shipping, import charges and the sample fault-on-arrival path are stated on the product page and linked policy pages — confirm destination and configuration before payment.

A sample order does not prove:

  • that every CAN field exists on every machine;
  • destination-market marks for a configuration that has not been document-checked;
  • batch consistency without a sample-to-production statement;
  • platform readiness without a mapped receiving workflow;
  • any customer case study, inventory level or traffic metric (those remain UNKNOWN unless separately evidenced).

Compliance documents for A300 are issued by the manufacturer per model and checked against the exact model number, radio module and antenna before quotation. No certificate on file currently lists A300 by name; do not invent FCC/CE coverage for this model. Keep your existing platform when that is the project intent — see keep your existing system and the buyer workflow in adding GPS hardware to an existing fleet platform.

Frequently asked questions

Is powered-on time the same as engine hours?

No. Powered-on time usually comes from an agreed ignition or supply signal. True engine hours need a verified machine interface and platform mapping. If that source is not verified, treat hours as unavailable rather than approximate them silently.

Does a map pin mean the sample is ready for a bulk order?

No. A location event only shows that one position message arrived in that setup. It does not establish machine-field coverage, platform field mapping, install survival or sample-to-production consistency.

When should a construction buyer pause on a CAN gateway such as A300?

Pause when the asset has no fixed power, or when the project only needs a basic location record with no machine field to validate. Unpowered trailers, containers and many attachments need a different device class.

What commercial starting point exists for an A300 evaluation?

Samples and small pilots are available. Customisation typically starts from 100 units, with a 12-month limited warranty from the commercial-invoice shipment date. Exact destination-market documents are confirmed per model before order.

Who wrote this

Ziyi Wang — LEXUNYU, Shenzhen. Independent sourcing and integration support for fleet and industrial telematics hardware. LEXUNYU does not manufacture devices and does not operate a SaaS fleet platform. This article is a practical buyer method, not a field test report.

Manufacturer documents and field results vary by model, configuration, site and market. Share the intended use case and evidence requirements for a written review.