we are using emlid RM2 for the past few years and It works well but recently we have faced one weird behavior in which we found a very high no. of triggers in events.pos file as compared to the actual no. of images.
can someone please resolve the issue as it’s essential for us and urgent otherwise, we will need to recapture the data which will cost the additional cost.
There are many red bars that mean cycle slips. They appear when the satellite signal disrupts, or there’s substantial interference nearby. You can also see that all observations have low SNR that oscillates periodically.
All these factors show us that Reach M2 is affected by strong interference noises. They are usually caused by the drone’s electronics. You may need to reconsider your hardware setup to avoid this. I’d recommend isolating Reach from all potential interference sources and wrapping it with aluminum foil. You can read our guide to find out more about it.
Hi All,
I have same problem…
when I doing ground test… the number of event and image is same…
but when, I’m doing test flight the number of event and image is difference …
the number of image is 104 photos… but the number of event is 3270 … this is very strange …
Thank you for the files! I’ve examined them and see that this number of events is caused by invalid time marks in the log. The log includes 117 proper time marks and 3153 invalid time marks.
Hence, Emlid Studio outputs 3270 events (117+3153). It’s worth showing to the devs, and I’ve already passed this data to the team for further investigation.
As a workaround for now, I’ve fixed your RINEX log. I removed all invalid time marks from the log, and post-processed it in Emlid Studio. Just in case, I’ve attached the rover log and pos files here in the zip archive.
These bars mean cycle slips that appear in the log when the signal is interrupted.
Please share the photos of your hardware setup, so I’ll be able to check if there are interference sources nearby. Furthermore, please note that Reach should be isolated from all potential interference sources and electronics to reduce the interference impact. You can read this section of our docs explaining this matter.
but yesterday we are doing test flight again… and we change settings the update rate is 10Hz and logging interval is 1s… and the result so far is good…
Indeed, changing the logging update rate helped to eliminate invalid time marks. So, you can leave these settings.
However, I’d still recommend you isolating Reach from potential interference or wrapping it in aluminum foil. The logs’ quality leaves much to be desired, despite the fact that I obtained almost 100% of FIX in both flights by setting Elevation mask to 20 and Glonass AR to Off:
Aluminum foil is indeed a good way of isolating Reach M2.
It’s quite hard to share exact photos of a perfect setup that will suit in your case, because each setup is unique. However, following our recommendations regarding Reach’s and antenna placement usually helps eliminate interference issues.
