Page 1 of 24 GPS Containment: RF Sniffer/Status Unit PC Interface Manual v3 Initial File Date: 04/03/2012 Author: Scott McFarland Revision File Date: 09/10/2012 Related Documents: [1] US Patent - Maddox 6,903,682 B1 [2] GPSC System Manual v4 [3] GPSC Mobile Unit PC Interface Manual v4 [4] GPSC Base Unit PC Interface Manual v41 [4] 37287.00 DRAFT Revised Application (clean) (00259633).PDF "Actionable Position and Speed" Revision History: 04/03/2012 Version v1 Initial release.
Page 2 of 24 Contents 1.0 Connection Diagram 2.0 Personal Computer Requirements 2.1 Hardware 2.2 Software 2.3 Port Settings 3.0 Input and Output Formats 3.1 Input Format 3.2 Output Format 4.0 Available Commands 4.1 Commands For All Likely Users 4.2 Commands Specific to Factory Test, Engineering, and/or Emissions Compliance 5.0 Decoding Output Headers and Messages 5.1 (Trace) Headers 5.2 [Task] Headers 6.0 Hex Bit Maps 6.1 Event Types (HEX): 7.0 RF Transmissions 7.1 Block Types Radio Systems Corp.
Page 3 of 24 1.0 Connection Diagram PC App RF Antenna PC’s USB Port USB Std A RF Sniffer/Status Radio Systems Corp.
Page 4 of 24 2.0 Personal Computer Requirements 2.1 Hardware A "GPSC RF Sniffer/Status" assembly. A personal computer equipped with at least one USB port. Connect per figure in section 1.0. 2.2 Software Terminal Emulation Software: i.e. TeraTerm TeraTerm (ttermp23.zip) is available at http://hp.vector.co.jp/authors/VA002416/teraterm.html. Device Drivers: FTDI USB drivers for the FT232RQ at http://www.ftdichip.com. RSC GPSC PC application software. 2.3 Port Settings Baud Rate: 38400.
Page 5 of 24 3.0 Input and Output Formats A Sniffer/Status Command Prompt will appear on the terminal emulator screen as, “SNIFF> “. Prior to entering or transferring command text, depress the key to force a Sniffer command prompt. If a command prompt does not appear, check all connections and PC port settings. 3.1 Input Format A Command is entered or transferred as text in CAPITAL LETTERS. The characters entered are echoed and appended to the end of the command prompt.
Page 6 of 24 4.0 Available Commands Commands are initiated by typing or transferring one of the following in ALL CAPITAL LETTERS and the key. Prior to entering or transferring command text, depress the key to clear any orphaned characters from the serial port buffers and force a command prompt. Commands for all likely users "VERSION" Display firmware version. "PRINTNV" Display parameter settings. "DEFAULTNV" Set parameters to their default settings.
Page 7 of 24 Description: Display parameter settings. Numeric Input Range: N/A Example (Set): SNIFF> DEFAULTNV [S],DEFAULTNV [SNV],RESTORE-DEFAULTS SNIFF> Suggested Numbering Convention: It is REQUIRED to have a unique DEVID for each Base, Sniffer/Status, and Mobile unit within 2000 ft. of the installation. BASE ID’s should set for 10, 20, 30, 40, etc.
Page 8 of 24 Example (Set): SNIFF> BASEREFID20 [SNV],UPDATE [S],BASEREFID,20 SNIFF> CLEARMOBILESTATUS Description: Clear ALL mobile status accumulated in RAM data structure. Numeric Input Range: N/A Example (Inquiry): BASE> CLEARMOBILESTATUS [S],CLEARMOBILESTATUS BASE> BOOT Description: Cause the unit to enter USB Boot mode. Numeric Input Range: N/A Example (Inquiry): SNIFF> BOOT 4.
Page 9 of 24 SNIFF> RXTESTEND [S], RXTESTEND SNIFF> TXTESTx Description: Places RF transceiver into one of several transmit test modes. Numeric Input Range: NONE, 1, 4, 5 Examples (Execute): SNIFF> SNIFF> SNIFF> SNIFF> TXTEST TXTEST1 TXTEST4 TXTEST5 full data blocks are transmitted every 2 secs (periodic). produces a continuous carrier only signal. continuous 1010 modulated data signal. continuous PN9 modulated data signal (random data).
Page 10 of 24 DESTxxxxxcommandtext Description: Forward a text command over the RF channel to a specific unit. Since the RF transceiver in a Mobile Unit is predominantly off, commands for a Mobile Unit must be queued and await transmission until the destination Mobile is ready to receive. Numeric Input Range: Mobile ID (5 digits with leading 0’s) followed by Mobile command text and any numeric input.
Page 11 of 24 5.0 Decoding Output Headers and Messages Most status and diagnostic messages are turned “ON” and “OFF” by the TRACExx…x command. Trace activated messages are suitable for parsing by a computer program as part of a GUI. Each (trace) activated display line will begin with one of the (trace) HEADERs detailed below. A (trace)will automatically shut-off once the (trace) timer decrements to zero. When a (trace) is executed, the timer is set for 300 seconds.
Page 12 of 24 5.1 (Trace) Headers A (trace) diagnostic message is turned “ON” or “OFF” by the TRACExx…x command. The xx…x (HEX) numeric input value represents a 32 bit map. A message is activated by turning on the corresponding bit in the bit map and is deactivated by turning the bit off. A (trace) header is bracketed by “()”. To end any and all TRACE(s), type TRACE0. All (traces) will end if the (trace) timer decrements to zero. Below is a list of available (trace) activated messages.
Page 13 of 24 (S7),0x00410126 (S7),0x0039FE7A (S7),0xDF2B2E8C (S7),0x6000A297 (S7),0x00005EAE (S7),0x19209168 (S7),0x40064071 (S7),0x00C84D1A . . where, line (parse header) = S7 field 1: 32 bit Receive Data Word (HEX) Note, TRACE1000 will only display blocks with bit errors.
Page 14 of 24 (S9),0x0000 (S9),0x1632 (S9),0x6120 (S9),0x005A (S9),0x005B . . where, line (parse header) = S9 field 1: 16 bit Receive Data Word (HEX) Note, TRACE2000 will only display blocks with errors. (S16) – Mobile Status, a continuous response activated by TRACE4000. Information presented here is collected from received MOBILE GPS and CONTAINMENT STATUS blocks. The information collected is maintained in RAM memory. Information is collected for up to 8 Mobile's.
Page 15 of 24 where, line (parse header) = S18 field 1: RF Noise Floor (dBm) (S22) – Header for RF Received RF Blocks in Readable Format, a continuous response activated by TRACE200000. This header is the generic output for all other RF Blocks that are not otherwise printed in readable format for by S23, S24, S25, S26, S27, S28, or S32.
Page 16 of 24 field 9: Hdop Position Error (0.01 meters) field 10: Time to Acquire Post (seconds) field 11: Post Weight field 12: Post Latitude (decimal degrees) field 13: Post Longitude (decimal degrees) (S25) – Readable Text for a Mobile GPS Block, a continuous response activated by TRACE200000 (S25),32,30,0,6,0,-71,1,1,3,35.914275,84.134731,45,45,0,9,9,0x0C010B1A,35.914280,-84.134730,-116,-86,3924,0.265,0 . .
Page 17 of 24 field 10: Base Reference Longitude (decimal degrees) field 11: Base Reference Altitude (meters) field 12: Base used GPS PRN bit map field 13: Base Most Recent Fix Latitude (decimal degrees) field 14: Base Most Recent Fix Longitude (decimal degrees) field 15: Base Most Recent Fix Altitude (meters) field 16: Base Hdop Position Error field 17: Base Firmware Version Alias field 18: System Transmit Power Setting: 0 = +13dBm, 1 = +5dBm, 2 = -3dBm, 3 = -11dBm (S27) – Readable Text for a Pseudo Range
Page 18 of 24 field 12: Mobile GNSS Longitude (decimal degrees) field 13: Mobile Seconds without Motion field 14: Mobile is within the Containment Area, 1 is yes, 0 is no field 15: Mobile is Armed for Corrections, 1 is yes, 0 is no field 16: Mobile Distance to Nearest Boundary Segment (ft.) field 17: Mobile Actionable Speed (ft.
Page 19 of 24 (S31),Tx (S31),RdyRx,,,,. .
Page 20 of 24 5.2 [Task] Headers A [task header] is bracketed by “[]” and identifies the line as an informative task output message. All fields following the header are comma delimited. Specific task headers are: [T] Periodic Task Header [P] Protocol Task Header [PSwi] Protocol Software Interrupt Header [R] RF Comm Task Header [S] Shell Task Header [Event] Diagnostic Event Activity Header [SNV] Sniffer Non-Volatile File Activity Header 5.2.3 [S] task header.
Page 21 of 24 [S],Command-Accepted,32 line 1: [task header] = S field 1: Command-in-Queue informative text indicating the command is in queue and awaiting transmission line 2: [task header] = S field 1: TONE informative text displaying the command is being forwarded to a device field 2: DEVID of the Unit to receive the command (Note: this action mimics a typed command, therefore the Base prompt is also displayed.
Page 22 of 24 field 1: DEVID, informative text and secondary parse string [SNV],BASEREFID,30 where, line (parse header) = SNV field 1: BASEREFID, informative text and secondary parse string field 2: BASEREFID, the destination ID that this unit will use to report status information 5.2.5 [Event] task header. Additional informative text and output fields that accompany the [Event] task header. The [Event] task header precedes an event diagnostic message. This message type may appear at any time.
Page 23 of 24 6.0 HEX Bit Maps 6.1 Event Types (HEX) These flag bits refer to events (recoverable and un-recoverable) as they MAY occur.
Page 24 of 24 7.0 RF Transmissions 7.1 Block Types Recall, that TRACE200000 activates display messages for "RF Received Block in Readable Format". Each received block contains a field that identifies its type. (S22),30,32,6,8,0,-71 where, line (parse header) = S22 field 4: Block Type Block types currently used in the GPS Containment System are: TYPE 1: MOBILE GPS – This block type is sent periodically from a Mobile to its assigned Base and Hub/Sniffer Unit.
FCC - USA This device complies with part 15 of the FCC 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. CAUTION: Modification or changes to this equipment not expressly approved by Radio Systems® Corporation may void the user’s authority to operate the equipment.
