-
-
Notifications
You must be signed in to change notification settings - Fork 143
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changing VTX settings from script causes issues with VTX Table #486
Comments
Duplicate of #482 |
In my opinion it's not a duplicate, it is a different issue. I have compiled the firmware with VTX and OSD already. If it can be of any help the VTX is a BetaFPV M03 with SmartAudio |
Does this happen when making the same changes in the betaflight configurator? |
No, it happens only when making changes to VTX parameters using the lua
script from the radio. I've tried changing accelerometer trims and PID
profiles without issues
|
can you try downloading the vtx tables again? https://github.com/betaflight/betaflight-tx-lua-scripts#setting-up-vtx-tables |
Yes, I've tried multiple times both downloading them from the script on the
radio and even generating the lua script from the configurator and copied
it manually on the radio but the outcome is the same, as soon as I do one
change the VTX table is altered and becomes unusable
|
That's strange. I'll have to see if I can reproduce |
If there's something that I can do to troubleshoot the issue just let me
know
|
Is it the setting of a specific parameter that causes the issue? Could you try 4.4.1 and maybe 4.4.0? |
It happened when changing VTX power. I can try to go back to these versions
and let you know
|
I have downgraded to BF 4.4.0 that was the previous release available for
my board, and it happens the same. I've noticed one thing, that if I copy
the VTX table lua script generated by Betaflight inside the script it works
until I change a parameter, but if I download the VTX table from the quad
it downloads a different VTX table that is the wiped one that I found
inside the configurator. Attached there is the Lua script generated by
Betaflight configurator and the lua script that is created inside the radio
if I download the VTX table. And there is the VTX table json saved before
and after the issue.
[VTX Tables.zip](https://github.com/betaflight/betaflight-tx-lua-scripts/files/12501888/VTX.Tables.zip)
|
Seems like the lua scripts end up with the "empty" vtx table after downloading? We'll have to figure out why that happens then. |
@AndreaPro Can you share a diff please? |
For sure! I have tried both with the stock CLI provided by BetaFPV and with my custom settings but I have the same issue. Do you have stock settings for your VTX table? Because the CLI on the BetaFPV website for the Meteor 65 appears to have the same VTX table as mine |
Got the same issue if I download the vtx table or copy the lua script from betaflight to my controller, it overwrites my vtx table. |
Could you please share more infos about radio firmware version, Betaflight version, script version, drone model, etc...? |
Oh ye sure sry, After I try to switch a setting, my VTX table on the flight controller gets overwritten to the same table u shared |
The only thing I can think of is that the payload somehow contains more bytes than it should, and this happens: It's strange because in the BF lua scripts we're only sending four bytes back to the FC |
@tomekste5 Which RX system are you using? |
I am using Express LRS version 3.3 2.4GHz and as a Receiver I use the Radiomaster RP1 |
So we have in common ELRS 3.30 2.4GHz |
maybe try disabling vtx administrator in the elrs lua script. |
I have tried VTX administrator in elrs lua script because the Betaflight script was destroying the VTX table, but I have never used it before discovering this issue |
try disabling it by setting "band" to "off". did this happen with earlier versions of elrs? the payload sent back from the betaflight lua scripts is only 4 bytes, but if more bytes are sent the vtx tables could be reset. not sure where those bytes are coming from. needs more investigating. |
I have tried the Betaflight lua directly starting with ELRS 3.3.0. I will try disabling it but I am sure that the first time that I have noticed this issue I haven't enabled VTX admin yet |
I have never enabled VTX administrator
|
If it's not too much hassle, could you guys please try ELRS 3.0? I'm not saying elrs is the issue, but we need to rule things out. As I said, the payload sent from the bf lua scripts is 4 bytes, but it could be that zero padding or something is added somewhere along the way to the FC. |
There is no target for the internal module of the Boxer radio in ExpressLRS v3.0 |
Done! On ELRS Discord they suggested me to try the nightly of the luascripts, I've tried v20231020.10 but still the same issue with ELRS 3.3 |
Same here. Latest stable v1.7.0 or nightly v20231020.10 wipes VTX tables on save. While in fact my diff contains this: vtxtablevtxtable bands 6 set vtx_band = 5 |
The mcu_id.lua on my SD card \SCRIPTS\BF\VTX_TABLES contains: return { |
Which drone and which ELRS version on TX and RX? |
@AndreaPro home made quad. ELRS 3.3.0 on both TX and RX. |
Which FC? |
board_name OMNIBUSF4SD version |
it probably has something to do with the new MSP VTX code in ELRS 3.3.0 |
updated to 3.3.0 now. All I have to do is start the bf lua and let it download vtx tables, and then they disappear from the FC |
That is not what happens here. iirc just saving a PIDs page with the lua script goes fine. (But i should re-test that when back at home.) |
I just built elrs 3.3.0 without msp vtx support, and now it works fine, so there's definitely something going on in the RX code. downloading vtx tables works, and saving the vtx page works. vtx tables still there. |
this problem is still there on elrs 3.3.1...will there be a fix or should we build our own fw without msp support? using edgetx 2.9.1 / tx16s mark ii btw i am new to this fpv hobby :) ahh...and i also tried to export the vtx table directly to the bf lua script vtx table folder but without any luck... |
@bloudman648 It only affects vtx/vtx tables. Everything else should work. There's not much we can do about this in the betaflight lua scripts. The script is working as it should and only sending the necessary bytes back when setting vtx parameters. The data is being tampered with somewhere else. You could report this issue here too ExpressLRS/ExpressLRS#2452 (comment) |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs within a week. |
I have exactly same issue with this.
|
Any luck with RX 3.3.1?
|
I haven't tried it yet but if no one fixed it in the Betaflight or ELRS code repos I doubt that it will be fixed by itself |
you're right. I guess we stuck with 3.2.1 then |
Perhaps a solution on the horizon ? ExpressLRS/ExpressLRS#2525 |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs within a week. |
Please confirm this is solved with ExpressLRS/ExpressLRS#2525 included |
I haven't tested it yet because I was thinking that the merged commit will become available with the next ELRS update |
Ah okay, just checked, we need version 3.4 to be released for testing. |
Tested today with |
I am using Betaflight Lua Scripts 1.7.0 (I've even tried the nightly), Betaflight Configurator 10.9.0, Radiomaster TX16S with EdgeTX 2.8.5 and a BetaFPV Meteor 75 Pro updated to BF 4.4.2 and I am using ELRS 3.3.0 on BetaFPV Micro 1W TX and on the quad.
If I open the lua script and I adjust some settings in the VTX section and save them and I power off the quad and connect it to Betaflight configurator the VTX table is wiped completely and the settings are not stored. I've tried generating the lua script VTX table from the configurator and retrieving them from the quad but the result is the same. Pratically the VTX section of the script is unusable because after restart the VTX table is completely wiped.
The text was updated successfully, but these errors were encountered: