Hello CubePilot Support,
I need help recovering a Herelink system that stopped transmitting RC/SBUS after an official firmware update. The system worked correctly before the update and no wiring was changed.
Hardware:
- Ground Unit model: Optimus
- Ground Unit Android serial: 667cbfe5
- Ground Unit operational build: BRU01211104
- Official Mac flasher package installed: FRU01260702, followed by the official OTA update
- Air Unit model: Telepathy Air
- Air Unit Android serial: 8a65aed5
- Air Unit build: AU01260317
- Flight controller: Cube Orange, Air Unit S.Bus out 1 connected to Cube RC IN
Observed behavior:
- Ground Unit buttons are detected locally and change their assigned internal SBUS channels.
- The Ground Unit sends no RC UDP packets to the Air Unit on port 16666.
- The Air Unit radio link is active and 192.168.0.10 can ping the Ground Unit at 192.168.0.11 with 0% loss.
- The Air Unit captures 0 UDP packets on port 16666 while buttons and sticks are operated.
- Air Unit SBUS UART counters remain unchanged (ttyS1 tx=25, ttyS0 tx=25).
- Air Unit rc_service reports zero frames every second and stops both frame outputs.
- Cube Orange receives RC_CHANNELS chancount=0, rssi=255, and channels remain zero.
The decisive Ground Unit boot errors are:
text
mlx90393 spi3.0: start mlx90393 joystick probe
mlx90393 spi3.0: mlx90393 joystick probe failed
mlx90393 spi3.1: mlx90393: js_right probe successful
Then the RC service reports:
text
input device ‘mlx_joystick’ not found.
input device num: 1
Only js_right is created under /dev/input; js_left and the combined mlx_joystick device are absent. A full 30-second power-off did not change the result. Reinstalling the saved joystick calibration also did not change it.
Air Unit configuration appears correct:
text
UnitType=air
sbus_count=2
sbus1_port=/dev/ttyS1
sbus2_port=/dev/ttyS0
sbus1_passthrough=true
sbus2_passthrough=true
rc_inet_udp_port=16666
Please confirm:
- Is Ground build BRU01211104 compatible with Air build AU01260317 for this hardware revision?
- Can a wrong Ground Unit image or driver variant cause the mlx90393 spi3.0 probe failure?
- Which official Ground Unit recovery image/firmware should be installed for Android serial 667cbfe5?
- Is an older matched Ground/Air firmware package available if a rollback is required?
The attached archive contains the complete flash log, Ground kernel/service logs, Air UDP/SBUS measurements, and Cube MAVLink RC test. No configuration was modified during the measurements.
Thank you.