-
-
Sorry I wasn't clear, I added the edit to clarify I wasn't suggesting the Pico was faulty since I can get it into bootloader mode - but I can't see it in terminal regardless of mode. The board I plugged in and could see (to make sure it wasn't me) was my other Espruino - the standard sized board not the Pico.
Good memory - previously I was struggling with the Chrome IDE on 10.6.8 (on my other Espruino) but could always use with the screen command.
-
Similar issue. Just got to playing with my Pico and cannot see it in Terminal using:-
ls /dev/tty.*
Mac 10.6.8 here too. Device appears to be recognised when plugged in and is listed in the System Report.
To check I wasn't making an error I connected my Espruino board, and the device was detected fine using the same command.
Edit: Was able to get Bootloader mode, so device is there.
-
-
-
For receiving webhooks without messing with firewalls etc use a public webserver to receive the request then poll that server for the data? My example is PHP - maybe be better in Go or Node.js, depending on how realtime you needed the thing to feel?
<?php const PRIVATE_KEY = "my_private_key"; // Authenticate if(!@$_REQUEST["key"] || $_REQUEST["key"] !== PRIVATE_KEY) { header('HTTP/1.0 401 Unauthorized'); echo 'HTTP/1.0 401 Unauthorized'; die(); } // Handle request if($_POST) { // Update data and write to a file - validation maybe - but it should be data you expect file_put_contents('data.espruino', json_encode($_POST)); } else { // Get data from file, set headers and display header('Content-Type: application/json'); echo file_get_contents('data.espruino'); }
-
@Gordon I did wonder if it might be worthy of a more prominent announcement. Glad to help!
-
-
-
-
Oddly it's started falling off the network again. I'll get it sorted though.
Thanks for the link, that's an interesting approach. I've planned to give it a target profile for the temp over the expected fermentation period, so I can increase it towards the end of fermentation, but having it respond to yeast performance as you suggest is also an idea.
The holy grail is something like they've done with 'The BeerBug', which I believe actually monitors and reports the specific gravity. I doubt I'll get to that.
When I get done I'll post up in 'projects'. I'm also thinking about how Espruino might be added to my beer system - that's documented here if you're interested http://beerdirective.tumblr.com/archive/2013/5
Lots of possibilities! Have a great day!
-
-
Hi Gordon, thanks though seems I'm good. It was the solder on the module, a piece on one contact had fallen away - I imagine what was left was a poor contact. Redone it. All good.
Thanks for your continued support. I can imagine you're pretty busy so it is appreciated. My project so far is here: http://esp.eantics.co.uk I'm aiming for a remotely monitorable beer fermentation setup.
Server working, temp now real ( now I know data is green :) ), next step the relays.
Best
Ollie
-
-
Suddenly my Web IDE console stops at "Connected" when I connect over Bluetooth. console.log does not echo to the left pane - I can 'send' programs which will run though. If I connect via screen in terminal on Mac it is a simlar problem - I just get a blank screen, however I can type commands which work, but I get nothing either, input or returns, shown in terminal window.
Both connection methods are fine over USB, I get the Espruino version info and the console responds and outputs console.log commands fine.
This was all working fine over Bluetooth a few days ago. Tested on 2 Macs both same. I have been flashing the board, but I'm pretty sure I'm back on 1.69 which is the firmware version I was using earlier with no problems.
Any ideas anyone?
-
-
It seems that anything might go with regard to color-coding the wires on these sensors!
I've revisited the ebay listing for the sensors I purchased, and the advert states in the tech specifications: yellow is ground, green is data!! It's the only advert I can see like this, all the others have yellow as data. I'm reluctant to even believe it - thinking it a mistake - but it would explain everything!
I shall test tonight - if you hear me laughing maniacally you'll know green was data.
-
-
Hi Gordon, no it's not I'm afraid. Thanks for testing your side to confirm it's ok on the firmware.
The earlier post in the other thread was pre-obtaining the correct resistor. At that point I believed that my issue. (I thought i better leave that thread alone as it appeared to be unrelated to firmware since I installed several of the earlier binaries to test which I should have mentioned here. Same result as 1.69)
I'm baffled. I suppose I probably need to try a sensor from a different supplier but is there a chance the bluetooth module has anything to do with this? I've powered down the CC3000 to rule it out but obviously the bluetooth is soldered on so powered up all the time. I'm clutching at straws with that though.
-
Thanks @DrAzzy. Good to know I've not made any obvious newbie mistakes with something this simple ;)
Code is basic: just the example from the DS18B20 page on the espruino site, reproduced below with my A0 pin in place of A1.
var ow = new OneWire(A0); var sensor = require("DS18B20").connect(ow); setInterval(function() { console.log(sensor.getTemp()); }, 1000);
I also tried sensor.isPresent() which just returns false.
-
Wow this is killing me. Something so simple and it's not working for me.
I have 5 of this sensors I've just got off ebay, they are the red/green/yellow type. Here is a pic of my setup. I previously thought I'd got the wrong resistor, but reading around people are using other pull up resistor sizes with this cable so I should have got something. I've got the correct 4.7k resistors today. Still null.
This is my setup. What am I doing wrong. I'm on v1.69 firmware. Also connected is a cc300o and bluetooth module. I've powered down the cc3000 but it makes no difference. I'm using A0 for the data. Tested on A1 too. Same result.
Either I'm missing something basic, somethings not working on my board or I've been sent 5 duff sensors (tested with 3 so far, 2 different breadboards, and I've bridged an LED to confirm I've got 3.3v coming out)
Apologies for posting up on something so basic, but I can't see where I'm going wrong.
-
Sorry to revive this. I've been getting the "null" response today. I'm fairly sure I have them connected correctly, whilst I'm new to electronics it doesn't appear to be that hard.
Would anyone know if this works ok in V1.69 of the firmware. Picture of my setup in case I'm doing anything obviously wrong. I'm using A1. The two additional wires near A1 are power for a CC3000 which is just out of shot.
Edit: I flashed some of the older firmware that people had this working with, still no work so it's likely me, but how/why I don't know.
Edit: I have the wrong resistor. Ignore me :(
-
That's fantastic news - and the speed at which you address stuff is amazing - cheers!