We have designed new board based on the Ublox NEO-M8N module.
The NEO-M8N Evaluation board makes evaluating the high performance of the u-blox 8 positioning engine simple. With a built-in USB interface for both power supply and high-speed data transfer, the need for an external power supply is eliminated. The NEO-M8N Breakout board is very compact, and it’s user-friendly interface and power supply options make it ideally suited for use in laboratories, vehicles and outdoor locations. Furthermore, the NEO-M8N breakout board can be used with a PDA or a notebook PC, making it the perfect companion through all stages of design-in projects. It’s a fully assembled and tested PCB for the u-Blox NEO-M8N with SMA antenna connectors.
NEO-7N breakout board features:
- 72-channel u-blox M8 engine GPS/QZSS L1 C/A, GLONASS L10F, BeiDou B1 SBAS L1 C/A: WAAS, EGNOS, MSAS Galileo-ready E1B/C (NEO-M8N)
- SuperSense Indoor GPS, -167dBm
- On-board Ultra low noise 3.3V voltage regulator
- USB, I2C (SDA,SCL) and Uart (Tx,Rx)
- SMA antenna connectors
- u-center GPS Evaluation Software
- Extensive visualization and evaluation features
- Supports AssistNow Online and AssistNow Offline A-GPS services
- 1 TTL UART port, 1 I2C port,1 USB port
- Time pulse LED
- Flash memory for firmware upgrade and settings inside in the module (can save setings without battery)
- Battery holder for HOT module start
- Dimensions: 40x18 mm
- Weight 8.1 gram
- Fully assembled and ready to use
NEO-M8N features:
- 72-channel u-blox M8 engine GPS/QZSS L1 C/A, GLONASS L10F, BeiDou B1 SBAS L1 C/A: WAAS, EGNOS, MSAS Galileo-ready E1B/C (NEO-M8N)
- Position accuracy 2.0 m CEP
- Acquisition
- Cold starts: 26 s
- Aided starts: 2 s
- Reacquisition: 1.5 s
- Sensitivity
- Tracking & Nav: –167 dBm
- Cold starts: –148 dBm
- Hot starts: –156 dBm
- Assistance AssistNow GNSS Online
- AssistNow GNSS Offline (up to 35 days)
- AssistNow Autonomous (up to 6 days)
- OMA SUPL & 3GPP compliant
- Oscillator TCXO
- RTC crystal Built-In
- Anti jamming Active CW detection and removal.
- Extra onboard SAW band pass filter
- Memory Flash
- Supported antennas Active and passive
- Odometer Travelled distance
- Data-logger For position, velocity, and time
Comments
Maybe you make sure to set the correct Baudrate and Port with the U-Center.
It is UART1
Protocol out: 0-UBX
Baudrate: 38400
It looks like I missed setting one configuration parameter that controls the messages sent by the GPS.
If you are using U-Center, you need to go to the Message View/MSG(Messages) and set UART1 On with a check in the box between "UART1" and "On" and put a 1 in the box to the right of "On"
I found this Message parameter setting in the 3DR LEA-6 configuration file.
The data stream appears to be pretty stable now in U-Center.
By the way, U-Center does not appear to convert UBX transmissions as far as HDOP and the number of sats.
Regards,
Tom C ArduRover2 Developer
- hide quoted text -
On Thursday, June 26, 2014 1:42:44 PM UTC-4, Tom Coyle wrote:
Hi All,
Since I am using U-Center, and not the MP connected to my Pixhawk which at boot up will send configuration parameters to the GPS, the reason for the data stream glitches, according to Craig Elder, is that the GPS is sending back unnecessary messages that are eliminated by the configuration parameters sent by the Pixhawk. The reduced number of required messages reduces the GPS transmission overhead thus eliminating the glitching.
Regards,
Tom C ArduRover2 Developer
On Thursday, June 26, 2014 12:25:06 PM UTC-4, Tom Coyle wrote:
Hi All,
I have continued experimenting with the capabilities of the CSG M8Q and I may have identified a potential problem with the M8Q.
I have setup the M8Q with the following configuration parameters:
PRT (ports)
UART 1
Protocol out
UBX
Baudrate
38400
RATE (Rates)
Measurement Period
200 ms
Measurement Frequency
5 Hz
NAV5 (Navigation 5)
Dynamic Model
Airborn 4G
Fix Mode
3 - Auto 2D/3D
Min SV Elevation
10 Grad
DGPS Timeout
120 sec
SBAS
Subsystem
Enabled
PRN Codes
EGNOS (EUROPE)
120, 124, 126, 131
With the PRN Codes adjusted to "Other" and 120, 124,126,129, 133-134, 137-138 (3DR LEA-6 configuration file values)
Using this configuration there is definite glitching in the data stream being received by the U-Center as others on DIY Drones have reported Link
Changing the Measurement Period back to 1000ms from 200ms cleared the data stream glitching.
Please be aware that I am doing my testing inside my house, but very close to a window with a view to the sky.
If the M8Q is not capable of operating at a Measurement Frequency of 5Hz, this may be a deal breaker in relation to using it with the Pixhawk.
Comments?
Regards,
Tom C ArduRover2 Developer
No you don´t have to config the GPS. Pixhawk or APM send the correct config data via the tx to Rx line.
I just picked up the M8N from CSGShop. Do I need to load a config file for use with APM/Pixhawk?
Is the Pixhawk able to send the correct Data to the GPS Modul?
And where can I find the correct ublox settings for the GPS Modul to store it via the Ublox center?
THANKS for your testing
Thanks CSGshop for that nicest toy for me in 2014..
http://diydrones.com/forum/topics/arducopter-3-2-beta-testing?comme...
@Northstar,
Use the Terminal Mode and the CLI to test the GPS to see if the Pixhawk can talk to it or that you have the Rx and Tx reversed.
Regards,
TCIII ArduRover2 Developer
yes I soldered the UART pads as well as the pads for 38k
Did you re-solder bottom side jumper from USB to UART mode?
-
1
-
2
-
3
-
4
-
5
of 5 Next