-
Notifications
You must be signed in to change notification settings - Fork 2
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
Script is not working with 2.3.15 #7
Comments
Thanks. Probably thinks it's EdgeTX (where it does work) and using an inappropriate serial API. |
Too soon. Should not be that, as the serialbaud API is common after 2.3.12. Leave it with me, I may need more info, just don't know what yet. |
I've modified the way the LUA serial baud rate is set; previously if the config file specified 115200, nothing was done because this was the default. In EdgeTX (and possibly in OpenTX), this is no longer a valid assumption.
Working on EdgeTX 2.7(.1), and seems to be generating messages in companion2.3.15 Can you give the changed files (ltm.lua, LTM/config.lua) from |
Unfortunately no luck. If I try to execute the ltm.lua directly I also get an error message saying : "?:0 attempt to call nill value" |
Thanks for trying.
Otherwise I'm rapidly running out of ideas. I'd prefer not to have to flash my radio back to OpenTX. |
OK, I relented and flashed my TX16S back to OpenTX
In both cases, valid data displayed in mwp via BT bridge. UART1 set to LUA, Max Bauds set to 115k, |
By not working do you mean:
|
Probably because I'm a very occasional LUA developer. |
Apologies, I broke your comment above. |
And apropos the
|
For posterity, here's the comment I erroneously broke, that demonstrates (last line) that the script works with CRSF.
This is the fix in #9 / v0.0.4 |
Since I have updated my TX16S to OpenTX 2.3.15 (from 2.3.10) the script is no longer working. I get no LTM output.
The strange thing is, when I tried your old initial version (without the config file), it is working. If you need more info, let me know.
The text was updated successfully, but these errors were encountered: