Hi @EliotBR ,
Do you have any documentation about how to send data to the NMEA socket?
Hi @EliotBR ,
Do you have any documentation about how to send data to the NMEA socket?
Hi @gecastro,
These docs may be useful. They’re for our old Companion software, but most of it should apply equally well if you’ve set up a socket on BlueOS using the NMEA Injector.
Did you have any luck with this, I have tried sending to port 27000, tried using the NMEA injector and nothing seems to be working.
Got it working, my NMEA message was incorrect, found out by looking at the NMEA Injector logs in the file explorer. Like the old guide says GPS mode has to be MAV and Component 220 is gps1 and 221 is gps2. Didn’t mess around trying to send to 27000, just sent to the injector.
Eliot, I know this is a bit old, but I would like some help with the NMEA injector.
I have the vehicle time sync’d with my topside. I am sending locally generated valid GPGGA messages with 9 satellites reported. The NMEA injector is reporting successful. But the vehicle Lat/Lon never changes for 0, 0.
Is there any other configuration of logging I can do to see what is wrong?
Thanks again for your help,
Mark Kozikowski
Hi @mark -
Checkout this post for information on the messages required, and and alternative method for consuming the NMEA messages (instead of the injector.)
Using the alternate NMEA receiver worked, Tony, thanks.
I do have a minor question of clarification.
" * There’s a “hard timeout” after 4 seconds which causes the driver to re-scan if essential messages are missing. If you see multiple “GPS1: detected as NMEA” messages, that means something is wrong/missing."
What does this 4 second timeout mean? I’m guessing, that if there are no NMEA messages, the alternate interface will be reset?
Hi @mark -
Glad that is working! If you don’t send nmea messages for more than 4 seconds, you will see the warning message noted. I’m not sure what you mean by “alternate interface will be reset” ?
I was just interpreting that as stating, if nmea messages stop, you will have to reconfigure the serial port again.
I think you cleared that up. I can deal with the warning message.
Mark