I saw that some people started a topic similar to this one, but were finished without a solution.
I followed the tutorial suggested by Emlid to connect the Reach M + to Pixhawk, however, I am not having success.
In fact I notice many people trying to follow the tutorial and not being successful.
The question is: How to know if the problem is in the connection of the cables that is not detailed in the tutorial or if the problem is in the configuration of the missionplanner. The base is easy to connect via TCP Client, but a Reach M + gps signal on MissionPlanner never worked.
I changed the communication protocol of the serial port 4/5 on the missionplanner “SERIAL4_PROTOCOL” to 5 “GPS” and 20 “NMEA OUTPUT” and neither option worked.
I created this pdf file with all the settings and connections between pixhawk 1 serial port 4/5 and Reach m + S1 port:
Sorry for the delay. We are working remotely, that is why it took us longer to reproduce the issue.
Please, try the following parameters in Mission Planner:
GPS_AUTO_CONFIG=1
GPS_AUTO_SWITCH=1
GPS_TYPE2=5 (GPS)
SERIAL4_PROTOCOL=5 (GPS)
GPS_INJECT_TO=1
SERIAL4_BAUD=57
Please, use the following settings in the Position Output tab in ReachView:
Device - UART
Baud rate - 57600
Format - NMEA
These settings were tested on the latest Ardupilot firmware for Pixhawk, v.4.0.5. Please, reboot your Pixhawk board by detaching it from the USB port of your PC after the settings were updated.