English
English
English
  • SWARM Documentation
  • What's new?
    • Version 2024.2
    • Version 2024.1
    • Version 2023.3
      • Update 1
  • SWARM in a nutshell
    • SWARM Perception Platform Overview
  • Quick start guide
    • P101, P401 or OP101
      • P101 - Perception Box
      • P401 - Perception Box
      • OP101AC - Outdoor Perception Box
      • OP101DC - Outdoor Perception Box
    • Virtual Perception Box
      • System requirements
      • Install VPX Agent on NVIDIA Jetson (Jetpack 4.6)
      • Install VPX Agent on NVIDIA Jetson (Jetpack 5.1.2)
      • Install VPX Agent on X86/NVIDIA Server
  • Solution areas
    • Traffic Insights
      • Set-up Traffic Counting
      • Set-up Traffic Counting with speed estimates
      • Set-up Intersection Insights
    • Parking Insights
      • Set-up Barrierless Parking
      • Set-up Barrierless Parking with ANPR
        • Set-up guide and recommendations - ANPR
      • Set-up Single Space/Multi Space Parking
        • Standard examples
    • Advanced Traffic Insights
      • Set-up Adaptive Traffic Control
      • Set-up Journey Time & Traffic Flow
        • Set-up guide - Installation
        • Technical concept
      • Set-up Queue Length Detection
    • People Entry/Exit counting
  • SWARM Control Center
    • Devices
      • Camera & Device Monitoring
      • Camera Configuration
        • Scenario Configuration
          • Models
          • Calibration support
          • Camera settings
        • Rule Engine
          • Use Case Examples for Rule Engine
      • Device Health
    • Data Analytics
      • Creation and organization of dashboards
      • Dashboard overview & Widget creation
        • Traffic Scenario
        • Parking Scenario
        • Generic Scenario
    • Data Integration
      • Data Analytics API (REST API)
      • Raw event data with Custom MQTT server
      • SCC API
    • Administration
      • Monitoring Alerts
      • License Management
      • User Management
  • Test & Performance measurements
    • Benchmarks
      • How do we measure Performance?
    • White paper for use cases
      • Traffic Counting
      • Barrierless Parking and ANRP
  • Useful knowledge
    • 🚒Troubleshooting Guidelines
    • Network Requirements
    • Browser Compatibility SCC
    • Our Object Classes
    • Number Plate Area Code
  • Guidelines
    • How to access the debug output?
    • How to use Azure IotHub as Custom Broker
    • VPX
      • Upgrade IotEdge from 1.1 to 1.4
      • Upgrade Jetpack from 4.4.1 to 4.6.0
  • Getting Support
    • Get in touch
    • FAQs
Powered by GitBook
On this page
  • Device Schedule (Running/Standby)
  • Improved latency for BMA/BMC
  • Other Improvements
  • Device Update Size
  • API

Was this helpful?

Export as PDF
  1. What's new?

Version 2024.2

Release Date: 02.04.2024

PreviousSWARM DocumentationNextVersion 2024.1

Last updated 1 year ago

Was this helpful?

Device Schedule (Running/Standby)

The device schedule allows you to define time slots when the device should be in operational mode (device state: running) or in power saving mode (device state: standby).

The power saving mode is mostly relevant for the battery powered system BMA Mobil since it extends the usage time for a single charge.

In our measurements, the BMA Mobil reduces the power consumption during standby by about 55%.

How to enable the schedule for a device?

  1. Open a device in the control center and select the tab schedule

  2. Switch the toggle to Enabled and select desired time slots when the device should be operational

  3. Save Schedule

What will happen during standby?

The device reduces the power consumption by pausing the video signal processing.

Functions that are not available during standby:

  • No events will be generated

  • No camera image is visible

  • No event triggers can be configured

Functions that are available during standby:

  • The device will be online in the Control Center, including available device health, logs, and reboot functionality.

  • Wake-up the device from standby (→Set the toggle to Disabled)

What is the expected battery lifetime?

In our measurements the BMA Mobil consumes 1,07A when active and 0,48A when in standby.

Examples

With an 100Ah battery degraded to 90Ah we get the following battery lifetimes:

  • Always active: 90Ah / 1,07A ~3,5 days

  • Always standby: 90Ah / 0,48A ~7,8 days

  • 13h active, 59h standby (Example from screenshot, total 3days): 13h * 1,07A + 59h *0,48A = 42Ah out of 90Ah (~50%)

Improved latency for BMA/BMC

We have been able to improve latency for the BMA working together with the BMC to < 1s. Measured by vehicle is physically present in a zone to the point when the BMC switches a dry contact.

Other Improvements

  • Fixed: On Curiosity startup the first Region of Interest event was always vacant (even if there were objects).

  • Improved: Curiosity performance improvements by avoiding to re-classify already classified objects

  • Improved: The Number Plate Column for DataAnalytics Parking widgets is optional

Device Update Size

2023.3 U1 → 2024.2: 155MB (BMA / P101 / Jetson Nano)

API

  • There are no API breaking changes