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.
:good: [with one caveat] I Know that he really knows this stuff....B-)
Did you get a chance to experiment with downgrading to Survey Pro 4.1? I'm curious because Trimble says the board is bad in my Epoch 35 and I never had a problem with this unit until I started using Spectra Precision Survey Pro.
Sorry for the delay, I am going to make a new post later with my findings. To answer your question though, Yes it worked. The unit is now getting fixed in under one minute at 26 miles to the closest broadcasting station. I plan on testing more and will create an updated post when I do.
Downgrading to 4.1 was easy as well. I can provide a link to the download if needed. I also tried using Carlson SurvCE and it worked as well.
Actually I downloaded and installed 4.11.2 Survey Pro
Where you running Spectra Precision Survey Pro 5.0 or greater prior to downgrading to 4.11.2?
Yes, 5.1 or 5.2
GPS Network rover issues. Two step to debug
I'd love to hear if 4.1 or Carlson solved your problems, because I'm seeing the same thing with Survey Pro 5.1.
I'm using the free Florida DOT network at myfloridaGPS.com. I've emailed with Scott Harris, the DOT network guru, a couple of times, but I've never brought up the long "fixed" waiting periods with him because I didn't realize it was unusual for longer ranged solutions. As I understand, the FDOT is in the process of replacing their CORS receivers with newer models that support GLONASS (and new software, too, I think), so when that system goes live I'll reevaluate the performance I'm seeing.
Thanks for the input though. RTNs are weird in that you have so many variables that are out the user's control that it's hard to wrap your head around the source of your trouble ... when it works, it work great. When it doesn't work, you have about 20 potential sources of trouble which are mostly "black box" technology and difficult for a user to troubleshoot. Having you posting here is a big help to those of use trying to make sense of RTNs.
GPS Network rover issues. Two step to debug
Like Gavin says...contact your VRS network admin person. Have them look at what is happening to your rover as you try to log on. They can tell you quite a bit.
I haven't seen any long intilization times with Survey Pro 5.xx EXCEPT for trying to use CMRx correction streams.... that is as they say "problematic"
As far as I know, Epoch 35 receivers MUST use RTCM corrections.
very interested in your findings! please post when you get a chance.
GPS Network rover issues. Two step to debug
I tried Survey Pro 4.11.2 and Carlson SurvCE, both seemed to have solved the problem.
The unit is now getting fixed in under one minute at 26 miles to the closest broadcasting station. I plan on testing more and will create an updated post when I do.
Downgrading to 4.11.2 was easy as well. I can provide a link to the download if needed.
GPS Network rover issues. Two step to debug
Yeah, I'd love to give it a try if you have a link. I think 5.X is Trimble's first major upgrade since buying TDS, and they changed quite a bit, so I supposed it's possible they bugged something up.
Working along the "edge" of the RTN
I'm wondering if some of the problems I'm having is because I'm on the edge of the network, in fact, a good portion of my county is on the Gulf side of a line that connects the nearest CORS. I plotted a few locations where network RTK has worked, and where it has not worked (stays in autonomous), and I found the limit to be roughly 2 miles outside of the CORS envelope (regardless of how far I am from an individual CORS). So, could there be a hardwired limit to how far you can stray from the network envelope? I should probably take Gavin's advice and call the network guru, but this just occurred to me, and I thought someone might know ... I'll call tomorrow.
GPS Network rover issues. Two step to debug
5 is when Trimble got involved. Here is a link to downloads of current and previous versions. I installed 4.11.2, just plug in collector and run the program. My install replaced the existing version. Do know that with the new .survey file format you won't see existing jobs on the collector. You might be able to import them but I haven't gotten that deep into it yet.
GPS Network rover issues. Two step to debug
Sure seems like all the "fixing" problems with my Epoch 35 started when I bought the Ranger 3 with Survey Pro 5.0 installed.
GPS Network rover issues. Two step to debug
If you try downgrading to 4.x please let me know how it works, that is the collector I'm looking at using from here on out (I am currently using a Nomad but not a fan of touchscreen with no full keyboard).
I am getting ready to leave the office and do final testing on getting fixed. Fingers crossed.
GPS Network rover issues. Two step to debug
The downgrade wouldn't be a problem, but Trimble has my Epoch and is replacing the board.
Working along the "edge" of the RTN
I am having same problems with my network rover on fdot network, I have 3 fdot
network towers within 10-15 miles of me, I can get fix in most places except when
I get close to gulf outer barrier islands, using a sp 780 gps and spectrac precision
survey pro version 5.2. I am always able to track 20-25 sattelites at any time.
Working along the "edge" of the RTN
I'm on the FDOT network, too. I think there is a limit to how far you can stray outside of the envelope created by the base stations. However, when I called the FDOT, and asked if they showed any problems on their end, they said they showed I was "fixed" on their server ... but my DC showed "autonomous". Weird.
A patch is to not use a network solution. If you use a single base, you can avoid the problem. If you are using port 10000 on the FDOT, NTRIP, when it prompts you to select your connection, find the one that says "Nearest". I think it will say something like NEAREST_RTCM3 ... something like that.
It should work better past the edges of the network, but you'll lose the advantage of using multiple base stations.