Jump to content
Light-O-Rama Forums

confusing light show


qbutah

Recommended Posts

My Christmas sequences for my light shows had lots of problems. I added a new controller this year, CTB16PC factory built. When we initially started the sequences there was some channel on my older CTB16PC turning off and on when the new controller was running the arches. With advise from LOR we updated the firmware for our older controller to 4.32 version but the new controller came with 4.40 version. The Fireware update seamed to help but as I added more sequences which included the arches, I started finding more and more channel not working at times or on when the sequence had them off. I check cat5 cable routings to keep them away from power cords and even change power sources but could not get rid of the problem. By this time we were well into the Christmas time and I had to just let them act the way they wanted, but now I have time and wish to resolve these problems before starting set ups next fall. Would it be better to have both controlles with the same firmware or what?

Link to comment
Share on other sites

Is it possible that you have more than one sequence running at the same time -- for example, one in your show's musical section and another in its background section -- which both have channels set up to represent the same physical string of lights? If so, they will compete for control over that string of lights, and odd behavior can result.

Or, the same sort of thing can happen within a single sequence, if you have two or more channels set up to represent the same string of lights.

I suggest checking your show with the LOR Verifier. It can detect a bunch of different types of problems and potential problems, and this particular one is among them.

Make sure that your show is scheduled - the Verifier only checks a show if it's scheduled, and only checks a sequence if it's in a scheduled show. The show doesn't have to be running, though.

Link to comment
Share on other sites

I will add that the firmware is most likely not the issue. I had a dozen CTB16PC V2 cards, with 4.40 (the only firmware that works on them) mixed in with about 30 CTB16PC V1 cards running 4.32. We saw no issues like this.

Beyond the items Bob suggested looking for, I would look for any sources of electronic noise. CFL bulbs powered from the controller is a big source, but I have also seen it from CFL bulbs on the same circuit. Others have reported seeing similar issues when doing lots of dimming on channels, and having the RS-485 cable too close to the power cables.

Link to comment
Share on other sites

I would say to also make sure that 1) you do not have more than controller with the same address and 2) that channels are assigned correctly in the software. Both of these should be caught in the verifier.

Link to comment
Share on other sites

qbutah wrote:

The display is now put away but I still have access to the controllers. Can I run the verify with just the controllers connected to the computer?


The verify only checks things (files, configuration, etc... ) on the PC. Nothing needs to be connected to run it.

Dan
Link to comment
Share on other sites

I'm with Salts,

I would like to see the OP pull out and hook up one controller at a time and confirm the addressing of each controller.

I am not really sure that the verifer would catch two rows of the seq. editor with same addressing. Is it possible for the verifier to catch this issue?

I know as I was hooking up my controllers for the first time this year. That one did seem to reprogram it's self to a different address. I dont remember all of the details any more. But it did act queer till I caught on to what was happening. Once I reset the address, all was good for the rest of the season, with the controllers. Did have a little problem with one string of lights and a bad quick connector (see stake ons) that I made off of the controller.

Link to comment
Share on other sites

I am not really sure that the verifer would catch two rows of the seq. editor with same addressing. Is it possible for the verifier to catch this issue?

Yes, it does.
Link to comment
Share on other sites

Guest
This topic is now closed to further replies.
×
×
  • Create New...