Z10 Troubleshooting Wizard
Use this visual decision tree for the most common field calls: manual override, sensor failure, 24V power loss, fuse issues, pushbutton issues, and Zelio/controller problems.
Before You Start: Could This Be a Legacy 5C?
If the panel says Lighting Manager - 5C, has a small older LCD with four buttons, or uses the older Powerbox-style front panel, stop the Z10 troubleshooting path and classify it as a legacy 5C system instead.
Step 1: What best describes the issue?
Choose the symptom that matches the site condition.
Field reference for the most common daytime lighting fault.
Step 2: Sensor path
Press and hold the left arrow on the Zelio. Confirm the displayed light level changes when you cover the sensor.
- 0 = dark
- 255 = bright daylight
- A change of about 50+ when covered is a good sign
Use the left-arrow readout to see what the controller thinks the sensor is seeing.
Likely Cause: Sensor or sensor wiring issue
The most likely problem is the LMZ10SEN1 sensor, its orientation, or its wiring back to the terminal strip.
- Clear cover should face north after installation
- Red = 24V, Black = common, White = signal
- DIP switches must be set as shown on the installation drawing
Use the installation drawing to verify orientation, conductor colors, and DIP switch settings.
Sensor replacement / wiring check
Verify wiring at the sensor and the terminal strip inside the cabinet before replacing the part. If the site still uses the older configuration, compare old vs new assembly details.
Reference drawing showing the LMZ10SEN1 assembly and legacy comparison.
Sensor appears to work
If the sensor value changes normally, the next checks are controller state and programming.
The standard troubleshooting order is overrides, RUN mode, sensor, then holiday/program checks.
Step 2: Manual override check
Are any of the red manual override buttons depressed and lit?
This image shows the timed override area, manual overrides, and output indicators on the Z10 panel.
Likely Cause: Manual bypass active
Press the red square button to cancel timed bypass. If the button sticks, fails to latch correctly, or keeps forcing outputs, inspect the pushbutton hardware.
Manual override and timed bypass should be your first check on almost every call.
Overrides not active
If no override is active, continue to power and controller checks.
Likely Cause: Pushbutton wear or operator issue
Inspect pushbutton heads and assemblies for sticking, failed contacts, broken lenses, or worn illuminated operators.
Step 2: Check 24V control power
Is the Zelio display active and is the ABLM1A24012 power supply energized?
This reference shows the control fuse locations and the ABLM power supply arrangement.
Likely Cause: Fuse or power supply path
If there is no control power, check fuse protection first, then the 24V power supply, then incoming terminals/wiring.
Likely Cause: Fuse failure
A blown control fuse is one of the quickest field fixes when the controller is completely dead.
Likely Cause: Power supply failure
If fuse protection looks good but there is no 24VDC output, the ABLM1A24012 power supply is the next most likely failed component.
Step 3: Zelio logic / programming check
If control power is present, move into controller state and programming. Check the parameter screens and confirm the controller is operating normally.
Use Menu/OK to enter Parameters and navigate the R00B screens.
Likely Cause: Zelio/controller output issue
If the controller is powered but outputs are incorrect, inspect program state, output switching, and controller integrity. The Zelio itself may be the failed component.
Likely Cause: Memory module or unstable control logic
If logic drifts, appears inconsistent, or does not behave as expected, inspect the memory module and confirm stable controller power first.
Programming Reference
Use the Zelio parameter screens to verify the main program values.
- Default password is typically 1000
- R00B000 = Holiday clock
- R00B001–010 = Light level outputs
- R00B011–020 = Timer control
- R00B021–030 = Light level delay
Intermittent operation path
For intermittent faults, start with the most common weak points in this order: pushbuttons, sensor input, 24V power stability, then Zelio/controller logic.
Step 3: Check RUN / STOP mode
If the Zelio display is active but the system is not behaving normally, confirm the controller is in RUN mode and not STOP.
- Controller must be in RUN for the lighting program to operate
- STOP mode can happen after transfer/program work
Your reference material explicitly calls out RUN mode as a troubleshooting priority.
Likely Cause: Controller left in STOP mode
If the display shows STOP or STOP FBD, the unit will not run the lighting program. Put the controller back into RUN mode.
- Menu/OK → Down Arrow → RUN/STOP
- Menu/OK → RUN
- After transfer, select WITH NONVOLAT INI if prompted
If the controller is not in RUN, nothing else downstream will behave correctly.
Controller is in RUN
If the controller is already in RUN mode, the next high-value check is the holiday clock override at R00B000.
Already in RUN but still not correct
If the unit is in RUN and the issue remains, move to holiday clock and parameter checks before replacing the controller.
Step 4: Check Holiday Clock (R00B000)
Your troubleshooting material specifically identifies the holiday timeclock as a possible program override. Go to R00B000 and confirm it is not forcing the wrong state.
- Default password is typically 1000
- Holiday Clock is under R00B000
- Every OFF event must have a corresponding ON event
Use Menu/OK to reach Parameters and navigate to R00B000.
Likely Cause: Holiday clock override
If the holiday schedule is set incorrectly, it can force the lights on or off even when the sensor and daily program look correct.
- Correct the OFF/ON pair at R00B000
- Save changes and return to main screen
- Re-test system operation afterward
Holiday clock problems are easy to miss and can look like a sensor or controller fault.
Holiday clock looks normal
If RUN mode is correct and the holiday clock is not overriding the program, continue with the normal parameter and component checks.