NEO-6M GPS Module

The NEO-6M is a high-performance GPS receiver module featuring a patch antenna.

Sensors14 blocksMicroPythonC++
NEO-6M GPS Module with Antenna

At a glance

Pins and properties exactly as the circuit editor and simulator define this part. The text below explains how to use them.

Pinout

Pinout of the NEO-6M GPS Module with Antenna, drawn as in the circuit editor. Select a label to see that pin in the table below.

Pins

Pins of this part
PinLabelType
VCCVCCPower in
RXRXSignal in
TXTXSignal out
GNDGNDGround

Properties

What you can change in the Property Inspector.

Properties of this part
PropertyRange or choicesDefault
Latitude (°N/S)-90 to 90 °13.0827 °
Longitude (°E/W)-180 to 180 °80.2707 °
Altitude (m)-100 to 9000 m18.5 m
Satellites Locked0 to 169
UART Baud Rate9600 Baud (Standard), 38400 Baud, 115200 Baud9600 Baud (Standard)

The NEO-6M is a high-performance GPS receiver module featuring a patch antenna. It communicates with the host microcontroller over a UART serial connection, transmitting standardized NMEA sentences. In Open Maker Studio, it is used for tracking geographic coordinates, altitude, UTC time, speed, and heading.


1. Hardware Specifications

  • Operating Voltage: 3.3V to 5.0V (logic pins operate on 3.3V tolerance).
  • Communication Interface: UART Serial (default baud rate 9600).
  • Update Rate: 1 Hz (default).
  • Sensitivity: -161 dBm tracking sensitivity.
  • LED Status Indicator: Blinks once per second when a valid satellite fix is acquired.
  • Pin Configuration:
    • VCC: Power.
    • RX: Connect to microcontroller UART TX.
    • TX: Connect to microcontroller UART RX.
    • GND: Ground.

2. How it Works (UART Parsing)

The GPS module constantly broadcasts NMEA-0183 sentences, primarily:

  • $GPGGA: Contains time, position fix data, altitude, and satellite count.
  • $GPRMC: Contains latitude, longitude, speed (knots), heading, and date. A parser library (e.g., TinyGPS++ for C++ or micropyGPS for Python) intercepts these UART strings, decodes checksums, and parses float coordinates.

3. Component Properties

The NEO-6M now has a real simulated component (neo6m_gps_module) — drag it onto the Circuit Canvas from the Components palette. It exposes:

  • Latitude (latitude) — range -90° to 90°, default 13.0827° (Chennai, India).
  • Longitude (longitude) — range -180° to 180°, default 80.2707°.
  • Altitude (altitude) — range -100m to 9000m, default 18.5m.
  • Satellites Locked (satellites) — range 0–16, default 9. The module reports a fix once this reaches 4 (matches Section 2's real-world minimum-satellite-count requirement).
  • UART Baud Rate (baudRate) — select 9600/38400/115200, default 9600.

All four real pins are wired: VCC/GND power the module, RX/TX are real UART pins with pull resistors modeling idle-line impedance.

[!NOTE] baudRate is a Property Inspector field with no simulated effect — checked the component's SPICE model and its state() readout function directly: neither one reads it anywhere. It's shown for reference/documentation purposes (matching whatever real baud rate you configure in your generated code's "setup GPS" block), but changing it on the canvas doesn't change anything about how the module behaves in simulation.


4. Simulator Behavior

With the component placed and the circuit running:

  • Click "Open Map" on the ceramic antenna to open an interactive world map — click anywhere on it to set latitude/longitude to that point, or pick from a city preset dropdown (Chennai, New York, Tokyo, London, Paris, Dubai, Singapore, Sydney, San Francisco), or type exact values into the direct latitude/longitude number fields.
  • A live text readout shows 🛰️ Fix (<satellites> Sats) | <lat>°N/S <lng>°E/W once satellites reaches 4, or 🔍 Searching Satellites... below that — continuously while powered, not a hover-only tooltip. A green PPS LED blinks once per second while a fix is held (matching Section 1's real hardware behavior); a red PWR LED lights whenever powered.

5. Supported Blockly Blocks

Drawing the blocks…

NEO-6M GPS Module — OMS Parts