Artnet to OctoWS2811?

Status
Not open for further replies.
I'm not sure I understand. That sketch will work with 8 universes, the number of universes is automatically calculated according to the number of leds.
 
Yes I understand how it should work but it does not want to automatically calculate the number of universes, sketch works well only by 170 pixels, 171 pixels after adding the sketch is not working properly neither of the universe does not turn 8 do not know where the problem may be ?.
 
That does not work either, so there is no need to modify certain libraries in order to use sketch with teensy 3.1 ?.
 
Normally no, did you try the other examples like ArtnetReceive to see if you get data through the serial monitor ?
did you change the mac address ?
 
Last edited:
Already it works but only for a maximum of 3 numStrips and ledsPerStrip to 170 if I use more than 3 outputs so it stops working, you tried it on the boards Teens 3 will it work properly ?.
 
I tried it on the Teensy 3.1 with the wizio820. As Headroom said the ethernet shield might be a big limitation...
 
It could be another issue though. When you say it does'nt work, do the lights light up or is it getting slower ?
how many leds in total are you controlling ?
 
Already it works but only for a maximum of 3 numStrips and ledsPerStrip to 170 if I use more than 3 outputs so it stops working, you tried it on the boards Teens 3 will it work properly ?.
folny, from my previous post, this might help:
So, have run some data transfer tests with different permutations. Using my old macbook connected directly to the ethernet module i can transfer up to about 16,000 led data sets a sec. Above this, the frames are incomplete. This test was done with these scenario:
90*8 leds @ 20fps
80*8 leds @ 25fps
50*8 leds @ 40fps
There was a difference in success when using different universe numbers. I found that using larger universe size and fewer universe was more successful than using lots of smaller universe ( i guess that this is to do with the packet overhead building up). An example was that 50*8leds @ 40fps worked well with universe size of 50, but not with universe of 25 (i.e 16 universe rather than 8). This test was carried out using the Pixelcontroller software for artnet output and the wiznet 820 with teensy 3.1.

for your setup, 170*3 = 510
16000/510 = 31, so you should be able to get 30fps before data transfer problems set in, BUT ... longer strip length = more time required for updates

Do you have the same problem using the tpm2 capability of the software . http://www.live-leds.de/
from their site it looks like live-LEDs supports this option rather also.
 
Last edited:
Thank you for your advice TPM2net I still have not tried that sketch you recommend that worked for you on the Teensy 3.1 ? I found it more and I do not know whose work properly.
 
@mortonkopf In the code I posted you should see slightly better results because leds.show() is called less often. Not sure what the limit is but when setting pixelcontroller to control 1400 leds my single 492 leds strip was updating at 44 fps
 
that sounds fab. I remember now about that discussion on the leds.show() in the routine being called within the loop rather than outside of loop once all frames were loaded. I didn't pursue it further at the time. glad you resolved it.
 
When you set up more than 80 pixels, the number of universes is automatically reduced to only 7 I tested it with a sketch ArtnetReceive I think that this has resulted in my Ethernet Shield. I would like to ask if you can help me I would like to modify a sketch for FastLed libraries since it uses SM16716 pixels you can try to edit the sketch? I'm not such a good programmer :)
 
That's because they designed it for the normal Arduino and the 5100 chip which is very slow. Getting the WIZ820io will really speed things up for you.
 
Status
Not open for further replies.
Back
Top