A real USB data plug
A complete cabled GPS receiver with its own antenna. It must send position data over USB, not use USB only for charging.
Choose a complete USB GPS receiver for your Pi. Start with the hardware we have tested, then check the exact specification before ordering.
Choose the u-blox 7 USB variant of the VK-162, also sold as a G-Mouse. Our physical test unit was detected automatically on Raspberry Pi 5 and supplied real position, satellite reports and validated GPS backup time.
Check the hardware, not just the name. Sellers can use the same VK-162 name for different revisions. Ask for a complete USB receiver with Linux support and NMEA output.
The linked listing describes the matching USB/chipset specification. Confirm the current item and returns policy; this does not qualify every unit or retailer revision.A complete cabled GPS receiver with its own antenna. It must send position data over USB, not use USB only for charging.
The seller should confirm Linux USB-serial support and standard NMEA position output. For the tested choice, confirm the u-blox 7 USB variant.
Allow room to place the puck clear of obstructions and secure its cable. Check the actual enclosure and mounting rating before outdoor or marine use.
“Is this a complete VK-162 USB GPS receiver using u-blox 7, with Linux USB-serial support and NMEA position output? Can you confirm the USB device ID and that it sends data over USB?”
Our tested unit reports 1546:01a7 and u-blox 7. This is a useful match, not proof of identical firmware, quality or environmental protection.
Linux-compatible NMEA receivers may work. Known GPS identities can be detected automatically; a generic USB-serial model may need manual GPS selection. They have not all been physically qualified by Layer400.
An antenna-only puck with an SMA connector, a bare UART/TTL board, a Bluetooth-only receiver or a USB charging cable is not the tested plug-in USB setup.
It supplies your station’s position and optional time. Keep your Remote ID radio or ADS-B input. Use the receiver hardware guide to choose those separately.
Keep normal power and internet connected. Plug the GPS into a free data-capable USB port and open Mobile → Test GPS. Fixed uploads continue during preview.
Connected does not mean Fix acquired. Wait for a fresh fix and check its age, coordinates and reported accuracy. Indoor reception and cold starts can take longer; no fixed acquisition time is guaranteed.
Add Wi-Fi / hotspot and enable Auto-join while still at home. Then follow the Mobile setup guide, including the cloud compatibility check and a stationary connectivity test.
Check the USB connection and open Select GPS device if offered. Select only the known GPS; never select an ADS-B, Remote ID or other radio. Advanced diagnostics shows the device identity and permission/device errors. Layer400 does not blindly seize every serial port.
A stationary puck should not make the receiver marker move around. It needs a fresh fix before GPS positioning can be enabled. On receivers with the Satellites view, icons show reported sky positions; trails build while the page is open. Satellite motion is gradual. A lost fix is labelled stale, not a new position.
Where the System time control is available, Automatic · internet + GPS backup lets the receiver validate GPS time before using it. Keep internet available for the initial check. USB serial timing is not PPS timing, and bad or stale GPS dates are rejected.
The u-blox 7 USB puck was physically checked on Pi 5 for automatic detection, real fixes and satellite data, GPS-time validation, controlled reboot and Layer400 uploads. That is not a guarantee for every retail revision, instant indoor fixes, hotspot handover, weather sealing or an arbitrary power cut. Validate your own installation before travelling.
Technical references: gpsd hardware notes and u-blox 7 receiver protocol documentation.
Layer400 hardware checks and guidance reviewed 28 October 2026.