Some or all of my connected LEDs seem to be stuck in the "ON" state and cannot be turned "OFF." What is causing this?
Troubleshooting
Please step through the below Troubleshooting Wizard to quickly identify the issue and find possible solutions. Start with Troubleshooting Line #1 and follow the logic until your problem has been resolved or identified.
| Troubleshooting Line # | Interview Question | Decision Tree | Link A | Link B |
|---|---|---|---|---|
| TL #1 | Are one or more (but not all) LED lights (loads) "Frozen ON" or all "Frozen ON?" | If one or some (but not all) loads are frozen ON proceed to Link A. If all frozen, proceed to Link B | Some Loads Frozen-but not all. Proceed to TL#2 for next step | All Loads Frozen. Proceed to TL#3 for next step |
| TL #2 | Are the loads that are frozen physically connected on communication chain downstream to all units that are operational? | If yes, proceed to Link A. If not, proceed to Link B | Downstream Units are Frozen. Proceed to Topic 100 | Units that are frozen are randomly spread across the CS-Bus, proceed to Topic 101 |
| TL #3 | Is the e-Node Gateway still connected ("discoverable") on the LAN network? Using a PC computer, open File Explorer and go to Network, Other devices and see if the e-Node appears (which means it is on-line. | If connected to the network, proceed to Link A. If not connected, proceed to Link B. | Proceed to Topic 102 | Proceed to Topic 103 |
| TL #4 | Was this system working prior to this event and just malfunctioned or has the issue been present since first installing the unit? | If recent, proceed to Link A. If problem just emerged, proceed to Link B. | Where there any events like power surges, lighting strikes that might have disrupted the systems. If yes, proceed to Topic 104 | This might be a wiring issue that has caused a short. Proceed to TL #5 |
| TL #5 | If the problem is isolated to one or a few units, can you locate the controlling ILC and see if there is any sign of smoke or burn marks on the unit? If yes, proceed to Link A. If not, proceed to Link B | If burn marks or smoke, proceed to Link A. If no signs of damage, proceed to Link B. | Proceed to Topic 105 | Proceed to Topic 106 |
- ILC-xx0 controller may have had an interruption during a firmware upgrade. The suspect unit(s) may still be Programming Mode after an attempted firmware update occurred (which did not complete successfully and left the ILC-00x in an usual state. Try to perform a firmware Manual Upgrade on any suspect units to see if their on-board LED turns onto GREEN or YELLOW. Please refer to this separate document for how to perform a Manual Firmware Update on these units halt. Review and correct as necessary.
- There may be noise on the CS-Bus line that is interfering with commands. There also may be situation a proper ground has not been connected to the 3rd pin on the ILC-xx0 power connector. Check and resolve.
- There may have been a short on the ILC-xx0 connected LED load (between for example between the RED and the common + that the internal protection circuitry was unable to respond to quickly enough). A short would trigger a special circuity that is embedded within the ILC-xx0 that turns on one or more colors (and leaves them turned on) to indicate the presence of a serious short.
- ILC-xx0 controller may have had an interruption during a firmware upgrade. The suspect unit(s) may still be Programming Mode after an attempted firmware update occurred (which did not complete successfully and left the ILC-00x in an usual state. Try to perform a firmware Manual Upgrade on any suspect units to see if their on-board LED turns onto GREEN or YELLOW. Please refer to this separate document for how to perform a Manual Firmware Update on these units halt. Review and correct as necessary.
- There may be noise on the CS-Bus line that is interfering with commands. There also may be situation a proper ground has not been connected to the 3rd pin on the ILC-xx0 power connector. Check and resolve.
- There may have been a short on the ILC-xx0 connected LED load (between for example between the RED and the common + that the internal protection circuitry was unable to respond to quickly enough. A short would trigger a special circuity that is embedded within the ILC-xx0 that turns on one or colors (and leaves them turned on) to indicate the presence of a serious short.
- ILC-xx0 controller may have had an interruption during a firmware upgrade. The suspect unit(s) may still be Programming Mode after an attempted firmware update occurred (which did not complete successfully and left the ILC-00x in an usual state. Try to perform a firmware Manual Upgrade on any suspect units to see if their on-board LED turns onto GREEN or YELLOW. Please refer to this separate document for how to perform a Manual Firmware Update on these units. Review and correct as necessary.
- There may be noise on the CS-Bus line that is interfering with commands. There also may be situation a proper ground has not been connected to the 3rd pin on the green ILC-xx0 power connector. Check and resolve.
- There may have been a short on the ILC-xx0 connected LED load (between for example between the RED and the common + that the internal protection circuitry was unable to respond to quickly enough. A short would trigger a special circuity that is embedded within the ILC-xx0 that turns on one or colors (and leaves them turned on) to indicate the presence of a serious short.
- The e-Node may be disconnected from the LAN. Check e-Node to make sure that the on-board LED is flashing 1x per second. If the LED is not on at all, check the power to the e-Node. The ILC-xx0 controller may have had an interruption during a firmware upgrade. The suspect unit(s) may still be in Programming Mode after an attempted firmware update occurred (which did not complete successfully and left the ILC-00x in an unusual state). Try to perform a firmware Manual Upgrade on any suspect units to see if their on-board LED turns onto GREEN or YELLOW. Please refer to this separate document for how to perform a Manual Firmware Update on these units. Review and correct as necessary.
- Power surges, or lighting strikes are likely candidates for failures of electronics. You may simply wish to reboot the system and see if the problem disappears. A very simply solution would be to power cycle the suspect ILC-xx0 device. Leave it off for 8-10 seconds before powering it back on again.
- There may have been a short on the ILC-xx0 connected LED load (between for example between the RED and the common + that the internal protection circuitry was unable to respond to quickly enough). A short would trigger internal circuitry embedded within the ILC-xx0 that turns on one or colors (and leaves them turned on) to indicate the presence of a serious short. You should check your LED load for shorts before replacing the ILC-xx0 with a replacement unit, however.
- There may have been a short on the ILC-xx0 connected LED load (between for example between the RED and the common + that the internal protection circuitry was unable to respond to quickly enough) but which did not result in any outward signs of damage. Check your load for shorts before replacing the unit. Note: A short would trigger a special circuity that is embedded within the ILC-xx0 that turns on one or colors (and leaves them turned on) to indicate the presence of a serious short. In many cases we can repair a unit (an internal fuse that is soldered onto the motherboard) provided there is not other consequential damage.
Topic 100. Downstream ILC-xx0 controllers have fallen off-line. Possible crimp issue or CS-Bus cable may have come unplugged. or poor or bad ground or no ground connected to ground pin on 3-pin green power connector.
See the possible causes of this condition below. Review and correct as necessary
Topic 101. Random ILC-xx0 controller issues. Possible lighting strike or firmware upgrade failure or no good ground on 3-pin green power connector.
See the possible causes of this condition below. Review and correct as necessary
Topic 102. e-Node is seen (discoverable) on network but one or more connected ILC-xx0 are frozen in the ON state. Possible issues are that one or more ILC-xx0 controllers may be temporarily unreachable or is off-line having received some corrupted/unexpected commands (noise) that is impacting it.
See the possible causes of this condition below. Review and correct as necessary
Topic 103. e-Node has fallen off the network and therefore no commands are being received by downstream ILC-xx0 devices.
See the possible causes of this condition below. Review and correct as necessary.
Topic 104. Recent event may have damaged ILC-xx0 controller
See the possible causes of this condition below. Review and correct as necessary.
Topic 105. Damaged internal over-current protection device
See the possible causes of this condition below. Review and correct as necessary.
Topic 106. Damaged internal over-current protection device
See the possible causes of this condition below. Review and correct as necessary.