Define the working day
Tell us what equipment you manage, where it works, what keeps going wrong and what your team wishes it could see.
How we help
Tell us what is difficult today. We will help define a workable hardware path.
You do not need to prepare a technical specification. Start with the vehicle, equipment or asset, where it works and the information your team needs. We then map the outcome to needed data, possible hardware, existing-system integration and a project check — with suppliers coordinated around the brief.
Match realistic options
We narrow the choice around the actual power, weather, mounting, vehicle information and platform instead of sending an unfiltered catalogue. Candidate suppliers and evidence stay separate until the project confirms the fit.
Adapt the setup
Work through the installation, transmitted information, alerts and platform output around a representative vehicle or machine so the setup reflects the operating requirement.
Verify it on real equipment
Check the installation, transmitted information, alerts and platform output on a representative vehicle or machine before wider use.
The manufacturer supplies documented hardware; the platform team accepts decoding, fields and access; the installer accepts wiring; the customer agrees the task, thresholds and rollout decision. LEXUNYU is not the manufacturer, platform owner or full algorithm provider; connectivity, platform/storage, installation and project-service costs stay with their responsible parties. No model, stock position, universal compatibility or test result is guaranteed before the project check.
Before your batch ships
Checks to agree for the units themselves.
We are an independent sourcing and validation partner in Shenzhen, not a factory. We agree the checks with you, then record the results from your sample run before a rollout decision, with responsibilities set across the customer, manufacturer, platform team and installer.
Sample check on arrival
Where agreed, power up, acquire a fix, report to an agreed test server, and compare the IMEI with the label on each unit sampled.
Firmware build recorded
Request the manufacturer build intended for the batch and record the version observed on the sample; shipment consistency remains a manufacturer confirmation.
Build changes recorded
Agree how a protocol or hardware change is notified before shipment and which party keeps the approved configuration record.
Serial list with the shipment
Request an IMEI and serial list with the goods where available, so the customer can agree how units are traced back to a batch.
If a unit fails
Who you talk to, and what happens.
12-month limited warranty from the shipment date shown on the commercial invoice, and 30-day DOA terms. Repairs are carried out by the manufacturer — the difference is that you deal with one person here rather than chasing a factory in a language and time zone that is not yours.
Report it
Send the IMEI, what the unit was installed on, what it did and what the platform saw. A photo of the wiring usually saves a round trip.
Diagnostic checklist first
Check configuration, wiring, power, network, receiver records and the installation context before deciding whether the manufacturer should inspect the hardware.
Decide the route
Replacement, repair or a configuration fix. If it is our misjudgement in the selection, we say so.
We follow it through
We handle the manufacturer side and report back. Carriage terms and turnaround are agreed per case rather than promised as a fixed number we cannot control.
Problems worth avoiding
A tracker should make work easier after it is installed.
A long feature list means little if the device cannot survive the site, read the needed information or send it to the system your team uses.
It stops working after rain or vibration
Outdoor machines need hardware and mounting planned for the real exposure, not an ordinary cabin installation.
The asset has no suitable power connection
Trailers and containers need a battery plan; powered machines need the right voltage and sleep behaviour.
The office receives location but not the information it needs
Machine hours, door events, temperature and fuel questions must be defined before choosing the device.
The device cannot talk to your current platform
We check the server, protocol and required events before a wider rollout, not after the devices arrive.
Start with what you need
Tell us the problem, or the result you need.
You do not need to turn it into a technical specification. Explain the situation in everyday language: what is difficult to manage, what information is missing or what you want to improve.
Tell us what is difficult to manage
For example, vehicles are hard to locate, machine hours are uncertain, or important temperature, fuel and door events are missing.
Tell us what information your team needs
This may be location, running time, driver identity, temperature, fuel, door activity or supported data from the vehicle or machine.
Tell us where the equipment works
Share the equipment type, working environment, available power, installation conditions and the platform your team currently uses.
Tell us what a successful test should prove
Explain the result you need to confirm on real equipment before deciding whether to use the setup more widely.