Support
Troubleshooting and evidence
Separate software behavior, compatibility, wiring, and physical commissioning evidence.
RuntimeRecord the exact runtime version
FirmwareRecord the exact build and board profile
HardwareRecord board and carrier revisions
When reporting a JetFlight problem, include the information that identifies the whole control path:
- Host operating system and JetFlight version
- Machine-definition revision
- Controller and carrier board revisions
- Firmware build/profile
- Drive command and feedback types
- Whether the result came from simulation or physical hardware
- The smallest program that reproduces the behavior
- Relevant logs and the machine state when it occurred
A successful simulation narrows the problem but does not prove wiring or hardware behavior. A merged source change is not proof that the public download contains it. The community forum keeps the report and response public so other builders can follow the evidence.
Reviewed 2026-11-06. Confirm the hardware catalog and current published release before connecting a machine.