Jump to content
Light-O-Rama Forums

LightORamaJohn

Administrators
  • Content Count

    248
  • Joined

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

LOR Software

  • LOR Software Version
    5.1.4
  • License Level
    Pro

Recent Profile Visitors

450 profile views
  1. The PixieLink adapter converts E1.31 for Pixies (and other LOR controllers) this. See:
  2. The PixieLink adapter allows you to operate your Pixie and most other LOR controllers over Ethernet in a standard E1.31 environment. The attached manual is mostly complete; hopefully the verbiage won't have to be to changed much; depends upon feedback received here. I’m waiting on a couple items. All the pictures have to be redone, but the changes will be cosmetic. We really didn’t want to offer this before last Christmas. The device is easy to use, but fairly complex internally. More time in QA seemed prudent. It’s already difficult to help customers without the introduction of a new device so close to Christmas. Since we have these in stock; we’ll probably offer them as part of the Mad Grab sale next month. This will give people a lot of time to experiment with them, and for us to correct any problems and make any improvements necessary before Christmas. Thanks in advance for feedback. This is the first time we're putting a manual out in draft form. I'm hoping this results in a better product. PixieLink_Man_Web.pdf
  3. You cannot add a pixel IC profile. These are coded into the Pixie. I have implemented the GS8208 (which is also the WS2813) in the next release of the Pixie firmware. If you submit a trouble ticket and send it to me, I can send you interim firmware and you can see if it works. I don't have a GS8208 string to test, but the waveform looks correct on the scope. It looks like you want firmware for a Pixie4, put that in the ticket.
  4. Here's the brochure. We are still playing with the web configuration interface, so I haven't finished the user manual yet. PixieLink.pdf
  5. Singing Trees are pixel based with two 100-pixel strings. You could program them that way, but that is very inconvenient because programming each tree would be different, and it would be time consuming to manipulate 200 pixels. The Pixie controllers have a 'tree' option in the configuration. The trees have names; Zuzu, Elden, Felix, & Ralphie. You configure the 'tree' option. Then the first 8 pixels (24 channels) of the first unit ID controls the face. Pixel 1 is the outline of the tree, Pixel 2 is the topper, Pixel 3 is eyes closed, Pixel 4 is eyes open, Pixel 5 is mouth closed, Pixel 6 is mouth half open, Pixel 7 is mouth full open, & Pixel 8 is mouth O. You can still use the full range of colors/intensities, the programming is consistent across faces, and much simpler than manipulating the individual pixels. You can only have 1 singing tree on a CCCII (Pixie2), ..., and 8 singing trees on a Pixie16.
  6. TheDucks explains how to quickly change the unit ID/network above. A 1M enhanced network should easily handle 16 50 pixel ribbons.
  7. No, only the original CCR is based on the primitive RGB IC. The CCR II has current generation 256 intensity RGB ICs, so it has twice the number of intensities that the original CCR controller simulated. The CCR II ribbon (or pixels) will be smoother than the older controller because if this. The CCR II controller is a Pixie and can control the old CCR ribbons, but it does not simulate intensities beyond what the RGB IC does natively. One thing I have noticed is that people will sometimes not use an enhanced network when driving pixels/ribbons. The older, non-enhanced, network protocol is incredibly command intensive and this can make displays look choppy. This occurs because people are dramatically upping the number of pixels on a network and the older network protocol performs poorly in that situation.
  8. The RGB IC in a CCR ribbon is a very old device that only supports 32 intensities. The CCR controller creates 128 intensities by rapidly updating the pixels and mixing an intensity with some off time. During every four ribbon updates, the controller will use the lower of two adjacent hardware supported intensities once, twice, or three times before switching to the next higher hardware intensity. This happens rapidly enough that your eye integrates it. So, if the CCR turns the pixel on for 3 of the 4 updates, you get an intensity that is 75% of the way to the next intensity supported by the RGB IC. The Pixie does not do this. If your fades are slow enough, your effects will appear choppy.
  9. Capabilities of the Pixie hardware with 1.04 firmware: LOR regular or enhanced networks at speeds from 19.2Kbps to 1Mbps. 170 pixels/port maximum. LOR regular network support is primarily for compatibility with old CCR/CCB sequences. Compatibility (resolution/macros/color effects) mode is only supported for 50 pixel/port configurations when running on a LOR regular network. You can run a LOR regular network with any number of pixels/port up to 170, but the complexity of LOR regular network commands may cause a lack of smoothness with more than 50 pixels/port. S4 PC Software considerations: The Sequencer and SuperStar addon can be configured to generate commands in either network mode. The Pixel Editor will only generate commands for enhanced mode networks. This may be the cause of confusion, if you use the Pixel Editor and set the network type to LOR regular, it will not work. Enhanced network mode will result in the smoothest transitions because it is designed for RGB pixel displays, you should always configure for Enhanced mode if possible. S5 PC Software should always use Enhanced networks.
  10. The support ticket was created at 11PM Friday night. It would have been fixed on Monday morning when people came in, but I forced it now.
  11. Pixie firmware versions: 1.01 Initial release version, bootloader does not work. (must be returned to factory to update bootloader) Macros, color effects, and standalone are not implemented. Only full resolution and resolution 1 implemented. Hold down test button to run test pattern on pixels. Supported: WS2811, WS2801, SM16716, LPD6803, TMI1803, TMI1804, TMI1809. Max pixels/string: 100. 1.02 Initial release version (same as 1.01), working bootloader. 1.03 Macros, color effects, and resolution implemented for 50 pixel ribbons/strings. (original CCR compatibility mode) Single shimmer timer for all pixels (LOR effect). Implement DIP switches for 2nd generation Pixies. Implement standalone - bug can cause standalone sequence to hang. Test button: Hold during power up to reset controller. Hold 5 secs while powered up to reset controller. Press momentarily to start pixel test pattern. Press momentarily again to stop, or wait 5 minutes. Implement DMX input for Pixie2 & Pixie4 - has two bugs. Add RGB ICs: 943, UCS1903 (Use WS2811 for UCS1903, timings adjusted for both) 1.04 4.3.34 Hardware Utility or later required to configure props & per port color order. If you have an earlier version of LOR software that supported Pixie configuration but does not recogninize your pixie with 1.04 firmware then you should upgrade to 4.3.34. If your license does not support upgrading to 4.3.34 and you are not ready for a license renewal then you can use the LOR_DeviceFile.txt (below) which should allow you to configure your pixie with 1.04 firmware. (Replace file normally located in C:\Program Files(x86)\Light-O-Rama\) Support Pixie4DMX (iDMX1000 replacement). Fix DMX input to Pixie2 & Pixie4. Fix boundary problem in Enhanced Network mode that could lose last pixel's data. Fix standalone hang. Standalone transmit rate changed to 500K. Implement Props (singing faces). Implement regular LOR network DMX intensity command. Implement port selectable color order. Max pixels/string: 170. 1.05 Max pixels/string: 200 Props (singing trees) on Pixie16 increased from 4 to 8. If number of pixels/string on Pixie16 set to more than 100, then LOR effects are disabled for all channels, before this version it would always process LOR effects on the first 50 pixels when in LOR network mode. Support for PixieLink protocol Allow Pixie2 in DMX to have 100 pixels on second string. DMX intensities 1-150 = first string 50 pixels. DMX intensities 151-450 = second string 100 pixels. RGB IC GS8208 (also WS2813) RGB IC APA102 (also SK9822) Fatal error 41 halt fixed */ LOR_DeviceFile.txt
  12. Here's the one I used. It's possible the latest version of LOR is organized differently; I don't follow the software that closely. LOR_DeviceFile.txt
  13. Looks like a bug in that Hardware Utility. Attached is an old one. Right click the light bulb and select unload Light-O-Rama just to be safe. Then drop this on the desktop and see if you can fix the end to end problem. LORHardware.exe
  14. For 5v pixels, we generally use 20ma/color, so for one row: (0.20amps)(3 colors)(48 pixels) = 2.88amps/row. 8 rows, one side of a Pixie16, would be 23amps; which is well within limits. 20 rows is almost 58amps. It might be the case that there is a peculiar power dip because all the LEDs come on full white and this is preventing the microprocessor from properly booting. The Pixie16 is powered from the port 1-8 power supply. Try pulling the row pixel string plugs for half of the strings powered by the power supply connected to ports 1-8. If the Pixie behaves correctly, you will probably have to dedicate each of your 30 amp power supplies to one side of the Pixie16 and get a smaller supply for the Pixie4.
  15. It doesn't matter if you configure more pixels than there are in a string/ribbon. Data beyond the last physical pixel is ignored. The only effect you will see is when using the test button to test the pixel strings/ribbons. There will be a pause before the controller steps to the next color because the controller is sending data to non-existent pixels at the end of your strings/ribbons.
×
×
  • Create New...