Hello, first thank you for sharing your project, I have used the google translator, I am sorry if there are errors in the text. I have followed the steps and I have managed to implement it in my arcade but there is a function that does not work correctly and if it does it with the original ledwiz. Using hyperspin it is able to speak and blink the frontend controls but not blink when launching a game, only speak. I have checked the configuration and it is correct. when i use original ledwiz it does it correctly. I have reviewed the code but I do not understand it and I do not know if the error is there, could you help me to solve it?

Hi, sorry, I stopped working on this a long time ago.  Unfortunately, I only tested it to the point that ledBlinky was happy using the in-built testing program and the routine creator. I never used it with Hyperspin or other program which uses ledBlinky.

Others have taken parts of this project and carried it further.  Perhaps post a comment/question in Kris's project?

https://hackaday.io/project/174056-ledblinky-controller-ws2812-arduino-usb-spi-update

Thanks for responding, I will contact Kris to see if he can help me.

Lee Cook, when I open the SimpleLEDtest.exe application it correctly detects the 8 ledwiz, if then for example I open the LEDBlinkyConfig.exe application without closing the previous one it tells me the error No LED Controllers Detected, I have to close simpleLEDtest.exe so that the detect. With original ledwiz I can open both at the same time and not show errors, could this be what is causing the malfunction? The way the serial port is used? On the other hand, I have contacted the developer of the ledblink application and I have sent him the log file that the application generates and see what is happening.

Update, it's working with ws2812b. I have not learned how to do the math on how long it takes for his work to send the led via spi it you have to take in to account buad rate, how many cycles each thing the micro control has to do etc. The timing of sending data to the ws2812 and ws2812b are the same, but for the last command. The time it gets a low signal before it starts to reset and take new data in. The ws2812b need 300 micro second at minimum before rest. So I track the code back to the main loop in virtual serial demo.c waited until after it output to the led and read in the data from the pc and added a delay of 300uS with _delay_us(). This got it working but it's lagging. I will play with it to see if I can make respond better. It needs a minimum of 300us it can take more but not less.

EDit: fixed i called _delay_ms(300); instead of _delay_us(300);. lag is fix works great. I will get the new files up on my addon project page soon.

Edit 2: it works great with ledblinky. With one exception. It is spoofing the led wiz that uses only 48 brightness levels. The ws2812b can do 256. It limits your range but works none the less. Not sure there is a workaround for this as it is capped at 48 in ledblinky because it thinks it's a ledwiz and won't let you pick over. I will think on this. At any rate good luck to all who use this. Enjoy.

https://hackaday.io/project/174056/details/

Lee has done some great work here. I just jumped back in and have learned so much from having to backtrack why I mine was not working. 

Tips:

1. If you have windows version above 7 the driver will need to be signed, I can post the cleaned up info file that you can use to self sign the driver. Will add later.

2. The Leonardo is a much different Arduino to upload to. After rest it goes in to a boot loader mode that always flashing, last about 8 seconds. The com port changes when this happens. You can also open a serial connect at 1200 baud and close it to cause this rest to happen.

3. I had to put the full path in to the .hex file being flashed to get it to work. I'm talking about when setting add the new tool.

4. Addressable leds are a pain. WS2812 and WS2812B are the same until year 2017, WS2812B in 2017 the rest aka latch time went way up, see my other post. WS2811 have different timings so they flat don't work.

Using spi to run WS2812 takes some math and a good understanding of the chip how it cycles, uplink speed etc. Unfortunately I was unable to find how he got the timing for the rest to work. It's not just a magical variable that needs changed. So I can't make this work with newer WS2812B.

I will keep an eye on this maybe Lee can give us 2 low level zips 1 for WS2812, and one for WS2812B if he can manage to change the rest timing without breaking the timing of the other high and low singles.

New WS2812B LEDs started to appear, requiring 300us reset times instead of the 50us for ws2812

EDIT: link to signing driver so it will install on newer windows OS's. tested on Win 10.

https://hackaday.io/project/174056/details/

Only getting green  light no control tho, only first led on green. Thought I had ws2812 but I may have ws2812b based on comment below.  What I have found out is this. issue comes with a change from 2017. New WS2812B LEDs started to appear, requiring 300us reset times instead of the 50us for the old ws2812B /ws2812

If we use a mega or other arduino with the 16u2, is it possible to flash the chip with the ledwiz firmware to get the arduino to show up as a ledwiz device? would it then be possible tol use the arduino IDE to program the mega2560 via icsp? I want an input controller and neopixel driver all in one. LEDBlinky is very behind in development.

This is likely too late to be of use. Sorry, I have email notifications turned off because I was being spammed by the Tindie channel and I've only just came on here after being off the site for a long while.

It's the PC DLL which actually pretends to be the LedWiz devices, the link to the Arduino is purely serial and is from the DLL.

So, in theory, you should be able to run the code on anything which presents a fast serial connection to the PC and still has the headroom to push out the WS2812 commands over the SPI link.

I'm using WS2812B and i only have a green led.

How hard would it be to port the AtmelStudio project from ATmega32U4 to ATmega328P to run on an Arduino UNO?

It should be easy. I only used the ATmega32U4 because it ran at 32MHz and because I was still getting to grips using the LUFA USB library on my main. It was a tester for me to implement a simple LUFA USB CDC serial link on the board I had laying around.

So long as you change the serial link ID in the DLL to the board you're using, and the UNO still has the power to service the serial and the SPI, you should be good to go.

ATmega32u4 runs at 16MHz no?

HI, I like your project, I would like to know if it is possible to implement it with arduino based on atmega328p?

Sorry for the huge delay.

See the replies above.

It should be easy. It's a standard serial link to the DLL which then converts it to what LedBlinky expects from the LedWiz devices.

Hello i try your project but need to adjust i dont understand how you code the pin because i want to use a second pin for a second set of ws2812 led, can you help me please

Sorry, you can only control a single set of outputs.  The code uses the SPI device (rather than timing a pin) on the chip to output the pulse train inecessary to turn the individual bits on and off.  This means you can only use the MOSI pin on the device.

Hi, I try to use your work.

I follow your instructions and I can saw the 8 ledwiz in simpleLEDTest, but my lestrip not blink. I use a WS2811 not a WS2812, but when I unplug / plug the pin 16 the led state change.

I try to understand your code (dll and arduino) but I don't have enough knowledge on this topic.

 Please I don't understand why could you help me?

Thanks

I've not used the WS2811.  If it has the same protocols and timings as the WS2812s it should work.