Alarm History Screenshot Checklist

Alarm history can show whether an issue is isolated, repeated, or part of a sequence. A clear screenshot helps support understand what happened before the machine stopped or required operator action.

Before changing settings or restarting repeatedly, collect the alarm evidence.

Screens to Capture

If the controller provides these pages, record:

• Current alarm screen.
• Alarm history list.
• Machine status or current cycle step.
• Program name or mold program screen.
• Any related auxiliary equipment status screen.

Take full-screen photos when possible. The screen title, time, and surrounding fields help support understand context.

Notes to Add with Screenshots

Alarm screenshots become more useful when paired with short notes:

• What was the machine doing when the alarm appeared?
• Did the alarm appear during mold close, injection, table movement, part removal, loading, or startup?
• Did it appear after a mold change, material change, maintenance activity, or parameter change?
• Does it appear once or repeatedly?
• Can the operator reset it, or does it return immediately?

Do not erase or overwrite the record before support has reviewed it if the issue is repeated.

Safe Photo and Video Guidance

If movement or timing is involved, a short video may help. Record only from outside guarded or moving areas. Do not place a camera inside the mold area, table area, or robot cell while equipment is active.

For insert molding and overmolding work, safe photos of insert loading position, fixture area, part removal path, and mold access may help explain why the alarm appears at a specific point in the cycle.

When to Use Troubleshooting Articles

If the alarm is connected with a visible part issue, review the related troubleshooting path as well. A short shot, flash, part sticking, insert shift, or unstable cycle may need both controller evidence and process evidence.

Related Reading

• Machine Alarms and Issues
• Controller Settings
• Pre-start Checklist
• Process Issues