Connecting a hotshoe adaptor to a m+ and navio2

I am planning to connect a m+ to a navio2 to improve accuracy and I would also like to attach the emlid hotshoe adaptor to improve geotagging accuracy.

Is this possible and are there any issues to be aware of?

I am planning on attaching the hotshoe adaptor to the c1 port on the m+ and the m+ to the navio2 by usb.

I also have a lidar lite v3 attached to the i2c port on the navio2 via a breadboard.

Thanks in advance!

Hi Thomas,

Welcome to our forum!

Yes, this setup should work just fine. You can connect a hot shoe adapter to the C1 port of M+ and also connect M+ to the USB port of the Raspberry Pi with the attached Navio2. Please check this guide for more details about the integration of M+ with Navio2.

Please note that for the correct time mark recording, you need to configure the corresponding GNSS selection and update rate. You can choose one of the following settings:

  • GPS + GLONASS + Galileo + SBAS + QZSS at 1 Hz
  • GPS + GLONASS + QZSS at 5 Hz
  • GPS + GALILEO at 5 Hz
  • GPS at 10 Hz

Сonfiguring Reach UAV Kit for PPK Mapping guide should be of great help to you.

This is additional information from mission planner. The last section after attempting to connect via udp over wifi. Any guidance would be appreciated.

INFO MissionPlanner.MAVLinkInterface - list count 991, rcvd total 991 indexseen count 991
INFO MissionPlanner.Controls.ProgressReporterDialogue - DoWork Done
INFO MissionPlanner.ArduPilot.APFirmware - https://firmware.ardupilot.org/manifest.json.gz
HUD 4 hz drawtime 0 gl True
bps 16944 loss 0 left 561 mem 51.2685546875 mav2 True sign False mav1 0 mav2 468 signed 0
HUD 14 hz drawtime 1 gl True
bps 1655 loss 0 left 525 mem 140.8447265625 mav2 True sign False mav1 0 mav2 52 signed 0
INFO MissionPlanner.ArduPilot.APFirmware - 45295
INFO MissionPlanner.Utilities.VersionDetection - ArduCopter V4.0.3 (296bb047)
INFO MissionPlanner.Utilities.VersionDetection - 4.0.3
HUD 8 hz drawtime 0 gl True
bps 1619 loss 0 left 525 mem 149.91015625 mav2 True sign False mav1 0 mav2 51 signed 0
HUD 14 hz drawtime 0 gl True
bps 1656 loss 0 left 525 mem 150.181640625 mav2 True sign False mav1 0 mav2 52 signed 0
HUD 13 hz drawtime 0 gl True
bps 1619 loss 0 left 525 mem 150.2802734375 mav2 True sign False mav1 0 mav2 51 signed 0
INFO MissionPlanner.CurrentState - messageHigh Unhealthy AHRS
HUD 14 hz drawtime 0 gl True
bps 1645 loss 0 left 525 mem 150.4052734375 mav2 True sign False mav1 0 mav2 52 signed 0
HUD 16 hz drawtime 0 gl True
bps 1655 loss 0 left 525 mem 150.412109375 mav2 True sign False mav1 0 mav2 52 signed 0
HUD 16 hz drawtime 0 gl True
bps 1619 loss 0 left 525 mem 150.4521484375 mav2 True sign False mav1 0 mav2 51 signed 0
HUD 16 hz drawtime 0 gl True
bps 1619 loss 0 left 525 mem 150.5546875 mav2 True sign False mav1 0 mav2 51 signed 0
HUD 16 hz drawtime 0 gl True
bps 1619 loss 0 left 299 mem 150.705078125 mav2 True sign False mav1 0 mav2 51 signed 0
INFO MissionPlanner.MAVLinkInterface - set giveComport Base Thread current False new False
INFO MissionPlanner.MainV2 - MenuConnect Start
INFO MissionPlanner.MainV2 - Cleanup last logfiles
INFO MissionPlanner.MainV2 - We are disconnecting
INFO MissionPlanner.Utilities.TerrainFollow - OnPacketReceived remove to packets
INFO MissionPlanner.MAVLinkInterface - set giveComport Base Thread current False new False
INFO MissionPlanner.MainV2 - Saving config
INFO MissionPlanner.Log.LogSort - Move log C:\Users\Tom\Documents\Mission Planner\logs\2023-09-09 14-34-09.rlog to C:\Users\Tom\Documents\Mission Planner\logs\QUADROTOR\1\2023-09-09 14-34-09.rlog
INFO MissionPlanner.Log.LogSort - Move log C:\Users\Tom\Documents\Mission Planner\logs\2023-09-09 14-34-09.tlog to C:\Users\Tom\Documents\Mission Planner\logs\QUADROTOR\1\2023-09-09 14-34-09.tlog
HUD 14 hz drawtime 1 gl True
HUD 16 hz drawtime 0 gl True
HUD 16 hz drawtime 0 gl True
HUD 16 hz drawtime 0 gl True
HUD 16 hz drawtime 0 gl True
HUD 16 hz drawtime 0 gl True
HUD 16 hz drawtime 0 gl True
INFO MissionPlanner.MAVLinkInterface - set giveComport Base Thread current False new False
INFO MissionPlanner.MainV2 - MenuConnect Start
INFO MissionPlanner.MainV2 - Cleanup last logfiles
INFO MissionPlanner.MainV2 - We are connecting to UDP 115200
INFO MissionPlanner.MainV2 - Reset connection stats
INFO MissionPlanner.MainV2 - Set Portname
INFO MissionPlanner.MainV2 - Set Baudrate
INFO MissionPlanner.MAVLinkInterface - set giveComport Base Thread current False new True
INFO MissionPlanner.MainV2 - About to do dtr if needed
INFO MissionPlanner.MainV2 - set dtr rts to false
INFO MissionPlanner.MAVLinkInterface - set giveComport Base Thread current True new False
INFO MissionPlanner.MainV2 - creating logfile 2023-09-09 14-34-32.tlog
INFO MissionPlanner.Controls.ProgressReporterDialogue - RunBackgroundOperation
INFO MissionPlanner.Controls.ProgressReporterDialogue - Focus ctl
INFO MissionPlanner.Controls.ProgressReporterDialogue - in focus invoke
INFO MissionPlanner.Controls.ProgressReporterDialogue - DoWork
INFO MissionPlanner.MAVLinkInterface - SubscribeToPacketType DISTANCE_SENSOR System.Func2[MAVLink+MAVLinkMessage,System.Boolean] False 1 1 INFO MissionPlanner.MAVLinkInterface - SubscribeToPacketType OBSTACLE_DISTANCE System.Func2[MAVLink+MAVLinkMessage,System.Boolean] False 1 1
INFO MissionPlanner.Utilities.Proximity - created for 1 - 1
INFO MissionPlanner.Utilities.TerrainFollow - OnPacketReceived to packets
INFO MissionPlanner.MAVLinkInterface - Open port with UDP14550 115200
Input Box Base Thread
HUD 9 hz drawtime 1 gl True
HUD 1 hz drawtime 0 gl True
HUD 1 hz drawtime 0 gl True
Input Box 2 Base Thread
Input Box 3 Base Thread
Input Box 4 Base Thread
Input Box 5 Base Thread

Hi Liudmila,

Thanks for the information. I tried to follow the setup instructions but it didn’t go smoothly; there seems to be a lot involved in the setup.

I have tried to revert to my previous setup, which is the standard navio2 parameters and have reflashed the sd card and switch raspberry pi from a model 2B to model 3.

I am having trouble connecting the navio2 via wifi. Previously this was not a problem and was achieved using udp"ip":14450

now I can only connect via ethernet cable, which works fine. When I go wifi then I am unable to connect. Any suggestions?

Thanks

Thomas



I have reverted to not using the m+ now. It took me some time to figure out the raspberry pi was not connecting to the wifi after I had disconnected from the m+.

I used ping 8.8.8.8 and this seemed to wake up the wifi connection and have been able to reconnect with mission planner and will stick with that setup.

Hi Thomas,

I’m not sure whether I got it right: are you able to connect to Navio2 with M+ connected to it in Mission Planner now? Are there any issues with configuring the settings for Navio2 and M+ integration?

Hi Liudmilla,

Thanks,

I have resolved the issue now.

1 Like

This topic was automatically closed 100 days after the last reply. New replies are no longer allowed.