Available Telematics Units
This list is introduced with FleetControl 2.0 and includes all CloudBoxxes that are assigned to your fleet but not yet (or no longer) installed and configured into a vehicle. There are mainly two reasons for a CloudBoxx to appear in this list:
- It is part of the CloudBoxx inventory that has been delivered to you, but is not yet installed into vehicles.
- The CloudBoxx has been uninstalled from a vehicle. This can either happen if the “replace telematics unit” feature of SmartControl has been used, or if the vehicle the CloudBoxx was associated with was archived.
Please Note
CloudBoxxes which are part of this list do not have an Inspect page and it is not possible to send commands to them from within FleetControl 2.0 or through the INVERS OneAPI. They are accessible using the CloudBoxx API just like before. If you think a CloudBoxx mistakenly part of this list, perform a car setup using SmartControl or the CloudBoxx API. It will then become a proper vehicle again.
Column | Description |
---|---|
Telematics Unit ID (QNR) | The telematics unit main identifier. For CloudBoxxes, this is the QNR. |
Secondary ID (Serial Number) | The secondary identifier of the telematics unit (serial number in case of the CloudBoxx). |
Firmware Version | The firmware version the telematics unit is currently running on. |
Telematics Unit Model | The model of the telematics unit (e.g., “4G”, “1020”). |
Telematics Unit Variant | The model variant of the telematics unit, if there are different variants available. |