LEXUNYUFLEET & EQUIPMENT TELEMATICS

Choose a project route

Keep what works, then compare an addition, replacement or second supply batch.

Known modelProject goalHardware catalog

Check camera connector compatibility

Add a camera view while keeping the existing viewing workflow.

Standard and HD connector paths have different camera-signal and equipment conditions. The reviewed Standard connector scope covers the US, Canada and UK, not Germany or the Netherlands; this restriction is not a claim about HD. Check the exact connector, gateway, dashcam, licence and country before choosing a path.

View project route →

Keep the tracker when adding video

Check how video can be added without replacing an existing tracker or platform.

FMC125, FMC225 and FMC650 are named DualCam hosts. Check the installed port, firmware, power and media receiver. FMC920 is not named in that host relation.

View project route →

Check the parked-temperature alert chain

A phone alert during parking needs more than a sensor name.

For C003F-CAT1, confirm the exact temperature probe, firmware and decoded platform field before setting an alert threshold.

View project route →

Preserve the installed security service

Check which installed services must remain before considering an addition or replacement.

Compare the device, monitoring, applicable identity or immobilisation features, installation and support as separate obligations. A GPS tracker alone is not an equivalent monitored service.

View project route →

Choose the location update your trailers need

Finding an asset may require a stored position, a fresh request or updates during a search.

Check battery maintenance, radio coverage and the device response while parked. Catalogue battery or module options do not establish wake-up behaviour or response time.

View project route →

Separate a new supply batch from a fleet migration

A new batch can be assessed without assuming all installed devices will be replaced.

Keep existing devices where appropriate and identify mandatory platform fields for the new batch. A supported-device directory does not establish every field, event, firmware or accessory.

View project route →

Separate video, DDD files and activity data

Identify the required output before selecting equipment.

FMC650 and TachoSync form a documented route for supported tachographs. Check the exact version, connection and firmware. The documented deployment requires a registered company card and an always-available card-reading computer; a card mention alone is not authorisation evidence. Confirm the file recipient.

View project route →

Check existing temperature data first

A missing report value does not automatically call for new equipment.

Compare the same device and time window across collected fields, stored history and report settings.

View project route →