# Pixel data and DMX data concurrently?

**URL:** <https://wled.discourse.group/t/pixel-data-and-dmx-data-concurrently/12004>\
**Category:** Issues\
**Created:** [June 9, 2024, 9:13pm UTC](https://wled.discourse.group/t/pixel-data-and-dmx-data-concurrently/12004 "2024-06-09T21:13:39Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![jasonsomers](https://yyz2.discourse-cdn.com/free1/user_avatar/wled.discourse.group/jasonsomers/32/7131_2.png) [@jasonsomers](https://wled.discourse.group/u/jasonsomers)\
**Post date:** [June 9, 2024, 9:13pm UTC](https://wled.discourse.group/t/pixel-data-and-dmx-data-concurrently/12004/1 "2024-06-09T21:13:39Z")

</div>

I would like to pass DMX (serial) data through output one of an ESP32 build.  
I would also like to pass pixel data through output 2.

Using the firmware from [WLED-wemos-shield/resources/Firmware/@Aircoookie/Dev/0.15.0-b3/WLED\_0.15.0-b3\_esp32\_dmx.bin at master · srg74/WLED-wemos-shield · GitHub](https://github.com/srg74/WLED-wemos-shield/blob/master/resources/Firmware/%40Aircoookie/Dev/0.15.0-b3/WLED_0.15.0-b3_esp32_dmx.bin)

I have a single PAR lamp on output 1 and it is working well. (GPIO2)  
When I add 50 pixels to output 2 (GPIO12), they work fine.

However, when I increase the number of pixels to about 73, the firmware crashes and becomes unusable unless re-flashed.  
If I keep the number of pixels to 72 or below, all is good.

The issue does not seem to be related to the number of outputs. I can run pixels on outputs 2,3 and 4 as long as I keep the total number of pixels below 73.

Is this a bug? Or is this expected behavior?  
Thanks,  
Jason