Device
On the Device tab you can create custom commands for tracking devices and map signals between devices and system variables.
The following sections are available:
Device protocol listeners
The Listeners menu shows the current state of the protocol listeners installed on the server. Every device type has one listener for each supported transport method (e.g. TCP/IP, UDP, http, SMS).
If you are missing listeners for a device you can look for additional listeners on the Plugins tab.
The table has the following fields:
| Description | Description of the listener with device type and transport method |
| Port | The port number that the listener is configured to |
| Connections | The number of devices currently connected to the listener |
| Unknown Devices | Column is visible when an unknown device has tried to connect to the server during the last week. You can assign the unknown device to a new user in an existing application. |
| Public Access | Shows if the server can be accessed from the Internet on the specified port. The status shows the last connection test |
| Test | Click Test button to perform a connection test from the Internet. The test simulates a connecting device |
| Last Tested | Shows the time stamp for the last connection test |
| Start / Stop | Click on Start to start the listener Click on Stop to stop the listener |
| Edit | Click on Edit to change the port number for the listener |
Firewall trouble shooting tips
The two main problems with failing connection tests are Firewalls and Port forwarding. You find a short explanation below, please contact your network administrator or consult the Internet if this is not enough.
Firewall
If you have a Firewall on your server you need to open a port to allow incoming traffic from your tracking devices. You should for example allow incoming TCP/IP traffic on port 30175 to support software client connections. It is good practice not to open more ports than you need.
Port forwarding
If you have a network router between your server and the Internet you will have to forward the incoming traffic from the router to your server. Configure your router to send the incoming traffic on the specific port number to your server. You should for example forward incoming TCP/IP traffic on port 30175 to the local IP address of your server.
It is the router that has the Public IP address shown by your server (your server has another local IP address). When your tracking devices send data to the Public IP address Port forwarding is used to forward the data to your servers local IP address.
Note:The Router may also have a firewall that you have to configure to allow the incoming traffic.
Commands
The Commands section enables you to create custom commands for tracking devices. You can create multi step commands to send many messages to a device as a single command. You can use template variables and conditional formatting to make your commands suit different device protocols.
Command
The Command table has the following fields:
| Protocol | The drop down list contains all the different device protocols supported on the server |
| Commands | The drop-down list shows the available commands. Select a command in the list to edit it or select New... to create a new one |
| Rights | You can select if only administrators should be allowed to send a command, or if it should be available for all users |
| Device Types | For every device protocol the available devices are listed here. You can select which of the devices a specific commands should be available for |
| Save / Delete | Use the Save Command and Delete Command buttons to save or delete a command |
Note: When you edit a command you can add steps to it to enable the sending of multiple messages as a single command.
Template Variables
Use the template variables to include system information, such as the server IP address and device phone number, in your commands. You can also use formatting variables and conditional evaluation in your commands to suit different device protocols.
Types
The Types section lets you create configurations for your device types. For a device type you can map device signals to system variables and select what commands to activate. One configuration is saved as a device type instance.
Tip: You can create multiple instances for a device type if you need different configurations for one device model. This enables you to activate different commands and map signals separately for different vehicles even if they have similar devices.
Device Type
The Device type drop-down lists all the device types activated in the system. Select the device type you want to work with from the list.
Tip: If you can not find your device type in the list the listener for that device type might be stopped. You can start listeners under the Service tab. You can also check for additional listeners and download them under the Plugins tab.
Instance
When working with instances you have the following options:
- Select the instance for a device type that you want to work with from the drop-down list
- Click on New to add a new instance
- Click on Import... to import an instance definition from a template file
- Click on Display Devices to list the devices in your system that are using the instance currently selected in the drop-down list
Create/Update
Add a name and description for your device type instance. Use a descriptive name, it is used when you select device mappers in the application.
Supported Commands
Select the commands you want to activate for the device mapper instance.
Tip: You can add your own commands under the Commands tab.
Device Mapper Template
The device mapper template is used to map device signals to system variables.
The template contains the following fields:
| Enabled | Check the box to enable the variable. |
| Input | This is the device specific name for the Input/Output variable |
| Type | The variable type can either be boolean (true/false), double (a decimal number) or String (a text) |
| Output | This is the generic system variable that the device is mapped to Note: these variables are used in the system for Event Rules, Reports, etc. |
| Multiplicator | A multiplicator can be inserted to calibrate the input variable. For example to double the input value you enter 2 as the multiplicator |
| Constant | A constant is used to calibrate an offset. For example to increase all input values with 3 you enter 3 here. |
| Unit | This is the unit for the system variable. The unit field is shown when you have selected a system variable |
You can Save, Copy..., Export... and Delete a device type instance.