I’ve been working on a project with one Reach M+ and I’d like to extract some IMU information from it. I know that there are some topics already opened about this subject, but I wanted to put some info together and try to figure out which method one should use.
The main solutions found on topics around there are:
- GitHub - erlerobot/erle-brain-2-imu - It’s the easiest to use in my opinion. It also lacks lacks documentation, but the python code is self explanatory (See topic here)
- GitLab - _a.richard/imu_reach_m - It’s a ROS module, very well documented and pretty complete. Haven’t found reports of others users besides the author’s own report (See topic here)
- GitHub - 14roiron/RTIMULIB_EMLID_REACH_2 - Need some gcc compilation. Other users have reported issues (See the topic here)
- GitHub - egorf/MPUtest - Lacks documentation and may be outdated, since its last commit is from 4 years now (See topics here and here)
Besides such efforts, we do not have an official solution from Emlid. I found this answer over here which says that we should be able to access IMU data with some Linux and programming knowledge. Later on the same topic (precisely here) it’s said that the MPU9250 is avaiable on /dev/spidev5.1 and the driver is located on /home/reach/MPUtest. Well… I guess it’s for another model, because Reach M+ has neither of them, as you can see in the picture below. (By the way, our ReachView version is the latest until yesterday, 2.18 I guess)
I would like to ask Emlid if there are any official tips for Reach M+ users, or if we may keep waiting for the community to help while this is not implemented on ReachView…
Sorry for the long text… I hope this helps anyone searching for ways of getting IMU data out of Reach M+. If me and my friends find out with something useful, we’ll let you know.
Thanks and good “Reaching” everyone!