Before an asset can use a specific mobile device or be configured to record certain events, the events, mobile device and peripheral devices that must be installed must be enabled on the organisation and this is done under libraries.
Libraries contain the elements which can be added to a database as a default configuration when configuring the actual mobile device, peripherals, events and parameters.
To understand how libraries, templates and configuration groups work together, read more here.
- Under Manage, click Config admin.
- Click Libraries.
Libraries are data center level repositories of configuration elements. When you make something available you copy these selected elements into the organisation library.
Mobile devices Library
The mobile device library comprises a full list of the available mobile devices e.g. MiX 6000, MiX 4000, MiX 2000, FM3316, VT1330, etc. Within this library you can define the mobile devices that the organisation will make use of in the creation of mobile device templates and edit the default mobile device settings for an organisation. Note: Changes made to the default mobile device settings on library will not cascade to the existing mobile device templates or configuration groups using this mobile device. It will be used for all new mobile device templates and configuration groups.
Peripherals Library
Peripherals are either physical devices connected to the input lines or can be intangible such as CAN scripts. Many standard peripherals, for example a Speed Sender, are already supported in the software and you can easily add other devices such as a Headlights Switch. Within this library you can perform some of the following functions:
- Make the input available for use in the creation of mobile device templates.
- Edit the default parameter calibration and configuration settings for the input device (not the input device type or parameters available).
- Add a new peripheral (and create a new parameter if necessary), select input type, define calibration and configuration settings for the input device.
- Duplicate an existing device and edit.
- Configure a peripheral device for Hours of Service.
Events can be defined to take information from these external devices into account. For example, an event to detect Over Speeding would take the value of Road Speed from the Speed Sender device into account.
Event Library
Events define what should be monitored and/or recorded by the unit as well as what other actions the unit should take when an event is detected, for example sending a message back to the office, switching on or off a device etc. Examples of standard events are Over Speeding, Harsh Braking and Excessive Idle. Within this library you can edit an existing events' settings and add a new user defined event for use by the organisation.
Parameter Library
Parameters are used to represent the values returned by connected devices. Examples of standard parameters are Road Speed (from the Speed Sender device) and Latitude (from the GPS Receiver device). In this library you can define the list of parameters that will be available for the creation of new input devices and events with their default settings and edit the default settings of a parameter (with the exception of its type) and define its profile.
This level is where the different elements are chosen for inclusion in the organisation's library and the default settings are defined here. These available elements can then be picked from to create a vehicle's configuration. Note: With the exception of the event library changes made to these libraries will not cascade to the mobile device templates or configuration groups using the mobile device, input device, parameter or event. If the update is required, it must be made at the template level as well.
For example, we have an asset that has a MiX 6000 unit installed, with a temperature sensor connected and we would like to know when any cold chain events trigger.
The best process to follow would be:
- Start by enabling the firmware by opening the firmware library, e.g. make firmware available for the MiX 6000 device you have installed this asset.
- Make the required devices available in the mobile device library and configure the default mobile device settings. Note: global changes should be made at library level. Fleet specific changes should be made at template level.
- Now select a peripheral from the peripheral library. When you make a peripheral available it also populates the parameters library with the associated parameters.
- Lastly choose the events, in the events library.
- If the event is not available, you can create it by adding a new custom event.
See below for a depiction of the steps required:
