Skip to content

CloudBoxx⚓︎

CloudBoxx Firmware 2.20.0

New features of this version are:

  • Smart Key Module Support: Adds support for the Smart Key Module (SKM).
  • Automatic Detection and Resolution of Downlink Data Communication Failures: The CloudBoxx can now detect and resolve special network situations where server initiated communication (downlink) is not working whereas device initiated communication (uplink) has no issues. This feature is now enabled by default.
  • Display Gearshift Position in CloudBoxx Status: The CAN data for reverse gear, neutral position, park position and drive position of vehicles with automatic transmission are now displayed in the status of the CloudBoxx and in vehicle states (OneAPI) as gearshift_position.
  • Support for ISO-14443A RFID-tags with HF Keyholder: Using the new keyholder device (high frequency keyholder), it is possible to monitor ISO-1443A RFID tags/cards (e.g., Mifare).

Improvements included in this firmware release are:

  • Damage Detection Feature Improvements: Optimized machine-learning models and internal improvements for damage detection.

CloudBoxx Firmware 2.19.0

CloudBoxx firmware version 2.19.0 has been released.

New features of this version are:

  • Intelligent Central Lock Status: Offers more precise information about the central lock status in certain cases (see release notes for more details).
  • Tracking Reasons: Tracking messages now include a reasons field indicating one or more reasons why a particular tracking event was triggered.

Improvements included in this firmware release are:

  • Improved data integrity around firmware upgrades or power loss scenarios
  • The GNSS position processing of the Damage Detection feature is improved
  • Various bugfixes

Info

Navigate to CloudBoxx > Release Notes to see a more detailed list of those changes, including instructions on how to use the newly introduced features. You need to login using your FleetControl credentials at the top right of this page to be able to view the detailed release notes.

New Event Reasons for CloudBoxx

We now have dedicated and more understandable event names for 5 CloudBoxx event reasons which were previously sent as part of a generic CAN value high or CAN value low event. Every CloudBoxx with a supported vehicle model will send out central_lock_read_state_changed and doors_changed events following the release of firmware version 2.18.

CloudBoxx Firmware 2.18.0

New features

GNSS speed as speed source

The CloudBoxx can now use the displayed GNSS speed as the speed source. This will cause the speed property to be updated with the speed data from the GPS module.

New event reasons

The CloudBoxx will now generate new dedicated events for door state changes and central lock read state changes. Additionally, three new configurable events are introduced for handbrake, lights and windows state changes. The configurable events can be enabled or disabled using the route reasons_to_create_events_for which is a child object of event-config.

Air quality detection (prototype)

The CloudBoxx can be equipped with an external air quality sensor that would enable it to send air quality events. This can be utilized for features such as smoke detection.

Improvements

Increased mobile data speed

The CB 1020 series modem now uses higher Baud rates for data transmission. This reduces the transmission time for damage detection messages and speeds up download times.

CloudBoxx can now detect permanent uplink data communication failures, which can occur under certain network conditions, and automatically switch to another mobile network.

CloudBoxx Firmware 2.17.0

New features

Auto Immobilizer Control

This firmware introduces a new feature ‘auto immobilizer control’. When this fleet feature is enabled, an unlocked immobilizer would automatically lock itself if certain lock conditions were fulfilled. This feature is meant to bring more safety to the car-sharing ecosystem. For assistance in configuring this feature, please contact our support team.

RTC Calibration

The CloudBoxx’s RTC (real-time clock) tends to drift a few seconds during the day due to some hardware limitations. A new compensation algorithm reduces this effect and improves the clock’s accuracy. The clock is used to generate timestamps for all sorts of events. The device must be running for at least 12 hours, before this new compensation algorithm takes effect, and it will occasionally need a GPS signal to ensure high accuracy.

OBD Feature

The CloudBoxx can now be operated in a more non-invasive way by connecting it to the vehicle’s OBD-II port. To do this, a basic functionality has been implemented where the CloudBoxx receives the following information via the OBD-II protocol: ignition, speed, fuel level and mileage. The availability of this information depends on the vehicle model.

Note that this feature is only available in OneAPI.

Improvements

Less current consumption when using the Damage Detection product

We have optimized the power consumption of the CloudBoxx. While using the Damage Detection product, you should now see less CPU time consumed by these boxes running this product.

New thresholds for low_bat_alarm configurations

You can now configure higher low_bat_alarm thresholds for the CloudBoxx. This is very helpful for vehicles that run on a different voltage level than the usual 12VDC.

The new maximum boundaries are:

CloudBoxx:

  • low_bat_alarm_threshold: 55.5V
  • low_bat_recovered_threshold: 56V

CloudBoxx Mini:

  • low_bat_alarm_threshold: 99.5V
  • low_bat_recovered_threshold: 100V

CloudBoxx Firmware 2.16.0

New features

Damage detection

This firmware introduces support for the optional Damage Detection service. Damage Detection provides detailed information on vehicle damage and enables comprehensive, automated damage management. The Damage Detection Module peripheral device captures various data from the vehicle in daily use. The solution’s algorithm filters and compresses a large part of this raw data. The filtered data points are then further analyzed in the cloud by an AI algorithm which identifies patterns and anomalies. The AI assigns them to specific events, such as a parking accident, in real-time that have actually led to damage to a particular component. At the same time, it recognizes if it was only a door being closed or a pothole being driven over, resulting in no damage and making a report unnecessary. This feature is available for the CloudBoxx 4G/1020.

New mileage source option combined

The new mileage_source option combined can be helpful to get a more accurate mileage value. This is typically the case if the vehicle provides the mileage on the CAN bus (with CDF4) but only with a resolution of one kilometer, i.e., without decimal places. With the mileage source option set to combined, the fractional part is captured using the speed information, and added to the basic mileage value read from the vehicle’s CAN bus.

Improvements

Faster initial cellular connection setup

The initial cellular connection setup after installation of the CloudBoxx in a new country has been sped up by two minutes. Country changes during operation were not affected by this delay. This improvement is available for the CloudBoxx 1020.

CloudBoxx Firmware 2.15.0

New features

New SmartKey options

Two new options for operating the CloudBoxx with a Passive Entry/Go SmartKey inside the SmartKey Device have been integrated. The option extended keyless resolves some issues with the SmartKey device installed in certain vehicles which use a more advanced SmartKey inside-/outside-detection. With the option only_on_central_lock, the SmartKey is only used for locking and unlocking the vehicle but not for immobilization. This option is recommended to be used with specific CloudBoxx setups that realize the immobilization of the vehicle differently, e.g., with the starter-interruption- or code-line-relay.

Integration of Birò Vehicle Interface

The electric micro car vehicle Birò is now supported with the CloudBoxx Mini. Special handling regarding the software and hardware interfacing is required to operate this vehicle with the CloudBoxx Mini. This handling can be enabled with the vehicle_interface parameter under the /devices/{qnr}/config resource. Note that Birò is only supported by the CloudBoxx Mini.

CloudBoxx Firmware 2.14.0

New features

Automatic SIM switch options for CloudBoxxes with 2 SIMs

CloudBoxxes equipped with two SIMs can now perform an automatic switch of the SIM whenever a disruption of service is detected for the current SIM.

The feature can only be configured by INVERS.

Improvements

Improved time synchronization

The synchronization of the Real Time Clock (RTC) is performed more regularly. Under normal conditions, this leads to a typical maximum time drift of about 6 seconds, whereas previously the drift could reach up to 20 seconds.

Improved total mileage storage

The mileage value is now additionally stored in non-volatile flash memory so that it can be restored after most failure scenarios. If the backup battery of the CloudBoxx ran out and in other rare scenarios, the total mileage value got lost which lead to the CloudBoxx reporting unreasonable values.

Improved timing for voltage measurements

When the CloudBoxx leaves standby mode, the measurement of the board voltage and the backup battery voltage (CloudBoxx Mini only) is now triggered more quickly. This provides more accurate board voltage values in the power-fail and power-recovered events.

CloudBoxx Firmware 2.13.0

New features

Survival mode

CloudBoxx Mini now supports switching to survival mode to save power. The device enters this mode automatically when the following entry conditions are met:

  • mode is activated
  • external power supply is unavailable
  • immobilizer is locked
  • ignition is off
  • configured low battery threshold is crossed

In this mode, the CloudBoxx is not sharing ready and unaccessible via server. Once in survival mode, the CloudBoxx will wake up in a specific time intervals and perform the following survival mode tasks:

  • measure backup battery voltage
  • send a heartbeat
  • send a tracking

Generic method to access Alarm Input Status and configuration

The API routes to access the Alarm Input status and configuration were extended to provide a more generic method to get and update the configuration of the Alarm Inputs and to get the state of the Alarm Inputs. The old methods are still available, but only support Alarm Input 1 and Alarm Input 2.

Warning

Unavailable Alarm Inputs are not displayed in the status anymore. Previously, they were displayed as off. This change currently only affects the CloudBoxx Mini.

Generic event for Alarm Input changes

The event was added as a generic event for Alarm Input changes, including Alarm Input 1 and Alarm Input 2. The existing events ALARM_INPUT_CHANGED for Alarm Input 1 and ALARM_INPUT_2_CHANGED for Alarm Input 2 are still generated.

Added Alarm Input 3 and Alarm Input 5 (only CloudBoxx Mini)

The Scooter Input of the CloudBoxx Mini can be used as Alarm Input 5. If the Scooter Input is used to control the vehicle, Alarm Input 5 is unavailable. Alarm Input 3 is available when certain extenders are connected. The current states of Alarm Input 3 and Alarm Input 5 are also accessible over BLE.

Improvements

Improved triggering accuracy for shock, motion, and crash detection

The shock, motion, and crash detection internal triggering accuracy has been improved.

Tilt detection also works while shocks or motion are active

A previous limitation has been resolved, so that now the tilt angle is also measured while a shock or motion is active and TILT_STATUS_CHANGED events are generated accordingly. The tilt measurement may fail during active shocks or motion if a measurement is impossible due to external circumstances.

Improved BLE power consumption

The power consumption of the BLE module has been reduced while the BLE Beacon feature is not configured.

Improved BLE Beacon compatibility

Added support for legacy Eddystone BLE Beacons and support for iBeacons with Extra Byte feature (the Extra Byte is ignored).

Deleting status- and event config

The DELETE method has been added to the /status-config and /event-config API routes to allow resetting existing configurations.

Extended Can Values field

The can_values field in the /status route can now show up to 20 values. Previously, it was limited to 16.

More event-config entries

The can_description_to_create_events_for field under the /event-config route can now hold up to 32 entries. Previously, it was limited to 16.

Cellular connection setup

The mobile connectivity of the CloudBoxx has been improved. Especially the reconnection speed after a connection loss has been sped up.

Event and tracking message latency

Congestion of event and tracking messages, caused by temporary loss of cellular connectivity, is now resolved faster. This reduces the latency of server-side reception of these messages.

Locking the vehicle per RFID after expiry of access grant

The vehicle can now be closed by presenting an RFID tag or card to the card reader even if the access grant for this tag/card has expired. According to the options of the access grant (parameter switch_immobilizer false or true) either only the central lock or both, i.e. central lock and immobilizer, are locked. Such locking of the vehicle with the expired access grant is no longer possible once the next immobilizer or central lock command is triggered, e.g. by API command, by BLE command, or by a different RFID tag with a valid access grant.

Default value for Heading Change Threshold

The default value for the configuration parameter tracking_heading_change_minimum_threshold has been changed from 60° to 45°.

CloudBoxx Firmware 2.12.0

New features

Crash detection

The Crash detection feature has been added. When enabled and while the immobilizer is unlocked, the CloudBoxx detects abrupt accelerations and generates crash_detected and crash_data_ready events. This feature uses the new group_id field of the event message.

Cornering detection

The Cornering detection feature has been added. When enabled and while the immobilizer is unlocked, the CloudBoxx detects sharp cornering of the vehicle and generates cornering_started and cornering_stopped events. This feature uses the new group_id fiel of the event message.

Heavy breaking detection

The Heavy breaking detection feature has been added. When enabled and while the immobilizer is unlocked, the CloudBoxx detects harsh acceleration and breaking and generates heavy_breaking_started and heavy_breaking_stopped events. This feature uses the new group_id field of the event message.

Additional data for Shock detection

Shock detection has been expanded by the shock_data_available event. It contains information about a previous shock event. The already existing configuration parameter minimal_interval_s can be used to select for how long the information is collected after the shock. This feature uses the new group_id fiel of the event message.

Improvements

CAN bus communication

Improved compatibility to CAN nodes with inaccurate clocks.

Cellular connection monitoring

In certain situations, the cellular module ddi not report the loss of the network connection, e.g. when the module crashed. The CloudBoxx now monitors the state of the cellular module more frequently so that the connection is reestablished much faster in these situations.

Cellular connection setup

The connection establishment has been accelerated.