What's new in Vehicle Monitoring 2.3.18.0 - Vehicle Monitoring 2.3.18.0

Vehicle Monitoring 2.3.18.0

Health metadata logging optional: You can now deactivate the logging of health metadata to reduce the amount of metadata stored on the vehicle. This is disabled by default and should only be activated if health metadata must be shown in the route playback task in the Fleet monitoring plugin.
NOTE: This setting should be deactivated unless your organization needs to be able to offload and playback this data.
Configuring the Vehicle Monitoring plugin role headend.

Vehicle Monitoring 2.3.17.0

Add metadata to GPS unit auto-created event: GPS units can now be automatically created when any data, or only metadata, is received from new vehicles that GPS units have not been created for yet.
Embed vehicle ID in NMEA sentence: You can now select whether the vehicle ID appears at the beginning or end of the NMEA sentence. For more information, refer to Configuring the Vehicle Monitoring plugin role headend and Configuring Vehicle Monitoring plugin data sources.

Vehicle Monitoring 2.3.16.0

Specific IP address for data source: You can now have a data source listen on all IP addresses (default) or a specific IP address for special cases. For more information, refer to Configuring Vehicle Monitoring plugin data sources.
Exclude health metadata from local vehicle data history report: You can now exclude health metadata from local vehicle data history reports to save data storage capacity and reduce on-screen clutter.
Continuous database cleanup: You can now institute continuous database cleanup. This increases efficiency by doing cleanup in small batches, frequently, instead of large batches, infrequently. For more information, refer to Configuring the Vehicle Monitoring plugin role headend.

Vehicle Monitoring 2.3.14.1

Retrieve geofence updates from headend: You can now configure the Vehicle Monitoring to update geofences using data from the headend. This process uses a REST API provided by the Fleet Monitoring plugin to retrieve the geofences. For more information, refer to the Geofence monitoring section of Configuring the Vehicle Monitoring plugin role on vehicles.

Vehicle Monitoring 2.3.13.2

Custom overlay text on videos: You can now overlay text on a vehicle's videos to help prevent sensitive information leaks by displaying the ownership or source of the video.

Vehicle Monitoring 2.3.13.1

Initiate Windows shutdown via Metadata key and value pair: You can now define a metadata key and value pair that, when matched, results in a Windows shutdown. For more information, refer to the Automatic Shutdown section of Configuring the Vehicle Monitoring plugin role headend.

Vehicle Monitoring 2.3.13.0

Automatic configuration of GPS units: You can now set up auto configuration in the Vehicle Monitoring plugin so that newly created GPS units conform to a pre-defined template. For more information, refer to Setting up auto config.

Vehicle Monitoring 2.3.12.0

REST API configuration template: You can now configure a REST API in the GPS plugin for configuration template management. For more information, refer to the REST API section of Configuring the Vehicle Monitoring Plugin metadata properties.

Vehicle Monitoring 2.3.11.0

Process only ALPR reads within geofence: You can now configure vehicles to only process ALPR reads when a GPS unit is within a geofence. The primary use case for this configuration is bus lane enforcement. For more information, refer to the Geofence monitoring and ALPR read events sections of Configuring the Vehicle Monitoring Plugin metadata properties.

Vehicle Monitoring 2.3.10.1

ALPR read events: You can now configure the Vehicle Monitoring plugin to listen for ALPR read events, record them as metadata, and bookmark video with that metadata.

Vehicle Monitoring 2.3.10.0

Automatic GPS unit creation

You can now set up automatic GPS unit creation. Create a GPS unit entity in the Area view task and designate it as your automatic creation template, then select this template GPS unit and define a default area in the Properties tab of the GPS plugin that automatically created GPS units will be assigned to. When the feature is enabled, if a vehicle ID is received in a data source and a GPS unit does not already exist for that vehicle ID, the GPS unit will be created automatically using the template GPS unit for its configuration. For more information, see the following:

Genetec mixed data source: GPS and metadata on the same port: You can now submit both GPS and Metadata on a single port. For more information, refer to Configuring the Vehicle Monitoring plugin role headend.
Monitoring tile metadata tab: You can now display the current value of each metadata key for GPS units in the Monitoring task.

Vehicle Monitoring 2.3.90.0

Log GPS and metadata to flat files: You can now choose to log GPS and metadata to files. You can configure the location of the logfiles as well as how many minutes of data should be kept for each logfile. For more information, refer to the Data Logging section of Configuring the Vehicle Monitoring Plugin metadata properties.

Previous versions

GUS for Vehicle Monitoring plugin: You can now update to the latest version of the Vehicle Monitoring plugin with the Genetec Update Service.