Troubleshooting
Work down the list for your symptom. Each fix starts with the most likely cause.
I can’t reach the web page
Section titled “I can’t reach the web page”WiFi is off by default. Close the WiFi switch (GPIO1 to GND) and power up, or power up and then hold BOOT for 3 seconds. Then join DROIDFX_xxxx and open http://192.168.4.1/.
If the serial log (115200 baud) says WiFi is starting but you still can’t connect, the board may be set to join a home network it can’t reach. It comes back on its own network if it can’t join; if not, a factory reset returns it to its own network. See System, WiFi & password.
I forgot the password
Section titled “I forgot the password”Power the board on, then press and hold BOOT within 3 seconds and keep holding for 10 seconds; the serial log says when the password is cleared. Or connect over USB and type clearpw into the serial console at 115200 baud. Restoring a backup won’t help: backups never contain the password.
R/C Monitor shows no channels
Section titled “R/C Monitor shows no channels”- Check the S.BUS pin is set on Pin Assignment, and that you restarted after saving it: that pin takes effect at start-up.
- Check the receiver is powered and bound to your transmitter.
- Check it’s sending S.BUS, not PPM or PWM.
The radio’s fine, but nothing lights up
Section titled “The radio’s fine, but nothing lights up”Two things gate every light:
- The LED master switch must be on. Watch its channel on R/C Monitor while you flip it.
- The light needs a reason to be on: Always On, or a button (or sequence, Startup, Idle) that uses it.
With the transmitter off, only Bench mode or Display mode lights anything, and Display mode not if its Lights is set to Off.
An effect runs the wrong way, or in the wrong place
Section titled “An effect runs the wrong way, or in the wrong place”The shape doesn’t match the wiring. Run Identify on that light (first pixel red, last blue, a white dot stepping between) and compare with what you drew. The pieces on the Shape tab must be in the order the data actually flows. If the shape is right but the motion isn’t, check the layer’s Moves setting. See NeoPixel shapes.
I changed the pixels or the shape, and nothing happened
Section titled “I changed the pixels or the shape, and nothing happened”Shapes, pixel counts, the LED type, RGBW and LED pins all apply as soon as you save. The save’s message says Applied, or why not: too little free memory for that many pixels, or a fifth NeoPixel light (four can run at once). Either way nothing changed; fix that and save again. Applied but still dark? See Nothing lights up.
Two paired lights flash together
Section titled “Two paired lights flash together”Pairing is set on the first light’s Hardware tab with Pair with, and only works for plain lights, not NeoPixels. Check the pattern really is two-tone, like Police Alternate or Wig-Wag; a one-tone pattern has no opposite half to give the partner.
No tracks detected
Section titled “No tracks detected”Check the sound module’s power, its two wires to the Audio pins on Pin Assignment (crossed over, TX to RX), and its SD card. The Audio board line on Droid Config’s Sound section updates by itself as soon as the module answers.
A button does nothing
Section titled “A button does nothing”Check its behaviour on Button Pad, that the LED master switch is on, and the link status at the top of the page. With the transmitter off, turn on Bench mode. On pages 2 and 3, see the next item.
Pages 2 and 3 press page 1’s buttons
Section titled “Pages 2 and 3 press page 1’s buttons”DroidFX doesn’t know which page the radio is showing: set Button page on Droid Config to the channel the ETHOS widget’s DroidFX Page is mixed to. See The ETHOS widget.
The pad file doesn’t appear on the radio
Section titled “The pad file doesn’t appear on the radio”It must sit in a pads folder next to the widget’s cfg_….txt files, on whichever storage the widget is installed on (radio or SD card). See The ETHOS widget.
A setting reset itself after an update
Section titled “A setting reset itself after an update”That setting’s storage changed, so the old copy couldn’t be read safely. The board restores it from its config.json mirror on the next start-up: restart once and check again. If it’s still wrong, restore your backup from Firmware → Backup & Restore.