MikeM551

Ah you do have a different panel. I did modify the fastLED line to GRB, the result is now red. ( nothing else was changed). RGB gives me green as intended. ( red and blue channels off) I left "int rgb = " alone. I thought we all had WS2812B LEDs.

On their original code try the following code change. Should be various green brightness....int red = random(0); //256 int green = random(50); //256 int blue = random(0); //256 int rgb = (green << 16) + (red << 8) + (blue); leds[i] = rgb;...works with red and blue as well.Don't forget the FastLED.addLeds<WS2812B, DATA_PIN, RGB>(leds, NUM_LEDS); vice FastLED.addLeds(leds, NUM_LEDS); fix.something else to try after.My last five lines of code look like this:FastLED.show(); // delay(4000); delay(10); // leds[i] = 0; // FastLED.show();Looks kind of cool actually.

well in this case ( instructables discussion boxes ) if you copy and paste to one of these boxes, anything inside of the < > including the < > will not paste correctly. I suppose they are control characters for this type of chat. Hence the <WS2812B, DATA_PIN, RGB> was left out of their original code casing compile errors. I have never had any real trouble with any .ino file, old or new over the years of Arduino IDE. Usually code error on my part.

RichW36 connect the 8x8 Matrix of WS2812B RGB LEDs Replace the lineFastLED.addLeds(leds, NUM_LEDS);in the Arduino code withFastLED.addLeds<WS2812B, DATA_PIN, RGB>(leds, NUM_LEDS);change the delay from 4000 to 10 for an interesting effect!The FastLED.h library is well commented.Mike M

RichW36 connect the 8x8 Matrix of WS2812B RGB LEDs Replace the lineFastLED.addLeds(leds, NUM_LEDS);in the Arduino code withFastLED.addLeds<WS2812B, DATA_PIN, RGB>(leds, NUM_LEDS);change the delay from 4000 to 10 for an interesting effect!The FastLED.h library is well commented.Mike M

connect the 8x8 Matrix of WS2812B RGB LEDs Replace the lineFastLED.addLeds(leds, NUM_LEDS);in the Arduino code withFastLED.addLeds<WS2812B, DATA_PIN, RGB>(leds, NUM_LEDS);change the delay from 4000 to 10 for an interesting effect!The FastLED.h library is well commented.Mike M

connect the 8x8 Matrix of WS2812B RGB LEDs Replace the lineFastLED.addLeds(leds, NUM_LEDS);in the Arduino code withFastLED.addLeds<WS2812B, DATA_PIN, RGB>(leds, NUM_LEDS);change the delay from 4000 to 10 for an interesting effect!The FastLED.h library is well commented.Mike M

I ran across something stupid on my part folks....Here is the run down with its solution.Open your arduino with the .ino fileSet up the Arduino IDE as the instruction states.Connect the ch340 to your scanner PCB --->3 wires only:1. ch340 TX to to scanner PCB RX2. ch340 RX to scanner PCB TX3. ch340 GND to scanner PCB GNDno VCC connection.Scanner PCB switch is OFF at this point.Connect the ch340 with a cable that you know will carry the data lines.. (I had one that was a charge only cable -- no data lines in it!!!)See green LED glowing on the ch340.Now go to your IDE ---> TOOLS / PORT.. select the port.. mine was COM19. Don't trust that default comm number that shows up in the lower right corner of the IDE!Check the ch340 connection PID ( Pelvic inflammatory disease ... opp…

I ran across something stupid on my part folks....Here is the run down with its solution.Open your arduino with the .ino fileSet up the Arduino IDE as the instruction states.Connect the ch340 to your scanner PCB --->3 wires only:1. ch340 TX to to scanner PCB RX2. ch340 RX to scanner PCB TX3. ch340 GND to scanner PCB GNDno VCC connection.Scanner PCB switch is OFF at this point.Connect the ch340 with a cable that you know will carry the data lines.. (I had one that was a charge only cable -- no data lines in it!!!)See green LED glowing on the ch340.Now go to your IDE ---> TOOLS / PORT.. select the port.. mine was COM19. Don't trust that default comm number that shows up in the lower right corner of the IDE!Check the ch340 connection PID ( Pelvic inflammatory disease ... opps .. errr. I mean process identification number) ---> TOOLS / Get Board INFO.. you will see a PID number .. the other info you can ignore. No PID.. you may have a bad USB cable with missing data lines. Try another cable.All is good so far, meaning that the comms to the ch340 are on.Now one can switch the scanner PCB on while holding that reset button. Nothing special to see here, so move along.release the RESET and click your IDE's check mark button ---> compile and upload <--- button on the IDE.( I did not check to see if the ESP8266 latches "boot loader mode".. or if it times out after a certain time.)In your Arduino status console window at the bottom of the IDE watch for this line:(esptool.exe upload tool directive line)C:\Users\Mike\AppData\... ...d2b9/esptool.exe -vv -cd nodemcu -cb 115200 -cp COM19 -ca 0x00000 -cf with the bin file --> C:\Users\Mike\AppData\Local\Temp\arduino_build_21464/WifiScanOLEDMike.ino.bin mine would fail after that line during flash writing since I was not paying attention the comm port setup entry. ( see above).hack.. as a side note.. you can start the compile and upload process.. then go and turn on your scanner PCB with the reset button held down.. waiting for the esptool.exe directive line to show up in the IDE, and release the reset button. There is a slight dwell after the programming directive line shows up.release the reset button when you see the line above.. mine dwells for about 2 seconds.Uploading to flash bla bla with incrementing % of data sent will be seen in the IDE console area.The OLED will now have text populating on it. SUCCESS

Platform and Arduino version?I used the GUI git to gather the resources as you did.I see a \\ vs my \.Windows treats \\ as \ ( single backslash) However this IDE is using Java based on Processing and other open-source software, so that could be an issue?cross platform environmentsThe double \\ is for path strings within code, hence escape character from within strings.I am using:Windows 10 with 1.8.3 Arduino. along with the GIT 2.16.2 +GUI following the instruction, and leaving everything default.Mine works .. here is a cut from the Arduino IDE console:***Build options changed, rebuilding allDetecting libraries used..."C:\Users\Mike\Documents\Arduino\hardware\espressif\esp32/tools/xtensa-esp32-elf/bin/xtensa-esp32-elf-g++" -DESP_PLATFORM ... and so forth...

Remember.. pin 8 and 10 from the USBasp 10 pin connector are ground for the pin 4 of the ATTINY85 in Step 10. When I followed the wiring diagram ( Step 10: USBasp - Atmel AVR USB Programmer ) for the pluggable Dev board on this page, random results were happening during programming. ATTINY85 had no ground on pin 4. I could program the ATTINY85 with out the Pluggable dev board just fine using a breadboard. So use the diagram ( USBasp to Pluggable Dev Board ), but ensure the green wire is going to pin 8 or 10 on the USBasp 10 pin connector.

Remember.. pin 8 and 10 from the USBasp 10 pin connector are ground for the pin 4 of the ATTINY85 in Step 10. Relocate the green wire in step 10 to pin 8 or 10 on the USBasp. You WILL get the SCK period warning, it is fine, no need to mess with a firmware update for the USBasp, as programming works with out any troubles.