connecting OLA+opc client + opc node server [rpi-ws281x-native] + ws28xx matrix 200 led
302 views
Skip to first unread message
faisal md
Jul 2, 2016, 2:08:19 PM7/2/16
to open-lighting
hi all, firstly, sorry if this might not relevan topic in this group because i also using opc node server in my setup.
does anyone success to connect more than 1 universe with this setup?, i can't pass thru 2nd universe in ola.
actually i follow tutorial from here
http://x10linux.blogspot.my/2015/08/driving-ws281xs-leds-on-raspberry-pi.html
hardware - raspberry pi rev 1.2
raspbian jessie lite/ Version 0.10.2 - compile from git
led ws2811 - 200 led 'chain together as matrix'
control from other laptop - jinx 2.4
target = 127.0.0.1:7890
target_127.0.0.1:7890_channel = 0
target = 127.0.0.1:7891
target_127.0.0.1:7891_channel = 1
but only 171 led work, not 200 led.
some user in comments section suggest to remove led 'render', i'm not sure what he mean.do you have any idea about it?
thanks you.
index.js - node-opc-server / which i run as sudo / sudo node index.js
does anyone success to connect more than 1 universe with this setup?, i can't pass thru 2nd universe in ola.
actually i follow tutorial from here
http://x10linux.blogspot.my/2015/08/driving-ws281xs-leds-on-raspberry-pi.html
hardware - raspberry pi rev 1.2
raspbian jessie lite/ Version 0.10.2 - compile from git
led ws2811 - 200 led 'chain together as matrix'
control from other laptop - jinx 2.4
i already edit ola-openpixelcontrol.conf
-------------------------
enabled = true-------------------------
target = 127.0.0.1:7890
target_127.0.0.1:7890_channel = 0
target = 127.0.0.1:7891
target_127.0.0.1:7891_channel = 1
but only 171 led work, not 200 led.
some user in comments section suggest to remove led 'render', i'm not sure what he mean.do you have any idea about it?
Correct. Now 2 listeners. Removed the led 'render' in the first listener else would draw the 'array' before it had all the required data for the led string.
can you help me figure this out?
hopefully someone can help me, & sorry for take time.thanks you.
index.js - node-opc-server / which i run as sudo / sudo node index.js
Peter Newman
Jul 2, 2016, 3:31:37 PM7/2/16
to open-lighting
You're using OLA, so it's certainly relevant.
OLA deals in DMX universes (512 channels); 170 8 bit RGB pixels are 510 channels, so that's our limit per universe, and we don't spread stuff across universes due to issues with sync, timing and output.
I'm not entirely clear exactly what's being driven from where and how, but I suspect that's the root of your problem.
Reading the blog makes a bit more sense of it, you'll need to patch a second OPC universe, listen to that in your Node JS code and then output the whole lot to the SPI port. So as he mentions in the comment, you'll need a second server/listener on another port, then work out when you want to output the pixel data via the renderer command. As lowey71 mentions, you don't necessarily want just the first half, which is precisely the issue we hit and why we don't support more than 170 pixels via the SPI plugin.
Also see the discussion here for some other options, some of which don't require going to JS and numerous other protocols.
OLA deals in DMX universes (512 channels); 170 8 bit RGB pixels are 510 channels, so that's our limit per universe, and we don't spread stuff across universes due to issues with sync, timing and output.
I'm not entirely clear exactly what's being driven from where and how, but I suspect that's the root of your problem.
Reading the blog makes a bit more sense of it, you'll need to patch a second OPC universe, listen to that in your Node JS code and then output the whole lot to the SPI port. So as he mentions in the comment, you'll need a second server/listener on another port, then work out when you want to output the pixel data via the renderer command. As lowey71 mentions, you don't necessarily want just the first half, which is precisely the issue we hit and why we don't support more than 170 pixels via the SPI plugin.
Also see the discussion here for some other options, some of which don't require going to JS and numerous other protocols.
Johannes Tamegger
Apr 17, 2018, 7:00:26 PM4/17/18
to open-lighting
hi, now 2 years later I am having the same problem. So did you managed?
Peter Newman
Apr 17, 2018, 7:25:35 PM4/17/18
to open-lighting
Where's your data actually coming from and going to Johannes?
As I alluded to in my reply (but seemingly failed to paste a link in somewhere), there may well be a better way, depending on what exactly you want to do...
As I alluded to in my reply (but seemingly failed to paste a link in somewhere), there may well be a better way, depending on what exactly you want to do...
Johannes Tamegger
Apr 17, 2018, 8:04:05 PM4/17/18
to open-lighting
Hi, Peter!
I am using the very same setup as in the blog post but trying to use more than one univers. I am using glediator to send Artnet to ola i created 4 univeres with different ports which works perfectly fine. Ola is getting the data for all 4 universes. So far so good. I am using the same index.js file as posted here besides i created 3 additional listeners for all 4 ports. The problem I have is that all the universes are overlapping in the first 170 LEDs. So clearly i need to give them an LED offset. I just couldn’t figure it out how to do that.
And thanks for your time Peter I appreciate it
I am using the very same setup as in the blog post but trying to use more than one univers. I am using glediator to send Artnet to ola i created 4 univeres with different ports which works perfectly fine. Ola is getting the data for all 4 universes. So far so good. I am using the same index.js file as posted here besides i created 3 additional listeners for all 4 ports. The problem I have is that all the universes are overlapping in the first 170 LEDs. So clearly i need to give them an LED offset. I just couldn’t figure it out how to do that.
And thanks for your time Peter I appreciate it
Peter Newman
Apr 20, 2018, 7:07:05 PM4/20/18
to open-lighting
Try this Johannes:
https://github.com/wwwil/node-opc-server
I've no idea if it's what I was trying to link to last time or not, but looks like it may do the job...
https://github.com/wwwil/node-opc-server
I've no idea if it's what I was trying to link to last time or not, but looks like it may do the job...
Michael Muck Kremtz
Apr 9, 2020, 7:02:12 PM4/9/20
to open-lighting
Hi everybody. I'm just taking my fist steps with OLA an Raspberry Pi and when folloing the installation instructions I run into the problem that
wget http://node-arm.herokuapp.com/node_latest_armhf.debresults in
HTTP request sent, awaiting response... 502 Bad Gateway
2020-04-09 21:55:50 ERROR 502: Bad Gateway.
Node.js is an essential component as far as I understood it.
Is there any workaround for a fresh raspbian buster installation?
Will there ever be a new binary package?
After reading a lot of old posts I'm glad I found this group here!
Have nice easter days everybody!
E.S. Rosenberg
Apr 9, 2020, 8:04:21 PM4/9/20
to open-l...@googlegroups.com
Maybe when the document you refer to was written nodejs in the debian/raspbian repositories was not up to date causing the need to install it from an external source but these days apt-get install nodejs should do the trick.
As for the rest of what you refer to I don't know, the repo has not been updated since 2016, not encouraging...
Op vr 10 apr. 2020 om 02:02 schreef Michael Muck Kremtz <mkr...@web.de>:
--
The Open Lighting Project: open-l...@googlegroups.com, #openlighting (irc.freenode.org)
To unsubscribe from this group, send email to open-lightin...@googlegroups.com
For more options, visit https://groups.google.com/groups/opt_out?hl=en
---
You received this message because you are subscribed to the Google Groups "open-lighting" group.
To unsubscribe from this group and stop receiving emails from it, send an email to open-lightin...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/open-lighting/5110b9ef-1f77-47b2-8a52-95427fd527fa%40googlegroups.com.
Reply all
Reply to author
Forward
0 new messages