Search results for:

Was going to test @Robin, but that link to travis/master is holding 1.87 builds when I go look.

Are all custom builds still using this FTP resource I wonder.

Edit: Yes, they are :/

@Robin if you can link to the firmware version, be happy to test.

I have an older version of esptool which works perfectly. But flasher.js might help you get some firmware onto your board while trying to resolve esptool issues. Don't have a link but Google will.

@navas thanks, but wasn't me. A couple of pull requests have improved it - authors mentioned in the credits.

Great to hear it's better though. Still fairly small at 1.45kb too :)

It's passed at the end of the request like this:

var options = {
...
}
var data = JSON.stringify({"key":"value", ...});
require("http").request(options, function(res)  {
   ...
}).end(data);

Replied on Gitter. It's not a good idea to post same question in multiple places in the forum. One post will generally get you all the help you need in here. More only confuse the discussion.

Replied to message on Gitter

I thought that too, but apparently it's coming in the next firmware release. You can get a travis build now with it included. @MaBe has more info

Nice @MaBe. Share the files!

Edit: I should have scanned up the thread a bit - they are there!

Ah so setIP() is coming. That explains it!

If I follow, you mean you can't consistently find it? Well you can jump on your router and reserve the IP address? That's what I do. Next time it boots you'll know its IP which is great for servers and connecting over Telnet.

That ```setIP()``` function shouldn't be in the docs - it isn't implemented.

Your module not found message is not unusual. To test loaded, load the above code in the IDE from right hand side. Then in left hand side key:

wifi.getStatus();```

You should get a return from that to indicate module was found and loaded and then can proceed to connect and subsequently save your wifi settings for easy connect at boot.

Does your Pico have a white sticker with a number on top of the processor? You can also getSerial() to return the serial number of your Pico. I'm only speculating but maybe either or both of these could be related to board revision based on @gordon's production records.

reset() gives you it under the Espruino banner.

Are you using the wifi module or serial to test. If the module ensure the correct one, there are a couple, since internals have changed to accommodate firmware revisions. If no joy try AT calls using serial to test.

Also is capacitor big enough, docs use 47uf and I used 100uf i think.

It's a while back but in my case think I had duff firmware, and flashing resolved.

Yes, the STP file looks to be good. I'll send over a PR with another STL

Dev boards like NodeMCU and D1 Mini do. They don't respond as BTN but...

Started a print on bottom.stl and hadn't clocked the subtle camber on the design in the file - so that went well :) I look to be 10 - 15 degrees out. What's the correct adjustment to match it to an axis.

IFTTT maker channel needs HTTP requests, so you'll need a proxy of some description between your Puck and the IFTTT service. There's an Espruino hub that's designed to run on Raspberry Pi 3. It offers a HTTP Proxy option. You could use Web Bluetooth but you'd need to script it. I started down this road with this project, but haven't so far go to the proxy piece, and maybe won't.

It's also worth evaluating if you need a Puck for your use case. If you want to communicate over the Internet maybe Espruino Wifi or Espruino on ESP8266 would be a more natural fit.

Thanks - got it. Bad download

Just looking at the files. Oddly I can't load them into Slic3r or Fusion 360. They load. But there's nothing there.

Edit: Ignore, must have been a bad download first go

However the design files are online

Excellent, I wondered if you'd made these available. Thanks!

Only suggestions to check

1) Puck will not advertise once connected to anything else. If your Mac Pro has it, your Mac Mini can't see/connect.

2) Mac OS versions. Are they the same? Support for BLE might not be same.

AP+STA mode is the default for Espruino on ESP8266.

From 56 it's no longer experimental -it's a default feature.

I've had some decent results with this over MQTT, the Mosquitto browser client (via websocket) library is much better than I'd hoped for.