1. Manuals
  2. Brands
  3. VIAVI Solutions Manuals
  4. Security System
  5. PNT 62 Series
  6. User manual

VIAVI Solutions PNT 62 Series User Manual

Assured position, navigation, and timing reference
Hide thumbs
Table of Contents

Advertisement

Quick Links

Download this manual
PNT-62xx Series
Assured Position, Navigation, and Timing
Reference
Users Guide
R002

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the PNT 62 Series and is the answer not in the manual?

Questions and answers

Summary of Contents for VIAVI Solutions PNT 62 Series

  • Page 1 PNT-62xx Series Assured Position, Navigation, and Timing Reference Users Guide R002...
  • Page 3 © Copyright 2023 VIAVI Solutions Inc. All rights reserved. VIAVI and the VIAVI logo are trademarks of VIAVI Solutions Inc. (“VIAVI”). All other trademarks and registered trademarks are the property of their respective owners. No part of this guide may be reproduced or transmitted, electronically or otherwise, without written permission of the publisher.
  • Page 4 PNT-62xx Assured Position, Navigation, and Timing Reference User Guide Page ii 22171774, R002 March 2024...

  • Page 5: Table Of Contents

    About this User Guide This prefix explains how to use this User Guide and includes the following topics: • “Purpose and scope” on page iv • “Assumptions” on page iv • “Related Information” on page iv • “Conventions” on page iv •...

  • Page 6: Purpose And Scope

    About this User Guide Purpose and scope Purpose and scope This manual is intended to help you use the capabilities of the PNT-62xx Assured Position, Navigation, and Timing Reference. This manual includes task-based instructions that describe how to configure, use, and troubleshoot the test capabilities available on your instrument assuming it is configured and optioned to support the capabilities.
  • Page 7 About this User Guide Conventions Table 1 Text formatting and other typographical conventions (Continued) Item(s) Example(s) Text you must type exactly as – Restart the applications on the server using shown into a command line the following command: interface, text file, or a GUI text $BASEDIR/startup/npiu_init field.

  • Page 8: Safety And Compliance Information

    About this User Guide Safety and compliance information Table 3 Safety definitions Term Definition DANGER Indicates a potentially hazardous situation that, if not avoided, will result in death or serious injury. It may be associated with either a general hazard, high voltage, or other symbol. See Table 2 more information.

  • Page 9: Federal Communications Commission (Fcc)

    About this User Guide Safety and compliance information Federal Communications Commission (FCC) The equipment was tested and found to comply with the limits for a Class A digital device, pursuant to Part 15 of the FCC Rules. These limits are designed to provide reasonable protection against harmful interference when the equipment is operated in a commercial environment.

  • Page 10: Technical Assistance

    About this User Guide Technical assistance Additional standards compliance The equipment meets the following standards and requirements: • Installation Category (Over Voltage Category) II under IEC 60664-1 • Pollution Degree 2 Category under IEC 62368-1 Safety Requirements for Electrical Equipment for Measurement, Control, and Laboratory Use Technical assistance If you require technical assistance, call 1-844-GO-VIAVI.
  • Page 11 Table of Contents About this User Guide Purpose and scope ............iv Assumptions .

  • Page 12: Table Of Contents

    Table of Contents Chapter 3 GPSCon Utility Description ............. . . 12 Installation .
  • Page 13 Table of Contents SYNChronization:SOURce:STATe:VALue? ....... . 33 SYNChronization:SOURce:PRIority? ........33 SYNChronization:SOURce:PRIority <STL|GPS|EXTernal>...
  • Page 14 Table of Contents DIAGnostic:LIFetime:SECond? ......... . 46 GPS Subsystem .
  • Page 15 Table of Contents GPS:STL:BPMReceived? ..........62 GPS:STL:BPMProcessed? .
  • Page 16 Table of Contents MEASure:APOWersupply? ..........79 MEASure:BPOWersupply? .
  • Page 17 Table of Contents SYSTem:ID? ............91 SYSTem:ID:SN? .
  • Page 18 Table of Contents PNT-62xx Assured Position, Navigation, and Timing Reference User Guide Page xvi 22171774, R002 March 2024...
  • Page 19 Introduction Chapter 1 This chapter discusses the following topics: • “About the PNT-62xx” on page 2 • “Applications” on page 2 • “Equipment included with the PNT-62xx Series” on page 3 PNT-62xx Assured Position, Navigation, and Timing Reference User Guide March 2024 22171774, R002 Page 1...

  • Page 20: Chapter 1 Introduction

    Chapter 1 Introduction About the PNT-62xx About the PNT-62xx The PNT-62xx Series combines concurrent L1, L2, L3, and L5 GNSS reception with a secure STL (LEO-based) timing receiver, terrestrial receivers, and full IEEE-1588 Edge-Grandmaster (EGM) and IEEE-1588-slave capability. Figure 1 shows the PNT-62xx.

  • Page 21: Variants

    Chapter 1 Introduction Equipment included with the PNT-62xx Series Variants Table 1 describes the PNT-62xx Series variants. Table 1 PNT-62xx Series variants Model # Part # Product Description PNT-6230S 22172402 DOCXO, STL, MOS GNSS, Transcoder, RoHS PNT-6250 22172901 DOCXO, GNSS-T, Transcoder, RoHS PNT-6250S 22172902 DOCXO, STL, GNSS-T, Transcoder, RoHS...

  • Page 22: Powering The Unit

    Chapter 1 Introduction Powering the unit Powering the unit Power is supplied to the instrument by the 12V power supply. Use of power adapters other than those supplied with your PNT-62xx is not recommended. Figure 2 shows the power supply label. Figure 2 12V power supply PNT-62xx Series connections and indicators...
  • Page 23 Chapter 1 Introduction PNT-62xx Series connections and indicators Table 2 Connections Connector Description 10 MHz SMA frequency output (x2) RF OUT SMA provides transcoder output, i.e. simulated GPS derived from STL input RS-232 9-pin DSUB console interface Mini USB console interface RJ-45 Ethernet console interface (for future use) A/12VDC...
  • Page 24 Chapter 1 Introduction PNT-62xx Series connections and indicators PNT-62xx Assured Position, Navigation, and Timing Reference User Guide Page 6 22171774, R002 March 2024...

  • Page 25: Chapter 2 Installation

    Installation Chapter 2 The following topics are discussed in this chapter: • “Overview” on page 8 • “Pre-installation” on page 8 • “Installation” on page 8 PNT-62xx Assured Position, Navigation, and Timing Reference User Guide March 2024 22171774, R002 Page 7...

  • Page 26: Pre-Installation

    Chapter 2 Installation Overview Overview The following sections describe how to install the PNT-62xx. Pre-installation Perform the following steps before installing the receiver. Determine STL antenna location. NOTE For indoor installations, locate the antenna near, or as close as possible, or within sight of a window, skylight, or outside wall.

  • Page 27: Connecting The Receiver

    Chapter 2 Installation Installation Figure 3 Handle placement Attach the brackets using the included 6-32 X 5/16 and 4-40 X 5/16 screws, as shown in Figure Figure 4 Bracket screw locations Mount the receiver in the desired location. Connecting the receiver Connect the antenna cable to the STL receiver STL/SAT connector using the 47 meter SMA cable.
  • Page 28 Chapter 2 Installation Installation Verify STL signal reception. The 1 PPS OK LED blinks every second while the STL signal is locked. After about 10 to 20 minutes, the SYNC LED and transcoder output turn on. Use the GPSCon utility to verify good burst reception (BPMP AVG of at least 10.) NOTE For some deep indoor locations, the receiver may take an hour or more to...

  • Page 29: Gpscon Utility

    GPSCon Utility Chapter 3 The following topics are discussed in this chapter: • “Description” on page 12 • “Installation” on page 12 • “Using GSPCon” on page 12 • “Interpreting the Data” on page 18 PNT-62xx Assured Position, Navigation, and Timing Reference User Guide March 2024 22171774, R002 Page 11...

  • Page 30: Installation

    Chapter 3 GPSCon Utility Description Description GPSCon – VIAVI Edition is a free program for the monitoring and control of VIAVI GPSDO, Simulator, and Receiver products. It communicates with the receiver using the SCPI command set. This free version of the GPSCon utility is only compatible with VIAVI products, and is available for download from the support section of the Jackson Labs website: http://www.jackson-labs.com/index.php/support...
  • Page 31 Chapter 3 GPSCon Utility Using GSPCon Figure 5 Options window Communication parameters Before you can use GPSCon, you must set the communication parameters for your system. Open the dialog box by pressing the wrench icon , then select the Coms tab.
  • Page 32 Chapter 3 GPSCon Utility Using GSPCon Auxiliary parameters After pressing the wrench icon , you can select the Auxiliary tab to configure auxiliary measurements. Figure 7 shows an example of an auxiliary measurement. Figure 7 Auxiliary parameters tab In the above example, the Aux1 request string has been set to GPS:STL:BPMP?<CR> and the Aux2 request string has been set to GPS:STL:BPMR?<CR>.

  • Page 33: Sending Manual Commands To The Receiver

    Chapter 3 GPSCon Utility Using GSPCon The labels and parameters are completed by default for traces 1 through 5. Any of the eight traces can be replaced by auxiliary traces as described in “Auxiliary parameters” on page 14. Press the Help button for a full description of each option in the Traces tab. Sending manual commands to the receiver You can send SCPI commands manually by using the drop-down box in the upper left of the main window, as shown in...
  • Page 34 Chapter 3 GPSCon Utility Using GSPCon Figure 10 Graph display You can set the horizontal range of the graph using the mouse. Perform the following steps to set the horizontal range. Set the start time by clicking on the point that marks the left side of the curve to be magnified.

  • Page 35: Exporting Graphics

    Chapter 3 GPSCon Utility Using GSPCon Figure 11 Expanded graph display When you have locked the start and stop time using the mouse, you can scroll left or right through the data: • To scroll to a later time, use Shift + Left click •...

  • Page 36: Interpreting The Data

    Chapter 3 GPSCon Utility Interpreting the Data • To manually export in accordance with the settings, press the 'Export' button. Interpreting the Data Figure shows an example of data acquired by a GPSDO unit over a period of time of more than 200 hours.
  • Page 37 Chapter 3 GPSCon Utility Interpreting the Data Figure 13 Zoomed captured data example The image shows a phase offset error of the internal OCXO to the UTC GPS reference. The maximum drift is -77 ns to +93 ns. The average is (TI = -0.03 ns).
  • Page 38 Chapter 3 GPSCon Utility Interpreting the Data PNT-62xx Assured Position, Navigation, and Timing Reference User Guide Page 20 22171774, R002 March 2024...

  • Page 39: Scpi Commands

    SCPI Commands Chapter 4 The following topics are discussed in this chapter: • “Introduction” on page 22 • “General SCPI commands” on page 22 • “SERVO Subsystem” on page 23 • “SYNChronization Subsystem” on page 31 • “CSAC Subsystem” on page 40 •...

  • Page 40: Introduction

    Introduction Introduction The Standard Commands for Programmable Instrumentation (SCPI) subsystem is accessed using a mini-USB or RS-232 serial cable and a terminal program. By default, the terminal settings are 115200, 8N1, no flow-control. A number of commands that can be used are listed below. To get a listing of the available commands, send the HELP? query.

  • Page 41: Help

    SERVO Subsystem For example: VIAVI, PNT-6220, Firmware Rev 0.71 HELP? Returns a list of available commands. SERVO Subsystem This subsystem regroups all the commands related to the adjustment of the servo loop: • SERVo? • SERVo:MODE <SLOW|MEDium|FAST|AUTO> • SERVo:MODE:FASTDURation <int> [60, 604800] •...
  • Page 42 SERVO Subsystem • SERVo:MODE? • SERVo:STATe? • SERVo:MODE:FASTDURation? • SERVo:MODE:MEDDURation? • SERVo:DACGain? • SERVo:EFCScale? • SERVo:EFCScale:MEDium? • SERVo:EFCScale:FAST • SERVo:PHASECOrrection? • SERVo:PHASECOrrection:MEDium? • SERVo:PHASECOrrection:FAST? • SERVo:EFCDamping? • SERVo:SLOPe? • SERVo:COARSedac? • SERVo:TEMPCOmpensation? • SERVo:AGINGcompensation? • SERVo:1PPSoffset? • SERVo:TRACe? • SERVo:FASTlock? •...

  • Page 43: Servo:falength [100,20000]

    SERVO Subsystem multiply the EFCscale by 2x, and an effective EFCscale value of 1.4 is applied to the PLL loop. This increased gain value difference will be reduced every second by 1/3600, so that the gain after two seconds would be: 1.3998, until after 3600 seconds the gain has been reduced back to its long term value of 0.70 as stored in the SERVo:EFCscale parameter.

  • Page 44: Servo:mode

    SERVO Subsystem SERVo:COARSedac? SERVo:MODE <SLOW|MEDium|FAST|AUTO> This command is useful in setting the filter loop time constants for different mission profiles to accommodate different usage scenarios of the CSAC GPSDO. The loop time constant of the CSAC can be chosen with these settings. The AUTO mode lets the firmware determine by itself which loop time constant is used, thus optimizing the units’...

  • Page 45: Servo:dacgain [0.001, 10000]

    SERVO Subsystem SERVo:DACGain <float> [0.001, 10000] This command is used for factory setup ONLY. This command will query the state of this command: SERVo:DACGain? SERVo:EFCScale <float> [0.0,500.0] Controls the Proportional part of the PID loop. Typical values are 0.7 (double oven OCXO) to 6.0 (simple single oven OCXO).

  • Page 46: Servo:efcdamping:medium [2,4000]

    SERVO Subsystem SERVo:EFCDamping:MEDium <int> [2,4000] This command controls the SERVo:EFCDamping setting when the servo state as reported by the SERVo:STATe? query is MEDIUM. The servo state and this setting only apply for the STL synchronization source. SERVo:EFCDamping:FAST <int> [2,4000] This command controls the SERVo:EFCDamping setting when the servo state as reported by the SERVo:STATe? query is FAST.

  • Page 47: Servo:phasecorrection [-500.0,500.0]

    SERVO Subsystem This command will query the state of this command: SERVo:AGINGcompensation? SERVo:PHASECOrrection <float> [-500.0,500.0] This parameter sets the Integral part of the PID loop. Loop instability will result if the parameter is set too high. Typical values are 10.0 to 30.0. This command has the following format: SERVo:PHASECOrrection <float>...

  • Page 48: Servo:slope

    SERVO Subsystem SERVo:SLOPe <NEG|POS> The parameter determines the sign of the slope between the EFC and the frequency variation of the OCXO. This parameter should be set to match the OCXO’s EFC frequency slope and should not be changed from the factory setting. This command has the following format: SERVo:SLOPe <NEG|POS>...

  • Page 49: Synchronization Subsystem

    SYNChronization Subsystem SERVo:TRACe? An example output is described here: 08-07-31 373815 60685 -32.08 -2.22E-11 14 10 6 0x54 [date][1PPS Count][Fine DAC][UTC offset ns][Frequency Error Estimate][Sats Visible][Sats Tracked][Lock State][Health Status] “SYNChronization:HEAlth?” on page 38 for detailed information on how to decode the health status indicator values.

  • Page 50: Synchronization

    SYNChronization Subsystem • SYNChronization:HOLDover:DURation? • SYNChronization:HOLDover:STATe? • SYNChronization:HOLDover:INITiate • SYNChronization:HOLDover:RECovery:INITiate • SYNChronization:HOLDover:TUNCertainty:PREDicted? • SYNChronization:TINTerval? • SYNChronization:TINTerval:THReshold <int> [50, 2000] • SYNChronization:TINTerval:RAW? • SYNChronization:IMMEdiate? • SYNChronization:FEEstimate? • SYNChronization:LOCKed? • SYNChronization:OUTput:1PPS:RESET <ON | OFF> • SYNChronization:OUTput:WIDTH <int> <ms|us> [100us,500ms] • SYNChronization:OUTput:HOLDover <int> [0, 604800] •...

  • Page 51: Synchronization:source:mode:edge

    SYNChronization Subsystem This command selects between the EXTernal, GPS, STL, and PRIority sync modes as the1PPS source. The GPS modes use the GNSS 1PPS input for disciplining the oscillator and synchronizing precise timing, the GPS mode also gates the 1PPS based on the GNSS status of the external receiver as indicated in the NMEA serial sentences from the GNSS receiver.

  • Page 52: Synchronization:source:priority

    SYNChronization Subsystem SYNChronization:SOURce:PRIority? This command returns the current priorty list setting stored in NV memory. SYNChronization:SOURce:PRIority <STL|GPS|EXTernal> This command will set or query the current priority order used with the SYNC:SOURCE:MODE PRI setting. This command has the following format: SYNChronization:SOURce:PRIority <STL|GPS|EXTernal> where multiple sources are listed separate by spaces.

  • Page 53: Synchronization:source:switchdelay:gps [0,64800]

    SYNChronization Subsystem SYNChronization:SOURce:SWITCHDELay:GPS <int> [0,64800] This command configures a delay before switching from GPS to another synchronization source. The default setting of 0 results in no delay before switching sources from GPS. SYNChronization:SOURce:SWITCHDELay:STL <int> [0,64800] This command configures a delay before switching from STL to another synchronization source.

  • Page 54: Synchronization:holdover:recovery:initiate

    SYNChronization Subsystem When the unit is placed into forced-holdover with this command, the unit will indicate the time interval difference between the 1PPS output and the GNSS or STL 1PPS by using the SYNC:TINT? command. This allows the user to see the OCXO drift when not locked to GNSS signals for testing purposes, or to prevent the GNSS receiver from being spoofed and affecting the OCXO frequency accuracy.

  • Page 55: Sybchronization:tinterval:raw

    SYNChronization Subsystem before the loop algorithms can pull the phase error toward 0ns. The following command queries the state of SYNChronization:TINTerval:THReshold: SYNChronization:TINTerval:THReshold? SYBChronization:TINTerval:RAW? This command queries the raw unfiltered time interval measurement or difference between the 1PPS output and the reference 1PPS signal. SYNChronization:IMMEdiate This command initiates a near-instantaneous alignment of the GNSS/STL/EXT 1PPS and Receiver output 1 PPS.

  • Page 56: Synchronization:output:1Pps:width [100Us, 500Ms]

    SYNChronization Subsystem SYNChronization:OUTput:1PPS:RESET <ON|OFF> This command will query the state of this command: SYNChronization:OUTput:1PPS:RESET? SYNChronization:OUTput:1PPS:WIDTH <int> <ms | us> [100us, 500ms] This command allows configuration of the 1PPS active high pulse width. The default pulse width on the standard PNT-62xx is 200 milliseconds and the pulse can be configured from 100 microseconds to 500 milliseconds.
  • Page 57 SYNChronization Subsystem If the OCXO coarse-DAC is mined-out at 0 HEALTH STATUS |= 0x2; If the phase offset to UTC is >250ns HEALTH STATUS |= 0x4; If the run-time is < 300 seconds HEALTH STATUS |= 0x8; If the GNSS receiver is in holdover > 60s HEALTH STATUS |= 0x10;...

  • Page 58: Synchronization:health:alarmdelay:holdover [0,604800]

    CSAC Subsystem SYNChronization:HEAlth:ALARMDelay:HOLDover <int> [0,604800] Configures a delay in seconds before indicating a health alarm to avoid unnecessary alarms from short holdover periods. A setting of 0 disables the delay and the maximum setting is 604,800 seconds or one week. This command has the following format: SYNChronization:HEAlth:ALARMDelay:HOLDover <int>...

  • Page 59: Csac:type

    CSAC Subsystem CSAC:TYPE? This query returns the type/model of the connected atomic oscillator. CSAC:LOCKed? This query returns the lock status of the atomic oscillator. A value of 1 is returned if the CSAC or Rubidium is in atomic lock. CSAC:RS232? This query returns the state (OK or FAIL) of the serial communication between the main CPU and the oscillator of the attached unit’s internal microcontroller.

  • Page 60: Csac:mode

    CSAC Subsystem Table 5 CSAC Status definitions Status Definition Laser Power Acquisition Laser Current Acquisition Microwave Power Acquisition Heater Equalibration Initial Warm-up Asleep (ULP mode only) CSAC:MODE? This query returns the mode value of CSAC or Rubidium clock. If the Microsemi Rubidium is attached to the PNT-62xx, this query will return one of two values: •...

  • Page 61: Csac:signal

    CSAC Subsystem CSAC:SIGnal? If the Microsemi Rubidium is attached to the PNT-62xx, this query will return an indication of the Microsemi Rubidium Vapor Cell DC interrogation signal level in mV. If the CSAC is attached, this query will simply return the indication of signal level. CSAC:HEATpackage? If the Microsemi Rubidium is attached to the PNT-62xx, it will return the Physics package heater power in mW.

  • Page 62: Csac:teccontrol

    CSAC Subsystem CSAC:TECcontrol? This query is compatible with the Microsemi Rubidium. It will return the TEC Control value in °C. CSAC:ALarm? Returns the Alarm value of CSAC oscillator, as shown in Table Table 7 Alarm values Alarm Definition 0x0001 Signal Contrast Low 0x0002 Synthesizer Tuning at Limit 0x0010...

  • Page 63: Csac:steer:latch Once

    DIAGnostic Subsystem CSAC:STeer:LATch ONCE This command stores the momentary steering offset into the respective unit’s internal NVRAM. This is done automatically by the firmware once every 24 hours, so as not to damage the NVRAM which has a limited number of write cycles. The user may force this value to be stored by issuing the CSAC:STeer:LATch ONCE command.

  • Page 64: Diagnostic:roscillator:efcontrol:relative [-100.0, 100.0]

    DIAGnostic Subsystem • DIAGnostic:ROSCillator:EFControl:RELative? : Relative oscillator setting • DIAGnostic:ROSCillator:EFControl:ABSolute? : Absolute oscillator setting • DIAGnostic:LIFetime:COUNt? : Time since power-on in hours (lifetime) An example of the syntax: scpi > diag? EFControl Relative: 0.025000% EFControl Absolute: 5 Lifetime : +871 DIAGnostic:ROSCillator:EFControl:RELative <float>...

  • Page 65: Gps Subsystem

    GPS Subsystem GPS Subsystem NOTE The PNT-62xx displays antenna height in MSL Meters rather than in GPS Meters on all commands that return antenna height (unless otherwise specified). The NMEA position fixes are in the WGS84 coordinate system, while the X, Y, and Z positions and velocity vectors are given in the ECEF coordinate system.
  • Page 66 GPS Subsystem • GPS:STL:RESET • GPS:STL:RESET:AUTO • GPS:STL:ISP • GPS:STL:SCPI • GPS:STL:SUBScription? • GPS:STL:SUBScription:AUTHKEY • GPS:STL:AGC • GPS:STL:CNO? • GPS:STL:CNO:MINTHReshold • GPS:STL:CNO:MAXimum? • GPS:STL:DOPpler:MINimum • GPS:STL:DOPpler:MAXimum • GPS:STL:PPSFilter:PFOM • GPS:STL:PPSFilter:TFOM • GPS:STL:CLOCKmodel • GPS:STL:CLOCKmodel:MEDium • GPS:STL:CLOCKmodel:FAST • GPS:STL:EXTCLOCK • GPS:STL:SERVo:LOOP •...

  • Page 67: Gps:type

    GPS Subsystem • GPS:PASHR • GPS:GPGSA • GPS:GPGSV • GPS:SATellite:TRAcking:COUNT? • GPS:SATellite:VISible:COUNT? • GPS:POSition? • GPS:POSition:ECEF? • GPS:HEIGHT? • GPS:HEIGHT:MSL? • GPS:HEIGHT:GPS? • GPS:STATus? • GPS:STATus:STRing? • GPS:STATus:ETA? • GPS:JAMInfo? • GPS:SN? • GPS:JAMlevel? • GPS:FWver? • GPS:INITial:DATE • GPS:INITial:TIME •...

  • Page 68: Gps:system:select [Gps | Sbas | Qzss | Gal | Bd ^ Glo]

    GPS Subsystem The query command GPS? will display the current receiver mode and status for the current receiver mode. Some NMEA outputs and SCPI query commands will also reflect on the current receiver mode selected. This command has the following format: GPS:TYPE:MODE <AUTO|UBLOX|SEPTentrio|STL>...

  • Page 69: Gps:system:lband

    GPS Subsystem The following example command will enable signals from L1 and L5 bands for PVT solution: GPS:SYST:LBAND L1 L5 The following command will query the currently enabled L band signals for PVT solution: GPS:SYST:LBAND? GPS:SYSTem:LBAND? This query returns the value of GPS:SYSTEM:LBAND. GPS:SYSTem:LBAND:MODE This command configures the L-band tracking mode.

  • Page 70: Gps:system:lband:svid

    GPS Subsystem GPS:SYSTem:LBAND:SVID? This command returns a list of Space Vehicle Identifiers (SVIDs) for each L-band tracker. GPS:SYSTem:LBAND:AGCPnorm? This command queries the ETA system and returns the Euclidean norm of the AGC gain for all L-band trackers. GPS:SYSTem:BANDTRACk [L1 | L2 | L3 | L5 | ALL] This command configures the L band signals to be tracked by the SEPTENTRIO receiver when SEPTENTRIO type is selected in GPS:TYPE? settings.

  • Page 71: Gps:system:timesource:state

    GPS Subsystem GPS:TYPE? settings. This command also determines the primary GNSS constellation in PVT solution. NOTE No PVT solution will be computed if insufficient satellites of selected timing resources are visible and tracked by the receiver. The default timing source is GPS. Under GPS-denied challenged environment, changing to GAL for Galileo system time or BD for Beidou system time is recommended for potential alternative PVT solution.

  • Page 72: Gps:reset Once

    GPS Subsystem GPS:RESET ONCE This command will issue a restart sequence for the uBlox/Mosaic GNSS receiver. The uBlox/Mosaic GNSS receiver will be initialized to its default settings after the reset. GPS:REFerence:ADELay <float> <s | ns > [-32767ns,32767ns] The ADELay command allows bi-directional shifting of the 1PPS output in relation to the UTC (USNO) 1PPS reference in one nanosecond steps for GNSS receiver ONLY.

  • Page 73: Gps:fov [3,85]

    GPS Subsystem This command has the following format: GPS:CNOthres [1,40] This command will query the state of this command: GPS:CNOthres? GPS:FOV <int> [3,85] This command allows the user to set the minimum elevation limit of a satellite above the horizon in order to be used in the GNSS navigation solution ONLY. Low elevation satellites may provide degraded accuracy, due to the long signal path through the atmosphere.

  • Page 74: Gps:gnss:reset

    GPS Subsystem GPS:GNSS:POWer <ON|OFF> This command will query the state of this command: GPS:GNSS:POWer? GPS:GNSS:RESET <ONCE | HOT | COLD> This command will issue a restart sequence for the uBlox/Mosaic GNSS receiver. The uBlox/Mosaic GNSS receiver will be initialized to its default settings after the reset. GPS:GNSS:FWver? This query prints the firmware version of the GNSS receiver.

  • Page 75: Gps:stl:isp On

    GPS Subsystem GPS:STL:RESET:AUTO <int> [0,604800] This command will query the state of this command: GPS:STL:RESET? GPS:STL:ISP ON This command will send the STL-2600™ board into ISP mode for reprogramming. Refer to Chapter 4 of the STL-2600™ User Manual for programming instructions. GPS:STL:SCPI <ASCII>...

  • Page 76: Gps:stl:agc [500,2700]

    GPS Subsystem ALERT If the new OTA key is received, the existing key will be overwritten. Subscription state may have changed and affected receiver operation. This is expected behavior in response to an OTA update. This command has the following format: GPS:STL:SUBScription:AUTHKEY <string>...

  • Page 77: Gps:stl:cno:maximum

    GPS Subsystem RECEiver:STL:CNO:MINTHReshold <float> [1.0,100.0] The following command will query the settings of this command: RECEiver:STL:CNO:MINTHReshold? GPS:STL:CNO:MAXimum? This command queries the current maximum CNO of recently received bursts from the STL receiver. GPS:STL:DOPpler:MINimum <double> [-36000.000000,0.0] This command allows the user to configure the minimum doppler value for any burst to be further processed in the STL solution.

  • Page 78: Gps:stl:ppsfilter:pfom [1,9]

    GPS Subsystem GPS:STL:PPSFilter:PFOM <int> [1,9] This command configures the maximum Position Figure of Merit (PFOM) allowed before the STL receiver provides a 1PPS output. For more details see the RECEiver:STL:PPSFilter:PFOM command in the STL-2600 User Manual. Default setting is 4. GPS:STL:PPSFilter:TFOM <int>...

  • Page 79: Gps:stl:extclock

    GPS Subsystem This command has the following format: GPS:STL:CLOCKmodel:FAST <double> [1E-20,1.0] The following command will query the settings of this command: GPS:STL:CLOCKmodel:FAST? GPS:STL:EXTCLOCK <ON|OFF> This command will toggle the state of CSAC_LOCK pin (8 on the STL-2600™ 20-pin connector) and enable/disable the use of the external clock (10 MHz) input to the STL- 2600™...

  • Page 80: Gps:stl:bpmreceived

    GPS Subsystem GPS:STL:BPMReceived? This query will return the number of received STL bursts in last 60 seconds on the STL- 2600™ board if mounted. Typical values range from 0 to 400 depending on the quality of STL signal reception at the time of query. GPS:STL:BPMProcessed? This query will return the number of processed STL bursts in last 60 seconds on the STL-2600™...

  • Page 81: Gps:survey Once

    GPS Subsystem GPS:TMODe <ON|OFF|RSTSURV> The following command will query the settings of this command: GPS:TMODe? GPS:SURVey ONCE The Timing Mode is not currently supported in PNT-62xx. This command starts a Survey. At the end of the Survey, the calculated Hold position will be stored in NVRAM. The Survey parameters can be set with the GPS:SURVey:DURation <sec>...

  • Page 82: Gps:hold:position

    GPS Subsystem GPS:SURVey:VARIANCE <mm^2> This command specifies the minimum variance of the average position computed during the Survey. This minimum value is used as a threshold under which the GNSS receiver can stop the Survey. The GNSS receiver will stop the Survey when the minimal duration has been reached and the variance of the average position is under the specified minimum variance.

  • Page 83: Gps:dynamic:mode [0,8]

    GPS Subsystem Table 8 lists all available dynamic modes. Table 8 Supported Dynamic GNSS operating modes Value Model Application Portable Recommended as a default setting Stationary Used in stationary applications Pedestrian Used in man-pack, pedestrian settings Automotive Vehicular velocity applications Used on ships, where altitude is expected to be constant Airborne <1g...

  • Page 84: Gps:dynamic:mode

    GPS Subsystem Table 9 Auto Dynamic Mode switching rules Selected Dynamic Velocity Threshold Fallback to lower setting Model >2 knots Pedestrian <1 knots >10 knots Automotive <8 knots >60 knots and >400 Airborne 1g <50 knots Feet/min climb/descent >150 knots Airborne 2g <130 knots >240 knots...

  • Page 85: Nmea Support

    GPS Subsystem This state can be different from the user-selected Dynamic model mode for two reasons: • If the dynamic mode is set to 8 (Automatic mode), the state will reflect the dynamic model being applied to the GNSS receiver depending on actual vehicle dynamics •...

  • Page 86: Gps:gprmc [0,255]

    GPS Subsystem Table 10 PRN numbering scheme for GNSS systems GPGSV PRN vehicle GNSS Type SV Range Talker ID numbering BeiDou B1-B37 401-437 IMES I1-I10 173-182 QZSS Q1-Q5 139-137 GLOSNASS R1-R32, R? 65-96, 0 In addition to standard NMEA sentences, the PNT-62xx GNSDO also supports PJLTS and PJLTV VIAVI proprietary NMEA sentences, PASHR and a proprietary version of the GGA sentence (GGASTat) described in “GPS:GGASTat <int>...

  • Page 87: Gps:gpgga [0,255]

    GPS Subsystem GPS:GPGGA <int> [0,255] This command instructs the PNT-62xx to send the NMEA standard GGA message every N seconds, with N in the interval [0,255]. The command is disabled until the GNSS receiver achieves a first fix. This command has the following format: GPS:GPGGA <int>...

  • Page 88: Gps:gpgll [0,255]

    GPS Subsystem traditional GPS receivers that display height in GPS Meters. The difference between MSL and GPS height can be significant, 35m or more are common. GPS:GPGLL <int> [0,255] This command instructs the PNT-62xx to send the NMEA standard GLL message every N seconds, with N in the interval [0,255].

  • Page 89: Gps:pjltv [0,255]

    GPS Subsystem • d is the lock status • e.eeeeeee is the EFC voltage, • ff.ffff is the EFC percentage (0% to 100%), • g.gEhh is the estimated frequency accuracy (similar to 100s ADEV) in scientific notation, • iii is the seconds in holdover, •...

  • Page 90: Gps:gpzda [0,255]

    GPS Subsystem Additionally, the number of accrued Leapseconds and GPS time of week is indicated in this message, which allows proper calculation of GPS time from UTC time as indicated by other messages, as well as proper handling of Leapsecond events. Use the following format to generate the velocity vector every N seconds, with N in the interval [0,255]: GPS:XYZSPeed <int>...

  • Page 91: Gps:gpgsa [0,255]

    GPS Subsystem parameters such as time, date, position, velocity, direction, altitude, quality of fix, and more. As an example, the String has the following data format: $PASHR,POS,0,12,191512.00,3610.11157,N,11518.89941,W,00887. 70,????,000.00,000.0 1,-00.00,00.0,00.8,00.0,00.0,0.46*21 NOTE The length of the string is fixed at 115 characters, plus the two binary 0x0d, 0x0a termination characters.

  • Page 92: Gps:gpgsv [0,255]

    GPS Subsystem The command has the following format: GPS:GPGSA <int>[0,255] This command queries the state of this command: GPS:GPGSA? The GPGSA string has the following data format: $GPGSA,a,a,x,x,x,x,x,x,x,x,x,x,x,x,x,x,x.x,x.x,x.x*[checksu The GSA output message header includes the talker ID for the currently enabled GNSS system(s) or STL receiver mode as described in “NMEA Support”...

  • Page 93: Gps:satellite:visible:count

    GPS Subsystem GPS:SATellite:VISible:COUNt? This query returns the number of satellites (PRN) that the almanac predicts should be visible, given date, time, and position for GNSS receiver only. GPS:POSition? This query will return the GPS:GPRMC latitude, longitude, the speed over ground in knots, and the course made good check.

  • Page 94: Gps:status

    GPS Subsystem GPS:STATus? This query returns the status of the GNSS or STL receiver. For GNSS receiver mode, a status of 1 means a fix is not available. A status of 2 indicates a 2D fix has been achieved and a status of 3 indicates a 3D fix has been achieved. For STL receiver mode, a status of 1 or higher indicates a 3D fix.

  • Page 95: Gps:initial:time

    GPS Subsystem synchronization of two units to each other. The internal RTC is driven by the highly stable ovenized oscillator 10MHz signal, and thus has very high time accuracy. If the internal RTC DATE has set itself to 1/1/2010 and the internal RTC TIME has set itself to 00:00:00 upon power-up, this indicates the clock is outdated and the user must wait for valid UTC data from the receiver or modify the time to a valid one.

  • Page 96: Gps:rtc:time

    GPS Subsystem GPS:RTC:TIME <hour,min,sec> This command allows setting the hardware RTC TIME manually when operating the unit in GNSS denied environments. The on-board super-capacitor C63 will keep the hardware RTC clock running for additional 1+ days after removing the PNT-62xx main power supply.

  • Page 97: Gps:passthru:count [1,86400]

    MEASURE Subsystem GPS:PASSthru:COUNt <int> <s> [1,86400] This command will set length of time the device remains in pass-through time-out mode described in “GPS:PASSthru:TIMEout <ON|OFF>” on page 78 . The time entered should be in seconds and the default period is 60 seconds. This command has the following format: GPS:PASSthru:COUNt [1,86400] This command will query the state of this command:...

  • Page 98: Ptime:date

    PTIME Subsystem PTIME Subsystem The PTIME subsystem regroups all the commands related to the management of the time. The following commands are supported: • PTIMe:DATE? • PTIMe:TIME? • PTIMe:TIME:STRing? • PTIMe:TINTerval? • PTIMe:OUTput <ON|OFF> • PTIMe:LEAPsecond? • PTIMe:LEAPsecond:PENDing? • PTIMe:LEAPsecond:ACCumulated? •...

  • Page 99: Ptime:leapsecond

    PTIME Subsystem SYNC:SOUR:MODE EXT command. This allows time-synchronization at the nanosecond level between two units which can be useful when operating in GPS denied environments. The following command returns the PTIME output setting stored in NV memory: PTIMe:OUTput? Sending the following command will cause the unit to automatically generate GPS:INIT:DATE and GPS:INIT:TIME sentences described in “GPS:INITial:DATE <yyyy,mm,dd>”...

  • Page 100: Ptime:leapsecond:accumulated

    RFOUTput Subsystem PTIMe:LEAPsecond:ACCumulated? This command returns the internally applied leap second offset between GPS time and UTC time as stored in the EEPROM (GPS Almanac not received yet) or as indicated by the GNSS receiver (GPS Almanac is available). PTIMe:LEAPsecond:DATE? This command returns the date of the pending leap second, if available for current receiver mode.

  • Page 101: Rfoutput

    RFOUTput Subsystem • RFOUTput:SIM:RESTART ONCE • RFOUTput:SIM:HOLDover:MODE <ON|OFF|LIMIT> • RFOUTput:SIM:HOLDover:LIMIT <int> [5, 86400] • RFOUTput:SIM:LNAV:SELect <AUTO|USER|LIVE> RFOUTput <ON|OFF> This command will enable or disable the transcoding RF output signal on the Micro- Transcoder. Transcoding is enabled by default. If the Transcoder is not transcoding properly, try sending the RFOUT ON command once.

  • Page 102: Rfoutput:reset Once

    RFOUTput Subsystem RFOUTput:DCBlock <ON|OFF> This command will query the state of this command: RFOUTput:RESET ONCE This command will issue a reset sequence for the Micro Transcoder™ board once. RFOUTput:ISP ON This command will send the Micro Transcoder™ board into ISP mode for reprogramming.

  • Page 103: Rfoutput:sim:holdover:limit [5, 86400]

    System subsystem RFOUTput:SIM:HOLDover:LIMIT <int> [5, 86400] This command specifies the limit, in seconds, that the holdover state should remain active in the Limit simulation holdover mode. The maximum limit is 1 day or 86400 seconds. Once this holdover limit is reached, the RF output is disabled. For longer holdover periods, use the ON simulation holdover mode.

  • Page 104: System:communicate:dload

    System subsystem • SYSTem:ISP • SYSTEM:POWER <SLEEP|DSLEEP|PDOWN|DPDOWN> • SYSTEM:FWConfig? • SYSTEM:ID? • SYSTEM:ID:SN? • SYSTEM:ID:UID? • SYSTEM:ID:MODELname? SYSTem:COMMunicate:DLOAD <STL|GNSS|TRANscoder> This command will enable the PNT-62xx to enter download/programming mode for the specified serial port. The ports that can be used for downloading are: STL, GNSS, or TRANscoder SCPI ports.

  • Page 105: System:communicate:serial:baud <9600|19200|38400|57600|115200

    System subsystem SYSTem:COMMunicate:SERial:FAST? SYSTem:COMMunicate:SERial:BAUD <9600|19200|38400|57600|115200> This command sets the serial speed for SCPI serial port. The serial configuration is always 8 bit, 1 stop bit, no parity, no HW flow control. Upon Factory reset, the speed is set at 115200 bauds. Higher baud rates such as 115200 are suggested if several NMEA commands are enabled, or high rates of serial communications are expected to avoid serial port overflow.

  • Page 106: System:communicate:rsrscpi:baud <9600 | 19200 | 38400 | 57600 | 115200>88

    System subsystem SYSTem:COMMunicate:RSRSCPI:BAUD <9600 | 19200 | 38400 | 57600 | 115200> This command sets the serial speed for SCPI port of the Micro-Transcoder. The serial configuration is always 8 bit, 1 stop bit, no parity, no flow control. The factory default setting is 115200 baud.

  • Page 107: System:communicate:csac:baud <9600 | 19200 | 38400 | 57600 | 115200

    System subsystem SYSTem:COMMunicate:STL:MODE <ON|OFF> This command will query the state of this command: SYSTem:COMMunicate:STL:MODE? SYSTem:COMMunicate:CSAC:BAUD <9600 | 19200 | 38400 | 57600 | 115200> This command sets the CSAC serial speed. The serial configuration is always 8 bit, 1 stop bit, no parity, no flow control. The factory default setting is 115200 baud. This command has the following format: SYSTem:COMMunicate:CSAC:BAUD <9600 | 19200 | 38400 | 57600 | 115200>...

  • Page 108: System:communicate:rsrgps:mode

    System subsystem SYSTem:COMMunicate:RSRGPS:MODE <ON|OFF> This command will enable or disable the communication for GPS port of the Micro- Transcoder port. This command has the following format: SYSTem:COMMunicate:RSRGPS:MODE <ON|OFF> This command will query the state of this command: SYSTem:COMMunicate:RSRGPS:MODE? SYSTem:STATus? This query returns a full page of GNSS status in ASCII format. The output is compatible with the GPSCon Windows program discussed in Chapter 3 “GPSCon Utility”.

  • Page 109: System:power

    System subsystem SYSTem:POWer <SLEEP|DSLEEP|PDOWN|DPDOWN> This command configures the power-down state of the microprocessor. The possible states include: sleep, deep sleep, power down mode, or deep power down mode. The SLEEP command puts the device into a power saving state where all actions are stopped.
  • Page 110 System subsystem PNT-62xx Assured Position, Navigation, and Timing Reference User Guide Page 92 22171774, R002 March 2024...

  • Page 111: Firmware Upgrade

    Firmware Upgrade Chapter 5 The following topics are discussed in this chapter: • “Introduction” on page 94 • “ISP Flash Loader Utility installation” on page 94 • “Putting the PCB into In-Circuit Programming (ISP) mode” on page 94 • “Downloading the firmware” on page 94 •...

  • Page 112: Introduction

    Chapter 5 Firmware Upgrade Introduction Introduction The following sections provide instructions on how to upgrade the PNT-62xx firmware. Please follow the instructions in order to prevent accidentally corrupting the PNT-62xx Flash. ISP Flash Loader Utility installation VIAVI recommends using the JLTerm application to upgrade the contents of Flash memory on the PNT-62xx.

  • Page 113: Using The Jlterm Programming Terminal

    Chapter 5 Firmware Upgrade Downloading the firmware Using the JLTerm programming terminal Download the JLTerm application from http://www.jackson-labs.com/index.php/ support. Install and open the JLTerm application. Select the COM port in JLTerm as needed on your PC. Once a successful connection is established, the connection icon becomes green, as shown in Figure 14.
  • Page 114 Chapter 5 Firmware Upgrade Downloading the firmware Figure 15 Open Hex file and download firmware If an error occurs during the programming process: Check the USB cable connection. While the unit is still in ISP mode after the error occurred, follow the steps in “Using the Flash Magic programming utility”...

  • Page 115: Using The Flash Magic Programming Utility

    Chapter 5 Firmware Upgrade Downloading the firmware Using the Flash Magic programming utility Perform the following steps to use the Flash Magic programming utility. NOTE The following procedure is for Flash Magic version 12.1 or later. For version 11.20 or older, refer to “Using the Flash Magic classic version”...

  • Page 116: Using The Flash Magic Classic Version

    Chapter 5 Firmware Upgrade Downloading the firmware The firmware is downloaded to the processor. Verify the firmware update as described in “Verifying the firmware update” on page 100. Using the Flash Magic classic version NOTE The following procedure is for Flash Magic version 11.20 or earlier. For version 12.1 or later, refer to “Using the Flash Magic programming utility”...
  • Page 117 Chapter 5 Firmware Upgrade Downloading the firmware Figure 20 Communications options Click OK to return to the main menu. Click the Select Device button. The Device Selection window appears, as shown Figure Figure 21 Device selection PNT-62xx Assured Position, Navigation, and Timing Reference User Guide March 2024 22171774, R002 Page 99...

  • Page 118: Verifying The Firmware Update

    Chapter 5 Firmware Upgrade Verifying the firmware update Expand the ARM CORTEX folder and select the appropriate processor, in this case LPC18S37. 10 Configure the following parameters, as shown in Figure: – Baud Rate: 115200 – Oscillator (MHz): 10.0 11 Check the Erase blocks used by Hex File box. ALERT Do NOT check the box marked Erase all Flash.

  • Page 119: Certification And Warranty

    Certification and Warranty Chapter 6 This chapter discusses the following topics: • “Certification” on page 102 • “Warranty” on page 102 • “Exclusive Remedies” on page 102 PNT-62xx Assured Position, Navigation, and Timing Reference User Guide March 2024 22171774, R002 Page 101...

  • Page 120: Certification

    Chapter 6 Certification and Warranty Certification Certification VIAVI certifies that this product met its published specifications at time of shipment. Warranty This VIAVI hardware product is warranted against defects in material and workmanship for a period of 1 (one) year from date of delivery. During the warranty period VIAVI will, at its discretion, either repair or replace products that prove to be defective.

  • Page 121: Appendix A Document Revision History

    Document revision history Appendix A Table 1 PNT-62xx Assured Position, Navigation, and Timing Reference User Guide, 22171774 Revision Date Details R000 April 2023 Initial release of document. R001 January 2024 Added: - ETA and commands - Jamming Detection - Minor editorial changes PNT-62xx Assured Position, Navigation, and Timing Reference User Guide March 2024 22171774, R002...
  • Page 122 PNT-62xx Assured Position, Navigation, and Timing Reference User Guide Page 104 22171774, R002 March 2024...
  • Page 124 22171774 R002, March 2024 English Viavi Solutions North America: 1.844.GO VIAVI / 1.844.468.4284 Latin America +52 55 5543 6644 EMEA +49 7121 862273 APAC +1 512 201 6534 All Other Regions: viavisolutions.com/contacts email TAC@viavisolutions.com Address 1445 South Spectrum Blvd., Suite 102, Chandler, AZ, 85286, USA...

Table of Contents