Skip to main content

Troubleshooting

Start with the symptom you can observe. Apply one change at a time, then retry the smallest Quick Start example.

Connection and upload​

The board does not show up as a port

Some USB cables only carry power. Try a cable you know transfers data, and plug it straight into the computer rather than through a hub. The board's USB-C port goes through a CH340K USB-to-serial chip: wait for its driver to install when you plug the board in, or install the CH340 driver yourself if your computer does not find one.

The upload fails or cannot connect

Check that Tools → Board and Tools → Port match this board. Close anything else that has the port open (Serial Monitor, mpremote or another terminal), because only one program can use it at a time. If it still fails, put the board into bootloader mode and upload again: hold the ESP32-IO0 button, press and release ESP32-RESET, then release ESP32-IO0.

Serial output​

Serial Monitor shows random characters

The baud rate in Serial Monitor does not match the one in the sketch. Set the dropdown in the corner of Serial Monitor to the value in Serial.begin(), which is 115200 for the library examples.

Serial Monitor stays empty

Press the board's ESP32-RESET button with Serial Monitor open: the sketch may have printed before the monitor connected.

The MicroPython REPL does not respond

Press Ctrl+C to stop a running program, then Ctrl+D for a soft reset. If there is still no >>> prompt, close other programs using the port and check that the firmware you flashed is the one for this board's chip.

Power and voltage​

The board resets on its own under load

The supply cannot keep up with the current peaks, and the chip restarts when the voltage dips (on an ESP32 the log says the brownout detector was triggered). Use a USB port on the computer itself or a powered hub, or a shorter cable.

A connected sensor or module does not work

The GPIO pins use 3.3 V logic. A 5 V signal on a GPIO pin can damage the board, so connect 5 V parts through a level shifter, and power each part from the voltage its own documentation asks for.

Nothing lights up, or the board gets warm

Unplug it straight away and disconnect everything wired to it. Look for a short between power and ground, then reconnect one part at a time. The purple PWR LED lights whenever the 3.3 V rail is up, unless jumper JP2 has been cut.

First program​

The upload worked but the LED does not blink

Check that the sketch uses pin 16, the WIFI ON LED, and turns it on with HIGH. The LED is connected through jumper JP4; if JP4 has been cut, the LED stays dark. See the jumpers in Hardware Details.

Board-specific issues​

No aircraft ever appear

Check that the included FXUB1900 ADS-B antenna is plugged into the receiver's IPEX connector, which is the receiver's antenna input.

No aircraft appear even with the antenna connected

The receiver can only report aircraft that are broadcasting ADS-B within its range. Aerobits rates that range at more than 150 km in open space with a 1 dBi antenna. With no traffic in range, the receiver has nothing to report: try again later.

A status LED stays off

Each status LED has its own cut jumper (JP2 PWR, JP3 PPS, JP4 WIFI ON, JP5 ADS-B LIVE). A cut jumper disables only that LED. The WIFI ON and ADS-B LIVE LEDs are wired to ESP32-S3 pins (IO16 and IO15), so your firmware decides when they light. The PPS LED stays off by default: it lights only when a PPS signal from a GNSS source is applied to the receiver's PPS input, and nothing on the board supplies one.

Still blocked?​