The Base + Rover combo I have been using have worked well UNTIL today.
The only changes made since yesterday have been to the height of instrument.
The Rover is obtaining correction data as seen by the grey bars alongside the Rovers satellites.
However both PDOP and AR ratio are both showing 0 in the Survey Module and the fix is showing SINGLE. Up until today PDOP has generally been <2 and AR values generally >20 and values in the 100’s quite common.
The BASELINE is showing 11,000+ metres wherein it is actually less than 200m.
BASE lat/long hasn’t changed - I use a NSW (Australia) State PM as the Base site.
I am using the latest DEV Reachview, which may be the problem source?
Another thing I noticed this morning on the BASE (without Rover switched on) was that in the “Status View” That it was showing Rover with 15 satellites and Base 0 satellites. Is that correct or does it think it’s a Rover? I’ve never really looked closely before as all had been functioning correctly and giving great results.
The first thing I did was that. The unit has been functioning extremely well until today and the only values changed was the height of instruments.
With it showing a baseline of 11,000+ metres is it possible it is obtaining the corrections from another source? Is it possible to know what the rover is using as its base?
I have reset the Base and reconfigured it. Ill set it up again in the morning and see what happens. If the same I’ll grab the system reports.
I can’t answer all of your questions however I can confirm that on your ReachRS+ configured as the base, the satellite count for that unit will show its satellite count as Rover, so yes the behaviour you describe is consistent with my experience with ReachRS+ units in RTK mode.
Also, whenever I get myself into a spot of bother and things don’t behave, I always go to the settings page and ‘reset settings to default’. I do this for the rover (and base when in local RTK mode) and then start again. Usually, I’ve tweaked a setting somewhere and I don’t pick up on it, so this is an easy step to take. It nearly always fixes my problems.
I have reset the 2 units and reconfigured. Will see how they go in the morning.
If they are not functioning correctly I’ll re flash/image the Edison chipset.
Using a DEV release image I would expect to run into trouble at some stage but after they were functioning so well its a little frustrating to have to trouble shoot.
Further to this problem I feel that the BASE unit’s image is a little “flaky”. The power charging and reporting seems incorrect. I noticed this yesterday and I verified this overnight. Charged for 10 hours - report said 100% charged. 10 minutes latter said 50% charged. 30 minutes latter <30%.
The ROVER uses the same charger. It shows 100% charge and holds that charge for a long time.
Base altitude deliberatey left blank as I wasnt confident of the “computed” conversion I had for that point and thought I had read somewhere that the Base would resolve that itself. As I dont rely on the heights I’ll use it again.
I have upgraded 1 unit which I had at home to grab some log files. I haven’t upgraded the base yet which is the one giving the power issue. Will do so in the morning as I wish to use them tomorrow.
