Hi Team,

I am running a VOXL2 and trying to connect wifi with this LM843 module. It works with my ubuntu 22.04 System so I can confirm the module is working.
However, using the USB breakoutboard and connecting the wifi module yields no result. It's also not showing up in ifconfig, lsusb or dmesg.

According to the vendor it supports linux kernel 2.6.24 - 5.18.
The drivers provided by the vendor don't compile either due to missing kernel headers (4.19.125). I only find 4.15.xx installed.

Any hint how i can get this running?
Thanks in advance

Phil

@astro_phil
px4 version: 1.14.0-2.0.68

@Alex-Kushleyev
Thanks for the quick reply

system-image: 1.7.8-M0104-14.1a-perf
kernel: #1 SMP PREEMPT Sat May 18 03:34:36 UTC 2024 4.19.125
hw platform: M0104
mach.var: 2.0.0
voxl-suite: 1.3.3

and using px4 1.14.0

both ESCs are running with a 2M baud rate

Hi Team,

I've bought 2 voxl mini ecs, but both have issue spinning up a motor connected on port 0. It seems to be stuck in the synchronisation phase when motor ist jumping back and forth.
However the motor works fine on every other port. I also used the script to set params to the esc and the spin script to check. Also tested with different firmware versions of the voxl2-mini computer with no change.

Any idea what the issue could be ?

Thanks in advance

Phil

@Alex-Kushleyev, Hi Alex

I recently setup a Hexarotor with 2 voxl-mini esc and created the second esc driver as described above. I know that this use case is not officially supported.
But i was hoping you still can help me out on the following issue.

As flying the drone inside a motion capture setup with position tracking, px4 has tough time holding it's position. A similar (in size and weight) quadrotor with the same firmware and setup works flawless.
Flying in stabilized mode / attitude control both drones are fine.

Looking into PX4 uorb rates I noticed running both esc drives reduces the update rate from 800 to 500hz in rate control. Also, some messages as the actuator_output and esc_status get published twice, once per esc, overwriting or setting the others esc status in the message to zero.
Inside the driver itself sometimes the write-read to the esc spikes up to ~2ms of execution time.

Any idea if some of these observations might lead to the bad tracking performance of px4?

Besides that, both escs i use have one bad port that is not able to spin up any motor, it just gets stuck in the synchronization phase and motor is jumping back and forth but that's a different issue.

Thanks, in advance

Phil