ESP8266 Community Forum

- Thu Apr 07, 2016 8:15 am #45039 Hi,

I flashed successfully a Wemos D1 mini.
Tried to connect and edit a blink program.

Connection to ESP through 192.168.4.1 takes quite of time .
Editing default.bas is nice.
Going through settings Ok.

But running default.bas ends-up with timeout.
If not trying to exit doesn't work.
Reconnect, etc .... is a real hassle.

I tried to reset in beetween, but no change.

Did I miss something ?
Did it happen on other users Wemos D1 mini ?

Many thanks for your help !

Guy from Paris

- Thu Apr 07, 2016 11:21 am #45053 Hi Guy,
I'm the last one that should be offering advice cos it's all new to me and I couldn't even get a driver working for the Wemos D1 Mini, but just to let you know - the new style Serial Dev Kit module that I'm using connects up so rock-solid that I've been leaving it on and connected 24 hours a day, and running various different Basic scripts without even so much as a reboot - so bad connection isn't likely to be an ESP Basic problem.

But program errors can often result in broken connections even though there might not be any other obvious sign of an error. You didn't say what version you flashed, and I remember the Blink example causing me problems in V2 because of the different way of using print with multiple arguments (V2 expects "&" concatenation symbol for multiple arguments, which wasn't needed in the V1 example).

Neither did you mention about saving the script, so that does raise the question of whether ESP Basic was actually trying to run your saved edited script, or perhaps trying to run recently-flashed empty memory.

So have you tried running something else to see if that makes any different to the problems you're having. I've just tried the Web GUI example below and it works on V2 without change (just remember to tidy up the last line to get the final "end" instruction without the last-line clutter which always seems to get appended when pasting using SELECT ALL, ie:

end - See more at: viewtopic.php?f=40&t=4848#sthash.alBXcNNu.dpuf

Can't suggest much else I'm afraid, but perhaps trying to run something different might help you pin things down a bit more.

Code: Select allcls
print "hello world"
let bla = "Test contents of textbox"
textbox bla
button "This is my button 1" [test1]
button "This is my button 2" [test2]
button Exit [TestExit]
wait

[test1]
print "You Clicked on 1"
print bla
wait

[test2]
print "You CLiked on 2"
let bla = "number 2 was clicked"
wait

[TestExit]
cls
print "hello world"
let bla = "Test contents of textbox"
textbox bla
button "This is my button 1" [test1]
button "This is my button 2" [test2]
button Exit [TestExit]
wait

[test1]
print "You Clicked on 1"
print bla
wait

[test2]
print "You CLiked on 2"
let bla = "number 2 was clicked"
wait

[TestExit]
end


Where to get modules?

https://www.banggood.com/custlink/KvGGhGF4wG

- Fri Apr 08, 2016 10:48 am #45111 Ok, without reflashing the Wemos, I tried your program and for sure that changed something: pressing the buttons and changing the message worked fine.

But still a lot of lost connections during the session.

So, I formated and flashed the Wemos by downloading the flasher in wich I expected to have version 2.
It is still version 1.91, so I concluded that the V2 should be the one under the "Unstable Version" button.

Now I have to prepare my home and help my lovely "Half" as we have all our family tomorrow.

I'll continue my testing next week.

Again many thanks as this helped me to sort out a train behind another train (and perhaps behind .....)

Guy

- Sun Apr 10, 2016 3:20 pm #45252 The ap mode dose not work as good as station mode. it is better normally to get the device connected to your wifi. Then i think your problems ill go away.

Serial terminal in the chrome browser see https://serialTerminal.com

http://esp8266basic.com
A BASIC interpreter for your ESP

Working now on Autodrop3d. A 3d printer with automatic part ejection system. https://autodrop3d.com