1. Home
  2. People
Avatar for Schweigi

Schweigi

Member since May 2015 • Last active Jan 2017
  • 1 conversations
  • 11 comments

Most recent activity

  • HTTPS support on Pico!
    in News •
    Avatar for Schweigi

    Wow, fantastic news!

    @ Gordon How much flash space will there be left for the actual program on the Pico after flashing the TLS capable firmware?

  • Pico power consumption down to 0.02mA

    in News •
    Avatar for Schweigi

    Nice! Thx a lot Gordon.

  • Espruino Pico: Can I power it via battery instead of USB?
    in General •
    Avatar for Schweigi

    @DrAzzy Do you mean this one: https://www.adafruit.com/products/1769 ?

    I would need some for myself because currently I'm using one which I got from a extension cable but it doesn't have the pins to solder.

  • started
    • 11 comments
    • 6,804 views
    @Gordon replied

  • No callback on http request
    in General •
    Avatar for Schweigi

    I finally found it.

    I used a breadboard for all my experiments with the ESP8266 on it. Apparently this was the issue. After soldering the ESP8266 to a shim all communication errors are gone.

    One small issue I mentioned in my previous post (issue (2)) is still left. When there is no res.on('data') event handler then the res.on('close') handler is never called.I'm not sure if this is by design or a bug.

  • No callback on http request
    in General •
    Avatar for Schweigi

    My issue (1) is if the requests are serial, not parallel. So only one request at a time.

  • No callback on http request
    in General •
    Avatar for Schweigi

    I checked. The Connection: close header is also added on the .request call by default. I think the issue is related to the content length. If I send too much data then I get the same behavior as with the Mandrill API also with the Requestbin API example.

    var CONTENT_LENGTH = 10; //<== always ok
//var CONTENT_LENGTH = 250-300; //<== request is sent but no answer received
//var CONTENT_LENGTH = 800; //<== request is not sent

Serial1.setup(9600, { rx: B7, tx : B6 });
var wifi = require("ESP8266WiFi").connect(Serial1, function(err) {
  if (err) throw err;
  wifi.reset(function(err) {
    if (err) throw err;
    wifi.connect("<WIFI_SSID>", "<WIFI_PW>", function(err) {
      if (err) throw err;
      
      var content = "";
      for(var i=0; i < CONTENT_LENGTH; i++) {
        content += "x";
      }
      
      var options = { 
        host: "requestb.in", 
        port: 80, 
        path: "/1lxvhjs1", 
        method: "POST",
        headers: {
          "Content-Type": "text/plain",
          "Content-Length": content.length
        }
      };
      
      wifi.at.debug();
      var req = require("http").request(options, function(res)  {
          console.log("status: " + res.statusCode);
      });
      req.end(content);
      console.log("Request sent (length: " + content.length + ")");
    });
  });
});

    While debugging I also found three other issues. I can reproduce those with a simple GET call. Just attach a ESP8266WiFi to your Pico and press the build-in button to trigger a request.

    1. The first issue is, that when I do multiple requests all but the first produce an error (see AT debug msgs). I event tried to give it a couple of minutes between the button pushes to be sure the prior connection is really dead but it does't help. I never managed to make more than one successful http request without restarting the Pico in-between.
    2. The second issue is, that if there is no res.on('data') event handler, then res.on('close') isn't called either (also CIPCLOSE is never called).

    3. The third issue is, that for some hosts (or probably servers) the connection isn't closed after the GET is done but only after the server closes it. Thus it can't take a long time until the data is available to read - see BBC example.

      var URL = "http://www.pur3.co.uk/hello.txt";

/*
** ISSUE 3 **:
Call to the BBC page closes only 60s after request has been started.
The AT debug messages show that the response is received immediately but 
the call is only closed after a timeout.
  
wifi.at.debug() output after 60s:
] "\r" <--- "\r"
] "\nE" <--- "\nE"
] "ERR" <--- "RR"
] "ERRO" <--- "O"
] "ERROR\r" <--- "R\r"
] "\nUn" <--- "\nUn"
] "Unli" <--- "li"
] "Unlink" <--- "nk"
] "Unlink\r" <--- "\r"
] "\n" <--- "\n"
["AT+CIPCLOSE=0\r\n"
  
var URL = "http://open.live.bbc.co.uk/weather/feeds/en/2647937/observations.rss";
*/

Serial1.setup(9600, { rx: B7, tx : B6 });
var wifi = require("ESP8266WiFi").connect(Serial1, function(err) {
if (err) throw err;
wifi.reset(function(err) {
if (err) throw err;
wifi.connect("<WIFI_SSID>", "<WIFI_PW>", function(err) {
  if (err) throw err;

  console.log("Press button to trigger a request");
  wifi.at.debug();
      
  setWatch(function(e) {
    var req = require("http").get(URL, function(res)  {
      console.log("Connection status: " + res.statusCode);
          
      var content = "";
      /* 
        ** ISSUE 2 **
        If the res.on('data') event handler is removed 
        then "AT+CIPCLOSE=0" is never executed and 
        res.on('close') is never called.
      */  
      res.on('data', function(data) {
        content += data;
      });
          
      res.on('close', function() {
        console.log("Connection data: " + content);
        console.log("Connection closed");
      });
    });
        
    console.log('Request sent');
  }, BTN, { repeat: true, debounce : 50, edge: "rising" });
});
});
});

    Btw my Pico firmware has 1v78 and the ESP8266 has 0018000902-AI03.

  • No callback on http request
    in General •
    Avatar for Schweigi

    I re-routed the http request form the Pico trough a proxy on my computer. The request itself is working but the Pico doesn't seem to close the connection. Also sometimes (10% of the time) not all the payload data is sent (it gets stuck at 272 bytes). I added a wifi.at.debug and after the data is sent the following is printed by at.debug:

    ] "> \r" <--- "\r"
] "\nER" <--- "\nER"
] "ERRO" <--- "RO"
] "ERROR" <--- "R"
] "ERROR\r\n" <--- "\r\n"
] "Unl" <--- "Unl"
] "Unlin" <--- "in"
] "Unlink" <--- "k"
] "Unlink\r\n" <--- "\r\n"
["AT+CIPCLOSE=0\r\n"
] "l" <--- "l"
] "li" <--- "i"
] "link" <--- "nk"
] "link i" <--- " i"
] "link is" <--- "s"
] "link is n" <--- " n"
] "link is not" <--- "ot"
] "link is not\r\n" <--- "\r\n"

    I guess this error is the problem. But I don't know where its coming from.

  • Pico and ESP8266
    in General •
    Avatar for Schweigi

    I didn't try the capacitor yet but I think most of the problems I wrote occurred because I loaded new code onto the Pico while a prior request was still running. Because once I stopped that the issues mostly disappeared.

  • No callback on http request
    in General •
    Avatar for Schweigi

    Ups. I forgot to call req.end() when I created the test code for the GET request. I'm sorry for the confusion. So the following is working too now:

    var options = { host: "http://www.google.com" };
var req = require("http").request(options, function(res)  {
        console.log("status: " + res.statusCode);
});
req.end(); // <=== was missing

    But I still have some issues with the post call not ending. I think its because of the Mandrill API. The following sample code (POST req. to Requestbin) is working. The console prints the status code (200) after the request:

    Serial1.setup(9600, { rx: B7, tx : B6 });
var wifi = require("ESP8266WiFi").connect(Serial1, function(err) {
  if (err) throw err;

  wifi.reset(function(err) {
    if (err) throw err;

    wifi.connect("<WIFI_SSID>", "<WIFI_PW>", function(err) {
      if (err) throw err;

      var content = JSON.stringify({ "msg": "Hello World!"});
      var options = { 
        host: "requestb.in", 
        port: 80, 
        path: "/1lxvhjs1", 
        method: "POST",
        headers: {
          "Content-Type": "application/json",
          "Content-Length": content.length
        }
      };
      var req = require("http").request(options, function(res)  {
          console.log("status: " + res.statusCode);
      });
      req.end(content);
      console.log('Request sent');
    });
  });
});

    But when I do the same for the Mandrill API then the post request is not ending. Mandrill gets the request successfully but its seems that the Espruino is still waiting for a response:

    Serial1.setup(9600, { rx: B7, tx : B6 });
var wifi = require("ESP8266WiFi").connect(Serial1, function(err) {
  if (err) throw err;

  wifi.reset(function(err) {
    if (err) throw err;

    wifi.connect("<WIFI_SSID>", "<WIFI_PW>", function(err) {
      if (err) throw err;
      
      var content = JSON.stringify({
        "key": "<MANDRILL_API_TOKEN>",
        "text": "This is a demo",
        "message": {
          "from_email": "example@mandrillapp.com",
          "to": [
            {
              "email": "<YOUR_EMAIL>",
              "type": "to"
            }
          ]
        }   
      });
      
      var options = { 
        host: "mandrillapp.com", 
        port: 80, 
        path: "/api/1.0/messages/send.json", 
        method: "POST",
        headers: {
          "Content-Type": "application/json",
          "Content-Length": content.length
        }
      };
      var req = require("http").request(options, function(res)  {
          console.log("status: " + res.statusCode);
      });
      req.end(content);
      console.log('Request sent');
    });
  });
});

    I will try to investigate further. The same request (http & https) using a rest-client (Postman) is working correctly.

Send Message
Actions

About Terms of Use Privacy Policy Cookie Policy Report a problem