Matek GNSS & Compass M9N-5883 GPS

Back due to demand - some believe this to be better than the M10

Specifications:

• GNSS u-blox NEO-M9N (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 also
  Ardupilot/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

Tips & Note from Matek:

• 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.

STL file here

Write a review