The send corrections via 2 channels at the same time was on my WISH LIST, for those times when internet is spotty or unsure if LORA will reach…being able to jump back and forth without having to return to the base is HUGE. Thank you!!!
Hi, here we use 10 hz to georeference radar traces (GPR) when doing helicopter airborne radar on glaciers. This is due to the speed of displacement and the density of points required. And I imagine that when done by airborne you must use up to 20hz. For most of the topographic surveys it is enough with 1-5 hz, but I do not like that they lower the performance of the equipment.
If anything, if the plan is too sacrifice a feature that has been on the product specs since day 1 in exchange for Dual Channel functionality (which the MAJORITY may want as everyone is giddy about it right now), then EMLID please at least make this a choice to TOGGLE between the 2 features. i.e Dual Channel OR 10Hz Update Rate. Please just dont KILL it altogether, even if many don’t use or need the feature. I don’t want to argue exactly who why needs 10hz etc or not… the specs advertised having it. IIRC at the start i think 15Hz or maybe 20Hz (cannot remember exactly) was also in the specs as a future feature to be unlocked… which never did happen?
FWIW, I’ve also noticed the specs for the Emlid receivers over the years have been edited / removed.
I see why they have not removed 10Hz from the M2, because it’s normally used for fast moving rovers (i.e. drones, aircraft, vehicles, robotics etc), not just walking point to point using a rover pole. Might not remove ot then???
I am NOT for what I am about to say, but going to put it out there anyways… but I see this as a missed opportunity to sell a NEW model that has DUAL CHANNEL capability if it is something very desirable. But then again, hope a new model has a ton more features anyways as in earlier discussions… i.e. L5, AR camera, remote laser distancing (EDM) etc etc. Other brands have already had all of this for quite sometime already.
EDIT: The worst thing I resent is when firmware and/or software is altered in a way that REMOVES features that have been relied upon for so long, then all of a sudden taken away with a mere update where there is no option to turn back. Wether other users agree or not.
But then again, its your choice to update.
Removing the 10Hz option for RS2/RS2+ was not an easy decision, and if there was a better way we wouldn’t do it. The chip firmware is evolving and improving, but that takes more processing power. We had to make a call whether to freeze things “as is” or to strive to improve the accuracy and reliability of positions by sacrificing some update rate, we chose the latter. With all the upgrades the chip is unable to output 10Hz anymore. We do not see any applications except for drone mapping where this rate is actually being used in our receivers, we send position updates at 5Hz to the user interface anyway, but the majority of our users could benefit from the improvements in positioning.
Yes, it is always painful to have to lower a number in the specification, but we wouldn’t be doing it if we didn’t believe that it would be for the benefit of the vast majority of applications. Some number will be lower, but the product will perform better.
Just to make it clear, this is not related at all to the dual base corrections output. These two changes are just being released as a part of one update, but are not affecting each other.
Understood.
But will the M2 retain 10Hz functionality being it mounts to a fast moving rover for the most part? i.e. Drones, aircraft, vehicles etc.
Thank you @igor.vereninov
All the drones I have used receive at 1Hz so this is a non-issue. The last time I ran 10Hz was vehicle-mounted at 20-30mph and a test against 5Hz and there was no benefit found.
Hmmm… kinda weird, as this seems to be EMLID’s biggest userbase?
I’d be willing to bet that actual connection to the drone is no more than 30% of Emlid product use in the wild. Even for me flight is about 4-5 hours a week and rover usage is about 10.
As a surveyor primarily using the emlids to fix control ( static ) and topo kinematic. The Accuracy and precision of the individual captured points matter far more to me that the update rate. So I welcome this change
Hi guys,
We understand that the option of 10 Hz comes in handy in drone surveys, so we didn’t release 33 beta for Reach M2. We’re still considering all the possible solutions on how to apply the new firmware for M2 with the least possible effect on its operation.
While their may be an advantage in some use case that I have not found the Mavic 3 Enterprise on receive correction at 1Hz and the Autel Evo II RTK at 5Hz. I am not aware of a drone besides a custom kit with an M2 that can receive above that. We have zero issues with the amount of corrections we receive.
For applications such as the use of the RTK Camera app, a frequency of 10 Hz proves to be very useful.
2 posts were split to a new topic: Incorrect cut value during stakeout with 33 Beta 1