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

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

User Manual

188 Camino RuizCamarillo, CA 93012www.xirgotech.comsupport@xirgotech.comXT6360UserGuideVersion 1.0
1Sales Engineeringsupport@xirgotech.comContentsDocument Change History .......................................................................................................................... 2Hardware Specification............................................................................................................................... 3Connector IO Interface................................................................................................................................. 4Cable Harness Specification........................................................................................................................ 6LED Defentition ........................................................................................................................................... 7Current Consumption ................................................................................................................................. 7Device mounting.......................................................................................................................................... 7PC Device Configuration ............................................................................................................................. 8Feature Matrix ............................................................................................................................................. 8Device Configuration................................................................................................................................... 9Parameter File ...........................................................................................................................................13Messages.....................................................................................................................................................14Script File ...................................................................................................................................................10Parameter File ...........................................................................................................................................13Appendices…………………………………………………………………………………………………………………………………………..137Regulatroy Statements..............................................................................................................................28
2Sales Engineeringsupport@xirgotech.comDocument Change HistoryRevisionDateChanges1.04/24/2015Initial Release (NB)
3Sales Engineeringsupport@xirgotech.com
4Sales Engineeringsupport@xirgotech.comHardware Specification:Cellular Wireless Technology:2G/GSM/GPRS/EGPRS: 850/900/1800/1900 Bands - Models: XT6360 / XT63553G (UMTS): 850/1900 Bands (Bands V, II) -Models: XT6360CDMA (1xRTT): 850/1900 Bands - Models: XT6360ParameterSpecGPS SpecificationReceiver56 channelsReceiver trackingsensitivity-162 dBmReceiver Cold Start-148dBmCEP Accuracy+/- 2.5mTTFF- Cold Start- Hot Start<29 sec< 1 secHW Options:3-axis Accel.BT/BTLELast Gasp Back-upBatteryInternal 250 mAh rechargeable Li-IonPower RequirementsD.C. Power9-32VPhysical ConnectionData Connector24-pin Molex Main14-pin Molex OBD/J-BusAntenna:Cellular/GPS /BTInternalSIM Access (2G/3G)N/AProgrammingSerialXirgo Device Manager (XDMI)MechanicalCase MaterialPC2407, BlackDimension3.05”x 3.08”x 0.8”Weight3 oz.OperatingTemperature-30C to +75CCertificationsProduct(CDMA) FCC ID: GKM-XT6360(3G): FCC ID: GKM-XT6360IC: 10281A-XT6360CarrierVerizon, ATTNotes:TTTF: All satellites at -130 dBm ;Accuracy: CEP, 50%, 24 hours static, -130 dBm, > 6 SVs
5Sales Engineeringsupport@xirgotech.comConnectors IO Interface:Main 24-pin Molex Connector (IO Interface):Pin No.Pin NameComments112/24 Volt Power2LED+12Vw/5K limiting resistor (panic LED)3GroundMain Battery GND4Ign OutBuzzer +12V/24V with 560 ohm5IN0Ignition Sense6IN17IN28IN3Panic: pin3 on panic 4-pin Molex9IN410OUT0Buzzer GND11OUT112OUT2Panic: pin4 (LED) on panic 4-pinMolex13Garmin PWR12V/2A Switched14Serial Port-1 TXGarmin FMI Tx15Serial Port-1 RXGarmin FMI Rx16Serial Port-1 GNDGarmin FMI GND17Serial Port-2 TX18Serial Port-2 RX19Serial Port-2 GND201-Wire Serial MainiButton Data (default)211-Wire Serial Sec.22Ext. ADC23Spare GNDPanic GND24Spare GND
6Sales Engineeringsupport@xirgotech.comOBD 14-pin Molex connector (OBD2/JBUS/SWC):J1962 OBD2Pin No.XT6360PinsXT6360 Pin Description9 Pin J-Bus6 Pin J-Bus61CAN_HS_HC2J1708_RXDGB3J1708_TXDFA154L_LINE105J1850_NEG26J1850_POS7148CAN_HS_LD39CAN_MS_H1110CAN_MS_L111SWC_BUS712K_LINE5&413GNDAE1614Vehicle Power (VBAT)BC
7Sales Engineeringsupport@xirgotech.comCable 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 fuse24-pinNo.ColorLengthAWGPin functionCommentsI-ButtonBuzz.Panic SWLEDGarmin1Red60 in.18VBAT3A fuse, 7 in. from end2Orange7 in.20LED+12V33Black60 in.18Ground4White7 in.20Ign Out15White60 in.18IN03A fuse, 7 in. from end6Gray60 in.20IN17Brown60 in.20IN28Blue7 in.20IN319Red60 in.20IN410Brown7 in.20OUT0Buzzer GND211Orange60 in.20OUT112Yellow7 in.20OUT2413Red7 in.20Garmin PWR12V/2A Switched514White/Brown7 in.20Serial Port-1TXGarmin FMI Tx115Green7 in.20Serial Port-1RXGarmin FMI Rx616Orange/Brown7 in.20Serial Port-1GNDGarmin FMI GND417Yellow7 in.20Serial Port-2TX18Green7 in.20Serial Port-2RX19Black7 in.20Serial Port-2GND20Gray7 in.201-Wire SerialMaini-Button1
8Sales Engineeringsupport@xirgotech.com21White60 in.20OWB222Purple60 in.20Ext. ADC23Black7 in.20Spare GNDPanic GND224Blue/Green7 in.20Spare GND2LED DefinitionCurrent ConsumptionOPERATING MODECURRENT CONSUMPTIONDeep Sleep (non-functional mode)3 mAStandby10 mAActive Receive65 mADevice Mounting:The XT6360 device must be securely installed. The accelerometer will not calibrate if unit is loosewhen vehicle is in motion. When mounting the device, use a tie strap to secure the device as notedbelow.BASEUNITLEDDescriptionStatusCellular (Amber)Searching for Cellular NetworkLED OFFCellular Carrier LockSolidGPS (Green)Searching for satelliteSolidGPS LockBlinkingOptionalBluetooth (Blue)TBDTBD
9Sales Engineeringsupport@xirgotech.comPC Device Configuration:a. A RS-232 to USB TTL converter cable is required to connect an XT6360 device to a computer forlocal configuration. Serial Port # 2 is used for configuration. Connect the XT6360 Tx wire tothe TTL converter cable Rx wire. Connect the XT6360 Rx wire to the TTL converter cable Txwire. Connect the XT6360 ground wire to the ground wire of the TTL converter cable. Use aterminal application to connect to the COM port associated with the TTL converter cable. Use thefollowing settings:A. Terminal Application Settings:a. Bits per second: 115200b. Data bits: 8c. Parity: Noned. Stop bits: 1e. Flow control: NoneB. Load Script File with the following commanda. :grscr x 2C. Load Parameter File with the following commanda. :uyscr x 2D. Save the configurationa. :vycfgFeature Matrix:Technology1XRTTFeature HighlightXT-4550LocateXIdleXVehicle DisableX5 Digital IOX2 - 1 Wire BusXIgnition On/OffXMileageXPeriodic ReportingXSpeedXDirection ChangeXBattery VoltageXBattery DisconnectXTow AlertsXMovement Start/StopXAcceleration/DecelerationX
10Sales Engineeringsupport@xirgotech.comDevice ConfigurationThe XT6360 is a full-feature device based on a platform that allows rapid customization by market andapplication requirements. The XT6360 series offers highly configurable firmware which allows full controlof device reporting behavior. The customizable messages provides only the data req uired to support uniqueand evolving business needs. The XT6360 configuration is accomplished by loading 2 files:Script FileParameter FileThe 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 inputsto core functionality of the XT6360 .Script FileA Script file can contain an unlimited number of Triggers. When scripting the Triggers are groupinto individual Trigger blocks. A trigger block is comprised of the following sections:TriggerConditional Actions - optionalActionsEXAMPLE:trigger when Eq(InputState(0), 1) [Debounce(0, 0)]condact alwaysactionsrun BuildAndSendMsg(0, 2, 0, 0)DESCRIPTION:When ignition goes high a message is sent to the server.Important notes on Scripting:Park TimeXVirtual OdometerXQuick FenceXDevice DiagnosticsXMotionXAccelerometerXGeo-Zones50 CircularBack Up Battery250mAhCommunication ProtocolTCP, UDP , UDPwACKFirmware DownloadFTP
11Sales Engineeringsupport@xirgotech.com1. Each Trigger Block has one Trigger.2. The Trigger must test true for an action to occur.3. A test is usually made of one comparison. See Comparison table.4. Each Trigger Block can contain unlimited Conditional Action Blocks.5. Trigger Blocks and Conditional Action block will use the following when building a script:a. System Valuesb. Eventsc. Special Functionsd. Numbers6. Each Conditional Action Block may optionally 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 describedfor Trigger Block Test).8. Each Conditional Action Block must contain one Action Block.How Trigger Block Tests WorkEach Trigger Block is entered when the Trigger Block Test becomes true. Note that the Trigger Block is NOTentered WHILE the Test IS true, only the moment it becomes true. For example if you want to trigger actionswhen 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 willnot continue to enter the trigger block during subsequent evaluations where the speed remains above 80km/hr. Once the speed drops below 80 (for at least one evaluation), then the trigger block will be enteredagain 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 po ssible to cause the actions to be executed asfrequently as the speed oscillates. In order to avoid this, make use of the debounce specifiers.How Conditional Action Block Tests WorkUnlike Trigger Block Tests, Conditional Action Block Tests allow the action to be performed WHILE the test istrue. Continuing with the example above, let's say we want to further limit our actions to only execute themoment 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)]actionsAll Conditional Action blocks are independent. One is not dependent on the other.Condact Always This means the actions inside a Conditional Action Block will ALWAYS run when thetrigger Block's test(s) are true.Condact When When only one comparison is usedCondact Any The test is true when ANY of the comparisons is true.Condact All - ALL comparisons must be true for test to be true.
12Sales Engineeringsupport@xirgotech.comCOMPARISONS TABLE:COMPARISONDESCRIPTIONInRange(<a>, <b>, <c>)True when argument a is between argument b and argument c (inclusive)NotInRange(<a>, <b>, <c>)True when a is less than b or a is greater than c. b must be less than c.Eq(<a>, <b>)True when a equals b.NotEq(<a>, <b>)True when a is not equal to b.Gt(<a>, <b>)True when a is greater than b.Lt(<a>, <b>)True when a is less than b.GtEq(<a>, <b>)True when a is greater than/equal to b.LtEq(<a>, <b>)True when a is less than/equal to b.Test items (<a>, <b>, <c> above) should be one of:System ValueEventSpecial FunctionNumbers (constants)Note:See Appendices for Complete TablesDebounceDebounce(<hi>, <lo>) - where hi and lo are specified in seconds (max: 15). The 'Debounce Specify' is onlyused following certain tests (see below). When a debounce is specified, it means that a test is true only AFTERthe 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 valueSpecial function.
13Sales Engineeringsupport@xirgotech.comParameter FileThe parameter file is the setting for all of the XT6360 hardware peripherals, network behavior, andinputs to core functionality of the XT6360. The following table contains all the parameters that can beconfigured in a XT6360:Acceleration eventthresholdsAccelerometer reportcorrectionAPNs (GSM only)Crash event paramsDebounce settingsDestinationECU_ThresholdsFlag save maskGarmin BlacklistGeofenceInput default polarityIgnition senseMIP/SIP Control (TBD)Motion sensitivityNMEA stream outputOdom Ign Off accumPacket Creation AppendPacket Creation RecipePacket RetrySerial port settingsTimer durationOBD RPM and SpeedOBD Accel and DecelVariable save maskSee Appendix C for Parameter settings.Creating a Parameter File:1. The parameter settings are written and saved as a .txt file.2. Use :wycfg in front of the parameter your are configuring.3. 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 commandsi. :uyscr x 2 load the fileii. :vycfg Save the parameter fileBelow 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
14Sales Engineeringsupport@xirgotech.comMessagesHow to create a MessageThe XT6360 custom message allows users to select what fields of data to be sent in a message whentriggered. A message can contain up to 40 data fields and you can have up to 128 different messages.Refer to Appendix F - Message Field TableWhen defining a Message use the following syntax:pcr[<slot_index>] "<recipe_hex_string>"where:o<slot_index> is in the range 0 - 127o"<recipe_hex_string>" is a quoted string of hexadecimal bytes (represented by two asciicharacters) The Message Field Table in Appendix F contains the Hex values for theindividual fields that can be selected to create the Packet.String format: "<recipe_id><num_fields><field_0><field_1>...<field_N>"EXAMPLESpcr[0] "0003010306"opcr 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:oThe device can store and use 128 pcr (messages):wycfg pcr[0] …. :wycfg pcr[127]RecipeID is always in Hex.pcr[1] "14050103070809"opcr 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
15Sales Engineeringsupport@xirgotech.com:wycfg pcr[254] "fe0401031213"oPCR slot 2 will contain a Recipe string with 4 fields: PacketID, DeviceID, Hdop, and NumSatsrecipe_hex_string -" fe0401031213"RecipeID feNumber of fields 04Field 0 is Packet ID 01Field 1 is DeviceID 03Field 3 is Hdop 12Field 4 is Numsats 13Decoding a MessageKnowing the Reason Code and Packet Id you will know how to parse your data. These 2 fields willlet you know what triggered the message, what data is being sent, and in what order you’rereceiving the data. Refer to Appendix F for a complete list of Fields available. The table containsformatting information on the data in each field. Data is sent in Binary via UDP andacknowledgments can be used.Reason Code – Number to identify what triggered message was sentExamples of Reason Codes:Reason # Description01 Ignition On02 Periodic Report when Ignition On03 Ignition Off04 Periodic Report when Ignition Off05 Direction Change06 Speed Threshold Alert07 Acceleration Report08 Deceleration Report09 Idle Report10 Movement Start Report11 Movement Stop Report12 Park Time AlertNote:A Reason number is like the Event number you have in a XT2060.4001: Periodic location reporting with ignition ON
16Sales Engineeringsupport@xirgotech.compcr BreakdownA 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 recipespcr[<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>"Example:pcr 1 will contain a 5 fields : PacketID, DeviceID, Latitude, Longitude, and Altitudepcr[1] "01050103070809"RecipeID 01Number of fields 05Field 0 is Packet ID 01Field 1 is DeviceID 03Field 2 is Latitude 07Field 3 is Longitude 08Field 4 is Altitude 09Below is an example of a packet recipe that is partially decoded.EXAMPLE:pcr[1] "010E01040305060708090a0b12131415"(all values below are in Hex)Recipe ID 01Number of fields 0EField HEX ID Value Parsed CommentPacketID 01 01 01ReasonCode 04 03 03 (IGN. OFF MESSAGE)Serial # 03 088c1c72 143400050 Unit Serial NumberPacketSerialNum 05 205a 8282Etc..DATA FROM DEVICE CONVERTED FROM BINARY TO HEX USED IN TABLE ABOVEdatagram: 4 from 75.255.159.0:3000 (size: 31 bytes)
17Sales Engineeringsupport@xirgotech.comHEX---------------------------------------------------------------------------01 03 08 8c 1c 72 20 5a 54 81 be e1 01 f7 fb ddfa 3a 18 7a 07 0c 0a 1e 01 1c 04 00 15 ff ff------------------------------------------------------------------------------AcknowledgementsCurrently 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 theserial number of the packet sent to you, in the third and fourth byte. Therefore, the XIRGO unit willonly accept an acknowledgement payload of 88-88-01-04 for a packet sent with packet serialnumber 260 (hex 01-04).
18Sales Engineeringsupport@xirgotech.comAppendixA SYSTEMVALUESVALUEDESCRIPTIONUnixTimeSeconds since midnight Jan 1, 1970.GPSLatDegrees of latitude (unit 0.000001 degree)GPSLonDegrees of longitude (unit 0.000001 degree)GPSAltHeight above sea level (unit 0.1 meter)GPSHeadingHeading of travel (unit 0.1 degree)GPSSpeed2D speed in km/hr.InputsUser Input statesOutputsUser Output statesDriverId1Most recent Driver ID detected on 1 wire bus channel 1DriverId2Most recent Driver ID detected on 1 wire bus channel 2OdomDeltaCurrent value of Trip odometer 1 (in meters)GPSHDOPGPS Horizontal dilution of precision (unit 0.1)GPSNumSatsNumber of GPS satellites used for navigation solution.GPSOdomVirtual odometer in metersOdomDiffTBDBattVoltageDevice External voltage (vehicle system voltage, unit 0.1V)InternVoltageDevice Internal voltage (unit 0.1V)MotionState1 when vehicle is moving (as reported by ECU), otherwise 0.EngineState1 when engine has RPM (as reported by ECU), otherwise 0.WakeReasonBit mask value representing the reason for waking from sleep:0x00 = Woke on SMS or UDP message received0x01 = Woke on Wired Ignition0x02 = Woke on Input 10x04 = Woke on Input 20x08 = Woke on Input 30x10 = Woke on Input 40x20 = Woke periodic0x40 = Woke on vibration detected0x80 = Woke on supply voltage > 13.2V
19Sales Engineeringsupport@xirgotech.comAppendixB EVENTTABLEEVENTDESCRIPTIONINDEX RANGETimerExpired(<index>)Evaluates to 1 when timer is expired,otherwise 0index is in the range 0 - 31UserEventIsActive(<index>)Evaluates to 1 when a user event hasbeen injected into interpreter, otherwise0index is in the range 0 - 255.Use :xrmsg <index> to inject a messageinto interpreter. (Must be caught ininterpreter script with this eventfunction)AccelEventIsActive(<index>)Evaluates to 1 when an accelerometerevent is detected, otherwise 0index is in the range 0 - 3.GarminResponseReceived(<index>)Evaluates to 1 when a non-blacklistedGarmin response is received (andGarmin is active), otherwise 0index is in the range 0 - 5.0 = Ack (or Nak) packet (onlytriggered when specified inSendGarminMsg())1 = Unit ID (a.k.a. Garmin ESN)response2 = Product ID response3 = Throttle Message response4 = Ping response5 = Generic response; any responsethat isn't listed above and isn'tblacklistedGarminUserPayloadReceived(<index>)Evaluates to 1 when a payload (destinedfor garmin device) has been received,otherwise 0index can only be 0.This signals that a payload has beensent to the device by a user/server.Typically this would be used totrigger a SendGarminMsg() action.DriverIdRead(<index>)Evaluates to 1 when driver id is detectedon 1-wire channel <index>, otherwise 0index is in the range 0 – 1SystemEventIsActive(<index>)Evaluates to 1 when system event<index> is active, otherwise 0.index is in the range 0 - 17.0 = Reset1 = Wakeup2 = BootloaderUpgrade (TBD)3 = FWUpgrade4 = ScriptUpgrade5 = ParamSetUpgrade6 = OverlayUpgrade7 = ManualConfigChange8 = CellRegistrationChange9 = IPChange10 = SMSReceived11 = SMSSendOK12 = SMSSendFailure13 = UDPReceived14 = UDPSendOK15 = UDPSendFailure16 = PacketStorageEmpty17 = PacketStorageFull
20Sales Engineeringsupport@xirgotech.comAppendixC SPECIALFUNCTIONTABLESpecial FunctionDescriptionIndex RangeUserVar8(<index>)Evaluates to value stored in user variableindex is in the range 0 - 15UserVar16(<index>)Evaluates to value stored in user variableindex is in the range 0 – 7UserVar32(<index>)Evaluates to value stored in user variableindex is in the range 0 - 7FlagIsSet(<index>)Evaluates to 1 when flag is set, otherwise 0index is in the range 0 – 31GeofenceState(<index>)Evaluates to:-1=<index> is not configured0=outside fence1=inside fenceindex is in the range 0 - 49InputState(<index>)Evaluates to 1 when input is high/whencondition is true, otherwise 0index is in the range 0 - 6.0 = Ignition1 = Input 12 = Input 23 = Input 34 = Input 45 = Device in motion (via GPS)6 = Vehicle Battery > Threshold7 = Accelerometer reorientationvaliditySystemState(<index>)Evaluates to 1 when true, otherwise 0index is in the range 0 - 16.0 = Valid Registration1 = Valid IP2 = Valid GPS3 = Valid Script4 = DM Session Active5 = Accel Oriented6 = Bluetooth Discoverable(TBD)7 = Bluetooth Paired(TBD)8 = Bluetooth Authenticated(TBD)9 = Bluetooth Connected(TBD)10 = Bluetooth Powered(TBD)11 = Cellular Powered12 = GPS Powered13 = Garmin Powered14 = Motion Via Accel15 = Motion Via GPS16 = External Power
21Sales Engineeringsupport@xirgotech.comAppendixD ACTIONSTABLEActionSyntaxReset DeviceResetDevice()Reset ModemResetModem()Reset GPSResetGPS()Turn Off GPSTurnOffGPS()Turn On GPSTurnOnGPS()Set User VariableSetUserVar(<type>, <index>, <value>)type is in the range 0 - 2 where:0 = 8bit variable1 = 16bit variable2 = 32bit variableindex is in the range:0 - 15 for 8bit variables0 - 7 for 16bit variables0 - 7 for 32bit variablesvalue is in the range:-128 to 127 for 8bit variables-32768 to 32767 for 16bit variables–2147483648 to 2147483647 for 32 bit variablesAdjust User VariableAdjustUserVar(<type>, <index>, <adjust_amount>)type is in the range 0 - 2 where:0 = 8bit variable1 = 16bit variable2 = 32bit variableindex is in the range:0 - 15 for 8bit variables0 - 7 for 16bit variables0 - 7 for 32bit variablesadjust_amount is in the range:-128 to 127 for 8bit variables-32768 to 32767 for 16bit variables–2147483648 to 2147483647 for 32 bit variablesSet FlagSetFlag(<flag_index>)index is in the range 0 - 31.Clear FlagClearFlag<flag_index>)index is in the range 0 - 31.Start TimerStartTimer(<timer_index>)index is in the range 0 - 31.Stop TimerStopTimer<timer_index>)index is in the range 0 - 31.Rest TimerResetTimer(<timer_index>)index is in the range 0 - 31.
22Sales Engineeringsupport@xirgotech.comACTIONSYNTAXBuild And Send Msg<packet_id>, <reason_code>, <destination_id>, <ack>)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 - 10 = No Acknowledgement needed1 = Resend until acknowledgedClear LogTBDEnter Deep SleepEnterDeepSleep(<wake_mask>, <wake_minutes>)wake_mask is in the range 0x00 - 0xFF where:0x01 = Wake on Wired Ignition0x02 = Wake on Input 10x04 = Wake on Input 20x08 = Wake on Input 30x10 = Wake on Input 40x20 = Wake after wake_minutes0x40 = Wake on vibration detected0x80 = Wake on supply voltage > 13.2VEnter SleepEnterSleep(<wake_mask>, <wake_minutes>wake_mask is in the range 0x00 - 0xFF where:0x00 = Wake on SMS or UDP message received0x01 = Wake on Wired Ignition0x02 = Wake on Input 10x04 = Wake on Input 20x08 = Wake on Input 30x10 = Wake on Input 40x20 = Wake after wake_minutes0x40 = Wake on vibration detected0x80 = Wake on supply voltage > 13.2VSet Garmin PowerSetGarminPower(<power_state>)power_state is in the range 0 - 1 where:0 = Off1 = OnSend Garmin MsgTBDClear Trip OdomClearTripOdom(<odom_index>)index is in the range 0 - 1.Set OutputSetOutput(<output_index>)index is in the range 0 - 3Clear OutputClearOutput(<output_index>)index is in the range 0 - 3.Pulse OutputPulseOutput(<output_index>, <seconds_on>)index is in the range 0 - 3.seconds_on is in the range 1 - 65535.
23Sales Engineeringsupport@xirgotech.comFlash OutputFlashOutput(<output_index>, <blink_rate>)index is in the range 0 - 3.blink_rate is in the range 1 - 65535Hz.Clear Driver IdsClearDriverIds()Device Check InCheckInNow()
24Sales Engineeringsupport@xirgotech.comAppendixE PARAMTERTABLEAcceleration eventthresholds8aet4<direction (adlr)> <start_duration> <end_duration> <mg_thresh>Accelerometer reportcorrection1arc1<correction_factor>APNs4apn3"<apn_name>" "<username>" "<password>"Crash event params1cep3<mg_thresh> <poll_freq> <hist_depth>Debounce settings6idb2<on_sec> <off_sec>Destination10dst2"<ip>|<hostname>" <port>|<serial_port_id>ECU_Thresholds1vth4<brake_thresh> <accel_thresh> <speed_limit> <rpm_limit>Flag save mask1fsm1<32bit_mask>Garmin Blacklist16gbl5<flags> <pid> <size> <byte0> <byte1> (see example below)Geofence50gfn3<lat> <lon> <radius>Input default polarity4idp1<pullup_disable> (0=active_low,1=active_high)Ignition sense1ign3<source mask> <ign on sec> <ign off sec>MIP/SIP Control (TBD)1mip1<value>Motion sensitivity1mst1<motion_sensitivity_value>NMEA stream output4nso1<8bit_mask> (see NMEA mask below. One param for each of the 4serial outputs)Odom Ign Off accum2oio1<accum>Packet Creation Append16pca1"<append_hex_string>"Packet Creation Recipe128pcr1"<recipe_hex_string>"Packet Retry2prt1<sec>Serial port settings2sps2<baudrate> "<dps>"Timer duration32tmr2<sec> <auto_start>OBD RPM and Speed2ors2<rpm threshold> <rpm time sec> <mph threshold> <mph time sec>OBD Accel and Decel2oad1<obd accel> <obd decel> (1mph/sec, 1mph increments)Variable save mask1vsm1<32bit_mask>NMEA maskOne bit for each of the available NMEA sentences. Values can be added to stream more than one sentence type. Set mask to zero to stopstreaming.GPGGA 0x01GPGLL 0x02GPGSA 0x04GPGSV 0x08GPRMC 0x10
25Sales Engineeringsupport@xirgotech.comAppendixF MESSAGEFIELDSTABLEIDIDHexFieldSizeUnitsresolutionRangeNotes10x01PacketID1N/A10 to 255packet recipes can be labelled from0-255, but there are only 128recipe slots"20x02FmCustomHeader1N/A10 to 255value TBD (currently zero)30x03DeviceId/Unit Serial #4N/A1100000000 to999999999Unsigned integer representingnumeric ESN40x04ReasonCode110 to 255Unsigned integer50x05PacketSerialNum210 to 65535Unsigned integer60x06UnixTime410x0 to 0xffffffffUnsigned integer representingnumber of seconds since UnixEpoch70x07Latitude4degrees1.00E-06-2147.483648to2147.483647Signed integer decimal value of4byte hex string divided by1000000 (useful range -180.0 to180.0)80x08Longitude4degrees1.00E-06-2147.483648to2147.483647Signed integer decimal value of4byte hex string divided by1000000 (useful range -90.0 to90.0)90x09Altitude2m0.1-2147.483648to2147.483647Signed integer100x0aHeading2degrees1.00E-01-3276.8 to3276.7Signed integer (useful range 0.0 to360.0)110x0bGpsSpeed1km/hr10 to 255Unsigned integer120x0cInputStates1N/A10x0 to 0x1fbitfield: for example - LSB (bit:0)represents INPUT0130x0dOutputStates1N/A10x0 to 0x7bitfield: for example - LSB (bit:0)represents OUTPUT0
26Sales Engineeringsupport@xirgotech.com140x0eDriverIdCode14N/A10 to4294967295Unsigned integer represent uniqueiButton ID150x0fDriverIdCode24N/A10 to4294967295Unsigned integer represent uniqueiButton ID160x10OdometerDelta4m10 to4294967295170x11Flags410 to4294967295bitfield180x12Hdop1DOP0.10.0 to 25.5Unsigned integer190x13NumSats1N/A10 to 255200x14ReceiverSigStr1dBm1.23-113 to -75210x15CellularCarrierId210x0 to 0xffff220x16InternalBattVolts1V0.10.0 to 25.5Possibly using a 2 byte unsignedinteger representing mV (0 to65535)230x17VehicleBattVolts1V0.10.0 to 25.5Possibly using a 2 byte unsignedinteger representing mV (0 to65535)240x18LifetimeOdometer4m10 to4294967295Unsigned integer250x19AccelStartDateTime410x0 to 0xffffffffUnsigned integer representingnumber of seconds from UnixEpoch260x1aAccelStartLat4degrees1.00E-06-2147.483648to2147.483647Signed integer decimal value of4byte hex string divided by1000000 (useful range -180.0 to180.0)270x1bAccelStartLong4degrees1.00E-06-2147.483648to2147.483647Signed integer decimal value of4byte hex string divided by1000000 (useful range -90.0 to90.0)280x1cAccelStartSpeed1km/hr10 to 255290x1dAccelStartHeading2degrees0.10 to 3599300x1eMaxAccel2mG10 to 32767
27Sales Engineeringsupport@xirgotech.com310x1fAccelEventDuration1seconds0.10 to 255320x20AccelEndDateTime410x0 to 0xffffffffUnsigned integer representingnumber of seconds from UnixEpoch330x21AccelEndLat4degrees1.00E-06-2147.483648to2147.483647Signed integer decimal value of4byte hex string divided by1000000 (useful range -180.0 to180.0)340x22AccelEndLong4degrees1.00E-06-2147.483648to2147.483647Signed integer decimal value of4byte hex string divided by1000000 (useful range -90.0 to90.0)350x23AccelEndSpeed1km/hr10 to 255360x24AccelEndHeading2degrees0.10 to 3599370x25GeofenceId1N/A0 to 49840x54ObdOdometer4m10 to429496729532-bit unsigned integer850x55ObdTotFuelUsed4liters10 to429496729532-bit unsigned integer860x56ObdTotEngHours4hours10 to429496729532-bit unsigned integer870x57ObdVehicleSpeed2kph0.10 to 255016-bit unsigned integer880x58ObdEngRpm2rpm10 to 6553516-bit unsigned integer890x59ObdEngCoolantTemp2Celsius1-40 to 21516-bit signed integer900x5aObdFuelLevelPct2%0.10 to 100016-bit unsigned integer910x5bObdTotDrivingSec4s10 to429496729532-bit unsigned integer920x5cObdTotCruiseSec4s10 to429496729532-bit unsigned integer930x5dObdTotIdleSec4s10 to429496729532-bit unsigned integer940x5eObdTotIdleFuel4liters10 to429496729532-bit unsigned integer
28Sales Engineeringsupport@xirgotech.com950x5fObdHarshBreakTotCnt410 to429496729532-bit unsigned integer960x60ObdSpeedExceedTotTime410 to429496729532-bit unsigned integer970x61ObdRPMExceedTotTime410 to429496729532-bit unsigned integer980x62ObdHarchAccelTotTime410 to429496729532-bit unsigned integer1010x65ObdVIN17ascii
29Sales Engineeringsupport@xirgotech.comRegulatory Statements:FCC ID:Model: XT6360FCC ID: GKM-XT6360This product contains FCC ID: XPYSARAU260FCC Information to User:The XT6360 does not contain any user serviceable components and is to be used with approved antennas only. Anyproduct 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 equipmentshould 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 twoconditions:1. This device may not cause harmful interference, and2. 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 ofthe FCC Rules. These limits are designed to provide reasonable protection against harmful interference in aresidential installation. This equipment uses and can radiate radio frequency energy and, if not installed and used inaccordance with the instructions, may cause harmful interference to radio communications. However, there is noguarantee that interference will not occur in a particular installation. If this equipment does cause harmful interferenceto radio or television reception, which can be determined by turning the equipment off and on, the user is encouragedto 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 isconnected.4. Consult the dealer or an experienced radio/TV technician for help.
30Sales Engineeringsupport@xirgotech.comIndustry Canada (IC):IC: 10281A-XT6360This product contains IC: 8595A-SARAU260This device complies with Industry Canada licence-exempt RSS standard(s). Operation issubject to the following two conditions:(1) this device may not cause interference, and(2) this device must accept any interference, including interference that may causeundesired operation of the device.Le présent appareil est conforme aux CNR d'Industrie Canada applicables aux appareilsradioexempts 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 lebrouillage est susceptible d'en compromettre le onctionnement.Under Industry Canada regulations, this radio transmitter may only operate using anantenna of a type and maximum (or lesser) gain approved for the transmitter by IndustryCanada. To reduce potential radio interference to other users, the antenna type and its gainshould be so chosen that the equivalent isotropically radiated power (e.i.r.p.) is not morethan that necessary for successful communication.Conformément à la réglementation d'Industrie Canada, le présent émetteur radio peutfonctionner avec une antenne d'un type et d'un gain maximal (ou inférieur) approuvé pourl'émetteur par Industrie Canada. Dans le but de réduire les risques de brouillageradioélectrique à l'intention des autres utilisateurs, il faut choisir le type d'antenne et songain de sorte que la puissance isotrope rayonnée équivalente (p.i.r.e.) ne dépasse pasl'intensité nécessaire à l'établissement d'une communication satisfaisante.This radio transmitter (IC: 10281A-XT6360 , Model Number: XT6360 ) has been approvedby Industry Canada to operate with the antenna types listed below with the maximumpermissible gain and required antenna impedance for each antenna type indicated. Antennatypes not included in this list, having a gain greater than the maximum gain indicated forthat 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èlesi 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 pourchaque antenne type indiqué. Types d'antennes ne figurent pas dans cette liste, ayant un gainsupérieur au maximum gagner indiqué pour ce type, sont strictement interdites pour une utilisationavec cet appareil..

Navigation menu