Beiträge von mammut

@penfold42 I can test with multicast. I am going to be on vacation the next week and am not sure when I'll be home to try it out though. I agree with you that splitting the universes across separate multicast addresses is not needed. For multicast maybe you could define which universe to start at in the Device config? That would give some flexibility to the multicast device setup.

I am trying to think through a use case for a DMX _listener and I couldn't come up with one.

Also on the ESPixelStick, Shelby is working on a 2.0 version I don't believe he has up in github yet. You may want to ping him. He in on diychristmas.org and doityourselfchristmas.com with a user name of sporadic. Most of the changes were around the UI and updating the firmware via a web interface I believe rather then pixel related.

@TPmodding No ESP for the 2048 LEDs.

I am using 4 P10 panels that have 2048 LEDs total to a RPi B+ with a matrix hat. I run a package on the pi called FPP that is used for mainly running Christmas light sequences but can also be used to bridge e1.31 to the P10 panels.

There is a lot of cool stuff going on with these LEDs being used for Christmas lights.

P10 Matrix Hat: https://ronsholidaylights.com/raspberry-pi-matrix-adapter/

FPP: http://www.falconchristmas.com/wiki/Falcon_FPP

Guide to setting up the panels, it uses a BBB and a different hat but same idea: http://www.diychristmas.org/wi…toscroller_Matrix_Display

Now that I have the right branch it works perfectly.

No issues running all 2048 leds in my p10 matrix through another e1.31 device and it also works with my regular string of ws2811 leds with the ESPixelstick.

This is really going to open things up for a lot of DMX devices. Great work and thanks!

Let me know and I can test out any other updates for it.

I must have screwed something up in my conf file. Getting this.

[HYPERIOND LedDevice] <INFO> configuration:
{
        "colorOrder" : "rbg",
        "name" : "DMX_e131",
        "output" : "192.168.1.210:5568",
        "rate" : 1000000,
        "type" : "e131"
}


[HYPERIOND LedDevice] <ERROR> Dummy device used, because configured device 'e131' throws error 'std::exception'

Tried with your branch and no luck. I am not seeing the packets hit the e1.31 device.

I tried using my 170 led conf file as well as a 2048 led conf. Both had the same result as no packets showing up at the pixel stick.

Was able to compile and test it out and it is working without issues with the max 170 pixels.

When you get it setup for multiple universes I can test out with up to 2048 leds with my P10 matrix to really push it.

Only issue I saw was it appears green and blue are swapped. I had to setup rbg in the .conf file rather then the normal rgb I have setup with my other e1.31 sources.

Wow! Amazing progress.

Sorry, haven't been getting email notifications on this thread.

I will test it out this evening.

Main reason for e1.31 is I already have some modules that support it and it would be easy to integrate for me. Totally understand if DMX type of interface is not in the scope of the project.

Thanks

http://forkineye.com/espixelstick/

I have a custom computer controlled Christmas light setup that accepts e1.31 traffic over wifi using the esp8266 to control ws2812 pixels. The project link is below. I currently have a wired Hyperion setup using the ws2812 connected directly to my Pi but would love to make this wireless and I have a spare couple of esp8266 e1.31 controllers around.

I know redPanther has added support for fadecandy and through OLA it is possible to send e1.31.

Any chance of native e1.31 support?

https://github.com/forkineye/ESPixelStick

Thanks for looking!