Start here / V3

Make vehicle risk actions accountable.

A wired risk-control tracker for rental, finance and managed vehicles where SOS, overspeed and authorised immobilisation need a defined workflow.

V3 is a wired risk-control tracker. Authority, qualified installation, safety checks and the receiving platform are confirmed together before a project decision.

V3 wired risk-control tracker for rental and finance vehicles
V3Risk-control vehicle terminal

01 / When to choose

Does the operation need an accountable risk-control workflow?

Start with who reviews the event and who may authorise an action. Hardware details follow the safety and installation boundary.

Choose V3 when managed vehicles need more than a location timeline.

  • Rental, finance or higher-risk managed vehicles are in scope.
  • Movement, overspeed, power and driver SOS events need review.
  • A qualified installer can define the relay wiring and safe conditions.
  • Remote immobilisation is discussed only with written authority and safety checks.
Pause / compare

Pause when authority or safety is not defined.

V3 is not a button for an unconditional remote stop. If no authorised owner, qualified installer or safety procedure exists, pause the project before discussing a control action.

Selection is a project decision

02 / Daily answers

Turn the workday into three clear questions.

The page follows a managed vehicle from event review to the person and safety check behind any control action.

Rental vehicle record being reviewed for movement and power events
01 / REVIEW

Which events need review?

Movement, overspeed and power events form a timeline for the agreed risk workflow.

Driver raising an SOS event within a managed-vehicle workflow
02 / ESCALATE

Can the driver raise SOS?

An SOS event, notification owner and response process are confirmed within the project.

Authorised immobilisation procedure being checked beside a vehicle
03 / AUTHORISE

Who may authorise immobilisation?

Relay action is discussed only after authority, qualified installation, safe conditions and sample testing.

Managed passenger vehicles being checked for a controlled installation
03 / Technical support keeps authority and safety in the hardware conversation.

03 / Technical support

Keep the risk-control boundary visible.

V3 is a wired managed-vehicle tracker. The technical list names event paths and the checks needed before anyone discusses a control action.

CAT1Market and band configuration to confirm
GPS / BDS / AGPS / LBSGPS / BDS / AGPS / LBS positioning
9–95 V wiredVehicle supply to check
Optional 60 mAhVersion and vehicle behavior to confirm
ACC / SOS / overspeedEvent paths to verify
Relay / remote cut-offAuthority, installer and safety gate

Platform connection depends on the selected protocol, fields and receiving system and is confirmed per project.

Before ordering

Open the conditions before a risk-control pilot.

Check authority, relay safety and destination-market requirements before order.

Passenger vehicles lined up for a controlled fleet installation
A control action is a governed project step, not an automatic promise.
01Authority and safety before immobilisation+
Define the authorised owner, prohibited conditions, qualified installer and safe operating procedure before discussing relay action.
02Relay / power and installer test+
Check wiring, vehicle behavior, stationary or safe conditions and the response path on a sample before rollout.
03Market, platform and protocol request+
Destination marks, exact protocol, event fields and the receiving route remain project checks.
PRODUCT DETAILS

Specifications & order checks

Review the listed features and the points to confirm for the exact configuration, destination market and receiving platform.

Cellular
Verified4G LTE Cat-1.
Protocol
On requestNot stated in the material we hold; requested from the manufacturer per firmware build.
Platform integration
On requestWe have no hosted-platform deployment record for this model. Platforms ask for three things — device name, manufacturer reference and protocol documentation. We can supply those and submit the integration request with you.
Certification
On requestNo certificate on file lists V3 by name. Compliance documents are issued by the manufacturer per model and checked against the exact model number, radio module and antenna before quotation.
GNSS
VerifiedGPS / BeiDou with AGPS and LBS.
Interfaces
VerifiedACC input, relay output for remote fuel or power cut-off, SOS input; power-cut and over-speed alarms.
Power
Verified9–95 V DC wired supply, optional 60 mAh backup battery.
Enclosure
On requestNo ingress rating is stated. 79 × 33 × 16 mm, 43.5 g; protected in-vehicle mounting.
Firmware / FOTA
On requestNot stated in the material we hold. If remote updates matter, the update method, trigger and rollback behaviour are confirmed before order.
Traceability
On requestIMEI and serial list supplied with the shipment. The firmware build is recorded per purchase order and kept consistent within that order; a protocol or hardware change is notified before it ships. Batch and production records on request.
Commercial terms
Samples and small pilots available. Customisation typically from 100 units. 12-month limited warranty from the commercial-invoice shipment date; DOA terms confirmed in the quote.
Where it fits / where it doesn't
Vehicle finance, leasing and risk-control fleets that need cut-off and SOS. Not for exposed mounting and not for machine data.

How to read these labels. Verified stated in the manufacturer’s datasheet and checked page by page against the original document — not our own measurement. Series a document on file covers the series but does not list this exact model number. On request not stated in the material we hold; confirmed per model with the manufacturer before quotation. Not held required in that market and not currently held. We would rather show you a gap than describe it vaguely.

04 / Before order

A guided risk-control conversation.

The sample is where vehicle power, event ownership, relay wiring, safety conditions and the receiving platform become one check.

01

Name the managed vehicle

Confirm the rental, finance or managed-vehicle type and the installation point.

02

Name the authority

Write down who may authorise an action and which conditions prohibit it.

03

Name the event path

Agree SOS, overspeed, power, protocol and platform ownership within the project.

04

Define the safety requirements

Use a qualified installer and sample test; keep market marks, FOTA and traceability open.

Commercial starting point

Start small enough to learn.

Samples and small pilots keep the first conversation tied to the actual vehicle, relay wiring and safety workflow.

Samples and small pilots availableCustomisation typically from 100 units12-month limited warranty from commercial-invoice shipment date

FAQ / V3

Keep the next risk-control question obvious.

Talk through fit
Can the vehicle be stopped while moving?

Relay control is considered only with written authority, qualified installation and a defined safety procedure.

Does SOS call emergency services automatically?

No emergency dispatch is promised. The event, notification owner and response process must be defined in the project.

Can V3 monitor fuel?

Fuel is not part of the current V3 configuration. Move that question to a C003F or A300 project assessment.

Why choose V3 over A7C?

V3 starts with managed-vehicle risk events and authorised control. A7C starts with ordinary fleet visibility and a repeatable wired baseline.

05 / Project inquiry

Tell us what the managed vehicle must answer.

Share the vehicle type, authorised risk workflow, safety constraints, target market, platform and quantity. We will reply with the checks still open.

Review the V3 FAQ

Ready to discuss the exact V3 configuration, market and quantity?

Discuss V3 pricing