You are using an unsupported browser. Please update your browser to the latest version on or before July 31, 2020.
You are viewing the article in preview mode. It is not live at the moment.

⚠️  JADConfig will reach End of Support on January 1, 2027. View the official notice!   ⚠️

Home > Device Configuration > How to Manage Power and Data LEDs (Omega, Ultra, and MaxColor Series)
How to Manage Power and Data LEDs (Omega, Ultra, and MaxColor Series)
Last updated: Oct 05, 2026

Overview

Omega Series, Ultra Series, and MaxColor Series Encoders and Decoders support commands and settings that change Power and Data LED behavior.

  • Commands: Change LED behavior immediately without a reboot. These changes do not persist through a reboot.
  • Startup settings: Change LED behavior after the settings are saved and the device reboots. These settings remain active until modified or removed.

Diagnostic information: Customized LED behavior can hide the device's actual operating status. Restore default behavior before using the LEDs for troubleshooting. See Understand Power and Data LED Behavior for normal patterns and troubleshooting steps.

Access the Command Line Interface

Connect to the device using either method:

  • Telnet: Connect to the device IP address on TCP port 23.
  • RS232 debug connection: Use a Just Add Power debug cable connected to the white, 3-pin Molex debug connector on the bottom of the device. Use 115200-8n1: 115200 baud, 8 data bits, no parity, and 1 stop bit. Contact Just Add Power Technical Support if you need a debug cable.

All commands, setting names, and values are case-sensitive.

Change LED Behavior Immediately

Execute a command below to change LED behavior immediately. These commands do not require saving or rebooting and do not replace the saved startup setting.

Command Behavior
leds on Turn on both LEDs regardless of device status.
leds off Turn off both LEDs regardless of device status.
leds blink Blink both LEDs steadily regardless of device status.
leds heartbeat Blink both LEDs in a heartbeat pattern: blink, blink, pause, repeat.
leds watchdog on Allow the device to change LED behavior. This command works only when the LED startup setting has been changed from its default.
leds watchdog off Prevent the device from changing LED behavior. This command works only when the LED startup setting has been changed from its default.
leds default Return the LEDs to standard behavior based on operating status. This does not remove a saved LED startup setting.

Verify the result by observing the LEDs on the device.

Configure LED Startup Behavior

Use a startup setting when the selected behavior must persist after a reboot.

Setting Behavior After Saving and Rebooting
astparam s leds always_off Keep both LEDs off.
astparam s leds only_on_video Turn on both LEDs when video is present and turn them off when video is absent.

Reboot interruption: Applying a startup setting requires restarting the device, which temporarily interrupts its operation.

  1. Execute the desired setting from the table.
  2. Execute astparam save to save the setting.
  3. Execute sleep 1 to wait one second before rebooting.
  4. Execute reboot.
  5. After the device restarts, verify that the LEDs follow the selected behavior. For only_on_video, check with video present and absent.

The setting can also be saved through the webUI before rebooting. For additional startup settings, see Startup Settings for Omega and Ultra Series Devices.

Restore Default LED Behavior

To restore standard LED behavior immediately, execute leds default.

If a custom startup setting was saved, remove it so default behavior also returns after future reboots:

  1. Execute astparam s leds with no value to remove the custom LED startup setting.
  2. Execute astparam save.
  3. Execute sleep 1.
  4. Execute reboot.
  5. After the device restarts, verify that the LEDs reflect its operating status.
close button
scroll to top icon