Table of Contents
Advertisement
9 Troubleshooting
My application (e.g. u-center 2) does not receive all messages
When using UART, check that the baud rate is high enough or reduce the number of enabled
messages. The maximum baud rate of 921600 or 460800 baud rate should be sufficient for most
use cases. If the baud rate is insufficient, GNSS receivers based on u-blox M10 GNSS technology will
skip excessive messages. Some serial port cards/adapters (e.g. USB to RS-232 converter) frequently
generate errors. If a communication error occurs while u-center 2 receives a message, the message
will be discarded.
My application (e.g. u-center 2) looses the connection to the GNSS receiver
u-blox M10 positioning technology and u-center 2 have an autobauding feature. If frequent
communication errors occur (e.g. due to problems with the serial port), the connection may be lost.
This happens because u-center 2 and the GNSS receiver both autonomously try to adjust the baud
rate, if the GNSS receiver has the autobauding enabled. Select a suitable baud rate from the available
list in u-center 2.
Some COM ports are not shown in the port list of my application (e.g. u-center 2)
Only the COM ports that are available on your computer will show up in the COM port drop down list.
If a COM port is gray or u-center 2 is not able to connect to the selected COM port, check if there is
another application running on the computer that is using the same port.
There is no data received from the EVK after connecting the EVK to my application.
Check the interface switch position and ensure that it is set to the communication interface that is
in use. For example, set the interface switch to position 0 or 2 for UART communication.
Do not change the interface switch while the EVK is still powered. Turn off the EVK, change
the interface switch position and turn on the receiver.
EXTINT signal is not working when connecting the EVK using RS-232 UART-to-USB cable.
Disconnect the RS-232 UART-to-USB cable and use the EXTINT signal from the front panel of the
EVK. The USB port on the EVK can also be used for UART communication because of the on-board
FTDI USB-to-UART converter.
EVK-M101/C is not able to use the available FTDI drivers automatically in Linux environment.
EVK-M101/C does not officially support Linux and the following configuration is only provided to
map the available FTDI drivers to the connected EVK, which should be useful in most cases.
Map the FTDI drivers that are available in the Linux system to the EVK device by saving the following
configuration in a new rules file under the
For example:
> nano /etc/udev/rules.d/10-evk.rules
ACTION=="add"
\,
SYMLINK+="ttyEVK%n" \,
RUN+="/sbin/modprobe ftdi_sio" \ RUN+="/bin/sh -c 'echo 1546 0506 > /sys/bus/
usb-serial/drivers/ftdi_sio/new_id'"
RUN+="/bin/stty -F /dev/ttyEVK%n -clocal raw ispeed 38400 ospeed 38400"
UBX-21003949 - R04
C1-Public
/etc/udev/rules.d/ folder.
ATTRS{idVendor}=="1546"
9 Troubleshooting
EVK-M101, EVK-M101C - User guide
\,
ATTRS{idProduct}=="0506"
\,
Page 24 of 30
Advertisement
Table of Contents
