XT6360 User Guide Version1.0 188 Camino Ruiz Camarillo, CA 93012 www.xirgotech.com support@xirgotech.com Contents Document Change History..........................................................................................................................2 Hardware Specification...............................................................................................................................3 ConnectorIO Interface.................................................................................................................................4 Cable Harness Specification........................................................................................................................6 LED Defentition ...........................................................................................................................................7 Current Consumption .................................................................................................................................7 Device mounting..........................................................................................................................................7 PC DeviceConfiguration .............................................................................................................................8 Feature Matrix .............................................................................................................................................8 Device Configuration...................................................................................................................................9 Parameter File ...........................................................................................................................................13 Script File ...................................................................................................................................................10 Parameter File ...........................................................................................................................................13 7Regulatroy Statements..............................................................................................................................28 Messages.....................................................................................................................................................14 Appendices..13 Sales Engineering support@xirgotech.com 1 Document Change History Revision 1.0 Date 4/24/2015 Changes Initial Release(NB) Sales Engineering support@xirgotech.com 2 Sales Engineering support@xirgotech.com 3 Hardware Specification:
Spec HW Options:
Cellular Wireless Technology:
Parameter GPS Specification 2G/GSM/GPRS/EGPRS:850/900/1800/1900Bands-Models:XT6360/ XT6355 3G (UMTS):850/1900 Bands(Bands V, II)- Models: XT6360 CDMA (1xRTT):850/1900 Bands-Models:XT6360 56channels
-162dBm
-148dBm
+/-2.5m
<29sec
< 1 sec Internal 250 mAh rechargeable Li-
Ion 9-32V 24-pinMolex Main 14-pinMolexOBD/J-Bus Internal N/A Serial Xirgo Device Manager (XDMI) PC2407,Black 3.05x 3.08x 0.8 3 oz.
-30C to +75C
(CDMA)FCC ID: GKM-XT6360
(3G): FCC ID:GKM-XT6360 IC: 10281A-XT6360 Verizon, ATT Notes:
TTTF: All satellites at -130 dBm; Accuracy: CEP, 50%, 24 hours static, -130 dBm, > 6 SVs Receiver Receivertracking sensitivity ReceiverCold Start CEPAccuracy TTFF-Cold Start
-Hot Start 3-axis Accel. BT/BTLE Last Gasp Back-up Battery D.C. Power Data Connector Antenna:
Cellular/GPS/BT SIM Access(2G/3G) Programming Case Material Dimension Weight Operating Temperature Product Carrier Power Requirements Physical Connection Certifications Mechanical Sales Engineering support@xirgotech.com 4 Connectors IO Interface:
Main 24-pin Molex Connector (IO Interface):
Pin No. 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 Pin Name 12/24 Volt Power LED+12V Ground Ign Out IN0 IN1 IN2 IN3 IN4 OUT0 OUT1 OUT2 Garmin PWR 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 1-Wire Serial Sec. Ext. ADC Spare GND Spare GND Comments w/5K limiting resistor (panic LED) Main Battery GND Buzzer +12V/24V with 560 ohm Ignition Sense Panic: pin3 on panic 4-pin Molex Buzzer GND Panic: pin4 (LED) on panic 4-pin Molex 12V/2A Switched Garmin FMI Tx Garmin FMI Rx Garmin FMI GND iButton Data (default) Panic GND Sales Engineering support@xirgotech.com 5 OBD 14-pin Molex connector (OBD2/JBUS/SWC):
J1962 OBD2 XT6360 9 Pin J-Bus 6 Pin J-Bus Pin No. 6 15 10 2 14 3 11 1 7 5&4 16 Pins 1 2 3 4 5 6 7 8 9 10 11 12 13 14 XT6360 Pin Description CAN_HS_H J1708_RXD J1708_TXD L_LINE J1850_NEG J1850_POS CAN_HS_L CAN_MS_H CAN_MS_L SWC_BUS K_LINE GND Vehicle Power(VBAT) C G F D A B B A E C Sales Engineering support@xirgotech.com 6 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. 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 Color Length AWG Pin function Comments I-Button Buzz. Panic SW Garmin Red Orange Black White White Gray Brown Blue Red Brown Orange Yellow Red White/Brown Green 60 in. 7 in. 60 in. 7 in. 60 in. 60 in. 60 in. 7 in. 60 in. 7 in. 60 in. 7 in. 7 in. 7 in. 7 in. Orange/Brown 7 in. Yellow Green Black Gray 7 in. 7 in. 7 in. 7 in. 18 20 18 20 18 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 Sales Engineering support@xirgotech.com VBAT LED+12V Ground Ign Out IN0 IN1 IN2 IN3 IN4 OUT0 OUT1 OUT2 Garmin PWR 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 3A fuse, 7 in. from end 3A fuse, 7 in. from end Buzzer GND 12V/2A Switched Garmin FMI Tx Garmin FMI Rx Garmin FMI GND i-Button 1 LED 3 1 4 1 2 5 1 6 4 7 21 22 23 24 White Purple Black Blue/Green 60 in. 60 in. 7 in. 7 in. 20 20 20 20 OWB2 Ext. ADC Spare GND Spare GND Panic GND 2 2 LED Definition LED BASE UNIT Cellular (Amber) GPS (Green) Optional Bluetooth (Blue) Description Searching for CellularNetwork CellularCarrier Lock Searching for satellite GPS Lock TBD Status LED OFF Solid Solid Blinking TBD Current Consumption OPERATING MODE CURRENT CONSUMPTION 3 mA 10 mA 65 mA DeepSleep(non-functional mode) Standby Active Receive TheXT6360devicemust besecurely installed.Theaccelerometerwill not calibrate if unit is loose when vehicle is in motion. When mounting thedevice,usea tiestrapto securethe deviceas noted below. Device Mounting:
Sales Engineering support@xirgotech.com 8 PC Device Configuration:
a. A RS-232 to USB TTL converter cable is required to connect anXT6360deviceto a computer for local configuration. Serial Port # 2isused for configuration. Connect theXT6360Txwire to the TTL converter cable Rx wire. Connect theXT6360Rx wire to the TTL converter cable Tx wire. Connect theXT6360ground 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 Flow control: None e. B. Load Script File with the following command a.
:grscr x 2 C. Load Parameter File with the following command
:uyscr x 2 a. D. Save the configuration a.
:vycfg Feature Matrix:
Technology Feature Highlight Locate Idle VehicleDisable 5 Digital IO 2-1 Wire Bus Ignition On/Off Mileage Periodic Reporting Speed Direction Change Battery Voltage Battery Disconnect Tow Alerts Movement Start/Stop Acceleration/Deceleration 1XRTT XT-4550 X X X X X X X X X X X X X X X Sales Engineering support@xirgotech.com 9 Park Time VirtualOdometer Quick Fence Device Diagnostics Motion Accelerometer Geo-Zones Back Up Battery Communication Protocol Firmware Download X X X X X X 50Circular 250mAh TCP, UDP , UDPwACK FTP Device Configuration Script File Parameter File TheXT6360is a full-feature devicebased on a platform that allows rapid customization by market and application requirements. TheXT6360seriesoffers 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. TheXT6360configuration is accomplished by loading 2 files:
The Script Fileis the file that triggers the alerts and actions of theXT6360. The Parameter Filespecifies values used to configure hardware peripherals, network behavior, and inputs to core functionality of theXT6360. Script FileA 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) When ignition goes high a message is sent to the server. DESCRIPTION:
Important notes on Scripting:
Sales Engineering support@xirgotech.com 10 How Trigger Block Tests Work Each Trigger Block has one Trigger. 1. The Trigger must test true for an action to occur. 2. 3. A test is usually made of one comparison. See Comparisontable. 4. Each Trigger Block can contain unlimited Conditional Action Blocks. Trigger Blocks and Conditional Action block will use the following when building a script:
5. System Values a. Events b. Special Functions c. d. Numbers 6. Each Conditional Action Block mayoptionally contain one Conditional Action Block Test. 7. 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. 8. 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 speedgoes 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 wherethe 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 whenGt(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 onthe other. 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 thecomparisons is true. Condact All-
ALL comparisons must be true for test to be true. Condact When Condact Any Condact Always Sales Engineering support@xirgotech.com 11 COMPARISONS TABLE:
COMPARISON DESCRIPTION True when argument a is between argument b and argument c (inclusive) InRange(<a>, <b>, <c>) True when a is less than b or a is greater than c. b must be less than c. NotInRange(<a>, <b>, <c>) True when a equals b. Eq(<a>, <b>) True when a is not equal to b. NotEq(<a>, <b>) True when a is greater than b. Gt(<a>, <b>) True when a is less than b. Lt(<a>, <b>) True when a is greater than/equal to b. GtEq(<a>, <b>) True when a is less than/equal to b. LtEq(<a>, <b>) Test items (<a>, <b>, <c> above) should be one of:
System Value Event Special Function Numbers (constants) See Appendices for Complete Tables Debounce(<hi>, <lo>)-where hiand loare 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 istrue only AFTER the comparison is true for hiseconds, and it is false only AFTER the comparison is false for loseconds. A test debounce MUST be specified any time the first argument in the test is either:
Debounce Note:
System value Special function. Sales Engineering support@xirgotech.com 12 Parameter File The parameter file is the setting for all of theXT6360hardware peripherals, network behavior, and inputs to core functionality of theXT6360. The following table contains all the parameters that can be configured inaXT6360:
Acceleration event thresholds Crash event params ECU_Thresholds Geofence MIP/SIP Control (TBD) Odom Ign Off accum Packet Retry OBD RPM and Speed See Appendix C for Parameter settings. 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 Creating a Parameter File:
:uyscr x 2
:vycfg 1. The parameter settings are written and saved as a .txt file. 2. Use :wycfgin front of the parameter your are configuring. To load the parameter file you can use XDMI or load the file over Serial Port 2. 3. a. Load via Serial port use the following commands i. load the file Save the parameter file ii. 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 o o EXAMPLES pcr[0] "0003010306"
where:o How to create a Message TheXT6360custom 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[<slot_index>] "<recipe_hex_string>"
<slot_index>is in therange 0-127
"<recipe_hex_string>"is a quoted string of hexadecimal bytes (represented by two ascii characters) The Message Field Tablein Appendix F contains the Hexvalues for the individual fields that can be selected to create the Packet. Stringformat: "<recipe_id><num_fields><field_0><field_1>...<field_N>"
pcr slot 0 will contain a Recipe string with 3 fields:PacketID,DeviceID, andGpsSpeed recipe_hex_string-"000301030b"
RecipeID 03(Hex) Number of fields 01(Hex) Field 0 is Packet ID 03(Hex) Field 1 is DeviceID 0b(Hex) Field 2 is GpsSpeed The device can store and use 128 pcr (messages)
:wycfg pcr[0].:wycfg pcr[127]
RecipeID is always in Hex. pcr slot 1 willcontain a Recipe string with 5 fields :PacketID,DeviceID,Latitude,Longitude, andAltitude recipe_hex_string-"14050103070809"
RecipeID 05 Number of fields 01 Field 0 is Packet ID 03 Field 1 is DeviceID Field 2 is Latitude 08 Field 3 is Longitude Field 4 is Altitude 00(Hex) pcr[1] "14050103070809"
01 07 09 Notes:
o o 14 Sales Engineering support@xirgotech.com
:wycfg pcr[254] "fe0401031213"
PCR slot 2 will contain a Recipe string with 4 fields: PacketID, DeviceID, Hdop, and NumSats o recipe_hex_string-"fe0401031213"
04 01 03 12 13 RecipeID Number of fields Field 0 is Packet ID Field 1is DeviceID Field 3 is Hdop Field 4 is Numsats fe Decoding a Message Knowing the Reason Code and PacketId youwill 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 youre receivingthe data. Refer to Appendix F for a complete list of Fields available. The tablecontains formattinginformationon the data in each field. Data is sent in Binary via UDP and acknowledgments can be used. Reason Code Number toidentify what triggered message was sent Examples of Reason Codes:
Reason #
Description 01 02 03 04 05 06 07 08 09 10 11 12 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 Note:
Sales Engineering support@xirgotech.com 15 pcr Breakdown A pcr isa listof fields that will be used to create a message to be sent from theXT6360to the server. Each packet recipe can contain up to 40 fields The device can store 128 packetrecipes Example:
pcr[<slot_index>] "<recipe_hex_string>"
<slot_index> is in the range 0-127
"<recipe_hex_string>"is a quoted string of hexadecimal bytes (represented by two ascii characters) String format: "<packet_id><num_fields><field_0><field_1>...<field_N>"
pcr 1will contain a 5 fields : PacketID, DeviceID, Latitude, Longitude, and Altitude pcr[1] "01050103070809"
RecipeID Number of fields Field 0 is Packet ID Field 1 is DeviceID Field 2 is Latitude Field 3 is Longitude Field 4 is Altitude EXAMPLE:
01 05 01 03 07 08 09 Below is an example of a packet recipe that is partially decoded. pcr[1] "010E01040305060708090a0b12131415"
(all values below are in Hex) 01 Recipe ID Number of fields 0E 01 01 PacketID 01 03 ReasonCode 04 03 143400050 088c1c72 03 Serial #
205a 8282 PacketSerialNum 05 Etc..DATA FROM DEVICE CONVERTED FROM BINARY TO HEX USED IN TABLE ABOVE datagram: 4 from 75.255.159.0:3000 (size: 31 bytes) HEX ID Parsed Value Field Comment
(IGN. OFF MESSAGE) Unit Serial Number 16 Sales Engineering support@xirgotech.com 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
------------------------------------------------------------------------------
CurrentlytheXT6360 supportsa simple acknowledgement consisting of four bytes (88-88-xx-xx) where xx-xx is the packet serialnumber. 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). Acknowledgements Sales Engineering support@xirgotech.com 17 Appendix A VALUE SYSTEM VALUES UnixTime GPSLat GPSLon GPSAlt GPSHeading GPSSpeed Inputs Outputs DriverId1 DriverId2 OdomDelta GPSHDOP GPSNumSats GPSOdom OdomDiff BattVoltage InternVoltage MotionState EngineState WakeReason 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 = Wokeon 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 EVENT Appendix B TimerExpired(<index>) UserEventIsActive(<index>) AccelEventIsActive(<index>) GarminResponseReceived(<index>) DESCRIPTION Evaluates to 1 whentimer is expired, otherwise 0 Evaluates to 1 when a user event has been injected into interpreter, otherwise 0 Use :xrmsg <index> 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 anon-blacklisted Garmin response is received (and Garmin is active), otherwise 0 GarminUserPayloadReceived(<index>) DriverIdRead(<index>) SystemEventIsActive(<index>) Evaluates to 1 when a payload (destined for garmin device) has been received, otherwise 0 Evaluates to 1 when driver id is detected on 1-wire channel <index>, otherwise0 Evaluates to 1 when system event
<index> is active, otherwise 0. EVENT TABLE INDEX RANGE index is in the range 0-31 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 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. index is in the range 01 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 Sales Engineering support@xirgotech.com 19 Appendix C SPECIAL FUNCTION TABLE Special Function Description UserVar8(<index>) UserVar16(<index>) UserVar32(<index>) FlagIsSet(<index>) GeofenceState(<index>) InputState(<index>) 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=<index> is not configured 0=outside fence 1=inside fence Evaluates to 1 when input is high/when condition is true, otherwise 0 SystemState(<index>) Evaluates to 1 when true, otherwise 0 Index Range index is in the range 0-15 index is in the range 07 index is in the range 0-7 index is in the range 031 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 ViaGPS 16 = External Power Sales Engineering support@xirgotech.com 20 ACTIONS TABLE Syntax 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 SetUserVar(<type>, <index>, <value>) AdjustUserVar(<type>, <index>, <adjust_amount>) ResetDevice() ResetModem() ResetGPS() TurnOffGPS() TurnOnGPS() typeis in the range 0-2 where:
0 = 8bit variable 1 = 16bit variable 2 = 32bit variable indexis in the range:
0-15 for 8bit variables 0-7 for 16bit variables 0-7 for 32bit variables valueis in the range:
-128 to 127 for 8bit variables
-32768 to 32767 for 16bit variables 2147483648 to 2147483647 for 32 bit variables typeis in the range 0-2 where:
0 = 8bit variable 1 = 16bit variable 2 = 32bit variable indexis in the range:
0-15 for 8bit variables 0-7 for 16bit variables 0-7 for 32bit variables adjust_amountis in the range:
-128 to 127 for 8bit variables
-32768 to 32767 for 16bit variables 2147483648 to 2147483647 for 32 bit variables indexis in the range 0-31. indexis in the range 0-31. indexis in the range 0-31. indexis in the range 0-31. indexis in the range 0-31. ResetTimer(<timer_index>) StartTimer(<timer_index>) SetFlag(<flag_index>) StopTimer<timer_index>) ClearFlag<flag_index>) 21 ACTION Build And Send Msg Clear Log Enter Deep Sleep Enter Sleep Set Garmin Power Send Garmin Msg Clear TripOdom Set Output Clear Output Pulse Output Sales Engineering support@xirgotech.com SYNTAX EnterSleep(<wake_mask>, <wake_minutes>
EnterDeepSleep(<wake_mask>, <wake_minutes>)
<packet_id>, <reason_code>, <destination_id>, <ack>) packet_idis in the range 0255. reason_codeis in the range 0-255. destination_idis in the range 0-9. One of the destinations servers dst[x]
ackis in the range 0-1 0 = No Acknowledgement needed 1 = Resend until acknowledged TBD wake_maskis 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 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 = Wakeon Input 4 0x20 = Wake after wake_minutes 0x40 = Wake on vibration detected 0x80 = Wake on supply voltage > 13.2V SetGarminPower(<power_state>) power_state is in the range 0-1 where:
0 = Off 1 = On TBD indexis in the range 0-1. indexis in the range 0-3 indexis in the range 0-3. indexis in the range 0-3. seconds_on is in the range 1-65535. PulseOutput(<output_index>, <seconds_on>) ClearTripOdom(<odom_index>) ClearOutput(<output_index>) SetOutput(<output_index>) 22 Flash Output Clear Driver Ids Device CheckIn FlashOutput(<output_index>, <blink_rate>) indexis in the range 0-3. blink_rateis in the range 1-65535Hz. ClearDriverIds() CheckInNow() Sales Engineering support@xirgotech.com 23 Appendix E PARAMTER TABLE aet 4 <direction (adlr)> <start_duration> <end_duration> <mg_thresh>
8 arc 1 <correction_factor>
1 apn 3 "<apn_name>" "<username>" "<password>"
4 cep 3 <mg_thresh> <poll_freq> <hist_depth>
1 idb 2 <on_sec> <off_sec>
6 dst 2 "<ip>|<hostname>" <port>|<serial_port_id>
10 vth 4 <brake_thresh> <accel_thresh> <speed_limit> <rpm_limit>
1 fsm 1 <32bit_mask>
1 gbl 5 <flags> <pid> <size> <byte0> <byte1> (see example below) 16 gfn 3 <lat> <lon> <radius>
50 idp 1 <pullup_disable> (0=active_low,1=active_high) 4 ign 3 <source mask> <ign on sec> <ign off sec>
1 mip 1 <value>
1 mst 1 <motion_sensitivity_value>
1 nso 1 <8bit_mask> (see NMEA mask below. One param for each of the 4 4 oio 1 <accum>
2 pca 1 "<append_hex_string>"
16 128 pcr 1 "<recipe_hex_string>"
2 prt 1 <sec>
sps 2 <baudrate> "<dps>"
2 32 tmr 2 <sec> <auto_start>
2 ors 2 <rpm threshold> <rpm time sec> <mph threshold> <mph time sec>
oad 1 <obd accel> <obd decel> (1mph/sec, 1mph increments) 2 1 vsm 1 <32bit_mask>
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 NMEA mask One bitfor 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 serial outputs) Sales Engineering support@xirgotech.com 24 Appendix F Field ID ID Hex MESSAGE FIELDS TABLE Size Units resolution Range Notes 1 2 3 4 5 6 7 8 9 10 11 12 13 0x01 PacketID 0x02 FmCustomHeader 0x03 DeviceId/
Unit Serial #
0x04 ReasonCode 0x05 PacketSerialNum 0x06 UnixTime 0x07 Latitude 0x08 Longitude 0x09 Altitude 0x0a Heading 0x0b GpsSpeed 0x0c InputStates 0x0d OutputStates Sales Engineering support@xirgotech.com 1 1 4 1 2 4 4 4 2 2 1 1 1 N/A N/A N/A 1 1 1 1 1 1 degrees 1.00E-06 degrees 1.00E-06 m 0.1 degrees 1.00E-01 1 km/hr N/A 1 1 N/A packet recipes can be labelled from 0 to 255 0-255, but there are only 128 recipe slots"
0 to 255 value TBD (currently zero) 100000000 to Unsigned integer representing 999999999 numeric ESN 0 to 255 Unsigned integer 0 to 65535 Unsigned integer 0x0 to 0xffffffff Unsigned integer representing number of seconds sinceUnix Epoch Signed integer decimal value of
-2147.483648 4byte hex string divided by to2147.483647 1000000 (useful range-180.0 to 180.0) Signed integerdecimal value of
-2147.483648 4byte hex string divided by to2147.483647 1000000 (useful range-90.0 to 90.0)
-2147.483648 Signed integer to2147.483647 Signed integer (useful range 0.0 to
-3276.8 to 3276.7 360.0) Unsigned integer 0 to 255 bitfield: for example-LSB (bit:0) 0x0 to 0x1f represents INPUT0 bitfield: for example-LSB (bit:0) 0x0 to 0x7 represents OUTPUT0 25 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 0x0e DriverIdCode1 0x0f DriverIdCode2 0x10 OdometerDelta 0x11 Flags 0x12 Hdop 0x13 NumSats 0x14 ReceiverSigStr 0x15 CellularCarrierId 0x16 InternalBattVolts 0x17 VehicleBattVolts 0x18 LifetimeOdometer 0x19 AccelStartDateTime 0x1a AccelStartLat 0x1b AccelStartLong 0x1c AccelStartSpeed 0x1d AccelStartHeading 0x1e MaxAccel Sales Engineering support@xirgotech.com 4 4 4 4 1 1 1 2 1 1 4 4 4 4 1 2 2 N/A N/A m DOP N/A dBm V V m 1 1 1 1 0.1 1 1.23 1 0.1 0.1 1 1 degrees 1.00E-06 degrees 1.00E-06 1 km/hr degrees 0.1 1 mG Unsigned integer represent unique iButton ID Unsigned integer represent unique iButton ID bitfield Unsigned integer 0 to4294967295 0 to4294967295 0 to4294967295 0 to4294967295 0.0 to 25.5 0 to 255
-113 to-75 0x0 to 0xffff Possibly using a2 byte unsigned integer representing mV (0 to 0.0 to 25.5 65535) Possibly using a 2 byte unsigned integer representing mV (0 to 0.0 to 25.5 65535) 0 to4294967295 Unsigned integer 0x0 to 0xffffffff Unsigned integer representing number of seconds from Unix Epoch Signed integer decimal value of
-2147.483648 4byte hex string divided by to2147.483647 1000000 (usefulrange-180.0 to 180.0) Signed integer decimal value of
-2147.483648 4byte hex string divided by to2147.483647 1000000 (useful range-90.0 to 90.0) 0 to 255 0 to 3599 0 to 32767 26 31 32 33 34 35 36 37 84 85 86 87 88 89 90 91 92 93 94 0x1f AccelEventDuration 0x20 AccelEndDateTime 0x21 AccelEndLat 0x22 AccelEndLong 0x23 AccelEndSpeed 0x24 AccelEndHeading 0x25 GeofenceId 0x54 ObdOdometer 0x55 ObdTotFuelUsed 0x56 ObdTotEngHours 0x57 ObdVehicleSpeed 0x58 ObdEngRpm 0x59 ObdEngCoolantTemp 0x5a ObdFuelLevelPct 0x5b ObdTotDrivingSec 0x5c ObdTotCruiseSec 0x5d ObdTotIdleSec 0x5e ObdTotIdleFuel Sales Engineering support@xirgotech.com 1 4 4 4 1 2 1 4 4 4 2 2 2 2 4 4 4 4 seconds 0.1 1 degrees 1.00E-06 degrees 1.00E-06 1 km/hr degrees 0.1 N/A 1 m 1 liters 1 hours kph 0.1 1 rpm Celsius 1 0.1
%
1 s s 1 1 s 1 liters 0 to 255 0x0 to 0xffffffff Unsigned integer representing number of seconds from Unix Epoch Signed integer decimal value of
-2147.483648 4byte hex string divided by to2147.483647 1000000 (useful range-180.0 to 180.0) Signed integer decimal valueof
-2147.483648 4byte hex string divided by to2147.483647 1000000 (useful range-90.0 to 90.0) 0 to 255 0 to 3599 0 to 49 0 to4294967295 0 to4294967295 0 to4294967295 0 to 2550 0to 65535
-40 to 215 0 to 1000 0 to4294967295 0 to4294967295 0 to4294967295 0 to4294967295 32-bit unsignedinteger 32-bit unsigned integer 32-bit unsigned integer 16-bit unsigned integer 16-bit unsigned integer 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 4 0x5f ObdHarshBreakTotCnt 95 0x60 ObdSpeedExceedTotTime 4 96 0x61 ObdRPMExceedTotTime 4 97 4 0x62 ObdHarchAccelTotTime 98 17 101 0x65 ObdVIN ascii 1 1 1 1 0 to4294967295 0 to4294967295 0 to4294967295 0 to4294967295 32-bit unsigned integer 32-bit unsigned integer 32-bit unsigned integer 32-bit unsigned integer Sales Engineering support@xirgotech.com 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. 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. Increase the separation between the equipment and the receiver. 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 prsent appareil est conforme aux CNR d'Industrie Canada applicables aux appareils radio exempts de licence. L'exploitation est autorise aux deux conditions suivantes :
(1) l'appareil ne doit pas produire de brouillage, et
(2) l'utilisateur de l'appareil doit accepter tout brouillage radiolectrique subi, mme 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. Conformment la rglementation d'Industrie Canada, le prsent metteur radio peut fonctionner avec une antenne d'un type et d'un gain maximal (ou infrieur) approuv pour l'metteur par Industrie Canada. Dans le but de rduire les risques de brouillage radiolectrique l'intention des autres utilisateurs, il faut choisir le type d'antenne et son gain de sorte que la puissance isotrope rayonne quivalente (p.i.r.e.) ne dpasse pas l'intensit ncessaire 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 priphrique par numro de certification, ou le numro de modle si Catgorie II) a t approuv par Industrie Canada pour fonctionner avec les types d'antennes numres ci-dessous avec le gain maximal admissible et l'impdance d'antenne requise pour chaque antenne type indiqu. Types d'antennes ne figurent pas dans cette liste, ayant un gain suprieur au maximum gagner indiqu pour ce type, sont strictement interdites pour une utilisation avec cet appareil.. Sales Engineering support@xirgotech.com 30