Transcript
Flextrack Lommy (Phoenix) Technical Description Version 0.73
www.flextrack.dk
Flextrack Lommy Phoenix platforms Technical Description Version 0.73
Lommy Personal
Lommy Pro
Lommy® is a registered trademark of JAX Invest A/S
Page 1 of 47
Flextrack Lommy (Phoenix) Technical Description Version 0.73
www.flextrack.dk
Table of Contents Introduction..........................................................................................................................................3 What is the GPS system?......................................................................................................................4 What is GPRS?.....................................................................................................................................5 Operating the unit................................................................................................................................6 Changing the configuration.................................................................................................................7 Inserting the SIM-card.........................................................................................................................8 System commands.................................................................................................................................9 STAT Description..........................................................................................................................12 Parameters.........................................................................................................................................13 SOS-SMS Description...................................................................................................................24 FLEXSERVER-IP → FLEXSERVER-IP-SEC failover...............................................................24 GSM-INFO....................................................................................................................................25 TILT Description...........................................................................................................................25 NOMOVE Description..................................................................................................................25 DEADMAN Description...............................................................................................................25 GEOFENCE Description...............................................................................................................26 STAT-IO........................................................................................................................................28 STEALTH Description..................................................................................................................28 PREFERRED-OPERATORS Description....................................................................................28 1-WIRE Description......................................................................................................................29 Voice files...........................................................................................................................................31 Status messages..................................................................................................................................33 UNITSTAT....................................................................................................................................33 Unit State field...............................................................................................................................34 OWDID-DISCOVER....................................................................................................................35 OWTEMP-REPORT.....................................................................................................................36 OPT-STATUS...............................................................................................................................37 WOLF-HEARD.............................................................................................................................38 WOLF-ALIVE...............................................................................................................................38 WOLF-REMOVED.......................................................................................................................38 FlexCI communication protocol........................................................................................................40 Low-level.......................................................................................................................................40 High-level......................................................................................................................................43 HTTP GET Request............................................................................................................................44 Wiring the option 2 (OPT2) board.....................................................................................................46 Technical specifications.....................................................................................................................47
Page 2 of 47
Flextrack Lommy (Phoenix) Technical Description Version 0.73
www.flextrack.dk
Introduction The Flextrack Lommy Phoenix platform is highly portable “Personal Tracking Units”, which allows persons or belongings to be followed with the help of the global GPS system (see the section “What is the GPS system?” for an explanation of the GPS system). The unit communicates with the “outside” world using GSM/GPRS technology. The use of GPRS allows monitoring of the units position in almost real-time as the unit is “always on”, and is very cost-effective as one only pays for the amount of data sent, and not for the time spent “online” (see the section “What is GPRS?” for an explanation of the GPRS technology). The unit has it’s own internal high-capacity battery, which will allow the unit to run continuously for many hours (days) before recharging is needed. The Flextrack Lommy unit can communicate with the outside world through different means, ranging from simple SMS messages, HTTP web requests, and for maximum flexibility, the FlexCI protocol. All 3 possibilities are described in detail throughout this document. Up to 3000 positions can be stored i a cylindrical memory if there it no continual connection to a server The Lommy Personal is equipped with a speaker and microphone, this allows the user to accept and initiate voice calls, for example should an emergency situation occur. It can play different audible messages for different events. Battery level low, emegency alarm sent etc. Depending on the model the Lommy Personal can be equipped with a 433MHz RF tranceiver, 868MHz transceiver, 3-axis G-force sensor and up to two additional buttons for additional functionality. The Lommy Pro is meant for fixed mount usage, but can be carried for personnel use as well. Depending on the model the Lommy Personal can be equipped withIt's equipped with and option-2 board with 4 analog input ports and two digital output ports. Other options are 433MHz RF transceiver, 868MHz transceiver, 3-axis G-force sensor and up to two additional buttons for additional functionality.
Page 3 of 47
Flextrack Lommy (Phoenix) Technical Description Version 0.73
www.flextrack.dk
What is the GPS system? GPS is a satellite-based radio navigation system developed and operated by the U.S. Department of Defence (DOD). GPS permits land, sea, and airborne users to determine their three-dimensional position, velocity, and time 24 hours a day, in all weather, anywhere in the world with a precision and accuracy far better than other radio navigation systems available today or in the foreseeable future.
One of the 28 satellites
The 28 satellites orbits the earth in 6 planes
The GPS concept of operation is based upon satellite ranging. Currently the GPS network consists of 28 satellites orbiting the earth. Users figure their position on the earth by measuring their distance from the group of satellites in space. The satellites act as precise reference points. Each GPS satellite transmits an accurate position and time signal. The user's receiver measures the time delay for the signal to reach the receiver, which is the direct measure of the apparent range to the satellite. Measurements collected simultaneously from at least four satellites are processed to solve for the three dimensions of position, velocity and time.
Page 4 of 47
Flextrack Lommy (Phoenix) Technical Description Version 0.73
www.flextrack.dk
What is GPRS? GPRS facilitates instant connections whereby information can be sent or received immediately as the need arises, subject to radio coverage. No dial-up modem connection is necessary. This is why GPRS users are sometimes referred to as being "always connected". Immediacy is one of the advantages of GPRS (and SMS) when compared to Circuit Switched Data. High immediacy is a very important feature for time critical applications such as tracking persons or vehicles where it would be unacceptable to wait for a dial-up connection to be established, or where the added cost of sending SMS messages would make running the application too expensive. Because of the Flextrack Lommy unit is equipped with GPRS (and GSM) technology, the unit is connected to the global Internet, making system integration with back-end (server) systems easy. The GPRS service runs on the same frequencies as the GSM network, and is an integrated part of that.
Page 5 of 47
Flextrack Lommy (Phoenix) Technical Description Version 0.73
www.flextrack.dk
Operating the unit The Lommy has 1 button, 4 light indicators (green, red, yellow and blue) and a connector at the bottom. To turn the unit on, press the red button shortly. The yellow light will indicate that it is starting up. Shortly afterwards the rest of the lights will flash. To turn it off again press and hold the red button until the yellow indicator flashes slowly. Now release and press the button again shortly within 2 seconds. The green indicator is the GSM indicator. It will blink 50/50 until it has connected the GSM network. After then you will only see it on, when the Lommy is receiving/sending data. If it keeps flashing, please make sure that a SIM-card is properly inserted and PIN-code control is either disabled or set to 10000 minus the last 4 digits of the serial number. Ex. a unit having the serial number 0061102002 must have the PIN-code 10000 - 2002 = 7998. The red indicator is flashing while charging and fully lit up when charging has completed. If the red indicator are flashing with no charger connected, the battery must be recharged. The yellow indicator is on while the Lommy is starting up. Giving one flash the unit is on and giving two flashes it is connected to a server using the FlexCI protocol The blue light is indicating GPS reception. Giving one flash there is no GPS coverage, else it will give one flash and a number of short flashes indicating the number of GPS satellites seen while the GPS is on. The bottom connector is used for charging the Lommy and pre configuration.
Page 6 of 47
Flextrack Lommy (Phoenix) Technical Description Version 0.73
www.flextrack.dk
Changing the configuration In order to get started configuring the Lommy, you need to download and install a software tools on your PC. On this link http://www.flextrack.dk/files/PConfig.zip you can download PConfig, a tool to configure and firmware upgrade the Lommy. Unpack the file to C:\ and connect the Lommy to your PC using a mini-USB cable. When prompted for the location of the driver, let it search in C:\PConfig Now start the program C:\PConfig\PConfig.exe and select "File -> Connect" The status bar should now show "Connected". If not please make sure the Lommy is turned on (by pressing the red button), cable is properly connected and driver successfully installed. In "Configuration" you can read or write the configuration. When read it will store the configuration in a text file that can be altered using ex. Notepad and written back using the "write" option. To upgrade the firmware select "File -> Upload Firmware.." If you have further questions and/or wants a notification when new firmware are available, just send an email to
[email protected]
Page 7 of 47
Flextrack Lommy (Phoenix) Technical Description Version 0.73
www.flextrack.dk
Inserting the SIM-card. 1. Place the Lommy with the front down and remove the 5 torx-screws (size 6). 2. Hold the plastic parts together and turn it around so the backside are now downwards. 3. Gently remove the front cover and remove the rubber ribbon 4. Insert the SIM-card (see figure 1) 5. Now follow point 1-3 in reverse order. Do not take out the module, and be very careful not to bend the GPS antenna!! figure 1
figure 2
Page 8 of 47
Flextrack Lommy (Phoenix) Technical Description Version 0.73
www.flextrack.dk
System commands The Flextrack Lommy unit can be controlled using a number of commands sent to it. The messages can be sent using either SMS messages or thru the FlexCI protocol. The messages allow you to query the state of different sub-systems in the unit, modify configuration parameters etc. Please note that the syntax for the commands has to be followed exactly, all commands must be written as stated below; especially note the commands are case sensitive! The “SL” field describes the security level needed for the command to be executed, high level means that only a sender that has its number listed in the "SMSSENDER" or "FLEXSERVER-SMS" parameter are allowed to send this command by SMS, low security level can be accepted from any sender. Command
Example
SL
Description
CLEAR-BUF CONF:
CLEAR-BUF CONF:PIN,1234
High High
CONF?
CONF?PIN
High
GSM-INFO
GSM-INFO
High
STAT
STAT
Low
STAT-IO
STAT-IO
High
RELOAD [ ]
RELOAD 120.121.122.123 application.pfw
High
RESET
RESET
High
Clears what might be in circular buffer. Modify/add a configuration parameter in the unit. If the ”name” does not exist, it will be created in the configuration parameters. More configuration changes can be send in the same message, separating commands with a semicolon. Ex.CONF:APN,internet;CONF:USERNAME,g prs;SAVEPARAM. More commands in one message are only supported using SMS. This will return the value of the parameter “name”. More values can be requested in the same message separating commands with a semicolon. Ex. CONF?APN;CONF?USERNAME;CONF? PASSWORD Get the current GSM channel information and neighbour channels (See description) Sends a SMS message with the status of the unit, battery voltage, signal level etc. 1) Get status of all input/output ports on models eqipped with OPT2 board (see description) This start the download of a new application from a web-server using OTAP. Please note that ‘APN’, ‘DNS’, ‘USERNAME’ and ‘PASSWORD’ must be configured correctly for this to work. If for some reason the RELOAD command fails (maybe just downloading half of the program) the unit will continue on the current firmware version. The Flextrack unit will be reset.
Page 9 of 47
Flextrack Lommy (Phoenix) Technical Description Version 0.73
www.flextrack.dk
Command
Example
SL
Description
POS
POS
High
ICCID NEWPOS
ICCID NEWPOS
High High
A message containing the last good GPS fix is sent back with information about lat/lon, speed, direction and number of satellites used in the fix. If there was no GPS fix the last time a report was sent, “No fix” will be indicated in the answer. Will return the ID of the SIM card in the unit Same behavior as the “POS” command above, except that the unit will try to get a GPS fix before sending the answer. (This command ONLY works when issued via SMS message !) It can also be used with two; (parameters (number of positions, delay between positions) Loads the non volatile configuration into the running configuration. This can be used to get back to normal if some values have been altered and no SAVEPARAM has been sent. Saves the current parameter set into non-volatile memory (in the sysconfig.cfg file on the Unit) Use the current/existing position as the centre of the geofence (only if there is a valid position, will wait GEOFENCE-GIVEUP period for a fix) A message will be sent back telling if the geofence was successfully set ot not. OFF, SET & AUTO is equivalent to the parameter GEOFENCE value 0, 1 & 2 ON will use the existing centre or acquire one if none is present. LOCATE returns distance and bearing to the geofence center position The unit will power down and wake up again in the specified number of minutes. During power down, the unit can be switched on manually as normal. The unit will be switched off. You must manually switch on the unit again. Tell the unit if SMS is to be used when sending unsolicited messages to the FlexCI server (UNITSTAT etc). Default after power on, is OFF. Forces unit to send a UNITSTAT message. The unit will NOT attempt to make a new GPS fix, the data from last time fix was attempted will be sent to the number(s) in FLEXSERVER-SMS Forces unit to send a UNITSTAT message. The unit will attempt to make a new GPS fix. The response will be sent to the number(s) in FLEXSERVERSMS Unit sends the complete current configuration (will only return the configuration if the command is issued on the FlexCI protocol, if sent using SMS, the answer is too big to be returned (max 160 characters)) Returns the IMEI of the unit.
NEWPOS 3,60 LOADPARAM
LOADPARAM
High
SAVEPARAM
SAVEPARAM
High
GEOFENCE
[GEOFENCE:SET /GEOFENCE:ON /GEOFENCE:OFF /GEOFENCE:AUTO /GEOFENCE:LOCATE]
High
POWERDOWN
POWERDOWN 60
High
POWEROFF
POWEROFF
High
SMS
[SMS:ON/SMS:OFF]
High
UNITSTAT
UNITSTAT
Low
NEWUNITSTAT
NEWUNITSTAT
Low
GETCONF
GETCONF
High
IMEI
IMEI
High
Page 10 of 47
Flextrack Lommy (Phoenix) Technical Description Version 0.73
www.flextrack.dk
Command
Example
SL
Description
BEACON
High
OPT-DO1:ON OPT-DO1:OFF OPT-DO2:ON OPT-DO2:OFF LPOS
[BEACON:ON/ BEACON:OFF] OPT-DO1:ON OPT-DO1:OFF OPT-DO2:ON OPT-DO2:OFF LPOS
OW-DEVICES
OW-DEVICES
High
OWDID-CLEAR OWDID-DELETE
OWDID-CLEAR OWDID-DELETE, aabbccddeeffgghh OWDID-INSERT, aabbccddeeffgghh OWDID-TOGGLE,1
High High
OWTEMP-CLEAR OWTEMP-INSERT
OWTEMP-CLEAR OWTEMP-INSERT, aabbccddeeffgghh,0,30
High High
OWTEMP-DELETE
High
OWTEMP-REPORTINTERVAL
OWTEMP-DELETE, aabbccddeeffgghh OWTEMP-REPORTINTERVAL,600
ODOMETER-SET OPT-TIMER
ODOMETER-SET,0 OPT-TIMER 1,0
High High
TALK
TALK 1,20
High
TIME
TIME 090303102100
High
CLEARPARAM
CLEARPARAM
High
VIBRATE
[VIBRATE:ON/ VIBRATE:OFF]
High
Turns the RFID transceiver on or off (Only in some models) Is setting output port 1 logic high. 2) Is setting output port 1 logic low. 2) Is setting output port 2 logic high. 2) Is setting output port 2 logic low. 2) When LPOS command is received, a special formatted response (much like the FLEETMAN HTTP GET requests) is sent back with the current position in, this can be used on cellphones as a link to, for example, Google Maps Will scan the bus for devices, and when done, send a OW-DEVICES report back in the format: OWDEVICES,YYYYMMDD,HHMMSS,[id1], [id2]...... Clears the list of the 80 driver id's Is deleting a specific driver id from the list of driver id's Inserts a specific driver id into the list of driver id's If a Driver ID is connected that is present in the list of driver id's, the OPT2 output 'x' will be on for 10 seconds. x can be '0' for none, '1' for output 1 or '2' for output 2. If ignition is active, output will be on until ignition is inactive. Clears the list of the 8 temperature sensors Inserts a specific sensor id and low/high temperature (in 1/10 deg) alarm into the list of temperature sensors Deletes a specific sensorid from the list of temperature sensors Number of seconds between reports (temperature for all configured sensors and their alarm state is sent) Sets the current odometer value (in meters) Set new value for one of the 4 hour counters for the OPT2 board (value is in minutes) Message xx is played thru the speaker at volume yyy (these are the same parameters as used in all the _VOICE parameters) Sets the current UTC time of the device, YY is year (00..99), MO is month (01..12), DD is date (01..31),HH is hour (00..23), MM is minutes (00..59), SS is seconds (00..59) Initializes all parameters in the unit to the factory default! This will start/stop the vibrator manually (if VIBRATE parameter is set)
OWDID-INSERT OWDID-TOGGLE
High High High High High
High High
High
Page 11 of 47
Flextrack Lommy (Phoenix) Technical Description Version 0.73
www.flextrack.dk
1) The content of the STAT response is: Version=Phoenix OPT2= NodeID= BattV= Runtime= MCC= Signal= Sat= HDOP= Ichg= Bt= odo= vt=<0/1 for unit having a valid time or not> 2) Only in the Pro model with option 2 board (OPT2)
Page 12 of 47
Flextrack Lommy (Phoenix) Technical Description Version 0.73
www.flextrack.dk
Parameters The Flextrack Lommy unit can be configured with a number of parameters. The parameters are normally set to fixed values from the factory; the individual parameters can be changed by sending the “CONF:” SMS message to the unit (see the section “System Commands”). Whenever the unit is started, the parameters are read from non-volatile storage (the sysconfig.cfg file on the unit) into the unit’s internal memory (RAM). If a parameter is changed with the “CONF:” command, it is only this internal representation in RAM that is changed. More commands can be sent in the same message, separating each with a semicolon The command “SAVEPARAM” must be issued in order to write the current parameters into non-volatile memory. Please note that all the parameters MUST be typed exactly as shown (all in upper case), or the module will not recognize them!! All default values are shown in bold underlined text. Parameter
Value
* Description
PIN APN USERNAME PASSWORD DNS
1234 internet user password 122.133.144.155
* * * * *
FLEXSERVER-IP
www.server.com:12345 fs1.care4all.dk:30000
FLEXSERVER-IPSEC
www.server-2.com:12345
FLEXSTREAM-IP
www.server.com:12345 / AUTO
FLEXSERVERSMS
+4512345678,+4577665544 +4550503185
FLEXSERVERIDLE
0/180..99999
Pin code for the SIM card APN name for attaching to internet via GPRS Username for attaching to internet via GPRS Password for attaching to internet via GPRS DNS server IP address, on some networks this must be specified, on other networks it can be blank. * IP address and port number to use for contacting a Flexserver. If this parameter is set to SMS, no connection will be made, but instead the FlexCI interface will behave as if there is no connection (SMS messages will be used for sending UNITSTA messages) If set to "AUTO" the FlexStream interface uses the same IP (and port) as the FlexCI interface is using (FLEXSERVER-IP / FLEXSERVER-IP-SEC) * IP address and port number to use for contacting a secondary Flexserver. This IP will be used if the “FLEXSERVER-IP” is not responding. IP address and port number to use for contacting a Flexserver using UDP. Only UNITSTAT’s will be sent to this service List of SMS phone numbers to use for contacting a Flexserver if not possible to establish a GPRS connection. A message is sent to each number in the list * Number of seconds between “keep alive” communication to the FlexServer. If set to 0, no “keep alive” communication is sent. The keep alive communication consists only of a . The FlexServer should answer back with a .
Page 13 of 47
Flextrack Lommy (Phoenix) Technical Description Version 0.73
www.flextrack.dk
Parameter
Value
FLEXSERVERCIRCULAR
[0..3000] 10
FLEXSTREAMFIELDS
[00000000..FFFFFFFF] 0003FFFF
FLEXSTREAMINTERVAL
[0..99999] 0
REPORTINTERVAL
[10..99999] 120
REPORTINTERVAL-SMS
[10..99999] 1800
REPORTINTERVAL-SMSROAMING
[10..99999] 1800
* Description * Circular buffers for UNITSTAT messages over
GPRS. The parameter FLEXSERVER-CIRCULAR sets the number of entries in the buffer, if set to 0 the buffers are disabled (the unitstat messages are sent immediately if connected else discarded). Max allowed number is 3000. If REPORT-INTERVAL is equal or below 7 seconds, the buffers are disabled (they would not be able to keep up with the high rate of reports A binary mask, each '1' bit will enable the corresponding field in the UNITSTAT message sent over Flexstream. The TNO and the text "UNITSTAT" is always present. Ex: FLEXSTREAM-FIELDS="0000101F", will enable date, time, serialnumber, lattitude, longitude and the height FLEXSTREAM-FIELDS="00020007", will enable date, time, serialnumber, and odometer value FLEXSTREAM-FIELDS="0003FFFF", will enable all fields (just as before the feature was implemented) The report interval for UDP datagram messages sent if FLEXSTREAM-IP is defined. Shortest interval possible is 3-4 seconds. Times in seconds between position (status) messages. MAT-LAT, MAX-LON, MAX-HDOP and FORCEREPORT are taken in consideration before the position is sent. Times in seconds between position (status) messages. MAT-LAT, MAX-LON, MAX-HDOP and FORCEREPORT are taken in consideration before the position is sent. If the value is higher than 50000(seconds) then the actual interval will be "report-interval-xxx" minus 50000 minutes instead! Example: The report-interval is set to 65000, the actual report interval will then be 65000 minus 50000, ie 15000 minutes. Time in seconds between position (status) messages are sent when a Flexserver is not present, and messages are sent to the “FLEXSERVER-SMS” number if the unit is on its home network (NOT roaming). If the value is higher than 50000(seconds) then the actual interval will be "report-interval-xxx" minus 50000 minutes instead! Example: The reportinterval is set to 65000, the actual report interval will then be 65000 minus 50000, ie 15000 minutes. Time in seconds between position (status) messages are sent when a Flexserver is not present, and messages are sent to the “FLEXSERVER-SMS” number if the unit is NOT on its home network (it is roaming). If the value is higher than 50000(seconds) then the actual interval will be "report-interval-xxx" minus 50000 minutes instead! Example: The reportinterval is set to 65000, the actual report interval will then be 65000 minus 50000, ie 15000 minutes.
Page 14 of 47
Flextrack Lommy (Phoenix) Technical Description Version 0.73
www.flextrack.dk
Parameter
Value
STATEMASK
[00000000..FFFFFFFF] FDFFFFFE
* Description
STATEMASK-SMS
[00000000..FFFFFFFF] FDFFFFFE
GPS-CHARGE
0/1
GPS-GIVEUP
300
GPS-TIMEOUT
50
FLEETMAN
www.server.com/httprecei ver.dll
FORCE-REPORT
[0.1000] 5
MAX-HDOP
[0..500] 300
MAX-LAT
[0..9999] 250
A mask used to identify when the “UNITSTAT” message should be sent, a ‘1’ in a bit in the mask will force the unit to send the “UNITSTAT” command whenever the corresponding bit in the Unit State field changes state. This mask is used when connected to the server in FlexCI mode. A mask used to identify when the “UNITSTAT” message should be sent, a ‘1’ in a bit in the mask will force the unit to send the “UNITSTAT” command whenever the corresponding bit in the Unit State field changes state. This mask is used when sending UNITSTAT as SMS.. If set to ‘1’, the GPS will be powered on continuously if the charger is connected to the unit (same effect as setting ‘GPS-GIVEUP’ to 0) Number of seconds to keep listening for a GPS position if no fix available, before powering the GPS off. The GPS will be powered on again when a new report is to be sent. If set to 0, the GPS will NOT be powered down between the individual “request for fix”. Number of seconds to keep listening for a GPS position. If no valid fix is found within this specified time, the report will be sent with the current information from the GPS receiver (position might be wrong) The URL for sending HTTP GET requests to. If this parameter is either omitted or left blank, no HTTP GET requests will be attempted. See the section “HTTP Get Request” for an explanation. If the position has not changed enough this number of times according to “MAX-LAT” and “MAX-LON”, send a position report anyway. Maximum “Horizontal Dilution Of Precision”. When a GPS position is acquired, the precision can be less than optimal, this number basically tells the unit how precise the position must be (as reported by the GPS receiver) before a position report is sent. The factor is based on the “standard accuracy of the GPS receiver” which is typically 5 meters. A HDOP value of 20 (2.0) means that the position error must be better than 5 meters multiplied by 2.0, i.e. 10 meters. Please note that there are other factors that influence the precision of the GPS positions, such as reflected signals etc! This is the number of “decimal minutes” a position must change in latitude for the position report to be sent. If the current position has NOT changed by more than this number as compared to the last position reported, no position report is sent (however “FORCE-REPORT” sets an upper limit for the number of not-sent reports).
Page 15 of 47
Flextrack Lommy (Phoenix) Technical Description Version 0.73
www.flextrack.dk
Parameter
Value
* Description
MAX-LON
[0..9999] 500
VOICE
[0/1/2/3]
CYCLIC
[0..99999] 0
LASTGOOD
[0/1] 0
SOSPHONE
+4512345678,+4512345679
SOSPHONE1
+4512345678,+4512345679
This is the number of “decimal minutes” a position must change in longitude for the position report to be sent. If the current position has NOT changed by more than this number as compared to the last position reported, no position report is sent (however “FORCE-REPORT” sets an upper limit for the number of not-sent reports). * Specifies if the unit supports voice or not. 0: Both speaker and microphone is disabled (silent) 1: Voice is supported (speaker and mic.) 2: speaker is off, microphone is in high sensitivity mode. 3: microphone is disabled, speaker in high volume mode * If this parameter is set (greater than 0) the unit will power down for this number of minutes 7 minutes AFTER the last command has been received (either by SMS or FlexCI protocol). The 7-minute period is restarted every time a command is received (there is approximately 1 minute overhead when using this feature, if you specify 10 minutes, it will actually take approximately 11 minutes before the unit is powered up again). If no GPS-fix are found within the 7 minutes, the value of GPS-TIMEOUT is added to the 7 minutes. If this parameter is set to 1, the values of Date, Time, Longitude, Latitude, Speed, Direction, SV and Elapsed time for fix, will be taken from the last good position, if unable to get the most current. Bit 8 in the Unit State will be raised then. The number to dial for establishing a voice channel when function button is activated for more than half a second. This parameter only gives meaning if ‘voice’ is set to 1, 2 or 3. There can be more numbers seperated with a comma ',' then the unit will call the first number. If the called party is not responding with a ”#”, it will try the next etc. The number to dial for establishing a voice channel when button 1 is activated for more than half a second. This parameter only gives meaning if ‘voice’ is set to 1, 2 or 3 (Only some models) There can be more numbers seperated with a comma ',' then the unit will call the first number. If the called party is not responding with a ”#”, it will try the next etc.
Page 16 of 47
Flextrack Lommy (Phoenix) Technical Description Version 0.73
www.flextrack.dk
Parameter
Value
SOSPHONE2
+4512345678,+45123456 79
* Description
SOS-SMS
+45123456,+4566778899
SOS-SMS1
45123456,+4566778899
SOS-SMS2
45123456,+4566778899
SOS-TEXT
ALERT
SOS-TEXT1
ALERT
SOS-TEXT2
ALERT
AUTOANSWER
+451123344,+452233432
The number to dial for establishing a voice channel when button 2 is activated for more than half a second. This parameter only gives meaning if ‘voice’ is set to 1, 2 or 3 (Only some models) There can be more numbers seperated with a comma ',' then the unit will call the first number. If the called party is not responding with a ”#”, it will try the next etc. This list of numbers (if defined) will receive a position report (like the answer to a “POS” command, only the first line will contain the word “PANIC”) if the function button is activated for more than half a second. The word "PANIC can be changed with the SOS-TEXT parameter. See below for contents of the message sent. This list of numbers (if defined) will receive a position report (like the answer to a “POS” command, only the first line will contain the word “PANIC”) if button 1 (only some models) is activated for more than half a second. The word "PANIC can be changed with the SOS-TEXT1 parameter. (Only some models) See below for contents of the message sent. This list of numbers (if defined) will receive a position report (like the answer to a “POS” command, only the first line will contain the word “PANIC”) if button 2 (only some models) is activated for more than half a second. The word "PANIC can be changed with the SOS-TEXT2 parameter. (Only some models) See below for contents of the message sent. The pre-text for SOS-SMS If the text is followed by a "/" only the text in the parameter is sent, otherwise position etc is added. The pre-text for SOS-SMS1 If the text is followed by a "/" only the text in the parameter is sent, otherwise position etc is added. The pre-text for SOS-SMS2 If the text is followed by a "/" only the text in the parameter is sent, otherwise position etc is added Specify a list of phone numbers that will be answered automatically by the unit. If the unit should answer an incoming voice call, and the phone number is NOT in this list, the call will only be accepted if the function switch is pressed. This parameter only gives meaning if “VOICE” is set to 1, 2 or 3. If the parameter is set to “ALL”, all callers will be answered automatically.
Page 17 of 47
Flextrack Lommy (Phoenix) Technical Description Version 0.73
www.flextrack.dk
Parameter
Value
SMSSENDER
+451123344,+452233432
* Description
POWEROFF-VOICE
[0..66],[0..100] 1,20
DEADMAN
[0/1]
DEADMAN-TIME
[30..99999] 900
DEADMAN-WARNING
[5..999] 15
DEADMAN-VOICE1 DEADMAN-VOICE2
[0..66],[0..100] 2,20 [0..66],[0..100] 3,20
DEADMANVOICECALL DEADMAN-SMS
+4512345678
DEADMAN-TEXT
DEADMAN
MOVEMENT
[0/1/2]
MOVEMENT-TIME MOVEMENT-VOICE1
[10..99999] 60 [0..66],[0..100] 4,20
MOVEMENT-VOICE2
[0..66],[0..100] 5,20
MOVEMENT-VOICE3
[0..66],[0..100] 6,20
MOVEMENT-SMS
+451123344,+452233432
MOVEMENTVOICECALL
+4512345678
+451123344,+452233432
A list of phone numbers that are allowed to send SMS messages to the unit (see the section “System Commands”). The numbers MUST include the country code also. (The parameter “FLEXSERVER-SMS” is also checked). If set to “ALL”, all senders will be accepted. File and volume of the file to be played (”Powering unit off”) 0: Function disabled 1 Function active. The red function button must be activated in a period given by DEADMAN-TIME or adeadman alarm will be sent (see below) The interval (in seconds) the red function button must be activated or a deadman alarm is sent Is the delay time in seconds where beeps (DEADMAN-VOICE1) are played before activating the alarm. File and volume of the file to be played (”beep”) File and volume of the file to be played (”Deadman alarm has been sent”) List of numbers to call if the Deadman function is activated One or more numbers that will receive the deadman alarm as SMS. Pre-text is "DEADMAN period exceeded" this can be changed with DEADMAN-TEXT The rest of the text is the same as for SOS-SMS The pre-text that will be added to DEADMANSMS. If the text is followed by a "/" only the text in the parameter is sent, otherwise position etc is added 0: Function disabled 1: TILT mode (see below) 2: NOMOVE mode (see below) The delay in seconds before being in alarm mode. File and volume of the file to be played (”Movement alarm will be sent in 10 seconds”) File and volume of the file to be played (”Movement alarm has been sent”) File and volume of the file to be played (”Movement alarm reset”) One or more numbers that will receive the movement alarm as SMS Pre-text is "MOVEMENT event" this can be changed with MOVEMENT-TEXT The rest of the text is the same as for SOS-SMS When a movement (tilt or deadman) occurs, a voicecall will be established to the number in this parameter
Page 18 of 47
Flextrack Lommy (Phoenix) Technical Description Version 0.73
www.flextrack.dk
Parameter
Value
MOVEMENT-TEXT
MOVEMENT
CHARGING-VOICE
[0..66],[0..100] 8,20
CHARGECOMPLETEVOICE GEOFENCE
[0..66],[0..100] 9,20
GEOFENCE-CFG
[0000]
* Description
[0/1/2]
GEOFENCE-CENTER GEOFENCE-RADIUS GEOFENCE-GIVEUP GEOFENCE-TIME
[100..99999] 1000 [0..99999] 60 [0..99999] 60
GEOFENCE-SMS
+451123344,+452233432
GEOFENCE-OUTTEXT
OUTSIDE-ZONE
GEOFENCE-IN-TEXT
INSIDE-ZONE
GEOFENCE-VOICE1
[0..66],[0..100] 10,20
GEOFENCE-VOICE2
[0..66],[0..100] 11,20
GEOFENCE-VOICE3
[0..66],[0..100] 12,20
GEOFENCE-VOICE4
[0..66],[0..100] 13,20
DOUT1 DOUT2 DIN1-SMS
+451123344,+452233432
DIN2-SMS
+451123344,+452233432
The pre-text that will be added to MOVEMENTSMS. If the text is followed by a "/" only the text in the parameter is sent, otherwise position etc is added File and volume of the file to be played (”Currently charging”) File and volume of the file to be played (”Charging complete”) 0: Function disabled 1: Manual mode, geofence enabled 2: Auto mode, will follow input 1 of the option 2 board (Only some models) See below the table for a description. Configuration of the various Geofence features (G sensor enable etc) Centre in Lat/Lon of the geofence centre ("N55.38.1234,E009.12.2234") Radius of the geofence in meters Number fo seconds to wait for a GPS fix Number of seconds between Geofence checks (if GPS is not already powered on, it will be switched on for minumum GEOFENCE-GIVEUP seconds) List of numbers to send SMS to. Pre-text is either "Outside of geofence" or "Inside geofence". This can be changed with the parameters GEOFENCE-OUT-TEXT and GEOFENCE-IN-TEXT. The pre-text that will be added to GEOFENCESMS. The rest of the SMS is the same as POS. If the text is followed by a "/" only the text in the parameter is sent, otherwise position etc is added The pre-text that will be added to GEOFENCESMS. The rest of the SMS is the same as POS. If the text is followed by a "/" only the text in the parameter is sent, otherwise position etc is added File and volume of the file to be played (”Geofence activated”) File and volume of the file to be played (”Geofence deactivated”) File and volume of the file to be played (”Outside geofence zone”) File and volume of the file to be played (”Inside geofence zone”) If defined, the value it is set to, plus ":ON"/":OFF" will activate/deactivate the digital output 1 on an OPT2 board If defined, the value it is set to, plus ":ON"/":OFF" will activate/deactivate the digital output 2 on an OPT2 board Number(s) to send message to when DIN1 changes state Number(S) to send message to when DIN2 changes state
Page 19 of 47
Flextrack Lommy (Phoenix) Technical Description Version 0.73
www.flextrack.dk
Parameter
Value
DIN1-HIGH-TEXT
DIN1 is high
* Description
DIN1-LOW-TEXT
DIN1 is low
DIN2-HIGH-TEXT
DIN2 is high
DIN2-LOW-TEXT
DIN2 is low
IDLE-TIME1
[0..99999] 60
IDLE-TIME2
[0..99999] 60
IDLE-SPEED
[0..99999] 0
CHARGER-SMS
+451123344,+452233432
BATT-LEVEL
0..9999
BATT-SMS
+451123344,+452233432
SMSLOWBAT LOWBAT-VOICE
+451123344,+452233432 [0..66],[0..100] 7,20
MOVE-WAKEUP
[0/1]
MOVE-TIMEOUT
[0..99999] 300
MOVE-SENSITIVITY
[100..6000] 1000
SOS-NOWAIT
[0/1]
REPORT-STARTUP
[0/1]
Text to send when DIN1 goes high on the OPT2 board Text to send when DIN1 goes low on the OPT2 board Text to send when DIN2 goes high on the OPT2 board Text to send when DIN2 goes low on the OPT2 board Number of seconds the reported GPS speed must be above the value in "IDLE-SPEED" for bit 15 in the unitstate to be '1' Number of seconds the reported GPS speed must be below the value in "IDLE-SPEED" for bit 15 in the unitstate to be '0' Speed in km/hour for the "moving bit" to be set in unitstate (bit 15). If set to "0", no detection is active (bit 15 is always '0') List of numbers an SMS is sent to whenever the charger is connected/disconnected (new state must be stable for at least 30 seconds before message is sent) Whenever the voltage goes below the value defined in "BATT-LEVEL" (value is mV) a SMS message is sent to the list of numbers in "BATTSMS". The detector is armed again when the voltage goes 200 mV above the "BATT-LEVEL" LOWBAT-VOICE message will be played when the battery level is below BATT-LEVEL List of numbers to send an SMS to if battery voltage goes below "BATT-LEVEL" List of numbers to send "Low battery" message to Voice message to play when battery level goes low. If set to '1' and the unit is moved more than "MOVE-SENSITIVITY", the unit will poweron for "MOVE-TIMEOUT" number of seconds before powering off again. If unit is moved with the "MOVE-TIMEOUT" period, the time is "restarted" When using this function, the NOMOVE and TILT functions can not be active (and vice-versa) Number of seconds the unit will be active if powered on because of "MOVE-WAKEUP" feature Number of mG of movement (minimum 100) before the unit is turned on (if "MOVEWAKEUP" is set to '1') If set to '1' and the red button is pressed, the UNITSTAT (and fleetman) reports are send regardless if there is a GPS fix, and before a configured voicecall/sms is sent If set to '1', a unitstat is sent when the device is powered on. Ex. to be used with CYCLIC
Page 20 of 47
Flextrack Lommy (Phoenix) Technical Description Version 0.73
www.flextrack.dk
Parameter
Value
* Description
CONF-SERIAL BUTTON-VOICE
[0..66],[0..100] 14,20
LPOS-PREFIX
OPT-CFG
[00000000..FFFFFFFF] 00000000
BEACON
[0/1/2/3]
REPORT-INTERVALSMS-VOICE STEALTH
[0..99999] 1800
SUPERCAP
[0/1]
AUTOSTARTCHARGE
[0/1/2/3/4]
CHARGENOTCOMPL ETE-VOICE
[0..66],[0..100] 15,20
[0/1]
This is a 5 digit number, whenever a SAVEPARAM is executed, this number is incremented with 1 by the unit Voice message to play when one of the buttons are pressed The prefix to put before the response (always prefixed with "http://") back to the LPOS command (typically something like "www.something.com/position.php?") This is a hex number setting different options on the OPT2 board present in some Pro models bit 0: enables the OPT2 borard bit 1: Input 2 will mimic the function button bit 2: Input 3 will mimic button 1 bit 3: Input 4 will mimic button 2 bit 6: Output 1 will be grounded when a phone call is in progress bit 7: The powersupply (which we charge our battery from) is shut off when charging is complete, and on when the battery level goes below 3.9V If set to '1' beacon will transmit on 433.92 MHz, if set to '2' beacon transmits on 868.2 Mhz. The frequency is hardware dependent 4X1X are 433.92 MHz models and 4X2X are 868.2 Mhz. It sends data at 1200 baud, FSK modulation (sends 20 bytes, first 10 bytes is serial number followed by 10 bytes with a value of 0) The transmission is started/stopped using the command BEACON If set to '3' it's in RFID mode. Number of seconds between SMS reports when voicecall is in progress When set to '1' and the ”red function button” is pressed, the unit will call the number in SOSPHONE (See description) When set to '1', the low battery warning is lowered by 0.15V. Only to be used if the supercap hardware is present. This is only possible in the Personal model. Specify what the unit should do if charger is connected: 0: Unit should stay off (if off) 1: Unit should turn on (if off) 2: Unit should switch off (if on) 3: Unit switches on when charger is disconnected, and off when charger connected 4: Unit switches off when charger is disconnected, and on when charger connected Voice message to play in the speaker if the charger is removed while the battery is not fully charged.
Page 21 of 47
Flextrack Lommy (Phoenix) Technical Description Version 0.73
www.flextrack.dk
Parameter
Value
* Description
DTMF-ID
[NODEID/0-9/A-D/*,#
PREFERREDOPERATORS
23801,23802,24012,3101 12,24112
SHARPTURN
[0..20],[0..360] [0,0]
OPT-REPORTINTERVAL ODOMETER
[0..99999] 0
OPT-THRESHOLDS
[0..60000],[0..60000], [0..60000],[0..60000]
GSM-RESTART
[0..99999] [86400]
SMS-SCA
+4540590000
VIBRATE
[0/1..5]
REPORT-INTERVALIGN WOLF-REPORTINTERVAL WOLF-TIMEOUT
[10..99999] 120
When parameter DTMF-ID is set to "NODEID", the units serialnumber/nodeid will be sent as a series of DTMF touch tones whenever the unit establishes (initiates) a voicecall, if set to something else (.ex "1234") this is sent as a DTMF string. List of up to 36 providers in the format MMMNNN where the MMM is countrycode and NNN is providerid (NNN is 2 digit in Europe, 3 digits used in US). * Number of positions and degrees in a (sharp)turn that will initiate a UNITSTAT report. If set to 0,0 the feature is disabled. The first number is the number of positions between the directions are compared, if parameter is set to "5,30", the first and the 5. position is being compared, if there is more than 30 degrees change, a report is generated Sets the number of seconds between reports of analog values of a OPT2 board Controls the odometer function. If set to '0', the odometer value is omitted from the UNITSTAT message (and no longer updated internally). If the parameter is set to '1', the odometer value is updated (every 10 seconds) as long as input 1 is active (high) on the OPT2 board. If set to '2', the odometer value is calculated continuously (every 10 seconds) regardless of the input Set the number of millivolts for each of the 4 analog inputs on the OPT2 board for active high state ex: "12000,10000,8000,8500" This sets the active high state for the 4 inputs to 12,10,8 and 8.5 volts. If the value is blank defaults are used (8V) Number of seconds between forced resets of the GSM module (some networks will detach the GSM module if no activity for a long period) ex: "86400" this sets the restart period to 24 hours * This can be set to the phonenumber of the SMS center if the default of the SIM card is not to be used Set this to a value between '1' and '5' if the vibrate module is installed (Note: OPT-CFG has to be 0 if vibrate module is installed!) '1' is fastest, '5' is slowest vibration. This value will be used instead of REPORTINTERVAL if input 1 (Ignition) is active Number of seconds between the WOLF-ALIVE message is sent to the server Sets the maximum number of seconds that a wolf tag is not heard before WOLF-REMOVED message is sent to the server
[0..2] 0
[0..99999] 3600 [10..99999] 120
Page 22 of 47
Flextrack Lommy (Phoenix) Technical Description Version 0.73
www.flextrack.dk
Parameter
Value
* Description
NO-ROAMING
[0/1]
POS-DECDEG
[0/1]
BEACON-INTERVAL
[0..99999] 0
* if set to '1' and the PREFERRED-OPERATOR list is defined, and none of the providers in the list can be used, no reports are being sent (both FlexCI, Flexstream and SMS) (Reports are inserted in the circular buffer if defined) If NO-ROAMING is set to 0, the list of operators will be tried first, if none of the providers in the list are available, the unit does an "automatic" attach to one of the available providers in the network * If set to '1', decimal degress is added to the response on all "POS" messages * Number of seconds between transmission of "connected tag in panic" messages when BEACON:ON command is received
Page 23 of 47
Flextrack Lommy (Phoenix) Technical Description Version 0.73
www.flextrack.dk
Please note that the “APN”, “USERNAME”,” PASSWORD” and “DNS” are specific for the individual GSM provider. Parameters marked with a * (asterisk) will only be effective when the unit is reset (this requires the current set of parameters to be saved with the “SAVEPARAM”) Message sent if SOS-SMS, SOS-SMS1 or SOS-SMS2 is set, and the function button is pressed: The Lat/Lon information, is from the last time the GPS receiver got a position fix: PANIC Time=05-10-24 12:22:32 Lat=N55.33.22 Lon=E009.38.06 Speed=120Km/H Direction=112Deg Sats=8
if GPS receiver did not get a valid position fix: PANIC No fix, last fix: Time=05-10-24 12:22:32 Lat=N55.33.22 Lon=E009.38.06 Speed=120Km/H Direction=112Deg Sats=8
The pre-text PANIC can be changed with the SOS-TEXT, SOS-TEXT1 & SOS-TEXT2 parameters. If the text ends with a slash "/" only the SOS-TEXT(x) will be sent FLEXSERVER-IP → FLEXSERVER-IP-SEC failover If the parameter FLEXSERVER-IP is defined with a valid server address, the unit will attempt to make a socket connection shortly after powering up. A failover server can be defined in FLEXSERVER-IP-SEC, so the unit will connect to that if the primary server fails to respond. The connection attempts will be made in this order: Only FLEXSERVER-IP is defined: The unit will try to connect 3 times with 15 seconds interval, then 3 times with 120 seconds interval. After that the GSM module will be reinitialized and the connection attempts will start over again. Both FLEXSERVER-IP and FLEXSERVER-IP-SEC is defined: The unit will try to connect 3 times with 15 seconds interval, then 2 times with 120 seconds interval. Then it will try 6 times with 15 seconds interval on the secondary server. After that the GSM module will be reinitialized and the connection attempts will start over again.
Page 24 of 47
Flextrack Lommy (Phoenix) Technical Description Version 0.73
www.flextrack.dk
GSM-INFO: Returns info for serving cell and data for (upto) 6 neighbour cells format: Serving cell in first line: MCC, MNC, LAC, CI, Channel, RX Level Then 6 lines, each with a neighbour cell: LAC, CI, Channel, RX Level Example: 238,2,0059,7820,93 <= Serving cell 0059,8220,76,89 <= Neighbour 1 0059,7565,161,90 <= Neighbour 2 0059,5A56,82,95 . 0000,0000,0,0 . 0000,0000,0,0 . 0000,0000,0,0 <= Neighbour 6
18
RX Level are absolute and should be treated as negative values. TILT: If MOVEMENT is set to 1 tilt mode is enabled When the Lommy is tilted more than 70 degrees from vertical, the timer for MOVEMENT-TIME is started. When the timer has exceeded MOVEMENT-VOICE1 is played and after 10 seconds the alarm is sent (MOVEMENT-SMS and/or bit 11 in the unit state) and MOVEMENT-VOICE2 is played. If the Lommy is placed vertical again before the timer exceeds the voice file MOVEMENTVOICE3 is played and the timer for MOVEMENT-TIME is reset. NOMOVE: If MOVEMENT is set to 2 nomove mode is enabled When the Lommy hasn't moved in the period set with MOVEMENT-TIME the voice file MOVEMENT-VOICE1 is played. After 10 seconds MOVEMENT-VOICE2 is played and the alarm is sent (MOVEMENT-SMS and/or bit 11 in the unit state). If the Lommy moving again before the timer exceeds the voice file MOVEMENT-VOICE3 is played and the timer for MOVEMENT-TIME is reset. DEADMAN switch: If DEADMAN is set to 1 the deadman switch function is enabled. When the DEADMAN-TIME period has expired DEADMAN-VOICE1 will be played and the DEADMAN-WARNING timer starts. In this period the alarm can be reset by pressing the red function button. If not reset DEADMAN-VOICE2 will be played and the alarm will send (DEADMAN-SMS and/or bit 12 in the unit state is raised). If SOSPHONE and/or SOS-SMS is defined the alarm can only be reset in the DEADMANWARNING period If SOSPHONE and SOS-SMS is undefined and bit 12 in the STATEMASK is 0, the period can be reset in both the DEADMAN-TIME and DEADMAN-WARNING period. Page 25 of 47
Flextrack Lommy (Phoenix) Technical Description Version 0.73
www.flextrack.dk
GEOFENCE, manual mode (GEOFENCE = 1) In Manual mode, the centre (latitude/longitude) of the Geofence is set either by the GEOFENCECENTER parameter, or by sending the GEOFENCE-SET command to the unit. If the centre is set using the GEOFENCE-SET command, the Geofence function will switch the GPS receiver on, and try to get a valid fix within the number of seconds set by GEOFENCE-GIVEUP parameter. The parameter MAX-HDOP sets the maximum HDOP (Horizontal Dilution Of Precision) that is allowed before the GPS position is taken as "valid" (high enough precision). If the position becomes valid, it will be stored in the GEOFENCE-CENTER non-volatile parameter in the device, and it will be used as the centre until a new position is set either using the GEOFENCE-SET command or the GEOFENCE-CENTER parameter is changed. If the position does not become valid with the number of seconds set by parameter GEOFENCEGIVEUP, the Geofence function will not do any further checking of the position (effectively disabled) If a valid fix was obtained, and the centre therefore was set, the Geofence function will check the current position each GEOFENCE-TIME number of seconds. When the check is to be performed, the function will wait a maximum of GEOFENCE-GIVEUP number of seconds for a valid fix (that obeys the MAX-HDOP value). If no valid fix is obtained within the GEOFENCE-TIME period, the check will be aborted, and the function will again wait GEOFENCE-TIME number of seconds before making another test if the position is within the specified geofence (centre/radius). If either the GEOFENCE-SET command is received or the GEOFENCE-CENTER parameter is changed, a new new centre position will be used in subsequent checks When checking if the current position is within the specified circle, the following steps are performed (same procedure as in Auto mode): 1) If the position in within the specified radius, the position is regarded as "within limits", and the position is reported as "inside the geofence" 2) If the position is outside the specified radius, but inside the calculated "outer radius", the GPS will continue to "run", and the position is checked 10 times (12 seconds between each check) and if the position does not come inside the specified radius any of the 10 times it is checked, the position is "outside limits", and a report is generated. "Outer radius" is calculated as: if GEOFENCERADIUS is less than 1000 meters, then "outer radius" is 2 x GEOFENCE-RADIUS, else it's GEOFENCE-RADIUS x 1,20 3) If the position is outside the calculated "outer radius", the GPS will continue to "run", and the position is checked 2 times (12 seconds between each check) and if the position does not come inside the specified radius any of the 2 times it is checked, the position is "outside limits", and a report is generated. After the device have determined that it's "outside" and a report is generated, the current position Page 26 of 47
Flextrack Lommy (Phoenix) Technical Description Version 0.73
www.flextrack.dk
needs to be 10 % closer to the centre than the inner circle (if radius is set to 1000 meter, we have to be within 900 meters of the centre in order to re-arm the geofence function again) When the position is outside the geofence zone bit 13 in the unit state will be raised Bit 14 is raised when the geofence checking is active (if a centre has been acquired or set). GEOFENCE, auto mode (GEOFENCE = 2) In Auto mode, the Input 1 input on the OPT2 board is used as the "activation" signal for the Geofence function. When the input 1 signal is at a high level (typically signalling that a car is driving) no check is performed. When the input 1 signal goes to a low level (the car is stopped, ignition is removed) the unit will try for GEOFENCE-GIVEUP number of seconds to get a valid fix. The parameter MAX-HDOP sets the maximum HDOP (Horizontal Dilution Of Precision) that is allowed before the GPS position is taken as "valid" (high enough precision). When the position becomes valid, it will be stored non-volatile internally in the device, and it will be used as the centre. If the position does not become valid with the number of seconds set by parameter GEOFENCEGIVEUP, the Geofence function will not do any checking of the position (effectively disabled) If a valid fix was obtained, and the centre therefore was set, the Geofence function will check the current position every GEOFENCE-TIME number of seconds for the first 24 hours. After the first 24 hours, the check will be performed every 15 minutes for power saving. When the check is to be performed, the function will wait a maximum of GEOFENCE-GIVEUP number of seconds for a valid fix (that obeys the MAX-HDOP value). If no valid fix is obtained within the GEOFENCE-TIME period, the check will be aborted, and the function will again wait GEOFENCE-TIME number of seconds (or 15 minutes if within the first 24 hours of activation) before making another test if the position is within the specified geofence (center/radius). If bit 0 in GEOFENCE-CFG is set to '1', then the function will make a check for the postion if the G sensor signals movement (more than +/- 200 mG) If either the GEOFENCE-SET command is received or the GEOFENCE-CENTER parameter is changed, a new new center position will be used in subsequent checks (the center position will be overwritten on the next high to low transition of the Ignition signal) When checking if the current position is within the specified circle, the following steps are performed (same procedure as in Manual mode): 1) If the position in within the specified radius, the position is regarded as "within limits", and the position is reported as "inside the geofence" 2) If the position is outside the specified radius, but inside the calculated "outer radius", the GPS will continue to "run", and the position is checked 10 times (12 seconds between each check) and if Page 27 of 47
Flextrack Lommy (Phoenix) Technical Description Version 0.73
www.flextrack.dk
the position does not come inside the specified radius any of the 10 times it is checked, the position is "outside limits", and a report is generated. "Outer radius" is calculated as: if GEOFENCERADIUS is less than 1000 meters, then "outer radius" is 2 x GEOFENCE-RADIUS, else it's GEOFENCE-RADIUS x 1,20 3) If the position is outside the calculated "outer radius", the GPS will continue to "run", and the position is checked 2 times (12 seconds between each check) and if the position does not come inside the specified radius any of the 2 times it is checked, the position is "outside limits", and a report is generated. After the device have determined that it's "outside" and a report is generated, the current position needs to be 10 % closer to the centre than the inner circle (if radius is set to 1000 meter, we have to be within 900 meters of the centre in order to re-arm the geofence function again) When the position is outside the geofence zone bit 13 in the unit state will be raised Bit 14 is raised when the geofence checking is active (if a centre has been acquired or set). STAT-IO: Returns status of in- and outputs of a device, if model is equipped with an OPT2 board (OPT-CFG, 1) ex. response: IO Status: In(1)=Not active In(2)=Not active In(3)=Not active In(4)=Not active Out(1)=Not active If no OPT-2 boards "No optionboard installed" is returned. STEALTH: If STEALTH is set to 1 stealth mode is enabled. If the ”red button is pressed”, the unit will keep call the number in SOSPHONE and the speaker will be silent in 20 second after the call has been answered. On models with vibrator, the vibrator will be active while the call is in progress. PREFERRED-OPERATORS: Rules for preferred provider list: In the list PREFERRED-OPERATORS (PO in the following explanation) all the preferred operators are listed (the first operator is the one with the highest priority etc.). The list looks like this: 23801,23802,24012,310112,24112 If the unit is Roaming, every 5 minutes the unit will ask for a list of currently "online" providers Page 28 of 47
Flextrack Lommy (Phoenix) Technical Description Version 0.73
www.flextrack.dk
that can be heard by the unit. The unit then goes through the configured PO list, one entry at a time. For every entry it checks if the entry is in the "on-line" list (and marked as "allowed"), if the entry in the PO list is "on-line", the unit will attempt to use that provider. (If the GSM command fails, the unit will just ask for "automatic" provider selection). If no provider from the PO list is on-line, the unit will just do a automatic selection of the provider. If the PO entry is the one the unit is currently connected to, the unit will not look further in the list of PO's, but just stay connected to this provider In the above example (with the PO list configured as shown), the following scenario will happen: The providers 23801 and 23802 are both listed as "on-line" and allowed (for the SIM card used) The unit will then make a connection to 23801 as this is the first entry in the list (before 23802). The next time the unit checks the currently on-line providers, it will see that it is already is connected to 23801, so nothing will happen, it will just stay connected to this provider If for some reason, the 23801 provider is no longer "on-line" (maybe out of reach), the unit will see that 23802 is on-line (and allowed), and connect to that one. If no of the entries in the PO list is currently on-line, the unit will just do a automatic selection of the available providers. If NO-ROAMING, if set to '1' and the PREFERRED-OPERATOR list is defined, and none of the providers in the list can be used, no reports are being sent (both FlexCI, Flexstream and SMS) 1-WIRE: The device supports temperature sensors and a driver id "button" on the 1wire bus. All devices has a 8 byte id, this is normally written as 8 groups of 2 digits: 00 01 3E FE 00 28 00 8D, in all commands the space between each digit is removed, so in all communications (reports and configuration) the device id will be sent like: 99913EFE0028008D Temperature sensors. The device supports up to 8 temperature sensors. Each sensor can be configured with a minimum and a maximum allowed temperature. If one of these are exceeded, an report will be generated to the server (just like the UNITSTAT report). The id's of the sensors as well as the minimum and maximum temperatures can be configured. All connected sensors will report their current temperatures (as well as their high/low alarm states) with a specified (configurable) interval. The unit will also trigger the transmission of a UNITSTAT message if bit 24 is set in the STAMEMASK parameter! Driver ID. The device can hold up to 80 different driver id's in a list. Whenever the device discovers a connected driver id button, it will search this list for the specific driver id. An report will be generated and sent to the server (containing the driver id and status for the search Page 29 of 47
Flextrack Lommy (Phoenix) Technical Description Version 0.73
www.flextrack.dk
result). If the driver id is present in the list, one of the digital outputs (configurable) be active for 10 seconds. The unit will also trigger the transmission of a UNITSTAT message whenever a driver id is connected/disconnected if bit 23 is set in the STAMEMASK parameter! The device number for driver id's is written on the small metal can like this: 8D 01 000011B215B2 The format to write this number is: 01B215B21100008D examples of reports: OWDID-DISCOVER,20080617,170715,1122334455667788,03 The device 1122.. is now connected, and it is present in the configured list of driver id's then the device is removed, the following message is sent: OWDID-DISCOVER,20080617,170715,1122334455667788,00 The device 1122.. is now disconnected OWDID-DISCOVER,20080617,170715,2345667711223344,01 The device 2345.. is now connected, and it is not present in the configured list of driver id's then the device is removed, the following message is sent: OWDID-DISCOVER,20080617,170715,2345667711223344,00 The device 2345.. is now disconnected OWTEMP-REPORT,20080617,170715,1122334455667788,-105,01,1234556677889900,230,05 The first sensor reports -10.5 deg, it is responding, and no alarms The second sensor reports 23.0 deg, it is responding, and has a "high temperature" alarm
Page 30 of 47
Flextrack Lommy (Phoenix) Technical Description Version 0.73
www.flextrack.dk
Voice files The voice files can be recorded with ex. the standard "Sound Recorder" found in Windows (Accessories -> Entertainment)
When saving the file select "File -> Save As..." select the button Format "Change..." and choose the format 8kHz; 8 Bit; Mono.
This is the only correct format for the Lommy The files can be downloaded to the Lommy using Pconfig "File -> Upload voicemessages.." It takes a cfg-file containing the index number and path for the wav-file.
Page 31 of 47
Flextrack Lommy (Phoenix) Technical Description Version 0.73
www.flextrack.dk
Here is the content of the standard file: ; ----------------------------------------------; Voice messages configuration for Phoenix device ; ----------------------------------------------1,C:\PConfig\voicefiles\poweroff.wav 2,C:\PConfig\voicefiles\beep.wav 3,C:\PConfig\voicefiles\deadman-alarm-sent.wav 4,C:\PConfig\voicefiles\movement-alarm-warning.wav 5,C:\PConfig\voicefiles\movement-alarm-sent.wav 6,C:\PConfig\voicefiles\movement-alarm-reset.wav 7,C:\PConfig\voicefiles\battery-low.wav 8,C:\PConfig\voicefiles\currently-charging.wav 9,C:\PConfig\voicefiles\charging-complete.wav 10,C:\PConfig\voicefiles\geofence-activated.wav 11,C:\PConfig\voicefiles\geofence-deactivated.wav 12,C:\PConfig\voicefiles\outside-geofence-zone.wav 13,C:\PConfig\voicefiles\inside-geofence-zone.wav 14,C:\PConfig\voicefiles\beep.wav 15,C:\PConfig\voicefiles\beep.wav
The index number is the first value in the VOICE parameters. The second value is the level 0-100 where 0 is max and 100 is min.
Page 32 of 47
Flextrack Lommy (Phoenix) Technical Description Version 0.73
www.flextrack.dk
Status messages The UNITSTAT message consists of a number of fields, each separated by a comma. This message is sent from the unit either at a fixed interval (see parameter “REPORT-INTERVAL”), when there is a state-change in the unit (the state-change is compared against a mask, see parameter “STATEMASK”), or when an operator initiated voice call is ended (in that case, bit 4 in “Unit State” will be set). The message contains the following fields: Field
Example
Description
UNITSTAT Date [YYYYMMDD] Time [HHMMSS] NodeID Latitude [DD.MM.DECM]
UNITSTAT 20050205 181923 7000004634 N55.46.0812
Longitude [DDD.MM.DECM]
E9.21.1665
Speed Direction SV Voltage Signal strength
122 198 6 3934 -81
Unit State
01A8
Current network
23802
Height HDOP
213 332
CellID
12FE
Elapsed time for GPS fix
45
Locacion Area Code (LAC) Odometer
0055 12989
Identifies the message The date The time in UTC The Flextrack unit’s nodeid The latitude in degrees, minutes and decimal minutes (a leading “N” or “S” identifies the position as north or south of the equator) The longitude in degrees, minutes and decimal minutes (a leading “E” or “W” identifies the position as east or west of Greenwich) Speed over ground in kilometers per hour The compass heading in degrees Number of GPS satellites used for position fix Current voltage of the LiIon battery in mVolts Current signal strength of the GSM basestation in dBm State of inputs and various states, coded as 8 ASCII Hex digits (32 bits). A detailed description of the field can be found below. Country code (3 digits) and GSM provider code (2 digits) Meters above sea level (MSL) The current HDOP value (multiplied with 10, 213 equals 21.3) The cell id of the current GSM basestation, 4 hex digits The elapsed time for getting a GPS fix after going to report The LAC from the GSM network Odometer value calculated and shown if parameter ODOMETER is set.
Example: UNITSTAT,20050205,181923,7000004634,N55.46.0812,E009.21.1665,122,198,6,3934,81,01A8,23802,213,55,37FD,45,0055,12878
Page 33 of 47
Flextrack Lommy (Phoenix) Technical Description Version 0.73
www.flextrack.dk
Unit State field Contents of the “Unit State” field (same definition as for the STATEMASK parameter): Bit
Description
29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
BEACON is active A RFID tag (wolf) has been heard A known RFID tag (sheep) has been heard or lost A RFID tag (sheep) in panic has been heard A SHARPTURN is detected 1-Wire temperature alarm 1-Wire Driver ID is connected DOUT2 state on a OPT2 board is active DOUT1 state on a OPT2 board is active Input port 4 is high (above 8V) (OPT2) Input port 3 is high (above 8V) (OPT2) Input port 2 is high (above 8V) (OPT2) Input port 1 is high (above 8V) (OPT2) Unit is in motion Geofence active Outside geofence zone DEADMAN alarm active MOVEMENT alarm active Button 2 has been pressed (Only on some models) Button 1 has been pressed (Only on some models) Unable to get current GPS fix, so sending last good (if “LASTGOOD” is set to 1) Voicecall is active Leading edge detected on the Aux signal (only if “AUX-ENABLE” is set to 1) Trailing edge detected on the Aux signal (only if “AUX-ENABLE” is set to 1) Function button pressed (whenever this bit is set and the Function button is pressed, a UNITSTAT message is sent) The state of the input signal (if “AUX-ENABLE” is set to 1) Battery low voltage detected if ‘1’ Charging state 00: No charger connected 01: Charger connected (but not charging) 10: Charging in progress 11: Charging complete The state 01 will only be seen once, after that, the state will change between 10 and 11.
Page 34 of 47
Flextrack Lommy (Phoenix) Technical Description Version 0.73
www.flextrack.dk
The OWDID-DISCOVER message is sent when an iButton is detected on the 1-Wire bus The message contains the following fields: Field
Example
Description
OWDID-DISCOVER Date [YYYYMMDD] Time [HHMMSS] HW Address Status
OWDID-DISCOVER 20050205 181923 aabbccddeeffgghh 00
Identifies the message The date The time in UTC The hardware address of the iButton seen Binary representation of State of inputs and various states, coded as 2 ASCII Hex digits. bit0 is raised when a device has been connected and read bit 1 is raised when the device read were found in the list of stored devices (OWDID-INSERT) Bit 23 in the STATE field of the UNITSTAT message is also set while a driverid is connected
Example:
OWDID-DISCOVER,20080820,090623,000012066D3A,00
Page 35 of 47
Flextrack Lommy (Phoenix) Technical Description Version 0.73
www.flextrack.dk
The OWTEMP-REPORT message is a temperature report, sent every OWTEMP-REPORT-INTERVAL number of seconds. The message contains the following fields: Field
Example
Description
OWTEMP-REPORT Date [YYYYMMDD] Time [HHMMSS] HW Address
OWTEMP-REPORT 20050205 181923 aabbccddeeffgghh
Temp
200
Status
01
Identifies the message The date The time in UTC The hardware address of the temperature sensor Current temperature in 1/10 degree Celcius (shown as 0 if device does not respond, status value is 00) status field (binary coded), and is coded as follows: bit 0: Is 1 if device is responding bit 1: Is 1 if low temperature alarm bit 2: Is 1 if high temperature alarm Bit 24 in the STATE field of the UNITSTAT message is also set
The fields HW Address, Temp & Status are continued the number of sensors configured. Example:
OWTEMP-REPORT,20080820,090623,289D7C6C01000080,225,01
Page 36 of 47
Flextrack Lommy (Phoenix) Technical Description Version 0.73
www.flextrack.dk
The OPT-STATUS message is a temperature report, sent every OPT-REPORT-INTERVAL number of seconds. The message contains the following fields: Field
Example
Description
OPT-STATUS Date [YYYYMMDD] Time [HHMMSS] Input 1 Input 2 Input 3
OPT-STATUS 20050205 181923 58 0 0
Input 4
60
AVal 1
2345
AVal 2
123
AVal 3
0
AVal 4
0
Identifies the message The date The time in UTC The analog value measured on input 1 The analog value measured on input 2 The analog value measured on input 3 (Only in Pro models) The analog value measured on input 4 (Only in Pro models) Accumulated time port 1 has been high (min) Accumulated time port 2 has been high (min) Accumulated time port 3 has been high (min) Accumulated time port 4 has been high (min)
The values measured are in the range 0-255 for the voltage range 0-60V So 60 reported is (60 / 255) * 60 = 14,1V Example:
OPT-STATUS,20080820,090623,58,0,0,60,2345,123,0,0
Page 37 of 47
Flextrack Lommy (Phoenix) Technical Description Version 0.73
www.flextrack.dk
The WOLF-HEARD message is sent when a RFID tag (model 0A1) is entering the range of a Lommy. The Lommy is only listening for tags is BEACON is set to 3. If STATEMASK bit 28 is set to '1', a UNITSTAT report is also generated The message contains the following fields: Field
Example
Description
WOLF-HEARD Date [YYYYMMDD] Time [HHMMSS] Tag ID RSSI
WOLF-HEARD 20090923 115745 0938000011 -91
Identifies the message The date The time in UTC ID of the tag heard Signal strength of the signal received from the tag.
Example:
WOLF-HEARD,20090923,115745,0938000011,-91 The WOLF-ALIVE message will be sent if a RFID tag is still in range (WOLF-HEARD message has been sent previously). The interval in which the WOLF-ALIVE message is sent is set in parameter WOLF-REPORT-INTERVAL the message format Field
Example
Description
WOLF-ALIVE Date [YYYYMMDD] Time [HHMMSS] Tag ID RSSI
WOLF-ALIVE 20090923 115745 0938000011 -91
Tag ID .... RSSI ....
.... ....
Identifies the message The date The time in UTC ID of the tag heard Signal strength of the signal received from the tag. Field Tag ID and RSSI are repeated for each tag in the list of heard devices
Example:
WOLF-ALIVE,20090923,115745,0938000011,-91,0932000021,-83 The WOLF-REMOVED message is sent when a RFID tag (model 0A1) was previously in range of this Lommy, but haven't been heard for the period given in WOLF-TIMEOUT. If STATEMASK bit 28 is set to '1', a UNITSTAT report is also generated The message contains the following fields: Field
Example
Description
WOLF-REMOVED Date [YYYYMMDD]
WOLF-REMOVED 20090923
Identifies the message The date
Page 38 of 47
Flextrack Lommy (Phoenix) Technical Description Version 0.73
www.flextrack.dk Time [HHMMSS] Tag ID
115945 0938000011
Example:
WOLF-REMOVED,20090923,115945,0938000011
Page 39 of 47
The time in UTC ID of the tag heard
Flextrack Lommy (Phoenix) Technical Description Version 0.73
www.flextrack.dk
FlexCI communication protocol The FlexCI protocol is described at both “low-level” and “high-level”. The low-level description explains the basic mechanisms that must be followed in order to transfer data between a Flextrack unit and a Server (or more general, between two “nodes”). The high-level description details the steps needed to establish a connection to the Server, this step is mainly issuing a “LOGON” command to the Server. To test the protocol when developing a backend, you can download a small "server" listening for incoming connections on port 30000. You will find the program here http://www.flextrack.dk/files/FlexCIServer.exe Low-level
FlexCI (Flextrack Communication Interface) is a TCP/IP based communication protocol, that handles the interface to and from the Flextrack units, typically from a PC based Server of some kind. The FlexCI protocol “rides” on normal TCP/IP sockets, which is supported on GPRS. FlexCI is ASCII based, all data and commands is pure ASCII. This makes it easy to handle in various Web applications, and also for testing purposes, as all information is human readable. The FlexCI protocol uses a single socket connection for the communication between the Flextrack unit and the Server. All commands consist of a transaction number (TNO) and some data. The data is of no interest to the FlexCI protocol itself, only the TNO is important (the data is simply passed to the application layer). Whenever a node wants to send something to the server, it starts by incrementing its current transaction number and then it sends the command. At the same time, it starts a timer. It will then “listen” for a message from the other node, with the same TNO as it used in the command it just sent. If the timer expires before a frame with the same TNO is received, it will report an error, and try to make a new connection to the server. It is important to notice, that only ONE command can be “in the air” at one time between the Flextrack unit and the Server, it is NOT allowed to send another command before the previous is either acknowledged or an timeout has occurred! The FlexCI protocol does not distinguish between the Flextrack unit and Server, both are just considered “nodes”. On some GSM networks it is necessary to send occasional “dummy communication” in order to keep the GPRS socket connection up and running. This communication simply consists of a . The character is sent after a number of seconds (for example 600 seconds) inactivity on the FlexCI communication channel (socket). When the Server receives an only, it should simply respond with a character.
Page 40 of 47
Flextrack Lommy (Phoenix) Technical Description Version 0.73
www.flextrack.dk Normal flow, no errors:
Node A sends two commands to Node B. Node B
Node A Send command xxx
”3311,xxx”
Execute command
Response received
”3311,ACK”
Send response
Send command yyy
”3312,yyy”
Execute command
Response received
”3312,ACK”
Send response
Normal flow, crossing messages:
Node A sends a command to Node B, and at the same time Node B send a command to Node A (effectively crossing each other before responses are received at each end) Node B
Node A Send command xxx
”3313,xxx”
Execute command
Execute command
”2311,zz”
Send command zz
Response received
”3313,ACK”
Send response
Send response
”2311,ACK”
Execute command
Page 41 of 47
Flextrack Lommy (Phoenix) Technical Description Version 0.73
www.flextrack.dk Abnormal flow, no response received:
Node A sends a command to Node B which sends a response that is NOT received at Node A. Node A resends the command to Node B (using the same TNO), and receives a response (it is also allowed to close and re-open the connection when the error occurs).
Node B
Node A Send command xxx
”3314,xxx”
Execute command
”3314,ACK”
Send response
Resend command xxx
”3314,xxx”
Same TNO, don’t execute again!
Response received
”3314,ACK”
Resend response
[Timeout receiving response]
Abnormal flow, command not received:
Node A sends a command to Node B, which does not receive the command. Node A gets a timeout receiving the response (which is never sent as Node A never received the command), and sends the command again (with the same TNO), this time it receives a response (it is also allowed to close and re-open the connection when the error occurs).
Node B
Node A Send command xxx
”3315,xxx”
Command not received
Resend command xxx
”3315,xxx”
Execute command
Response received
”3315,ACK”
Send response
[Timeout receiving response]
Page 42 of 47
Flextrack Lommy (Phoenix) Technical Description Version 0.73
www.flextrack.dk
High-level In order to establish a valid connection where commands can float in both directions, the Flextrack unit must make an “LOGON” sequence with the Server. Basically this just means that the Flextrack unit sends a “LOGON,nnnnnnnnnn,iiiiiiiiiiiiiiiiiiii” where the “nnnnnnnnnn” is the units 10 digit Node ID (typically the serial number of the unit) and ”iiiiiiiiiiiiiiiiiiii” is the ICCID number of the SIM-card. When the Flextrack unit receives an “ACK” on this command, it is connected, and further communication can follow between the Flextrack unit and the Server. Whenever a Flextrack unit is started, it will try to establish a socket connection to the defined Server. The Flextrack unit has to establish the connection, as the unit often sits behind the GSM operators Firewall, and therefore it’s not possible for the Server to establish the connection to the unit. When the Flextrack unit has created the connection, it must send a “LOGON” command to the Server, in order to identify itself. The logon command contains the Flextrack unit’s serial number and the ICCID number of the SIM-card. When the unit receives an acknowledge message from the Server, both ends are ready to communicate with each other. If either the Server or the Flextrack unit discovers that the communication is lost (socket closes or timeout on send/receive) it will initiate a socket close. The Flextrack unit will then discover this situation, and re-establish the connection (and make a new “LOGON” attempt). Whenever a Lommy unit is switched off by the user (or a RESET command is received from the server, the unit will send a DISCONNECT message to the server. This tells the server that the unit is about to close the socket connection in a “controlled” manner. Below you will see a typical scenario between a Lommy unit and a Server, beginning with the Lommy being switched on. Flextrack Logon
Server ”-1,LOGON,7000000123,8945000000”
Verify NodeID
”-1,ACK”
Send response
The Lommy is now registered at the Server Set parameter
”32,CONF:REPORT-INTERVAL,180”
Send response
”32,ACK”
Set new report-period
The Lommy sends status messages every 3 minutes (or when the masked status changes) Send status update
”-2,UNITSTAT,20050210,101112….”
”-2,ACK”
Page 43 of 47
Send response
Flextrack Lommy (Phoenix) Technical Description Version 0.73
www.flextrack.dk
HTTP GET Request The unit can send position reports to a server by using a standard HTTP GET request. The parameter “FLEETMAN” needs just to be set to a correct HTTP URL, and the unit will then automatically send data to the specified server. The layout of the HTTP GET request is as follows:
Field
Example
Description
Server adress
www.server.com/httpreceiver. dll
Node-ID Date/Time [YYYYMMDD] [HHMMSS] Latitude [DD.MM.DECM]
&node= 7000000637 &time=20050314122134
Longitude [DDD.MM.DECM]
&lon=E9.38.1330
Speed
&spd=89
Direction Height Elapsed time for GPS fix
&dir=211 &hgt=88 &ttf=45
SV
&sv=3
Voltage
&bat=3788
GPS quality
&hdop=16
CellID
&cid=12FE
Constant; identifies the message. This is the content of the “FLEETMAN” parameter. Nodeid of the unit sending the data The UTC date and time of the message The latitude in degrees, minutes and decimal minutes. A leading “N” or “S” identifies the position as north or south of the equator. The longitude in degrees, minutes and decimal minutes. A leading “E” or “W” identifies the position as east or west of Greenwich. Speed over ground in kilometers per hour The compass heading in degrees Meters above sea level (MSL) The elapsed time for getting a GPS fix after going to report Number of GPS satellites used for this position fix Current voltage of the Li-Ion battery in mVolts The hdop value is the actual hdop multiplied by 10, so "&hdop=16" is a hdop value of 1.6 The bigger the hdop value is, the less the precision of the LAT/LON values is. Basic accuracy of the GPS receiver used is 5 meters. Therefore an hdop value of 16 means a real accuracy for a given position report of 5m * 1.6 = 8 meters The cell id of the current GSM base station, 4 hex digits
Unit state
&lat=N55.46.5003
&state=2
Value of the unit state field
Page 44 of 47
Flextrack Lommy (Phoenix) Technical Description Version 0.73
www.flextrack.dk
Field
Example
Description
Location Area Code (LAC) Signal strength
&lac=0055 &rsi=-81
Current network
&prov=23802
Odometer value
&odo=47315
The LAC from the GSM network Current signal strength of the GSM basestation in dBm Country code (3 digits) and GSM provider code (2 digits) If parameter ODOMETER is set (different from '0') the string "&odo=nnnnn" will be added. (nnnnn is odometer length in meters), if ODOMETER parameter is set to '0', "&odo=" (blank value) will be added.
Page 45 of 47
Flextrack Lommy (Phoenix) Technical Description Version 0.73
www.flextrack.dk
Wiring the option 2 (OPT2) board Pin
Wire color
Connection
1 2 3 4 5 6 7 8 9 10
Pink Yellow Green
Analog Input port 4 (up to 60 VDC) Digital Output port 2 (Connects to ground when active) max. 500mA Analog Input port 3 (up to 60 VDC) N/A Dallas 1-Wire Bus Supply +10-60VDC - Ground Ignition / Analog Input port 1 (up to +60VDC) Analog Input port 2 (up to 60 VDC) Digital Output port 1 (Connects to ground when active) max. 500mA
Purple White Black Brown Grey Blue
The standard cable is assembled with wires for pin 6-10
Page 46 of 47
Flextrack Lommy (Phoenix) Technical Description Version 0.73
www.flextrack.dk
Technical specifications
Operation Battery (at 20 C)
Buttons Indicators
Connectors Audio
Personal: 2000 mA/H LiIon battery, giving approx 30 hours operation with position reports every 3 minutes (longer duration with longer times between position reports) Pro: 1000 mA/H LiIon battery, giving approx 20 hours operation with position reports every 3 minutes (longer duration with longer times between position reports) Function/On switch (big button on front), normally answers/initiates a voice call (Personal only) (also switches the unit on and off) Red indicator: Charge activity Green indicator: GSM activity Yellow indicator: Connected to server / power off indicator Blue indicator: GPS status Charge connector Mini-USB for charging and configuration Built-in loudspeaker and microphone (Personal)
GSM/GPRS Band Tri band (900/1800/1900 Mhz) or (850/1800/1900 MHz) Transmit power Class 4 (2W) at EGSM 900 Class 1 (1W) at GSM 1800Class 4 (2 W) for EGSM850 Class 4 (2 W) for EGSM900 Class 1 (1 W) for GSM1800 Class 1 (1 W) for GSM1900 GPRS Mobile station class B Class 10, PBCCH support. Antenna Built-in tri band antenna
GPS Receiver Sensitivity Antenna
16 Channel parallel Very High Sensitivity receiver Tracking: -158 dBm / -188 dBW High efficiency Helix antenna
Environmental Temperature range operating Material Dimensions Weight
-20 to +45 C (Charging of unit is to take place between 0 and +45 C) 1.5mm ABS Plastic Personal 74 x 61 x 23 mm (H x W x D) Pro 76/90 x 40 x 20 mm (L x W x D) Personal 99 g
Page 47 of 47
