I followed the instructions shown in a dedicated Rami Tamimi tutorial for RS3 and all went well except for saving points. I could not save any point. The device was recording and I had 30-40 satellites, open view (no canopy) but the Save button was greyed-out saying “Waiting to fix …” for more than 14 min, so I gave up. I tried twice on two different days and locations, but no success in saving points. I tried with both, tilt compensation mode and without it, still no avail … Any tips?
P.S.: I have screenshots of the settings etc, but see no option to attach them to the message.
What was the solution? FLOAT or SINGLE? You won’t get a FIX without a good connection to a base receiver. If you do want to record a point anyway, in the survey screen where you would press to record the point, press on the gear icon and uncheck the ‘FIX Only’ setting.
Hi Gabriel,
thank you for your quick reply, much appreciated.
I’ve been doing everything it SINGLE mode, so bad connection with the base can be ruled out.
As for the “force-recording” the point; in the survey screen I see a Tools icon (I guess this is what u mean by gear icon), but I only find New data, Inverse, Traverse, Localization, and Base shift options. I was playing with other icons too, but nowhere I could find the uncheck “Fix Only” option …
Any other suggestions?
It’s when you’ve pressed on the blue plus button to add a point. Just beside the pole height button, there’s a gear icon. In there you will find methodology for point recording, including the FIX Only setting.
Ok, now I think I know which icon you mean (I took all possible screenshots).
But let’s say I can force-record a point, that’s just a bypass. Why it doesn’t want to record a point like in the tutorials?
That option exists so when we work in real-time differential positioning (i.e. RTK), we can block recording a point if we lose the best possible position solution momentarily (losing internet connection, losing radio signal with base, under trees, etc.).
If you work in SINGLE, your precision is at best 40-50cm or so with an RS3. If you need more precise and accurate measurements, you’ll need to either connect to a third party correction service or have your own static base to connect to (or work with long observations in static mode then post-processing with a PPP service).
Yea….should never collect in single unless you plan on doing PPK and are logging at the rover (and perhaps base too). Single in real time May get sub-meter but no guarantee. I am thinking that you were intending on being connected to your base to get corrections. If you are single, you are likely not connected to your base (via Lora or internet).
The FIX only setting can be found under the gear icon after tapping on the plus sign in your project. After disabling this option, Emlid Flow will allow you to collect points even in SINGLE.
So let me understand, the FIX option is only meant for when connected to a base or correction station, and when we don’t have either we turn it off?
The collected point will have of course low accuracy and needs post processing to improve it’s accuracy.
Thank you also for the screenshot, it makes the communication much easier. And now I see the icon that allows image uploads/attachments (a clip icon would be easier to find).
Correct. The terms FIX , FLOAT, and SINGLE refer to how the receiver is determining it’s position.
SINGLE means that the receiver is just using the gps satellites themselves.
FLOAT means that the receiver is using the satellites AND is connected to a corrections network of some kind BUT has not resolved ambiguities enough to determine it’s position to centimeter level.
FIX means that the receiver is using satellites AND is connected to a corrections network of some kind AND has resolved ambiguities enough to determine it’s position within centimeters.
So. You see that If you set up your receiver in SINGLE mode (not receiving corrections from a network or base), but in your point measure settings you have FIX or FLOAT selected as a requirement. Your receiver will sit there for ever “waiting for fix”.
We could make this a feature request / suggestion for the Emlid team to make a tweak in Flow. If a user does not have a correction input source set and has float, or fix selected in the measure settings, Maybe the app should display an alert that “a fix or float result is not possible with current settings”
Yea, indeed, when I found out the reason why I couldn’t record the point I was wondering why there isn’t any warning or automatic switch … Would be a good upgrade indeed.
I see how this additional warning about the FIX solution would be of help. Thank you for bringing it up! I’ve noted it and will add it as a feature request.
There is some times, under heavy foliage, FIX is not stable. It’s come and gone. Any attempt to save is loose because every time the GNSS status change the record clock is reset.
Could be possible to aggregate just the times the FIX is acquired, and do not store in Float or Single?
Currently, it’s not possible to save the actual averaged position when the solution changes or to ignore the FLOAT and SINGLE solutions during averaging.
But I’ve noted your feedback and will pass it on to the team. Thanks!
