Fix with GPS and Glonass does work and in our testing it is more robust than with GPS only, just don’t forget to disable Glonass AR when working with a different type receiver, Glonass still can be enabled.
Should be a few weeks. We are pushing it really hard, but there are lot’s of things requiring a rework. New wi-fi settings, new logging and new image are yet to be finished.
Completely rewritten backend and frontend, new looks, removed most advanced settings by setting them to an optimal value, only needed settings left and made user-proof. Several layers of protection to make it impossible to kill the ap with wrong settings. New update and packaging mechanism to ensure safe and consistent delivery of updates. Built-in maps and dashboard with detailed status of RTK. Dropped the buggy Intel wi-fi setup script and integrated network settings in the app. Stream statuses (very important for NTRIP to see if connection succeeded). Merged rover and base modes, now possible simultaneous operation in rover and base modes on one device. Different options for base coordinates: average single on boot for t minutes or average fixed position from NTRIP for t minutes and start corrections after that or manual value. This is not a full list of changes, there are many more.
Regarding the rover not booting with active base we were not able to reproduce the issue on the image v1.2. If you know how, please let us know.
@antonio.arns1 Antonio, overall fix time will depend on the surroundings and satellite geometry. Average time in our testing is at 3-5 minutes in GPS+GLO, but it can be longer in less favourable conditions. If you are still seeing problems, please reply to my message in your topic:
@Andreas_Ortner I have answered to you in your thread.
@Multirotorcraft Let’s get to the bottom of the issues in a separate thread.
I don’t have problems getting a fix, but i’m interested in the Glonass-Setting with two different receivers you mentioned. What does “more robust” mean? Does it really make sense to enable Glonass (with 5Hz only) if it couldn’t be used for AR?
@dirkkoller It does, as the sats are still used. I had tracks where adding glonass sats with AR off improved things.
thank you for the update. It sound promising!
It sounds that this will improve the use of the system. We will all see if it also improves the fix mode…
thank you and best regards
Just a note about using NTRIP corrections, baseline lengths are usually longer than they should be so your corrections are no longer as accurate. We use NTRIP, VRS and local base stations and by far the best setup is one of our own base stations always within a mile. Anything longer than 5 miles and its time for static GNSS sessions.
The introduction of an RTK product to a consumer market was always going to be interesting …
Most of the users are expecting a black box solution when in practice achieving RTK results requires a good understanding of the gps and differential gps principles.
I hope that the support load I’d not going to overwhelm EMLID …
Your spot on. When I first got my Reach I knew very little about GNSS aside that RTK used local corrections from a base. I was indeed hoping for a black box solutions, but quickly learned a whole bunch of things about GNSS, who knew they could be so complicated
On the flip side every time I mention high precision GNSS I am given a lecture on how GPS (not GNSS) works.
totally understand how you feel.
when I tell people that A-GPS is faster because we can download the almanac from the internet instead of waiting for the 12.5 minutes for the whole NAV message to be received, they say A-GPS is actually based on cell towers that can triangulate your position better than GPS. Don’t even get me started on GNSS. facepalm
Hi my topic " No fix No float using 3dr" was out, so I update to reachview 0.4.9, and nothing change. Yesterday I try to make Fix but I past 2 hours and don’t get fix or float. I think my problem is with gps signal level, because just one or two bars get above 45 Snr level, my gray bars dont drop at any moment. I attached one picture of my hardware configuration, please some one can help me. Thanks
Yes, only two satellites above 45 does not sound like a good reception.
The hood may be a bad placement for the antenna - big part of the view is obstructed by the windshield.
If the car is running it may also produce RF noise.
Try to make two ground planes for antennas and put them on tripods (or just sticks) a little bit higher.
4 weeks are gone since i started the thread. You said it would take you a few weeks.
can you please give us a estimation when it will be finshed? A week or a month ?
Will there be one big release or a few small ones?
thank yiou and best regards
Is there any information on time when the new software will be done?
Are some parts of the problem resolved?
Is there anything we can test?
- August: I come up with a problem
- August (3 weeks later): promise that there will be a solution in a few weeks
18.September (7.5 weeks after first email): question about progress with now response.
6.Oktober (10 weeks after first email): this email
I would be pleased if I can get an answer. This there any hope that before the winter begins is a new version available?
Thank you and best regards
I need to be clear here, there was no promise to make the workflow that you want work. Yes, we are working on the new app that should be released soon, but it will not help with positioning in the forest or make float as precise as fix. There was no actual problem report in the first place.
If you can post raw data logs of the situation when you are not getting a fixed solution we can certainly look at them and try to find the cause (As we did when you were no getting fix from NTIP).
Same for us here too!
Unable to make it work under daily work. Trying to make it work on known base coordinate is a pain… never stay fixed more than a couple of minutes or worst, never get fixed! We bought two kits to be able to replace our old Trimble kit… I just spent many dollars and now that Emlid Reach RS are only paper press!
Lost a lot of hours testing and learning… working together with a surveyor, comparing results and keep trying to find a workflow that will be stable… a total fail! We all know that time is money, so I evaluate that the final cost is just to ridiculous to be written here.
It’s frustrating for sure but it’s more disappointing!
Conclusion here: Emlid ReachRS is simply not a professional tool. You can spend money and use it as a learning tool but not more! Don’t even think to be accurate with that over the time. You will bust any job that need to be geodesic. Nad post processing with a unstable algorithm is no more professional.
Positive points: Emlid team is working hard to give technical support.
Sorry to hear you’ve got issues with configuring RS and getting fix.
Our team and our community indeed work hard on assisting users who just start with Reach and need help with setting up.
You can share the configuration of your base and rover and send us logs and we will be happy to look through them and help you to find stable workflow for you application.
I just sent a email with our logs.
Waiting for a reply
Never get reply so… can’t update the situation
So what version of Reachview are you running?
RV2.9.3 has proven very stable. and delivers a good real time kinematic solution for me.
We never got something stable under 2.9.3 and we tested with 2.10.0.
Something is going wrong for sure with my settings…
Post screen shots of your rover set up
RTK settings and Correction input