AWCSL TRACX
AWCSL TRACX
Table of Contents
Introduction.......................................................................................................................................................................................................5
In Brief............................................................................................................................................................................................................5
Features.........................................................................................................................................................................................................5
Features in detail.....................................................................................................................................................................................5
Receiving GPS positions............................................................................................................................................................................6
Directly..........................................................................................................................................................................................................6
Via TRICX Radio-Interface gateway............................................................................................................................................6
Via Hytera Gateway/DDC controller.........................................................................................................................................7
Supported browsers....................................................................................................................................................................................7
Logging in to the TRACX.........................................................................................................................................................................7
User account levels................................................................................................................................................................................7
Logging into the TRACX system...................................................................................................................................................7
Default TRACX account....................................................................................................................................................................8
Using TRACX..................................................................................................................................................................................................9
Introduction................................................................................................................................................................................................9
Overview of main screen................................................................................................................................................................10
Main menu icons..................................................................................................................................................................................11
Map navigation menu........................................................................................................................................................................11
Map following modes........................................................................................................................................................................13
Manual..................................................................................................................................................................................................13
Follow currently selected device..........................................................................................................................................13
Follow most recently updated device...............................................................................................................................13
Options menu icons...........................................................................................................................................................................13
Interacting with markers...................................................................................................................................................................14
Information shown in device pop up................................................................................................................................14
Device Pop-up icons...................................................................................................................................................................15
Quick history trail.................................................................................................................................................................................15
Map layers.................................................................................................................................................................................................16
Overview map.......................................................................................................................................................................................17
Searching for devices.........................................................................................................................................................................17
Showing currently active devices................................................................................................................................................18
Jumping to a predefined location...............................................................................................................................................19
Searching for an address..................................................................................................................................................................20
Alarms.........................................................................................................................................................................................................21
Administration overview........................................................................................................................................................................22
Definitions and terms........................................................................................................................................................................22
Fleet.......................................................................................................................................................................................................22
Device..................................................................................................................................................................................................22
Subfleet................................................................................................................................................................................................23
Event Rules........................................................................................................................................................................................23
Network device links...................................................................................................................................................................23
Incoming connections.................................................................................................................................................................23
Connection groups.......................................................................................................................................................................23
Alert sounds.....................................................................................................................................................................................23
Marker..................................................................................................................................................................................................23
User.......................................................................................................................................................................................................23
Fleet Admin......................................................................................................................................................................................24
System admin...................................................................................................................................................................................24
Overview..................................................................................................................................................................................................24
Accessing the administration menu.................................................................................................................................................24
Device administration...............................................................................................................................................................................25
the device administration menu..................................................................................................................................................25
Device ID..................................................................................................................................................................................................26
How a device is identified by the TRACX server............................................................................................................26
messages from a radio device................................................................................................................................................26
Messages received from a GSM/GPRS tracker or mobile device....................................................................27
Adding a new device..........................................................................................................................................................................27
Automatically added devices.........................................................................................................................................................28
Importing device list from a file...................................................................................................................................................28
Exporting device list to a file.........................................................................................................................................................28
Connecting to GPS sources.................................................................................................................................................................28
Network device links.........................................................................................................................................................................29
Adding a new device...................................................................................................................................................................30
Channel groups.....................................................................................................................................................................................31
Channel sources...................................................................................................................................................................................31
Example configuration.......................................................................................................................................................................33
Fleet administration...................................................................................................................................................................................33
Creating Fleets.......................................................................................................................................................................................33
Assigning devices to fleets..............................................................................................................................................................34
Automatically assign devices to fleet using a Channel group.....................................................................................35
Assigning users to a fleet.................................................................................................................................................................35
Markers.............................................................................................................................................................................................................35
Marker defaults menu........................................................................................................................................................................35
Marker options for active GPS devices............................................................................................................................36
Marker options for invalid GPS fixes.................................................................................................................................36
Marker and timeout for inactive devices.........................................................................................................................37
Creating custom markers................................................................................................................................................................37
Anchor point....................................................................................................................................................................................38
Notes on marker creation..............................................................................................................................................................38
Deleting markers..................................................................................................................................................................................39
Status and text messaging......................................................................................................................................................................39
Text lookups...........................................................................................................................................................................................39
Status lookups........................................................................................................................................................................................39
Adding a new status value..............................................................................................................................................................40
Status ID....................................................................................................................................................................................................40
Events and actions......................................................................................................................................................................................41
Event Types.............................................................................................................................................................................................41
Action types............................................................................................................................................................................................41
Defining an event/Action.................................................................................................................................................................42
Rule name field...............................................................................................................................................................................42
Event fields.........................................................................................................................................................................................42
Action fields......................................................................................................................................................................................43
Places..................................................................................................................................................................................................................43
Categories................................................................................................................................................................................................43
Add new place.....................................................................................................................................................................................44
GSM/GPRS trackers..................................................................................................................................................................................45
TRACX tracker ports........................................................................................................................................................................45
GH3000 tracker configuration.....................................................................................................................................................46
FM12xx tracker configuration.......................................................................................................................................................46
Illustration Index
Illustration i: TRACX log-on screen....................................................................................................................................................8
Illustration ii: TRACX main screen - desktop...............................................................................................................................9
Illustration iii: TRACX main screen - mobile..............................................................................................................................10
Illustration iv: Annotated main TRACX screen........................................................................................................................10
Illustration v: Main screen with navigation submenu..............................................................................................................12
Illustration vi: Device pop-up...............................................................................................................................................................14
Illustration vii: Quick-history trail on map.....................................................................................................................................16
Illustration viii: Satellite view with map layer options visible.............................................................................................17
Illustration ix: Device search window.............................................................................................................................................18
Illustration x: Recently update device list......................................................................................................................................19
Illustration xi: My Places list...................................................................................................................................................................19
Illustration xii: Address search window.........................................................................................................................................20
Illustration xiii: Alarm icon shown.....................................................................................................................................................21
Illustration xiv: Current alarm list.......................................................................................................................................................22
Illustration xv: TRACX administration menu.............................................................................................................................24
Illustration xvi: Device administration menu...............................................................................................................................26
Illustration xvii: Add device dialogue...............................................................................................................................................27
Illustration xviii: Network device links menu..............................................................................................................................29
Illustration xix: Adding a new network device..........................................................................................................................30
Illustration xx: List of channel groups..............................................................................................................................................31
Illustration xxi: List of channel sources...........................................................................................................................................32
Illustration xxii: Adding new channel sources............................................................................................................................32
Illustration xxiii: Fleet administration menu.................................................................................................................................34
Illustration xxiv: Add/edit device popup.......................................................................................................................................35
Illustration xxv: Marker defaults menu...........................................................................................................................................36
Illustration xxvi: "Android mobile" marker selected...............................................................................................................36
Illustration xxvii: Create new marker dialogue..........................................................................................................................37
Illustration xxviii: Tower icon on different background colours......................................................................................38
Illustration xxix: Status menu showing status table................................................................................................................41
Illustration xxx: Event definition dialogue.....................................................................................................................................42
Illustration xxxi: Place menu.................................................................................................................................................................43
Illustration xxxii: Add new Place category...................................................................................................................................44
Introduction
In Brief
The TRACX application enables the near-real time tracking of GPS equipped vehicles, people and
assets. TRACX has the ability to track different radio types, including TETRA, DMR, MPT and
conventional, as well as smartphone devices meaning you can monitor any asset, anywhere
worldwide.
TRACX is a mapping server running a web server. This means that users can access AVL functions
through a standard browser, enabling AVL to be deployed anywhere with web access to the system.
This could be from a desktop computer, tablet or smart-phone.
Features
With the TRACX the user gets a clean, simple to use tracking application. You have the ability to
define custom map layers, this enables the customer to have maps to their required detail.
The TRACX has full text and status messaging capabilities for incoming and outgoing communication.
For safety critical users, it supports lone-worker, man down and emergency alarms with email alerting,
audio and visual alerts
A key feature of the TRACX is the ability to divide a system down into fleets and sub fleets. This
means that you could have several customers running on the same system with and they can only see
their devices. The TRACX is able to be installed on closed networks where data security is critical. As
the TRACX serves map tiles to the client there is no need for the server to access the internet in
order to view any maps.
However if internet access is available the TRACX will continually check to see if there are updates
available and if they are it will automatically download and update the map.
Features in detail
Track multiple device types in near-real time
•
•
•
•
•
•
•
•
•
•
•
TETRA-PEI
MPT (Simoco or any Map27-compatible radio via external GPS interface)
DMR Tier 2 (Simoco, Hytera, Kenwood dPMR)
DMR AIS
Kenwood Fleetsync
GPS-enabled smartphone tracking
Web-based application compatible with desktop and tablet PC’s
Offline mapping options for closed networks
Custom mapping styles
Auto-update mapping
Online mapping options
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
Lone worker, man down, emergency alarms
Full messaging interface for text and status messaging
Geofencing
Customizable map marker icons for devices, status and alarms
Triggerable actions in response to events
All data archived indefinitely
Data backup to NAS device for off-site backup
Configurable audio alerts
Email alerting for GPS events/alarms
System dividable into fleets to support multiple user groups on a single installation of TRCX
Favourite places list for quick jumping to pre-defined map locations
Search for locations by address, place name, etc.
Data export and reporting
Quick-view GPS trails in real time from map interface
Location accuracy estimates shown for equipped devices (smartphone)
Flexible APIs allow easy integration with 3rd party applications.
Receiving GPS positions
Currently, the TRACX server can receive position updates via a number of routes.
Directly
The following connections are handled directly via the TRACX server:
•
Smart-phone connection
•
Supported GSM/GPRS tracker devices
•
Simoco tier 2 DMR repeater
Via TRICX Radio-Interface gateway
The following connections are handled via a connected TRICX radio gateway interface server:
•
MotoTRBO DMR
•
MPT networks
•
◦
Simoco MPT
◦
AWCSL GPS interface gateways
TETRA
◦
Sepura GPS
•
Kenwood fleetsync/dPMR
•
DMR Tier 3 AIS
Via Hytera Gateway/DDC controller
The AWCSL Hytera gateway and DDC desktop controller products can supply GPS position
information to a TRACX server.
Supported browsers
OS
Microsoft Windows
Browser
Supported version
7
Mozilla Firefox
Latest 2 + LTS
8.1
Google Chrome
Latest 2 versions
Internet Explorer
IE 10
IE 11
Mozilla Firefox
Versions supported by
Canonical
Google Chrome
Android 4.3+
(Samsung Galaxy S4
Google Nexus 5
Google Nexus 7)
Safari
iPhone 4+
iPad 2+
?
?
Ubuntu Linux
Android
?
iPad/iPhone
Mac OS X
?
Logging in to the TRACX
User account levels
There are three access levels for user accounts:
Level
Description
User
Standard system users. Each user account is assigned to a specific fleet.
Users can see devices only for this fleet.
Fleet Admin
An administrator for a specifc fleet. These accounts can add and remove
devices for their fleet, and add or remove standard user accounts for their
fleet.
System Admin
System administrators have full access to the TRACX system settings. They
can add/remove devices and users for all fleets and create and remove fleets
and device link settings.
Logging into the TRACX system
To connect to the system, open a supported web browser and navigate to the TRACX server's
address. Unless otherwise configured, this will be the IP address of the server, i.e.
http://192.168.1.24
The TRACX log on screen should be loaded:
Enter username and password and press the “sign-in” button.
Default TRACX account
When supplied, the TRACX has a single Admin user account. The default username and password
are:
Username:
admin
Password:
admin
For security reasons, the default password should be changed before the
system is opened to users, especially if the server is visible on the internet.
The TRACX username and password are not the same as the username
and password for the TRACX server's Linux operating system.
Using TRACX
Introduction
Once a user is logged in, the main TRACX mapping window is shown. This shows a map with
location markers for active devices and a number of controls.
Illustration ii: TRACX main screen - desktop
Overview of main screen
Zoom
Zoomcontrols
controls
Status
Statusinfo
info
Main
Maincontrols
controls
Map
Maplayers
layers
Device
Devicemarker
marker
Overview
Overviewmap
map
Map
Mapscale
scale
Main menu icons
The following icons are shown in the main menu bar.
Icon
Purpose
Open the device search window.
Show map navigation menu. Hover (or tap on phone/tablet) on this icon to show the
map navigation menu.
Open inbox.
Show recently active devices window.
Show options menu. Hover/tap on this icon to show further options menu.
Map navigation menu
This menu is shown by hovering (or tapping) the navigation menu icon.
Icon
Purpose
Jump to place. Shows a searchable list of the pre-defined locations.
Clicking “Jump To” next to a place will move the map to this location.
Opens address search window. This feature requires the TRACX server to have an active
internet connection.
Jump to latitude/longitude. Allows manual entering of lat/lng coordinates to jump to.
Jump to your location. This will use the current web browsers geo-location feature to find
your current position and centre the map on this position. The web browser may prompt
you for permission to access your current location.
This is most useful on GPS equipped devices using the TRACX software to see nearby
features.
Keep map centred at current location. The map will no longer follow a selected device or
jump to the most recent GPS update.
Jump to selected device. If a device is currently selected, centre the map on that device.
Jump to most recent update. The map will automatically relocate to the device which most
recently sent a GPS update.
Map following modes
The map can automatically move its location depending on the currently selected mode. There are
three modes for map following.
Manual
In this mode, the map will not move automatically.
This is the default state for the map unless a device is selected or the “jump to most recent update”
icon is clicked.
Follow currently selected device
In this mode, the map will automatically be centred on the location of the currently selected device
whenever it sends in a new GPS position update.
The map can still be manually moved, but will automatically recentre on the selected device when it
posts a new position update.
Follow most recently updated device
In this mode, the map will automatically centre on the GPS device which has most recently sent a
GPS update. This mode is entered by clicking the “jump to most recent update” icon.
Options menu icons
The options menu is shown by hovering over (or tapping) the “show options menu” icon.
Icon
Purpose
Show name tags. Name labels will always be shown next to map markers.
Hide name tags. No name labels will be shown.
Show name tags on mouse hover. Only show the name tag for a device when hovering
over its map marker.
Go full screen.
Go to settings menu.
Log out.
Interacting with markers
Clicking or tapping a device marker icon on the map will open a pop-up with more information and
options for a specific radio.
Information shown in device pop up
Direction
Directionof
oftravel
travel
Device
Devicename
name
Close
Closepop
popup
up
Update
Updatetime
time
GPS
GPSaccuracy
accuracyestimate
estimate
The pop up window shows some details about the current state of the device:
Item
Description
Direction of travel
Shows a marker showing the current direction of travel.
If device is stationary or the direction of travel is unknown, a circle icon
is shown.
Device name
The name of this device
Update time
Time since the last GPS position for this device
GPS accuracy estimate
Circle which shows the GPS margin of error for this fix. Only shown for
devices which support GPS accuracy estimates.
Invalid fix
Shown if the last GPS update from this device did not have a valid GPS
fix. This means that the device is still active but doesn't currently know
its location.
Device Pop-up icons
There are a number of icons for interacting with a device. Some icons may not be shown depending
on the configuration of the TRACX system.
Icon
Purpose
Follow this device. The map will be centred on this device and will move to the device
after each GPS update from it.
Show quick history trail. Opens a quick interactive history trail for this device.
Detailed history list. Open a detailed list of GPS updates sent by this device.
Show street image. Loads a photo taken from the point of view of the device. Requires
internet connection.
Send message to this device.
Open the inbox for this device.
Quick history trail
To show the quick history trail for a device, click the
open the quick history line for this device.
icon in the device popup menu. This will
Illustration vii: Quick-history trail on map
A line showing the trail that the device has taken up to its current position. Moving the time slider
will change the duration of the GPS trail shown.
It is possible to show history trails for multiple devices at a single time – clicking the trail icon for a
new device does not close the trail of another device if it is already shown.
If a trail line is left open, the trail will automatically grow as the device moves around.
To close all of the open trail lines, click or tap the “close” button by the time slider.
Map layers
The TRACX server is supplied with its own map generation software which generates the map
images. This map is based on data from the OpenStreetMap project.
It is possible to configure alternative mapping sources (for example, satellite imagery, OS maps, other
web map sources) – the available mapping sources will depend on the configuration of the TRACX
server.
To change between map sources, click the layer chooser icon:
be displayed – click one to choose.
. A list of available map sources will
Overview map
A smaller overview map is shown in the bottom-right corner of the window. To hide the overview
map, click the arrow icon shown on the overview map .
To show the overview map when hidden, click the expand arrow.
The overview map is not shown on mobiles.
Searching for devices
To search for a device, click the device search icon in the main controls
search window:
. This will open the device
Devices can be searched either by name or number. The search results will update automatically as
the search term is entered.
Clicking the “follow” button will jump to the location of this device on the map and enter the device
following mode.
Showing currently active devices
To show a list of devices which have sent a GPS update recently, click the recently active devices icon
in the main controls
There is a time slider control. Adjusting this will include all devices which have sent a GPS update in
this time range. The list will automatically update.
Jumping to a predefined location
It is possible to define a list of favourite locations for quick navigation to set points. To access this list,
click the “Jump to place” icon .
Illustration xi: My Places list
To search for a place, enter a search term in the text box. The results list will be updated in real
time. Both place name and description are searched.
Searching for an address
To search for an address, open the navigation sub-menu and click the search icon:
the address search window:
. This will open
Enter a search term and click or tap the search icon. This search does not update automatically – you
must press the search icon to start searching.
The search term can consist of street name, town, city, county, region, state or country. Addresses
should be specified left-to-right, for example
1 Merchant's Drive, Carlisle
Alarms
Depending on system configuration, some radios and devices can trigger alarms within the TRACX.
When an alarm is triggered, a large alert icon is shown in the bottom-left corner of the display. This
icon will remain on the screen until all outstanding alarms are acknowledged.
Clicking this icon will bring up a list of all of the current alarms:
Clicking “Clear Alarm” will acknowledge this alarm. The TRACX system stores which user
acknowledged each alarm.
Once there are no outstanding alarms, the alert icon will disappear from all users' screens.
Administration overview
Definitions and terms
Fleet
Fleets are used to subdivide a single TRACX server into multiple, distinct systems – i.e. to provide a
TRACX service to multiple customers.
Any GPS device will belong only to a single fleet, and standard users can only access resources which
are part of their assigned fleet.
Device
A GPS equipped device for tracking – i.e. mobile radio, smart-phone or dedicated tracker unit. Each
device belongs to a specific fleet.
Devices are identified by their radio ID and the connection group which receives a GPS message.
Subfleet
Used to divide a single fleet into separate units. For example, a fleet which belongs to a council user
may have separate subfleets for refuse vehicles, maintenance units, etc.
Event Rules
Event rules are used to trigger custom actions in respose to events which are received by the system.
Examples of an event include receiving a text or status message and receiving an alarm from a radio.
Network device links
Network device links define external server devices which the TRACX server is connected to for
receiving and sending GPS, text and status messages.
These external device types include TRICX server, Hytera gateway, Simoco T2 gateway, etc.
Incoming connections
Incoming connections define individual sources of GPS or message data, for example, a single TRip
unit connected to a TRICX server.
Connection groups
A connection group defines a group of incoming connections – for example, a number of TRip units.
Connection groups are used to uniquely identify different radio devices. A radio with ID “123” in
connection group A is considered to be a different device than a radio with ID “123” in connection
group B.
There is a default (null) connection group – any device which is not assigned to a different connection
group is automatically considered to be part of the null group.
GSM/GPRS tracker devices and mobile phones are always in the null group.
Alert sounds
An alert sound is a sound file which can be played in response to a system event.
Marker
Markers are the icons shown on the map to represent the position of a device. Custom map markers
for devices can be defined – the TRACX has an extensive icon library for map markers.
User
An account associated with the human who will be logging into and using the TRACX server.
Fleet Admin
A fleet admin only has access rights for a single fleet on the system. These users can add/remove
devices and make changes to settings only for their fleet.
System admin
A system admin has access to all fleets on the system. They can add and remove fleets and all types
of user accounts, as well as adding and removing devices to any fleet. They can access all settings on
the system.
Overview
The TRACX server is designed to support GPS position data from multiple sources – multiple radio
protocols, smart-phone applications and multiple GPS tracker units. It supports multiple distinct user
groups on a single server instance.
To allow this, the TRACX is divided into fleets. Each fleet is completely independent from the other
fleets on the system. Each user only has access to a single fleet. All devices belong to a single fleet.
This allows the TRACX to be sub-divided between multiple customers, for example.
In addition to receiving GPS updates, it can receive incoming text and status messages from a number
of sources.
Accessing the administration menu
To access administration settings, log into the system as a full system admin user. Access the settings
by hovering over (or tapping) the options menu icon ( ) and then clicking or tapping the settings
icon ( ).
Access sub menus by clicking the items on the left-hand menu. The available menus are:
Overview
GPS devices
Add, edit and remove GPS devices from the system
Icons and markers
Create custom map markers
Marker defaults
Set the default markers for GPS devices
Places
Define a set of predefined locations for quick navigation
Status
Associate text messages with incoming status numbering
Event rules
Create actions in response to triggered events
Alert sounds
Upload sounds for playing in response to event rules
Fleets
Create fleets for subdivision of the TRACX server
Sub fleets
Sub-divide fleets into logical sub units
Network device links
Configure links to external servers and gateways
Incoming connections
Define GPS receiver sources (i.e. TRip units) and collect them into
groups
User administration
Add, edit and remove users
Change password
Device administration
the device administration menu
The device administration menu shows a list of the devices defined in the system. The table shows
the following columns:
Column
Description
No header
The custom marker for this device
#
The DeviceID for this device
Name
Name
Number
Radio ID for this device
Channel group
The channel connection group that this device belongs to. If the device is in the
null group, this will be blank
Fleet
Fleet the device belongs to
Sub fleet
Auto added
Shows a tick if this device was automatically added to the TRACX system
Clicking the header of any column will sort the table.
Device ID
Each device has a unique ID number which identifies it in the TRACX database. This number is
automatically generated by the system and isn't related to the radio ID or telephone number of the
device.
The maximum device ID is 18,446,744,073,709,551,615.
How a device is identified by the TRACX server
On receipt of a GPS update or message, the TRACX works out the device ID for the update using
two methods, depending on the source of the message.
messages from a radio device
For a GPS or message received from a radio, the radio ID is not sufficient to uniquely identify a
device. Particularly when supporting multiple customers with distinct radio networks, or a
combination of radio protocols.
The TRACX uses a combination of channel connection group and radio ID to work out the device
ID1.
Messages received from a GSM/GPRS tracker or mobile device
Mobile phones and GSM/GPRS tracker devices always belong to the null channel group. Devices are
identified either by phone number, IMEI2 number or Username depending on the type of device.
1
2
See section on channel connection groups for more information on how radio numbers are associated with device
IDs.
IMEI numbers currently must be added manually to the TRACX database. User interface for this will be in a later
software update
Adding a new device
The following items are required when adding a new device:
Device name: Display name for the device. Shown on the map marker for this device.
Device number:
•
For radios, the over-the-air ID of the radio.
•
For mobiles using the web-based mobile.php tracker, this should be the Username entered in
the device.
•
For trackers identified by mobile phone number, this should be the devices number.
•
For trackers identified by IMEI, this should also be the mobile phone number. The IMEI is
entered separately.
Group: Channel group that this device will send GPS updates to.
Fleet: Fleet that this device belongs to.
Marker: Optional custom marker to show on map for this device.
Automatically added devices
If a GPS update (or status/text message) is received from a device which is not already in the TRACX
devices table, it will be added automatically.
If the update arrives on a known channel source (that is, a channel source which is a member of a
channel group, defined on the “Incoming connections” menu), then the new device will be named in
the following format:
GroupName RadioNumber
For example, a GPS update from radio 201 on a TRICX channel which is a member of a channel
group called “MPT” will become
MPT 201
In this instance, the device will automatically be assigned to the default fleet associated with this
channel group.
If the update comes in on an undefined channel endpoint or is received directly from a mobile device,
then only the number will be used. In this case, the fleet can't be automatically determined; the
device will be assigned to the first available fleet.
There is a column in the GPS devices menu which shows which devices were automatically added to
the system.
Importing device list from a file
This feature is currently unavailable. It will be restored in a future software version.
Exporting device list to a file
This feature is currently unavailable. It will be implemented in a future software version.
Connecting to GPS sources
This chapter covers connection to GPS sources – for example, connecting to a TRICX server linked
to a GPS-receiving radio.
A channel connection group is a collection of individual channel sources where a channel source is an
endpoint – a single specific entry point – to the TRACX system. An example of a channel source is a
TRip unit connected to a TRICX server.
Each channel source is identified by its channel number and the gateway device it is connected to.
For example, trip_number:=7 on a TRICX called TRICX2012 is identified uniquely as TRICX2012:7.
This differentiates this from trip_number:=7 on a different TRICX system.
Network device links
The network device links menu configures external network devices which can send GPS, text and
status messages to the TRACX server.
The possible network devices are:
Network device type
Description
TRICX
A TRICX server – either TRICX, TRICX-lite or TRICX-microLite
Hytera Gateway
AWCSL Hytera Tier II gateway or DDC-1/2 controller for Hytera
GSM modem
Not currently implemented
Simoco T2 gateway
AWCSL Simoco Tier II gateway
MPT gateway
Not currently implemented
Configuring attached servers and devices lets the TRACX server correctly establish where an
incoming GPS message is received from. It will also allow for sending text and status messages and
GPS poll messages (where supported) in future iterations of the TRACX software.
Adding a new device
Click the “Add connection” button.
Link description: A descriptive name for this network device.
Device name: A unique name for a network device. This field is used to distinguish between
different servers sending data to the TRACX server. This name is supplied when sending a GPS
update to the TRACX server. It is a configurable item in the TRICX server – see section on
configuring TRICX for GPS.
Device type: Class of connected device.
Link type: TCP/IP or serial. For most links, TCP/IP is the only valid option. GSM modems will be
connectable via either TCP/IP or a serial link.
Device address: Address of the device. The address format depends on the device type:
Device type
Address
format
Example
TRICX
IP:PORT
192.168.1.100:49980 TRICX comms port is usually 49980
Hytera T2 gateway
IP
192.168.1.100
GSM modem (TCP/IP)
IP:PORT
192.168.1.100:12345
GMS modem (serial)
Serial port path /dev/ttyS0
Simoco T2 gateway
IP:PORT
192.168.1.100
Notes
Linux file path for the serial device
Channel groups
Channel groups define logical groups of GPS sources channels:
•
A GPS update received from radio ID 123 on any channel source in group A is considered to
be from the same device.
•
A GPS update received from radio 123 on a channel source outside of group A is considered
to be from a different device.
This distinction allows the TRACX server to support multiple radio fleets which may have overlapping
radio numbering schemes – for example, supporting an MPT fleet and a DMR fleet on the same
system, or multiple customers with distinct radio systems.
Channel groups are created on the Incoming Connections menu.
When adding a new channel group, it is possible to change the default fleet. This is used to set the
fleet of new devices which are automatically added to the TRACX server. Any new devices which
appears on any channel source in this group will be automatically assigned to this fleet.
Channel sources
Each channel source is an individual device which receives GPS updates. Every channel source is a
member of a channel source group.
Defining a new channel source is via the Incoming Connections menu.
Each channel source is associated with a network device, defined in the Network Device Links menu.
For TRICX servers, the channel field refers to the TRip_Number field defined in the TRip.ini file. For
Hytera T2 gateways/DDC-1 controllers in Hytera mode, the channel refers to the timeslot
configuration number.
It is possible to add multiple channels at the same time by entering multiple channel numbers
separated by commas. Each channel is added as a new entry in the channel list.
Example configuration
The following example demonstrates the use of channel groups to distinguish between overlapping
radio IDs over multiple TRICX servers.
The system is configured as follows:
•
•
TRICX server A:
◦
Connected to a DMR network via three DMR mobiles. The DMR mobiles are
TRip_number 1, 2 and 3
◦
Connected to an MPT network via a single mobile, TRip_number 5
TRICX server B:
◦
Connected to the same MPT network as TRICX A using three mobiles: TRip_numbers 2,
3 and 4
◦
Connected to a different DMR network via 2 mobiles: TRip_numbers 11 and 12
The numbering schemes for the two DMR networks overlap – i.e. both networks have a radio
numbered 123. The DMR numbering schemes also overlaps with MPT numbering.
To configure this in the TRACX server:
1. Add the two TRICX servers via the Network Device links menu.
2. In the Incoming Connections menu, add three channel groups: DMR A, DMR B and MPT.
3. Add the channel sources as follows:
Link Device
Channel
ChannelGroup
TricxA
1,2,3
DMR A
TricxA
5
MPT
TricxB
2,3,4
MPT
TricxB
11, 12
DMR B
Fleet administration
Creating Fleets
Add new fleets via the Fleets menu.
Assigning devices to fleets
To assign a device to a fleet, use the GPS Devices menu. The group can be assigned when creating a
device or later altered by editing.
Automatically assign devices to fleet using a Channel group
Channel groups each have a default fleet associated with them. If a GPS fix from an unknown device
is received on any known channel source, then the newly automatically created device entry will
become a member of the fleet associated with this channel group.
Assigning users to a fleet
Standard Users and Fleet Admins have access only to a single fleet on the TRACX system.
Fleets can be assigned when a user is created. A user's fleet can be edited at a later time.
Markers
The TRACX allows custom markers to be created for devices on the map. Each device can either be
assigned a custom marker or use the system defaults. Automatically added devices will use the
system default icons.
Marker defaults menu
The marker defaults menu is selected in the administration menu,
Marker options for active GPS devices
Active GPS devices are any device which has sent a GPS fix to the TRACX server within a specified
time frame from now.
Choose the default marker for these devices by selecting the radio button to the left of the desired
icon:
This marker will be shown as the map marker for all devices which are currently active and don't have
a custom map marker shown.
The timeout for active markers is defined here. Only devices which have sent a GPS update within
this timeout are considered to be active.
Marker options for invalid GPS fixes
The marker for devices which have sent a GPS update without a valid GPS fix. This occurs when a
device is switched on and active but its GPS receiver is unable to provide a valid position.
Marker and timeout for inactive devices
Define the marker for inactive devices – this is any device which hasn't posted a GPS update within
the active timeout period.
The inactivity timeout period defined here is not currently applied.
Creating custom markers
Custom markers are created vua the “Icons and Markers” menu.
This menu shows all of the currently defined marker types.
To create a new marker, click the “Create marker” button.
Illustration xxvii: Create new marker dialogue
Marker type:
There are five options for marker type:
Type
Example
Notes
Dropper
A default marker pin. If an icon is chosen, it appears instead of the
marker's circle cutout
DropperWithIcon
A bigger marker pin. If an icon is chosen, it appears inside the centre
circle cutout.
Flag
A flag marker. Icon appears inside the flag.
Simple
An icon without any marker. If no marker is specified then the
default locator icon is used.
File
*not implemented. Future versions will allow custom marker file upload.
Colour:
The colour for the marker. If Simple marker type is chosen, then the selected icon is colourified to
this colour.
Icon:
An icon for this marker.
The TRACX server is supplied with an extensive marker library which can be searched by entering
text in the search box. The search results appear in a drop-down list below the search box – select
an icon by choosing one of the search results here.
Future software releases will have an icon upload facility to add icons to the library.
Anchor point
Each marker has an anchor point. This is the exact pixel in the image which corresponds to the
device position on the map. For the Dropper, DropperWithIcon and Flag marker types, this anchor
point is the point at the sharp end of the marker image. For Simple marker types, the centre of the
image is used.
Notes on marker creation
The markers are built by the TRACX server into a single image file by superimposing a number of
individual images into a single result image which is then saved as a .png file for use by the TRACX
mapping.
The icons are all black images. They are superimposed on a white drop shadow before being
positioned on the marker so they are visible on markers of any colour:
Illustration xxviii: Tower icon on different background colours
Deleting markers
Remove a marker by clicking it in the Markers and Icons menu.
If this marker is in use by any device, it will revert to system defaults marker options.
Status and text messaging
The TRACX server supports receiving both pre-defined status messages and free text messages from
radios. These messages are shown in the inbox for a device.
Status messages are treated differently to text messages. On receipt of a recognized status message,
the current status value for the device is set and stored.
Both incoming numeric values and text can be looked up against the status table. This allows predefined text messages sent by a mobile device to be treated in the same way as numeric statuses and
to set the current status of the radio. When using text message lookup for incoming status, the
incoming text must exactly match the stored value (however, the lookup is not case sensitive).
Each text and status value is associated with a particular channel group; that is, the status value “123”
will have a different entry for each channel group. For example, the status “12” on a channel group
for MPT radios (“MPT”) can have a different meaning than status “12” on a channel group for DMR
radios.
Text lookups
When any text message is received, it is checked against the status table. If the received text message
matches an entry in the table, it will be treated as a status message. This will add the extra features
which status messaging provides.
This adds status-like facilities to radio systems which do not natively support status messages but do
support “quick text” predefined text messages.
If a text message does not match any item in the status table, it is treated as a text message. This is
shown in the inbox for a device, but doesn't change the radios currently stored status value.
Status lookups
Any incoming numeric status is automatically treated as a status value, even if not defined in the status
lookup table. It will still set the stored status value of the radio. In this case, the associated text
lookup will be substituted with the text “status value' where value is the numeric status.
Adding a new status value
New status values are added via the Status menu.
Status: The numeric status or fixed text message to perform a lookup on.
Status text: The text message to display for this status.
Incoming connection group: The channel group that this status message is associated with.
Marker: Marker to display on the map when a device's current status is this status.
Status ID
Each stored value has a StatusID associated with it – this is used by the TRACX system to refer to
the specific status. This value is shown in the Status table in the '#' column.
This status ID is automatically generated when adding a new status lookup. It is used when defining
event rules to refer to a specific status value.
Events and actions
Event rules allow customization of the TRACX system behaviour. The system can be set up to
perform a predefined action in response to a trigger event. For example, on receiving a man-down
alert from a radio an on-screen alert can be set.
Event Types
Currently, the only event types defined are:
•
Status received – a status message which is defined in the TRACX is received
•
Alarm received – a radio or device sends in an alarm or alert
Action types
Currently, only the following actions are defined:
•
JumpTo – jump to the location of the relevant device
•
SetAlarm – set an alarm. This also causes an on-screen notification which must be
acknowledged by a user
•
PlaySound – play an audio alert tone.
Defining an event/Action
The event definition dialogue contains a number of fields, the meaning and relevance of which is
dependent on the event and action types selected.
Rule name field
This is a descriptive name for the event/action pair. This should give a clear description of the
intended use of this rule.
Event fields
There are two parameters for event definitions – DeviceID and StatusID. Their meaning, depending
on the selected event, is listed in the table below.
An event will cause an action to be triggered if all the criteria are met.
Event type
DeviceID
StatusID
StatusReceived If set, will match only the specified
deviceID (ID number in devices table).
If blank, will match any device.
If set, will match the status ID. Status ID
taken from the status table,
If blank, will match all status messages.
AlarmReceived
Not used
Action fields
There is only a single field for actions – parameter. The meaning of this is dependent on the selected
action type:
Action type
Parameter meaning
JumpTo
Not used
SetAlarm
Not used
PlaySound
Sound ID (taken from Alert sounds table)
Places
The Places feature allows the definition of a number of pre-defined locations to be stored. Currently,
the TRACX offers the facility to use these pre-defined locations to quickly jump to places of interest;
future software versions will offer the ability to place markers on maps (with toggle-able display
layers) which can show useful information about those places.
Categories
These categories allow the place names to be arranged into logical groups – for example, a local
authority may have a Schools category.
If the “available as map layer” box is checked, this will be available as a switch-able icon layer on the
map. This feature is not currently available.
Add new place
Place name: The name of this place.
Description: Add further text for this place. This description text is used when searching for a place
in the TRACX software. It will also be shown in the popup for the map marker in future versions.
Latitiude and longitude: Location for this place. This can also be selected by clicking “find on map”
and positioning the marker on the shown map.
Marker: A marker to show on the map for this place (when its associated category is visible on the
map) – not currently used.
Category: Category that this marker belongs to.
Fleet: Fleet that this marker belongs to.
GSM/GPRS trackers
The TRACX supports multiple tracker device units. Currently implemented:
•
Teltonik (?) GH3000
•
Pebbel thing:
◦
What is this actually called?
◦
Only partial implementation – I actually need to fix this.
Future:
•
Teltonik FM12xx protocol
•
TBD
Currently supported trackers all use internet-based protocols via GPRS. Future updates will include
SMS-based protocols.
TRACX tracker ports
The following ports are used by default by the TRACX for various tracker protocols. If required,
these ports should be routed to the TRACX server from the internet.
Tracker type
Protocol
Listen port
GH3000
UDP
12050
Pebbel thing
TCP
12051
FM12xx
UDP
12052
GH3000 tracker configuration
FM12xx tracker configuration
Alphabetical Index
Active devices...............................................................................................................................................................................................18
Channel.............................................................................................................................................................................................................28
Connection group......................................................................................................................................................................................26
History.....................................................................................................................................................................................................................
Quick history trail.................................................................................................................................................................................15
Icons...........................................................................................................................................................................................................11, 13
Overview map..............................................................................................................................................................................................17
Radio device...................................................................................................................................................................................................26
Search......................................................................................................................................................................................................................
Searching for an address..................................................................................................................................................................20
Searching for devices.........................................................................................................................................................................17
Was this manual useful for you? yes no
Thank you for your participation!

* Your assessment is very important for improving the work of artificial intelligence, which forms the content of this project

Download PDF

advertisement