search

iNavFlight / inav

INAV: Navigation-enabled flight control software
https://inavflight.github.io
GNU General Public License v3.0
3.18k stars 1.48k forks source link

2.2.1 Smartaudio don't work #5037

Closed yanzen1989 closed 4 years ago

yanzen1989 commented 5 years ago
  1. FC Matek f405-ctr 2.Firmware INAV 2.2.1 3.VTX AKK DVR VTX

Problem with SMARTAUDIO. If i flash two last firmwares smartaudio not work If i downgrade firmware to 2.1.0 and load my config vtx smartaudio SA work stable

What's wrong?

https://pastebin.com/ESrdUDx6

Sorry for my speak, i'm Russian.

issue-label-bot[bot] commented 5 years ago

Issue-Label Bot is automatically applying the label BUG to this issue, with a confidence of 0.87. Please mark this comment with :thumbsup: or :thumbsdown: to give our bot feedback!

Links: app homepage, dashboard and code for this bot.

gregm412 commented 5 years ago

I have the same problem with the furious f35 flight controller and akk fx2 vtx. Can anyone help here?

CertainBot commented 5 years ago

@yanzen1989 you mentioned smart audio but not the VTX. I guess it is an AKK VTX. If thats the case there is already open case somewhere for that issue for quite a long time already. Hope there comes some solution soon.

teckel12 commented 5 years ago

@issue-label-bot[bot] SA 2.1 is not yet fully supported with INAV.

leeph commented 5 years ago

Any indication whether support will be provided in 2.2.2 or whatever the next release will be?

It's a shame to lose vTX control with latest SmartAudio devices.

teckel12 commented 5 years ago

@leeph I haven't got around to building a new model with a SA v2.1 VTx but it's on my list. No INAV 2.2.2 PRs resolve this at this point.

leeph commented 5 years ago

Would it help if you were to be provided with a SA2.1-capable VTX for development, or is it more a time/resources issue?

SA2.1 code in Betaflight4.x is available so I would imagine adding support shouldn't be too onerous.

teckel12 commented 5 years ago

@leeph It's more of a time issue at this point. Also, I believe the SA2.1 stuff in Betaflight was part of a total rewrite of certain related things. So it's not as easy as just copying a few lines of code. Things need to be stripped out and/or refactored.

Jetrell commented 5 years ago

Are you guys aware of #4928 SmartAudio fix by @fiam I'm not sure if its a SA v2.1 fix for iNav 2.3 ?

sirPerna commented 5 years ago

If we can support this by supplying hardware with different SA versions for testing please let us know.

TBS

leeph commented 5 years ago

@sirperna it would be useful to know what SA changes exist in Unify Pro32HV firmware - the change log doesn't mention any but the fact is that SA is completely non-functioning in v1.08 but almost fully functioning in v1.12 beta save for incorrect power levels towards the top end.

sirPerna commented 5 years ago

@sirPerna it would be useful to know what SA changes exist in Unify Pro32HV firmware - the change log doesn't mention any but the fact is that SA is completely non-functioning in v1.08 but almost fully functioning in v1.12 beta save for incorrect power levels towards the top end.

The Unify Pro32 HV does report the supported power levels through SA. In early firmware versions there was a bug where the Unify reported too many power levels which made betalfight not accept it as the amount was bigger then the buffer they offer. We fixed this inside the Unify firmware a while ago.

Also if INAV support the variable frame length it can thread SA2.1 VTX with the SA2.0 standard and they will still work.

putimir commented 4 years ago

Hello all! May I ask if there is someting getting done on this request/issue? Can TBS make the hardware backward compatible with previous versions of SA?

Thanks

CertainBot commented 4 years ago

I would like to know if there is any solution available or if there is some workaround. Might be wrong as I am not following the issue but as far as I know this is solved in Beta

DzikuVx commented 4 years ago

INAV 2.5 bring SA2.1 support