u-center 2: Supports F20 & X20 variants

Enable Debug Messages

To enable debug messages and record a log file using u-center 2, complete the following steps. 

Note: Debug message settings are stored in RAM by default and will be removed after a power cycle. If the configuration is saved to FLASH memory, the settings will persist across reboots. Consider saving your current receiver configuration first, as you may need to restore it later to disable debug messages if reverting to defaults is not an option.

1. Increase the baud rate to 460800 within u-center 2 when using a USB serial connection. If using UART1, configure CFG-UART1-BAUDRATE to 460800 before enabling debug messages.
2. Click Enable Debug Messages button located under Data sources.

Record Using u-center 2

1. After debug messages have been enabled, click on the record icon under Data sources.
2. Select the destination folder and enter a descriptive filename for the .uc2x log file then click Record log file.
   
3. Once you are done recording click the stop icon to end logging (same location as record icon).
   More information about u-center 2 can be found here

Alternative: Record Using Your Host System

The debug message configuration can be saved to the receiver's flash memory, allowing debug messages to remain enabled across power cycles. This is particularly useful for field testing and troubleshooting in embedded or Linux-based environments. Be sure to save your current receiver configuration beforehand, as you may need to revert to the default receiver configuration to disable debug messages.

When recording debug messages, configure the receiver and any serial interfaces used for logging to operate at 460800 baud where applicable. Ensure the host system is configured to capture NMEA and UBX messages. The captured data can then be saved in any format supported by the host system, such as a text or binary log file.

1. On the left navigate bar click Add view -> Message view.
2. In the Message view navigate to UBX -> CFG -> CFG
3. On the right side, check devFlash - (1) then Send to save the configuration to FLASH layer.

Alternative: Enable Debug Messages Using HEX Configuration

If you cannot use u-center, you can use the example Python F9_Enable_Debug.py attached to enable debug messages in Linux or other environments. The script is compatible with F9P, F9R, and F9K modules, and it simply sends a HEX configuration to the F9 RAM layer that enables debug messages. The script will automatically set the baud rate to 460800 to prevent buffer or memory issues. If your setup is limited to a lower baud rate please let us know and we can provide a lighter debug script.

1. Run F9_Enable_Debug.py to enable all debug messages in the RAM layer
2. Run a logging application capable of recording the receiver output without filtering NMEA or UBX messages.
    

Note: We provide a Python sample script for an NTRIP Client that you can use to record logs with the '--ubx' argument. See PointPerfect Downloads.

u-center (Classic) - Supports F9 variants

Enable Debug Messages

1. Increase the baud rate to 460800 within u-center when using a USB serial connection. If using UART1, configure CFG-UART1-BAUDRATE to 460800 before enabling debug messages.
2. Click Enable All Debug Messages on the top toolbar.

Record Using u-center

1. After debug messages have been enabled, click on the "Record" button on the top toolbar.
2. Select the destination folder and enter a descriptive filename for the .ubx log file.
3. Click No. Due to a known issue in u-center, automatic configuration file generation may not function correctly. If a configuration file is needed, create it manually using Tools → Receiver Configuration... → "Transfer GNSS → File".
   
   u-center will begin recording all receiver data to the specified .ubx file.
    

4. Once you are done recording click the Eject button to stop logging.
   More information about u-center can be found Here

    

Alternative: Record Using Your Host System

The debug message configuration can be saved to the receiver's flash memory, allowing debug messages to remain enabled across power cycles. This is particularly useful for field testing and troubleshooting in embedded or Linux-based environments. Be sure to save your current receiver configuration beforehand, as you may need to revert to the default receiver configuration to disable debug messages.

When recording debug messages, configure the receiver and any serial interfaces used for logging to operate at 460800 baud where applicable. Ensure the host system is configured to capture NMEA and UBX messages. The captured data can then be saved in any format supported by the host system, such as a text or binary log file.

1. At the top, navigate to View -> Messages View or press F9 on keyboard
2. Click UBX -> CFG -> CFG
3. On the right side, select Save current configuration.
4. In the lower-left corner, click Send the Message to save the configuration.

Important Notes: 
1. If you need support to troubleshoot an issue, u-blox would need a 30-minute log.  Please share both the logs (.uc2x/.ubx) and configuration file (.txt) generated for best results in your support ticket.  If the configuration file is unavailable, generate one manually using Tools → Receiver Configuration → Transfer GNSS → File. (u-center only)

2. u-blox modules have a default baud rate of 38400. When debug messages are enabled, the amount of data transmitted increases, which may lead to the buffer space being exceeded. When this happens, new messages won't be sent. To prevent this message loss, it is recommended to increase the baud rate to 460800. If the baud rate cannot be set higher, then it is important to carefully select the number of enabled messages to ensure that the expected number of bytes can be transmitted in less than one second. (if you have baud rate limits ask support for help)