Just trying to come up with a way to test and setup your great script on the bench without having to run my transmitter for long periods of time.Īs I said my final testing is done on a real radio, I don't feel the need to test the script with simulated real data in companion.Īnother big issue is that passthrough telemetry is way richer than what companion can simulate so there would be no way of properly testing the script. What editor are you using?ĭon't get me wrong please! I am not putting you or your methods down at all. If I could edit the script I would definitely give it a try, but when I read yappu into my lua editor it just shows garbage. Instead of attempting to get sensor data from a non existing passthrough stream, it would read it using the more commonly used method. That's why I asked if there was a configuration in the script that might let one run it in the simulator. I have been hacking away at lua scripting for quite a while using this command with no problems. I can see where passthrough might be faster, but for testing in the simulator speed isn't as important as it is at the flying site.Īs for getting data from the simulator, other lua scripts use commands to read data from the simulation ( getValue) and act upon that data. Preferably use the latest version of your TX firmware (OpenTX or EdgeTX) Between flights (before armed), long-press Enter/dial and select Reset. There's some bugs in pre-release and release candidate versions that cause Lua Telemetry to crash. The thing I hate is having my transmitter on for long periods of time while testing. If you have any issues, first make sure you're using the release version 2.2.2+ of OpenTX.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |