Jump to content
Light-O-Rama Forums

All Activity

This stream auto-updates     

  1. Today
  2. CMB24's have switches. be sure you have them firmly in On or OFF. You might exercise the upper octet switches(2,3,4,5) 10,11,12 are normally OFF. 12 is used to reset the board (see the manual for the sequence)
  3. This is where having a Hall Effect clamp-on Amp meter would be handy. Not cheap, but, they work sweet. Just like you would with the AC version Come to think. Use a Kill-a-Watt. Very cost effective. Measure the idle watts, then set 1 string to white. The diff, should be close enough for planning (you couls then do multiples, to see if it tracks
  4. Don't go off of what the manufacturer tells you. Test the strings. You can buy a $10 meter from Harbor Freight. I've never had 12v nodes that were 60ma white. I run my whole display at 30% intensity or less. Average is around 20ma white at 30% intensity
  5. Well I hooked up my three controllers. 2 basic 16 channel and one 24cmd flood controller. They are 1,2,3. When i do a network search it is finding 6 controllers. 1 and 2 seem fine but there is a 3,13,23,33. All 24cmd controllers. Tried to unplug the flood controller and reset it, but now the unit ID wont change. I have no idea what I did to cause this or how to correct it. mike
  6. In the Advanced Port Setting you can set the Max Intensity. You can also adjust the intensity in the Sequencing Suite Software as well.
  7. Can you tell me how the pix Con 16 does it thank you
  8. Yesterday
  9. The amp rating of the controller board is just that - a max rating. Has nothing to do with how much current is passing through it at any given time. As a general rule of thumb, most controller boards are rated for either four or five amps per output. There is also generally a max limit for either the entire board or each half. Your three amps per output should be fine for any controller that I know of. As for your last paragraph, the Pixie controllers have no ability to reduce the outputs by a percentage, the PixCon16 does.
  10. This is the reply from the company from whom I bought my 50 count 12v rgb smart pixels from. I have the lor 16 channel pixel controller v4 and I also have pix con 16 pixel controller and I also have 4 channel pixel controller. I don't think these boards have the ability to change the amps built in to them.I believe it has to be done in the hard ware utility is this right new to rgb ??? thank you don't have a video on this, but our 12v 12mm pixels are 0.06amps per bulb, if you are running the full white. The amps change based on the color the bulb is projecting. So if you plan on 3amps for a 50 count strand you’ll be safe. (50 x 0.06amps = 3amps) The calculate watts: amps x voltage = watts In the case of the 50 count strand: 3amps x 12v = 36 watts. Again, this assumes you are running full white on the lights which would be your worse case scenario. Not to complicate this, but most rgb controllers have the ability to reduce the output of the strands. So you could set the controller to 50% output, which would reduce you to 1.5amps, yet, the brightness of the lights will still be good enough for your display. This would let you reduce the amount of power supplies you need to run your lights.
  11. It is usually in August but hey, who really knows.
  12. Does anyone know the timeline of the summer sale? Is it early summer? If I miss this sale I would have to wait till next year Thanks, AJ
  13. Why make it more complicated than needed? Here is a good read for you as far as setting up the pixie series controllers. Your pixie 16 can be set to unit 1 and your pixie 8 to unit 11. That would make your next available unit ID 19. The pixie series do not use the standard numerical system while assigning unit ID's. Also,my pixie controllers have seen +100 temps and run many hours a day without a fan. My pixie16 and 8 combo does have vents but none of my other pixies have any vents. Have not had a failure. Also I recommend using the control panel to set the unit ID's. The main reason, if you ever need to change them you do not need to open the enclosure. Its all explained in my writeup or video attached to the writeup. JR
  14. Okay,so an answer to my own question. It does cause a problem during playback. It doesn't show the duplicates only the first one that shows in the grid shows up. But I worked it out, i had to select "Same Channel as" and then select the one that considers the 'master' prop. It may not be the first in the list alphabetically.
  15. the back story. Just light strands, not pixels and converted from S4 to S5. I had done work in Visualizer to create an image of my yard. One thing i did was to create multiple 'props' for lights that were on the same circuit. For example, i have 4 windows that were on the same circuit, so i created 4 objects, and assigned them all to the same unit and channel. After conversion to S5, the image looks good and it seems to animate correctly. But in the channel grid it shows on of them, the first which is fine. But in the preview warnings tab, for every prop i created this way, i get this error, "has an invalid master prop". I don't see any way to assign a master prop to get rid of the error.
  16. Last week
  17. The forum worked just as planned... the support from the forum made me comfortable I was doing the right thing and your explanation also explains why restarting everything got it working. I managed to get everything else working as expected so far, being new to S5, still learning the tricks there i suspectI am one of few in a 100 mile radius that had a Christmas tree up in their office on Easter (I made a stand so i could test it indoors).
  18. Phil, Thanks for your thoughtful feedback - it is much appreciated. We design the dialogs and menus so that they are displayed correctly on a standard laptop screen (1366x768 pixels). If you right-click on the sequence grid in the S4 Sequence Editor, the menu overflows the screen on such a laptop. That is why the timing commands were moved down a level in S5. We will look at ways to perhaps make that configurable in a future version. Matt
  19. I am using the box that came with the Pixie16 below. Also using the 500 watt power supply that came with it. Remounted it with a 350 watt power supply that is powering the Pixie 8. It is vented in the back and thinking of putting a fan in the front door. This will be for a Fireworks display so temps could be in mid to upper 90's. It will only need to run for a few hours, one time during the show. Also had room to mount a Gen3 mini Director at the bottom of the box. Plan is to have everything self-contained for the show with a timer to start the mini Director. Have the dip switch set on the Pixie 16 to start at 1 and the Pixie 8 to start at 17. Have not been able to test this yet. Finishing up on wiring
  20. As Mike said: Contact the Mfg. My 50 ct pixel strings are 3A (white). Rule of thumb: Size your PSU at 125% of expected load. You never want to be up against the wall, odd things happen and the life of the PSU can suffer.
  21. That's a great question that I'm just now researching tfritz28. Hope to find an answer here, but if no one responds, I'll ask the LOR Help Desk. They are good at responding to all the questions I've posed so far. This should be any different. What did you find out?
  22. It's going to be different for each mfgs string -- it's not a constant. A mfg could have used super high power LEDs on a string or they could have used very low power LEDs. For the correct number, you need to contact the mfg. A rule of thumb (that you should not rely on when sourcing power supplies, controllers, wires, etc) is slightly less than 4A for 100 pixels at 12V, slightly less than 4A for 50 pixels at 5V.
  23. Here are few ideas: 1) Check your display driver. If you are running Intel-based graphics, then you can try the Intel Driver and Support Assistant, which can sometimes locate newer drivers than are included with Windows. https://www.intel.com/content/www/us/en/support/detect.html This is the most likely cause. 2) If #1 doesn't help, then create a help desk ticket (http://helpdesk.lightorama.com/) and attach 2 files: a) the Sequencer's trace/log file: "\Documents\LORSequencer-trace.txt" b) the Preview file - there is a small possibility that something in your Preview file is causing a problem at startup: "\Documents\Light-O-Rama\CommonData\LORPreviews.xml" Matt
  1. Load more activity
  • Create New...