Topics created by Ansel Misfeldt

Ok, thanks!

@Zachary-Lowell-0 Got it working. It seems we encountered a documented bug where the defaults were somehow getting incorrectly set to the wrong parameter for RC input protocol when we reset the board to firmware defaults. We were checking the COM_RC_IN_MODE but had always had the RC_IN set to Auto previously. This made everything look fine until it glitched and changed the parameter without us knowing.

In case anyone else runs into it, here is the bug: https://github.com/PX4/PX4-Autopilot/issues/22986

Appreciate the assistance on figuring this out Zachary, we can switch over to Flight Cores and VOXL Flights for this client now which they'll be happy about.

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

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

@Ansel-Misfeldt

FW update feature is working in QGC daily build starting today, no change needed on flight core v2.

23df224f-21ae-4469-b90e-bb255be91ab0-image.png

Hi @liftedsystems
I just saw this now.. sorry for our delays on this...
We respond better when you start a new thread because we ALL get notified of it internally ... Thread replies are on a "best effort" basis to check so we miss some.... but if you wish to do so, please just tag us using the "@" like you did to get Chad and we will see that at a higher level too, but new threads are always the best!
Thanks, and I hope Travis gave you the info you were hoping for!!

@Chad-Sweet Yes, it usually is a good starting point. I do want to mention it took us 3 or 4 separate resets of all related radio settings before this particular glitch went away.

@modaltb Interesting, that's good to know they should be identical (what I assumed), that's why I was puzzled when it didn't seem to work.

On VOXL Flight we're using port J13 and it's always worked perfectly without issue the first time we're wired up a new unit.

I have not tried starting via the command line, but that's a good idea to try.

My best guess is a loose connection in the wiring somewhere or a pin not making good contact on the board. If it should be working the most obviously problem is user error on our part or something not making contact properly.

We ended up sending them one of our VOXL Flight units where we knew it worked perfectly each time instead of using the Flight Core because they were in a rush to get things working.

Thanks for the suggestions!