The LightSort system performs an auto ID sequence during startup that reports the number of controllers (hubs) and lights connected. During start up, it is possible to get unusual results for either the reported number of hubs or lights.

Unexpected Hub Count

Currently supported configurations should only report one hub. If more than one hub is reported, one of the following is probably true:

  • There are multiple powered primary racks connected in a system. 
  •  A previous rack is connected to the port on the controller reserved for Ethernet cables, as shown in the diagram below. 

While the simplest fix for this problem is to rearrange the racks so there are no racks with controllers connected to each other, there is a proper method of including a primary rack as an auxiliary rack if necessary. 

Disconnect the controller from the Rack ID Board on the rack that will serve as an auxiliary rack.

Connect the acting primary rack directly to the Rack ID Board.

No power is needed for the rack whose controller is not being utilized.  

Unexpected Light Count

In addition to the Hub count, the controller displays the number of light boards that are connected. The number of lights reported should be a multiple of 15, as each rack contains 15 light boards. There are two likely causes for an unexpected light count, a cable connection problem or a bad circuit (either a light, grounding, or Rack ID) board/boards. Cable connection problems commonly involve the exposed cable that connects racks, which will usually result in a large discrepancy in light count, and multiple dark lights in a row. Alternatively, a bad light board will most likely appear as a small discrepancy in light count and isolated lights that don't function. Furthermore, a shorted light board cause the controller display to flash steadily.

Scanning the "Test Lights" command barcode can locate the problem.  Only light boards detected during the auto ID sequence will illuminate during a light test. 

Note: An individual light board that doesn't light is not necessarily the "bad" board!

To troubleshoot a connection issue, first check that the cable connection between the last functioning and first non-functioning light board is secure. If the connection is secure and the problem persists, try replacing the Cat 5 cable in that location. If securing a connection or replacing a cable does not resolve a connection issue, please call Customer Support.

To troubleshoot a light board issue, it is important to understand how the light boards communicate to the controller and to each other. During the auto ID sequence, each light board 'talks' to the controller and to the previous board in the sequence. This is done to establish the order and identity of the lights connected to the system. 

When a light board fails, circuitry related to the auto ID communication process may be affected. Only boards that are successfully identified during the auto ID process will light during a light test. Because of this behavior, the problem may lie with a light board that does not light during a light test or the previous light board. Use the following process to determine which board needs to be replaced: