Jump to content

LightORamaJohn

Administrators
  • Content Count

    252
  • Joined

Community Reputation

0 Neutral

About LightORamaJohn

  • Rank
    Member

Profile Information

  • Location
    Morristown, NJ
  • Occupation
    b

More About Me

  • Favorite Decorating Holiday?
    c

LOR Software

  • LOR Software Version
    5.1.4
  • License Level
    Pro

Recent Profile Visitors

568 profile views
  1. Exactly, you can configure it in a couple minutes: The Pixie is based on a 16-bit processor which only has enough RAM to support 3,200 pixels. So the max is 200/port. The idea was to provide users who wanted only 10 to 20 thousand pixels with an inexpensive, easy to configure and cable up solution. We sell a lot of these, so we think we've guessed correctly. As an engineer, it's easy for me to understand and use null pixels and power injection, but as an intrinsically lazy person, it's just too much of a nuisance to setup, configure and then repair displays built that way. I thin
  2. The device has been ready for a while. We've had them in stock for at least 6 months. So, we've been using them for a while and have had no problems -- of course, people using them in real displays will likely expose something(s). We're confident in the hardware. However, we wanted distribution of new firmware to be easy for customers... There were two problems, one was releasing it right before Christmas, which would have incurred a support load we didn't want, and the other was the bootloader. Dan wrote the bootloader in all our devices in LOR year 0. So, as devices became more complic
  3. The PixieLink adapter is not a pixel controller. It maps 192 E1.31 universes to its six RS485 ports. If we were to go the route of using an additional universe just to target the remaining 30 pixels/string, it would have to handle 384 universes. This probably isn't possible, but even if it is, it would mean that the LAN bandwidth consumed by a fully loaded PixieLink device would jump from 32+Mbps to 65Mbps because I have only seen full DMX payloads regardless of the configured pixels/string. It seemed to us to be the wrong way to go, especially since almost no one does power injection to get a
  4. The PixieLink Adapter does process standard E1.31. Everybody's software already has the ability to transmit E1.31, it would be silly to create some new protocol. The idea was to make an inexpensive device that would allow Pixies, and other LOR G3 controllers, to be easily moved to a standard E1.31 environment. The Pixie firmware, that supports the higher speeds used by the PixieLink Adapter, also supports 200 pixels/port. This is not possible with standard E1.31 since it really is just an IP transport for DMX universes. We will most likely allow (at some point in the future) users to configure
  5. The PixieLink adapter converts E1.31 for Pixies (and other LOR controllers) this. See:
  6. 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 n
  7. 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.
  8. Here's the brochure. We are still playing with the web configuration interface, so I haven't finished the user manual yet. PixieLink.pdf
  9. 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, Pixe
  10. TheDucks explains how to quickly change the unit ID/network above. A 1M enhanced network should easily handle 16 50 pixel ribbons.
  11. 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
  12. 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 RG
  13. 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 cons
  14. 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.
  15. 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
×
×
  • Create New...