My quad won't play its melody — a troubleshooting checklist
Flashed everything, wrote the melody, and your quad is silent on arm? Work through this list top to bottom — the cause is almost always one of these eight things.
You did everything right. Flashed Bluejay, generated the song, pasted it in, wrote the melodies. You power up the quad and… nothing. Or maybe one motor beeps and the others don't. Or it plays a generic startup tone instead of your song.
Don't panic. Silent-melody problems almost always come down to one of eight causes. Work through them in order — they're sorted by how common they are.
1. The melody wasn't written, only accepted
In the melody editor there are two steps: Accept (validates the RTTTL string) and Write Melodies (actually saves it to the ESCs). It's easy to click Accept, see the green checkmark, and assume you're done. You're not. Click Write Melodies and wait for the confirmation.
2. You're hearing the default startup tones, not your song
Bluejay plays a short initialisation beep sequence on every power-up regardless of melody. If you hear some beeps but not your song, the melody slot might be empty. Re-open the editor, confirm your RTTTL is actually in each slot, and write again.
3. One or more melody strings failed validation
If a single RTTTL string has a syntax error, that one motor stays silent while the others play. The editor usually flags it, but it's easy to miss. Check each of the four slots has a valid string. Our post on common RTTTL mistakes covers the usual culprits — stray spaces, missing name segment, wrong dotted-note order.
4. The melody is too long and got truncated
Bluejay's budget is 128 bytes (~62 notes) per ESC. Paste a 90-note string and the firmware silently truncates it — sometimes mid-note, which can make the whole thing sound broken or cut off early. The converter caps output at the budget automatically, but if you hand-wrote or pasted from elsewhere, count your notes. Keep each motor under 62.
5. Notes are out of the playable octave range
If your song is written very low or very high, the notes get clamped to Bluejay's playable window (roughly octaves 4–7) and can come out as silence or wrong pitches at the extremes. If the song "plays" but you can barely hear parts of it, try an octave shift to bring everything into the 5–6 range.
6. The ESC didn't actually get flashed with Bluejay
Re-read your setup in the configurator. If a motor still shows stock BLHeli_S, the flash didn't take for that one (bad connection mid-flash is the usual reason). Re-flash that ESC, then re-write the melody.
7. A hardware fault on one motor's signal line
If one motor is consistently silent across re-flashes and re-writes, while the others work, suspect hardware. A cracked solder joint on the ESC signal pad, or a motor wire that's barely hanging on, will stop both music and (more importantly) flight commands. Reflow the joint.
8. You're listening in a noisy place
This sounds silly but it happens: motor music is quiet. Indoors next to a fan, or outdoors in wind, a working melody can be nearly inaudible. Before you tear the quad apart, hold it up to your ear in a silent room and arm it. If you hear the song there, nothing's broken — you just have a volume-expectations problem. Our post on field acoustics explains why and what helps.
Still stuck?
If you've worked through all eight and your quad is still silent, the most likely remaining causes are:
- An ESC that's physically fine but in a confused firmware state — flash it back to stock BLHeli_S, confirm it works, then flash Bluejay fresh.
- A flight controller that isn't passing the startup tone through — rare, but some FC configs suppress ESC beeps. Check your Betaflight/Emuflight settings for anything muting ESC startup.
And if you find a cause that isn't on this list, let us know and we'll add it. This checklist grows every time someone hits something new.