sparkfun/sparkfun_u-blox_sam-m10q

Repository for the SparkFun GPS Breakout - Chip Antenna, SAM-M10Q (Qwiic)

SparkFun GPS Breakout, Chip Antenna - SAM-M10Q (Qwiic)

SparkFun GPS Breakout, Chip Antenna - SAM-M10Q (Qwiic) (GPS-21834)

The SparkFun SAM-M10Q GPS Breakout features the the SAM-M10Q chip-antenna module from u-blox^©. The SAM-M10Q can receive up to four GNSS constellations at once which improves time-to-fix and positional accuracy even in areas with limited view of the sky. The module includes a built-in chip antenna and is compatible with the L1 band on all five GNSS constellations (GPS L1 C/A, QZSS L1 C/A L1S, GLONASS L1OF, BeiDou B1C, and Galileo E1B/C). It has a horizontal position accuracy of 1.5 m, max update rate of 18 Hz when transmitting with just one GNSS constellation (max of 5Hz with 4 GNSS) and a cold start time to fix of 23 seconds. The board includes a rechargeable 3V/1mAh battery to provide backup power for up to four hours to maintain a hot start of just 1 second.

Repository Contents

• /Documentation - Data sheets, additional product information
• /Hardware - Eagle design files (.brd, .sch)
• /docs - Hookup Guide files for the GPS Breakout, Chip Antenna - SAM-M10Q (Qwiic)
• /Production - Production panel files (.brd)

Documentation

• Library - Arduino library for the SparkFun u-blox boards v3.
• Hookup Guide - Basic hookup guide for the GPS Breakout, Chip Antenna - SAM-M10Q (Qwiic).

Product Versions

• [GPS-21834](part URL)- Initial release of GPS Breakout, Chip Antenna - SAM-M10Q (Qwiic)

License Information

This product is open source!

Please review the LICENSE.md file for license information.

If you have any questions or concerns on licensing, please contact technical support on our SparkFun forums.

Distributed as-is; no warranty is given.

• Your friends at SparkFun.

sparkfun_u-blox_sam-m10q's Issues

config-security-lock not working (disabled?)

Subject of the issue

config-security-lock isn't working
After setting config-security-lock in non-volatile memory (BDR) all configuration on the M10 should be permanently locked. Device should always power up to the locked configuration and it should no longer be possible to change it.

My concern is that these feature has been somehow disabled in the hardware?
The devices are useless if they cannot reliably maintain operating config

Your workbench

Using a Mac with U-Center 2 ver. 22.10.39687
Per U-Blox recommendation (U-Center 1.0 not recommended for 10-gen modules)

Steps to reproduce

See attached screenshot.

Suggest you change baud rate setting and some NMEA outputs, write to device. Then send config values from the screenshot to the device. Reboot device several times over 1 hour period.

Expected behavior

Device should default to the saved config values and it should no longer be possible to write new config values to the device.

Actual behavior

No change at all.
Device does not lock. It remains possible to update config values.
Also, after powering down/up the device (possibly more than once) it tends to revert back to default values (so 9600 bauds, all NMEA messages, all interfaces, etc)