I am having an issue with my GPS configuration in Cockpit , I had it working with the assistance of Rafael, but on site it stopped logging on the telemetry and now I have lost the GPS reading in Cockpit.
I am using a Tritech Micronav with Genesis software program, that is set up in an separate PC and then exported through the Micronav hub (with $GPGGA string, I also tried $GPRMC string) and then it is picked up on my main Cockpit/BlueOS computer port through an MNEA router and Output through UDP 192.168.2.2:27000 and then should normally be picked up with the BlueOS /Cockpit and displayed
Happy that you got it to work! Could you explain what was the problem or how did you configure it to work? I’m sure other people are using the MicroNav, so it can help them as well.
it was what Tony posted for me a few days ago , we got it working the same way as well, but I had forgotten with all the other issues going on , but then followed Tony’s ( and remembered what you had explained) instructions and got it going
Any NMEA position stream can be parsed by the Navigator Autopilot. To receive the messages from a network-connected device simply configure the Autopilot parameters GPS_Type to NMEA, Serial2_Protocol to GPS, and verify no other Serial port # protocol is set to GPS. Finally, under Autopilot Firmware, Serial port Configuration, set Serial 2 to: udpin:0.0.0.0:27000. Then direct your UDP NMEA stream to the IP address of the BlueBoat/BlueROV2. Note that these NMEA messages are required for navigation: RMC, GGA, VTG, HDT. This approach uses the ArduPilot driver to interpret the NMEA messages - you can also use the NMEA Injector in BlueOS, which has support for fewer messages. If using a serial connection to bring the NMEA position data to the Navigator serial port 3 or 4, set the appropriate Serial# Protocol parameter to GPS and restart the autopilot. NMEA messages should be sent at 10hz or faster.
