SXL1 USERS MANUAL SXL1 Asset Tracking Solution 5116-21-00772| Revision 1.
|Page Proprietary and Confidential Revised 10-11-11
Table of Contents SXL1 .................................................................................................................................................5 Connecting the SXL1 to the Computer .................................................................................................5 SXL1_Programmer Software...............................................................................................................5 Standard Reporting Tab ...............................................
Motion Status (Byte 6 bit 0)......................................................................................................... 24 Message Cause (Byte 7 bits 7:6) ................................................................................................ 24 Engine Run Time (Byte 7:8)........................................................................................................ 24 Reserved (Byte 7 bits 5:0 and Bytes 8:9) ....................................................................
SXL1 The SXL1 is a small but fully self-contained, global satellite-based tracking device capable of determining location using GPS and reporting the location over a low earth orbit (LEO) satellite network. The SXL1 is powered by a field replaceable battery and requires no wiring or harnesses for use. The SXL1 communicates data via the Globalstar Simplex Data Service.
When launched, the program will auto-detect a SXL1 programmer. If a programmer is detected the SXL tab will appear along the top of the program window The SXL1_Programmer tool is structured as a standard Windows application with tabs along the top of the display area that groups similar configuration controls and displays.
SXL Tab The “SXL” tab only appears if the program detects that a SXL1 programmer is attached to the computer. The SXL tab contains functions specific to the RF link between the transceiver in the SXL1 and the SXL1 programmer. When the program is first opened and it detects a SXL1 programmer, it will initiate a scan for SXL1 devices within its RF range. The scan will last approximately 7.5 seconds.
Standard Reporting Tab The “Standard Reporting” tab is used to configure the device for routine position reporting. The SXL1 can be configured to report on a time delay between reports (Standard Interval) or at a specific time of day (Time of Day). The pull down dialog box is used to select one or the other mode. Or Note that if Standard Interval is selected, the user may use the “Days, Hours, Minutes” controls to set the amount of time between a standard location report.
Note: When programming SXL1 for Time of Day reporting: Programming for Time of Day mode within 1 hour of the scheduled time will result in the first days message being pushed out 24 hours. Also, if the device time is not current, the first time of day event may take a complete 24 hours from time of program to complete. Users should thus allow up to 48 hours for the unit to begin reporting on schedule. Time of day reporting mode is set in UTC.
Also, on the Standard Interval tab is the dialog to configure the Engineering Message. The Engineering Message is a transmitted message containing data related to the health and operation of the SXL1. It is advisable to send the Engineering Message routinely, typically monthly or bi-weekly. The Engineering message interval may also be configured for time of day operation. This is useful, for example, when requiring a daily count of engine runtime.
In Motion: In Motion mode configures the device to detect start and stop of motion and report at a set interval while remaining in motion. The Sensitivity and Start and Stop Time configurations are as described earlier. The Subsequent Message Interval controls set the time between reports while the unit remains in motion. The Subsequent Message dialog (count) is ignored. Triggered Reporting Tab The “Triggered Reporting” tab is used to configure the device for alarm detection and reporting.
Alarm: Alarm magnet mode configures the device to initiate an alarm message operation. In this mode the magnet is recognized by the SXL1 but does not trigger “sleep mode”. When the device detects the magnet inserted for at least 15 seconds, the device will arm itself for alarm on magnet removal. The alarm is triggered on magnet removal only, not insertion. The dialog “GPS FIX?” checkbox is used to instruct the SXL1 to send an alarm message with or without GPS location.
Send Engineering Message: This button triggers the SXL1 to send an on-air Engineering Message. Send Custom Payload: This button triggers the SXL1 to send an on-air Raw Data Message containing the first 8 bytes entered into the text box to the right. The data must be entered in hexadecimal form. Query GPS: This button triggers the SXL1 to get a GPS fix and populate the Latitude, Longitude and Fix time textboxes above the button.
Profiles Tab The “Profiles” tab is used to save and retrieve device configuration files called Profiles. A configuration may be saved to a new file by entering a filename in the topmost textbox and selecting “Save as New Profile”. Existing profiles appear in the bottom textbox and may be loaded into the tab configuration boxes by selecting “Load Profile” or deleted by selecting “Delete”. The “Save as Selected” allows a previously saved profile to be edited. Profiles are kept in a database file C:\Program F
Each of the 3V batteries has an operational range of 2.1 to 3.0V, with end of life near 1.85V (3.7V for each series pair). New Battery Installation For installation of a battery on a new SXL1, remove battery from packaging. Ensure that the gray neoprene gasket is in place around the oval connection port to the electronic assembly section of the SXL1. Verify that you have two 6/32 T10 Torx security screws to affix the battery to the unit.
SXL1 Serial Message Protocol The SXL1 uses the on board RF transceiver and the programmer for both configuration and support of wireless sensors. The SXL1 programmer can accept serial commands from a sensor or it can be connected directly to a open/closed or analog sensor. This user’s manual contains the messaging for serial wireless sensors only. When the programmer is connected to an open/closed or analog sensor it uses the following protocol to send the appropriate message to the SXL1 for transmission.
Serial CRC Algorithm The CRC checksum uses the CCITT-16 Reversed (0x8408) algorithm: The Security Field is a 16-bit CRC of all of the previous fields including the preamble, length, and command bytes. The remainder is initialized to all 1's (0xFFFF) and the CRC is inverted before being sent.
Remote Data Command (message type 0x04) The SXL1 supports remote sensors or other devices that force a satellite transmitted message using this command. The external interface may relay up to 8 bytes of data for transmission by the SXL1 over the system. Format of the user data is undefined. The SXL1 acknowledges receipt of the Remote Data Command immediately, then sends the data to the satellite system using message type 0xCF (Remote Message pg 24).
SXL1. Each message below describes the payload region of the satellite burst message. The network protocol is removed from this description for clarity. Network operators utilizing the resulting internet packets must refer to Globalstar documentation regarding Simplex Data Service use. All on-air SXL1 messages follow the payload format depicted below. Because the satellite packet is restricted to 9 bytes total, the message fields are used sparingly.
Position (Bytes 2-8) The Latitude and Longitude information is encoded in these bytes. Refer to Appendix B for calculating the Lat and Long from this information. Status (Byte 9) The Status byte contains various operational information about the SXL1. Battery Status (Bits 2:0) These bits hold the current battery status, calculated by the device and reflected proportionally in this field. Battery status starts at seven (7) and counts down in 12.5% resolution of usage.
1110 Analog Custom Sensor 1 1111 Digital Custom Sensor 7 Note: Remote message cause 0 through 7 translate to message cause 8 through 15 (bit 4 = 1 = remote alarm initiated). The message cause field alternatively can hold engine run time data as described below in the bit 9 description. Engine Run Time (Bit 9) This bit is zero unless the device is configured for engine run time (Cut Wire Configuration in Run State byte of the configuration message).
Termination Message The SXL1 automatically stops functioning, issuing a termination message upon completion of the termination count as configured by the configuration serial command. The Termination Message is the same format as a location message except the message type is 0xD3.
undefined Message Cause 6 6 (5:4) (7:6) Engine Run Time 7-8 16 undefined 00 = Engineering interval expired 01 = First run of device 10 = Watchdog reset 11 = Low battery warning (Engineering message generated upon reaching 12.5% remaining) Hours of cut wire detection accumulated. Message Type The SXL1 Engineering message shows 0xD7 in the first byte denoting an Engineering message.
Termination Reset (Byte 6 bit 1) This bit toggles each time the Termination Count is reset. Motion Status (Byte 6 bit 0) This bit shows whether the device is moving or stationary. 0 is stationary and 1 is moving.
Appendix Appendix A: Regulatory Notices The SXL1 contains a GPS radio receiver and simplex radio transmitter as well as a digital-computing host interface board. The FCC requires the following notification for the device in compliance with 47CFR 15.105 for this Class B digital device. Full product test reports are available from Numerex upon request. NOTE: This equipment has been tested and found to comply with the limits for a Class B digital device, pursuant to Part 15 of the FCC Rules.
NOTICE: This equipment complies with the FCC RF Exposure Limits. A minimum of 20 centimeters (8 inches) separation between the device and the user and all other persons should be maintained. FCC verified transmitter FCC ID: TWV-SXL1 The SXL1 is certified to the following safety standards: UL60950-1/CSA C22.2 No. 60950-1, Second Edition: Safety of Information Technology Equipment, Dated March 27, 2007.
? ? ? ? The SXL1 encodes 180 degrees of LATITUDE as a 24-bit (3-byte) signed integer. The SXL1 encodes 360 degrees of LONGITUDE as a 24-bit (3-byte) signed integer. The encoded LATITUDE data is the first three bytes of the location data payload The encoded LONGITUDE data is the next three bytes of the location data payload.
Appendix C: SXL1 Data Interface Scope This document describes the SXL1 Data Interface (Datastreams ) transport methods and data formats available for machine-t o-machine communications from a device to a Value Added Reseller (VAR) or customer’s back office. All methods and formats described in this document can be configured in the FELIX Software Administration website. It is assumed the reader is familiar with the terms and technology described in this document.
longitude: The longitude reported in the forwarded tracker message, and determined by the hexadecimal field in the raw payload. address: The address calculated by the latitude and longitude. The address is an approximation made on available geographic data, it is not intended to be exact. street_address: The approximation of the number and street information by the latitude and longitude. The address number may or may not be present, depending on the street type.
PAGE 313. Determine the Failure Response. If FELIX is to ignore failures, retry for a certain number of attempts or retry for a certain number of minutes. 4. Fill in appropriate Contact Information for Numerex to use in case of failure to forward. 5. Save your changes. When saving a Delivery Method, FELIX will verify a connection can be made prior to saving the changes. 6. Next, you must create a Trigger. Figure 1: Create Delivery Method Figure 2: Save Delivery Method Create Trigger.
2. 3. 4. 5. Choose the Trigger Source. Every Trigger Source is determined by an incoming message from the tracker. In the case of triggering on payloads, the available payload fields are dependent on the GPS Device Type as some fields are specific to certain devices. Choose the desired Message Type, Payload Field, Operator and Value. See the screenshot to see the configuration for a Trigger that will initiate a Datastream if the battery level gets below 50%. Click Save.
Figure 4: Create Action Figure 5: Assign Assets to Action Queuing, VAR Back Office Acknowledgement, and Error Notifications With the use of user defined data transfers it is up to the VAR to make sure data is being received at the VAR’s back office properly. The Datastream assumes the VAR’s back office is functioning properly and handling data without error.
After a set number of failed attempts or error messages an alert will be emailed to an address provided notifying the VAR of failure. Custom Defined Methods Datastreams are capable of defining custom formats, transport layer methods, and acknowledgement states as defined by the VAR. Methods include but are not limited to: TCP, UDP, SSL, FTP, SOAP, etc. Data encapsulation formats include but are not limited to: CoT (Cursor On Target), custom XML schemas, custom binary encoding, etc.
