GLOBALSTAR PROPRIETARY AND CONFIDENTIAL INFORMATION Use or disclosure of data contained on this sheet is subject to the restrictions in the Distribution Statements on the title page of this document.
Version: 0.8 Date: June 18, 2020 Document number: TBD Globalstar, Inc. 1351 Holiday Square Blvd. Covington, LA70433 USA Copyright © Globalstar Inc., 2020. All rights reserved. Printed in the United States of America. Distribution Statements: GLOBALSTAR CONFIDENTIAL AND PROPRIETARY INFORMATION – All data and information contained in this document are confidential and proprietary to Globalstar, Inc.
Table of Contents Foreward (TBD)....................................................................................................................... Error! Bookmark not defined. List of Tables (TBD) ................................................................................................................. Error! Bookmark not defined. List of Figures (TBD) ................................................................................................................ Error! Bookmark not defined.
.2 4.1.1.1 “?” ........................................................................................................................................................... 20 4.1.1.2 “esn” ....................................................................................................................................................... 21 4.1.1.3 “data” ...................................................................................................................................................
4.3 4.2.2.17 “Cancel Proprietary Track/Proprietary Motion Activated Track” command ....................................... 40 4.2.2.18 “Proprietary Track Status” query ........................................................................................................ 41 4.2.2.19 "Tracking Statistics" query .................................................................................................................. 43 4.2.2.20 "GPS Statistics" query .........................................
4.4.5 ON AX50324 low-level load via AXSEM proprietary programming interface. ............................................. 72 4.5 Example CRC calculation routines for serial packets ........................................................................................... 72 4.6 24-bit location format ......................................................................................................................................... 75 4.6.1 CALCULATING LATITUDE .................................
Distribution Statements: GLOBALSTAR CONFIDENTIAL AND PROPRIETARY INFORMATION – All data and information contained in this document are confidential and proprietary to Globalstar, Inc. WARNING – This document may contain technical data whose export is restricted by the Export Administration Act of 1979, as amended, Title 50, U.S.C., App 2401 et seq. Violations of these export laws are subject to severe criminal penalties. Disseminate only in accordance with such export laws.
1 Introduction 1.1 Purpose This document describes the physical, electrical, and functional characteristics of the ST100 satellite transmitter module with Bluetooth Low Energy. The information contained in this document is intended to provide the VAR/Integrator with the necessary technical information required to configure and use the module in a custom application.
Under VAR setup and configuration, and normal use by the end user, communication with the device is via a Bluetooth Low Energy (BLE) GATT/Modem interface with a mixture of ASCII and binary command/query protocols. The ST100 Board is a small, low-profile device with the dimensions shown below: Figure 1 Board Physical Dimensions 1.4 Certifications Bluetooth LE RoHS WEEE 2 Application 2.1 Theory of Operation for Globalstar Simplex The ST100 Board operates on the Globalstar LEO satellite network.
Figure 2 LEO Constellation Since the satellite position is constantly changing, simplex devices on the ground will transmit (with no knowledge of any of the satellites locations) and the transmission may be received by one or more satellites. These satellites will then relay the message to the nearest satellite gateway as shown below.
There are brief periods of time where there is no satellite in range of the simplex transmitters due to obstructions and/or satellite coverage geometry. Since a simplex device has no way of knowing if a transmitted message has been successfully received, the ST100 Board is designed to send multiple (redundant) transmissions for each message being sent over the Globalstar network. The default value for the number of redundant transmissions per message is 3.
The transmission sequence for a two-packet message using the default setting of 3 redundant transmissions is shown below. For normal conditions where the transmitter has an open view of the sky, this will result in a better than 99% chance that the message will be received. GLOBALSTAR PROPRIETARY AND CONFIDENTIAL INFORMATION Use or disclosure of data contained on this sheet is subject to the restrictions in the Distribution Statements on the title page of this document.
2.2 Block Diagram 2.3 Handling of Electrostatic Sensitive Devices Some components on the ST100 PCB are sensitive to electrostatic discharge (ESD). The following general guidelines can help reduce damage due to ESD. 1. Use a grounding bracelet if possible, to minimize charge build-up on personnel. 2. Handle the ST100 PCB by the long edges without touching components or printed circuit paths. The long edges measure approximately 2" (50.8mm). The short edges measure approximately 1" (25.4mm).
2.4 Wiring If the ST100 will be line-powered, proper installation and field wiring practices are important to follow. Users and installers should familiarize themselves with the requirements of all applicable codes, laws, and standards. 2.5 Noise Sources Electrical noise is an important consideration in any installation of the ST100. When possible, sufficient physical separation should be maintained between electrical noise sources and the ST100. 2.
2.8 External Connections The picture (below) depicts the PCB external interfaces. GPS/Satellite u.FL connector Solar (+) terminal Solar (-) terminal Battery (+) terminal Battery (-) terminal 14 pin connector 2.8.1 External Antenna Option The ST100 has provisions where an external antenna can be used on either the Bluetooth and/or the GPS / Satellite antennas. If an external antenna is used, care should be taken when connecting the external antenna to the u.FL connector - Hirose part # U.
Regulatory Note: The ST100 was certified using its Satellite and Bluetooth PCB Trace antennas. The use of any external antennas will require additional regulatory testing plus approval from Globalstar Engineering. 2.8.2 Battery The ST100 has terminals on the PCB where a battery can be soldered to. The user / installer should carefully note the location of the positive and negative terminals marked on the PCB and solder the battery accordingly.
adequate for use with the selected battery. 3. Regulatory Note: If a battery is used, it will be the responsibility of the VAR/installer to obtain / verify the relevant battery approvals / certifications for where the end-product will be used (i.e. IEC62133 approval) 4. Due to the solar charger chip’s 100mA max input current, the max recommended battery size is 500mAh. 2.8.3 Solar Panel The ST100 has terminals on the PCB where a solar panel can be soldered to.
tested as acceptable. 2. The VAR/installer should review the pairing of solar panel / battery and determine if the solar panel is adequate for use with the selected battery. 3. This value is based on the efficiency of the solar charger chip, which is typically 80-85%. 4. The solar panel should be chosen for outdoor use, if the end-application will be mostly outdoors. 2.8.
3 General Specifications Table 4 – Operating Conditions Component Temperature Range (without battery) Board Functional Temperature Range Board Storage Temperature Range (without battery) Power requirements (Battery Input) Input protection (Battery Input) Power requirements (Solar Input) External Serial Port Parameters Current Drain Satellite RF output GPS / Satellite antenna gain Bluetooth Low Energy (BLE) Bluetooth antenna gain -30 to +70°C (Note 1) -20 to +60°C -40 to +85°C 3.4V to 5.
6. The maximum current the solar charger chip on the ST100 board will accept is about 100mA, regardless of solar panel size. 7. If connecting a 5V source to the solar input, the source must be current limited to 100mA. 8. The external serial port consists of 4 GPIO pins connected to the ST100 Bluetooth processor. 9. The 24.5dBm is the conducted power going into the antenna.
abort bursts hardware firmware test_cw test_packet test_mod setup hib fgd tfg frr raw bpm auth edfg 4.1.1.2 “esn” Prints the unit ESN in the form “0-123456”. Command: esn Arguments: None Example: esn Example response: esn: 0-123456 4.1.1.3 “data” Sends raw data via the Simplex Satellite modem. The example shown here would send that hex string and would require 2 9 byte simplex packets.
4.1.1.4 “abort” Aborts a redundant burst in progress. Note does not cancel a running tracking session. Command: abort Arguments: None Example: abort Example response: Message Aborted 4.1.1.5 “bursts” Returns the remaining bursts for a message in progress. Command: bursts Arguments: None Example: bursts Example response: 2 remaining 4.1.1.6 “hardware” Returns the ST100 Board hardware version Command: hardware Arguments: none Example: hardware Example response: Hardware Version: 1.0.0-F0 4.1.1.
Example: firmware Example response: Firmware version: 1.0.0 (010000-010000) 4.1.1.8 “setup” Command: setup Arguments: Sending the command with no arguments returns the current settings. If sent with arguments, the response is the same, confirming the settings. Example: setup 0 3 60 120 Example response: Setup: Channel: 0 Bursts: 3 Min Interval: 60 Max Interval: 120 All arguments must be present.
4.1.1.9 “raw” Send raw binary command to the ASIC Command: raw Arguments: A hex string command to send to the ASIC (See “Binary Serial Packet Commands” section). CRC is omitted, and is generated and appended by the Nordic firmware as it sends the command to the ASIC Example: raw AA0501 Example response: Response: AA090100123456 This allows any command in the “Binary Serial Packet Commands” section to be sent to the ASIC.
4.1.1.11 “auth” Unlocks privileged commands. Command: auth Arguments: A 32 bit unlocking key in Hexadecimal Example: auth 11764BA3 Example response: Auth success! The following commands require a unique authorization key to be issued via this command before they will be recognized: “bpm”, “raw”, “edfg” The commands requiring “auth” are unlocked for 30 seconds after sending the auth command. Sending the commands multiple times (e. g. “raw”) DOES NOT “bump out” the 30 second timer.
4.2.1 Serial Packet Format Preamble Length Command Data CRC (1 byte) (1 byte) (1 byte) (variable length) (2 bytes) Preamble Length Command Fixed pattern 0xAA Total number of bytes in the serial packet including the preamble Command type (See Table 5 Serial Packet Type). Responses to commands carry the same command type as the command that initiated the answer Data associated with the command or answer 16 bit CRC Data CRC Figure 4 Serial Packet Format 4.2.
Response: AA 05 00 D9 C4 The example above commands the ST100 Board to send 9 bytes of user defined data over the Globalstar Simplex network. If the ST100 Board receives a properly formatted Send Data command, it returns an acknowledge response as shown above. If the command is not properly formatted, it will return the NAK response AA 05 FF A1 CB. 4.2.2.
0x04 Command: Leader Len Cmd CRC1 CRC2 AA 05 04 FD 82 AA 05 04 FD 82 Response: Leader Len 04 count CRC1 CRC2 AA 05 04 XX CC CC Example Response: AA 06 04 00 F4 33 Where the bursts remaining returned is: 0 GLOBALSTAR PROPRIETARY AND CONFIDENTIAL INFORMATION Use or disclosure of data contained on this sheet is subject to the restrictions in the Distribution Statements on the title page of this document.
4.2.2.5 Query Firmware Version (0x05) The Query Firmware Version command requests the ST100 BOARD to return the current firmware version. 0x05 Command: Leader Len Cmd CRC1 CRC2 AA 05 05 74 93 AA 05 05 74 93 Response: Leader Len 4 FW major FW minor AA 8 5 XX XX Example Response: FW Build XX CRC1 CRC2 CC CC AA 08 05 01 07 04 E0 6A Where the firmware version returned is: 1.7.4 4.2.2.6 Setup (0x06) The Setup command requests the ST100 BOARD to use the specified setup parameters.
Where the setup information is: • • • • RF channel : # of bursts: Minimum Burst Interval: Maximum Burst Interval: 00 03 18 30 Channel A 3 bursts per message 0x18 = 24, 24 x 5 = 120 seconds 0x30 = 48, 48 x 5 = 240 seconds 4.2.2.7 Query Setup (0x07) The Query Setup command requests the ST100 BOARD to return the current setup parameters.
4.2.2.8 Query Hardware Version (0x09) The Query Hardware Version command requests the ST100 BOARD to return the current hardware version information.
Set GPS Timeout command format Byte Bits Parameter 0 0–7 Leader 1 0–7 Length 2 0–7 Command Code. Description Always a value of 0xAA. 0x07 3-4 0 – 15 GPS timeout value 5-6 0 – 15 CRC 0x23 = Set GPS timeout GPS timeout value in seconds. Must be between 60 and 300 seconds (1 to 5 minutes). Factory default is 4 minutes (240 seconds) Example response: AA 05 23 [CRC] [CRC] 4.2.2.
Get GPS Timeout Query response Byte Bits Parameter 0 0–7 Leader 1 0–7 Length 2 0–7 Command Code. 3-4 0 – 15 GPS timeout value 5-6 0 – 15 CRC Description Always a value of 0xAA. 0x07 0x24 = GPS Timeout Query GPS timeout value in seconds 4.2.2.11 “SPOT GEN3 emulation. The ST100 board has the ability to emulate the tracking and messaging modes of a SPOT GEN3 device for particular applications.
0x10 = RESERVED 0x20 = Low Battery (Tracking rate reduced to low battery rate) 0x40 = GPS location invalid 0x80 = GPS location of low confidence 4.2.2.13 “Proprietary Track” command This command allows the initiation of a periodic track message with user defined data prepended and appended to the latitude and longitude fields. A periodic 9-byte custom track message, transmitted nominally at the interval specified, will result.
Proprietary Track command format Byte Bits Parameter 0 0–7 Leader 1 0–7 Length 2 0–7 Command Code. 3 -4 0 - 15 Interval 5 0-7 Byte 0 value 6 0-7 Byte 7 value 7 0-7 Byte 8 value 8-9 0 - 15 CRC Example Command: Description Always a value of 0xAA. 0x0A (10 decimal) 0x30 = Initiate proprietary track. Interval in minutes between the track points. 2 to 65535 minutes. (A setting of 2 actually results in a 2.
Initiate proprietary track response Byte Bits Parameter 0 0-7 Leader 1 0-7 Length 2 0-7 Command Code. 3 -4 0 - 15 CRC Example Response: AA 05 30 5A F5 Example Payload: 0xAA2B4856BFF032BBCC Where: Description Always a value of 0xAA. 0x5 0x30 = ACK or 0xFF = NAK 2B4856 is the 24-bit latitude 30.433051586151 (North) BFF032 is the 24-bit longitude -90.086817741394 (West) See section 4.6: “24 bit location format” for documentation of the encoding/decoding of Globalstar on-air location data.
While in Motion Activated Track mode, the accelerometer sub-system will remain powered during the standby periods in between transmissions and the accelerometer standby current will be the “Standby mode supply current w/Accelerometer” value in Table 4.
Where: • • • • Period : Payload Byte 0: Payload Byte 7: Payload Byte 8: 0x000A (10 minute intervals) 0xAA 0xBB 0xCC Initiate proprietary track response Byte Bits Parameter 0 0-7 Leader 1 0-7 Length 2 0-7 Command Code. 3 -4 0 - 15 CRC Example Response: AA 05 30 5A F5 Example Payload: 0xAA2B4856BFF032BBCC Where: Description Always a value of 0xAA. 0x5 0x30 = ACK or 0xFF = NAK 2B4856 is the 24-bit latitude 30.433051586151 (North) BFF032 is the 24-bit longitude -90.
Byte Bits Parameter 0 0–7 Leader 1 0–7 Length 2 0–7 Command Code. 3 -4 0 - 15 Interval 5 0-7 Byte 0 value 6 0-7 Byte 7 value 7 0-7 Byte 8 value 8-9 0 - 15 CRC Description Always a value of 0xAA. 0x0A (10 decimal) 0x35 = Initiate proprietary dock mode track. Interval in minutes between the track points. 2 to 65535 minutes. (A setting of 2 actually results in a 2.5 minute interval, any other value results in an interval of that many minutes).
Example Command: AA 08 31 AA BB CC 21 FA Where: • • • Payload Byte 0: Payload Byte 7: Payload Byte 8: 0xAA 0xBB 0xCC Update Proprietary Track Data response Byte Bits Parameter 0 0-7 Leader 1 0-7 Length 2 0-7 Command Code. 3 -4 0 - 15 CRC Example Response: Description Always a value of 0xAA. 0x5 0x31 = ACK or 0xFF = NAK AA 05 31 D3 E4 4.2.2.
Example Command: AA 05 32 48 D6 Cancel Proprietary Track response Byte Bits Parameter 0 0-7 Leader 1 0-7 Length 2 0-7 Command Code. 3 -4 0 - 15 CRC Example Response: Description Always a value of 0xAA. 0x5 0x32 = ACK or 0xFF = NAK AA 05 32 48 D6 4.2.2.18 “Proprietary Track Status” query Proprietary Track Status Query Byte Bits Parameter 0 0-7 Leader 1 0-7 Length 2 0-7 Command Code. 3 -4 0 - 15 CRC Description Always a value of 0xAA.
Proprietary Track Status Query Response Byte Bits Parameter Description 0 0-7 Leader 1 0-7 Length 2 0-7 Command Code. 3 0-7 Suspend / Power State 0x00 = Fully suspended 0x01 = Low battery / Partial Suspend 0x02 = Fully unsuspended 4 0-7 Specific track mode 0x30 = Proprietary Track 0x34 = Motion activated proprietary track 5–6 0 - 15 Track interval Value of interval in minutes 7 0-7 Byte 0 value The value being transmitted as byte 0.
4.2.2.19 "Tracking Statistics" query Tracking Statistics Query Byte Bits Parameter 0 0-7 Leader 1 0-7 Length 2 0-7 Command Code. 3 -4 0 - 15 CRC Description Always a value of 0xAA. 0x5 0x39 = Tracking Statistics Query Tracking Statistics Response GLOBALSTAR PROPRIETARY AND CONFIDENTIAL INFORMATION Use or disclosure of data contained on this sheet is subject to the restrictions in the Distribution Statements on the title page of this document.
Byte Bits Parameter 0 0-7 Leader 1 0-7 Length 2 0-7 Command Code. 3 0-7 Reset Flag 4 0-7 Suspended state 5 0-7 Resolution of next field 6-7 0 - 15 Time remaining in current interval 8 0-7 9 - 10 0 - 15 11 0-7 12 13 0 - 15 Track burst tries remaining Time to next transmission in burst. Number of attempts remaining in interleaved burst Time to next interleaved burst Description Always a value of 0xAA.
14 0-7 Number of packets in interleaved burst message 15 16 0 - 15 Total messages in mode 17 18 0 - 15 CRC The number of packets in the interleaved burst message. Note: As a "quirky feature" this value does not clear when the burst finishes, and if no interleaved burst is running, this will show the number of packets that were in the last interleaved burst that ran. It can be determined if a burst is currently running by examining bytes 11, and 12-13.
Byte Bits Parameter 0 0-7 Leader 1 0-7 Length 2 0-7 Command Code. 3 0-7 Reset Flag 4-5 0 - 15 Grand total fixes 6-7 0 - 15 Total fix fails 8-9 0 - 15 Mean fix time 10 11 0 - 15 12 13 0 - 15 14 0-7 15 16 0 - 15 17 0-7 Description Always a value of 0xAA.
4.2.2.21 "Transmitter Statistics" query. Transmitter Statistics Query Byte Bits Parameter 0 0-7 Leader 1 0-7 Length 2 0-7 Command Code. 3 -4 0 - 15 CRC Byte Bits 0-7 Leader 1 0-7 Length 2 0-7 Command Code. 3 0-7 Reset Flag 4-5 0 - 15 6-7 0 - 15 Total messages in mode Total Packets Transmitted 0 - 15 Always a value of 0xAA.
4.2.2.22 “Send Redundant Burst with GPS” command This command is used to initiate a redundant bursted message (as setup in STX configuration). Bytes 1 – 6 of the first packet of the message shall contain latitude and longitude in standard Globalstar 24-bit format. Since each on-air message must be a multiple of 9 bytes, the message will contain up to 16 9-byte packets depending on the size of the payload.
Where: • • • • • • • • • • • • Payload Byte 0: Payload Byte 7: Payload Byte 8: Payload Byte 9: Payload Byte 10: Payload Byte 11: Payload Byte 12: Payload Byte 13: Payload Byte 14: Payload Byte 15: Payload Byte 16: Payload Byte 17: 0x01 0x02 0x03 0x04 0x05 0x06 0x07 0x08 0x09 0x0A 0x0B 0x0C Send Redundant Burst with GPS response Byte Bits Parameter 0 0-7 Leader 1 0-7 Length 2 0-7 Command Code. 3 -4 0 - 15 CRC Description Always a value of 0xAA.
Query Location Command Byte Bits Parameter Description 0 0–7 Leader 1 0–7 Length 2 0–7 Command Code. 3-4 0 – 15 CRC Always a value of 0xAA. 0x05 0x25 = Query Location command This response is sent to response to a “Query Location” command. The timestamp fields represent the exact second the fix being reported was obtained. Query Location Response Byte Bits Parameter 0 0–7 Leader 1 0–7 Length 2 0–7 Command Code.
12 - 14 0-23 Longitude 15 - 16 0-15 CRC 24-Bit Signed Integer encoded Longitude. 360 degrees of longitude in signed binary. Byte 6 is MSB. Positive longitude corresponds to East longitudes. Will contain the response CRC Command: AA 05 25 76 B2 Response: AA 0C 25 2B 48 5B BF F0 2B 00 2E A1 Latitude = 0x2B485B (30.4331), Longitude = 0xBFF02B (-90.0870) 4.2.2.24 “Set Lifetime” command This command sets the lifetime of the device.
0 0–7 Leader 1 0–7 Length 2 0–7 Command Code. 3-4 0-15 CRC Always a value of 0xAA. 0x05 0x70 = “Set Lifetime” Will contain the response CRC The first time the unit gets a GPS fix after this command is issued, an end date will be calculated. The factory default lifetime is 1 month. If this command is never issued, the unit will expire 1 month after getting its first GPS fix.
4.2.2.25 “Query Lifetime Status” command This command is used to query the lifetime status of the unit. Query Lifetime Status Command Byte Bits Parameter 0 0–7 Leader 1 0–7 Length 2 0–7 Command Code. 3-4 0-15 CRC Description Always a value of 0xAA.
Byte Bits Parameter 0 0–7 Leader 1 0–7 Length 2 0–7 Command Code. 3 0-7 Programmed lifetime Description Always a value of 0xAA. 0x0A (10 decimal) 4 0-7 End Month 5 0-7 End Day 6 0-7 End year 7 0-7 Alive or Dead 8-9 0 - 15 CRC 0x71 = Query Lifetime Status The number of months for which the device was originally programmed. Contains the month of the expiration date.
Byte Bits Parameter Description 0 0–7 Leader 1 0–7 Length 2 0–7 Command Code. 3-4 0 - 15 Rate 5-6 0 – 15 CRC Always a value of 0xAA. 0x07 0x84 = Set minimum track rate command Rate in minutes, MSB first Response: AA 05 84 Note, if a track mode (0x30, 0x34, or 0x35) is already active, this command will be NAKed if a value of greater than the track already running is sent.
0 0–7 Leader 1 0–7 Length 2 0–7 Command Code. 3-4 0 - 15 Rate 5-6 0 – 15 CRC Always a value of 0xAA. 0x07 0x85 = Query minimum track rate Rate in minutes, MSB first 4.2.2.28 "Suspend/Unsuspend" command The purpose of this command is to suspend tracking due to battery low, as well as to suspend tracking when the unit is in the "waiting to activate" state.
Byte Bits Parameter 0 0–7 Leader 1 0–7 Length 2 0–7 Command Code. 3-4 0-15 CRC Description Always a value of 0xAA. 0x05 0x81 = Suspended state query Will contain the CRC Suspended state query response Byte Bits Parameter 0 0–7 Leader 1 0–7 Length 2 0–7 Command Code. Description Always a value of 0xAA.
Byte Bits Set low battery rate command Parameter Description 0 0–7 Leader 1 0–7 Length 2 0–7 Command Code. 3-4 0 - 15 Rate 5-6 0 – 15 CRC Always a value of 0xAA. 0x07 0x82 = Set low battery track rate command Rate in minutes, MSB first Response: AA 05 82 4.2.2.31 "Query Low Battery Rate" Query low battery rate Byte Bits Parameter 0 0–7 Leader 1 0–7 Length 2 0–7 Command Code. 3-4 0 – 15 CRC Description Always a value of 0xAA.
3-4 0 - 15 Rate 5-6 0 – 15 CRC Rate in minutes, MSB first 4.2.2.32 “Turn On GPS” command This command will turn on the GPS engine and once a fix is obtained, the location will be available in memory for later querying. Use the “Query GPS Statistics” command to monitor the progress of the GPS engine. Once a fix is indicated, use the “Turn Off GPS” command to power down the GPS engine. Turn On GPS Byte Bits Parameter Description 0 0-7 Leader Always a value of 0xAA.
4.2.2.33 “Turn OFF GPS” command This command will turn off the GPS engine. Turn Off GPS Byte Bits Parameter Description 0 0-7 Leader Always a value of 0xAA. 1 0-7 Length 0x06 2 0-7 Command Code. 0xFD 3 0-7 Sub Command Code. 0x22 (Turn Off GPS) 4-5 0 – 15 CRC Command: AA 06 FD 22 F4 9A Response: AA 05 FD B3 E8 4.2.2.
Turn On GPS Pass-through Byte Bits Parameter Description 0 0-7 Leader Always a value of 0xAA. 1 0-7 Length 0x06 2 0-7 Command Code. 0xFD 3 0-7 Sub Command Code. 0x00 (Turn On GPS Pass-through) 4-5 0 – 15 CRC Command: AA 06 FD 00 E4 98 Response: AA 05 FD B3 E8 Example NMEA messages: $GNRMC,204738.00,A,3028.62674,N,09003.83218,W,0.132,,100420,,,A*73 $GNVTG,,T,,M,0.132,N,0.244,K,A*3F $GNGGA,204738.00,3028.62674,N,09003.83218,W,1,06,1.59,11.0,M,-27.
0 0-7 Leader Always a value of 0xAA. 1 0-7 Length 0x06 2 0-7 Command Code. 0xFD 3 0-7 Sub Command Code. 0x20 (Turn Off GPS Pass-through) 4-5 0 – 15 CRC Command: AA 06 FD 20 E6 B9 Response: AA 05 FD B3 E8 GLOBALSTAR PROPRIETARY AND CONFIDENTIAL INFORMATION Use or disclosure of data contained on this sheet is subject to the restrictions in the Distribution Statements on the title page of this document.
4.3 ST100 BOARD Serial Test Command 4.3.1 “Self Test” command This command is used to initiate an internal self test of the ST100 BOARD. When this command is received by the ST100 BOARD, there will be a 2 - 5 second delay before the response is returned (self test in progress). Self Test Command Byte Bits Parameter Description 0 0-7 Leader Always a value of 0xAA. 1 0-7 Length 0x06 2 0-7 Command Code. 0xFD 3 0-7 Sub Command Code.
4.4 Bootloading. Field update of device firmware 4.4.1 Nordic nRF52832 firmware update via bootloader (“Buttonless” DFU) The Nordic Bluetooth Low Energy application is written to support the Nordic Buttonless DFU (Device Firmware update) bootloader. The Nordic DFU app for Android or IOS can be used to update the firmware. It is essential that any custom firmware written by an OEM or VAR include the DFU library, provided with the Globalstar ST100 SDK, to support this functionality. 4.4.
into the application. However, if you issue 0x60 in the application, and then again in the bootloader, you have committed to load a new application, A response of length 6 will be returned with a condition code as follows: Jump to Bootloader Response Byte Bits Parameter Description 0 0-7 Leader Always a value of 0xAA. 1 0-7 Length 0x06 2 0-7 Command 0x60 0xFF = Bootloader is running and application area is blank or not completely loaded.
Flash One Line message Byte Bits Parameter Description 0 0-7 Leader 1 0-7 Length Always a value of 0xAA. Length contains the length of this Entire binary message, including CRC (as in all other message of this protocol).
• “0x61” message is sent, the user has committed to load the complete application before jumping out of the bootloader. The “end of file” marker in every Intel Hex file looks like this: “:00000001FF”. This marker encodes an address of 0, a byte count of 0, a “record type” of 0x01 (End of File), (and a checksum of 0xFF). When the end of the Intel Hex file is reached, this marker must be encoded by the user application into a “0x61” message via the format in the table above and sent to the device.
Flash One Line Message response Byte Bits Parameter Description 0 0-7 Leader Always a value of 0xAA. 1 0-7 Length 0x06 2 0-7 Command 0x61 Response codes with the MSB set are “NAKs” or “fails” and indicate that the bootloader didn’t do anything with the record. Codes without the MSB set are various success codes, indicating that the message was acted on as expected. 0x01 = OK but not done loading. (Returned for each line loaded until End of File is received.) 0x00 = OK and done.
4.4.2.3 0x62 “Enter Application” Enter Application Command Byte Bits Parameter Description 0 0-7 Leader Always a value of 0xAA. 1 0-7 Length 0x05 2 0-7 Command Code. 0x62 3-4 0 – 15 CRC Enter application response: GLOBALSTAR PROPRIETARY AND CONFIDENTIAL INFORMATION Use or disclosure of data contained on this sheet is subject to the restrictions in the Distribution Statements on the title page of this document.
Enter Application response Byte Bits Parameter Description 0 0-7 Leader Always a value of 0xAA. 1 0-7 Length 0x06 2 0-7 Command 0x62 0x00 = OK booting application 0xF0 = CRC/Signature failed. If this is received, the bootloader “believed” it had a valid application loaded but a re-check of the CRC/Signature failed. (This should be quite rare and indicates a significant glitch occurred during the loading process, or the device has bad flash memory.) 0xFF = Other error.
Bootloader/Application Status Query Byte Bits Parameter Description 0 0-7 Leader Always a value of 0xAA. 1 0-7 Length 0x05 2 0-7 Command Code. 0x63 3-4 0 – 15 CRC Byte Bits Parameter Description 0 0-7 Leader Always a value of 0xAA. 1 0-7 Length 0x06 2 0-7 Command 3 0-7 Response Code. 0x63 0x00 = Application running 0x05 = Bootloader running 4-5 0 – 15 CRC Enter Application response 4.4.3 JTAG programming adaptor.
The AXSEM proprietary programmer connects to the RJ-45 connector on this board for programming the AX50324 ASIC. 4.4.4 Nordic low-level load via JTAG Using the breakout board above, the Nordic can be programmed and debugged through a compatible JTAG programmer. Globalstar recommends Segger Studio as the development and debugging environment for this processor. The Nordic processor can also be programmed via Nordic’s NRF Go Studio application. 4.4.
unsigned short crc16_lsb(unsigned char *pData, int length) { unsigned char i; unsigned short data, crc; crc = 0xFFFF; if (length == 0) return 0; do { data = (unsigned int)0x00FF & *pData++; crc = crc ^ data; for (i = 8; i > 0; i--) { if (crc & 0x0001) crc = (crc >> 1) ^ 0x8408; else crc >>= 1; } }while (--length); crc = ~crc; return (crc); } USAGE: calculate the CRC for a message and update the message CRC unsigned short crc = crc16_lsb(msg, msg [1]-2); msg [msg [1]-2] = (unsigned char) (crc&0xFF); msg [ms
The following example is written in the Java programming language: char crc16_lsb(byte pData[], int length) { int pData_i = 0; char s1,s2; byte i; char data, crc; crc = (char) 0xFFFF; if (length == 0) return 0; do { data = (char)((char)0x00FF & pData[pData_i++]); crc = (char)(crc ^ data); for (i = 8; i > 0; i--) { if ((crc & 0x0001) != 0) crc = (char)((crc >> 1) ^ 0x8408); else crc >>= 1; } }while (--length != 0); crc = (char)~crc; return (crc); } USAGE: calculate the CRC for a message and update the messa
4.6 24-bit location format The 24-bit format used for latitude and longitude encodes 180 degrees of LATITUDE as a 24-bit (3-byte) signed integer and 360 degrees of LONGITUDE as a 24-bit (3-byte) signed integer. 4.6.1 CALCULATING LATITUDE Latitude may be calculated by converting the 3 encoded latitude bytes represented in hexadecimal to a decimal number and multiplying this decimal integer by the DEGREES_PER_COUNT_LAT conversion factor. DEGREES_PER_COUNT_LAT = 90.
This number converted to decimal (base 10) is: 12,579,947. 12,579,947 * (180.0 / 223) = 269.936378 Since this result is greater than 180 degrees, subtract 360 degrees from the result to create the correct signed representation. 269.936378 degrees – 360 degrees = -90.063622 degrees = 90.063622 degrees WEST 4.7 Flash Memory Map (TBD) 5 Test Modes 5.1 Hardwired Method The ST100 BOARD provides several test modes intended to aid in manufacturing testing and certification testing.
0 1 Test Packet - The test packet shall comply with the Air Interface Packet format with a user information equal to the hex stream 0x80AAF0F0F0AAF0F0F0 where the most significant bit is transmitted first 1 0 CW mode - An un-modulated carrier is continuously transmitted. 1 1 Normal Operation Table 6.1 The channels are selected via the Rx and RTS pins as follows RX RTS Channel 0 0 B 0 1 C 1 0 Reserved 1 1 Channel specified in the flash setup.
5.2.2 Step 2: Set the channel that you wish to perform the test on. Use the “setup” command for this. Using the configuration application in “advanced” mode: • • • 5.2.3 Tap the “auth” button. Send the command: “setup 3 60 120” Where “ = o 0 = Channel A o 1 = Channel B o 2 = Channel C o 3 = Channel D Step 3: Start the desired mode. Using the configuration application in “advanced” mode: Tap the “auth” button.
6 GENERAL WARNINGS Warning – Modifications: Changes or modifications to the ST100 not expressly approved by the party responsible for compliance could void the user's authority to operate the equipment. Warning – Blasting Area: To avoid interference with blasting operations, turn your ST100 off when in a “Blasting Area” or in areas posted “Turn off two-way radio.” Obey all signs and instructions.
7 ANTENNA TUNING GUIDANCE 7.1 GPS / Satellite Antenna Tuning If the VAR wants to tune the internal GPS / satellite antenna on the PCB for a specific enclosure / environment, the following should be used as guidance. 1. An appropriate vector network analyzer (VNA) should be used to measure return loss (S11) of the antenna. The VNA output should be 50 ohms, and the frequency range should go up to about 3MHz but can be higher if the VNA allows.
GLOBALSTAR PROPRIETARY AND CONFIDENTIAL INFORMATION Use or disclosure of data contained on this sheet is subject to the restrictions in the Distribution Statements on the title page of this document.
7. On the other board (ST100 antenna tuning board), install a 0 ohm, 0402 resistor as shown below, and install a 0 ohm, 0201 resistor onto L21. 8. For both PCBs, if a u.FL connector is not installed on J2 (bottom side of PCB), there will need to be an RF cable (i.e. semi-rigid RF coax pigtail) soldered to the board so that the VNA RF signal can be connected to the semirigid RF coax pigtail.
9. On the calibration PCB, connect a u.FL / SMA adapter to the J2 u.FL connector. If J2 is not installed, ensure the semi-rigid RF coax is soldered onto the PCB. GLOBALSTAR PROPRIETARY AND CONFIDENTIAL INFORMATION Use or disclosure of data contained on this sheet is subject to the restrictions in the Distribution Statements on the title page of this document.
GLOBALSTAR PROPRIETARY AND CONFIDENTIAL INFORMATION Use or disclosure of data contained on this sheet is subject to the restrictions in the Distribution Statements on the title page of this document.
10. Turn on the VNA, set the start frequency to 1GHz, end frequency to 3GHz, the measurement bandwidth as low as possible (10kHz should be ok), the measurement is set to S11, the system impedance = 50 ohms, the format for the S11 response is Smith Chart, and the RF power of the VNA is on. Add markers in the S11 response at 1615MHz and 1575.42MHz. 11. Ensure the calibration kit you are using for the VNA is selected in the VNA software (and all the settings for the calibration kit have been verified). 12.
16. Remove the u.FL / SMA adapter cable from the ST100 calibration board and connect it to the other ST100 board for antenna tuning (Note: the other ST100 board will require a semi-rigid RF coax if J2 is not installed). 17. Once the u.FL/SMA adapter is connected to the other ST100 PCB, record the impedances of the 1575.42MHz and 1615MHz markers. This is the initial antenna impedance without tuning. You can also take a photo to have as a reference for later. 18.
2. The matching components for the Bluetooth antenna are located in the area shown below. GLOBALSTAR PROPRIETARY AND CONFIDENTIAL INFORMATION Use or disclosure of data contained on this sheet is subject to the restrictions in the Distribution Statements on the title page of this document.
8 Globalstar Certification Process for Customer Products Before a customer’s end product can be used on the Globalstar network, it must receive a Globalstar Product Certification. The certification process ensures that the customer’s product meets Globalstar’s internal system standards and has received the applicable regulatory approvals for the countries it will be operating in. Typical certification process flow: • • • • • • • • Customer designs their product using the ST100 module.
this transmitter must be installed to provide a separation distance of at least 20 cm from all persons and must not be collocated or operating in conjunction with any other antenna or transmitter. The ST100 modular transmitter is only FCC authorized for the specific rule parts (i.e., FCC transmitter rules) listed on the grant, and that the host product manufacturer is responsible for compliance to any other FCC rules that apply to the host not covered by the modular transmitter grant of certification.
undesired operation. This Class B digital apparatus complies with Canadian ICES-003. Cet appareil numérique de classe B est conforme à la norme NMB003. Hereby, Globalstar declares that this ST100 BOARD is in compliance with the essential requirements and other relevant provisions of Directive 2014/53/EU. The declaration of conformity may be consulted at www.globalstar.com/regulatory NOTICE: This equipment complies with FCC, IC and CE RF Exposure Limits.
Portuguese English Produto não acabado, de uso interno, cuja integração em outros equipamentos pode requerer nova certificação. Unfinished product, for internal use, the integration of which into other equipment may require further certification. GLOBALSTAR PROPRIETARY AND CONFIDENTIAL INFORMATION Use or disclosure of data contained on this sheet is subject to the restrictions in the Distribution Statements on the title page of this document.
GLOBALSTAR PROPRIETARY AND CONFIDENTIAL INFORMATION Use or disclosure of data contained on this sheet is subject to the restrictions in the Distribution Statements on the title page of this document.
GLOBALSTAR PROPRIETARY AND CONFIDENTIAL INFORMATION Use or disclosure of data contained on this sheet is subject to the restrictions in the Distribution Statements on the title page of this document.
GLOBALSTAR PROPRIETARY AND CONFIDENTIAL INFORMATION Use or disclosure of data contained on this sheet is subject to the restrictions in the Distribution Statements on the title page of this document.
