Error Code 85 when reading Ephemeris File

[howmean]

Hi,

I've encountered some problems when running GPS Toolkit 1.5 Shipping Example (niGPS Write Waveform to File (Simple, Automatic Mode).vi).

The error code that I received is "Error 85 Scan From String...."

In order to find out what is wrong, I set breakpoints at 2 locations in the VI and used probes to monitor the error propagation.

Please refer to the attached screenshots.

As it is a "Scan from String" error, it should be related to either Almanac or Ephemeris files.

After doing comparisons between 2 ephemeris and almanacs files of different dates, I realised that the difference occurs at how floating numbers are represented in the Ephemeris Files.

For e.g: 0.100000000000E+01 or 0.100000000000D+01

Refering to RINEX V2.10 specs, there is this part that states:

"*) In order to account for the various compilers, E,e,D, and d are allowed letters between the fraction and exponent of all floating point numbers in the navigation message files. Zero-padded two-digit exponents are required, however."

Apparently, the Ephemeris file that gives Error Code 85 is the one with letter "D" because when I changed all the "D"s to "E"s, the VI worked fine.

I downloaded the Ephemeris files from the following link: ftp://cddis.gsfc.nasa.gov/pub/gps/data/daily/2010/brdc/

- brdc1700.10n -> uses "E" between fraction and exponent

- brdc1750.10n -> uses "D" between fraction and exponent

May I know if this is a bug of GPS Toolkit 1.5? Has anyone encountered similar problem?

Thanks,

howmean

[Akiel]

Anyone? im having similar problems

[Akiel]

to give an update, i have found the source of the problem, at some point in the passed few years the ephemeris file format changed. Not just the way numbers are represented (i have looked at the KB and used the tool to no avail). I am able to use a ephemeris file from 2009 but not the latest one using the same code. Now to find a solution, will post it as soon as I have it

[Sastry]

🙂 I will definitely give kudos. Thank you for posting. 

But I am confused now. You are still getting the error? To the best of knowledge, nothing other than the "E" to "D"  changed. And we validated it as well in later version like GPS 2.0. So, what we do is, when an ephemeris file is provided, the D is converted to E if D is present. And we have validated that with all kinds of ephemeris. As I write, I have validated that the toolkit works with 2012 dated Ephemeris files as well. 

So, I am confused that you are getting this error.  Even after converting ? There is a tool provided on the web. Have you tried that ? Can you attach a problematic file (that you think should have worked) and tell me the line number where you are getting the error?  

May be some space didnt get properly inserted ? 

[Akiel]

Sorry for the long delay, yep I get this problem in gps1.5 after the tool has been used. I am updting to gps2.0 as I type, hopefully this will resolve the issue.