Can you run the following after boot and compare what you see on a board with working wifi and non-working one:

dmesg | grep wlan

There should be a bunch of wlan-related messages and you could diff the output between the two boards to help narrow down the issue.

Alex

Since you are in the voxl-flight category, I'll assume you are using Flight Core v1. If so, here are the details https://docs.modalai.com/flight-core-firmware

@jskard Hi, how did you solve the first issue above? I am having the same problem. My second calibration does not ring as well. And my first calibration took 30 minutes but the jinggle doesnt stop.

I had the same issues but even with different lighting, I cannot get it to work. I managed to calibrate the tracking camera but not the stereo. Does anyone have any idea how I could try to fix this?

I have the same problem: The reprojection error is to large for the stereo cameras and the calibration fails.

@rdjarvis Woot! Enjoy!

@skl1g14 , very nice!! Thank you for documenting your configuration and results!!

@JP-Drone VOXL Flight doesn't handle cameras any differently than VOXL so that is a bit surprising to me that it would work on one but not the other as they are they same hardware and software

Express LRS does work via the above wiring on VOXL flight after testing 👍 in Q Ground Control

@Alex-Kushleyev thank you for your response, this answers my question!

@boga Sorry, yes, I was referring to VOXL 2.

@stevedan @bensusana I'm also facing this issue. Have you been able to solve this?

@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

I tried swapping the tof camera with a spare one I had around. The spare tof worked immediately without issue. I then disconnected the spare tof, configured the camera server with only hires and tracking (with no connected tof camera, which worked fine). I then tried to plug back in the original tof and it started working again. So nothing changed, just unplugged and plugged back the tof camera and reflected the changes by configuring the camera server accordingly, weird...

@LucasW to answer my own question, VOXL supports 5 GHz. This can be verified by running iw list and looking at the supported channels.

The /data/misc/wifi/wpa_supplicant.conf file does not seem to take effect when trying to specify frequencies, for instance (for 5 GHz channels 36, 40, 44, and 48:

country=ch ctrl_interface=/var/run/wpa_supplicant network={ ssid="my-ssid" bssid=00:00:00:00:00:00 freq_list=5180 5200 5220 5240 scan_freq=5180 5200 5220 5240 proto=RSN key_mgmt=WPA-PSK pairwise=CCMP TKIP group=CCMP TKIP psk="my-pwd" }

The only way I found to connect to 5 GHz is to disable the 2.4 GHz radio entirely on the router. Otherwise, the connection defaults to 2.4 GHz.
On the router, it is also better to set a fixed channel (e.g., 36) rather than letting it be automatic. In auto mode, the robots could not connect systematically to the network.

Note also that my question was wrong in the sense that the hostapd.conf files are used to generate the access point, not to connect in station mode.

These are maybe considerations that could be added to the technical doc @Chad-Sweet ?