Jump to content
Light-O-Rama Forums

LightORamaJohn

Administrators
  • Content count

    233
  • Joined

  • Last visited

Community Reputation

0 Neutral

About LightORamaJohn

  • Rank
    Member

Profile Information

  • Gender
    Male
  • Location
    Morristown, NJ
  • Occupation
    b

More About Me

  • How I learned about Light-O-Rama -
    a
  • Favorite Decorating Holiday?
    c

Recent Profile Visitors

197 profile views
  1. Unit ID question

    If your Pixie has a DIP switch, setting all positions to 'off' means you want the Hardware Utility to set the Unit ID. If any switches are on, then the DIP switch overrides the Hardware Utility setting when the controller next powers up. There is only one manual for all Pixies. The new manual was put up a couple days ago.
  2. pixie 16 confused with 62 pixels/string

    Maybe a different wording. If you set the number of pixels to anything other that 50 with the Hardware Utility, the only logical resolution that you can set in the Hardware Utility that does anything is 1. If you set the logical resolution in the Hardware Utility to anything other than "1" with pixels strings that are not 50 pixels, the logical resolution is ignored and you get the full resolution of whatever number of pixels you configured.
  3. pixie 16 confused with 62 pixels/string

    When the number of pixels is anything other than 50, the only logical resolution that works is "1", which makes the string will look like a dumb rgb ribbon. Any resolution other than "1" when the number of pixels is other than 50 means the controller will operate at full resolution.
  4. Pixie 16 setting help

    A enhanced network requires that the Comm Listener be running for LOR programs to access the network (except the Hardware Utility). There should be a "CL" icon near the "SE" and "PE" icons. Make sure you started LOR by running the LOR Control Panel from the start menu. There should be a red light bulb in the list of icons displayed when you click the "^" on the lower right.
  5. Pixie Firmware update?

    Just noticed this thread. I have a beta release available, but would like to release just the Pixie16 version. I've tried to mimic the CCR, but this is pretty much a rewrite so until people actually run it on their props we won't know if it's close enough to the original CCR/CCB/CCP. Are you interested in running this through on your equipment and then submitting tickets where it falls down? Tracking troubleshooting conversations through this forum is just too hard. Once we get the Pixie16 working, the others should have few, if any, problems. These are the changes in the interim: If the number of pixels/port is 50, then color effects, macros and resolution should work. The implementation is very different in this controller, so the timing could be slightly different. The number of pixels has been increased to 200/port on the Pixie16 and 400 on the other Pixies. The current LOR software supports 170 pixels/port. The support for more than 50 pixels/port requires an Enhanced Network -- the processing and memory resources required for a regular network are just too much. There is a single shimmer timer for all pixels when running on a regular LOR network. A standalone sequence can be downloaded. Standalone used to send commands to other controllers at 19.2Kbps, it does that at 115.2 now. The Test Button behavior is different. If the button is held while powering up the controller, it tests the EEPROM and resets the controller -- it will flash the status LED rapidly if everything is OK and you should release the button to allow the controller to boot, otherwise it will flash an error code to indicate what's wrong with the EEPROM. If the button is pressed momentarily while the controller is powered, it will run the test pattern until you press the button again or 5 minutes goes by. If you hold the test button for 5 seconds while the controller is up, it will reset and reboot the controller. You will know this is happening because the LED will flash rapidly and you can release the button. The interactive inputs are implemented.
  6. uf50d setup

    The UF50D uses exactly the same firmware as the CF50D, and that firmware has been upgraded to understand enhanced networks. If you load the latest firmware the UF50D should work. DIP switch 11 being ON tells the firmware that it's in a UV flood as opposed to RGB.
  7. Cosmic Color Flood Strobe Help

    The easiest way to play with this is the Hardware Utility. Make sure shows are disabled and the Sequence Editor is not running so the Hardware Utility can get the USB port. Start the Hardware Utility and click Refresh to find your controller(s). Note the unit ID of the 50w F -- it will show up as "nn - F50RGB" Note the nn unit ID. Depending upon your version of the Hardware Utility, click the Console or Light Console button. Make sure the correct unit ID is selected in the Console. Move the first three sliders to set the color you want to strobe. Then move slider 5 to 50% intensity -- the flood will flash about once/second. You can experiment moving 5 up and down to get the flash rate you want and note the Intensity level for your sequence. You can move slider 4 up to make the flashes longer. Again, note the Intensity if you want to change this in your sequence.
  8. Sale - Cosmic Color Floods

    Yes, these are black light floods. The flood head only accepts one 50w LED chip. The back of the head is a pretty large heat sink that isn't designed to dissipate 100w. The head would have to be almost twice as big to contain both RGB & UV LED chips. For comparison purposes, the individual flood heads on the older CCF were about 18w. Other than the UF50D being designed for outdoors, the big advantage of it is that LEDs are instant on/off so strobe effects are possible. The datasheets and user manual are ready, so I'll ask to have them put up on the doc page.
  9. Sale - Cosmic Color Floods

    The replacement flood is 50w and is being manufactured now. There are two versions, RGB & UV. The flood head contains the controller and there is a separate power supply; both outdoor rated. To the software they look and are driven exactly like a single head CCF. I will get data sheets and a user manual up this week.
  10. CCP - Interferring with Garage Door?

    CCB/CCP controller needs v1.18 firmware to correct this problem. See this thread: http://forums.lightorama.com/index.php?/topic/29328-ccbccp-preventing-garage-door-opener-transmitters-from-working/
  11. Multiple USB485B's with ELL's

    Make sure there is nothing wrong with the USB485B adapters: Even if they are not configured properly in the software, as long as they are plugged into the USB port, they should supply accessory power. If they are supplying accessory power, LED1 on the ELLs should be flashing about once/second. Some PCs have high and low power USB ports. If you find that the ELLs flash when the USB485B is plugged into one PC USB port but not another, that could be the problem. There is no limitation on the number of ELLs you can use other than the maximum of 16 (one on each USB485B on comm ports 1 through 16.) The Hardware Utility on recognizes the ELL when it first starts up. If you change the comm port, you probably have to stop and restart the HWU to get it to see the ELL on that port.
  12. LOR adapter with d-light

    You should not have a problem controlling the d-light controllers. Many years ago I did find that two-way communications with d-light controllers seemed to require a d-light adapter, so hardware utility type functions (set unit id, see all controllers) did not work with a LOR adapter.
  13. CMB24D in DMX 1990 mode E1.27 or other

    The jumpers on the CMB24D that select LOR Network or DMX E1.27-2 change the wiring of the RJ45 jacks. These jacks are always RS485 and should never be connected to a LAN. When these jumpers are in the LOR Network position, the RJ45 jacks are wired to be connected in a standard LOR Network and/or use LOR USB485 adapters. When these jumpers are in the DMX E1.27-2 position, the RJ45 jacks are wired in the way commonly used by DMX networks. The Entec Open DMX has an XLR5 connector. You would need to purchase a standard XLR5 to RJ45 converter. It would map the wires in the XLR5 to an RJ45 connector with E1.27-2 wiring. In this case, you would put the CMB24D jumpers in the DMX position. If you use a LOR USB adapter, leave the CMB24D jumpers in the LOR Network position even if you are running DMX through the adapter.
  14. No problems have been reported by multiple users, but I would recommend using it only if your remote garage door opener does not work. The attached firmware does two things. 1) It changes the data clock frequency. 2) It only updates the bulb strings when something changes. During the day when the display is inactive, there should be no interference. During a show, it depends upon how active the bulbs are. It only takes a fraction of a second of inactivity for the GDO to get through unimpeded. Even when the bulbs are continuously active, the change in data clock frequency allowed me to open the door, but the range was restricted. If you find any anomalies in the way the bulbs work it's probably because I missed a spot where I need to update the bulb strings. In this case, please explain exactly what effect/activity you had on the bulbs when they messed up. Old firmware version here: http://www1.lightora...B100D-V1_16.lhx CB100D-V1_18.ZIP
  15. No problems have been reported by multiple users, but I would recommend using it only if your remote garage door opener does not work. The attached firmware does two things. 1) It changes the data clock frequency. 2) It only updates the bulb strings when something changes. During the day when the display is inactive, there should be no interference. During a show, it depends upon how active the bulbs are. It only takes a fraction of a second of inactivity for the GDO to get through unimpeded. Even when the bulbs are continuously active, the change in data clock frequency allowed me to open the door, but the range was restricted. If you find any anomalies in the way the bulbs work it's probably because I missed a spot where I need to update the bulb strings. In this case, please explain exactly what effect/activity you had on the bulbs when they messed up. Old firmware version here: http://www1.lightorama.com/downloads/CCB100D-V1_16.lhx CB100D-V1_18.ZIP
×