u-blox NEO-M9N Integration Manual

Standard precision gnss module

Hide thumbs

Table Of Contents

Table of Contents

Quick Links

Download this manual



NEO-M9N

Standard precision GNSS module

Integration manual

Abstract

Integration manual describing the u-blox NEO-M9N GNSS module. NEO-

M9N oﬀers ultra-robust meter-level GNSS positioning performance with

concurrent reception of up to four GNSS (GPS, GLONASS, BeiDou, Galileo)

in a 12.2 x 16.0 mm package.

www.u-blox.com

UBX-19014286 - R07

C1-Public

Table of Contents

Summary of Contents for u-blox NEO-M9N

Page 1 Standard precision GNSS module Integration manual Abstract Integration manual describing the u-blox NEO-M9N GNSS module. NEO- M9N oﬀers ultra-robust meter-level GNSS positioning performance with concurrent reception of up to four GNSS (GPS, GLONASS, BeiDou, Galileo) in a 12.2 x 16.0 mm package.
Page 2 ﬁtness for a particular purpose of the information. This document may be revised by u-blox at any time without notice. For the most recent documents, visit www.u-blox.com.
Page 3: Table Of Contents
NEO-M9N - Integration manual Contents 1 Integration manual overview..................... 6 2 System description.......................7 2.1 Overview..............................7 2.2 Architecture..............................7 2.2.1 Block diagram..........................7 3 Receiver functionality......................8 3.1 Receiver conﬁguration........................... 8 3.1.1 Changing the receiver conﬁguration..................8 3.1.2 Default GNSS conﬁguration......................8 3.1.3 Default interface settings......................9 3.1.4 Basic receiver conﬁguration......................9...
Page 4 3.14 Security..............................61 3.14.1 Spooﬁng detection / monitoring.................... 61 3.14.2 Jamming/interference detection / monitoring..............62 3.14.3 GNSS receiver integrity......................63 3.15 u-blox protocol feature descriptions....................63 3.15.1 Broadcast navigation data...................... 63 3.16 Forcing a receiver reset........................67 3.17 Firmware upload..........................68 4 Design............................. 69 4.1 Pin assignment............................69...
Page 5 NEO-M9N - Integration manual 4.5.2 Antenna design with external LNA or active antenna............73 4.5.3 Out-of-band blocking immunity....................75 4.6 EOS/ESD precautions.......................... 75 4.6.1 ESD protection measures......................76 4.6.2 EOS precautions...........................76 4.6.3 Safety precautions........................77 4.7 Electromagnetic interference on I/O lines..................77 4.7.1 General notes on interference issues..................77 4.7.2 In-band interference mitigation....................78...
Page 6: Integration Manual Overview
NEO-M9N - Integration manual 1 Integration manual overview This document is an important source of information on all aspects of NEO-M9N system, software and hardware design. The purpose of this document is to provide guidelines for a successful integration of the receiver with the customer's end product.
Page 7: System Description
The receiver also provides higher navigation rate and improved security features compared to previous u-blox GNSS generations. The NEO-M9N module is available in the 12.2 x 16.0 mm NEO form factor LCC package. 2.2 Architecture The NEO-M9N receiver provides all the necessary RF and baseband processing to enable multi- constellation operation.
Page 8: Receiver Functionality
This section describes the NEO-M9N operational features and their conﬁguration. 3.1 Receiver conﬁguration The NEO-M9N is fully conﬁgurable with UBX conﬁguration interface keys. The conﬁguration database in the receiver's RAM holds the current conﬁguration, which is used by the receiver at run-time.
Page 9: Default Interface Settings
Refer to the applicable interface description [2] for information about further settings. By default the NEO-M9N outputs NMEA messages that include satellite data for all GNSS bands being received. This results in a higher-than-before NMEA load output for each navigation period.
Page 10: Rtcm Corrections
NEO-M9N design. The u-center NTRIP client connects over the internet to an NTRIP service provider, using access credentials such as user name and password from the service provider. The u-center NTRIP client then forwards the RTCM 3.3 corrections to a NEO-M9N receiver connected to the local UBX-19014286 - R07...
Page 11: Legacy Configuration Interface Compatibility
CFG-NAVSPG-* conﬁguration keys. 3.1.7.1 Platform settings u-blox receivers support diﬀerent dynamic platform models (see the table below) to adjust the navigation engine to the expected application environment. These platform settings can be changed dynamically without performing a power cycle or reset. The settings improve the receiver's interpretation of the measurements and thus provide a more accurate position output.
Page 12 3D ﬁx (min four satellites available), the altitude is kept constant at the last known value. This is called a 2D ﬁx. u-blox receivers do not calculate any navigation solution with less than three satellites. 3.1.7.3 Navigation output ﬁlters The result of a navigation solution is initially classiﬁed by the ﬁx type (as detailed in the...
Page 13 NEO-M9N - Integration manual UBX-NAV-STATUS message also reports whether a ﬁx is valid in the gpsFixOK ﬂag. These messages have only been retained for backwards compatibility and users are recommended to use the UBX-NAV-PVT message. 3.1.7.3.1 Speed (3D) low-pass ﬁlter The CFG-ODO-OUTLPVEL conﬁguration item oﬀers the possibility to activate a speed (3D) low-pass ﬁlter.
Page 14 NEO-M9N - Integration manual Figure 2: Position publication in static hold mode Figure 3: Flowchart of the static hold mode UBX-19014286 - R07 3 Receiver functionality Page 14 of 95 C1-Public...
Page 15 NEO-M9N - Integration manual 3.1.7.5 Freezing the course over ground If the low-speed course over ground ﬁlter is deactivated or inactive (see section Low-speed course over ground ﬁlter), the receiver derives the course over ground from the GNSS velocity information. If the velocity cannot be calculated with suﬃcient accuracy (e.g., with bad signals) or if the absolute speed value is very low (under 0.1 m/s) then the course over ground value becomes inaccurate too.
Page 16: Sbas
Every SBAS satellite that broadcasts ephemeris or almanac information can be used for navigation, just like a normal GNSS satellite. For receiving correction data, the NEO-M9N automatically chooses the best SBAS satellite as its primary source. It will select only one since the information received from other SBAS satellites is redundant and could be inconsistent.
Page 17: Geofencing
NEO-M9N - Integration manual To conﬁgure the SBAS functionalities use the CFG-SBAS-* conﬁguration group. Parameter Description CFG-SIGNAL-SBAS_ENA Enabled/disabled status of the SBAS subsystem CFG-SBAS-USE_TESTMODE Allow/disallow SBAS usage from satellites in test mode CFG-SBAS-USE_RANGING Use the SBAS satellites for navigation (ranging) CFG-SBAS-USE_DIFFCORR Combined enable/disable switch for fast-, long-term and ionosphere corrections...
Page 18: Geofence State Evaluation
NEO-M9N - Integration manual The current state of each geofence plus the combined state is output in UBX-NAV-GEOFENCE with every navigation epoch. 3.3.3 Geofence state evaluation With every navigation epoch the receiver will evaluate the current solution's position versus the conﬁgured geofences. There are three possible outcomes for each geofence: •...
Page 19: Setting The Logging System Up
NEO-M9N - Integration manual Message Description UBX-LOG-STRING Enables a host process to write a string of bytes to the log ﬁle Table 8: Logging control and conﬁguration messages Message Description UBX-LOG-RETRIEVE Starts the log retrieval process UBX-LOG-RETRIEVEPOS A position log entry returned by the receiver...
Page 20: Recording
NEO-M9N - Integration manual is 9 bytes and the maximum 24 bytes, the typical size is 10 or 11 bytes. If the odometer is enabled then this will use at least another three bytes per ﬁx. Each log also has a ﬁxed overhead which is dependent on the log type. The approximate size of this overhead is shown in the following table.
Page 21: Retrieval
NEO-M9N - Integration manual as 1 km. Within these limits, the recorded accuracy will always be greater than the ﬁx accuracy number (by up to 40%). • Heading to a precision of one degree. • Odometer distance data (if odometer is enabled).
Page 22: Command Message Acknowledgment
NEO-M9N - Integration manual The UBX-LOG-FINDTIME message can be used to search a log for the index of the ﬁrst entry less than or equal to the given time. This index can then be used with the UBX-LOG-RETRIEVE message to provide timebased retrieval of log entries.
Page 23: Retrieval
This way the receiver will send a UBX-MON-BATCH message ﬁrst that contains the number of ﬁxes in the batching buﬀer. This information can be used to detect when the u-blox receiver ﬁnishes sending data. Once retrieval has started, the receiver will ﬁrst send UBX-MON-BATCH if sendMonFirst option was selected in the UBX-LOG-RETRIEVEBATCH.
Page 24: Communication Interfaces
3.7 Communication interfaces u-blox receivers are equipped with a communication interface which is multi-protocol capable. The interface ports can be used to transmit GNSS measurements, monitor status information and conﬁgure the receiver.
Page 25: Uart
The NEO-M9N includes two UART serial ports. UART1 can be used as a host interface for conﬁguration, monitoring and control.
Page 26: I2C Interface
3.7.2 I2C interface An I2C interface is available for communication with an external host CPU or u-blox cellular modules. The interface can be operated in slave mode only. The I2C protocol and electrical interface are fully compatible with the I2C industry standard fast mode.
Page 27 NEO-M9N - Integration manual Do not use registers 0x00 to 0xFC. They are reserved for future use and they do not currently provide any meaningful data. Figure 11: I2C register layout 3.7.2.2 Read access types There are two I2C read transfer forms: •...
Page 28 NEO-M9N - Integration manual Figure 12: I2C random read access If the second form, "current address" is used, an address pointer in the receiver is used to determine which register to read. This address pointer will increment after each read unless it is already pointing at register 0xFF, the highest addressable register, in which case it remains unaltered.
Page 29: Spi Interface
Figure 14: I2C write access 3.7.3 SPI interface NEO-M9N has an SPI slave interface that can be selected by setting D_SEL = 0. The SPI slave interface is shared with UART1 and I2C port, the physical pins are same. The SPI pins available are: •...
Page 30: Usb Interface
USB host compatibility testing is thus recommended in this scenario. The NEO-M9N receiver supports only self-powered mode operation in which the receiver is supplied from its own power supply. The V_USB pin is used to detect the availability of the USB port, i.e.
Page 31: Predefined Pios
Table 16: D_SEL conﬁguration 3.8.2 RESET_N The NEO-M9N provides the ability to reset the receiver. The RESET_N pin is an input-only pin with an internal pull-up resistor. Driving RESET_N low for at least 100 ms will trigger a cold start.
Page 32: Timepulse
I/O port. 3.8.4 TIMEPULSE The NEO-M9N module provides a time pulse on the TIMEPULSE pin. More information about the time pulse feature and its conﬁguration can be found in the Time pulse section.
Page 33: Multiple Gnss Assistance (Mga)
The AssistNow Oﬄine service beneﬁts u-blox GNSS receivers that only have occasional internet access. Users request data from the service by specifying the time period for which they want coverage (1 to 5 weeks).
Page 34: Assistnow Offline
(1 day to 5 weeks) and the types of GNSS. This data must be uploaded to a u-blox receiver, so that it can estimate the positions of the satellites, when no better data is available. Using these estimates will not provide as accurate a position ﬁx as if current ephemeris data is used, but it will allow much faster TTFFs in nearly all cases.
Page 35 Key Name Unit/Range Optional Description token String Mandatory The authorization token supplied by u-blox when a client registers to use the service. gnss String Mandatory A comma-separated list of the GNSS for which data should be returned. The currently supported GNSS are: gps and glo.
Page 36 The user's host system must download the data from the AssistNow Oﬄine service when an internet connection is available, and then deliver all of that data to the u-blox receiver. As the total amount of data to be uploaded is large (typically around 100 kbytes) and writing to ﬂash memory is slow, the upload must be done in blocks of up to 512 bytes, one at a time.
Page 37: Assistnow Autonomous
• Optionally it may also download a current set of almanac data from the AssistNow Online service. • The host wants to use the u-blox receiver. • If necessary it uploads any almanac, position estimate and/or time estimate to the receiver.
Page 38 NEO-M9N - Integration manual • A broadcast ephemeris downloaded from the satellite is a precise representation of a part (for GPS nominally four hours) of the satellite's true orbit (trajectory). It is not usable for positioning beyond this validity period because it diverges dramatically from the true orbit afterwards.
Page 39 NEO-M9N - Integration manual 3.9.4.3 Interface Several UBX protocol messages provide interfaces to the AssistNow Autonomous feature. They are: • The CFG-ANA-USE_ANA item is used to enable or disable the AssistNow Autonomous feature. When enabled, the receiver will automatically produce AssistNow Autonomous data for newly received broadcast ephemerides and, if that data is available, automatically provide the navigation subsystem with orbits when necessary and adequate.
Page 40 NEO-M9N - Integration manual • The Save-on-Shutdown feature preserves AssistNow Autonomous data (more information about the SoS feature: NEO-M9N Interface description [2]. 3.9.4.4 Beneﬁts and drawbacks AssistNow Autonomous can provide quicker start-up times (lower the TTFF) provided that data is available for enough visible satellites. This is particularly true under weak signal conditions where it might not be possible to download broadcast ephemerides at all, and, therefore, no ﬁx at all would...
Page 41: Save-On-Shutdown Feature
• The host commands the saving of the contents of BBR to the ﬂash memory using the UBX- UPD-SOS-BACKUP message. • For a valid request the u-blox receiver reports on the success of the backup operation with a UBX-UPD-SOS-ACK message.
Page 42: Power Management
NEO-M9N - Integration manual 3.11 Power management u-blox receivers support diﬀerent power modes. These modes represent strategies of how to control the acquisition and tracking engines in order to achieve either the best possible performance or good performance with reduced power consumption.
Page 43: Continuous Mode
3.11.1 Continuous mode u-blox receivers make use of dedicated signal processing engines optimized for signal acquisition and tracking. The acquisition engine delivers rapid signal searches during cold starts or when insuﬃcient signals are available for navigation. The tracking engine delivers signal measurements for navigation and acquires new satellites as they become available during navigation.
Page 44 NEO-M9N - Integration manual • Tracking state: The receiver continuously tracks and downloads data. Less power consumption than in Acquisition state. • POT state: The receiver repeatedly loops through a sequence of tracking (Track), calculating the position ﬁx (Fix), and entering an idle period (Idle). No new signals are acquired and no data is downloaded.
Page 45 NEO-M9N - Integration manual • The receiver will be forced to stay awake if EXTINTWAKE is enabled and the conﬁgured EXTINT pin is set to "high" and it will be forced to stay in (Inactive) awaiting next search/Fix states if EXTINTBACKUP is enabled and the conﬁgured EXTINT pin is set to "low" (see EXTINT pin control for details).
Page 46 NEO-M9N - Integration manual • After a valid position ﬁx, Tracking state is entered and the ONTIME starts. In other words the ONTIME starts with the ﬁrst valid position ﬁx. • Once the ONTIME is over, POT state is entered. • In POT state the receiver continues to output position ﬁxes according to the CFG-RATE-*. To have maximum power savings, set the ONTIME to zero.
Page 47 NEO-M9N - Integration manual Conﬁg key Description OPERATEMODE Receiver mode of operation POSUPDATEPERIOD Time between two position ﬁx attempts in on/oﬀ power save mode ACQPERIOD Time between two acquisition attempts if the receiver is unable to get a position ﬁx Acquisition MINACQTIME...
Page 48 NEO-M9N - Integration manual 3.11.2.2.5 On time (ONTIME) The ONTIME parameter speciﬁes how long the receiver stays in Tracking state before switching to the POT state (in PSMCT) or (Inactive) awaiting next fix state (in PSMOO). 3.11.2.2.6 Wait for time ﬁx (WAITTIMEFIX) A time ﬁx is a ﬁx type in which the receiver will ensure that the time is accurate and conﬁrmed to...
Page 49 NEO-M9N - Integration manual If the Force-OFF ( EXTINTBACKUP ) feature in CFG-PM is enabled, the receiver will enter Inactive states for as long as the conﬁgured EXTINT pin is set to 'low' until the next wake-up event. Any wake-up event can wake up the receiver even while the EXTINT pin is set to 'low' (see Wake up).
Page 50: Peak Current Settings
NEO-M9N - Integration manual 3.11.2.3.3 Behavior while USB host connected As long as the receiver is connected to a USB host, it will not enter the lowest possible power state. This is because it must retain a small level of CPU activity to avoid breaching requirements of the USB speciﬁcation.
Page 51: Power On/Off Command
ﬁx within a very short time. This is the "hot start". The hot start ﬁx time is given in the NEO-M9N Datasheet [1]. The NEO-M9N supports two kinds of backup modes. These are: •...
Page 52: Clocks And Time
The receiver is dependent on a local oscillator for both the operation of its radio parts and also for timing within its signal processing. No matter what nominal frequency the local oscillator has, u-blox receivers subdivide the oscillator signal to provide a 1-kHz reference clock signal, which is used to drive many of the receiver's processes.
Page 53: Itow Timestamps
Depending on the conﬁguration of the receiver, such "invalid" times may well be output, but with ﬂags indicating their state (e.g. the "valid" ﬂags in UBX-NAV-PVT). u-blox receivers employ multiple GNSS system times and/or receiver local times (in order to support multiple GNSS systems concurrently), so users should not use UBX messages reporting GNSS system time or receiver local time.
Page 54: Utc Representation
NEO-M9N - Integration manual that the probability of the time to be correct is very high. Note that information about time validity conﬁrmation is only available if the confirmedAvai bit in the UBX-NAV-PVT message is set. validDate means that the receiver has knowledge of the current date. However, it must be noted that this date might be wrong for various reasons.
Page 55: Leap Seconds
23:59:58 will be followed by 00:00:00. u-blox receivers are designed to handle leap seconds in their UTC output and consequently users processing UTC times from either NMEA or UBX messages should be prepared to handle minutes that are either 59 or 61 seconds long.
Page 56: Timing Functionality
3.13.1 Time pulse 3.13.1.1 Introduction u-blox receivers include a time pulse function providing clock pulses with conﬁgurable duration and frequency. The time pulse function can be conﬁgured using the CFG-TP-* conﬁguration group. The UBX-TIM-TP message provides time information for the next pulse and the time source.
Page 57 Although u-blox receivers can combine a variety of diﬀerent GNSS times internally, the user must choose a single type of GNSS time and, separately, a single type of UTC for input (on EXTINT pins) and output (via the TIMEPULSE pin) and the parameters reported in corresponding messages.
Page 58 Time pulse signal can be conﬁgured using the conﬁguration group CFG-TP-*. The NEO-M9N module provides only one time pulse pin. Conﬁguration for TP1 applies to this pin. 3.13.1.5 Conﬁguring time pulse with CFG-TP-* The conﬁguration group CFG-TP-* can be used to change the time pulse settings, and includes the...
Page 59 NEO-M9N - Integration manual • pulse length/ratio - Length or duty cycle of the generated pulse, either speciﬁes a time or ratio for the pulse to be on/oﬀ. • pulse length/ratio lock - Length or duty cycle of the generated pulse, as soon as the receiver has calculated a valid time from a received signal.
Page 60: Timemark
NEO-M9N - Integration manual Figure 23: Time pulse signal with the example parameters 3.13.2 Timemark The receiver can be used to provide an accurate measurement of the time at which a pulse was detected on the external interrupt pin. The reference time can be chosen by setting the time source parameter to UTC, GPS, GLONASS, BeiDou, Galileo or local time in the CFG-TP-* conﬁguration group.
Page 61: Security
Figure 24: Timemark 3.14 Security The security concept of NEO-M9N covers the air interface between the receiver and the GNSS satellites and the integrity of the receiver itself. There are functions to monitor/detect certain security threads and report it to the host system.
Page 62: Jamming/Interference Detection / Monitoring
NEO-M9N - Integration manual The spooﬁng detection algorithm monitors multiple observed signal parameters for suspicious changes to identify external manipulation. A ﬂag in UBX-NAV-STATUS message (ﬂags2 - spoofDetState ) alerts the user to potential spooﬁng activity. A detection is successful when a signal is observed to transition from an initially genuine one to a spoofed version.
Page 63: Gnss Receiver Integrity
3.14.3 GNSS receiver integrity 3.14.3.1 Secure boot The NEO-M9N boots only with ﬁrmware images that are signed by u-blox. This prevents the execution of non-genuine ﬁrmware images run on the receiver. 3.14.3.2 Secure ﬁrmware update The ﬁrmware image itself is encrypted and signed by u-blox. The NEO-M9N veriﬁes the signature at each start.
Page 64 The meaning of the content of each subframe depends on the sending GNSS and is described in the relevant interface control documents (ICD). 3.15.1.2 GPS NEO-M9N is designed to receive and track the L1C/A signals provided at 1575.42 MHz by the Global Positioning System (GPS). 3.15.1.2.1 GPS L1C/A For GPS L1C/A signals, there is a fairly straightforward mapping between the reported subframe and the structure of subframe and words described in the GPS ICD.
Page 65 Figure 26: GLONASS navigation message data 3.15.1.4 BeiDou u-blox M9 receivers can receive and process the B1I signals broadcast at 1561.098 MHz from the BeiDou Navigation Satellite System. The ability to receive and track BeiDou signals in conjunction with another constellation results in higher coverage, improved reliability and better accuracy.
Page 66 NEO-M9N - Integration manual 3.15.1.5.1 Galileo E1-B For the Galileo E1-B signal, each reported subframe contains a pair of I/NAV pages as described in the Galileo ICD. Galileo pages can either be "Nominal" or "Alert" pages. For Galileo "Nominal" pages the eight words are arranged as follows:...
Page 67: Forcing A Receiver Reset
NEO-M9N - Integration manual Alert pages are reported in very similar manner, but the page type bits will have value 1 and the structure of the eight words will be slightly diﬀerent (as indicated by the Galileo ICD). 3.15.1.6 SBAS For SBAS (L1C/A) signals each reported subframe contains eight 32-bit data words to deliver the 250 bits transmitted in each SBAS data block.
Page 68: Firmware Upload
• Controlled GNSS start starts all GNSS tasks. 3.17 Firmware upload NEO-M9N is supplied with ﬁrmware. u-blox may release updated images containing, for example, security ﬁxes, enhancements, bug ﬁxes, etc. Therefore it is important that customers implement a ﬁrmware update mechanism in their system.
Page 69: Design
This section provides information to help carry out a successful schematic and PCB design integrating the NEO-M9N. 4.1 Pin assignment The pin assignment of the NEO-M9N module is shown in Figure 30. The deﬁned conﬁguration of the PIOs is listed in...
Page 70: Power Supply
If V_BCKP is not provided, the module performs a cold start at power up. If a host is connected to NEO-M9N, V_BCKP can be partially emulated by using UBX-UPD-SOS functionality. BBR data can saved to the host and restored at startup. See the applicable...
Page 71: V_Usb: Usb Interface Power Supply
Figure below. Figure 31: Minimal NEO-M9N design For a minimal design with the NEO-M9N GNSS modules, the following functions and pins should be considered: • Connect the power supply to VCC and V_BCKP. • If hot or warm start operations are needed, connect a backup battery to V_BCKP.
Page 72: Neo-M9N Internal Components
• Choose the required serial communication interfaces (UART, USB, SPI or I2C) and connect the appropriate pins to your application. If SPI is used D_SEL must be connected to ground. • The NEO-M9N module includes an LNA enabling the receiver to work well with a simple passive antenna.
Page 73: Antenna Design With Passive Antenna
For applications where passive antenna performance is not suﬃcient, the module supports controlling and supplying an external LNA or active antenna. The NEO-M9N has an internal DC block and 50 Ω impedance matching for GNSS signal input, so there is no need to add these components to the RF path.
Page 74 • A series current limiting resistor is required to prevent short-circuits destroying the bias-t inductor. • If the VCC_RF voltage of the NEO-M9N module does not match the supply voltage of the active antenna, use a ﬁltered external supply instead of the VCC_RF.
Page 75: Out-Of-Band Blocking Immunity
It is recommended to verify that the receiver performance is not aﬀected or is at an acceptable level in the presence of interference. Figure 34: NEO-M9N out-of-band immunity level at 400 - 1460 MHz and 1710 - 3300 MHz. CW test signal is used. 4.6 EOS/ESD precautions To avoid overstress damage during production or in the ﬁeld it is essential to observe strict...
Page 76: Esd Protection Measures
NEO-M9N - Integration manual To prevent overstress damage at the RF_IN of your receiver, never exceed the maximum input power as speciﬁed in the applicable data sheet [1]. When integrating GNSS receivers into wireless systems, pay special attention to electromagnetic and voltage susceptibility issues. Wireless systems include components which can produce Electrostatic Discharge (ESD), Electrical Overstress (EOS) and Electro-Magnetic Interference (EMI).
Page 77: Safety Precautions
Figure 36: Active antenna EOS protection 4.6.3 Safety precautions The NEO-M9N must be supplied by an external limited power source in compliance with the clause 2.5 of the standard IEC 60950-1. In addition to external limited power source, only Separated or Safety Extra-Low Voltage (SELV) circuits are to be connected to the module including interfaces and antennas.
Page 78: In-Band Interference Mitigation
NEO-M9N - Integration manual • In-band interference: Although the GNSS band is kept free from intentional RF signal sources by radio-communications standards, many devices emit RF power into the GNSS band at levels much higher than the GNSS signal itself. One reason is that the frequency band above 1 GHz is not well regulated with regards to EMI, and even if permitted, signal levels are much higher than GNSS signal power.
Page 79: Layout
4.8.3 Package footprint, copper and paste mask Copper and solder mask dimensioning recommendations for the NEO-M9N module packages are provided in this section. These are recommendations only and not speciﬁcations. The exact copper, solder and paste mask geometries, distances, stencil thickness and solder paste volumes must be adapted to the speciﬁc production processes (e.g.
Page 80 NEO-M9N - Integration manual 4.8.3.1 Mechanical dimensions Figure 37: NEO-M9N mechanical dimensions UBX-19014286 - R07 4 Design Page 80 of 95 C1-Public...
Page 81: Layout Guidance
NEO-M9N - Integration manual 4.8.3.2 Footprint Figure 38: NEO-M9N suggested footprint (i.e. copper mask) 4.8.3.3 Paste mask Figure 39: NEO-M9N suggested paste mask 4.8.4 Layout guidance The presented layout guidance reduces the risk of performance issues at design level. 4.8.4.1 RF In trace The RF In trace has to work in the middle L-band frequencies.
Page 82: Design Guidance
4.8.4.2 VCC pad The VCC pad for the NEO-M9N module needs to have as low an impedance as possible with large vias to the lower power layer of the PCB. The VCC pad needs a large pad and the decoupling capacitor must be placed as close as possible.
Page 83: Backup Battery
• If USB is used, is there a 1 uF capacitor right near the V_USB pin? This is just for the V_USB pin. • Is there a 1 uF cap right next to the module VCC pin? • Compare the peak current consumption of the NEO-M9N GNSS module with the speciﬁcation of your power supply.
Page 84: Antenna/Rf Input
If a patch type antenna is used, a suﬃcient antenna ground plane is required. 4.9.6 Schematic design For a minimal design with the NEO-M9N GNSS modules, consider the following functions and pins: • Connect the power supply to VCC and V_BCKP.
Page 85: Product Handling
NEO-M9N - Integration manual 5 Product handling 5.1 ESD handling precautions NEO-M9N contains highly sensitive electronic circuitry and is an Electrostatic Sensitive Device (ESD). Observe precautions for handling! Failure to observe these precautions can result in severe damage to the GNSS receiver! •...
Page 86 NEO-M9N - Integration manual As a reference, see “IPC-7530 Guidelines for temperature proﬁling for mass soldering (reﬂow and wave) processes”, published in 2001. Preheat phase During the initial heating of component leads and balls, residual humidity will be dried out. Note that the preheat phase does not replace prior baking procedures.
Page 87 NEO-M9N - Integration manual Modules must not be soldered with a damp heat process. Optical inspection After soldering the module, consider optical inspection. Cleaning Do not clean with water, solvent, or ultrasonic cleaner: • Cleaning with water will lead to capillary eﬀects where water is absorbed into the gap between the baseboard and the module.
Page 88: Packaging
5.3 Packaging The NEO-M9N modules are delivered as hermetically sealed, reeled tapes in order to enable eﬃcient production, production lot set-up and tear-down. For more information about packaging, see the u- blox Package Information Guide [4].
Page 89: Reels
Figure 44: NEO-M9N tape dimensions (mm) 5.5 Reels The NEO-M9N receivers are deliverable in quantities of 250 pieces on a reel. The receivers are shipped on reel type B, as speciﬁed in the u-blox Package Information Guide [4]. 5.6 Moisture sensitivity levels The moisture sensitivity level (MSL) for NEO-M9N is speciﬁed in the table below.
Page 90: Appendix
This section describes important diﬀerences to consider when migrating from NEO-M8 modules to the NEO-M9N module. A design review with a u-blox support team is recommended to verify proper use of the product features.
Page 91 IO output pin or adjust the load accordingly. Table 28: NEO-M9N hardware features compared to NEO-8Q/M8 modules Refer to NEO-8Q, NEO-M8, and NEO-M9N data sheets for details on performance comparison [1]. Table 29 presents a summary of the key software-related changes between NEO-M9N and NEO-8Q/M8 modules, as well as required actions during migration.
Page 92: B Glossary
NEO-M9N - Integration manual Refer to SPG 4.04 release notes and interface description for more information on supported features and messages in the u-blox M9 receiver [3], [2]. B Glossary Abbreviation Deﬁnition ANSI American National Standards Institute Antenna reference point BeiDou Chinese navigation satellite system...
Page 93: Related Documents
M9 SPG 4.04 Release notes, UBX-20036165 Packaging information for u-blox chips, modules, and antennas, UBX-14001652 For regular updates to u-blox documentation and to receive product change notiﬁcations please register on our homepage https://www.u-blox.com. UBX-19014286 - R07 Related documents Page 93 of 95 ...
Page 94: Revision History
Updated description of recording in section 3.3.4. 25-May-2020 jesk Advance information Ordering and numbering of sections updated. Added section 3.1.5 RTCM corrections. Removed old section 4.3.4 NEO-M9N power supply. Updated description of 50 Ω matching in section 4.5 Antenna. 11-Sep-2020 jesk Early production information Updated ﬁrmware version to 4.04.
Page 95 NEO-M9N - Integration manual Contact For complete contact information visit us at www.u-blox.com. u-blox Oﬃces North, Central and South America Headquarters Asia, Australia, Paciﬁc Europe, Middle East, Africa u-blox America, Inc. u-blox AG u-blox Singapore Pte. Ltd. Phone: +1 703 483 3180...

u-blox NEO-M9N Integration Manual

Quick Links

Related Manuals for u-blox NEO-M9N

Summary of Contents for u-blox NEO-M9N

This manual is also suitable for:

Table of Contents