maze1980

Most recent activity

• Read ESP8266 serial console with Arduino UNO

  in ESP8266 • 1 month

  

  Your Adruino code looks complicated, and I'm not sure if it's correct, or if you're overwriting the variable IncomingString in the while loop.

  The sample code for serial input from https://www.javatpoint.com/arduino-seria­l-available:

  void loop( ) // loop function that executes repeatedly  
  {  
  if(Serial.available( ) > 0) //  It will only send data when the received data is greater than 0.  
  {  
  arrivingdatabyte = Serial.read( );  // It will read the incoming or arriving data byte  
  Serial.print("data byte received:");  
  Serial.println(arrivingdatabyte, DEC); // here, DEC means Decimal  
  }  
  }  
  

  I'd suggest to remove the while and the true/false in your code, and change it according to the sample code.

• performance tips for computations on an ESP32

  in ESP32 • 1 month

  

  Well, optimizing for speed is often bad for readability. I wouldn't add "+0.5" to the code, just to save the time needed for this extra operation.
  And yes, numbers in square brackets are not rounded to an integer. And we all love code like this:

  >foo={"0.5": "bar", "1": "foo"};
  >foo[0.5];
  ="bar"
  >foo[Math.round(1.5)];
  ="foo"
  

  Since prepareDisplay is one of the slowest functions: ColorMap has only 8 different values, Temperature has 208 different values - so it might be feasible to pre-compute things and avoid all division and multiplication operations with Temperature in this function - if there's enough RAM available on the ESP32. Anyway, that's much harder than just removing rounding and clamping for TemperatureMap values. Removing 262 function calls will result in a measurable improvement, even for the compiled version.

• performance tips for computations on an ESP32

  in ESP32 • 1 month, 1 week

  

  Just looked at the code, and I think there are still options for improvement: All the clamping and rounding for TemperatureMap values can be omitted:

  >let foo = new Uint8ClampedArray(3);
  =new Uint8ClampedArray(3)
  >foo[0] = -0.5; foo[1] = 1.5; foo[2] = 255.5;
  =undefined
  >foo
  =new Uint8ClampedArray([0, 1, 255])
  

  One day I'll test this code, I think the effect will be nice.

• Strange issue with wifi!11!!1!

  in ESP8266 • 2 years, 1 month

  

  "wpa2" should work
  "wpa and wpa2" could cause problems
  WiFi 6 could cause problems

• digitalPulse "Timeout on Utility Timer"

  in ESP8266 • 2 years, 3 months

  

  I don't think it is easy to fix, especially without breaking existing code. Maybe it is possible to change

  digitalPulse(csPin, true, [1, 1, 0.03, 0.03, 0.045]);
  

  to

  digitalPulse(csPin, false, [1, 0.03, 0.03, 0.045]);
  

  and get the desired pulse, just a a little delay. Then there would be no code change required, just a note in the documentation.

• digitalPulse "Timeout on Utility Timer"

  in ESP8266 • 2 years, 3 months

  

  More like
  https://github.com/espruino/Espruino/blo­b/e568c6c7ac78e81b4ab40bb28bd92e8052f4e7­b6/libs/neopixel/jswrap_neopixel.c#L236-­L238
  and

• digitalPulse "Timeout on Utility Timer"

  in ESP8266 • 2 years, 3 months

  

  The neopixel module for ESP8266 does a dry-run/pre-roll without emitting any pulses. That dry run is necessary to load the machine code from flash into RAM. Without this dry run the timing of the pules representing the first byte won't have proper timing. It might be the same issue in this case. Reference files:
  jswrap_neopixel.c, line 220...
  jswrap_io.c, line 201...

  There is no dry-run for ESP8266 in jswrap_io.c, so I would assume it is the same issue. That code is not capable of producing very short pulses accurately in the first run.

• Power Loss/Drain problems

  in Pico / Wifi / Original Espruino • 2 years, 3 months

  

  A simple FET switch might be all thats needed to turn off the juice to the Neopixel hogs or a relay as indicated in post #2 What about using a pin on the Espruino to control a Buck step-up converter that would supply the 5V? hummmmmm . . . .

  Neopixel shall be connected with ground first, i.e. a simple FET wouldn't be a good solution. Get a high rail FET, e.g. MIC94060 or something else with an internal charge pump.

• Espruino Wifi Power Consumption in Deep Sleep at 2mA

  in Pico / Wifi / Original Espruino • 2 years, 3 months

  

  I see console.log("doing stuff"); in your code, but no serial port connected on the picture. Do you have data waiting at the serial port?

• Power Loss/Drain problems

  in Pico / Wifi / Original Espruino • 2 years, 4 months

  

  According to the first post the battery dies after one hour. Then illuminating 10 LEDs for a minute will work for 60 times (that is again 60 minutes) until the battery dies. Is this enough?
  What do you actually build, with 300 LEDs and portable (I guess, as it is battery powered)?