The Matek GNSS M9N-CAN, UAVCAN & MSP GPS features AP F303 CAN node, NEO-M9N, QMC5881L, DPS310, I2C, UART1 & UART3 breakout. UAVCAN protocol & UART_MSP.
\r\nFeatures
\r\n- \r\n
- M9N-CAN is based on ArudPilots’ AP_Pheriph firmware, It is a GNSS+COMPASS+BAROMETER peripheral with CAN/UAVCAN and UART/MSP interfaces to the autopilot, plus an I2C expansion bus for additional peripherals, such as airspeed sensors. \r\n
- M9N-CAN 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. \r\n
Specifications
\r\n- \r\n
- GNSS u-Blox NEO-M9N (GPS, GLONASS, Galileo, and BeiDou) \r\n
- Magnetic Compass QMC5883L \r\n
- Barometer DPS310 \r\n
- ArduPilot AP_Periph F303 CAN node \r\n
- UART1, Firmware update \r\n
- UART2, onboard NEO-M9N \r\n
- UART3, MSP Protocol \r\n
- CAN, UAVCAN Protocol \r\n
- I2C, onboard QMC5883L & DPS310 \r\n
- I2C JST-GH connector, external AirSpeed sensor \r\n
- CAN bootloader LED, Blue \r\n
- Fast blinking, No communication between CAN node and Flight Controllers \r\n
- Slow blinking, Communicating between CAN node and Flight Controllers \r\n
- GNSS PPS LED, Green \r\n
- blinking(1Hz) when GNSS has 3D fixed \r\n
- Input voltage range: 4.5~5.5V (5V pad/pin) \r\n
- Power consumption: 100mA \r\n
- Operating Temperatures: -20~80 °C \r\n
- 32mm*32mm*10mm \r\n
- 15g \r\n
Tips
\r\n- \r\n
- Compass Alignment(Arrow forward and flat mounting): \r\n
- Ardupilot/Mission Planner: Rotation None \r\n
- Make sure to have compass/magnetometer 10cm away from power lines/ESC/motors/iron-based material \r\n
- The scratches on the ceramic antenna are the result of tuning the antenna. \r\n
Includes
\r\n- \r\n
- 1 x M9N-CAN \r\n
- 2 x JST-GH-4P to JST-GH-4P 20cm silicon wire \r\n