#Axisflying Argus F7 AIO target missing from BF configurator

1 messages · Page 1 of 1 (latest)

violet mulch
#

Hi guys, BF Configurator 10.10 cannot auto detect this AIO. https://www.axisflying.com/Axisflying-Argus-F7-AIO-F722-40A-with-Aluminum-shell-p4853437.html

Configurator has detected the board: AXISFLYINGARGUSF7AIO but no official Betaflight target was found

Is there a way to add it? It's being shipped with 4.5.0 pre-installed but Axisflying themselves to not seem to provide the binary anywhere.

Can I just post name/device ID, dump etc. at Github as request?

dull ingot
#

argusf7aio

violet mulch
dull ingot
violet mulch
#

no, I meant the argusf7aio target. but I see in the config.h that it has both. My AIO uses icm which gives me headaches because gyro is noisy and makes the quad twitch mid air 😩

dull ingot
#

then send us 2k logs

violet mulch
#

its on 4.5 already (but pre-installed). got 4k logs if that is ok.

#

i guess that gyro data is not normal in slow turns. quad is mechanically sound and was flying fine with a mamba stack previously

dull ingot
#

4k is too much and could hang stm. make 2k log it has enought data, enable please rpm field/

dull ingot
violet mulch
#

not sure, couldn't test really hard, but it seemed to fly better on 2k blackbox. that reminded me, that when I put the logging to 8k ealier, the drone would behave strangely. disarming would take 1 second or more... maybe logging level does indeed influence flight performance in this case?

dull ingot
violet mulch
#

good to know, I assumed f7 can handle it, because I also assumed f7 is a faster processor. thanks, I'll keep an eye out for it and report back

dull ingot
#

also I asked you to enable disabled fields, but it doesn't matter now, I don't see any major problems other than suboptimal PIDs

dull ingot