| Symptom |
Solution
|
| Vehicle or Controller does not boot up |
Some SD cards larger than 32Gb do not boot correctly. Use SD cards smaller than 32Gb.
|
| Vehicle or Controller does freeze, crashes or reboots |
Mostly due to power issues (insufficient power). Check your 5V BECs. Add filtering caps as explained in the Hardware section. Use more powerfull BECs. Use separate BECs for the SBC and for the radio cards.
|
| Vehicle or Controller does not work. |
The builtin LED on the Pi boards have the folloing blinking patterns. Few seconds after you power up, the LED should start blinking. Use them to figure out is the Ruby software is working fine or if there was an error detected on the hardware or configuration:
Vehicle:
- LED blinks once every second: All is working fine, no errors detected;
- LED blinks fast, few times (5) every second: An error was detected in the hardware configuration (like no radio interfaces working properly);
Controller:
- LED blinks once every 3 seconds: All is working fine, no errors detected;
- LED blinks fast, few times (5) every second: An error was detected in the hardware configuration (like no radio interfaces working properly);
|
| Serial radio interface or other serial device/USB is not recognized |
If you are using any USB-serial adapters and your serial device (i.e. ELRS radio module, SiK radio interface, etc) is not recognised by Ruby:
- Use only brand name USB to serial adapters or ones with CP2109 or CP2102 chipsets. The USB serial adapters with CH340 chipset are not supported.
- The CP2102 chipsets are the most reliable ones and work in all conditions. The CP2109 might be incompatible with some Pi boards, depending on the manufacturer.
|
| Flight modes are wrong |
Make sure you set the right vehicle type in Menu->Vehicle->General as the flight modes types depend on the vehicle type (car, drone, plane, etc).
|
| Video freezes |
Usually a sign a insufficient power supply. You need a power supply that can deliver more current.
|
| Video freezes after few minutes |
Make sure your USB connections wires are shielded or twisted. Better yet, also solder directly all the wires instead of using USB connectors.
Also, you can try decreasing the CPU clock on the vehicle (from Ruby menu) and increase the CPU over voltage from 3 to 4.
|
| Controller and vehicle start, but controller did not detected the vehicle |
A) If using Raspberry Pi 2B, 3B or 4, try to use different USB ports on the Pi;
B) Or, from the controller: search for the vehicle on all bands.
C) Check if vehicle does boot in vehicle mode (using a HDMI display). On boot, on the vehicle side, the check to see if it should boot as vehicle is successful if one of these conditions is true:
- A camera is attached to the Pi;
- GPIO 19 is connected to 3.3v; (see hardware connections for detailed info)
- A file named "forcevehicle" is detected at boot on the SD Card;
|
| There is visible video latency |
If you have video latency do:
* Decrease video bitrate and/or
* Increase radio bitrate;
If using a HDMI camera, change camera profile to HDMI from Menu->Vehicle->Camera->Profile
|
Strong interferences
(Video has random bad picture) |
You have an undesired strong source of radio interferences near the controller or the vehicle. Shield the radio cards and the CSI camera cable.
|
| RC RSSI Always shows 0 in the OSD |
If you don't have a valid telemetry connection to your flight controller and you are not using Ruby RC link, it will always show 0.
If you have enabled Ruby RC link, it will show the RC link quality of the Ruby RC link.
If you have telemetry link to the flight controller, make sure you configure your flight controller to generate the RSSI value as here: ArduPilot RSSI configuration
Note: Some RC receivers and some RC protocols can't generate a RSSI value that a flight controller could use.
|
Ruby