I got things up an running , but now I cannot get the lat and long to show in cockpit , the GPS from my Tritech Genesis MicroNav is coming into my surface computer via an NMEA router, I Have tried all string outputs ( $GPGGA, GPGLL & GPRMC) but nothing showing,
I previously had the lat and long showing in Cockpit, but now I am using a new faster CPU computer , the lat and long will not show
Hi @Mac1 -
Cockpit generally is not involved in conveying NMEA gps position information to the autopilot - it just shows where the vehicle thinks it is!
Therefore, you need to route your NMEA data to the autopilot in BlueOS. You can do that with the NMEA bridge, or by configuring the correct serial input. You’d your MicroNav to target the ROV IP address, at port 27000, and set the parameters as detailed in the BlueBoat FAQ:
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.
I tried to follow the instructions from the previous post, but I got confused when it got to the serial port setup. I’m not very experienced with software, and when things aren’t clearly explained step by step, they’re hard for me to understand. Technical instructions written by programmers can be difficult to follow if you’re not familiar with that kind of language.
Please understand this comment as an explanation of where I’m having difficulty, not as a contradiction of what you’re trying to explain.
Hi @Mac1
Apologies if the instructions are confusing. No programming is required!
Does your MicroNav GPS interface allow to to target an IP and port #? It’s difficult to support you with specific instructions without more context. If your recall anything on how you previously set this up and were having success, that would also be helpful. Maybe before you used the BlueOS nmea bridge, documented in the link shared previously?
The serial port setup is confusing only because you’re telling serial 2 that it is connected to a network port, and not a hardware serial port. By configuring it to expect GPS data from that source, the autopilot then knows what to do with the input.
Please share as much detail on your setup as you can, where you’re getting stuck, and what you recall from your prior successful setup process.
Normally in the past (either in QGC or Cockpit) I have a separate computer allocated for the Micronav program, from there I export the micronav ROV pingers GPS lat and long output through a dedicated port in the micronav (normally with $GPRMC)
I then pick the string up in the companion computer with an MNEA router serial input and set output to UDP 192.168.2.2:27000
In QGC it was picked up with no problem, but in Cockpit Rafael set it up for me, and I thought it would all have been saved , but does not appear to be.
So I am lost as to how to pick up the output UDP in Cockpit (or BluoOS) settings
Rafael said that he may be available tomorrow for an online set up configuration, unless you are able to guide me through a simple process set up in the mean time, as I have a pending survey on Tuesday and would like to relax and have everything all set up and prepared the sooner the better.
