Jump to content
Light-O-Rama Forums


  • Content Count

  • Joined

  • Last visited

Community Reputation

1 Neutral

About cam308

  • Rank

Profile Information

  • Gender
  • Occupation
    Web Design

More About Me

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

Recent Profile Visitors

280 profile views
  1. The PixCon16 is not a plug and play device. In fact, from my experience, it's one of the more advanced controllers I've had to set up. If your using this with an LOR network, you will need to assign the controller an ID, just like you did with the other controllers in ur setup. In order to do this with the PixCon16, you do not use the Hardware Utility. You have to interface directly with the unit using the Network Configuration Utility. You will need to connect the PixCon16 directly to ur local computer network by using the silver ethernet port on the device. From there you can set the LOR Unit ID. Once you have completed that, you will then be able to use the ethernet IN/OUT ports on the board to jump from one controller to the next. So I don't think your CAT5 wiring is the issue at this point. The reason ur not seeing any response from the PixCon16 is because you have not configured it yet. Take a look at the info below. This helped me get everything up and running. Just take ur time and pay attention to the steps in order: Bare Minimum PixCon16 Setup Checklist Be sure to follow each of these steps IN ORDER. Do not proceed to the following step until you are sure the current step is complete. Please note that you may be further along in your testing than where this check lists starts. Please do not skip any of the previous steps even if you think you have performed them correctly already. Start at #1. If you have already tried to configure the board, you should first FACTORY RESET the PixCon16. Instructions are provided in the manual. This checklist assumes that you have a 'stock' PixCon16 to start with. Critical checkpoints points are in bold, but you may experience a problem at any step. If you are having problems at a checkpoint, check ALL steps up to this one to ensure they are completed properly. The PixCon16 is a professional level board, and does require some in-depth knowledge about how E1.31 works, DMX and networking concepts. You may need to consult other sources if you run into issues or do not understand a concept. If you do have an issue and if you think everything is good to that point, and you would like to contact us for help STOP. Do not go further and do NOT change any configuration. If you would like to experiment and try to resolve the issue, please do! We encourage you to find the solution on your own. However if in the end you must contact us, reset the board and start again at step 1 and then stop at the failing step and contact us. We rely on the board being in a known state at every step of this checklist to help you. Please ensure that you have AT LEAST S4 V4.3.14 Or Higher to configure the board. Some older versions may not be able to properly detect the Pixcon16. Pixels have a front and a back (IN and OUT). Ensure you know which side data goes IN to. Pixels from LOR are plainly marked, or are correctly pre-wired. if your pixels have an arrow, that arrow points AWAY from the board. Pixels have a voltage. Ensure you have the proper power supply. LOR Pixels are typically 5v or 12v. If your pixel package from LOR included a power supply, you do not need to worry about this step. Pixels have current draw (amperage). Ensure you are not exceeding the amps per channel/power supply/etc. Pixels from LOR will draw 3A per 50 pixels at 5V (15 Watts), 3A per 100 pixels at 12V (36 Watts). If you pixel package from LOR included a power supply, you do not need to worry about this step. Wire power supply to PixCon16, if not already wired. Remember – never connect or disconnect anything from PixCon16 with power applied. Power up board. Follow instructions in "An Introduction to DMX and E1.31 for Pixel Control" document if needed (linked below). Open Network Preferences/Find Configure PixCon16/Click on PixCon16 in list, and open the PixCon16 configuration window. Only work with a SINGLE PixCon16 connected to your network at one time until properly configured -- IP address conflicts can occur if you attempt to configure 2 or more. Do not continue until you are able to reliably talk to the board and configure it. If you are having difficulty reliably talking to the board, read: http://www1.lightorama.com/PDF/IntroductionToDMXandE131.pdf Pay particular attention to page 8. Ensure board firmware is AT LEAST 1.4.8. WARNING! Do NOT downgrade if higher! Downgrading a PixCon16 will brick the board requiring special software to recover! All PixCon16s sold since late 2016 are at or above V1.4.8. Do not continue until firmware is updated to at least 1.4.8. Instructions are found in the manual. If you have the LOR Control Panel loaded, UNLOAD IT before attempting to update firmware. Updating the firmware while the Control Panel/Comm listener are running can cause the board to FAIL. Properly set up Pixel Type and Pixel Speed in configuration. Ignore all other parameters. LOR Pixels are WS2811. Most are high-speed. Properly wire 1 pixel string to a 4 wire connector. Follow pin-outs in the manual. Note -- Some pixels do not have/require the clock signal. Connect pixels to a single port, and power up. Pixels may briefly flash. Pixels that stay ON indicate incorrect pixel type or speed selected in #8. For LOR Pixels, ensure that you selected 'High Speed'. If High Speed does not work (it should in almost all cases), select slow speed. Run hardware test on the pixels as documented in manual by using the buttons on the PixCon16. If pixels do not work, problem is most likely #8. Go back there. Do not continue until the Hardware Test works properly. Wire the rest of your pixels to the 4 wire connectors. Connect them to the PixCon16. Run the hardware test (step 11) again. Ensure all pixels are working correctly. Pixels that are not working indicate a problem with the pixel itself, or an under-rated power supply. Do not continue until the Hardware Test works properly for ALL pixels. Again bring the PixCon16 configuration up. On the first tab of PixCon16 configuration, ensure you have the correct option specified for J3/J4. If you will use the board in ELOR mode, turn this option ON. For E1.31 ensure this option is OFF. If you have not done so yet, install the drivers for the USB adapter and ensure the USB adapter is working properly. On the Second tab set up each port of the PixCon16 properly. You can use simple mode or advanced mode. All options are documented in the help file for the software or in the manual for the PixCon16. Remember, for E1.31 universes must also be set up in Network Preferences (the software will offer to do it for you), for ELOR, 500K speed and Enhanced Light-O-Rama network (done in step 16). It is best to write down the settings. Ensure you have the LOR Control Panel loaded (which will load the LOR COMM Listener). The COMM Listener is ALWAYS required to control pixels. Properly configure your network preferences: E1.31: Ensure Universe matches universe on the board & Set IP address correctly (multicast or unicast/specify). It is easiest to use multicast. ELOR: Ensure the COM port is set to at least 500K and ELOR mode is turned ON. Properly connect networking: E1.31: Do not make any changes. Both LEDs should be SOLID ON. Do not continue until they are. NOTE: Your computer may need to be rebooted. If you reboot go back to step 15. ELOR: Disconnect Network cable, ensure jumpers on PixCon16 for J3/J4 are set to LOR. Connect HS USB adapter to computer, CAT5 from USB adapter to J4 of PixCon16. NOTE: You must have previously installed the drivers for the high speed USB adapter. Use another non-PixCon16 unit to test if you are unsure the USB adapter is working properly. Both LEDs should be SOLID ON. Do not continue until they are. NOTE: Your computer may need to be rebooted. If you reboot go back to step 15. Start Hardware Utility. If asked if the HWU should take control of a port say NO. Open the pixel console. Set Pixel Console params correctly and test pixels with sliders. Do not continue until you can successfully control pixels. Your board is now ready to use.
  2. Pretty sure I found the answer in another post from Mr. P. Appreciate the info. I quoted it below:
  3. Anyone know why a Pixie8 controller would keep resetting the Unit ID back to 01? I have it set as Unit ID 33 on AUXA Network with a few other Pixie8 and a PixCon16, all of which are assigned different Unit ID's, none of which are 33. So each device has it's own unique ID. I'm pretty sure the affected Pixie8 loses it's assigned ID when I power cycle the controller. I'm not 100% on that, as I'm waiting to see if it goes without me power cycling. But either way, none of the other Pixie8 on that outlet lose their ID when I power cycle, so I think something is going on here. Any suggestions?
  4. Got it. Thanks! Also, for those using S5, if you check more than one color under LIGHTS in PROP DEFINITION, you'll be able to keep all the channels nested within that same unit. Just use different circuit numbers for each channel and keep unit ID same for all.
  5. I’m only using 2 channels on this main director for strobes. So that the only things not playing right now. Main use for unit is for the SD Card and I’m getting intermittent flash of the strobes during playback. Unit has ID of 01, but don’t have it configured in Sequencer or Pixel Editor. So wanted to know proper way to set it up so I can program those 2 strobe channels. They’re multiple stings of C4 strobes.
  6. Got it! Used Hardware Utility to reverse specific strings according to house outline. Looks a lot better. Thanks for the tip. Still wondering what “starting position” refers to in Pixel Editor when configuring a CCB unit??
  7. "All Over The Place" - The chase is off. Some units start from left side of house, others from right, top and bottom. So best way to correct this would be to take it one string at a time and set the start position in Pixel Editor? How would I flip the second string around?
  8. Guys, What is the correct way to add a Gen3 Director with 16 channels into S5? How would I configure that a a prop? I'm using it with regular incandescent bulbs.
  9. Guys, I'm using 7 different CCB controllers, with 50 bulbs on each of the 2 strings per controller, to outline my house. All CCB controllers have been assigned unique ID numbers. I'm trying to get the effect I see in the visualizer in pixel editor to match the actual display on the house. For example, when I do a while from left to right, it appears to play correct in PE. But when played on Gen3 Director, the wipe is all over the place. It's like the CCB controllers are not configured properly. What is the correct way to configure these in PE so that the wipe can flow from left to right? I have all the controller grouped as one line when adding the effect so the software knows what to include in the wipe.
  10. Anyone know how to configure CCB units so that the applied effects display in correct order. Meaning if I use a wipe from left to right of house, and there are 7 CCB units outlining the house, I would want the effect to display properly. Currently, it’s all over the place. Each CCB currently has its own Unit ID. There are 2 string on each with 50 bulbs. Does it have something to do with the starting position option listed in prop configuration?
  11. How would I configure a Gen3 Showtime unit as a prop in Sequencer using S5 beta? It has 16 channels and I'm using regular incandescent bulbs. What should the settings look like?
  12. Guys, I'm trying to get the physical display of the outline of my house to mimic what I'm seeing in Sequencer effect preview. I'm using 8 controllers of CCB bulbs. The all have unique unit id numbers. All mapped out to match placement in preview window. The effect I'm trying to display would be "blended bars" using the "right" option for example. With 2 colors selected, the effect preview seamlessly wipes across the house when previewing on computer. But when I run the show from Gen3 Showtime Director, it's all over the place. The wipe is not wiping across the house. The strands of CCB are not in sync. What am I missing when configuring the design preview for each controller? Currently I have each set of CCB set as: - lines-connected - 2 segments (depends on how many times each set turns a corner) - 50 pixels per string - starting location: left What exactly is starting location? Should it be different for each controller depending on placement? Or just which side of the controller the effect would start on?
  13. Clarification... The reason I was getting: Autoconfiguration IPv4 Address. . : Mask . . . . . . . . . . . : Gateway . . . . . . . . . : in Windows 10 when running "ipconfig" was because the IP address was already in use on the MAC side of the system. So DHCP or VM must have automatically assigned Windows 10 with IP of That was still causing a conflict once I clicked on the PixCon16 in the LOR Network Configuration Window. So in addition, I had to set a manual IP address for the adapter in Windows 10 environment of for everything to play nice with each other. So in conclusion, to avoid some headaches either use a standalone PC machine to communicate with PixCon16 or be sure to set the IP address of both MAC and WIN environment to be on same subnet, and use Bridged Setting on VMware.
  14. Guys, Thanks for all the help and suggestions. I was finally able to figure this out!!!! I am using VMware Fusion running on MAC hardware. This software allows me to use MAC as a "PC" running Windows 10. So inside this environment I had to go into Virtual Machine Settings --> Network Adapter --> Bridged (Ethernet) to force machine to use static IP set for that ethernet adapter back in MAC environment. The PixCon16 came right up when searching in the Network Configuration Window. For those interested, the most confusing part is when inside the Window 10 environment, if I run "ipconfig" here's what I get: Autoconfiguration IPv4 Address. . : Subnet Mask . . . . . . . . . . . : Default Gateway . . . . . . . . . : But for some reason this does not matter because the Virtual Machine Settings --> Network Adapter --> Bridged (Ethernet) setting is overriding this somehow telling the system to use the static IP set for the adapter back in MAC environment. So setting the IP manually in Windows 10 environment was not controlling the adapter. Had to be set in MAC and use Bridged Setting. Hope I gave clear explanation on fix. Thanks again!
  15. Should I have to change any of the jumper settings? Everything is back to the default way it was sent from LOR.
  • Create New...