See my username. I’ll never get offended at someone asking if I overlooked something obvious.
But yeah, the line for E011 was already un-commented (there has to be a better way to say that).
So, I am just going to include my current config (using the default E011 pid setup as it existed in the repository when I downloaded it).
https://pastebin.com/4Tq0GGXN (EDIT for future visitors: << THIS IS THE WRONG FILE, SEE THIS ONE https://pastebin.com/8xsSUvAZ )
But, in its current configuration I have it flying in Race Mode using the stock TX. I did not manage to get Rates working however. When compiling, it threw errors every which way I thought of to configure the line, but I was in a hurry and probably overlooked something obvious.
My VM with STlink and uVision imploded on a forced windows update so I had to rebuild it and lost most of my play time to that today. I’ll find time to dig in and read through some of the files soon and better familiarize myself with the changes.
I am liking the new config layout BTW, and Racemode is everything I hoped it would be.
I don’t know where I found this, but one of the SIlvers mentioned it I think in a thread for setting the TX power specifically for the BLE app. The comments are my own, and based on a quick test and no experimentation (I didn’t test it at 7, or 0, just 4).
// 0 - 7 - power for app
//#define TX_POWER_GENERAL 4 // enable this when using BLE_APP for telemetry. Perhaps set higher than 4. Touch antenna to give it signal, or touch antenna to metal to extend it to connect to app, or set quad directly on phone.
That might be something worth including in the config (with a better description). I could also be totally wrong about it doing anything.
I removed the buzzer from my usual TX, but I have a spare that is completely untouched, and I can test in the future if needed with that if there is a code change to remove that maddening beeping. Personally, I’m fine with just removing the buzzer.