AI Assistant
Topcon Hiper V and ...
 
Notifications
Clear all

Topcon Hiper V and VRS

5 Posts
3 Users
0 Reactions
1,010 Views
CMC77
(@cmc77)
Posts: 10
Member
Topic starter
Translate
English
Spanish
French
German
Italian
Portuguese
Russian
Chinese
Japanese
Korean
Arabic
Hindi
Dutch
Polish
Turkish
Vietnamese
Thai
Swedish
Danish
Finnish
Norwegian
Czech
Hungarian
Romanian
Greek
Hebrew
Indonesian
Malay
Ukrainian
Bulgarian
Croatian
Slovak
Slovenian
Serbian
Lithuanian
Latvian
Estonian
 

We have recently run into a problem with our Topcon Hiper V's when utilizing the Ohio VRS system. When using the VRS, we have found that our elevations are approximately 3.7' higher than the listed NAVD 88 elevations. We've run checks multiple times and compared the elevations to other surveyors, and everything seems to point towards the equipment.

Everything checks within the surveys themselves, as well as when we use RTK everything is fine. We only run into the issue when using the VRS. The issue also isn't isolated to a single base?ÿ / rover set. We've noticed it on multiple sets.

Has anyone else run into this before? Any suggestions as to how we can fix the problem?


 
Posted : August 24, 2018 8:59 pm
zammo
(@zammo)
Posts: 104
Member
Translate
English
Spanish
French
German
Italian
Portuguese
Russian
Chinese
Japanese
Korean
Arabic
Hindi
Dutch
Polish
Turkish
Vietnamese
Thai
Swedish
Danish
Finnish
Norwegian
Czech
Hungarian
Romanian
Greek
Hebrew
Indonesian
Malay
Ukrainian
Bulgarian
Croatian
Slovak
Slovenian
Serbian
Lithuanian
Latvian
Estonian
 

Hey mate,

?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ Sounds very odd, the fact that it's only happening when VRS and not all the time makes me think there may be a setting that may need to be adjusted. Without being able to see whats happening on screen, I'd assume that a geoid file may be the culprit.

A good check for this would be to do some checks on a localized project using VRS and see if the error continues, if it doesn't then you can eliminate the equipment being the issue. Also, if the other surveyors are using the same type of controllers and field software try running your receivers with their controllers to see if the error continues.

What field software are you using?


 
Posted : August 24, 2018 11:11 pm
leegreen
(@leegreen)
Posts: 2186
Member
Translate
English
Spanish
French
German
Italian
Portuguese
Russian
Chinese
Japanese
Korean
Arabic
Hindi
Dutch
Polish
Turkish
Vietnamese
Thai
Swedish
Danish
Finnish
Norwegian
Czech
Hungarian
Romanian
Greek
Hebrew
Indonesian
Malay
Ukrainian
Bulgarian
Croatian
Slovak
Slovenian
Serbian
Lithuanian
Latvian
Estonian
 

Very common mistake. 3.7 ft is the difference between NAD83 and NAD83_NO_TRANS. You should always use the later with a Network GPS.?ÿ


 
Posted : August 25, 2018 1:35 am
CMC77
(@cmc77)
Posts: 10
Member
Topic starter
Translate
English
Spanish
French
German
Italian
Portuguese
Russian
Chinese
Japanese
Korean
Arabic
Hindi
Dutch
Polish
Turkish
Vietnamese
Thai
Swedish
Danish
Finnish
Norwegian
Czech
Hungarian
Romanian
Greek
Hebrew
Indonesian
Malay
Ukrainian
Bulgarian
Croatian
Slovak
Slovenian
Serbian
Lithuanian
Latvian
Estonian
 

We tried the NAD 83 and NAD 83_NO_TRANS and that solved the problem.

Thanks.


 
Posted : August 27, 2018 8:27 am
leegreen
(@leegreen)
Posts: 2186
Member
Translate
English
Spanish
French
German
Italian
Portuguese
Russian
Chinese
Japanese
Korean
Arabic
Hindi
Dutch
Polish
Turkish
Vietnamese
Thai
Swedish
Danish
Finnish
Norwegian
Czech
Hungarian
Romanian
Greek
Hebrew
Indonesian
Malay
Ukrainian
Bulgarian
Croatian
Slovak
Slovenian
Serbian
Lithuanian
Latvian
Estonian
 

Great!


 
Posted : August 27, 2018 9:52 am