Most recent activity
-
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.
-
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.
-
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.
-
-
-
-
-
https is not working on 2.04
You have to build your own version, using less jsvars. However no details on how much to reduce the variables. See also: https://github.com/espruino/Espruino/issues/1613
I'll make a custom build, sooner or later, maybe end of this year. (Without the graphics library, without telnet and without ota.). And, if necessary for https, less jsvars.
"wpa2" should work
"wpa and wpa2" could cause problems
WiFi 6 could cause problems