Locate vehicles and assets
Location, movement and power events can start with a wired or battery GPS terminal, antenna and connectivity. Choose reporting intervals around the asset and the record your dispatcher needs.
Asset location projects →Hardware for your fleet & equipment data.
For fleet operators, equipment teams and integration partners: we match hardware, coordinate multiple suppliers and support project validation — from GPS and machine data to video and sensors, with your existing system in view.
No mandatory LEXUNYU platform subscription.
Connectivity and third-party service fees may apply.
FIELD OPERATIONS
Start with the decision your team needs to make.
Keep my existing platform or start from the operational outcome. We will ask for the receiver, installation and decision the path must support.
Find vehicles and assets, plan machine service, review a trip event or understand a cold-chain exception. The useful output comes first; the terminal, gateway, camera and sensors follow the project.
Which operating question needs a clearer answer?
Data & hardware combinations
One operating result can need more than a tracker.
We help scope the components across suppliers. Start with the record your team needs, then match the hardware and receiving path. These are project paths, not pre-integrated packages.
Bring machine data into view
Hours, operating state and available controller fields may need a vehicle or industrial gateway, CAN/J1939 or serial interface and the right harness. We coordinate field and access checks with the supplier and your system team.
Equipment data projects →Review an event with video
A useful clip needs an agreed trigger, timestamp and retrieval path. Camera, recorder, power, storage and data plan are considered together with your receiving platform and access permissions.
Event video projects →Record temperature and condition
Temperature, door and fuel readings may involve probes, contacts or other sensors, a reader and a terminal. Placement, calibration and the way a reading becomes a report matter as much as the device.
Cold-chain records →Identify, install and control
Driver or asset identification can involve readers and tags; authorised control may involve a relay. Harnesses, mounting and power protection are part of the installation discussion, with responsibilities agreed before a sample.
Explore component roles →Connect to the system you use
Network access, antennas and gateways support the receiving path. We distinguish a device protocol from platform API/file exchange and historical migration, rather than treating them as the same connection.
Existing-platform paths →How we coordinate
From your working requirement to a sample decision.
You bring the operation and receiving system. We coordinate hardware options, supplier information and a practical validation plan with the people responsible for installation and integration.
Define the result
Agree the record, alert or export your team needs and the action it supports.
Match the components
Compare supplier paths against data fields, interfaces, installation and target market.
Agree the handoff
Confirm the receiver, permissions, integration owner and separate third-party costs.
Check a sample
Compare source and received records against acceptance criteria agreed with your team.
Representative products
A starting selection, not the boundary of your project.
Our nine published GPS and telematics models remain available to review. Wider hardware combinations are scoped across suppliers around your data, installation and receiving system — not limited to this selection.
A300
Heavy equipment data terminal
For powered machines that need location, operating state and validated machine or sensor data.
Heavy equipmentCAN / J1939Sensor projects
Review A300 
C003F
Expandable road-fleet tracker
Start with routine tracking, then add supported driver, temperature, fuel, camera or SOS workflows.
Road fleetsDriver IDTemperature & fuel
Review C003F 
GT76
Battery tracker for unpowered assets
For trailers, containers and temporary equipment that need periodic location without fixed power.
No fixed powerMagnetic mountingLong dwell time
Review GT76 
A18
Compact wired 4G tracker
Essential location, ignition status and security events where mounting space and budget are tight.
Compact mountingTwo-wheelersEssential tracking
Review A18 Samples and small pilot quantities available.
Customisation typically starts from 100 units. Sample dispatch time is confirmed when we quote. Volume lead time is confirmed per order.
Why buyers come to usOwn the hardware.
Own the hardware.
Keep your platform.
There is no mandatory LEXUNYU platform subscription. Connectivity, a customer or third-party platform, API or storage work, and project or installation services may cost separately and should be agreed for the route you choose.
No mandatory LEXUNYU platform subscription
Hardware can be assessed for an existing or third-party receiving route. Connectivity, platform, API, storage and installation responsibilities remain separate project decisions.
Cost lines stay visible
Hardware, connectivity, customer or third-party platform fees, API or storage work and installation are discussed as separate lines. Samples and small pilots come before any wider commitment.
Assess the receiving platform path
Where the selected firmware and receiver support it, the device may point at your server. Protocol documentation is requested from the selected model or manufacturer where available; fields, permissions and a sample still need checking.
Where available, manufacturer-issued compliance documents are checked for the exact model, variant and target market before quotation or order. How document coverage is checked →
Where hardware projects lose alignment
Hardware projects often lose alignment before installation.
A suitable device can still become the wrong project choice when operating conditions, installation requirements, the data path or delivery details remain unclear.
Requirement is still too broad
“We need GPS tracking” does not define the information, events and operational decisions the project actually needs.
Installation conditions appear too late
Power, space, wiring, weather exposure and operator behaviour can change which hardware configuration is suitable.
Device data does not match the platform
A device may report data and still fail to match the protocol, format or workflow expected by the existing platform.
Sample and rollout configurations drift apart
Firmware, accessories, cabling, market version and documentation must remain aligned as the project moves towards a larger deployment.
From hardware to your platform
Your platform stays yours. We help coordinate the data path.
An example four-stage cold-chain validation workflow. Each stage ends with a written result you can hand to the factory, the platform team and the installer.
-
LocationEvery 10 minBox temperatureEvery 5 minDoor statusOn open / closeFour fields in scope. Fuel level and driver ID stay out of scope this phase. 01Define
Define
Fix the fields, reporting intervals, event rules and platform format before a model is selected.
- Which fields are in scope, and which are not
- How often each field reports
- What triggers an exception event
- How field names and units map to your platform
Stage deliverable Field & Reporting Interval Sheet→ You get: a first draft based on the available inputs, with timing agreed for your project.
-
AntennaExternal — metal bodyPower24 V vehicle batteryTap pointUnder the dashboardConstraints are not there to praise a product. They are there to eliminate products. 02Match
Match
Work backwards from the real installation and target market, then compare the options that survive.
- Power source, voltage and tap point on the vehicle
- Water, vibration and temperature range at the mounting point
- Available bands and approvals in the target country
- Interfaces and external sensors required
Stage deliverable Candidate Comparison Sheet→ You get: a candidate comparison after the installation and market conditions are documented.
-
RoutingAlong the A-pillarPower tapConstant + ACCProbe entryThrough the box wallBeing able to buy the device does not mean the data gets in. 03Adapt
Adapt
Agree the message fields, units, time zone, harness and platform work before ordering the sample.
- Protocol and message format confirmed
- Field mapping, unit conversion and time zone
- Harness, interfaces and mounting position
- How accessories and external sensors connect
Stage deliverable Data Path & Mapping Note→ You get: an initial mapping note after the required protocol and platform information is available.
-
What the acceptance record compares
Location pointsexpected vs receivedTemperature samplesexpected vs receivedDoor eventsexpected vs receivedTimestamp alignmentagainst your platform clockFilled in from your own sample run, not from ours.Sample unitOn the vehicleA sample that runs proves nothing. Received matching expected does. 04Verify
Verify
Compare what the platform received with the agreed fields, then lock the validated firmware and configuration.
- Sample data checked line by line against the spec
- Firmware version and configuration locked
- Agreed method for checking batch consistency
- Who owns what if something goes wrong
Stage deliverable Sample Acceptance Record & Production Lock Sheet→ You get: an acceptance record after the sample evidence is complete.
Operational evidence
Turn selected field signals into operational evidence.
Available outputs depend on the selected hardware, connected sensors, vehicle or machine signals, network conditions and your platform.
Routine fleet record
Output: time, location and trip or event record. Core: tracking terminal, connectivity and receiver. Optional: ID, temperature or fuel input. Pilot: compare source timestamps and gaps with what dispatch receives.
Trips and unusual activity
Investigate supported events such as after-hours movement, route deviation or unexpected relocation.
Equipment hours
Output: machine or controller hours. Core: accessible source plus terminal or gateway. Optional: ignition-derived or manual comparison. Pilot: agree what counts as working before comparing records; never assume productive hours.
Temperature/door records
Output: timestamped temperature, door and exception records. Core: compatible probe, terminal and receiver. Optional: local storage. Pilot: agree probe position, clock, gaps and received fields.
Who moves the project forward
Operator: defines the useful decision. Platform/integrator: confirms receiver and mapping. Installer: confirms power and mounting. Procurement/distributor: confirms documents, commercial route and order handoff.
Data received by your platform
Inspect actual messages and fields during the pilot. The receiver, API or export path is selected with the platform team; documentation is available only where the selected model or manufacturer permits it.
Free, no sign-up
Three things you can use before you talk to anybody.
All three run in your browser. The answers are processed in your browser, and the tools themselves do not submit answers. Standard site performance measurement may still run under the Privacy notice, and the tools work with a supplier you found somewhere else.
01
Tracker selection check
Eight questions about power, wiring and how often you need to know. You get a hardware direction, existing candidate models, the requirements that contradict each other, and the checks still needed before final selection.
Run the check → 02 Field & Reporting Interval SheetThe blank document a project should open with: fields in scope, reporting interval, format, event rules, sample pass mark, three signatures. Fill it in the browser and print or save it as a PDF.
Open the blank sheet → 03 GPS tracker data usage calculatorEstimate data usage, compare update intervals and plan a 72-hour pilot for fleet and IoT projects.
Estimate SIM data →START WITH THE ACTUAL OPERATION
Tell us what you need to monitor, connect or replace.
A short description is enough. We will reply with the questions still open and an initial hardware direction.