is Arduino GPS module viable? UART? i2C? NMEA0183?

[sinneD]

Greetings- 

I inherited a TinyGPS module with antenna, orignally intended to woork with Arduino. I am trying to figure out if I can make it work with OpenPlotter. It uses a blox NEO-M8 module. The model silkscreened on the PCB is GY-GPSV3-NEO. 

searching here for u-blox GPS devices, all i seem to find are USB based ones.  

I am pretty sure that it used SoftwareSerial in Arduino, so which way to interface with Openplotter/MacArthur HAT? 

Then I get confused by other things like https://portal.u-blox.com/s/question/0D5...on-via-i2c
that reference it as i2C capble, but it needs to be progtrammed as such, I think.  

Tryin to read the blox datasheet/protocol docment is overwhelming to me. frankly, Iam not sure what i should  be looking for. 

Some Arduino library info here- 
https://github.com/mikalhart/TinyGPSPlus...me-ov-file
refrences that it talks in NMEA 'sentences' GGA and RMC

Is this worthwhile or a time waster? 

Dennis

[PaddyB]

I use similar. It outputs TTL which is sort of like upside down serial. It can attach direct raspberry pi Uart pins which are set up in the openplotter serial app. https://openplotter.readthedocs.io/lates....html#uart
From perplexity (usually worth asking it first to see, often nails it straight away)
Mine cost €2.80 and is always on.

The GY-GPSV3-NEO is a compact GNSS/GPS module based on the u-blox NEO-M8N chipset, popular for DIY marine electronics and embedded projects like Arduino or Raspberry Pi integrations.��Key FeaturesSupports multiple satellite systems including GPS, GLONASS, BeiDou, and Galileo for improved accuracy up to 2 meters CEP.�� UART interface defaults to 9600 baud (configurable), with onboard EEPROM for settings storage and a backup battery for RTC functionality.�� Includes IPEX antenna connector, LED fix indicator, and operates on 3.3-5V with low power draw, suitable for battery-powered boat tracking or navigation setups.��Pinout and WiringStandard pins include VCC (3.3-5V), GND, TX/RX for UART, and mounting holes for easy integration.� For Arduino/OpenPlotter use, connect TX to RX pin (e.g., D4) and RX to TX (e.g., D3); libraries like TinyGPS++ parse NMEA data effectively.�Marine ApplicationsIdeal for SignalK/OpenCPN position logging on sailboats, with 10Hz update rate and -40°C to 85°C range for offshore reliability.�� Pairs well with ESP32 or Pi for BLE broadcasting of lat/long data in your cruising projects.�

[saltwaterone]

Greetings- 

I inherited a TinyGPS module with antenna, orignally intended to woork with Arduino. I am trying to figure out if I can make it work with OpenPlotter. It uses a blox NEO-M8 module. The model silkscreened on the PCB is GY-GPSV3-NEO. 

searching here for u-blox GPS devices, all i seem to find are USB based ones.  

I am pretty sure that it used SoftwareSerial in Arduino, so which way to interface with Openplotter/MacArthur HAT? 

Then I get confused by other things like https://portal.u-blox.com/s/question/0D5...on-via-i2c
that reference it as i2C capble, but it needs to be progtrammed as such, I think.  

Tryin to read the blox datasheet/protocol docment is overwhelming to me. frankly, Iam not sure what i should  be looking for. 

Some Arduino library info here- 
https://github.com/mikalhart/TinyGPSPlus...me-ov-file
refrences that it talks in NMEA 'sentences' GGA and RMC

Is this worthwhile or a time waster? 

Dennis

A bit of an old thread, and I hope you got this figured out, but if not I wrote some code for the ublox gps (and most I2C connected GPS's) to output over USB, with an ESP32 converting the signal to NMEA0183.   It should also work on arduino.  There is suppprt for some other sensors as well in the code, which shouldnt be a problem, since it should just send null values of the other sensors are not connected, but still send the GPS NMEA sentences just fine (or just delete the superflous code), I think signalk data model is designed to handle multiple data sources over thr same (or different) paths, so it shouldnt break other devices of the same class you may have deployed.   You may have to renumber the GPIO pins I used, Im not sure what those might be on arduino, but any GPIO pins should work.  Heres the code if this helps

https://github.com/sv-enkidu/esp-32-sign...tData-puck

[sinneD]

A bit of an old thread, and I hope you got this figured out, but if not I wrote some code for the ublox gps (and most I2C connected GPS's) to output over USB, with an ESP32 converting the signal to NMEA0183.   It should also work on arduino.  There is suppprt for some other sensors as well in the code, which shouldnt be a problem, since it should just send null values of the other sensors are not connected, but still send the GPS NMEA sentences just fine (or just delete the superflous code), I think signalk data model is designed to handle multiple data sources over thr same (or different) paths, so it shouldnt break other devices of the same class you may have deployed.   You may have to renumber the GPIO pins I used, Im not sure what those might be on arduino, but any GPIO pins should work.  Heres the code if this helps

https://github.com/sv-enkidu/esp-32-sign...tData-puck

THANKS ! I will look into it. This unit is my 'test bed' and I used it by wiring direct to the raspi I2C pins and it works great straight up. 

i will check out your repo- i am always up for better. 

sinneD

A bit of an old thread, and I hope you got this figured out, but if not I wrote some code for the ublox gps (and most I2C connected GPS's) to output over USB, with an ESP32 converting the signal to NMEA0183.   It should also work on arduino.  There is suppprt for some other sensors as well in the code, which shouldnt be a problem, since it should just send null values of the other sensors are not connected, but still send the GPS NMEA sentences just fine (or just delete the superflous code), I think signalk data model is designed to handle multiple data sources over thr same (or different) paths, so it shouldnt break other devices of the same class you may have deployed.   You may have to renumber the GPIO pins I used, Im not sure what those might be on arduino, but any GPIO pins should work.  Heres the code if this helps

https://github.com/sv-enkidu/esp-32-sign...tData-puck