<< Click to Display Table of Contents >>

Navigation:  Program use > Configuration > Modules > Tracker data redirection >


In the Data redirection module’s configuration window (Fig. 1):


1.Select the format.

2.Specify the IP address and port of the server the data will be redirected to.

Match the variables in the parser with the respective fields in the data packet to be sent to the target server.



Fig.1. Configuration window




Formats – select one or several formats. Individual settings will be used for each format. To activate a redirection in the required format, select the checkbox by the format name. To modify redirection settings for the required format, click and select it on the list.


Target server – specify the connection string for the required server. In this field, you can specify several target servers, separating them with a semicolon.


TCP – use the format (IP address followed by the colon and the port number). Multiple servers:;

UDP - udp://




New connection for each tracker – the module emulates a real tracker by creating a new connection to the target server for each tracker. That increases CPU load but also improves compatibility, as not all target servers accept data from multiple trackers through the same connection.


Maximum number of connections – here you can limit the maximum number of connections to the target server. It is recommended to specify the limit value exceeding the number of working trackers by 20%. That way, the module will have enough time to transmit the live data being received from the trackers and restore the backed-up data from the archive in case of transmission failure.


Backup data packets to folder if unable to send – should any problems occur while transmitting data to the target server, the module will create temporary data files. When the connection is restored, it will both transmit the live data and restore the backed-up data.


Please note that in this case the chronology of the data transmission can be breached. Some target servers may be sensitive to the sequence of the data flow.


The module makes only five attempts to transmit data from the backup. Therefore, data loss is probable when the target server remains unavailable for too long.


Log responses from target server – this option may be useful when configuring or troubleshooting a connection to the target server. In the log files, you can view the server’s replies to the packets sent to it and, for instance, find out why the target server does not accept the data.




On this tab (Fig. 2) you can match up the variables in the parser with the items in the new data packet in the selected format.



Fig.2. Matching variables


Please note that not all source data can be redirected to another server. In general, the redirection works only for the common telematic data (date, time, coordinates, speed).


By default, the redirection module is configured to transmit as much data as possible; however, you can change the content of the data to be transmitted by modifying the correspondence of the variables.


Data packet item – contains the list of all possible items in the new data packet.


Parser item name – specify the name of the parser variable, the value of which will be used when forming the data packet.


Use default value – if the source packet doesn’t have a variable with the specified name, the module will use the default value when forming the new data packet.


If there is no variable in the source packet, and the default value is not set, the new packet too will not have the respective value. If the target format does not allow skipping values, the program will add a zero, empty string or FALSE (depending on the field’s data type).


Scale analog values – the module can proportionally recalculate the source value into a new one. For instance, if in a new data packet, the value is an integer between 0 and 4096, the source value is 10, the minimum is 0, and the maximum is 100, the new value in the packet will be 4096 * 10 / 100 = 409.


Table 1 lists the fields and their data types, which the module expects to receive from the parser. When matching up the values, you should keep in mind that the redirection module expects to receive data from the parser or the data filtration modules in the specified format. When matching up the values, the module can automatically convert their data types as follows:


Float into integer by discarding the fractional part;

Integer into float;

Number into string;

String into number;

Number into a logical value (0 – logical FALSE, any other value – logical TRUE).


Data packet field

Data type




Device identifier (number, IMEI, etc.)

Date and Time





In the GPS format; e.g., 48.71514



In the GPS format; e.g., 48.71514

Height (m)


In meters above the sea level



Angle 0-360 degrees






Travel distance, km

Relay 1-8


Status of relay 1-8

Sensor 1-8


Status of sensor 1-8

ADC 1-4


Value of ADC 1-4

Voltage 1-2


Voltage in Volts in the range between 0 and 25.5



Number of satellites (0 – 14)



GSM signal level (0-5)

T int.

Signed byte

Internal temperature (degrees) from -127 to 127

T ext.

Signed byte

External temperature (degrees) from -127 to 127

Fuel 1-2


Value of fuel sensor 1-2

Engine hours 1-2


Value of engine hours 1-2

Alarm indication

Logical or numeric

0 or False – no alarm indication; otherwise, an alarm indication is present.




On this tab (Fig. 3) you can set up filters for trackers redirection is enabled for. The identifiers can be set in the module settings. You can also specify a name for the external text file.


If the text file name is specified, the module will check it occasionally and refresh the list in the memory when the file gets modified.


When the option "Filter out specified IDs" is enabled, the redirection will be enabled for all trackers except for listed in the table.


When the option "Redirect specified IDs only" is enabled, the redirection will be enabled only for trackers listed in the table.



Fig.3. Filter settings




This tab provides brief performance statistics for the entire module (list of active and inactive connections). This data can be used for troubleshooting and obtaining information on the load of the redirection module. When the load is low, you can reduce the number of simultaneous connections and thus save CPU resources. Alternatively, the other way around, increase the number of connections if the outgoing queue is large.