Skip to content

Releases: SlashDevin/NeoGPS

v4.2.9

02 Jun 14:00
Compare
Choose a tag to compare
Add missing PUBX config file

New fix members and messages

31 May 13:37
Compare
Choose a tag to compare
  • New class and example sketch for Garmin proprietary $PGRMF message
  • New fix members for Velocity North/East/Down. Parsed from ublox $PUBX,00 and NAV_PVT messages
  • New fix members for Speed, Heading and Time error estimates
  • Data Model page updated

Release incorporating several bug fixes.

06 May 23:31
Compare
Choose a tag to compare

Minor work-around for Due platform

19 Mar 16:21
Compare
Choose a tag to compare

Add North/East/Down velocity feature

18 Mar 18:44
Compare
Choose a tag to compare
  • Add new Velocity North/East/Down members
    • new configuration item in GPSfix_cfg.h
    • values and validity flags added to gps_fix
    • printed by trace_all
    • parsed from UBX NAV_VELNED message

Minor fixes

09 Mar 21:10
Compare
Choose a tag to compare
  • lat_err copy and paste error caused compile error #71
  • methods to set Location lat/lon from float values didn't work #73

v4.2.3

04 Sep 00:18
Compare
Choose a tag to compare
  • Examples default to using AltSoftSerial on boards without an extra HardwareSerial port (like Serial1)
  • Char and field validation implemented for all standard NMEA sentences

GPL License

23 Aug 13:42
Compare
Choose a tag to compare
  • Relax license from LGPL to GPL
  • Add GPL license header to all files

GPSport.h rework, update Installation instructions

14 Aug 17:44
Compare
Choose a tag to compare
  • Add location, altitude, speed and heading validation tests
  • Character and Field validation configurations default to false
  • gpsPort is the new serial port variable for all examples
  • Add instructions to use Serial for GPS and Serial Monitor messages
  • Add UBX binary message HNR-PVT

New validation options

03 Aug 13:33
Compare
Choose a tag to compare
  • Because the NMEA checksum is not very good at error detection, extra validation test can be performed:
    • Character validation simply checks whether a particular character is valid for a field. For example, integer fields can only contain digits 0 to 9.
    • Field validation checks whether a parsed field value is in an acceptable range. For example, latitude degrees must be between -90 and +90.
  • The options are in NMEAGPS_cfg.h
  • This increases the program size (extra code) and the execution time (extra tests).
  • This version validates only the N/S field of a location. Future releases will contain validation of all fields.