Skip to content

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