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

How to Recover Abbreviated ASCII Logs from Raw Data

Commands/messages are sent/logged in:

binary: requested by appending `b` to message name (i.e: BESTPOSB)
ASCII: requested by appending `a` to message name (i.e: BESTPOSA)
Abbreviated ASCII: used for ease of reading during acquisition via NovAtel Connect or a third party terminal emulator application. No letter appended after message name (i.e: BESTPOS)

If for some reason users forget to append the `b` to a log request (while saving data to the PC for post-processing, troubleshooting), the log will be saved in abbreviated ASCII rather than binary (or ASCII, even though binary is recommended). Now, when converting the data from binary to ASCII via NovAtel Convert, they will have an issue as Convert does not recognize abbreviated ASCII messages. Thus, the binary messages will be converted to ASCII, but the abbreviated ASCII logs will be ignored. 

The problem here is that the file contains both binary and ASCII data and as such a method is required in order to separate one from the other. That way, the abbreviated ASCII messages could be isolated and parsed some other way. 

Linux contains the string command line command which separates binary from ASCII strings in one file. The script found in provides the same functionality for Windows DOS. The input neeeded is:

strings.exe -a -n input.log > output_AbASCII.txt


-a  -->  specifies we want to isolate ASCII 
-n 10 -->  specifies we only want to consider strings that are greater than 10 characters in length
2014_322_2804_span_1.log  -->  the original binary + abbreviated ASCII messages
Output.test --> output file