Jump to content
Light-O-Rama Forums

Leaderboard


Popular Content

Showing most liked content on 04/06/2018 in all areas

  1. Enclosure

    Here is Kevin's YouTube video. Very impressive wiring. Tom
  2. Continue The Story In 3 Words...

    Those damn owls!
  3. New Controller and Old Controller

    Correct - the likelyhood is that your older controllers do not support enhanced networking. As far as I know, if the controller has a green status LED, it is Gen3 and will handle enhanced, and if it's red, it is older and won't. There is really nothing to be gained by moving to DMX - UNLESS you have DMX only controllers. In fact, you can put more channels on a LOR network than on a DMX network. The iDMX is perfect for someone who is running LOR networking and needs a fairly small number of DMX channels, but does not want to run a separate network. Your one DMX spotlight is a perfect example of a use for the iDMX. The Booster adapter is generally used when you need to power one end of an ELL link. Since the default speed (56K if I remember right) is working fine for you, there is little reason to buy another adapter. The only reason to buy another adapter is to have a spare, or if you need to go to higher speed at some later date. BTW, one of my standard recommendations is to have a spare USB to RS-485 adapter. The reason is that if that fails, your entire show is dead until you receive a replacement. If / when you start using E1.31 for pixels, it would connect via an ethernet LAN (either the same LAN that you use for other stuff for the house or a separate dedicated LAN just for E1.31 traffic). Another one of my standard recommendations is that if you are running E1.31 in addition to LOR networking, use a different color cable. It makes it at least harder to plug a cable into the wrong type of device (which CAN be bad). In my case, my E1.31 LAN uses green cable, my "normal" home LAN uses blue cable, and my LOR networks use purple cable. I'm going to clarify that statement a bit. xLights is similar to Pixel Editor (or the Pixel Editor portion of S5). The Sequencer in S5 is similar to the Sequence Editor in S3 and S4. The big difference is that in S4, Sequence Editor, Pixel Editor, and SuperStar are all separate programs, where in S5, The Sequence Editor and Pixel Editor functions are in one program and SuperStar is sort of integrated.
  4. New Controller and Old Controller

    First thing. Forget xLights. You do NOT need to move to xLights. From your description, you are planning on staying with a relatively small channel count. As I understand it, the largest reason for going to xLights is large channel counts. Personally, I have no plans to leave LOR software - and I'm running 66K channels this year. This is my opinion, but as I understand it, xLights is essentially very similar to Pixel Editor (which I substantially dislike), so I see very little reason to even look at xLights - and no one has ever come up with a reason for me to try it. As for DMX, using LOR software, you CAN drive all or part of your display with DMX if you want or need to. An example of NEED to is if you have some stage spotlights that use a DMX interface. You can also use E1.31 which is DMX over ethernet. E1.31 is VERY commonly used for pixels. In my case, my 2017 display was over 75% E1.31. For 2018, it will be about 95% E1.31 despite adding over 100 channels on LOR controllers. As for networking, let me explain a couple. LOR non-enhanced network: Uses RS-485 as an electrical interface, so you use a LOR USB to RS-485 adapter. LOR has two versions of the adapter, the older black adapters which officially work up to 115K speed, and the newer red adapters that support up to 1,000K speed. Some people have reported being able to use the black adapters at higher speed, however my advise is that ANY time someone buys a LOR USB to RS-485 adapter, that they buy the high speed adapters (they are only $2.00 more). LOR Enhanced network: Uses the same electrical interface as non-enhanced networks. If you use intensity files (optional with SuperStar, required with Pixel Editor), you MUST use enhanced networking. Note that you can NOT detect inputs on an enhanced network, so if you use inputs on controllers or InputPup controllers, they MUST reside on a non-enhanced network. DMX: Uses the same electrical interface as LOR networks, although the wiring MAY be different (depending on the hardware). More on that part if you need it. You can use LOR USB to RS-485 adapters for DMX, but there are specialized DMX adapters that CAN work better. Again, more on that if desired. DMX is the standard interface for the stage lighting industry. E1.31: This is the same data protocol as DMX except that the data is encapsulated in ethernet frames and runs over an ethernet LAN. Because of the far higher speeds that an ethernet network can run, it is possible to fun FAR more lighting channels over an E1.31 network than either LOR of DMX. I can give you more details on all of what I just said, and more than happy to get you on the phone to better explain stuff too. I hope this has helped.
  5. Boy, i guess asking you to make this one was a good idea, seems to be very popular.
  6. Enclosure

    Holy hell! Never have I even imagined anything so massive. That is a lot of wiring and all coming from one central location.
  7. New Controller and Old Controller

    Enhanced network were added with S4. Using enhanced networks allows a larger number of channel commands per network - which generally means more channels. Because of changes in the data, older controllers can’t support enhanced networks, and some newer ones require firmware updates in order to do so. Use of enhanced networks also requires a Pro level LOR software license. If you are only running a few 16 channel controllers, you don’t need to use enhanced - unless you want to run Pixel Editor (which requires it).
  8. Input Device

    You can go to YouTube. Look up . Lafffchristmas. Reflections of earth. Light o Rama I won light o Rama contest with this one I'll send you a picture of pole with buttons if you send me your email I never going to use them anymore like to change display every few years . Dennis
  9. Enclosure

    I did the same basic build for my mega tree when I made up one box for controller cards for it. I have 96 strands of 70 count LEDs for the tree and a 3 channel star. I have to use 2 strands per channel (only because I made the tree bigger after I had the box built) but that has not been a big problem at all to my sequences and shows when I was still doing them. I have not had a show since 2014 due to health issues and other things but maybe I will get going again. I used a metal 24 x 36 x 8 deep NEMA enclosure which I picked up from an electrical supply house cheap ( they had ordered it for a customer who canceled the order on them). I put in 4 of the CTB16K cards, 32 outlets (cut so that it is really 64 single outlets), 2 ecs weatherproof Cat connectors, 2 30 amp weatherproof power connectors, and 4 lighted switches to be able to shut off any card for work if necessary. I mounted the box on a stand and painted it green with a big red bow so it stands next to the mega tree and just looks like a big present out in the display. The only drawback to it is that it weighs 87 lbs so you don't just pick it up and walk around with it! But it also makes it hard to steal at the same time I guess. It has worked out great for me here in upstate NY for many years so far with no fans or any trouble at all.
  10. Round power cable

    From the been there, done that department: Just about everything you buy from either a vendor or fellow decorator has whatever connectors THEY used. It gets real awkward real fast to have a bunch of different size/style connectors laying around. Choose your connectors and then stay with those EXCLUSIVELY. Replace everything else you might have and get rid of everything else. In my case, I settled on the 4-pin pigtails and extension cables from DIY LED Express. I use them on every RGB controller (whether pixels or dumb RGB) and every RGB/pixel prop in my inventory. It took me about a week to bring everything into compliance, but now I'm no longer held hostage having to use certain props only on certain controllers.
×