user106712

Most recent activity

• "net" server socket's information

  @user106712 started

  • 1 comment
  • 64 views

  @user106712 replied
• "net" server socket's information

  in ESP8266 • 3 weeks, 3 days

  

  The socket object returned from createServer() shows (using JSON.stringify(sock)):

  {"type":0,"sckt":15,"conn":true}

  Are the above the only key/value pairs available?

  sock.remoteAddress and sock.remotePort are both undefined.

  Can these be discovered somehow?

• BLE cannot find puck.js

  @user106712 started

  • 6 comments
  • 216 views

  @user106712 replied
• BLE cannot find puck.js

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

  

  Not as far as I know. Both Pucks now behave well. Thanks.

• PuckJS Infrared - Does the case get in the way?

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

  

  Your first line (D25,D26) produces result but not (D26,D26)!

  
  var cmds = {
  
      // main menu top left - select
      mainSelect: [
  9.0, 4.4, 0.6, 0.5, 0.6, 1.6, 0.6, 1.6, 0.6, 0.5, 0.6, 0.5, 0.6, 0.5, 0.6, 0.5, 0.6, 1.6, 0.6, 1.6, 0.6, 0.5, 0.6, 1.6, 0.6, 0.5, 0.6, 0.5, 0.6, 0.5, 0.6, 0.5, 0.6, 0.5, 0.6, 0.5, 0.6, 0.5, 0.6, 0.5, 0.6, 0.5, 0.6, 1.6, 0.6, 0.5, 0.6, 1.6, 0.6, 0.5, 0.6, 1.6, 0.6, 1.6, 0.6, 1.6, 0.6, 1.6, 0.6, 0.5, 0.6, 1.6, 0.6, 0.5, 0.6, 1.6, 0.6, 42.9, 9.0, 2.2, 0.6, 95.9, 9.0, 2.2, 0.6, 95.9, 9.0, 2.2, 0.6, 95.9, 9.0, 2.2, 0.6, 95.9, 9.0, 2.2, 0.6, 95.9, 9.0, 2.2, 0.6, 95.9, 9.0, 2.2, 0.6, 95.9, 9.0, 2.2, 0.6
  ]};
  
  /* received on the other end (D25,D26):
  4.4,0.5,0.6,0.5,1.6,0.5,1.6,0.6,0.5,0.5,­0.5,0.5,0.5,0.5,0.5,0.6,1.6,0.6,1.6,0.6,­0.5,0.6,1.6,0.6,0.5,0.6,0.5,0.6,0.5,0.6,­0.5,0.6,0.5,0.6,0.5,0.6,0.5,0.6,0.5,0.6,­0.5,0.5,1.6,0.6,0.5,0.6,1.6,0.6,0.5,0.6,­1.6,0.5,1.6,0.6,1.6,0.6,1.6,0.5,0.5,0.6,­1.6,0.6,0.5,0.6,1.6,0.6,42.9,8.9,2.3,0.5­,95.9,8.9,2.3,0.5,95.9,8.9,2.2,0.7,95.9,­8.9,2.2,0.7,95.9,8.9,2.2,0.6,95.9,9.0,2.­2,0.6,95.9,9.0,2.2,0.6,95.9,8.9,2.2
  0.2
  */
  

  I guess I will use D25,26 for transmission.

  A query: not sure why the first value is consistently missing (i.e. 9.0).

  Am I in fact transmitting the inverse pattern or am I just not understanding the IR protocol? (The definition file was captured (transmitted from a physical remote) using the same Receiver code, i.e. (from you!)

  function onInit() {
  
      digitalWrite(D2, 0);
      pinMode(D1, "input_pullup");
      var d = [];
      setWatch(function (e) {
          d.push(1000 * (e.time - e.lastTime));
      }, D1, {
          edge: "both",
          repeat: true
      });
  
  
      var lastLen = 0;
      setInterval(function () {
          if (d.length && d.length == lastLen) {
              d.shift(); // remove first element
              console.log(d.map(a => a.toFixed(1)).toString());
              d = [];
          }
          lastLen = d.length;
      }, 200);
  
      setInterval(() => LED3.toggle(), 500);
  
  }
  

• PuckJS Infrared - Does the case get in the way?

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

  

  Thanks - I am using v2.05 firmware (Sep 2019 vintage PuckJS). The onboard IR LED transmits in the ~940nm (same as mine) so it's odd that the same receiver does not see it.

  I have now inverted the roles of the two PuckJS. Again the same phenomenon (second Puck sees the IR signal from my own LED but not Puck's). It is unlikely that the transmitter on both Pucks are faulty. But I don't have anything else to test them with. Any idea?

• PuckJS Infrared - Does the case get in the way?

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

  

  Hi @Gordon,

  I am looking for the spec for the IR transmitter on the PuckJS. I have been able to use your demo code to transmit and receive IR signals using a pair of PuckJS and 940nm transmitter and https://www.vishay.com/docs/82491/tsop38­2.pdf receiver using the following code to test:

  setWatch(() => {
      Puck.IR(cmds.mainSelect);  // line 1
      Puck.IR(cmds.mainSelect, D31, D30); // line 2
      LED2.toggle();
  }, BTN1, true);
  

  Line 2 works as advertised.

  When I use line 1 only, I cannot get any reading. I doubt the onboard transmitter is busted so it could be an incompatibility issue somewhere else?

• BLE cannot find puck.js

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

  

  I used another computer and managed to see two entries (9663). I did not pair then.

  I returned to the first computer and was able to find the Puck and pair with it.

  Solved. Thanks! But why the two entries?

• BLE cannot find puck.js

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

  

  I have made sure that other bluetooth devices are no connected to it.

  I've reflashed the Puck with v2.05 using nRFTool. I also powered up while holding the button (until beyond the 5 red blinks).

  On the desktop, I reset its bluetooth module so that it has no memories of prior pairings (I had to re-pair my keyboard and mousepad).

  In this fresh start, the other Puck appears quickly in web IDE and is re-paired.

  The web IDE still cannot seem to find this Puck during 're-scan'.

• BLE cannot find puck.js

  in Puck.js, Pixl.js and MDBT42 • 4 weeks

  

  I have two puck.js, received a few months ago. I had paired both in IDE and everything worked. Then they went in the drawer somewhere.

  I got them out today. Upgraded both to v2.05. One paired with the IDE and works well. The other does not seem to show up at all during BLE Select. I have hard reset it a few times. The self-test seems to pass. It seems functional, just does not connect/pair.

  How do we forget a Puck that was paired before but does not now show up?