I've noticed on the tracking page on the R10's web gui, that several of the check boxes are not checked. GPS L2C and GPS L5 as well as one of the GLONASS and Galileo. I have to re-enable every time I boot up the R10. Are these constellations supposed to be disabled by default?
| ?ÿ | ?ÿ | ?ÿ | ?ÿ |
I have wondered that as well. But, I will say that it doesn't always reset the tracking list, but sometimes it does. I don't know exactly what causes it to change. Maybe it is dependent on the firmware version. The Alloy definitely seems to keep the list after power down?ÿ
In my opinion why not just have them all on by default? Memory is plentiful.
One of the problems with Trimble is that there is no direct contact between users and the company, you have to go through the dealer network.?ÿ
For example, I recently asked the RTX contact why Beidou is not being used in post processed RTX (nor in real time RTX), even though the web page for RTX says it uses Beidou. Here is the answer I got...
From a "better signal" stand point, RTX will select the best options available for trilateration in your current position, aiming for better accuracy.
Case you're and end customer and still need specific information on your device operation, please contact your dealer. If you are the dealer, you should be able to request technical information from the geospatial division.
I assume the "Case you're and end customer" should be "Because you are an end customer""
I'm wondering if using all these constellations degrades the solution a little bit in open skies. Maybe there is a bit of systematic error between the different constellations. Sometimes our solutions in open skies aren't as good as they should be.
Seems weird that GPS L5 would be disabled. I thought L5 was supposed to be the better signal for canopy work?
I have noticed an issue with the R10 (using Survey Pro) getting a bad fix in canopies. It's almost always an error of about 5 feet... I'll be staking to a calc point, get a fix that is 5 ft away from where I am actually standing and then after a few epochs it will jump back to where it should be. Sometimes it will jump back and forth every few epochs until I reset ambiguities. I never had this issue with my old 2007 Topcon HiPer Ga's.
Have you tried to connect to the R-10 directly and not through Survey Pro? You can connect via the receiver wifi and see all kind of settings. Perhaps there is something goofy going on there. FYI I have never been a fan of Survey Pro and wouldn't surprise me if some of your issues are SurveyPro related.
N10,000, E7,000, Z100.00
PLS - IL, MO, AR, KS, MN, KY
Access controls that from the survey style and configures the units as you start the survey.?ÿ
Have you tried to connect to the R-10 directly and not through Survey Pro? You can connect via the receiver wifi and see all kind of settings. Perhaps there is something goofy going on there. FYI I have never been a fan of Survey Pro and wouldn't surprise me if some of your issues are SurveyPro related.
yeah I connect to the R10's web gui through its wifi connection.?ÿ
I was about to type that and saw there was a second page. +1
Always be sure the base/rover settings are what you want in your survey styles. e.g. if they're turned off at the base they won't do any good at the rover.
After I thought about this I realized that I now almost always start the base using the webui, not access. I think using access may reset the tracking. Not using access leaves the tracking as it was the last time it was used, so if I had checked all frequencies/constellations then it should stay that way. And I think it does.
Since I rarely (almost never) use the radio on the R10 for RTK, I find it easier to always use the webui. We use NTRIP over cellular. The only time I would use the radio would be a very small area, and even then I can configure everything easier over the webUI than using access. We do use radio when doing woods check points, set a base on the vehicle roof nearby and then survey in to the woods. Also, I can connect back to the R10 over cell to check battery, change anything, etc.
I've noticed on the tracking page on the R10's web gui, that several of the check boxes are not checked. GPS L2C and GPS L5 as well as one of the GLONASS and Galileo. I have to re-enable every time I boot up the R10. Are these constellations supposed to be disabled by default?
?ÿ ?ÿ ?ÿ ?ÿ
Carlson was doing this with GLONASS on me for a while.?ÿ Finally called to see what was up and it ended up being a bug in the software which they patched and worked fine after that.
One of the problems with Trimble is that there is no direct contact between users and the company, you have to go through the dealer network.
That isn't confined to Trimble. It is the biggest issue that I have with Topcon as well. There are functions in Magnet that I cannot find anyone that is able to explain. Our rep is good, but they are at the mercy of the next level that they talk to.
This is where Microsurvey, Carlson, etc have an advantage. I call with a question about Star*Net, I talk to people that care about their product and how it is perceived. There is never a deflection. They are honest about what they know and if they don't know, they can go talk to the coders and developers. The service is extraordinary. You cannot get that with layers in between you and the real information.
A few days ago I sent you a PM regarding our experience with BeiDOU tracking ok but not in the RTK fix - not sure if you saw that. Also, our system needs to run RTCMV3.2 in order to get BeiDOU into RTK.
I did not see the message (still don't). If you could resend I would be very interested in what you have to say. I was able to get Beidou in the RTK fix over cell using CMRx.
Here's what I messaged:
We have clone RTK equipment since 2013 which uses Trimble hardware (BD970) and firmware, running on SurvCE DC software (V5.03). A couple of years ago, via our supplier, we had a GNSS update in both the firmware and the software (SurvCE 3.X to 5.X in order to get RTCMV3.2) to enable us to use BeiDOU in RTK. We did all the updates remotely (we are far away, in the SW Pacific islands), however, after successfully going through all the updates, including that the message type on both the base and rover was RTCMV3.2, I could see that although the base and rover were seeing BeiDOU, it was specifically cut out from RTK. Our supplier suggested that we ??manually? start the base, which I understood to be the hard-buttons on the base receiver (which is what we normally do) and I tried a number of times but still no remedy. So I took the equipment to our supplier (international flights and a couple of days of road travel) ?? turns out ??manual? start of the base is BT connect to it and SurvCE sending the RTCMV3.2 and other settings to it, and then RTK BeiDOU is all good at the rover, a two minute fix. I found this very odd, but it works, and is our SOP.
It MAY be that Beidou is not used if started from access, or maybe not used over a radio link (not enough bandwidth). I will do some experimenting during these down times to see exactly what happens under different scenarios. I have an 8 acre test site with two fixed pedestals here at my home/office, and PLENTY of time on my hands, at least for now. Hopefully that won't last (the time on my hands) too long.
The next 4 days are supposed to be nice weather here, but at at least one of those days I am heading for the mountains for a nice drive, I have barely been off of my property for 16 days now.