-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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
Current issues #1
Comments
I have update a new telnet demo, pls have a try. |
Thanks - I will try the telnet . PLEASE, PLEASE fins a way to fix the heal issue, this is SO near to being GREAT firmware. |
Erm, whereabouts is the new telnet demo? |
telnet2.lua in examples folder |
Hmm, up to now nothing - ConnectBOT on my Android tablet says connecting... nothing happening. I have checked I have an IP address setup and I've dumped in your code. Connectbot just says "connecting to 192.168.0.22:2323 via telnet" - the IP address is right... |
Nope - got it to work - it said "Welcome to NodeMci World... So I sent print("Hello") and it died... Connected to.loft-east.IP:.192.168.0.22
|
And again - rebooted, reloaded the new telnet script - connected "Welcome to NodeMcu World".. I sent back print("hello") and the ESP-01 immediately croaked and rebooted. |
How many ram(print(node.heap()) you got when esp-01 started? |
and try to send only "enter" to see if it echo ">" back |
Ok so once I was started up with my init routine etc in there, the heap shows as 18456 On loading your telnet, a call to print(node.heap()) shows 5832 On connecting the tablet..... (it says Welcome top NodeMcu world) if I then try print(node.heap()) again - the board reboots.... so basicalyl doing anything at that point - it reboots.. |
Yes if I hit ENTER only I get a > on the tablet - I can do that many times. But any kind of print - and it reboots. |
I'm only here for another 10 minutes then will continue again tomorrow night - off to see friends. Quite happy to test this to death until it works if that helps... |
change node.output(s_output, 0) to node.output(s_output, 1) to see if there is any output in serial. |
Ok, made that change... Loaded the function. Said print("hi") Hi came up on the serial terminal.... and then it rebooted.
|
In case it helps... this is what I have in power up...use your router and pass in place of xxxx and yyyyy file.remove("init.lua") file.writeline([[function listap(t)]]) file.writeline([[print("Connecting")]]) |
I'm out of time - in on Sunday if that helps...happy to test. |
If only this were open source... |
telnet.lua and telnet2.lua working for me. i think your problem is heap. i think your functions consuming a lot of memory. Welcome to NodeMcu world. ->print(node.heap() )
|
They may well be but if a couple of subroutines are finishing off the RAM then we are in real trouble. |
Lua needs absolutly ram management. |
And that's what I'm counting on the author to fix.. are you able to help, have any ideas? |
I just tried the domain name resolution - and that works - but again - heap management is simply not working. I put a memory check on either side and ran the function several times - here's what happened.
I'm losing 80+ bytes every time. How to get that back? |
same on me. i pressed wrong key last line and ram always running out
|
i think variables can not completely delete and this consuming ram.
|
Well, that's interesting isn't it! |
intresting and alarming. i am using esp8266 mostly temprature logging operation and i am using deepsleep function. (restarts chip every minute) ram restored every restarts but there must be a solution for ram without restart.otherwise we cant use lua for any project. |
Exactly - well, setting a variable to NIL gets memory back;
So that's straight forward enough... but it is usually not that straightforward. my socket listener usually uses no RAM at all but if the chain of communication is broken - maybe the socket server stops part way through... I'm losing serious RAM - which means eventually it will die. There are several circumstances where you lose RAM and given there is so little of it this definitely needs fixing. |
On the other hand - here is how to magic up memory (well, not really but it looks that way)
and at around 3k - the interpreter falls over and the card reboots. |
what is the problem ? Have you any idea?
|
I do... there just isn't enough RAM to do this..wrap it in a file and use dofile to run it... what I don't understand is how you start off with 19k - I don't have anywhere near that amount. |
the dns api has memory leak problem. |
Lovely, I've just finished my meetings for this week and an ESP-03 just turned up on my door - I can feel some experimenting coming on in the morning. Thanks for your work. |
Update to MarsTechHAN's nodemcu-firmware
Followed Vladimir Dronnikov's advices.
Added I/O expander MCP23008 module and two examples: digital output with...
I'm using firmware 0.9.6 build 20150704 on ESP01 to send data over internet, but each tcp call the heap consumes about 500 bytes. The code in the alarm is: conn=net.createConnection(net.TCP, false) |
Use a current build. See #719 for comments on 0.96 builds. |
* File LFS module initial commit * LFS file module update #1 * LFS file module update #2 - doc update and file.stat() returning read only attribute * Implementing file.list() * Fine-tuning `file_lfs` module * Adding `file_lfs` to mkdocs.yml * Implementing file.list() update #1 * Fine-tuning * Fine-tuning #2
* File LFS module initial commit * LFS file module update #1 * LFS file module update #2 - doc update and file.stat() returning read only attribute * Implementing file.list() * Fine-tuning `file_lfs` module * Adding `file_lfs` to mkdocs.yml * Implementing file.list() update #1 * Fine-tuning * Fine-tuning #2
Current issues I'm aware of.. the latest http: server demo, every time it is used, the heap drops - starting at 6k and dropping eventually to 3k at which point the board reboots. The heap management needs sorting other wise any kind of fast polling (remote phone monitoring of output state or similar) would be impossible.
Secondly - - the Telnet demo just fails. Two of us have tested both of these on different installations, same response. REALLY would appreciate any fixes.
Are you planning to use the new SDK?
The text was updated successfully, but these errors were encountered: