Equipment: R8-2 with GSM (GSM not used, no card inserted), TSC 12.50, wifi connection from tethered phone
I am set up for a VRS survey style (corrections through controller) with a dial in to the INDOT Cors through my tethered phone. I have checked my settings and, for now, believe they are all correct. You can review below at the end of this post
I then start a new job, start to measure with the VRS style, and after initialization, start collecting points. 15 satellites, good...Pdop/H:.06'/V:.07', tolerances all good...set for 5s observation and TSC 12.50 stores the point. But the points I am collecting have no coordinates when I review them! Why?
Is it because I have an R8-2 with a GSM radio and yet I am trying to route corrections through the controller? Any thoughts? Ask me any questions please.
(1) Detailed of VRS Style
*Rover Options
Survey Type: RTK
Broadcast Format: VRS (CMR)
Store Points As: Positions
EL. Mask: 10 deg
PDOP mask: 6.0
Ant. Type: R8 GNSS
Measure to: Bottom of ant.
Part No.: 60158-00
Serial Number: ?
Use L2e: Yes
GPS LsC: check
GPS L5: unchecked
Glonass: checked
*Radio Options
Type: Internet connection
Route Through Controller: Yes
Dial Profile: INCORS
*Topo Point
Auto step size: 1
QC: QC1 & QC2
Auto Store Point: check
Occupation time: 0m5s
Number of measurements: 3
Precision auto tolerance: check
Store RTK Fixed Only: Check
(2) Dial Profile
Name: INCORS
Network connection: localhost
Bluetooth modem: None
Modem Pin: blank
APN: None
Use NTRIP: check
Connect directly to mountpoint: check
MP Name: CMRP_IMAX(GNSS)
NTRIP username: *as supplied by INDOT*
NTRIP password: *as supplied by INDOT*
IP Address: *as supplied by INDOT*
IP Port: *as supplied by INDOT*
Connection type: GPRS
Send user info: unchecked
Scott,
What Coordinate System is your Job File set to?
Dave
I have the job set up for:
System: US State Plane 1983
Datum: Indiana East 130
Datum: NAD 183 (Conus) (MOL)
Use geoid model subgrid of Geoid 09 (hmm... bought this from a dealer in Utah, I am Indiana, wonder what the subgrid is....didn't catch the subgrid part, but wouldn't that only affect the verticals?)
Use datum grid: no
coords: Grid
Project Height 730.00sft.
Scott Bordenet, post: 324688, member: 10097 wrote: I have the job set up for:
System: US State Plane 1983Datum: Indiana East 130
Datum: NAD 183 (Conus) (MOL)
Use geoid model subgrid of Geoid 09 (hmm... bought this from a dealer in Utah, I am Indiana, wonder what the subgrid is....didn't catch the subgrid part, but wouldn't that only affect the verticals?)
Use datum grid: no
coords: Grid
Project Height 730.00sft.
It sounds like the geoid model isn't covering your area, this will cause the file to fail.
of course, I don't know this cause it happened to me,,,,,,,,,,like I went out of the subgrid area and couldn't get any data and had collect data in a different file without the geoid applied,,,,,,,,,no,,,,,,I wouldn't let that ever happen
Anyway join the club, you aren't the only one it's done this too, if you think about it makes sense GPS is all 3-d and the geoid file is part of that and if it cant see a correction to apply...........
OK - yeah, makes sense. I will get 12 whole CONUS, try again this weekend, and report back.
Scott
See if you can view the point in WGS84 Lat Lon Height.
If you can, then it's not a problem with your connection, it's something in your coordinate system as mentioned above.
James
Make sure you get Geoid 12a, 12 had some bad points.
Scott,
If you'd like to grab just a piece of Geoid12A, Trimble has a neat utility called Grid Factory here:
http://www.trimble.com/globalTRLTAB.asp?Nav=Collection-37882
Dave
Thanks for pointing that out. The GEOID files Trimble have assembled all in one place there are convenient too. I've bookmarked that.
Yes, the issue was the geoid file wasnt covering my location. I put in a geoid file that did (12a whole CONUS) and everything worked. Thanks to all that read my post and replied. Problem on Friday, solution by Monday morning.....PERFECT...THANKS.
Scott in Indy.
Scott Bordenet, post: 324896, member: 10097 wrote: Yes, the issue was the geoid file wasnt covering my location. I put in a geoid file that did (12a whole CONUS) and everything worked. Thanks to all that read my post and replied. Problem on Friday, solution by Monday morning.....PERFECT...THANKS.
Scott in Indy.
Right on man. We were gonna have to meet this week with our gpses side by side.
Say Wendell, where is that tip jar?
Scott Bordenet, post: 324896, member: 10097 wrote: Yes, the issue was the geoid file wasnt covering my location. I put in a geoid file that did (12a whole CONUS) and everything worked. Thanks to all that read my post and replied. Problem on Friday, solution by Monday morning.....PERFECT...THANKS.
Scott in Indy.
Good to hear, it was the great Glen Borkenhagen who explained it to me many years ago. He knew instantly what was wrong, so then when I did it again I didn't half to call him, at least I knew. :-@
These days you can make your file very large, just try and remember that going too far might cause the same issue, it's not like you can really quantify the area all that precisely.