Welcome › Forums › General Discussion › OpenMMS Version 2.0
- This topic has 11 replies, 7 voices, and was last updated 2 years, 3 months ago by Anonymous.
-
AuthorPosts
-
-
February 28, 2021 at 10:25 AM #919AnonymousInactive
Hi, I thought maybe having a topic where we can discuss things in 2.0 version of the project would be good!
First of all, I am really thrilled about this part of the project. It will potentially attract a lot of attention!
Equipment that is listed is cheap and more and more people will be able to get hands-on hardware!
That said, I will try to get my hands on the hardware and participate if I can.Ryan, could you list all the equipment that you plan to use? e.g. which computer unit?
It is a good idea to use a built-in IMU from the LiDAR sensor, and I think it could be a good idea to leave some space for external IMU if this proves to be not sufficiently accurate.
Brs,
Luka -
March 1, 2021 at 10:28 AM #920Ryan BKeymaster
Hi Luka,
Thanks for starting this topic! I am very pleased to see the community’s response to and interest in the OpenMMS v2.0 R&D. For complete transparency, I am in the final stages of my geomatics graduate studies work at UF which occupies >90% of my time and energy, so progress on the v2.0 R&D is going to be slow for at least the next few months. That being said, here are the planned initial R&D tasks:
1. Modify the existing aluminum case design of v1.3 to enable the installation of the Livox Horizon lidar sensor. Thankfully the wiring of the Horizon is practically identical to the Mid-40 so connecting the Horizon to the internal circuitry requires no additional modifications.
2. Modify the existingopenmms_controller_livox.py
to enable the collection of the raw IMU observations from the Horizon sensor.
3. Update the respective lever arm offsets for the new lidar sensor and perform an in situ boresight calibration for the lidar sensor and Sony mapping camera.
4. Collect and process datasets (using the existing OpenMMS post-processing workflow) to verify the accuracy and performance of the new Horizon lidar sensor.These preceding steps will establish a baseline accuracy and performance reference for comparing and quantifying the proposed trajectory solution produced using the Livox IMU and the Emlid GNSS sensors.
5. Temporarily install the Emlid Reach M2 GNSS sensor and Tallysman GNSS antenna on the outside of the OpenMMS case and estimate the respective lever arm offsets.
6. Operate the Reach M2 as a standalone sensor (using the ReachView app) and collect raw GNSS observations at the same time as collecting data using the OpenMMS sensor (i.e., GNSS + IMU observations from the Applanix APX-18 and lidar + IMU observations from the Livox Horizon).
7. Explore using NovAtel’s Inertial Explorer Xpress GNSS-INS post-processing software to generate a trajectory using the raw GNSS observations from the Reach M2 sensor and the raw IMU observations from the Horizon sensor.
8. Compare and quantify the new trajectory against the APX-18 reference.
9. If the suitability of the new trajectory solution is confirmed, then the next round of R&D will focus on the hardware integration of the Emlid Reach M2 GNSS sensor within the OpenMMS case and electronic circuitry.If the IMU observations from the Livox Horizon prove to not be of satisfactory quality, then other standalone IMU sensors can be explored using a similar approach.
Also… finding, leveraging, or developing a robust, rigorous, open-source post-processing GNSS+IMU software solution is a big goal of OpenMMS and will always be kept in mind within the v2.0 R&D. Any help from the community on this goal would be greatly appreciated!
Thanks for reading,
Ryan
-
March 26, 2021 at 12:44 AM #932AnonymousInactive
Hei Ryan.
Great work you have hear! Congrats. I’m working a similar project but using the Reach RS2 in a ground vehicle, the Livox 40 , Sony DSC-RX1R Mark II and the Micasense Altum.As you say, I believe that the hardest part of your and my project will be the post processing for the Lidar. I will let you know how it goes, if you are interested!
-
August 5, 2021 at 10:22 AM #999AnonymousInactive
Hi Ryan!
Did you have any progress regarding 2.0 version?
I would be thrilled to see some results. So far there has been no comparison of such high accuracy reference data as Applanix and Reach M2/ integrated IMU.
-
August 5, 2021 at 8:01 PM #1002Ryan BKeymaster
Hi Luka,
Thanks for the inquiry. Last day of grad school is tomorrow! I plan to start designing the aluminum piece to allow the Livox Horizon sensor to be installed within the current OpenMMS v1.3 case (objective #1 from above) next week. This will mark the official start of the R&D for OpenMMS v2.0! I will be posting updates as things progress.
Stay tuned,
Ryan
-
August 7, 2021 at 5:14 AM #1003AnonymousInactive
Nice! I cant wait to see some updates.
If it turns out that this approach will at least somewhat work, I will buy the equipment immediately and build one!
-
-
-
August 28, 2021 at 10:59 AM #1015AnonymousInactive
Hi Ryan,
thank you Ryan for your hard work.I have the same low cost equipment, m2 + Horizon and PI4.
Maybe Inertial Explorer is a good choice. I’ve tried but not too far.
I’m an amateur, I wish you success and in the future can share the best results about this project
-
October 6, 2021 at 6:40 AM #1016AnonymousInactive
Hi Ryan!
How is the version 2.0 going? Did you have any progress?
Brs,
Luka -
November 8, 2021 at 6:50 AM #1017AnonymousInactive
Hi Ryan,
Really excellent work!!Interested with the progress of OpenMMS version 2.0, is it still on progress?
Many thanks fo your hard work.
-
February 15, 2022 at 9:28 PM #1026AnonymousInactive
I cannot find any details about ver 2.0 and hardware docs pages are still about ver 1.3 Is there any page where I can see details related to this new version?
-
February 19, 2022 at 8:14 AM #1027Ryan BKeymaster
Hello, Everyone.
Thanks for the inquiries into OpenMMS v2.0. It’s been a busy and stressful last 12 months, to say the least. Unfortunately, my research and work on hardware advancements, bug fixes, and other general improvements have not come to fruition yet. I hope to start dedicating time on a weekly basis to begin the hardware integration of the Livox Horizon lidar sensor (and internal IMU) and the Emlid Reach M2 GNSS sensor into the project. Once this is done, then the big task of developing an open-source GNSS-INS post-processing solution can begin.
I appreciate everyone’s continued interest (and patience)!
All the best,
Ryan -
July 25, 2022 at 1:28 AM #1047AnonymousInactive
Hi Ryan
Thank you so much for the great work you have done,
is there any news about the progress of the work?
thank you very much
-
-
AuthorPosts
- You must be logged in to reply to this topic.