Using CCB's in DMX-Xlights

[colonelcline]

And probably all CCD's? I googled myself silly trying to find this information and never found one single answer. Suspect people figure it out and then that's it. Here is how I made them work, trial and error:

The CCB;' are hard coded like the 16ch boxes so a CCB ID   uses channels 321-470. anything above ID 17 exceeds the 512 limit. See DMX-DOC.pdf
LOR S3 is the only thing looking at ID's and since there is no handshake you could have multiple ID's on the same network. They play the same things.
LOR S3 and the e 1.31 network interfaces don't care about  ID's so you could have many ID 1's. They all get sent the data for ID1 and  thru the com or ip# as sequenced.
In HWU, you set the CCB's to RGB only so as to ignore the macro channels.
In S3 you may want to delete the 151-157 macro channels altho xLights allows for that and S3 is OK with them.
If you only have CCB's in 1 universe, ID 1 = 1-150 and ID 0B = 161-320 and ID 15 = 321-470 works OK. Gets confusing for me when I have 16h boxes in a Universe too.

xLights test is wonderful if you have all numbers set right in the universes. But I found da_131.exe easier to go hunting for "where is it" when it comes to the LOR products. Kinda a quirky program but works. Hope this helps someone from googling themselves silly!

Now comes the caveats. Works for me, your mileage may vary.

[bullets]

Colonelcline:
My name is bullets (aka Paul) and I've been googling myself silly for weeks! lol

Seriously, I've been trying for weeks to get my 4 CCB's into a DMX network and to work in xLights.  After reading your post I'm still a bit confused about setup and I was hoping you had a few moments to clarify.

"LOR S3 is the only thing looking at ID's and since there is no handshake you could have multiple ID's on the same network. They play the same things." -
Does this mean that all of the CCB's will be doing the same output?

"LOR S3 and the e 1.31 network interfaces don't care about  ID's so you could have many ID 1's. They all get sent the data for ID1 and  thru the com or ip# as sequenced".
How are you doing it??? Are you using an LOR 485 Dongle with a cross over cable?  Are you using something else like a SanDevices E682 in DMX mode?  I have both.

"If you only have CCB's in 1 universe, ID 1 = 1-150 and ID 0B = 161-320 and ID 15 = 321-470 works OK. Gets confusing for me when I have 16h boxes in a Universe too."
How many CCB's are you using and what ID's are you using?  What are the other 16 boxes you are using and how are you connecting them?

Thanks
bullets

[colonelcline]

Colonelcline:

"LOR S3 is the only thing looking at ID's and since there is no handshake you could have multiple ID's on the same network. They play the same things." -
Does this mean that all of the CCB's will be doing the same output?

Only if they are in the same universe with he same ID#. S3/XL>IP#>Universe>Channel
This is Unicast. Multicast might be different but din't think e1.31 looks at ID's. .

"LOR S3 and the e 1.31 network interfaces don't care about  ID's so you could have many ID 1's. They all get sent the data for ID1 and  thru the com or ip# as sequenced".
How are you doing it??? Are you using an LOR 485 Dongle with a cross over cable?  Are you using something else like a SanDevices E682 in DMX mode?  I have both.

They should all work about the same. I use Pixlite-16's and 4's. They have RS-485 outputs. I use a LOR crossover cable (http://www.seasonalentertainmentllc.com/store/en/adapters/107-lor-dmx-adapter.html) and then to the CCB or any LOvice, then CAT to the CCB. Think you might need to use one of your outputs?

"If you only have CCB's in 1 universe, ID 1 = 1-150 and ID 0B = 161-320 and ID 15 = 321-470 works OK. Gets confusing for me when I have 16h boxes in a Universe too."
How many CCB's are you using and what ID's are you using?  What are the other 16 boxes you are using and how are you connecting them?

I've attached my excel spreadsheet. My universes are a mix of the LOR 16 channels and CCB's. I've retired all my CCR's and gone with 2811/12 strips (http://www.holidaycoro.com/Smart-Pixel-RGB-LED-Strip-5v-30Leds-M-p/660.htm).

I've never been able to use my CCB's as a 100 bulb prop but think that would maybe effect the hard coded channels? Like e one hard coded ID set of channels 1-300 vs. 2.

Thanks
bullets

[attachment deleted by admin]

[colonelcline]

Note: my spreadsheet had some errors but is an example.

I now have all my CCB's working under 1.31. I discovered that if in HWU you set it as one string, 100 pixels and an ID of one, it comes out channels 1-300. But ID 15 arts at 321.  Be sure and select RGB only, no macros. You can see where there are some limitations on ID's and channels.I updated my firmware to 1.16 one controller was not responding and had an older version.
Note. I have 3 ID1's now all under 1.31 b different universes and they all test fine. I'll have to go back now and change all my songs to the new config in Lor and then convert back to XL and fseq. Geesh.

One oddity is that one bulb and the same in each of my strings and not the "connection" one is off color. Going  line my ducks up and see what it does with a sequence.

[bullets]

Thank you Colonel I'll give it a try... let's hope I make out as good as you did.

[colonelcline]

Thank you Colonel I'll give it a try... let's hope I make out as good as you did.

I just updated a LOR SEQ and channel config, then converted that sequence into xseq format and played it in Preview and the CCBs worked as programmed. Going to use LOR next and make sure it works as well. Still "fiddling" with the Pi Player.

L8R: And LOR show Player has no problem playing the Sequence and CCB's.