I did something wrong I think, I want to remove all commits expect the last two how descriped here:
#457 (comment)
But anyting go wrong.
I change from the 9 commits listed only the 3 one I do not want to have to fixup and then I pushed again over cmd git: git push --force-with-lease
But then I see also old comits inside?! Do I have to change the git rebase -i HEAD(削除) 9 to git rebase -i HEAD (削除ここまで)5 and then change pick to fixup only for the one I want to hold anymore?

Please check: https://github.com/betaflight/betaflight/wiki/Betaflight-Contribution#squash-your-commits

I'm trying this now, and I'm not sure I understand how it's supposed to work. I can't change anything. It goes through all retries and the changes won't take effect.

The Adress you can change to select the osd element you want to change.
The you have to go down to the line where the on off points are if all 3 points are off you will not see the element in the osd
If one of it is one you can see the element in the osd, this the first number you can change the position, if you are if you then save the osd element should be on a mother position if you atere in the right osd page.
So my idea was at first only to move a element if you see on the field it's not fitting perfekt lx you like it and you have no pc here.

Here is a Video
https://youtu.be/4ZpBPOYd2qk

I'm trying this now, and I'm not sure I understand how it's supposed to work. I can't change anything. It goes through all retries and the changes won't take effect.

Did you see the video? What system do you have for me it works perfekt, I have a taranis x light pro.

Yes, I saw the video. I have a taranis qx7. Tested with fport and tracer. FC config is minimal. Just rx and osd enabled. I can make changes in the configurator and they show up in the script. It may be that my test setup is a little too minimal.

What I'm not sure if the addresses are always the same or if they depend what's aktivated for example gps, but I do not know how to read out the availible elements due to the config like the betaflight editor do. If anybody can help me there maybe that's better?!

What I'm not sure if the addresses are always the same or if they depend what's aktivated for example gps, but I do not know how to read out the availible elements due to the config like the betaflight editor do. If anybody can help me there maybe that's better?!

They should be the same. I got it working here by clearing the values table before preparing the payload when saving. See one of the comments above for explanation.

I'll just add that this doesn't work with ELRS because MSP_OSD_CONFIG results in a huge payload spread across more than 2 CRSF frames. Not much we can do about it here as it's a ELRS limitation.

I did most changes expect this two:

• Global Variable not fixed, because then on reload it do not work it did not have again the same selected osd element
• Screen Value is needed because it needs >1 https://github.com/betaflight/betaflight/blob/b7b53399abd712476255c3b62099e04c65ba116d/src/main/msp/msp.c#L4155
  --> I moved screen value to x and y -300 so it ́s not visible for the user

I changed all the things, hopefully I get everything ;-). Thx for your good Ideas it helps me to improve my programming skills ;-).

Almost there. Just some minor things that need fixing.
There are probably more optimizations that could be done here with regard to memory use, but it's ok for now I think.

hopefully all is ok now ;-)

Looks good 🙂 Just need to squash/fixup to one commit now

Hopefully all is fine now, I ́m not shure if I did everything right, but I hope only on commit is visible with the right input.