Wilberforce

Most recent activity

• Less memory building from sources

  in ESP32 • 4 days, 15 hours

  

  Yes. We updated to the latest esp-idf v3.1 and it seems to use more memory. We've not been able to establish what is taking up more space - I suspect buffers used for wifi and ble. @JumJum

• Is there support for the ESP32Cam?

  in ESP32 • 2 weeks, 2 days

  

  https://www.espruino.com/Extending+Espru­ino+1

• Is there support for the ESP32Cam?

  in ESP32 • 2 weeks, 3 days

  

  I think you would have to compile into the firmware. The is graphics for output - im not aware of any input device that you could use as an example.

• Maximise battery life for wearable continuous glucose monitor device

  in Puck.js, Pixl.js and MDBT42 • 2 weeks, 3 days

  

  What does the nfc device do? Isn't that already built into the module - or is it not ble?

• Espruino on your watch!

  in Projects • 2 weeks, 5 days

  

  The watch with esprunio on it has me interested.

• MDBT42Q page documentation clarification needed

  in Puck.js, Pixl.js and MDBT42 • 2 weeks, 6 days

  

  The default espruino build for this model only has 1 spi defined:

  https://github.com/espruino/Espruino/blo­b/master/boards/MDBT42Q.py#L60

  Support could be added for SP2 and SP3 in hardware.

  https://github.com/espruino/Espruino/blo­b/master/targets/nrf5x/jshardware.c#L107­2-L1123

  Pins are checked to see if they can be used:
  https://github.com/espruino/Espruino/blo­b/master/targets/nrf5x/jshardware.c#L116­4-L1169

• PUCK Ble HID keyboard

  in Puck.js, Pixl.js and MDBT42 • 3 weeks, 6 days

  

  It's so that B is not sent until A is done, it waits until the event is complete before adding a new event.

• websocket example connection error

  in JavaScript • 1 month, 1 week

  

  I can confirm that this is working now.

• websocket example connection error

  in JavaScript • 1 month, 1 week

  

  Thanks for updating!

• websocket example connection error

  in JavaScript • 1 month, 1 week

  

  I've manager to reproduce one of these issues using a current build on linux.

  vue native sockets in chrome browser -> Backend Espruino WS server.

  If protocol is specified, then all is well:

  const ws = new WebSocket('ws://192.168.1.203:8000', 'protocolOne');

  However, if this is defaulted, ws.js on the espruino sends as a header:

  Sec-WebSocket-Protocol: undefined

  this test seems to be failing:
  https://github.com/espruino/EspruinoDocs­/blob/master/modules/ws.js#L196-L197

  if (this.protocol)
      socketHeader.push("Sec-WebSocket-Protoco­l: "+this.protocol);
  

  in the constructor we have:
  https://github.com/espruino/EspruinoDocs­/blob/master/modules/ws.js#L76-L86
  this.protocol = options.protocol;

  So it seems this is setting this.protocol=undefined.

  What is the cleanest way to fix?

  if ( typeof(this.protocol) != 'undefined' )