I have an old TDS Recon with Survey Pro 4.2.1. It was running RTK successfully in the past, but now every time I try to set it up again I get the following message: "Unspecified projection error. The coordinate was out of range of the coordinate system or grid files"
I have tried a local projection and also a mapping plane approach with the same result. I start with an assumed point Ā (5000,5000), then establish geodetic values on it with the GPS receivers, and still get the error. Also stored an autonomous point with no success. I have tried moving points the proper coordinates with the projection routine and the collector will not make the calculation - gives an error message. I have even tried storing a point with the proper GPS Ā lat / long and corresponding State Plane values (calculated with Corpscon) and it still will not work. Seems like something is corrupted in the software as I have done this in the past many times, but I am not ruling out something I am doing wrong.
I did verify the GPS receivers were working correctly. Used the Recon to store static observations and processed successfully with OPUS.
I really would like to get this collector going again and do not desire to upgrade as this is just used for the rare side project. Any help or suggestions most appreciated.
Thanks,
Doug
Replies
Thanks for the responses so far- sorry I have not responded sooner, but I just now got power back on here in North Georgia thanks to Irma. Anyway, Ā I am not using a VRS network. I am simple connecting to Topcon receivers and trying to do RTK. I will look at the geoid update. Trying to stay away from the Trimble site for updates as they always embed a nice little fee somewhere for every update :)
Check with the service provider.
I don't blame you for not updating. If it ain't broke, you'll break something trying to unnecessarily fix it. Ā I waste more time waiting on updates to load; only to find out they changed some stinking font or input box. Ā Its like surveying for an engineer that wants to move a soccer field a foot just to be able to bill the client again.
Doug,
You most likely need to update the Geoid file that is in your data collector. Ā
Try doing an initialization setup for the sessions by using the "here" option to find a local coordinateĀ
Also, if you are close to a zone boundary you will get an error if your position is outside the limits of that zone. Ā So try the next zone near you. Ā It happens more than you might think - Ā It happens couple times a year here in Central Indiana which has both Indiana East and West zones overlap.
Lastly and most obvious, is there a reason you have not updated from 4.2.1? Ā
Kevin