I can't seem to get a certian file to load into the processor.
I took 4 gps obs. on this day, and one REFUSES to load.

It will download, from LOCUS to my PC, and shows as a file. BUT won't show up as a file in the processor.

It shows up in download.

HELP!

LOCUS Ver. 2.4

Nate

PS
Phil,
I emailed it all to you.

the problem file is TOO SMALL

What the H*** happened?

Have I got to go and reshoot this stinking thing?

Modified By Nate Dearyan on 9/24/2002 at 11:11 AM

Nate, I used what J.D. calls my VooDoo on it and made it work for me. My repaired version of the stubborn B file is on the way to you.

It is a small file. If that receiver is being stubborn do a full reset then set it outside for 25 minutes to get a new almanac before you go to the field with it again.

As always, keep a diary on your tools. The ones that keep causing problems need to be repaired.

What happened is a glitch that I see once in a very great while with the Locus data. I am not sure why it happens but we have some tools that will often make it all better. Sometimes when I clean the file up it will work. Sometimes it does not.

Phil,

Tell me the nature of what you did.

Your little VOODOO ain't voodoo, it is science.

Tell me some of it.

I got in too big of a hurry, and so I drove back to the site today, cleared (reset)all 3 recievers, and re-shot stuff. This way I could determine what was real. On that shot to No. 3, I used different recievers. (the ones that worked).

What's got me puzzled is that all 3 recievers had been cleared at the same time, and should have had the same basic stuff in them.

By the way, the "fixed" file you returned, checked within 0.025' of what I shot today.

I guess I'm looking for a little more of an explanation.

I want to know how to avoid this in the future.

Thanks, Phil


Nate

With any electronic gadget there are bound to be random problems that come up. It seems like mine are always at the point that is farthest from the truck.

There is probably not anything that you did to make it happen and may not be anything that you can do to keep it from happening again.

We got lucky and fixed it.

OK

Howdja fix it?

Huh?

Nate

Nate, I don't have a clue what Phil did either: But here's an idiot's way to do what he did scientifically...

Convert the Locus file to Rinex. Then open it up in wordpad, look at it briefly and smile to yourself..Then convert it back from rinex to ashtech format and insert into Locus....

I kid you not....I think it has something to do with Doppler information not being written for one bird, and the rinex converter looks for that info and magically either interpolates it or ignores it so the conversion back does not have that problem...

Phil, if youall don't want some more stupid speculation about how it works please give us a hint......thnks. bob



PS NATE, STOP SPINNING THAT ANTENNA SO FAST!!!!!!!!
Modified By Robert Bills on 9/24/2002 at 10:58 PM

OK, so I have some tools that are not for public distribution. That's just one of the rules I have to live by. But Bob's idea sounds interesting.

I submitted a request that the particular problem that you guys sometimes send to me in Locus files be solved with a routine in Ashtech Solutions.

I have seen this less than six times in one year so who knows whether it will just be one of those things that one of us has to help you with. It may be a part of our reason to be here.

I really don't know why it goes wrong. I see the problem and I sick this software tool on the file that has the problem and it does the repair.

It's not much science on my part. It's mostly about helping you fix problems as a full time job.

OK OK, so "I have some tools that are not for public distribution".

Thats OK with me.

I have a thing against asking for help, when I have not exhausted all my own resources.

So, now if you get a file from me, is NOT MY FAULT.

I will be upset, if you ever go away.

If you ever go away, send me your tool kit. Or leave it in your will.

I don't like to feel vulnerable.

:)

Thanks for the help.

Nate