Hello,

I RMA'd one of my Starling V2's a couple of months ago for a replacement voxl2. Yesterday, I tried to fly it for the first time since getting it back but I am having difficulty getting the RC to talk to the voxl. I'm using the Ghost Atto + Orqa FPV RC combination.

The controller and receiver are paired (the receiver LED switches from red to greenish-yellow when the controller is switched on). Is there another way to verify this?

The output of running "px4-qshell ghst_rc status" on the VOXL2 is shown below. There are no UART RX bytes received, which seems to be the issue. I've checked the output of this command on working drones and they are properly receiving UART bytes. The physical connection looks fine, but I won't know until I check with a scope. Are there other diagnostic tools on the voxl that I might be able to use to help debug this?

INFO  [muorb] SLPI: qshell gotten: ghst_rc status
INFO  [muorb] SLPI:   arg0 = 'ghst_rc'

INFO  [muorb] SLPI:   arg1 = 'status'

INFO  [muorb] SLPI: UART device: 7
INFO  [muorb] SLPI: UART RX bytes: 0
INFO  [muorb] SLPI: Telemetry disabled: Singlewire RC port
INFO  [muorb] SLPI: ghst_rc: cycle interval: 26442 events, 4596.45us avg, min 4520us max 5196us 49.697us rms

Version:

system-image: 1.7.8-M0054-14.1a-perf
kernel:       #1 SMP PREEMPT Sat May 18 00:16:30 UTC 2024 4.19.125
hw platform:  M0054
mach.var:     1.2.0
voxl-suite:   1.3.2

Hello,

I am having trouble communicating between drones in Adhoc mode with the included ALFA WiFi dongle (AWUS036EACS). Has anyone been able to get this to work?

Configuring the ALFA in any which way (iw, wpa_supplicant, etc...) results in the same thing: configure two drones and each radio gives the impression it has successfully switched to IBSS, both share the same cell ID and ESSID. Despite this, they cannot ping. I've verified the configuration methods I am using are working on another set of radios that I have.