Troubleshooting

Troubleshooting Guide

This guide covers the most common setup and configuration problems. Most issues are caused by USB cables, serial port selection, screen driver selection, or unsaved settings.

Troubleshooting

If something is not working, start here. Most issues can be fixed with the correct USB cable, the right serial port, or the right screen driver.

Before you begin

  • Use a data-capable USB cable. Some micro USB cables are charge-only.
  • Make sure no other program is using the serial port.
  • Press Enter a few times after connecting.
  • If you changed settings, enter save before disconnecting power.

Controller is not detected

If the computer does not show a new serial port:

  • Try a different USB cable.
  • Try a different USB port.
  • Close any other terminal or configurator that may already be connected.
  • Reconnect the controller and check Device Manager or your system’s serial port list again.

Terminal opens but nothing happens

If the terminal connects but the controller does not respond:

  • Confirm that you selected the correct COM port or serial device.
  • Disconnect and reconnect the controller, then open the terminal again.
  • Press Enter several times.
  • Make sure the terminal is set to the expected baud rate if your program requires settings.

Characters look wrong or unreadable

If you see random symbols or broken text:

  • Check the serial settings.
  • Use 115200 baud, 8 data bits, no parity, 1 stop bit, and no flow control if your terminal requires settings.

Screen is blank, white, shifted, or upside down

If a display does not look right:

  • Select the correct screen.
  • Choose the correct driver for the display resolution.
  • Use invert, flip, rotate, or mirror if needed.
  • Try a different driver if the screen is blank or only partially drawn.

Wrong colors on a screen

Some screens, especially small round displays, may show inverted colors by default.

  • Use the invert command.
  • If the image is still wrong, verify that the driver matches the display.

Parts of one screen appear on another screen

If you see screen data bleeding into the next display:

  • Use drawdelay 3.
  • If needed, increase to drawdelay 5.

Settings disappear after power is removed

If changes do not stay after reboot:

  • Make sure you entered save after changing settings.
  • Reboot the controller after saving.

Map changes do not load

If new airports, runways, or waypoints are not showing:

  • Enter map save.
  • Reboot the controller.
  • Confirm the map data was entered correctly.

GPS or telemetry data is missing

If the system is not showing expected flight data:

  • Confirm the input source is correct.
  • Check the flight controller connection.
  • Make sure the correct UART speed is selected if using MSP or Mavlink.
  • Verify that the selected input type matches your setup.

Still having trouble?

Use the following pages for setup help:

If the issue continues, use the Contact page and include:

  • Your controller type
  • Your input source
  • Your screen driver
  • The exact problem
  • A photo of the screen if possible

Related Documentation