Xirgo Technologies XT6360 Vehicle GPS/Cellular Tracking Device with BT User Manual

Xirgo Technologies Inc. Vehicle GPS/Cellular Tracking Device with BT

User Manual

Download: Xirgo Technologies XT6360 Vehicle GPS/Cellular Tracking Device with BT User Manual
Mirror Download [FCC.gov]Xirgo Technologies XT6360 Vehicle GPS/Cellular Tracking Device with BT User Manual
Document ID2621508
Application IDTYWDJQvUcBnIvV0zWYY2CQ==
Document DescriptionUser Manual
Short Term ConfidentialNo
Permanent ConfidentialNo
SupercedeNo
Document TypeUser Manual
Display FormatAdobe Acrobat PDF - pdf
Filesize30.87kB (385824 bits)
Date Submitted2015-05-21 00:00:00
Date Available2015-11-18 00:00:00
Creation Date2015-04-24 18:19:38
Producing SoftwareNitro Pro 9 (9. 0. 5. 9)
Document Lastmod2015-04-24 18:19:51
Document TitleUser Manual
Document CreatorNitro Pro 9 (9. 0. 5. 9)

XT6360 User Guide
Version 1.0
188 Camino Ruiz
Camarillo, CA 93012
www.xirgotech.com
support@xirgotech.com
Contents
Document Change History .......................................................................................................................... 2
Hardware Specification............................................................................................................................... 3
Connector IO Interface................................................................................................................................. 4
Cable Harness Specification........................................................................................................................ 6
LED Defentition ........................................................................................................................................... 7
Current Consumption ................................................................................................................................. 7
Device mounting.......................................................................................................................................... 7
PC Device Configuration ............................................................................................................................. 8
Feature Matrix ............................................................................................................................................. 8
Device Configuration................................................................................................................................... 9
Parameter File ........................................................................................................................................... 13
Messages.....................................................................................................................................................14
Script File ...................................................................................................................................................10
Parameter File ........................................................................................................................................... 13
Appendices…………………………………………………………………………………………………………………………………………..13
Regulatroy Statements..............................................................................................................................28
Sales Engineering
support@xirgotech.com
Document Change History
Revision
1.0
Date
4/24/2015
Sales Engineering
support@xirgotech.com
Changes
Initial Release (NB)
Sales Engineering
support@xirgotech.com
Hardware Specification:
Cellular Wireless Technology:
2G/GSM/GPRS/EGPRS: 850/900/1800/1900 Bands - Models: XT6360 / XT6355
3G (UMTS): 850/1900 Bands (Bands V, II) - Models: XT6360
CDMA (1xRTT): 850/1900 Bands - Models: XT6360
Parameter
GPS Specification
Receiver
Receiver tracking
sensitivity
Receiver Cold Start
CEP Accuracy
TTFF
- Cold Start
- Hot Start
HW Options:
3-axis Accel.
BT/BTLE
Last Gasp Back-up
Battery
Power Requirements
D.C. Power
Physical Connection
Data Connector
Antenna:
Cellular/GPS /BT
SIM Access (2G/3G)
Programming
Mechanical
Case Material
Dimension
Weight
Operating
Temperature
Certifications
Product
Notes:
Sales Engineering
support@xirgotech.com
56 channels
-162 dBm
-148dBm
+/- 2.5m
<29 sec
< 1 sec
Internal 250 mAh rechargeable LiIon
9-32V
24-pin Molex Main
14-pin Molex OBD/J-Bus
Internal
N/A
Serial
Xirgo Device Manager (XDMI)
PC2407, Black
3.05”x 3.08”x 0.8”
3 oz.
-30C to +75C
(CDMA) FCC ID: GKM-XT6360
(3G): FCC ID: GKM-XT6360
IC: 10281A-XT6360
Verizon, ATT
Carrier
TTTF: All satellites at -130 dBm
Spec
Accuracy: CEP, 50%, 24 hours static, -130 dBm, > 6 SVs
Connectors IO Interface:
Main 24-pin Molex Connector (IO Interface):
Pin No.
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
Sales Engineering
support@xirgotech.com
Pin Name
12/24 Volt Power
Comments
Ign Out
w/5K limiting resistor (panic LED)
Main Battery GND
Buzzer +12V/24V with 560 ohm
Ignition Sense
IN2
Panic: pin3 on panic 4-pin Molex
LED+12V
Ground
IN0
IN1
IN3
IN4
OUT0
OUT1
OUT2
Garmin PWR
Serial Port-1 TX
Serial Port-1 RX
Serial Port-1 GND
Buzzer GND
Panic: pin4 (LED) on panic 4-pin
Molex
12V/2A Switched
Garmin FMI Tx
Garmin FMI Rx
Garmin FMI GND
Serial Port-2 TX
Serial Port-2 RX
Serial Port-2 GND
1-Wire Serial Main
iButton Data (default)
Ext. ADC
Spare GND
Panic GND
1-Wire Serial Sec.
Spare GND
OBD 14-pin Molex connector (OBD2/JBUS/SWC):
J1962 OBD2
Pin No.
XT6360
Pins
9 Pin J-Bus 6 Pin J-Bus
XT6360 Pin Description
CAN_HS_H
J1708_RXD
15
L_LINE
10
14
SWC_BUS
12
5&4
16
Sales Engineering
support@xirgotech.com
CAN_HS_L
11
13
14
J1850_POS
CAN_MS_H
10
J1850_NEG
11
J1708_TXD
CAN_MS_L
K_LINE
GND
Vehicle Power (VBAT)
Cable Harness Specification:











24-pin Microfit: Molex 43025-2400
Panic SW/LED Button Conn. Molex 43020-0401 (4 pin 2 row female shell)
I-Button Conn.: Molex 43640-0201 (2 pin Female Shell)
Buzzer Conn.: Molex 43640-0301 (3 pin Female Shell)
Garmin Conn. Molex 43020-1001 (10 pin 2 row female shell)
Garmin pins 2 and 4 looped-in (black wire, 26 AWG)
Molex male pins: 43031-0002
Total length: 5 ft.
Pins 1, 3, and 5 are 18 AWG, All others are 24 AWG.
Fuse: 3A in line with pins with pins 1 (red) and 5 (white), 7 in. from wire end
Wires 1, 3, and 5 to be jacketed up to the fuse
24-pin
No.
Color
Length
AWG
Pin function
Comments
Red
60 in.
18
VBAT
3A fuse, 7 in. from end
Orange
7 in.
20
LED+12V
Black
60 in.
18
Ground
White
7 in.
20
Ign Out
White
60 in.
18
IN0
Gray
60 in.
20
IN1
Brown
60 in.
20
IN2
Blue
7 in.
20
IN3
Red
60 in.
20
IN4
10
Brown
7 in.
20
OUT0
11
Orange
60 in.
20
OUT1
12
Yellow
7 in.
20
OUT2
13
Red
7 in.
20
Garmin PWR
12V/2A Switched
14
White/Brown
7 in.
20
Garmin FMI Tx
15
Green
7 in.
20
Garmin FMI Rx
16
Orange/Brown
7 in.
20
Garmin FMI GND
17
Yellow
7 in.
20
18
Green
7 in.
20
19
Black
7 in.
20
20
Gray
7 in.
20
Serial Port-1
TX
Serial Port-1
RX
Serial Port-1
GND
Serial Port-2
TX
Serial Port-2
RX
Serial Port-2
GND
1-Wire Serial
Main
Sales Engineering
support@xirgotech.com
I-Button
Buzz.
Panic SW
LED
Garmin
3A fuse, 7 in. from end
Buzzer GND
i-Button
21
White
60 in.
20
OWB2
22
Purple
60 in.
20
Ext. ADC
23
Black
7 in.
20
Spare GND
24
Blue/Green
7 in.
20
Spare GND
Panic GND
LED Definition
LED
BASE
UNIT
Cellular (Amber)
Optional
Bluetooth (Blue)
GPS (Green)
Description
Searching for Cellular Network
Cellular Carrier Lock
Searching for satellite
GPS Lock
TBD
Status
LED OFF
Solid
Solid
Blinking
TBD
Current Consumption
OPERATING MODE
Deep Sleep (non-functional mode)
Standby
Active Receive
CURRENT CONSUMPTION
3 mA
10 mA
65 mA
Device Mounting:
The XT6360 device must be securely installed. The accelerometer will not calibrate if unit is loose
when vehicle is in motion. When mounting the device, use a tie strap to secure the device as noted
below.
Sales Engineering
support@xirgotech.com
PC Device Configuration:
a.
A RS-232 to USB TTL converter cable is required to connect an XT6360 device to a computer for
local configuration. Serial Port # 2 is used for configuration. Connect the XT6360 Tx wire to
the TTL converter cable Rx wire. Connect the XT6360 Rx wire to the TTL converter cable Tx
wire. Connect the XT6360 ground wire to the ground wire of the TTL converter cable. Use a
terminal application to connect to the COM port associated with the TTL converter cable. Use the
following settings:
A. Terminal Application Settings:
a. Bits per second: 115200
b. Data bits: 8
c. Parity: None
d. Stop bits: 1
e. Flow control: None
B. Load Script File with the following command
a. :grscr x 2
C. Load Parameter File with the following command
a. :uyscr x 2
D. Save the configuration
a. :vycfg
Feature Matrix:
Technology
Feature Highlight
1XRTT
XT-4550
Locate
5 Digital IO
Idle
Vehicle Disable
2 - 1 Wire Bus
Ignition On/Off
Mileage
Periodic Reporting
Speed
Direction Change
Battery Voltage
Battery Disconnect
Tow Alerts
Movement Start/Stop
Acceleration/Deceleration
Sales Engineering
support@xirgotech.com
Park Time
Device Diagnostics
Virtual Odometer
Quick Fence
Motion
Accelerometer
Geo-Zones
50 Circular
Back Up Battery
250mAh
Communication Protocol
TCP, UDP , UDPwACK
Firmware Download
FTP
Device Configuration
The XT6360 is a full-feature device based on a platform that allows rapid customization by market and
application requirements. The XT6360 series offers highly configurable firmware which allows full control
of device reporting behavior. The customizable messages provides only the data required to support unique
and evolving business needs. The XT6360 configuration is accomplished by loading 2 files:
Script File
Parameter File
The Script File is the file that triggers the alerts and actions of the XT6360 .
The Parameter File specifies values used to configure hardware peripherals, network behavior, and inputs
to core functionality of the XT6360 .
Script File
A Script file can contain an unlimited number of Triggers. When scripting the Triggers are group
into individual Trigger blocks. A trigger block is comprised of the following sections:
EXAMPLE:
Trigger
Conditional Actions - optional
Actions
trigger when Eq(InputState(0), 1) [Debounce(0, 0)]
condact always
actions
run BuildAndSendMsg(0, 2, 0, 0)
DESCRIPTION:
When ignition goes high a message is sent to the server.
Important notes on Scripting:
Sales Engineering
support@xirgotech.com
10
1.
2.
3.
4.
5.
6.
7.
8.
Each Trigger Block has one Trigger.
The Trigger must test true for an action to occur.
A test is usually made of one comparison. See Comparison table.
Each Trigger Block can contain unlimited Conditional Action Blocks.
Trigger Blocks and Conditional Action block will use the following when building a script:
a. System Values
b. Events
c. Special Functions
d. Numbers
Each Conditional Action Block may optionally contain one Conditional Action Block Test.
A Conditional Action Block Test may contain up to 5 comparisons (Using same “any” or “all” logic as described
for Trigger Block Test).
Each Conditional Action Block must contain one Action Block.
How Trigger Block Tests Work
Each Trigger Block is entered when the Trigger Block Test becomes true. Note that the Trigger Block is NOT
entered WHILE the Test IS true, only the moment it becomes true. For example if you want to trigger actions
when vehicle speed goes above 80 km/hr:
trigger when Gt(GPSSpeed, 80) [Debounce(0, 0)]
The interpreter will enter the trigger block at the moment the vehicle speed increases above 80 km/hr. It will
not continue to enter the trigger block during subsequent evaluations where the speed remains above 80
km/hr. Once the speed drops below 80 (for at least one evaluation), then the trigger block will be entered
again next time the speed increases above 80 km/hr.
Note that if the speed oscillates between 80.0 and 80.1 km/hr it is possible to cause the actions to be executed as
frequently as the speed oscillates. In order to avoid this, make use of the debounce specifiers.
How Conditional Action Block Tests Work
Unlike Trigger Block Tests, Conditional Action Block Tests allow the action to be performed WHILE the test is
true. Continuing with the example above, let's say we want to further limit our actions to only execute the
moment speed goes above 80 km/hr AND only when the vehicle heading is within 10 degrees of North:
trigger when Gt(GPSSpeed, 80) [Debounce(0, 0)]
condact any
InRange(GPSHeading, 3500, 3600) [Debounce(0, 0)]
InRange(GPSHeading, 0, 100) [Debounce(0, 0)]
actions
All Conditional Action blocks are independent. One is not dependent on the other.
Condact Always
Condact When
Condact Any
Condact All -
This means the actions inside a Conditional Action Block will ALWAYS run when the
trigger Block's test(s) are true.
When only one comparison is used
The test is true when ANY of the comparisons is true.
ALL comparisons must be true for test to be true.
Sales Engineering
support@xirgotech.com
11
COMPARISONS TABLE:
COMPARISON
InRange(, , )
NotInRange(, , )
Eq(, )
NotEq(, )
Gt(, )
Lt(, )
GtEq(, )
LtEq(, )
DESCRIPTION
True when argument a is between argument b and argument c (inclusive)
True when a is less than b or a is greater than c. b must be less than c.
True when a equals b.
True when a is not equal to b.
True when a is greater than b.
True when a is less than b.
True when a is greater than/equal to b.
True when a is less than/equal to b.
Test items (, ,  above) should be one of:
System Value
Event
Special Function
Numbers (constants)
Note:
See Appendices for Complete Tables
Debounce
Debounce(, ) - where hi and lo are specified in seconds (max: 15). The 'Debounce Specify' is only
used following certain tests (see below). When a debounce is specified, it means that a test is true only AFTER
the comparison is true for hi seconds, and it is false only AFTER the comparison is false for lo seconds.
A test debounce MUST be specified any time the first argument in the test is either:
System value
Special function.
Sales Engineering
support@xirgotech.com
12
Parameter File
The parameter file is the setting for all of the XT6360 hardware peripherals, network behavior, and
inputs to core functionality of the XT6360. The following table contains all the parameters that can be
configured in a XT6360:
Acceleration event
thresholds
Crash event params
ECU_Thresholds
Geofence
MIP/SIP Control (TBD)
Odom Ign Off accum
Packet Retry
OBD RPM and Speed
Accelerometer report
correction
Debounce settings
Flag save mask
Input default polarity
Motion sensitivity
Packet Creation Append
Serial port settings
OBD Accel and Decel
APNs (GSM only)
Destination
Garmin Blacklist
Ignition sense
NMEA stream output
Packet Creation Recipe
Timer duration
Variable save mask
See Appendix C for Parameter settings.
Creating a Parameter File:
1.
2.
3.
The parameter settings are written and saved as a .txt file.
Use :wycfg in front of the parameter your are configuring.
To load the parameter file you can use XDMI or load the file over Serial Port 2.
a. Load via Serial port use the following commands
i. :uyscr x 2
load the file
ii. :vycfg
Save the parameter file
Below is an example of a parameter file.
:wycfg pdo 0 1
:wycfg dst[0] "71.24.53.116" 65534
:wycfg dst[9] "none" 65535
:wycfg pcr[0] "00080104030607080b17"
:wycfg pcr[1] "01050103070809"
:wycfg pcr[2] "02140104535455565758595a5b5c5d5e5f6061622c2e"
:wycfg pcr[3] "030701040305060708"
:wycfg pcr[4] "040701040305060708"
:wycfg pcr[5] "050701040305060708"
:wycfg pcr[6] "06080104030607080b17"
:wycfg pcr[7] "07080104030607080b17
:wycfg pcr[8] "08040104060c"
:wycfg tmr[0] 90 1
:wycfg tmr[1] 90 1
:wycfg aet[0] 0 1000 1000 205
Sales Engineering
support@xirgotech.com
13
Messages
How to create a Message
The XT6360 custom message allows users to select what fields of data to be sent in a message when
triggered. A message can contain up to 40 data fields and you can have up to 128 different messages.
Refer to Appendix F - Message Field Table
When defining a Message use the following syntax:
pcr[] ""

where:
o  is in the range 0 - 127
o "" is a quoted string of hexadecimal bytes (represented by two ascii
characters) The Message Field Table in Appendix F contains the Hex values for the
individual fields that can be selected to create the Packet.
 String format: "..."
EXAMPLES

pcr[0] "0003010306"
o pcr slot 0 will contain a Recipe string with 3 fields: PacketID, DeviceID, and GpsSpeed
 recipe_hex_string -"000301030b"
 RecipeID
00 (Hex)
 Number of fields
03 (Hex)
 Field 0 is Packet ID
01 (Hex)
 Field 1 is DeviceID
03 (Hex)
 Field 2 is GpsSpeed
0b (Hex)
Notes:

The device can store and use 128 pcr (messages)
 :wycfg pcr[0] …. :wycfg pcr[127]
 RecipeID is always in Hex.
pcr[1] "14050103070809"
o pcr slot 1 will contain a Recipe string with 5 fields : PacketID, DeviceID, Latitude, Longitude,
and Altitude
 recipe_hex_string -"14050103070809"
 RecipeID
01
 Number of fields
05
 Field 0 is Packet ID
01
 Field 1 is DeviceID
03
 Field 2 is Latitude
07
 Field 3 is Longitude
08
 Field 4 is Altitude
09
Sales Engineering
support@xirgotech.com
14
:wycfg pcr[254] "fe0401031213"
o PCR slot 2 will contain a Recipe string with 4 fields: PacketID, DeviceID, Hdop, and NumSats

recipe_hex_string -" fe0401031213"
 RecipeID
 Number of fields
04
 Field 0 is Packet ID
01
 Field 1 is DeviceID
03
 Field 3 is Hdop
12
 Field 4 is Numsats
13
fe
Decoding a Message
Knowing the Reason Code and Packet Id you will know how to parse your data. These 2 fields will
let you know what triggered the message, what data is being sent, and in what order you’re
receiving the data. Refer to Appendix F for a complete list of Fields available. The table contains
formatting information on the data in each field. Data is sent in Binary via UDP and
acknowledgments can be used.
Reason Code – Number to identify what triggered message was sent
Examples of Reason Codes:
Note:
Reason #
01
02
03
04
05
06
07
08
09
10
11
12
Description
Ignition On
Periodic Report when Ignition On
Ignition Off
Periodic Report when Ignition Off
Direction Change
Speed Threshold Alert
Acceleration Report
Deceleration Report
Idle Report
Movement Start Report
Movement Stop Report
Park Time Alert
A Reason number is like the Event number you have in a XT2060.
4001: Periodic location reporting with ignition ON
Sales Engineering
support@xirgotech.com
15
pcr Breakdown
A pcr is a list of fields that will be used to create a message to be sent from the XT6360 to the server.


Each packet recipe can contain up to 40 fields
The device can store 128 packet recipes
pcr[] ""
 is in the range 0 - 127
"" is a quoted string of hexadecimal bytes (represented by two ascii characters)
String format: "..."
Example:
pcr 1 will contain a 5 fields : PacketID, DeviceID, Latitude, Longitude, and Altitude
pcr[1] "01050103070809"
RecipeID
01
Number of fields
05
Field 0 is Packet ID
01
Field 1 is DeviceID
03
Field 2 is Latitude
07
Field 3 is Longitude
08
Field 4 is Altitude
09
Below is an example of a packet recipe that is partially decoded.
EXAMPLE:
pcr[1] "010E01040305060708090a0b12131415"
(all values below are in Hex)
Recipe ID
Number of fields
Field
PacketID
ReasonCode
Serial #
PacketSerialNum
Etc..
01
0E
HEX ID
01
04
03
05
Value
01
03
088c1c72
205a
Parsed
01
03
143400050
8282
Comment
(IGN. OFF MESSAGE)
Unit Serial Number
DATA FROM DEVICE CONVERTED FROM BINARY TO HEX USED IN TABLE ABOVE
datagram: 4 from 75.255.159.0:3000 (size: 31 bytes)
Sales Engineering
support@xirgotech.com
16
HEX--------------------------------------------------------------------------01 03 08 8c 1c 72 20 5a 54 81 be e1 01 f7 fb dd
fa 3a 18 7a 07 0c 0a 1e 01 1c 04 00 15 ff ff
------------------------------------------------------------------------------
Acknowledgements
Currently the XT6360 supports a simple acknowledgement consisting of four bytes (88-88-xx-xx)
where xx-xx is the packet serial number. You will want to send the 88-88 header and return the
serial number of the packet sent to you, in the third and fourth byte. Therefore, the XIRGO unit will
only accept an acknowledgement payload of 88-88-01-04 for a packet sent with packet serial
number 260 (hex 01-04).
Sales Engineering
support@xirgotech.com
17
Appendix A
VALUE
UnixTime
GPSLat
GPSLon
GPSAlt
GPSHeading
GPSSpeed
Inputs
Outputs
DriverId1
DriverId2
OdomDelta
GPSHDOP
GPSNumSats
GPSOdom
OdomDiff
BattVoltage
InternVoltage
MotionState
EngineState
WakeReason
SYSTEM VALUES
DESCRIPTION
Seconds since midnight Jan 1, 1970.
Degrees of latitude (unit 0.000001 degree)
Degrees of longitude (unit 0.000001 degree)
Height above sea level (unit 0.1 meter)
Heading of travel (unit 0.1 degree)
2D speed in km/hr.
User Input states
User Output states
Most recent Driver ID detected on 1 wire bus channel 1
Most recent Driver ID detected on 1 wire bus channel 2
Current value of Trip odometer 1 (in meters)
GPS Horizontal dilution of precision (unit 0.1)
Number of GPS satellites used for navigation solution.
Virtual odometer in meters
TBD
Device External voltage (vehicle system voltage, unit 0.1V)
Device Internal voltage (unit 0.1V)
1 when vehicle is moving (as reported by ECU), otherwise 0.
1 when engine has RPM (as reported by ECU), otherwise 0.
Bit mask value representing the reason for waking from sleep:
0x00 = Woke on SMS or UDP message received
0x01 = Woke on Wired Ignition
0x02 = Woke on Input 1
0x04 = Woke on Input 2
0x08 = Woke on Input 3
0x10 = Woke on Input 4
0x20 = Woke periodic
0x40 = Woke on vibration detected
0x80 = Woke on supply voltage > 13.2V
Sales Engineering
support@xirgotech.com
18
Appendix B
EVENT
TimerExpired()
EVENT TABLE
DESCRIPTION
Evaluates to 1 when timer is expired,
otherwise 0
Evaluates to 1 when a user event has
been injected into interpreter, otherwise
Use :xrmsg  to inject a message
into interpreter. (Must be caught in
interpreter script with this event
function)
Evaluates to 1 when an accelerometer
event is detected, otherwise 0
Evaluates to 1 when a non-blacklisted
Garmin response is received (and
Garmin is active), otherwise 0
INDEX RANGE
index is in the range 0 - 31
GarminUserPayloadReceived()
Evaluates to 1 when a payload (destined
for garmin device) has been received,
otherwise 0
DriverIdRead()
Evaluates to 1 when driver id is detected
on 1-wire channel , otherwise 0
Evaluates to 1 when system event
 is active, otherwise 0.
index can only be 0.
This signals that a payload has been
sent to the device by a user/server.
Typically this would be used to
trigger a SendGarminMsg() action.
UserEventIsActive()
AccelEventIsActive()
GarminResponseReceived()
SystemEventIsActive()
Sales Engineering
support@xirgotech.com
index is in the range 0 - 255.
index is in the range 0 - 3.
index is in the range 0 - 5.
0 = Ack (or Nak) packet (only
triggered when specified in
SendGarminMsg())
1 = Unit ID (a.k.a. Garmin ESN)
response
2 = Product ID response
3 = Throttle Message response
4 = Ping response
5 = Generic response; any response
that isn't listed above and isn't
blacklisted
index is in the range 0 – 1
index is in the range 0 - 17.
0 = Reset
1 = Wakeup
2 = BootloaderUpgrade (TBD)
3 = FWUpgrade
4 = ScriptUpgrade
5 = ParamSetUpgrade
6 = OverlayUpgrade
7 = ManualConfigChange
8 = CellRegistrationChange
9 = IPChange
10 = SMSReceived
11 = SMSSendOK
12 = SMSSendFailure
13 = UDPReceived
14 = UDPSendOK
15 = UDPSendFailure
16 = PacketStorageEmpty
17 = PacketStorageFull
19
Appendix C SPECIAL FUNCTION TABLE
Special Function
UserVar8()
UserVar16()
UserVar32()
FlagIsSet()
GeofenceState()
InputState()
SystemState()
Sales Engineering
support@xirgotech.com
Description
Evaluates to value stored in user variable
Evaluates to value stored in user variable
Evaluates to value stored in user variable
Evaluates to 1 when flag is set, otherwise 0
Evaluates to:
-1= is not configured
0=outside fence
1=inside fence
Evaluates to 1 when input is high/when
condition is true, otherwise 0
Evaluates to 1 when true, otherwise 0
Index Range
index is in the range 0 - 15
index is in the range 0 – 7
index is in the range 0 - 7
index is in the range 0 – 31
index is in the range 0 - 49
index is in the range 0 - 6.
0 = Ignition
1 = Input 1
2 = Input 2
3 = Input 3
4 = Input 4
5 = Device in motion (via GPS)
6 = Vehicle Battery > Threshold
7 = Accelerometer reorientation
validity
index is in the range 0 - 16.
0 = Valid Registration
1 = Valid IP
2 = Valid GPS
3 = Valid Script
4 = DM Session Active
5 = Accel Oriented
6 = Bluetooth Discoverable(TBD)
7 = Bluetooth Paired(TBD)
8 = Bluetooth Authenticated(TBD)
9 = Bluetooth Connected(TBD)
10 = Bluetooth Powered(TBD)
11 = Cellular Powered
12 = GPS Powered
13 = Garmin Powered
14 = Motion Via Accel
15 = Motion Via GPS
16 = External Power
20
Appendix D
Action
Reset Device
Reset Modem
Reset GPS
Turn Off GPS
Turn On GPS
Set User Variable
Adjust User Variable
Set Flag
Clear Flag
Start Timer
Stop Timer
Rest Timer
Sales Engineering
support@xirgotech.com
ACTIONS TABLE
Syntax
ResetDevice()
ResetModem()
ResetGPS()
TurnOffGPS()
TurnOnGPS()
SetUserVar(, , )
type is in the range 0 - 2 where:
0 = 8bit variable
1 = 16bit variable
2 = 32bit variable
index is in the range:
0 - 15 for 8bit variables
0 - 7 for 16bit variables
0 - 7 for 32bit variables
value is in the range:
-128 to 127 for 8bit variables
-32768 to 32767 for 16bit variables
–2147483648 to 2147483647 for 32 bit variables
AdjustUserVar(, , )
type is in the range 0 - 2 where:
0 = 8bit variable
1 = 16bit variable
2 = 32bit variable
index is in the range:
0 - 15 for 8bit variables
0 - 7 for 16bit variables
0 - 7 for 32bit variables
adjust_amount is in the range:
-128 to 127 for 8bit variables
-32768 to 32767 for 16bit variables
–2147483648 to 2147483647 for 32 bit variables
SetFlag()
index is in the range 0 - 31.
ClearFlag)
index is in the range 0 - 31.
StartTimer()
index is in the range 0 - 31.
StopTimer)
index is in the range 0 - 31.
ResetTimer()
index is in the range 0 - 31.
21
ACTION
Build And Send Msg
Clear Log
Enter Deep Sleep
Enter Sleep
Set Garmin Power
Send Garmin Msg
Clear Trip Odom
Set Output
Clear Output
Pulse Output
Sales Engineering
support@xirgotech.com
SYNTAX
, , , )
packet_id is in the range 0 – 255.
reason_code is in the range 0 - 255.
destination_id is in the range 0 - 9. One of the destinations servers dst[x]
ack is in the range 0 - 1
0 = No Acknowledgement needed
1 = Resend until acknowledged
TBD
EnterDeepSleep(, )
wake_mask is in the range 0x00 - 0xFF where:
0x01 = Wake on Wired Ignition
0x02 = Wake on Input 1
0x04 = Wake on Input 2
0x08 = Wake on Input 3
0x10 = Wake on Input 4
0x20 = Wake after wake_minutes
0x40 = Wake on vibration detected
0x80 = Wake on supply voltage > 13.2V
EnterSleep(, 
wake_mask is in the range 0x00 - 0xFF where:
0x00 = Wake on SMS or UDP message received
0x01 = Wake on Wired Ignition
0x02 = Wake on Input 1
0x04 = Wake on Input 2
0x08 = Wake on Input 3
0x10 = Wake on Input 4
0x20 = Wake after wake_minutes
0x40 = Wake on vibration detected
0x80 = Wake on supply voltage > 13.2V
SetGarminPower()
power_state is in the range 0 - 1 where:
0 = Off
1 = On
TBD
ClearTripOdom()
index is in the range 0 - 1.
SetOutput()
index is in the range 0 - 3
ClearOutput()
index is in the range 0 - 3.
PulseOutput(, )
index is in the range 0 - 3.
seconds_on is in the range 1 - 65535.
22
Flash Output
Clear Driver Ids
Device Check In
Sales Engineering
support@xirgotech.com
FlashOutput(, )
index is in the range 0 - 3.
blink_rate is in the range 1 - 65535Hz.
ClearDriverIds()
CheckInNow()
23
Appendix E
Acceleration event
thresholds
Accelerometer report
correction
APNs
Crash event params
Debounce settings
Destination
ECU_Thresholds
Flag save mask
Garmin Blacklist
Geofence
Input default polarity
Ignition sense
MIP/SIP Control (TBD)
Motion sensitivity
NMEA stream output
Odom Ign Off accum
Packet Creation Append
Packet Creation Recipe
Packet Retry
Serial port settings
Timer duration
OBD RPM and Speed
OBD Accel and Decel
Variable save mask
PARAMTER TABLE
aet
4    
10
16
50
apn
cep
idb
dst
vth
fsm
gbl
gfn
idp
ign
mip
mst
16
128
32
arc
1 
nso 1
oio
pca
pcr
prt
sps
tmr
ors
oad
vsm
"" "" ""
  
 
"|" |
   
<32bit_mask>
     (see example below)
  
 (0=active_low,1=active_high)
  


<8bit_mask> (see NMEA mask below. One param for each of the 4
serial outputs)

""
""

 ""
 
   
  (1mph/sec, 1mph increments)
<32bit_mask>
NMEA mask
One bit for each of the available NMEA sentences. Values can be added to stream more than one sentence type. Set mask to zero to stop
streaming.
GPGGA 0x01
GPGLL 0x02
GPGSA 0x04
GPGSV 0x08
GPRMC 0x10
Sales Engineering
support@xirgotech.com
24
Appendix F
ID
ID
Hex
Size Units
resolution Range
Notes
0x01 PacketID
N/A
0 to 255
0x02 FmCustomHeader
N/A
0 to 255
packet recipes can be labelled from
0-255, but there are only 128
recipe slots"
0x03
N/A
0x04 ReasonCode
Field
MESSAGE FIELDS TABLE
DeviceId/
Unit Serial #
0x05 PacketSerialNum
0x06 UnixTime
0x07 Latitude
100000000 to
999999999
0 to 255
0 to 65535
0x0 to 0xffffffff
degrees 1.00E-06
-2147.483648
to
2147.483647
0x08 Longitude
degrees 1.00E-06
-2147.483648
to
2147.483647
0x09 Altitude
-2147.483648
to
2147.483647
10
0x0a Heading
degrees 1.00E-01
11
0x0b GpsSpeed
km/hr
12
0x0c
N/A
13
0x0d OutputStates
N/A
InputStates
Sales Engineering
support@xirgotech.com
0.1
value TBD (currently zero)
Unsigned integer representing
numeric ESN
Unsigned integer
Unsigned integer
Unsigned integer representing
number of seconds since Unix
Epoch
Signed integer decimal value of
4byte hex string divided by
1000000 (useful range -180.0 to
180.0)
Signed integer decimal value of
4byte hex string divided by
1000000 (useful range -90.0 to
90.0)
Signed integer
-3276.8 to
3276.7
Signed integer (useful range 0.0 to
360.0)
0x0 to 0x1f
bitfield: for example - LSB (bit:0)
represents INPUT0
0x0 to 0x7
0 to 255
Unsigned integer
bitfield: for example - LSB (bit:0)
represents OUTPUT0
25
14
0x0e DriverIdCode1
N/A
15
0x0f
DriverIdCode2
N/A
16
0x10 OdometerDelta
17
0x11 Flags
19
0x13 NumSats
18
20
21
0x12 Hdop
0x14 ReceiverSigStr
0x15 CellularCarrierId
DOP
dBm
N/A
0.1
1.23
0 to
4294967295
0 to
4294967295
0 to
4294967295
0 to
4294967295
0.0 to 25.5
0 to 255
0x0 to 0xffff
0x16 InternalBattVolts
0.1
0.0 to 25.5
23
0x17 VehicleBattVolts
0.1
0.0 to 25.5
24
0x18 LifetimeOdometer
0 to
4294967295
25
0x19 AccelStartDateTime
0x0 to 0xffffffff
0x1a AccelStartLat
degrees 1.00E-06
-2147.483648
to
2147.483647
-2147.483648
to
2147.483647
27
0x1b AccelStartLong
degrees 1.00E-06
28
0x1c
km/hr
30
0x1e MaxAccel
mG
29
AccelStartSpeed
0x1d AccelStartHeading
Sales Engineering
support@xirgotech.com
degrees 0.1
Unsigned integer represent unique
iButton ID
bitfield
Unsigned integer
-113 to -75
22
26
Unsigned integer represent unique
iButton ID
0 to 255
Possibly using a 2 byte unsigned
integer representing mV (0 to
65535)
Possibly using a 2 byte unsigned
integer representing mV (0 to
65535)
Unsigned integer
Unsigned integer representing
number of seconds from Unix
Epoch
Signed integer decimal value of
4byte hex string divided by
1000000 (useful range -180.0 to
180.0)
Signed integer decimal value of
4byte hex string divided by
1000000 (useful range -90.0 to
90.0)
0 to 3599
0 to 32767
26
31
0x1f
32
0x20 AccelEndDateTime
33
AccelEventDuration
0x21 AccelEndLat
seconds 0.1
0 to 255
0x0 to 0xffffffff
degrees 1.00E-06
-2147.483648
to
2147.483647
34
0x22 AccelEndLong
degrees 1.00E-06
-2147.483648
to
2147.483647
35
0x23 AccelEndSpeed
km/hr
0 to 255
37
0x25 GeofenceId
N/A
36
0x24 AccelEndHeading
degrees 0.1
84
0x54 ObdOdometer
85
0x55 ObdTotFuelUsed
liters
86
0x56 ObdTotEngHours
hours
88
0x58 ObdEngRpm
rpm
87
89
90
91
0x57 ObdVehicleSpeed
0x59 ObdEngCoolantTemp
0x5a ObdFuelLevelPct
0x5b ObdTotDrivingSec
92
0x5c
93
94
ObdTotCruiseSec
kph
Celsius
0.1
0.1
0x5d ObdTotIdleSec
0x5e ObdTotIdleFuel
liters
Sales Engineering
support@xirgotech.com
Unsigned integer representing
number of seconds from Unix
Epoch
Signed integer decimal value of
4byte hex string divided by
1000000 (useful range -180.0 to
180.0)
Signed integer decimal value of
4byte hex string divided by
1000000 (useful range -90.0 to
90.0)
0 to 3599
0 to 49
0 to
4294967295
32-bit unsigned integer
0 to
4294967295
32-bit unsigned integer
0 to 2550
16-bit unsigned integer
0 to
4294967295
32-bit unsigned integer
0 to 65535
16-bit unsigned integer
-40 to 215
0 to 1000
0 to
4294967295
0 to
4294967295
0 to
4294967295
0 to
4294967295
16-bit signed integer
16-bit unsigned integer
32-bit unsigned integer
32-bit unsigned integer
32-bit unsigned integer
32-bit unsigned integer
27
95
0x5f
ObdHarshBreakTotCnt
96
0x60 ObdSpeedExceedTotTime 4
97
0x61 ObdRPMExceedTotTime
98
0x62 ObdHarchAccelTotTime
101 0x65 ObdVIN
Sales Engineering
support@xirgotech.com
17
ascii
0 to
4294967295
32-bit unsigned integer
0 to
4294967295
32-bit unsigned integer
0 to
4294967295
32-bit unsigned integer
0 to
4294967295
32-bit unsigned integer
28
Regulatory Statements:
FCC ID:
Model: XT6360
FCC ID: GKM-XT6360
This product contains FCC ID: XPYSARAU260
FCC Information to User:
The XT6360 does not contain any user serviceable components and is to be used with approved antennas only. Any
product changes or modifications will invalidate all applicable regulatory certifications and approvals.
FCC Guidelines for Human Exposure:
The XT6360 complies with FCC radiation exposure limits set forth for an uncontrolled environment. This equipment
should be installed and operated with minimum distance of 20 cm between the radiator and your body.
This transmitter must not be co-located or operating in conjunction with any other antenna or transmitter.
FCC Declaration of Conformity:
The XT6360 complies with Part 15 Subpart B of FCC CFR47 Rules. Operation is subject to the following two
conditions:
1. This device may not cause harmful interference, and
2. This device must accept any interference received, including interference that may cause undesired operation.
FCC Radio Frequency Interference Warnings & Instructions:
The XT6360 has been tested and found to comply with the limits for a Class B digital device, pursuant to Part 15 of
the FCC Rules. These limits are designed to provide reasonable protection against harmful interference in a
residential installation. This equipment uses and can radiate radio frequency energy and, if not installed and used in
accordance with the instructions, may cause harmful interference to radio communications. However, there is no
guarantee that interference will not occur in a particular installation. If this equipment does cause harmful interference
to radio or television reception, which can be determined by turning the equipment off and on, the user is encouraged
to try to correct the interference by one or more of the following methods:
1. Reorient or relocate the receiving antenna.
2. Increase the separation between the equipment and the receiver.
3. Connect the equipment into an electrical outlet on a circuit different from that which the radio receiver is
connected.
4. Consult the dealer or an experienced radio/TV technician for help.
Sales Engineering
support@xirgotech.com
29
Industry Canada (IC):
IC: 10281A-XT6360
This product contains IC: 8595A-SARAU260
This device complies with Industry Canada licence-exempt RSS standard(s). Operation is
subject to the following two conditions:
(1) this device may not cause interference, and
(2) this device must accept any interference, including interference that may cause
undesired operation of the device.
Le présent appareil est conforme aux CNR d'Industrie Canada applicables aux appareils
radio
exempts de licence. L'exploitation est autorisée aux deux conditions suivantes :
(1) l'appareil ne doit pas produire de brouillage, et
(2) l'utilisateur de l'appareil doit accepter tout brouillage radioélectrique subi, même si le
brouillage est susceptible d'en compromettre le onctionnement.
Under Industry Canada regulations, this radio transmitter may only operate using an
antenna of a type and maximum (or lesser) gain approved for the transmitter by Industry
Canada. To reduce potential radio interference to other users, the antenna type and its gain
should be so chosen that the equivalent isotropically radiated power (e.i.r.p.) is not more
than that necessary for successful communication.
Conformément à la réglementation d'Industrie Canada, le présent émetteur radio peut
fonctionner avec une antenne d'un type et d'un gain maximal (ou inférieur) approuvé pour
l'émetteur par Industrie Canada. Dans le but de réduire les risques de brouillage
radioélectrique à l'intention des autres utilisateurs, il faut choisir le type d'antenne et son
gain de sorte que la puissance isotrope rayonnée équivalente (p.i.r.e.) ne dépasse pas
l'intensité nécessaire à l'établissement d'une communication satisfaisante.
This radio transmitter (IC: 10281A-XT6360 , Model Number: XT6360 ) has been approved
by Industry Canada to operate with the antenna types listed below with the maximum
permissible gain and required antenna impedance for each antenna type indicated. Antenna
types not included in this list, having a gain greater than the maximum gain indicated for
that type, are strictly prohibited for use with this device.
Cet émetteur radio (identifier le périphérique par numéro de certification, ou le numéro de modèle
si Catégorie II) a été approuvé par Industrie Canada pour fonctionner avec les types d'antennes
énumérées ci-dessous avec le gain maximal admissible et l'impédance d'antenne requise pour
chaque antenne type indiqué. Types d'antennes ne figurent pas dans cette liste, ayant un gain
supérieur au maximum gagner indiqué pour ce type, sont strictement interdites pour une utilisation
avec cet appareil..
Sales Engineering
support@xirgotech.com
30

Source Exif Data:
File Type                       : PDF
File Type Extension             : pdf
MIME Type                       : application/pdf
PDF Version                     : 1.4
Linearized                      : No
Create Date                     : 2015:04:24 18:19:38Z
Modify Date                     : 2015:04:24 18:19:51Z
XMP Toolkit                     : 3.1-701
Creator Tool                    : Nitro Pro 9  (9. 0. 5. 9)
Metadata Date                   : 2015:04:24 18:19:51Z
Format                          : application/pdf
Creator                         : 
Title                           : 
Description                     : 
Keywords                        : 
Producer                        : Nitro Pro 9  (9. 0. 5. 9)
Document ID                     : uuid:21f2dfef-f692-4d6c-828b-43094e8cb6e1
Page Mode                       : UseNone
Page Count                      : 31
EXIF Metadata provided by
EXIF.tools
FCC ID Filing: GKM-XT6360

Navigation menu