I am trying to use the Marvelmind ultrasonic system for indoor navigation and I am currently facing some issues.
There seem to be three ways to connect ArduPilot with the MM hedgehog:
- NMEA protocol
- ublox protocol
- Marvelmind protocol
Please correct me if I’m wrong, but the first two seem to emulate a conventional GPS signal and pass it on to the FC, while the other one is more general and is processed in AP.
Now I managed to get the NMEA protocol running simply by hooking the MM hedgehog up and setting GPS_TYPE = 5 (NMEA). I put my GPS coordinates into MM Dashboard → Mode/Geofencing. I am getting a GPS 3D_FIX sometimes but not sufficiently often. Also there seems to be a lot of delay between the movement of the drone and the registered movement shown in MP. The delay is also way bigger than the one in the MM Dashboard.
Is there a way to make this NMEA signal more robust?
I could get any signal out of MM when changing GPS_TYPE = 2 (ublox) and changing to ublox in MM, respectively. When contacting the support, they immediately respond that the are only testing PX4 and not AP, and not much more. Has anyone here achieved a ublox signal with MM?
Finally the Marvelmind protocol which is also in the wiki Marvelmind for Non-GPS navigation — Copter documentation . I followed the instruction but couldn’t get it to work either. I saw some forum posts from 2018 but not a whole lot after that. Is this depricated?
I would appreciate any and all help I can get to have MM running the indoor GPS for AP.
Kind regards,
Felix