This is a rather lengthy update to a previous thread posted here:
[msg=187647]GPS Network rover issues. At my wit's end[/msg]
I finally did more testing on this issue. I initially tried connecting and getting a Network Fix at my house, which is 26 miles to the nearest broadcasting station and a location where I have had trouble getting fixed. At my house I only tried quick connections without shots stored only to see if I could get fixed. I was able to connect with the Epoch 35 in under 1 minute and sometimes almost instantaneously using both Survey Pro 4.11.2 and also using Carlson SurvCE. The connection was not as quick as when using the Epoch 50, but it was getting fixed none the less.
This was the same location I had previously tried using the Trimble R8 which connected instantly. This was also the same location I had connected using a Topcon GRS-1 that would take 5 minutes plus to fix, and sometimes no fix at all. Also, the GRS-1 would have different results on a point I have set in my backyard, varying as much as 0.50' from the point.
I then tested out the Epoch 35 & 50 on a site where I was having troubles getting fixed with both the GRS-1 and the Epoch 35, as mentioned in the previous thread. This site is 18 miles to the nearest broadcasting station. The 50 was quicker to connect but the 35 was able to connect in under 2 minutes.
Lastly I tested at a site that is 21 miles to the nearest broadcasting station and took comparison shots and made notes of connection times and reconnect times after resetting or flipping the rover upside down to disrupt fix. This was done running TDS Survey Pro 4.11.2 and later Carlson SurvCE on the 35. Here are my results
Epoch 50
TDS Survey Pro 4.11.2 on Trimble Nomad 900
Attempt 1
Showing 13 satellites on receiver display
0:20 seconds initial fix (but only showing 7 satellites)
0:15 seconds to reconnect
0.04 horizontal accuracy displayed
Attempt 2
0:25 seconds initial fix (but only showing 7 satellites)
0:15 seconds to reconnect
Attempt 3
0:30 seconds initial fix (but only showing 7 satellites)
Epoch 35
TDS Survey Pro 4.11.2 on Trimble Nomad 900
Attempt 1
Showing 13 satellites on receiver display
1:37 minutes initial fix (showing 13 satellites)
0:30 seconds to reconnect
0.04 horizontal accuracy displayed
Attempt 2
1:55 minutes initial fix (showing 13 satellites)
Attempt 3
2:30 minutes initial fix (showing 13 satellites)
With this connection it showed precisions of 0.04 but stayed on Network Float for the last 30 seconds of connection time.
Epoch 35
Carlson SurvCE on Trimble Nomad 900
Attempt 1
1:20 minutes initial fix (showing 13 satellites)
0:20 seconds to reconnect
Attempt 2
0:30 seconds initial fix (showing 13 satellites)
I will list the coordinates of the shots I took with both the 50 & the 35. Same point for both but different rods.
Epoch 50
2020317.321753, 1595988.930500 shot time of 3 minutes (180 epochs)
2020317.319269, 1595988.926896 shot time of 5 seconds (5 epochs)
Epoch 35
2020317.257647, 1595988.931890 shot time of 3 minutes (180 epochs)
2020317.267284, 1595988.941118 shot time of 5 seconds (5 epochs)
The largest difference between the two is 0.06' but using two different rods might factor in a little. I shot the same point using Carlson as well but had the wrong State Plane conversion in the collector and chose not to include even after conversion.
Sorry for the long post but I wanted to show my results. Hopefully this might help someone. If anyone has any questions I will be glad to answer them.
Hi Pencerules, thanks for posting your results. I'm just curious which version of SurvCE did you use to connect to the Epoch50? The SurvCE (v2.62 latest) I used won't connect with Epoch50 via Bluetooth successfully, I noticed that the LCD display in the Epoch50 changes from A / 10 (A = Autonomous, 10 = Satellites) to this " -/-- " and there are no GPS readings appearing on the Monitor Skyplot tab either. All my GPS configuration settings were in order and Epoch50 is supported according to SurvCE's Release Notes so im quite confused why it appears not.
The Log Raw File command in SurvCE is also not supported for the Epoch50 if you want to log raw static files.
I switched to using a Ranger-3 data collector with SurveyPro v5.20 and everything worked fine.
I did not hook up the Epoch 50 using Carlson, only the 35, but I do think they are setup the same way through SurvCE. You have to connect bluetooth to the receiver and connect a cable from the collector to com port 2 on the receiver. It will also disable the display readout on the receiver.
The version of SurvCE I am using is 2.61.
I also want to say for those who have not read all of the previous post, the reason for showing results with Survey Pro 4.11.2 was that I could not get a Network Fix (or it would take an exceedingly long amount of time) using Survey Pro 5.2
So, what conclusions can you make? I'm sorry I don't quite follow...
My post was trying update what I had found by downgrading to 4.11.2 and using Carlson SurvCE. Trimble changed Survey Pro in version 5 and it appears caused trouble in the ability to get a Network Fix using an Epoch 35 (Novatel board inside). Using an Epoch 50 (Trimble board inside) worked fine using Survey Pro 5. I don't know if this was intended by Trimble or not, I am merely showing my results and hopefully helping someone else in my situation.
My Epoch 35 is back with a new board installed. We tested it in the dealers parking lot, but didn't see much improvement. It would fix, but it still takes way too long to fix to be productive. We didn't have a controller with 4.11 installed on hand to try, but it sure looks like the 35 doesn't like to play with Spectra's version of Survey Pro.
In case you need a download of 4.11.2 and didn't see the link in my previous thread:
I hope this works for you. It sounds like you're in the same situation I was. If I can answer any questions I'd be glad to help.
If they can't resolve the problem and I get stuck with the receiver I will go that route, but for now I have an Epoch 50 loaner from them that works great.