How to View Log Messages from a Just Add Power Encoder or Decoder

Jan 08, 2026

Overview

This procedure collects a complete, timestamped snapshot of system state and activity from a Just Add Power device. When captured consistently, these logs allow Support to verify system uptime, configuration state, and runtime behavior before, during, and after a reported issue.

Following the steps below ensures that logs are complete, verifiable, and aligned across devices.

Quick Reference

Power cycle the full Just Add Power system
Record the date and time of the power cycle
Identify the affected Encoder and Decoder
Configure PuTTY session logging
Reproduce the issue if possible
Note the date/time and device uptime when the symptom occurs
Run the full command set on both devices
Email the saved log file and context to [email protected]

Common Mistakes to Avoid

Capturing logs from only one device instead of both the Encoder and Decoder
Skipping the system power cycle before logging
Not enabling PuTTY session logging
Omitting device uptime verification
Copying partial or edited command output
Submitting logs without symptom timing or trigger context

Applies To

Just Add Power Products

Omega Series
All Encoders, Decoders, and Encoder/Decoder models
Ultra Series
All Encoders, Decoders, and Encoder/Decoder models
MaxColor Series
All Encoders, Decoders, and Encoder/Decoder models

Minimum Firmware Required

Omega / Ultra Series: B2.X.X
MaxColor Series: v3.X.X

Prerequisites

IP access to the target Encoder and Decoder
CLI access via webUI, Telnet, or PuTTY
Ability to power cycle the Just Add Power system

Logging Preparation

Important: Logs must be captured from both the Encoder and the Decoder. Single-device logs rarely provide enough information for root-cause analysis.

Perform a full Just Add Power system power cycle.
Record the date and time this is completed.
Identify the Encoder and Decoder involved in the issue.
Optional:
If the issue scope is unclear, prepare additional devices for logging.

Optional Time & DNS Configuration

DNS Server: 8.8.8.8
Time Server: time.nist.gov

These settings are optional but can improve timestamp alignment across devices.

Configuring PuTTY Session Logging

To ensure all output is captured accurately, PuTTY should be configured to log the entire session to a file.

Open PuTTY and enter the device IP address.
In the left menu, expand Session → Logging.
Select All session output.
Choose a log file location and filename.
Return to Session and click Open.

Do not copy and paste command output manually. Use the saved PuTTY log file when submitting logs to Support.

When the Symptom Is Occurring

Record the current date and time.
Record the device uptime.
This confirms how long the device has been running since the last reboot.
Document what triggered the symptom.

Required Command Set

Run the following commands in order on both the Encoder and Decoder. All output should be captured by the PuTTY session log.

Command	Purpose
`cat /proc/uptime`	Verifies device uptime and confirms reboot timing
`astparam dump`	Captures current system configuration parameters
`astparam dump ro`	Captures read-only factory and hardware parameters
`cat /var/log/messages`	Captures system and runtime log messages

All commands must be run. Missing output may require the logs to be recollected.

Submitting Logs to Support

Submit the complete PuTTY session log file without editing or filtering.

Email the log file(s) to:
[email protected]
Include in the email:
- Date/time of system power cycle
- Date/time when the symptom occurred
- Which Encoder(s) and Decoder(s) logs were captured from
- Any relevant context around the symptom trigger

Providing complete, consistent logs allows Just Add Power Support to analyze issues more efficiently and reduces the likelihood of follow-up data requests.