> For the complete documentation index, see [llms.txt](https://docs.premium-modellbau.de/premium-modellbau-portal-fuer-anleitungen/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.premium-modellbau.de/premium-modellbau-portal-fuer-anleitungen/matek/matek-systems-ubersicht/matek-gps-module/m9n-5883.md).

# M9N-5883

**Artikelnr.:** PM-5683 | **HAN:** M9N-5883

[Zum Premium-Modellbau Shop](https://www.premium-modellbau.de/search?sSearch=PM-5683)

## **Matek M9N-5883 Ublox GPS und Kompass Modul M9N**

Matek Ublox GPS (NEO-M9N Multiband!) und Kompass Modul

Gewicht: ca. 14,5g

Abmessungen: 32x 32 mm

### **Specifications**

* M9N-5883 uses multi-constellation GNSS powered by u-blox NEO-M9N , NEO-M9N is a concurrent GNSS receiver which can receive and track multiple GNSS systems. Owing to the multi-band RF front-end architecture all four major GNSS constellations, GPS,Galileo, GLONASS and BeiDou can be received concurrently.
* More details about the NEO-M9N, pls check out [u-blox NEO-M9N](https://www.u-blox.com/en/product/neo-m9n-module) page

### **Specifications**

* GNSS [u-blox NEO-M9N](https://www.u-blox.com/en/product/neo-m9n-module) (GPS, GLONASS, Galileo and BeiDou
* Magnetic Compass QMC5883L
* Patch antenna 25\*25\*4mm
* Input voltage range: 4\~6V (5V pad/pin)
* Power consumption: 50mA
* Operating Temperatures: -20\~80 °C
* UART(TX, RX) interface for GNSS NEO-M9N
* I2C(DA, CL) interface for Compass QMC5883L
* JST-GH-6P connector
* 3.3V Power LED, Red
* GNSS PPS LED, Green, blinking(1Hz) when GNSS has 3D fixed
* 32mm\*32mm\*10mm
* 14.5g

### **Includes**

* 1x M9N-5883
* 1x JST-GH-6P to JST-GH-6P 20cm silicon wire

### **Wiring and settings**

* M9N-5883 5V to Flight controller 4\~6V
* M9N-5883 RX to Flight controller UART\_TX
* M9N-5883 TX to Flight controller UART\_RX
* M9N-5883 CL to Flight controller I2C\_SCL
* M9N-5883 DA to Flight controller I2C\_SDA
* M9N-5883 G to Flight controller GND
* Compass Alignment(Arrow forward and flat mounting): **INAV/BetaFLight: CW 270° Flip when flight controller arrow is facing forward alsoArdupilot/Mission Planner: Rotation None**
* Protocol: Ublox or NEMA
* Make sure to have compass/magnetometer 10cm away from power lines/ESC/motors/iron based material
* The scratches on ceramic antenna are the result of tuning the antenna.
* [u-center Windows](https://www.u-blox.com/en/product/u-center-windows)

**Tips:**

* ArduPilot supports NEO-M9N well
* INAV2.5 ublox/ublox7/NEMA all don’t support NEO-M9N for now. new protocol is required in INAV2.6
* Betaflight UBLOX protocol doesn’t support NEO-M9N, Pls select **NEMA protocol** & **Auto Baud**.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.premium-modellbau.de/premium-modellbau-portal-fuer-anleitungen/matek/matek-systems-ubersicht/matek-gps-module/m9n-5883.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.