ADR Sign Convention used in NovAtel GPS Receivers and RINEX Almanac Injection Procedure Amperage vs Voltage ASCII to binary log conversion example Can carbon fiber be used as an antenna cover? Can the GPGGA positions be output with more decimal places? Destination IP Should be Set in ICOMCONFIG if Setting up UDP Connection Difference Between Message Latency and Time Accuracy DL-4 DL-V script Example Do GPS-700 series antennas have a defined "North point"? GNSS-750 MTBF GNSS Ephemerides and Almanacs GNSS Frequencies and Signals GPS Receiver and SPAN SDLC card synchronization GPS Tracking Performance on Aircraft (Power Supply Issues) How does RTKANTENNA work? How Electrical Overstress damage is caused How often does Averaging Filter in POSAVE Command get Applied? How to Connect to PwrPak7 How to Determine the Channel in an ASSIGN Command How to extract 85-bit string from GLORAWFRAME log How to identify my PwrPak7 How to Recover Abbreviated ASCII Logs from Raw Data How to Use PASSCOM to Redirect Data HxGN SmartNet on NovAtel receivers In what frame is CORRIMUDATAS output in OEM6? ITK and Dual Antenna Receivers Maximum Cable Length vs. Data Rate MIC Mating Connectors MSM 6 and MSM 7 Issue MTBF Specifications for GPS-700 Series New ALIGN Message Lengths OEM4 and OEMV Reporting 1994 (Week Roll Over) OEM615 MTBF OEM628 MTBF OEM6 Dev Kit weight OEMStar API Specifcations OEMStar MTBF OEMV1-DF MTBF OEMV-2 & OEMV-2G MTBF OEMV Auth Codes for 3.907 ProPak6 FTP ProPak6 - USB Drive File Format Recommended Alignment Procedures Recommended Logs for Post Processing Regarding Absolute and Relative Antenna Calibrations Regarding standard deviations used in RBV Calibration Remaining memory on OEM638/ProPak6 Reporting a Stolen Receiver RTK Quality Mode, Extra Safe Mode SBAS Position Mode Sending Batch File and Logging Binary Data in Real Term SPAN-CPT Commonly Asked Questions SPAN-CPT Power specifications SPAN Troubleshooting logs Understanding IMU Data Gaps: Causes and Mitigation Strategies Updating SMART6 firmware from 6.230 or 6.231 to 6.510 (or later) USB Not Supported in WinLoad Software Using RTCM ephemeris data to speed up Time To First Fix (TTFF) WGS84 to ETRS89 datum transformations What Ionospheric Correction will SETIONOTYPE AUTO use? What is a EURO card? What is the Difference Between Active and Passive Serial Connection in CDU/Connect? What is the Effect of Bad Lever Arms in the GNSS/INS Filter? What is the Maximum Accepted Latency in ALIGN? What would cause speed (Field 8) in GPRMC to remain constant for some amount of time? Why am I seeing Two Kinds of HEADING2 Logs when Using two PP6Ds in Relative INS? Why Can't I disable RXSTATUSEVENTA permanently? Why is there no decoding information on the CAN PGNs? Why is the standard deviation of the BESTPOS log larger than the spec on the data sheet? Support Search

Almanac Injection Procedure

=== Q1] I was trying to upload an almanac into an OEM4/OEMV GPS receiver, but I am continuously getting the checksum error. What's the problem?

A1] First, you need an almanac to inject. It typically takes 15 to 20 minutes of continuous GPS tracking to download an updated almanac message. When the GPS receiver has obtained an up-to-date almanac, the almanac can be output using the following command: LOG ALMANACA The resulting output will contain the full ASCII version of the ALMANACA message, including the #ALMANACA header, the 32-bit checksum, and and a terminating [CR][LF]. An ALMANACA message can be injected into the GPS receiver using HyperTerminal's "Send Text File" option under HyperTerminal's "Transfer" menu, or via any serial interface mechanism that allows you to upload (send) straight text data to the GPS receiver. This only works for the full ASCII version of the ALMANACA message, due to some destructive bit stripping HyperTerminal does to the binary ALMANACB message. When the GPS receiver successfully processes an injected almanac, a response similar to the following example will be generated by the GPS receiver: #ALMANACR,COM1,0,0.0,SATTIME,1371,249834.000,00000000,0004,2177;OK*13be07c1

=== Q2] Is the injected almanac saved to memory automatically, or do I need to use the SAVECONFIG command to store the injected almanac?

A2] No, the injected almanac is not stored to NVRAM automatically. And no, SAVECONFIG will not save the injected almanac into NVRAM either. Only the live almanac downloaded directly from the GPS satellites will be saved into the NVRAM, and this will be done automatically. The injected almanac will be used temporarily and then be replaced with the live broadcast almanac when it becomes available after 15 to 20 minutes of continuous (uninterrupted) GPS tracking.

=== Q3.] So why would I bother to go through all this trouble injecting an older almanac into the GPS receiver?

A3.] If the injected almanac is close to up-to-date, injecting the almanac can speed initial acquisition of GPS satellites. Any application which requires rapid GPS satellite acquisition from a cold start state can benefit from an almanac injection initially prior to insertion into a live GPS satellite tracking environment.