User: Mamoo, Location: Ashburn, VA
Asked on: Friday, November 8, 2024 at 6:42 pm EST
Answered on: Thursday, March 6, 2025 at 5:01 am EST
Question: Hey all, we use nLight lighting controls at our facility and I’m trying to figure out if we have a failing power pack(s).An electrician mentioned a bad power pack but I was only testing line voltage when checking it out, and the fuse for the PP was still good. (NPP16-D-EFP)I replaced the drivers today and the lights are funky as hell now. Only the 2nd driver I installed turns on and it’s really dim. The first light generally won’t come on, but was working when I first tested it.I’m starting to think the control wires for dimming could be bad or the power pack is somehow failing.Is this behaviour a sign of a bad power pack or wiring issue with the dimmers? I also can login to sensor view and check the PP on there if need be but haven’t tried yet
Okay, this sounds like a frustrating troubleshooting situation! Let's break down the symptoms and explore possible causes with the nLight system. Based on your description, here's a structured approach
Understanding nLight Power Packs and Dimming
Power Pack (NPP16-D-EFP)
This is the heart of the control. It takes line voltage, provides power to the lighting fixture, and importantly, interprets the nLight control signals for on/off and dimming. The "-D" in the model number indicates it's a dimming power pack.
Control Wiring
This is crucial. nLight uses a low-voltage, typically Cat5/Cat6, network to communicate between the sensors, switches, and power packs.
Drivers
These convert the AC power from the power pack to the specific DC voltage and current needed by the LEDs.
SensorView
This software is your best friend for diagnosing nLight issues.
Possible Issues and Troubleshooting Steps1. SensorView Diagnostics (PRIORITY #1)
Log in to SensorView. This should be your first step. Check the Status of the Power Packs
SensorView should tell you if the power packs are online and reporting errors. Look for:
Offline Status
If a power pack is offline, that's a clear indication of a problem (power, network connectivity, or pack failure).
Error Codes
nLight devices report error codes. Document these and look them up in the nLight documentation. They can pinpoint the type of failure.
Dimming Level Reporting
Can you see the dimming level being sent to the power pack? Does it match what you expect based on the sensor or switch settings?
Check Occupancy Sensor and Switch Status
Ensure they are communicating and sending signals correctly.2.
Wiring (Especially the Control Wiring)
Bad Control Wiring Connections
This is the most common culprit in nLight systems.
Check the Cat5/Cat6 connections at the power pack
Are they properly terminated? Are any wires loose or corroded? Ensure all 8 wires of the cable are properly punched down.
Check the connections at the sensors and switches
Same as above.
Test the Cable
If possible, use a cable tester to check the Cat5/Cat6 cable for continuity and shorts. A shorted or open wire on the data lines can cause all sorts of weird behavior.
Incorrect Wiring
Double-check that the Cat5/Cat6 cables are wired according to the nLight standard. It's easy to accidentally swap wires, especially if re-terminating.
Daisy Chaining Limits
nLight has limits on the number of devices you can daisy-chain on a single segment of control wiring. Exceeding this limit can cause communication problems. Look at your installation diagram to see if you're nearing the limit.3.
Power Pack Problems
Partial Failure
It's possible the power pack is failing in a way that it's still passing line voltage (hence the good fuse), but the dimming control circuitry is damaged. This would explain why you see some power but the lights are acting strangely.
Voltage Imbalance
Try testing the VAC output to the drivers and ensure they are outputting the correct voltage based on the driver model.4.
Driver Compatibility
Are the New Drivers Compatible with the nLight Dimming System? This is critical. nLight typically uses 0-10V dimming. The drivers must support 0-10V dimming. If they don't, they will not respond correctly to the nLight control signals. Look at the driver's specifications to confirm. Driver Wiring
Ensure the dimming wires (+ and -) from the driver are correctly connected to the power pack's dimming terminals.
Driver Power Supply
Make sure the driver you installed has the correct input voltage and wattage for the power pack.5.
Troubleshooting Steps Isolate the Problem
Test with One Light
Disconnect all but one of the lights from the power pack. Does that single light behave correctly? If so, the problem might be related to overloading the power pack or a problem with one of the other lights/drivers.
Swap Power Packs
If you have another identical power pack nearby, temporarily swap it with the suspect one. Does the problem move with the power pack? This is a good way to confirm a power pack failure.
Manually Override Dimming (If Possible)
Some nLight power packs have a way to manually override the dimming (e.g., a potentiometer). Try this to see if you can get the lights to brighten or dim. This would help isolate whether the dimming control is working at all.
Specific Recommendations for Your Situation Log into SensorView immediately. This is non-negotiable. Get the diagnostics. Check the new drivers' specifications. Confirm they are 0-10V dimmable and compatible with the nLight system. Carefully inspect the Cat5/Cat6 connections at the power pack, sensors, and switches. Look for any signs of damage, corrosion, or loose wires. Try the single-light test.Important Notes Safety
Always work with electrical systems with the power off. If you're not comfortable working with electricity, call a qualified electrician who is familiar with nLight systems.*
Documentation: Refer to the nLight documentation for your specific components (power packs, sensors, switches, and drivers). The documentation will have wiring diagrams, troubleshooting tips, and error code descriptions.Good luck! Troubleshooting lighting control systems can be tricky, but with a systematic approach, you should be able to find the problem. Remember to document your steps and findings along the way. Let me know what you find in SensorView. Flag for review