Coder2012

Most recent activity

• Problem trying to update Espruino Wifi to firmware v106

  in Pico / Wifi / Original Espruino • 1 month

  

  Even more sorry for a longer delay :)

  So I'm using the Chrome App. I'm happy to report that I have updated to v1.07.

  I honestly have no idea what finally fixed it, i've reinstalled the Chrome IDE many times, I've switched COM ports because sometimes it sees a port then when in bootloader mode that port now disappears.

  Then all of a sudden COM port 5 appears in bootloader mode and boom I get to update the firmware.

  So relieved it's finally worked but sorry can't explain what the cause was.

• Problem trying to update Espruino Wifi to firmware v106

  @Coder2012 started

  • 3 comments
  • 303 views

  @Coder2012 replied
• Is my Espruino sleeping?

  @Coder2012 started

  • 13 comments
  • 826 views

  @Gordon replied
• Is my Espruino sleeping?

  in Interfacing • 4 months, 1 week

  

  Ok so I've now tested this using different USB plugs, cables and computers. The result is always the same, after maybe one or two hours. The Espruino WiFi seems to stop executing, and there led that is being used for sleep indicator, starts to flicker quickly and is no longer brightly lit.

  Does this sound like it's trying to sleep?

  I even added a ping back to the raspberry pi to make sure the connection stays alive every 15 seconds.

• Problem trying to update Espruino Wifi to firmware v106

  in Pico / Wifi / Original Espruino • 4 months, 1 week

  

  I am trying to update my Espruino Wifi to v106. It was recently updated to v105 without any issues.

  Here's what i've tried:

  1. Put the Espruino Wifi into boot loader mode, the red and green light pulsate in sequence.
     
  2. Click the flash firmware button.
     
     

  Error popup in the web ide says -

  Firmware for this device can't be updated from  the IDE at the moment. 
  

  (I used the above steps to update to v105 last week and it was successful)

  1. Put the Espruino Wifi into boot loader mode, the red and green light pulsate in sequence.
     
  2. Click flash from file button and locate previously downloaded - espruino_2v06_wifi.bin
     
     

  This time I see:

  Connected to COM1 (No response from board)
  Initializing...
  Error Flashing: Can't find STM32 bootloader. Make sure the chip is reset into bootloader mode by holding down BTN1 while pressing RST
  Disconnected from COM1
  

• Is my Espruino sleeping?

  in Interfacing • 4 months, 1 week

  

  Oddly after several attempts using reset and save its started working again.

• Is my Espruino sleeping?

  in Interfacing • 4 months, 2 weeks

  

  Ok so now I have this very simple piece of my implementation and i'm still getting this dreaded error:

  New interpreter error: FIFO_FULL
  

  All I'm doing is the following:

  const wifi = require('Wifi');
  const WIFI_NAME = 'BTHub6-3TFX';
  const WIFI_OPTIONS = { password : 'mypassword' };
  
  function onInit() {
    wifi.connect(WIFI_NAME, WIFI_OPTIONS, (err) => {
      if (err) {
        console.log('Connection error: '+err);
        return;
      }
      console.log('Connected!');
    });
  }
  

  I really don't understand why it just throws this error when I do anything with Wifi now, this was all working the other day.

  Any ideas guys?

• Is my Espruino sleeping?

  in Interfacing • 4 months, 2 weeks

  

  Hey AO good to hear from you. I only call onInit when I'm running in the web IDE.

  I remove this call when I run save(); in the IDE.

  I must admit the various methods of saving and running code on espruino don't make a lot of sense to a regular web developer such as myself. I'll need to do some reading up on this area.

• Is my Espruino sleeping?

  in Interfacing • 4 months, 2 weeks

  

  I'm also unable to update to v106 even though the red and green lights are pulsing as expected.

  Error Flashing: Can't find STM32 bootloader. Make sure the chip is reset into bootloader mode by holding down BTN1 while pressing RST.

  Is there a way I can hard reset on Espruino Wifi? I'm running into a few issues lately.

• Is my Espruino sleeping?

  in Interfacing • 4 months, 2 weeks

  

  So i've read the docs and I do indeed have console logs in my code, so my plan is to remove those, but I've somehow hit another issue. When I try to send code to my board i'm getting the following error.

  New interpreter error: FIFO_FULL
  Connection error: No 'ready' after AT+RST
  

  This is odd as it has been working from the web IDE just fine recently. Here's the source. I have a raspberry pi4 running nodered which reads sensors around the house, some of these send data via MQTT which i'm picking up with the Espruino Wifi.

  const neo = require('neopixel');
  const wifi = require('Wifi');
  const WIFI_NAME = 'BTHub6-3TFX';
  const WIFI_OPTIONS = { password : 'xxxxxxxx' };
  
  let delay = 0;
  let rgb = new Uint8ClampedArray(36);
  
  
  function onInit() {
    setSleepIndicator(LED1);
    const server = '192.168.1.64';
    const options = {
      client_id : 'random',
      keep_alive: 60,         // keep alive time in seconds
      port: 1883,             // port number
      clean_session: true,
      username: 'username',   // default is undefined
      password: 'password',   // default is undefined
      protocol_name: 'MQTT',  // or MQIsdp, etc..
      protocol_level: 4,      // protocol level
    };
    const mqtt = require('MQTT').create(server, options /*optional*/);
  
    mqtt.on('connected', () => {
      console.log('connected to broker');
  
      mqtt.subscribe('doorOpen');
      mqtt.subscribe('doorClosed');
      mqtt.subscribe('heartbeat');
    });
  
    mqtt.on('publish', (pub) => {
      console.log('topic: '+pub.topic);
      console.log('message: '+pub.message);
  
      switch(pub.topic) {
        case 'doorOpen':
          console.log('doorOpen');
          doorOpen();
          break;
  
        case 'doorClosed':
          console.log('doorClosed');
          doorClosed();
          break;
  
        case 'heartbeat':
          if(parseInt(pub.message) > 1) {
            heartbeat();
          }else{
            motion();
          }
          break;
  
        default:
          neo.write(B15, lights({r: 0, g: 0, b: 0}));
          break;
      }
  
    });
  
    wifi.connect(WIFI_NAME, WIFI_OPTIONS, (err) => {
      if (err) {
        console.log('Connection error: '+err);
        return;
      }
      console.log('Connected!');
      mqtt.connect();
    });
  
    function lights(colors) {
      for (let i = 0; i < rgb.length;) {
        rgb[i++] = colors.g;
        rgb[i++] = colors.r;
        rgb[i++] = colors.b;
      }
      return rgb;
    }
  
    function doorOpen() {
      neo.write(B15, lights({r: 0, g: 0, b: 0}));
      update({r: 255, g: 0, b: 0});
    }
  
    function doorClosed() {
      neo.write(B15, lights({r: 0, g: 0, b: 0}));
      update({r: 0, g: 255, b: 0});
    }
  
    function heartbeat() {
      neo.write(B15, lights({r: 0, g: 0, b: 0}));
      update({r: 0, g: 0, b: 255});
    }
  
    function motion() {
      neo.write(B15, lights({r: 0, g: 0, b: 0}));
      update({r: 0, g: 255, b: 0});
    }
  
    function update(color) {
      neo.write(B15, lights(color));
      delay = setTimeout(() => {
        neo.write(B15, lights({r: 0, g: 0, b: 0}));
      }, 1000);
    }
  }
  
  onInit();