NEO-M8P U-blox M8 High Precision GNSS Modules

NEO-M8Pu-blox M8 High Precision GNSS ModulesData SheetHighlights Centimeter-level GNSS positioning for the mass marketIntegrated Real Time Kinematics (RTK) for fast time-to-marketSmall, light, and energy-efficient RTK moduleComplete and versatile solution due to base and rover variantsMoving baseline technology for attitude sensing & follow-meapplicationsWorld-leading GNSS positioning technologywww.u-blox.comUBX-15016656 - R06

NEO-M8P - Data SheetDocument InformationTitleNEO-M8PSubtitleu-blox M8 High Precision GNSS ModulesDocument typeData SheetDocument numberUBX-15016656Revision and dateR06Document statusEarly Production Information16-May-2017Document status explanationObjective SpecificationDocument contains target values. Revised and supplementary data will be published later.Advance InformationDocument contains data based on early testing. Revised and supplementary data will be published later.Early Production InformationDocument contains data from product verification. Revised and supplementary data may be published later.Production InformationDocument contains the final product specification.This document applies to the following products:Product nameType numberROM / FLASH versionPCN / IN referenceNEO-M8PNEO-M8P-0-11FLASH FW3.01 HPG1.40N/ANEO-M8PNEO-M8P-2-11FLASH FW3.01 HPG1.40N/ANEO-M8PNEO-M8P-0-10FLASH FW3.01 HPG1.40PCN UBX-17023320NEO-M8PNEO-M8P-2-10FLASH FW3.01 HPG1.40PCN UBX-17023320u-blox reserves all rights to this document and the information contained herein. Products, names, logos and designs described herein may inwhole or in part be subject to intellectual property rights. Reproduction, use, modification or disclosure to third parties of this document orany part thereof without the express permission of u-blox is strictly prohibited.The information contained herein is provided “as is” and u-blox assumes no liability for the use of the information. No warranty, eitherexpress or implied, is given, including but not limited, with respect to the accuracy, correctness, reliability and fitness for a particular purposeof the information. This document may be revised by u-blox at any time. For most recent documents, visit www.u-blox.com.Copyright 2017, u-blox AG.u-blox is a registered trademark of u-blox Holding AG in the EU and other countries. ARM is the registered trademark of ARM Limited inthe EU and other countries.UBX-15016656 - R06Early Production InformationPage 2 of 30

NEO-M8P - Data SheetContentsContents. 31Functional description. 51.1Overview . 51.21.3Product features . 5Performance . 61.4Block diagram. 71.5GNSS . 71.5.1GPS . 71.5.2BeiDou . 71.5.3GLONASS . 71.6RTK operation. 81.6.1Rover navigation modes . 81.6.21.6.3Base station mode (NEO-M8P-2). 9RTCM message requirements . 101.7Raw data . 111.8Assisted GNSS (A-GNSS) . 11TM1.8.1AssistNow Online . 111.9Augmentation systems . 111.9.1Differential GNSS (DGNSS) . 111.10Data logging . 121.11Host Interface Signature . 121.121.13Geofencing . 13TIMEPULSE . 131.14Protocols and interfaces . 131.15Interfaces . 131.15.1 UART . 141.15.2USB . 141.15.31.15.4SPI . 14Display Data Channel (DDC) . 141.16EXTINT: External interrupt . 141.17Clock generation . 141.17.1 Oscillators. 141.17.2Real-Time Clock (RTC) . 141.18Power management . 151.18.1 Power control . 151.192Antenna . 15Pin definition . 162.1Pin assignment . 162.2Pin name changes. 17UBX-15016656 - R06Early Production InformationContentsPage 3 of 30

NEO-M8P - Data Sheet3Configuration management . 183.14Interface selection (D SEL) . 18Electrical specification . 194.1Absolute maximum rating . 194.2Operating conditions . 204.34.4Indicative current requirements . 20SPI timing diagrams . 214.4.14.5Timing recommendations . 21DDC timing . 215Mechanical specifications . 226Reliability tests and approvals . 236.16.27Reliability tests . 23Approvals . 23Product handling & soldering . 247.1Packaging . 247.1.1Reels . 247.1.2Tapes . 247.2Shipment, storage and handling . 257.2.1Moisture Sensitivity Levels . 257.2.2Reflow soldering . 257.2.3ESD handling precautions . 258Default messages . 269Labeling and ordering information. 279.1Product labeling. 279.2Explanation of codes. 279.3Ordering codes . 27Appendix . 28Glossary . 28Related documents. 29Revision history . 29Contact . 30UBX-15016656 - R06Early Production InformationContentsPage 4 of 30

NEO-M8P - Data Sheet1 Functional description1.1OverviewThe NEO-M8P modules combine the high performance u-blox M8 positioning engine with u-blox’s Real TimeKinematic (RTK) technology. The NEO-M8P provides cm-level GNSS performance designed to meet the needs ofunmanned vehicles and other machine control applications requiring accurate guidance.u-blox’s RTK technology introduces the concept of a “rover” (NEO-M8P-0) and a “base” (NEO-M8P-2) on theM8 platform for stunning cm-level accuracy in clear sky environments. The base module sends corrections via theRTCM protocol to the rover module via a communication link enabling the rover to output its position relative tothe base at cm level accuracies. The NEO-M8P is ideal for applications requiring vehicles to move faster andmore accurately, operate more efficiently, and automatically return to base platforms. Such applications includeUAV, unmanned vehicles (e.g. robotic lawn mowers), and Precision Agriculture guidance.The NEO-M8P modules enable the system integrator to access u-blox’s complete end-to-end RTK solutionincluding the stationary “survey-in” functionality that is designed to reduce the setup time and increase theflexibility of the application. The NEO‑M8P includes Moving Baseline (MB) support, allowing both Base andRover to move while computing a centimeter-level accurate position between them. Moving Baseline is ideal forUAV applications where the UAV is programmed to follow its owner or to land on a moving platform. It is alsowell suited to attitude sensing applications where both Base and Rover modules are mounted on the samemoving platform and the relative position is used to derive attitude information for the vehicle or tool.NEO-M8P modules are compatible with a wide range of communication technologies (Cellular, WiFi, BlueTooth,UHF) enabling the user to select the communication link best suited to their application. With u‑blox’s RTKtechnology, integration and software development efforts can be reduced, ensuring a minimal cost ofownership.u-blox M8 modules use GNSS chips qualified according to AEC‑Q100, are manufactured in ISO/TS 16949certified sites, and fully tested on a system level. Qualification tests are performed as stipulated in the ISO16750standard: “Road vehicles – Environmental conditions and testing for electrical and electronic equipment”.u-blox’s AssistNow services supply aiding information, such as ephemeris, almanac and time, reducing the timeto first fix significantly. The NEO-M8P operates with the AssistNow Online service which provides current GNSSconstellation orbit data to allow a Time To First Fix in seconds.1.2Product featuresUBX-15016656 - R06Early Production InformationFunctional descriptionPage 5 of 30

NEO-M8P - Data Sheet1.3PerformanceParameterSpecificationReceiver type72 channel u-blox M8 engineGPS L1C/A, GLONASS L1OF, BeiDou B1IAccuracy of time pulse signalRMS99%Frequency of time pulse signalOperational limits 130 ns60 ns0.25 Hz 10 MHz (configurable)Dynamics 4gAltitude50,000 mVelocity500 m/sVelocity accuracy0.05m/sDynamic heading accuracy0.3 2,3Time-To-First-Fix 3GPS & GLONASSGPS & BeiDouCold start26 s28 s29 sHot start1s1s1s2s3s2sAided starts 4Sensitivity5Max navigation update rateTracking & Navigation6GPS–160 dBm-160 dBm–160 dBmReacquisition–160 dBm-160 dBm–160 dBmCold start–148 dBm-148 dBm–148 dBmHot start–157 dBm-157 dBm–157 dBmRTK5 Hz5 Hz8 HzMoving Baseline RTK4Hz4Hz4HzPVT5 Hz5 Hz10 HzRAW10 Hz10 Hz10 HzConvergence time7RTK 60s8 60s93.5 min9Horizontal position accuracyStandalone9RTK 6, 102.5 m CEP0.025 m 1 ppm CEPTable 1: NEO-M8P performance in different GNSS modes (default: concurrent reception of GPS and GLONASS)1Assuming Airborne 4 g platform50% @ 30m/s for dynamic operation or assuming a 1m baseline in MB modeAll satellites at -130 dBm4Dependent on aiding data connection speed and latency5Demonstrated with a good external LNA6Limited by FW for best performance7Depends on atmospheric conditions, baseline length, GNSS antenna, multipath conditions, satellite visibility and geometry8Measured with 1 km baseline, patch antennas with ground planes; GPS BeiDou measured in Singapore9CEP, 50%, 24 hours static, -130 dBm, 6 SVs10ppm limited to baselines up to 10 km23UBX-15016656 - R06Early Production InformationFunctional descriptionPage 6 of 30

NEO-M8P - Data Sheet1.4Block diagramFigure 1: NEO-M8P block diagram1.5GNSSThe NEO-M8P positioning modules are concurrent GNSS receivers that can receive and track multiple GNSSsystems. NEO-M8P receivers are configured by default for concurrent GPS and GLONASS reception. Acombination of GPS and BeiDou can also be used. If RTK update rate is a key factor, the receiver should beconfigured to use only GPS.1.5.1 GPSThe NEO-M8P positioning modules are designed to receive and track the L1C/A signals provided at1575.42 MHz by the Global Positioning System (GPS).1.5.2 BeiDouThe NEO-M8P modules can receive and process the B1I signals broadcast at 1561.098 MHz from the BeiDouNavigation Satellite System. The ability to receive and track BeiDou signals in conjunction with GPS results inhigher coverage, improved reliability and better accuracy. Currently, BeiDou is not fully operational globally andprovides Chinese regional coverage only. Global coverage is scheduled for 2020.1.5.3 GLONASSThe NEO-M8P positioning modules can receive and process GLONASS concurrently with GPS. The NEO-M8Pmodules are designed to receive and track the L1OF signals GLONASS provides at 1602 MHz k*562.5 kHz,where k is the satellite’s frequency channel number (k –7,-6,., 5, 6). The ability to receive and track GLONASSL1OF satellite signals allows design of GLONASS receivers where required by regulations.UBX-15016656 - R06Early Production InformationFunctional descriptionPage 7 of 30

NEO-M8P - Data Sheet1.6RTK operationRTCMstreamFigure 2: The M8P modules work as a pair, where the Base provides a stream of RTCM messages to the RoverUnder RTK operation, the M8P modules operate as a pair consisting of a Rover and a Base. The Rover needsaccess to a stream of RTCM 3 messages before it can enter RTK mode and before centimeter level accuracies canbe reached. The various concepts are explained in detail below.1.6.1 Rover navigation modesIn its default configuration the NEO-M8P Rover will attempt to provide the best positioning accuracy dependanton the received correction data. It will enter RTK Float mode as soon as it receives an input stream of RTCM 3messages. Once the Rover has resolved the carrier phase ambiguities it will enter RTK Fixed mode. It is when theRover is in RTK Fixed mode that the relative accuracies can be expected to be correct to the cm-level.It will typically take less than 60s before the Rover has been able to solve the carrier ambiguities and go fromRTK Float mode to RTK Fixed mode. The length of this time period is referred to as the Convergence time.The Rover will attempt to provide RTK fixed mode when 5 or more ambiguities can be estimated. For singleconstellation receivers, this means that at least 6 satellites with continuous phase lock need to be visible abovethe elevation mask (default 10 ). Adding satellites from an additional constellation requires at least 2 satellites toform the double difference meas

u-blox M8 modules use GNSS chips qualified according to AEC‑Q100, are manufactured in ISO/TS 16949 certified sites, and fully tested on a system level. Qualification tests are performed as stipulated in the ISO16750 standard: “Road vehicles – Environmental conditi