Serial Console
screen, picocom, or PuTTY on the
USB serial port at 115200 baud.
How this works
This page is a WebSerial terminal. It speaks USB-CDC to the badge's EAGLE-5 console. No toolchain, no terminal app. Bytes in, bytes out; xterm.js renders the ANSI in between.
Click Activate Ludicrous Speed and pick a serial port. The badge shows up
twice as "Eagle 5"; take the lower-numbered one
(e.g. cu.usbmodem1101, not cu.usbmodem1103). That's the CLI side.
Press Enter to wake the prompt, then type help.
Wrong port?
If the terminal stays dead, you grabbed the higher-numbered port: the RNode KISS / Reticulum channel, which wants framed bytes, not keystrokes. Disconnect and take the lower one.
Privacy
Everything happens in your browser. No telemetry, no logging, no server. The page is static, and the serial bytes flow straight between your USB port and this tab.
EAGLE-5 quick reference
menu: the full command deckhelp/help <cmd>: framed help for any commandstatus: radio + power + link cockpitdiag: preflight pass/warn/fail checklights/lights modes: the wing showradio listen/listen stop: decode RNS framesradio sniff/radio scan: raw frames / spectrum sweepprompt minimal: if the ANSI gets weirdcredits: the open source this badge stands on
Keyboard
- Ctrl-C: cancel current line (badge-side)
- Tab: CLI completion
- ↑ / ↓: command history
- Ctrl-L: clear screen (badge-side)
Buttons in this UI
- break: send Ctrl-C from the panel (when the keyboard isn't focused)
- clear: local clear (badge state untouched)
- save log: download the visible session as a
.txt
Trouble?
No port in the picker usually means a charge-only cable. Swap in a data-capable USB-C one. If it's still missing, you may have double-pressed USR into the UF2 bootloader, where the badge mounts as a disk, not a serial port. Power-cycle to come back.