Topics created by marian

@marian , I was able to replicate it and when running dmesg, I see the following message:

[ 390.539854] R0: [VosMCThread][02:38:25.067557] wlan: [3231:E :PE ] limProcessAssocReqFrame: 914: Max Sta count reached : 2

Changing max_num_sta in hostapd.conf did not help.

After doing a little bit of digging, it seems like this may be a hardware limitation of the wifi hardware on VOXL1 in SoftAP mode : https://android.googlesource.com/kernel/msm.git/+/android-msm-bullhead-3.10-n-preview-1/drivers/staging/qcacld-2.0/CORE/MAC/src/pe/lim/limProcessAssocReqFrame.c#847 .

It could also be a setting somewhere low level and unfortunately we don't have any information on that. Sorry about that.

The wifi module on VOXL1 is QCA6174.

Alex

@tom Thank you!

@marian Oh yes, thanks for letting us know. When you are using raw frames over USB 2.0 you have to go to a much lower frame rate or else there isn't enough bandwidth to transfer them.

@Chad-Sweet Thanks for your support!

@Alex-Gardner I installed the 0.8 on the voxl, and mow I'm trying to configure the voxl flight deck for a new drone, but it seems to not work at all. I chose the frame type and once applying the modification, the system restart as normal. Once restarted, it ask again to chose the frame type, it doesn't keep the previous settings.

Have you any idea what can be?

The hires channel was renamed to hires_preview, it's identical otherwise

@CY-1992 said in Building new docker image error - Cmake version not good:

ubuntu:20.04

Thanks @CY-1992 is working just fine!

@Alex-Gardner Thank you, is looking good and promising for this use case. I'll give it a try.

@tom Thank you so much!
I was having the exact same problem with @marian.
I could connect to the voxl via ssh but could not via adb shell.
But could solve it after removing the /etc/udev/rules.d/51-android.rules.
Try to remove the file, who are facing the same problem with me.

No answer from Chad, so I put the problem again here hoping someone can advice me how to advance with this topic.

I took a look at the parameters send over, but there is nothing about the rotation of the board. These params are installed on my board, but the results are the same:

whenever I use it for indoor, I do the accel & gyro calibration with ROTATION-NONE, but I have a roll failure detected once I try to arm and I got the visio for local position whenever I use it for outdoor, I add a M8N GPS with compass, I can't calibrate de compass because the position indicated on the QGC is different as the position of the drone if ROTATION-NONE is selected.

By the modalai doc. is ROTATION-NONE that it should be used. Did I get it correctly, or do I need to select another ROTATION value of the board for calibration?

Thanks!

@Chad-Sweet Hi Chad, I go further and for the accelerometer calibration I have another issue.

With Rotation None, the QGC see my aircraft on left side instead of level position, and so on.
When I test to arm and take off, it see the vehicle as turn on right side and have failsafe issue.

If I put Rotation = Roll 270 is much better, and I can arm and takeoff (just simulate for now).
Still, I have two positions that are not right, aka it show the vehicle on:

left side instead of noise up right side instead of noise down

I would really appreciate your help to indicate me the right value for the Rotation to well calibrate this sensor.

Thank you!

Understood. Thank you again!