Knowledge Base:  
Knowledge Base > How-To Articles, RGB Training, FAQs, Presentations --> Knowledge Base > How-To Articles, RGB Training, FAQs, Presentations
Procedure for repair of a mid-span failure in pixels
Last Updated: 07/10/2017
This article details how to repair pixels (nodes, modules, strip, bulbs) when that length of lights has a mid-span failure. This process does not apply to pixels with one or two failures of a single color (red, green, blue). Here would be examples of such a failure:

  • Controller Output > 30 WORKING pixels > 20 COMPLETELY NON-WORKING pixels
  • Controller Output > 30 WORKING pixels > 1 COMPLETELY NON-WORKING pixel > 19 WORKING pixels

Before you start - make absolutely sure this is an actual pixel failure. Here are common reasons for assuming a pixel string is bad:
  • Testing pixels with a sequence application (an external source of pixel control) - we recommend ONLY using the built-in test mode on your controller to test pixels. This will ensure that any possible mis-configuration in the sequencing software is no affecting the testing.
  • Pixel string is hooked up backwards. All pixels have a direction and typically this is an arrow and that arrow should point AWAY from the controller's output
At first appearance it might seem that we should only remove any "bad"pixels after the last working pixel but in many cases that last "working" pixel is actually bad and not sending data on to other pixels. To reduce the amount of time we spend repairing the pixels, we will be removing the last working pixel and the first non-working pixel. Here is an example of how we should fix the string:

  • Controller Output > 30 WORKING pixels > 20 NON-WORKING pixels
    • Cut between pixels 29 and 30 and again and cut between pixels 31 and 32
    • Re-connect / solder the original pixel count of 29 to 32 - make sure to maintain the same direction (don't reverse the string direction)
    • Re-test output
  • Controller Output > 30 WORKING pixels > 1 NON-WORKING pixel > 19 WORKING pixels
    • Cut between pixels 29 and 30 and again and cut between pixels 31 and 32
    • Re-connect / solder the original pixel count of 29 to 32 - make sure to maintain the same direction (don't reverse the string direction)
    • Re-test output
  • Here is a diagram that shows the above process:


Q: I needed 50 pixels in my string but now I have 48 - what do I do?
A: If you need the exact number of pixels that were originally in the string, that can be accomplished in two ways:
  • If there is not a plug at the end of the string or you are not using the plug at the end of the string, solder on any additional pixels to the end of the string (two in the example above)
  • If there is a plug at the end of the string and the removed pixels (two in the example above) need to be replaced, that can be done anywhere on the string - just cut between two pixels and add in the pixes.
Q: If I cut up the string and remove the pixels, will this affect the address of the pixels?
A: No, pixels do not have any specific address, they get their address based on the location in the string. See this article for more information on pixel addressing.

Q: Can I do this same process for pixel strip?
A: Yes, see the video below for how to splice pixel strip.
Using solder and 1/8" shrink tubing:


Using solder shrink tubes:


Pixel strip repair / splice using 1/2" shrink wrap and RTV silicone:
Tags: repair, pixel


How helpful was this article in answering your question?

Comments / Feedback / Corrections (please, no questions):
 

Related Articles
 > Display Design (Presentation)
 > Death of the Grid (Object Oriented Sequencing or OOS)
 > Do HolidayCoro "Coro" type products come with lights?
 > How do you store coro items in the off-season?
 > Why are there not exact numbers of holes for each channel / section?
 > How we ship 4'x8' sheets of coro
 > Understanding DMX (presentation)
 > The Amazing World of Coro (presentation)
 > IP (Ingress Protection) Ratings
 > Customer Supplied Tools and Supplies
 > Warranty Periods and Policies for HolidayCoro Products
 > DMX + Power over CAT5 System Details
 > Differences between Chip Protocols
 > Why HolidayCoro needs detailed information about your project
 > HolidayCoro PRE-SALE Dates, Status and Policies
 > I'm new to RGB Lighting - Where can I go for help?
 > Software Applications Supported by HolidayCoro Lighting Controllers
 > What Glue Gun Should I Use For My Coro Project?
 > Pixel MegaTree "CCR" Strip Style Tree Construction Recommendations (Under Development)
 > RGB Arch Assembly Suggestions
 > What is the complete cost / What is required for a mini-light animated character?
 > The Color Of My RGB Lights Don't Match the Color on the Monitor
 > What is a Null Pixel and do I need them?
 > Why we don't list lumen ratings
 > Restoring Shape to a Waterproof Cable Male Threads or Female Nut Deformed Mis-shapen
 > Sequencing Software Models for HolidayCoro Products
 > MegaTree Pole, Guy Wire and Stake Construction Suggestions
 > PolyCromatic Coro Custom Printing - Customer Provided Graphics Recommendations
 > Troubleshooting: xLights Confirmation Capture
 > Why did my controller come with outputs labeled starting at 33 to 48 instead of 1 to 16?
 > Residential Displays
 > Commercial Displays - Malls, Municipal Projects, Zoos, Drive Through Parks, Theme Parks and More