TIMELINE click to seek, shift+click to toggle a breakpoint

LOAD ON THE BADGE

C SOURCE

PROJECT FILE

Studio JSON keeps the editor structure, name and fps. Re-import it from the IMPORT view.

HOW IT WORKS

A sequence is a list of frame blocks. Each block runs at one specific frame, top to bottom, and gives commands to the LEDs. The frame counter advances at the badge fps setting, so at 30 fps a 150 frame sequence lasts 5 seconds.

1. Every block starts with an empty selection. A SELECT in an earlier block does not carry over.
2. SELECT adds LEDs to the selection. RESET SELECTION empties it again inside the same block.
3. A color command applies to every currently selected LED, and owns that LED for its LENGTH in frames.
4. A command keeps running after its own block ends, until it expires or another command overwrites that LED.
5. An LED with no live command is black.
6. When the sequence restarts, every LED and the selection are cleared.

INSTRUCTION REFERENCE

Sizes include the opcode byte. LED_SELECT costs 2 bytes per LED. A frame block costs 3 bytes on top of its instructions (2 for the start frame, 1 for the end marker). The sequence header costs 2 bytes.

RANGES AND GOTCHAS

• Frame counts, start frames and lengths are 16 bit: 0 to 65535.
• R, G, B are 0 to 255. Blink PERIOD is a single byte, 0 to 255.
• H is 0 to 359. S and V are 0 to 100.
• HSV is stored pre-scaled, and the macro truncates: (int)(100 * 2.55) is 254, not 255, because 2.55 has no exact binary form. S=100 and V=100 therefore land one step below full. This studio reproduces the truncation exactly, so the preview matches the badge.
• Only 101 of the 256 storable S/V byte values are reachable from an integer input, so importing hex that was not produced by these macros may round.
• An unterminated frame block makes the badge reject the whole sequence and fall back to the red blink from examples/error.c.

KEYBOARD