CPC Package - 32" Star Topper for Pixel Tree

SKU: CPC-StarTopper32

Coro-Pixels-Controller (CPC) Package for a 32" Star Tree Topper (50 ct). An additional Pixie2 controller is required in order to add this star to your network if the pixel strands of your tree end at the BASE (folded strands). Use this package in your own sequences or with our RGBPlus Sequence Layout.

About the Price

This price will update as you choose options below.


Shipping calculated at checkout

Default Title
Current processing/packing time for an order containing this item is 1-3 business days. The item will ship using your chosen shipping method after it is processed.

What can your display look like with our CPC Packages? Take a look!

Our "CPC" packages include the "Coro, Pixels, and Controller" you need to easily add smart pixel props into to your display. These packages can be connected to an existing network of Gen3 Light-O-Rama Controllers, or used on a separate network within the same show. A Cat5 cable is required to connect this controller to existing controllers in a multi-controller network, or a computer/showtime director if it is the only Unit in the show.

S5.6.0 or higher is recommended for easiest use; a Pro license level is required to use Pixel Motion Effects. 

Our RGBPlus sequences contain effects for this star; our traditional and deluxe sequences do not. If you purchased any SD card before October 1, 2022, your card does NOT have effects for this star. You must have an RGBPlus layout SD card or individually downloaded sequence for this star to have effects (or you can create your own sequence.)

The Assembled Pixie2 controller (or "CCR II") includes the controller board and power supply wired and mounted in a weather-proof, ventilated and UL listed enclosure case. The power supply also is UL listed. This is a 12 Volt controller system compatible with 12V RGB smart pixel strands and devices. Dumb RGB devices or standard LED / Incandescent lights cannot be plugged into the ports of this controller. 

Included for use with a 16x50 Pixel Tree Kit (Pixel Tree strands end at the TOP):

  • Coro Star 32" (50 Node)
  • 50 Ct Black Pixels (4" spacing)

Additions to above for use with a 32x50 Pixel Tree Kit (Pixel Tree strands end at the BOTTOM):

  • Pixie2 Assembled Controller - Black
  • Pixel Extension - Black (10ft, 15ft, 25ft)


  • Cat5 Cable (10ft, 25ft, 50ft, or 100ft)

Not Included:

  • Mounting Materials to attach star topper to the top of the pixel tree 

Kit Assembly

Pixels are not pre-pushed. Assembly is to be completed by the customer. 

The star should be oriented so that the two vertical attachment slats are straight up and down. When viewing the star from the back, the "star" for "start" on the pixel path should be in the "valley" at the bottom of the slats. From the back view, the pixel path will run counterclockwise. 

After installing your pixels, install the two larger pieces of the coro clamp in from the front side of the star. The fit is tight so it will stay in place. Next, insert the two filler plates on the back side of the star above the bottom pixels and use 4 zipties (not included) to hold all four pieces of the coro clamp together. This will lock in the coro clamp to the star.

If using the star with a 16x50 Pixel Tree Kit (strands end at the TOP), connect the pixel strand of the star to Strand #16 of your pixel tree. The Unit ID in the preview editor should be 7F (the ID of the last port on the Pixie16 for the tree), and the starting circuit should be 151. 

WARNING: DO NOT use more than a 10 foot pixel extension if you are connecting the star to the 16th strand of pixels on the Pixel Tree.

If you are using the star with a 32x50 Pixel Tree Kit (strands end at the BOTTOM), set your Pixie2 controller to a base Unit ID of 80 (the ports on the controller will therefore be 80 and 81). Connect the star to the first port of the Pixie2 by using an extension to reach from your Pixie2 controller on the ground to the star at the top of your tree.

Our CPC packages can be used in a display with custom sequencing as long as the controller's Unit IDs do not conflict with any other Unit ID assignments on the network, and network limits have not been exceeded.