Search results for:

Couple of things:-
Make sure you are running latest build (so if using that build thread you need to be going right to the bottom to get the latest added) but you should be able to ignore module not found warnings. If you are using @Gordons 1.85 Espruino build - that has built in support for ESP8266 - I don't think you will get them (someone jump in if that is not correct).

Also the code you are using looks old, the ESP8266 module API no longer includes some of those methods (as far as I know). All the documented ESP8266 methods can be found here:

http://www.espruino.com/Reference#ESP8266

You'd be looking at the wifi.StartAP() method. You may need the wifi.StopAP() method if it is running at boot. The docs relevant to anything ESP8266 and wifi are here

http://www.espruino.com/Reference#Wifi

As far as I'm aware ..._user2.bin is only used when flashing over wifi. To flash via serial, depending on ES8266 variant you will always need .._user1.bin, boot...bin, and blank.bin.

The flashing command will vary. There's a README in the archive with more info on the variations

Edit

@Wilberforce I didn't realise ESP32 has started to ship! Now who's going to port Espruino :)

Edit: Scrolled down for spec and realise a pre-order. Still "expected June"

He's done Kickstarter successfully already - twice now I think.

That's ace!

Not sure about error but in short term you can require the module directly using a path to it's URI on espruino.com (or anywhere else), or download it and require it from disk.

First approach v.simple:

var WebSocket = require("http://www.espruino.com/modules/ws.min.js")

@dwallersv Odd. With nothing running, on a totally wiped board and to be stuck in the reset loop.. I've read elsewhere that this can be power, or pull up related but if you aren't running anything at all that's unlikely. Potentially a defective NodeMCU?

@dwallersrv @Ducky first thing to do is use 'erase_flash' with esptool.py. Then reflash it. This will clear any saved code.

I think this is related to module size. What build are you using on ESP8266?

When the ESP8266 port started we had 1300 JSVars. We had to cut down the MQTT module to bare basics to get it to load and leave some space for application code.

But there are now some ESP8266 builds out there with 1600 (even 1700 JSVars) and I do wonder if the core module would run in this - I haven't had opportunity to test.

Maybe seek out one of the latest builds - with 1600/1700 JSVars, and try again or try this cut down MQTT module which has worked very well for myself and a couple of others.

https://github.com/olliephillips/tinyMQTT

Thanks @MaBe, I'll catch you in Gitter to ask you about it, rather than hijack this thread :)

Where can we find this 1700 JSVar build? Awesome indeed!

It's not the Pico per se that works or does not with the ESP8266, it's the ESP8266 wifi module that has required slight tweaks to work with the different ESP8266 firmware versions out there.

So you might need to try the different modules, but having said that, you can also change the firmware of the ESP8266 either by flashing via the Pico or via your USB-TTL adapter.

Flashed fine. Anything in particular to test?

@tve 1600! :)

Pretty rough Gordon. It's a pity they felt the need to fork the whole thing when they could have just produced an Espruino compatible board - still not what you want - but a bit more congruent, certainly better than forking and passing off the whole project as their own!

Pic 3 bends your head a bit!!

There is no way of knowing if this is a 'real' 85c or the bogus first value

Ignore first reading since it's always 85C, and report from the next? Assuming you're capturing at intervals a counter var is all needed. Workaround, but works fine for me.

Nice. I like the ClearCmdHistory one. How much memory can this give back? I know it gets run if 'save()' fails, but never thought of it as something to use at runtime. Thanks!

Nice. I like the ClearCmdHistory one. How much memory can this give back. I know it gets run if 'save()' fails, but never thought of it as something to use at runtime. Thanks!

There's an open issue re this, here https://github.com/espruino/Espruino/issues/735 AFAIK pinMode is still required. I set it in the sketches I'm running on ESP8266, although I don't have latest build.

Love it!

Thanks all for the info and tips. Very useful. Had a bash at hard wiring my MQTT temperature controller at the weekend. Made a right mess of it. Wrote off two ESP8266-01 in the process with my Maplin "lava lance"

I'll be investing in something better, and give the Lidl one a miss.

Tell me, does the quality of solder matter, is there a brand those in the know all use?

Also wire, do you just chop up the jumper cables and use those?

Okay, that soldering iron is garbage, and you're an idiot for considering it! (am i doin it right? :-P )

I think you nailed it!

Seriously though, do appreciate anyone that takes the time to offer info that will help me and maybe others move up the curve. I will be looking at the kit you mention.

Cheers.

This looks amazing. Will be following progress!