Jump to content


  • Posts

  • Joined

  • Last visited

  • Days Won


lzimmerman last won the day on October 8 2020

lzimmerman had the most liked content!

About lzimmerman

  • Birthday June 29

Profile Information

  • Location
    San Diego
  • Occupation
    Computer Systems Engineer

More About Me

  • Interests
    Hiking, cruising, Disney, technology
  • Favorite Decorating Holiday?

LOR Software

  • LOR Software Version
  • License Level

Recent Profile Visitors

83 profile views

lzimmerman's Achievements

New Forum User

New Forum User (1/3)



  1. Thanks Aubrey, good to know that I was on the right track
  2. So, for anyone else following, it turns out there was a hardware solution to the problem. The Pixie 2 comes with a jumper installed (on the JP5 block) that overrides any settings you make in the Hardware Utility. With that removed I can configure the Ports on the Pixie to have 108 pixels and the extra 8 pixels light up just fine. Thanks to TheDucks who replied to my post in the hardware forum and sent me down the right track to solve this.
  3. Problem solved thanks to TheDucks! It was actually a jumper (on JP5) that had to be removed to allow the Hardware Utility settings to override the factory settings. It's amazing the things that we learn from year to year and then forget when we actually need it.
  4. Trying to verify that there is a hardware limit on the Pixie2 that keeps it from driving more than 100 pixels per port. The controller of interest is running v1.04 of the firmware and I have tried in the hardware utility to set it the 108 pixels that I need for a prop. I added a little 8 pixel string onto the two 50 pixel strings that were already on that port and the 8 pixels will not light. I run my pixels at the 50% pixel light curve, so pretty confident I am not going to run out of power for 108 (especially with only 33 pixels on Port 2). However, may be beat if there is a hard limit. Lee Z.
  5. I am creating an animated pixel "North Pole" prop to go next to our Santa's Workshop for this year - Boscoyo ChromaPole with a Boscoyo Spinner topper. Unfortunately, when I decided how tall to make the ChromaPole, I ended up needing 108 pixels (6 columns x18 pixels). I tried just adding 8 more pixels to the Pixie2 port, but it seems to be hard wired to only support at most 100 pixels no matter what I tell it in the Hardware Utility configurator and in my preview. The good news is that the spinner is only 33 pixels, so there are plenty of extra pixels in a 50 pixel string on Port 2 of the Pixie. What I can't figure out is how to set up Preview so that it knows that the first 8 pixels on that string are part of the ChromaPole and the next 33 are the spinner? My best guess is to create a little 1x8 custom prop that finishes out the last column of my matrix and then group that with the rest of the matrix that is the pole, but I think that is going to make for some weird pixel effects across the matrix. I would just rebuild the prop with shorter rows so it uses less than 100 pixels, but it took me hours to push the pixels into the strips and I really don't want to pull them all out and start over again. Any ideas? Lee
  6. This turned out to be slightly harder than it should have. Whoever at LoR set the controller for the lights it was supposed to be integrated with not only did not get that right, but they left a jumper on JP5 which told the controller to ignore any new settings sent by the hardware utility. Once I found that and removed it your suggestions worked great. Oh, the second Pixie2/CCR combo I ordered during the Summer Sale worked perfectly out of the box. Now the problem is another Pixie2 that I ordered with (4) 50 pixel strings of square pixels. I got the Unit ID and the number of pixels per port set correctly using the Hardware Utility. However, multiple attempts to set the correct color order have not stuck, even though the hardware utility says it successfully sent the configuration change. I did notice that this controller is running v1.04 of the firmware and I think all the others are at 1.03. Any ideas?
  7. Thanks for the rapid and helpful responses. Seems like this would have come up before, but I did not see it addressed in the last couple years of posts. I do now see the paragraph on color order in the manual, but it is interesting that the couple page instruction sheet on connecting the pixels to the controller did not mention the need to set color order. Live and learn.
  8. I bought pixels and controllers several months ago and just got around to testing them as I start to build new stuff for this year’s show. This will be the first year running pixels in the show, though I played around with them a bit last season. When I run the hardware utility on my new Pixie 2 controllers with 2 CCRII ribbons (purchased as a set), the colors are not right - I tell it to do red and the lights go blue or I ask for blue and I get green. To do some troubleshooting I got out a string of bullets pixels and connected them to one of the controller plugs and they behave as expected. I then got a second Pixie 2 out and connected it to the test network (just the two Pixies). The bullets connected to either controller behave as expected and the ribbons connected to either controller display the wrong colors. It seems like the RGB channels are not in the standard order on my ribbons, but that seems odd as I have never seen anyone mention that as a configuration item you need to set. I suppose I could go into the sequence editor and change the RGB channel mapping for every node on these strings, but that seems like a lot of work for something that should work “out of the box”. Am I missing something?
  • Create New...