Commands
Use the shortest command path that matches the documented firmware workflow. When a mode needs setup, follow the prompts shown on first entry.
Result
What it means
The command path is working when the target responds and the firmware prints the expected menu, status or captured data.
Troubleshooting
- Re-enter the mode setup when pins or peripherals are not already initialized.
- Check common ground and target voltage before blaming software.
- Prefer Serial CLI for long captures or high-volume output.
- Repeat the read or capture to confirm stability.
Infrared remote shell FAQ
When is the universal remote shell useful?
Use it for quick tests of common actions like power, mute and volume on supported protocols. Use captured or .ir files when you need exact model-specific buttons.
How should I build an IR command test set?
Start with a small group of known functions, label each capture or code clearly, then expand only after the target reacts consistently. That keeps the shell useful as a repeatable remote bench.
Should I test many IR commands at once?
No. Send one command, watch the target, then continue. This avoids changing device state unexpectedly and makes it easier to know which protocol or key actually worked.