Structure of Setting template
During manufacturing every device receives a setting template with main functionality.
In XDM portal you can edit existing template, or create your own to create desired performance.
Note. For Setting template to work, you need to configure just few elements (APN, Telemetry server, Data packet), rest are optional.
Main tree of Setting template.
1. Connectivity.
This part controls all settings related to device connections to servers.
Category | Subcategory | Description |
|---|---|---|
Configuration server | Session setting | Settings and rules for connecting to XDM configuration manager. |
Server address | By default must be set to the following address: | |
Internet permissions | Connection permission settings | Allows to configure internet permissions, or bans in certain conditions (roaming, etc.) |
GSM/GPRS | GSM operator group | Allows to assign a group of operators to ban them, or make as preferred |
APN list | APN list is necessary for automatic activation and correct device behavior | |
SMS service number | Phone number of technical team to get replies from SMS commands to | |
Telemetry server | MQTT security | Settings of authorization, and encryption |
MQTT broker address | Address where telemetry data will be sent | |
MQTT session parameters | Keep alive intervals, session time, etc. | |
MQTT topic names | Topic names to request data | |
NTP server | NTP server settings | Domain and enabling of NTP server |
2. Hardware.
This part controls all peripherals of the unit (f.e. Outputs, 1-wire, CAN, GNSS).
Category | Subcategory | Description |
|---|---|---|
Outputs | OUT settings | Set a way of output control - by script, or remote commands |
Digital inputs threshold | Inputs threshold settings | Voltage, from which inputs will get On |
GNSS | GNSS settings | Source, behavior and minimum quality requirements for GNSS |
Wiegand26 | Wiegand26 settings | Control of Wiegand interface |
CAN | CAN function ID setting | Setting reading of CAN interface |
Vehicle model | CAN program to read from CAN Database | |
1-wire | 1-wire settings | Control of 1-Wire interface |
LED | LED settings | Selecting a source of LED flashes |
Battery charging | Battery charging settings | Current to charge internal battery |
3. Data Recording.
This part controls parameter registration rules (which parameters will be included into packet).
Category | Description |
|---|---|
Simple | Here you can create a data packets, which will be triggered from chosen conditions. |
Extended | Here you can create sensors, which can trigger from chosen conditions, time, or threshold of sensor value. |
Note. Simple and Extended options can not be used simultaneously. If you set both - device would not send any data.
Check more about differences and configuration here: Data recording methods.
4. Script.
This part is Script manager (assign already released script). Maximum scripts to be assigned is 3.
Here you can assign scripts, which you have created and released. Also scripts, created by Xirgo team. By default we provide for free LLS script to read fuel level sensors via RS232 or RS485 and Common script (to control outputs, timers, static signals, identification, speed, eco-driving and more).
5. Deep Sleep.
This part controls "sleep" mode of the unit (energy saving mode).
In chosen conditions device can go into sleep mode by disabling all interfaces and processes inside the device. It will let to reach consumption <8 mA.
More about configuration of this option: Sleep mode configuration.
6. Identification.
This part lets to assign already created ID lists to a template.
Later you can use it to create immobilization functionality with f.e. Common script.
7. Geofencing.
This part is geozone group manager (assign already imported geozone groups).
Later you can use it to create speed notifications functionality with f.e. Common script.
8. Miscellaneous.
This part controls all settings related to device connections to servers.
Category | Subcategory | Description |
|---|---|---|
Fuel level averaging | Averaging state | Enables additional CAN fuel level approximation |
Crash detection | Crash detection settings | Setting to trigger an impact notification (IN15) based on G powers and time |
Event logging | Device event logging | Enable/disable of debug messages (events) send |
Tachograph settings | Text data requests | Lets to create additional text data requests from tachograph (do not forget to add parameters to “Data recording” |
DDD file settings | Let’s to set count of days in DDD file | |
Numeric data requests | Lets to create additional numeric data requests from tachograph (do not forget to add parameters to “Data recording” | |
Tacho file server | Here you need to set authentication and DDD file download addresses | |
Virtual input voltage threshold | IN8 | Let’s to set from which voltage will IN8 (power detection) get On |
Function keys | Function access keys | Function key to unlock device access to ISOBUS line |