ezio wrote:jhitesma wrote:But I'm still having issues with it thinking it's connected when it's not.
Because I haven't look at it at all.
That's a good reason

And to be fair it could very easily be something about my setup instead of the app based on the other issues I have.
I also noticed in the latest update that it says it now confirms PID writes - but I think there may be something wrong with that.
"Confirms" means that the app displays "Settings saved" when it recives the confirmation from FC. It doesn't check the values etc. The write mechanism is the same as in MultiWiiConf. If the data was corrupted along the way they shouldn't be accepted by FC.
Something strange is going on with your FC. There should be possible to write all zeros by mistake.
Bart
Ah, good to know. My FC is pretty hacked together. It's just a counterfeit mega board I wired some sensors to, it's been through some hard crashes and the oscillator is dented and a couple of the power supply components have been knocked off the board. That it's even flyable kind of surprises me - but I like pushing things past the point of good sense and seeing how much abuse they'll withstand so I'm still flying on it
I haven't looked into the nitty gritty of MSP very much yet but I have seen enough to understand that it should be error tolerant...but I'm not convinced it really is. My link is really sketchy right now. I'm running it over an openLRSng in passthrough telemetry mode. But that means the baud rate over RF is considerably lower than the rate between the FC and RX as well as between the TX and my BT module. I know openLRS is supposed to buffer but I have a feeling there's just too much data and it's overwhelming the RF link. One other sign of this is that my battery voltage readings are always off over the RF link (they're off over straight USB as well...but not nearly as far off) and that I keep getting voice alerts that my mode is changing or that my quad is disarming even though I'm flying just fine. So I strongly suspect I'm getting lost or corrupted packets on my telemetry connection.
I just assumed it couldn't result in something like all zeros being written to my settings due to the error correction I thought the protocol included. Guess I need to do a bit more reading and a bit more experimenting on my telemetry settings.
So you probably don't need to loose any sleep over the connection issues I'm seeing. I'm leaning more and more towards believing the problem is with my RF link and not your app.