I am having trouble getting a network fix using the Ky DOT RTN network. I have posted once before about similar issues but thought that different equipment would remedy the problem but it hasn't completely.
My issue is when I am 10-15 + miles from the closet broadcasting station I have trouble getting fixed. It can take 2 minutes up to 1 hour (if it ever does fix). My accuracy slowly drops showing Network Float, sometimes will even drop down to 0.04' vertical and horizontal, but will not fix.
I have used a Topcon GRS-1, and two different Spectra Epoch 35 receivers. No canopy, severe clear, and 15+ satellites do not affect it, nor does time of day. Always great cell signal. Always using same internet provided (At&T). Tried at different job sites as well. Turning off Glonass did not help. Clearing NVRAM did nothing as well.
I have however used a Trimble R8 and a Spectra Epoch 50 as well, and both worked flawlessly, connecting in under 20 seconds for Network Fix.
The network I am using is a Trimble VRS network, and the R8 and Epoch 50 both have Trimble boards inside, but the Epoch 35 has a novatel board.
Has anyone else had this issue or anyone have any ideas of a solution?
Am I restricted to only using a Trimble board on a Trimble network?
Try disabling SBAS (WAAS) corrections from your rover if it permits this type of correction. I've learned that newer versions of the Trimble VRS processing software might throw out the rover's NMEA position string if WAAS corrections are enabled in certain GPS receivers.
Thanks for the response.
SBAS tracking is turned off on the controller (running Survey Pro).
Sounds like you have a mount point issue. Both the Topcon GRS1 and the Epoch 35 are not compatible with CMR, which is normally one of the main mount points that a Trimble Network would put out. Try connecting to an RTCM mount point and see if you get any change.
Sometimes I have to turn off glonass to get fixed when they're close to gps sv's, but I'm not using a network, just a base & rover (topcon). It only takes a minute or two to find out, just turn off glonass and see if it fixes.
oops, didn't see you already tried that, I don't have any other suggestions.
My dealer told me this is a surveypro problem.
If, as the OP says, the unit eventually fixes (after 2 to 60 minutes) doesn't that mean that he has the proper settings and data format set? It seems to be an issue of extremely slow fixes rather than a settings problem. FWIW, I have a Old HiPer Pro that I use on a RTN, with RTCM 2.3 or CMR, and I also see extremely slow "fixes" past 10 miles. I figured that was typical for long distance fixes. Should I expect better? BTW, this is also with TDS Survey Pro.
I have seen this with Topsurv as well as Survey Pro. Survey Pro is also what I used with the Epoch 50 and it worked flawlessly (same collector as used with Epoch 35).
Change the mount point. It'll work.
Have also tried that with no success. I tried using the closest station and the next closest stations with no luck. Have also tried using VRSRTCM 3 as mount point. Tried with both the GRS-1 and Epoch 35's.
I have changed the mount points and that did not help my problem. I will talk to the network administrator and see if they have any insights. This problem is not very high on my priorities at the moment as I rarely use that system for network RTK.
> Have also tried that with no success. I tried using the closest station and the next closest stations with no luck. Have also tried using VRSRTCM 3 as mount point. Tried with both the GRS-1 and Epoch 35's.
I thought the mount point would be your problem too. I would try installing Survey Pro 4.11 and connecting on RTCM 3...that's what I'm running on the NC RTN with an epoch 35 and have great results.
Wes
I have an Epoch 35 and Ranger 3 running Spectra Survey Pro and have the same issues. Most days it will hardly fix at all on the Ohio ODOT network, it just sits there and floats even after the residuals get down in the hundreths. I took it to the shop and they couldnt get it to fix either. They even pulled out another Epoch 35 and controller they had in stock and theirs didn't fix either. I have an Epoch 50 loaner while they look at my unit in and I can hardly get through the setup before it fixes. I suspect it's the Spectra Survey Pro software as the problem has gotten worse as I've went through the updates since version 5.0. I used to rent this same Epoch 35 from this shop before I bought it and it worked flawless with the TSC2 and old TDS Survey Pro. It's been in the shop for over a month now, so we'll se what comes of it.
Kelly
I had somewhat of a same experience Saturday. Standing in wide opens spaces and not initializing. I looked at mission planning and knew I would have a few bad times before noon. As it turns out, the "bad times" were almost all of Saturday morning. I did get several initialzations but the results were all over the place. Sometimes 2, 3 or 6 feet difference from the previous shot. Here's a shot from mission planning for that day.
Also, maybe part of my initialization problem was that I was 21 miles 'outside' the network. 🙂
Either way, I just wanted to say that after 12:00 noon, everything worked like a charm! You can see from the planning shot that the DOP values were much better afternoon than in the morning. I was staking line in a wooded area and had no bad initializations after 12:00. At 5:00, I rechecked a shot I got at noon and it was fine.
I don't know if this is what you are experiencing but maybe take a look and mission planning and keep an eye on the best times to be out there.
Not that it makes a difference but I was using a Geomax network rover on the WisCORS network.
My problems were on different days, through all hours of the day, on different job sites.
I am going to try using Carlson SurvCE to see if it remedies the problem. I also might downgrade to Survey Pro 4.1 as well checking to see if that works.
I am not to hopeful though due to the problem happening with Topsurv as well.
GPS Network rover issues. Two step to debug
Have done step one. I was the only one with issues.
Step two has also been done. First dealer with GRS-1 could not find solution to problem, so it was returned. Second doesn't have a solution either.
GPS Network rover issues. Two step to debug
I recommend that you take gschrock up on his offer for you to contact him directly.
I think that he really know this stuff and will send you in the direction you need.
GPS Network rover issues. Two step to debug
I will be trying Carlson SurvCE later today and possibly Survey Pro 4.1. If those don't help I will probably email you in regards to a previous post of yours.
Thanks for the help.
