Yeah I know they are old but so am I and 99% of the time they work great.
Just did a survey (I have 3 units) one unit was set all day as a base station, the other two moved at ~60min intervals to 3 points each. All the vectors errors are in the hundredths of a foot range exc one. The vector between the base station and the section cor about 1200 ft away has 1 ft errors float fail. Is there anyone that can read the files and see if just part of it is corrupted or if that session is junk or know someone that can. Someone did that for me at Ashtech some years ago but last time I contacted them they just said those were obsolete and no assistance was available.
Thanks.
Maybe PHIL STEVENSON ?
Good Luck
Derek
email Me
I will reply and then you can reply with the attached files. You cannot send attachments through the Surveyor Connect email link.
Send me all your downloaded files for the day.
Paul in PA
What version of Asthech Solutions are you using? If it's "2.X" I could probably give you some pointers to try to work out the bad data.
If you were using 3 receivers, and one vector failed, then that means you have a good vector to the section cor.?
If you have Ashtech Solutions 2.7, or something similar, you can view the quality of the data files by going to the "Vector Tab", then right clicking on your failed vector, and clicking "View Raw Data" and/or "View Residuals".
A failed vector could be the result of one bad Satellite feed, so if you notice one Sat has a lot of cycle slips, or drops in/out of receptions, or has a bad signal to noise ratio, you can turn off that Sat. for the observations and reprocess.
To do that, right click on the failed vector from the vector tab, and click "Process". There, you will get some options, like you can change your start/stop time, turn off a Sat, change the reference sat for processing, or change your elevation mask. Tinkering with those settings can often eliminate the bad data and get your vector to pass.
Sometimes just upping the elevation mask by a couple of degrees will cause a fail vector to pass. I'd start by just changing that, from say 10 to 12, then if that doesn't pass, try 12 to 14, etc. Do that up to about 20 degrees, keep reprocessing, to see it if passes.
If that doesn't work, change the elevation mask back to 10, then look your "View Residuals" tab to see what the reference Sat is for that process, then ban that reference sat, and reprocess.
If that doesn't work, look at the "View Residuals" tab and "Raw Data" tab to try to identify the "noisiest" sats. Write down 3 or 4 that look bad, then ban each sat (one a time) and reprocess. Make sure you remove the last sat from the list, before you add a new one, so that your number of sats. available does not drop too much.
You can also try cutting off the first or last 5 minutes of the file and reprocessing. Sometimes that works.
If none of this works, you can try combinations of the ideas above, including banning two sats at the same time.
Sometimes it works, sometimes it doesn't.
You might spend an hour messing with the data, then still have to go back out and reobserve.
At least, if I understand your post correct, you have a passed vector from a third LOCUS that you can use a check, to make sure that tinkering with the data has not resulted in a false "fix.
Good luck.
Thanks for all the response.
Late last night I remembered the person watching this unit had to change the batteries shortly after startup. I had a brain fart and was wondering why that unit, base unit, had 2 sessions. I removed that A session and all is good. Weird that we were GPSing 3 points at the time and only the one leg was affected.
Anyways, Thanks again.
