Was testing out the latest opentx nightly for a different reason and I saw I was getting a memory error. Seems to happen after paging through a few lua screens.
Script Syntax Error
BF/ui.lua:335
not enough memory
@mikeller Looks like the Jenkins build didn't have the -s switch for luac. Should we do an increment release with the current master and include a better build, or should I just update the release zip to contain a build using -s?
@codecae: No problem, we are still in the process of getting this set up. I would say there have been a couple of pretty significant bug fixes since 1.0, so a release 1.0.1 would be in order. (Also, we should totally move to SemVer (https://semver.org/).)
One of the things in SemVer that is sometimes overlooked, but in my opinion is a crucial part of it is
Once a versioned package has been released, the contents of that version MUST NOT be modified. Any modifications MUST be released as a new version.
Breaking this rule will create a lot of confusion and frustration amongst users ('I tried v1.0, it did not work, why would I try it again') for no benefit at all (there is an unlimited supply of version numbers, and they are free ;-) ).
I also tested it with opentx-x9d+-noheli-lua-en-2.2.2 and BF scripts: bf-tx-lua-1.0.2.zip and have this issue.
Thing is, if I go directly to the lua script page after powering the tx ON, it works great. But, if go to that lua page after I, for example, edited settings on my model, it shows this error on page 1.
(I edited "x9pre.lua" so VTX is 1st page)
I got this working.
I have re-flashed Opentx-x9d+-noheli-lua-luac-en-2.2.2 and BF scripts: bf-tx-lua-1.0.2.zip
the change from my previous try is not modifying any files of the scripts.
As to JB's youtube video, he says there are two options to modify the order of the pages. The second one, modifying x9pre.lua, and moving vtx to the top, seem to be making the issue for me.
@Lazy8onez: Did you recompile the scripts after modifying them? If not, uploading changed source code will force recompilation on the TX, which would explain why this does not work properly.
@Lazy8onez: My suspicion is that the on-board compilation is less optimised than off-board, so compiling it before installing will have a better chance of working.
@Snake675: Part of the seemingly inconsistent behaviour that gives some users errors for things that work for others could stem from the 'pick and choose' build on the fly system that OpenTX uses to build their firmware - there are over 1000 possible permutations of the every 'release' of OpenTX that users can install, all of which probably have a different RAM consumption...
You are correct because usually a build of your own fw on opentx companion
for just Lua script extensin will solve this issue, thats how I solved it
for me. maybe a note or installation instruction on the Lua scripts release
page would probably help...at this point thou this error can still come up
because of what Michael Keller said about many builds
On Sun, Sep 16, 2018, 6:59 PM Michael Keller, ***@***.***> wrote:
@Snake675 <https://github.com/Snake675>: Part of the seemingly
inconsistent behaviour that gives some users errors for things that work
for others could stem from the 'pick and choose' build on the fly system
that OpenTX uses to build their firmware - there are over 1000 possible
permutations of the every 'release' of OpenTX that users can install, all
of which probably have a different RAM consumption...
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#97 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AKlVsnhNq6vbJPe8fm_f5S-dXJY15VJ5ks5ubtftgaJpZM4QlQLY>
.
@frizzle101101 & mikeller
Yes. But I wonder if a own fw without luac helps if you want to open the BF scripts by telemetry screen. If not, I would rather still stick to the previous version of OTX...
Activity
codecae commented on Nov 21, 2017
@brycedjohnson did you download the source or use the release zip file?
brycedjohnson commented on Nov 21, 2017
@codecae Release zip file. Should I try the source?
codecae commented on Nov 21, 2017
no the release is the smallest in terms of memory. Which page is loading when you hit the limit?
brycedjohnson commented on Nov 21, 2017
On the 4th or 5th page in. Weirdly one time it just worked and I didn't have any issues until I rebooted the taranis.
codecae commented on Nov 21, 2017
Would you mind trying this zip?
http://null.eastus.cloudapp.azure.com/job/Betaflight%20Lua%20-%20X7,%20X9,%20X9D,%20X9D+,%20X10,%20X12/24/artifact/obj/*zip*/obj.zip
brycedjohnson commented on Nov 21, 2017
That seemed to fix it! Tried it like 3 times and it worked everytime. Thanks!
brycedjohnson commented on Nov 21, 2017
Want me to close this issue or want to close it when you reference whatever fix you did? Thanks for the quick help!
codecae commented on Nov 21, 2017
I'd like to leave it open for tracking purposes.
Glad it helped you :)
@mikeller Looks like the Jenkins build didn't have the -s switch for luac. Should we do an increment release with the current master and include a better build, or should I just update the release zip to contain a build using -s?
mikeller commented on Nov 21, 2017
@codecae: No problem, we are still in the process of getting this set up. I would say there have been a couple of pretty significant bug fixes since 1.0, so a release 1.0.1 would be in order. (Also, we should totally move to SemVer (https://semver.org/).)
One of the things in SemVer that is sometimes overlooked, but in my opinion is a crucial part of it is
Breaking this rule will create a lot of confusion and frustration amongst users ('I tried v1.0, it did not work, why would I try it again') for no benefit at all (there is an unlimited supply of version numbers, and they are free ;-) ).
David-VG commented on Nov 21, 2017
I am not sure if it's the same bug or not, but I am using OpenTX 2.2.0 on a Taranis X9D:
Script syntax error
TELEMETRY/bf.lua:10
not enough memory
I get this with the release 1.1 and the file http://null.eastus.cloudapp.azure.com/job/Betaflight%20Lua%20-%20X7,%20X9,%20X9D,%20X9D+,%20X10,%20X12/24/artifact/obj/*zip*/obj.zip
But... i am using FPort :P
David-VG commented on Nov 21, 2017
Also disconected but switching between pages I get at the VTX page:
Script syntax error
BF/ui.lua 335
not enought memory
David-VG commented on Nov 21, 2017
As a little tip: I am using 2 telemetry scripts, one is the betaflight tx lua scripts and the other one: https://github.com/tozes/taranis_telemetry
I am not sure, but maybe betaflight tx lua scripts needs ALL of the available memory.
raphaelcoeffic commented on Nov 21, 2017
@David-VG yes, definitely! but you could use the one-time script (in /BF/bf.lua) for configuring, and the other as a telemetry script for flying.
raphaelcoeffic commented on Nov 21, 2017
Or just buy yourself a brand new shinny X10: no issue with memory there ;-)
David-VG commented on Nov 21, 2017
I dont get Memory errors that way, (running BF.lua manually). But just wanting to warn about the memory issues. Thanks @raphaelcoeffic
131 remaining items
OZamirO commented on Aug 7, 2018
I also tested it with opentx-x9d+-noheli-lua-en-2.2.2 and BF scripts: bf-tx-lua-1.0.2.zip and have this issue.
Thing is, if I go directly to the lua script page after powering the tx ON, it works great. But, if go to that lua page after I, for example, edited settings on my model, it shows this error on page 1.
(I edited "x9pre.lua" so VTX is 1st page)
Saschabrix commented on Aug 13, 2018
Good morning,
I have the same issue as the user Florian Galler.
Opentx-x9d+-noheli-lua-en-2.2.2 and BF scripts: bf-tx-lua-1.0.2.zip.
Same Issue,
Script Syntax Error
BF/ui.lua:335
not enough memory
OZamirO commented on Aug 13, 2018
I got this working.
I have re-flashed Opentx-x9d+-noheli-lua-luac-en-2.2.2 and BF scripts: bf-tx-lua-1.0.2.zip
the change from my previous try is not modifying any files of the scripts.
As to JB's youtube video, he says there are two options to modify the order of the pages. The second one, modifying x9pre.lua, and moving vtx to the top, seem to be making the issue for me.
LIAUTFAM commented on Aug 13, 2018
Yep worked for me too... great to see not just me!
Try this, per Lazy8onez and my post above, if you have this problem, and report if successful.
mikeller commented on Aug 14, 2018
@Lazy8onez: Did you recompile the scripts after modifying them? If not, uploading changed source code will force recompilation on the TX, which would explain why this does not work properly.
floriangaller commented on Aug 15, 2018
I got it also working... my mistake seemed that i used the opentx version without luac...
OZamirO commented on Aug 16, 2018
@mikeller, no I did not
mikeller commented on Aug 16, 2018
@Lazy8onez: My suspicion is that the on-board compilation is less optimised than off-board, so compiling it before installing will have a better chance of working.
Snake675 commented on Sep 9, 2018
@Lazy8onez: Did you call the luac script by menu (as done by jb on his youtube video) or from the telemetry screen?
OZamirO commented on Sep 10, 2018
@Snake675
Telemetry screen.
Pigost commented on Sep 11, 2018
I've also got "script syntax error FB/ui.lua: 335 not enough memory"
Snake675 commented on Sep 14, 2018
I hope this issue will be fixed soon for shure. Some of us seem to have no errors but others do. So what is going on?
mikeller commented on Sep 16, 2018
@Snake675: Part of the seemingly inconsistent behaviour that gives some users errors for things that work for others could stem from the 'pick and choose' build on the fly system that OpenTX uses to build their firmware - there are over 1000 possible permutations of the every 'release' of OpenTX that users can install, all of which probably have a different RAM consumption...
frizzle101101 commented on Sep 16, 2018
Snake675 commented on Sep 17, 2018
@frizzle101101 & mikeller
Yes. But I wonder if a own fw without luac helps if you want to open the BF scripts by telemetry screen. If not, I would rather still stick to the previous version of OTX...