Satellite Vehicle Tracker
Satellite vehicle tracker driver is used to monitor and control various GPS/GLONASS tracker devices using a generic vendor-agnostic approach. The driver allows to employ flexible rules for tracker message parsing.
Driver Information
Driver Plugin ID: | com.tibbo.linkserver.plugin.device.tracker |
Global Settings
The driver global configuration comprises Tracker Communications and Data Processing Configuration table:
Field | Description | |
Type | Identifier of the tracker type, can only contain English letters, numbers and underscore. The type is selected for each particular device in its account settings. | |
Description | Human-friendly description of the tracker type. The type is selected for each particular device in its account settings. | |
Protocol | Protocol(s) that trackers of this type use for server communications: TCP, UDP, or Both. | |
TCP Connection Port | Port to listen for incoming TCP connections from trackers of this type. | |
UDP Connection Port | Port to listen for incoming UDP connections from trackers of this type. | |
Message Separator | Character or string that separates individual tracker messages in a TCP stream. In UDP, each message is usually sent in a separate datagram, however, multiple message per datagram are also supported. | |
Parsing Rules | Rules used for parsing tracker message string into a Data Table. A table that defines a sequential rule set that should result in a table. Expressions of the rule set should refer A resulting table returned by the rule set should contain raw values for Device Identifier (usually IMEI number), type of the tracker message, and message parameters (e.g. latitude and longitude). | |
Device ID Expression | An expression that should return a Device Identifier unique within a Iotellect Server installation. Usually, tracker's IMEI number is used as the identifier. This ID will be used to find a matching device account that has the same ID defined in its properties. All remaining message data will be associated with this device account. | |
Device ID Expression Resolution Environment | ||
|---|---|---|
None. | ||
Table returned by Parsing Rules. | ||
0 | ||
Standard variables only. | ||
Variable Name Expression | An expression that should return a name of a device setting variable that will hold data of this tracker message. It usually refers type of the tracker message. | |
Variable Name Expression Resolution Environment | ||
Context of the tracker device. | ||
Table returned by Parsing Rules. | ||
0 | ||
Standard variables only. | ||
Device Variables | A table defining device setting variables that will be added to each device account using this tracker Type. Each variable is defined by:
If a certain variable's format doesn't define any fields, it's deemed dynamic and any data table returned by Parsing Rules will be used as a valid variable's value. | |
Latitude Expression | Once Type of a tracker device account is defined of changed, this expression is written into Latitude Expression field of Generic Device Properties. It is further used for evaluating device latitude, so it normally refers to one of Device Variables. | |
Longitude Expression | Similarly to the above, re-defines device account's Longitude Expression once a tracker type is changed. | |
User Level Settings
None defined.
Device Account Properties
Type. Tracker type, one of the types defined in Tracker Communications and Data Processing Configuration global configuration table.
Device ID. Unique identifier of the tracker, usually its IMEI number. This ID should be received in each tracker command.
Offline Status Delay. If no messages were received from the tracker for longer than that time, the tracker device account will be switched to Offline mode.
Device Assets
Assets are not supported by the driver.
Device Settings
Satellite tracker device account will expose one variable per each record of Device Variables subtable contained in Tracker Communications and Data Processing Configuration table's record matching selected tracker type.
Variable names, descriptions and formats are defined in Device Variables table.
Device Operations
No operations provided by the driver.
Device Events
No events provided by the driver.
Connection Handling
This driver makes the device Online if any message is received and successfully associated with this tracker account, i.e. one of Device Variables is successfully updated.
The device switches back to Offline mode if no associated messages were received for longer than Offline Status Delay.
Synchronization Details
This driver doesn't perform a regular device synchronization. Instead, it follows the below pattern:
Driver listens to each port defined in Tracker Communications and Data Processing Configuration.
Once a TCP connection is accepted or a UDP datagram is received, it splits incoming data into messages using Message Separator.
Once a complete message received, the driver processes Parsing Rules to form a command table. If rule processing fails, an error is logged within the global configuration context of the Satellite Vehicle Tracker driver.
The command table is evaluated by Device ID Expression.
Driver tries to find a device account which Device ID matches ID returned by the above expression. If it fails, an error is logged within the global configuration context of the Satellite Vehicle Tracker driver and message processing is aborted.
Driver evaluates Variable Name Expression to figure out that device setting variable should be updated using command table. If this expression returns null or incorrect name, processing is aborted and error is logged within the device account context.
Command table is used as a new value for the detected variable, i.e. written into tracker's device account.
Was this page helpful?