Artnet LED Pixels With ESP8266

34,594

82

68

After the success of my last Instructable, ESP8266 Artnet to DMX, I have completely revamped my espArtNetNode code, releasing v2 with new features such as RDM support and WS2812 output. This code is still in beta and there are a few known bugs - and probably a few unknown also.

I have written this Instructable to help with some common questions on setting this device up to control WS2812 pixels.

We will quickly look at how I have laid out and wired my 30 x 15 pixels, then I'll show you which settings you need to get the ESP connected. Next, I'll do a quick run through how to patch the ESP outputs into Jinx so we can get some cool effects running. In the final step, I'll discuss some of the issues I'm currently having and things I'd like to add in the future.

The video here will show you very quickly through all of these steps. I apologize for the poor sound quality - I don't have an external microphone and my laptop fans are really loud.

I'd love to see how you use this. Post some photos, videos and comments below to let me know your experience and any suggestions you may have. I read all the comments I receive and try to reply in a timely manner.

Let's get started....

Supplies:

Step 1: Pixel Layout and Wiring

This step is fairly easy but very time consuming.

Find a board to mount everything to - I used a 6mm MDF sheet, 600mm x 1200mm in size.

Work out the best way to lay everything out. I had 3x 5m rolls of tape so decided to do 15x 1m strips. This gave me 200mm at the side for the electronics and PSU. I used small bolts and standoffs to mount the PSU and PCBs. Measure the hole spacing and drill through the MDF - you might want to make a test template using scrap paper first.

I spaced the tape so the LEDs are the same distance apart as they are on the tape. I used the adhesive already on the LED tape to stick it down. Make sure you pay attention to the data in and data out for each strip - have them alternate to make connecting the data lines easier, ending up in a snakelike pattern. Also make sure your ESP location is next to the data in for the first strip.

Now wire all the power up. I chose to run 3 power lines, 1 per 5m of tape, and each with it's own fuse. When using such a large PSU, I'd recommend fuses to ensure you don't damage anything if there's a short. I mounted my fuses to a small piece of perf board to make a basic power distro board. If your runs are longer than about 150 pixels, you'll need to "inject" power along the runs to ensure the LED brightness and colour doesn't suffer. Make sure you insulate any connections so you don't get a short.

Data can now be connected. My code will allow a max of 680 ws2812 pixels per port. Wire the ESP to the data in of the first strip. Wire the data out of the first strip to the data in of the second strip, data out of the second to data in of the third....

To finish it off, I ran a strip of black gaff tape to hold the end down and protect the small data connections when I move it around.

Step 2: ESP8266 Hardware & Firmware

The PCB in the photos is of the prototype which I'm currently testing. It is not quite finalised so the PCB files aren't yet public. I have however put the schematic above. There are also earlier schematics available on my github along with a Max485 to Pixel schematic needed if you use this schematic in it's entirety - I bypassed the OK & Max485 in the schematic above for my testing.

Ensure you have the latest ESP8266 Arduino Core files and the latest Arduino IDE version.

You can get the latest source code and pre-compiled binaries for this project from my github. You can also submit bugs or requests using the Issues tab there or you can post in the comments below.

Flashing:

Open the source file, connect the ESP8266 and flash it. I'm not going to cover this here as it's already been covered.

Once you've flashed the ESP, unplug it for a few seconds before repowering it. I find a soft reset doesn't always work for me.

The next time you want to flash firmware, you can do so via the web UI explained in the next step. In the Arduino IDE, goto Sketch->Export Compiled Binary to generate a .bin file in your sketch directory. Then goto the ESP web UI, select the firmware tab and upload it there. This is much easier then connecting a USB-serial programmer each time. You can also use pre-compiled bin files from my github when they're released.

Step 3: EspArtNetNode Config

Now that you've got the device firmware installed, we can start getting everything connected.

Your computer should be able to see a WiFi network called espArtNetNode_xxxxx (the network will have a random number based on the chip's ID). Connect to it - the default password is byMtongnz2017 which can be changed later if you wish.

Once you're connected, open your browser to 2.0.0.1 and you should see the settings UI shown above. The first page gives you a run down of your settings.

Head to the WiFi settings page. Either enter your WiFi SSID and password or you could use stand alone mode. Click save - the save button should turn green to indicate the ESP has saved the settings.

If you need, head to the IP settings page and set a static IP. Once again click save.

Now unplug your ESP, wait a few seconds and repower it. Once again, I find it sometimes doesn't work when using a soft reset.

Reconnect to your main WiFi and you should be able to now point your browser at your ESPs new IP. If you're using DHCP, you may need to check on your routers config page to find the IP. You should see the same settings UI.

Head to the port A and/or port B settings. Choose WS2812 as the port type then click save - you should now have options for your pixel output, filled with the defaults which should be fine for most people.

First set the protocol - I use Artnet but you can use sACN if desired. sACN will still use Artnet for discovery and configuration.

Next, set the number of pixels - less pixels per port will make the device faster so it pays to set it to what you actually have but leaving it higher wont cause any issues.

Make sure you have pixel mapping as the mode. 12 channel FX allows you to control all your pixels while only using 12 DMX channels. It's explained more on my github.

Finally set the Net, Subnet and Universe settings. Each DMX universe allows 512 channels, so 170 RGB pixels. Hence why we need 4 universes for 680 pixels :)

Once everything is set, click save again. Make sure you click save if you intend to leave the page as the device won't prompt you to save and you'll lose any changes.

Step 4: Jinx Config

Jinx is a free software for controlling LED matrices. It is not the only software for this - there are heaps of others available, both free and paid.

Start off by unchecking the Start Output option in the Setup menu. You'll be unable to make any changes while this is enabled.

Now we need to add some Output Devices, also in the Setup menu. Click Add, select Artnet or sACN, turn off Broadcast, enter the ESPs IP, enter the Net, Subnet and Universe as per the settings from the previous step, and then click OK to save the device. You need to add a new device for each universe you'll need - I'm using 3 for my 450 pixels.

Once you've added all your devices, click Close. Open the Matrix Options and enter your pixel dimensions - for me it's 30 pixels wide by 15 high. I don't touch the other options. Click OK to save the settings and close the window.

Now open the Output Patch. This is the tricky part and you must match each pixel in the physical world with each pixel in Jinx. My pixels are patched in a snaking pattern, starting at the top left corner but you can have them in any configuration you'd like. Start by clicking Clear Patch - the patch should already be clear but this makes sure.

Red squares means there's no output patched to that pixel, green means there is. Click a square and you'll see the device it's patched to and the channel for red, green and blue. You can manually enter these for each pixel but that'll take a while.

Select the top left corner and click the Fast Patch button. Select the dimensions for what you're patching, for me it's X: 30, Y: 6 (180 pixels - it'll only patch 170 as that's the max per universe). In patch mode, select the wiring type you used, for me it's snake lines starting top left. Set your pixel order - normally RBG for ws2812. For the first channel, set it as 0 (Jinx counts from 0, not 1). Select your device - mine is 192.168.0.37 (0 | 0 | 0). Now click OK and your channels will be patched.

Use the fast patch in combination with manual patching until your entire matrix is patched. Then click close on the patch window.

Go back to the Setup menu and check the Start Output option.

Jinx should now be sending data to your pixels via the ESP - but it's probably all black for now. Have a play with the various effects and find something you like. Jinx allows you to scroll text, play video, have an EQ running and you can store scenes for later callback.

Step 5: Bugs and Future Goals

As you can see here, there are a few bugs and feature requests that still need to be addressed. I'm going to discuss the main ones below and also mention my give away for people who help me out with these.

Main Bug:

The biggest bug at present it a watchdog timer reset which occurs about 10-20 minutes into operation. I haven't been able to find the cause of this yet. Suggestions for a cause at this stage are that it's related to a rouge interrupt or possibly the WiFi/service routines being blocked for too long. I am offering a reward for the person(s) who can fix this issue.

Feature Wish List:

Many of the other issues are more feature requests. They range from web UI improvements to support for other pixel types.

I would like to see a scene storage feature added as I have in v1.2 of this device. With the addition of the ws2812 support, there is a lot more data to store. I'd also like to be able to store chases. This is a feature for which there is a reward offered.

People would also like to have a hardware button or screen to select stored scenes. Once scenes storage is implemented, I think this would be easy to add.

I'd also like to allow DMX inout to control ws2812 output or DMX scenes on the other port. This may be quite tricky to implement.

Give Away

I am offering a few of my PCBs featured in this Instructable as prizes/rewards for people who contribute to this project. In addition to the 2 mentioned above, I'm giving one to someone who contributes the most. They will be fully populated and flashed with the latest firmware. Details are here.

2 People Made This Project!

Recommendations

  • Woodworking Contest

    Woodworking Contest
  • Classroom Science Contest

    Classroom Science Contest
  • Colors of the Rainbow Contest

    Colors of the Rainbow Contest

68 Discussions

0
None
DJ_BREIKO

5 weeks ago

Hi everyone. It is working forme, but with two minor issues.
The first one is about using the two outputs (Port A and Port B) to drive 680 LEDS each. There is some delay on the 7th and 8th universes.
The second issue happens when I try to generate the bin file again from Arduino IDE I am getting the following error:
C:\Users\elton.pimentel\Downloads\ESP8266_ArtNetNode_v2-master\ESP8266_ArtNetNode_v2-master\source\espArtnetNode_2.0.0_b5g\ajax.ino:101:55: error: ambiguous overload for 'operator~' (operand type is 'IPAddress')
deviceSettings.broadcast = deviceSettings.ip | (~deviceSettings.subnet);
Does anybody has some fixes for any of this problems?
Thanks.

1 reply
0
None
DJ_BREIKODJ_BREIKO

Reply 5 weeks ago

Regarding the problem with the ambiguous overload, the solution was simple. I have cahnged the code line to deviceSettings.broadcast = uint32_t(deviceSettings.ip) | ~uint32_t(deviceSettings.subnet);

0
None
mmorlan62

3 months ago

I just discovered this project and am totally jazzed. I've done some DMX stuff but this will be my first attempt with ArtNet. Thanks for leading the way.

This will be a perfect compliment to my DMX Node project, which has smaller BOM. I note you added opto-isolators with your latest design. Excellent. I only used one for my receive-only node but that still left the output pin exposing the board to transients. Fail. Time to redesign that.

0
None
ChiefTrippinBulls

4 months ago

Alrighty, I've scoured just about every comment and read both versions of this project and I can't seem to get it to output to LED's with a nodeMCU.

Changes undergone in my limited understanding of this :
-uploaded fresh .bin through firmware option on esp.
-output from tx
-3.3v regulator going to esp w/ 5v rail on side for ws2812's, all powered from a stand-alone psu. USB power removed once IDE work was finished and esp configured online
-tried cpu speed to 160mhz for IDE upload (couldn't interface with esp on browser beyond load screen). Reuploaded at 80 as that was the most progress



Present Status:
-OTA interface works great, all settings easily changed, OTA update received
-Occasional all-white on the led's, doesn't seem to be linked to anything but moving pins around
-jinx I believe is configured correctly (refer to pictures) as I've used the same setting with the same static ip with another unit (teensy). The only thing that makes me think otherwise is the Artnetominator is showing that, although the node is being seen, no data is being output anywhere.
-Unit is nodeMCU 1.0, i'm pretty nub at this, and I'm a visual person. I don't think I messed up the wiring but it's hard for me to understand diagrams so I could of (breadboard pictured)
-When outputting artnet from QLC+, Artnetominator showed that it wasn't outputting to the nodes specifically even though it was directed towards the node's ip. BUT the led's turned on all white and one blue (maybe fried?) (not the intended setting and the LED's didn't change from there.) Even stranger was the tiny blue led from the ESP started to flicker very quickly and remained solid after closing QLC+.

I honestly am so frustrated with this project that I'm resorting to bothering ya'll. Thanks to any assistance from anyone.


IMG_20190123_135616.jpgIMG_20190123_135633.jpgIMG_20190123_135642.jpgIMG_20190123_142024.jpgIMG_20190123_142530.jpg
0
None
Osuspiro

1 year ago

That's a cool project, and it works form me at the on the first try.

I connect to jinx! and resolume and works well.

There is only an issue that turns me out. Sometimes when the NodeMCU was plugged off lost the configuration information about the wifi it has to connect and i don't know why.

Anyone has an idea why?

Thanks for all your work!!

3 replies
0
None
ahlynskyOsuspiro

Reply 11 months ago

Im trying to get this working with the NodeMCU as well and cant for the life of me figure out what pins correspond to the A and B channel. Do you have any insight? Thank you!

0
None
ChiefTrippinBullsOsuspiro

Reply 4 months ago

It's currently on the tx pin to no avail. Node is now recognized on Artnetominator and I believe Jinx is configured correctly (it worked with same settings and ip assignment) but artnetominator says that no data is being sent out to the esp (I think?)
0
None
JoeD182

5 months ago

I finally got around to adding a single strip of the WS8212s for some Christmas lights outside!
I did notice the bug and though it's not a fix, i was able to run it for a few hours with no trouble the other night.
I noticed that if i changed the FX channel every 20 min or so, it seemed to run just fine throught the night.
I am going to try and program a scene in Freestyler to sycle the FX channel on it's own so i don't have to babysit it.
Otherwise, works great!

0
None
fthebunny1PaoloF30

Reply 5 months ago

You should make a push request on his github project, you would get a better feedback. Do it before I push back your solution :P

Thanks by the way

0
None
DBender

Question 7 months ago

Hello, have any updates been made to the bug fixes?

0
None
aeinfaithelijah

Question 10 months ago

Hi, noob question here can i use this diagram for my open dmx to control ws2812b?

Thank you :)

convert_max485_to_pix.png
1 answer
0
None
tmdrake

9 months ago

Ya, finally got mine working... Seems the 470 ohm resistor can cause a slewing problem due to the wires used to transmit the data to the LED's. I removed it on the WS2811 12MM strings.

artnet.jpg
0
None
tmdrake

9 months ago

Seems like i'm stuck too...all white an no control. Maybe TSHOOTING tonight.

0
None
Ronald2016

Question 1 year ago

Hi, what a great project and code!

I have connected 1 meter ledstrip with 60 ws2812b leds to an ESP8266 with firmware v2.0.0 beta 5g.

The leds react to ArtNet but the leds at the end of the ledstrip are flickering.

When I change 'Number of Pixels' in the Web UI to whatever number and save the changes the flickering stops and the whole strip works as expected.

After a reboot of the ESP8266 the flickering comes back. Again, when I change the 'Number of Pixels' everything works fine until a reboot.

I tried many different hardware related options: with/without resistor in the data line, different power sources, power the strip from both sides etc. With no succes.

Is there something in the Arduino code I can change to prevent the flickering? Many thanks!

1 answer
0
None
JörgS1Ronald2016

Answer 9 months ago

the flickering probably comes from too little power. just put on 5V at the end of the stripes again.

0
None
JörgS1

Question 9 months ago

I would like to use a NodeMCU V3.1 for the Artnet node, is there a layout for the PCB?

0
None
MichaelJ205

1 year ago

Hi,
I tested it on WS2812 strips but it doesnt work. The problem is that my WS2812 strips work on 800kHz and the ESP is outputting 400kHz for the strips. I found a hint of that switch in your ws2812Driver file, but I cant get it to work with double speed. Can you say where I have something to change?