What Is It

The Smidnya IL22 Black Body Metal Pilot Light Red/Blue is a panel-mount metal pilot light designed for local machine-status indication. The red/blue combination is especially useful when operators must distinguish between real abnormality, alarm, trip, stop, or unsafe machine conditions and manual mode, setup mode, service state, local mode, or deliberate operator-selected states.

The black body finish works particularly well in modern control panels because it visually blends into darker fascia layouts, HMI bezels, and premium enclosures, allowing the illuminated signal color to remain the primary attention point.

Key Specifications

How It Works

A pilot light converts an electrical signal into a visible machine-state condition. In industrial control systems, the signal usually comes from a PLC output, relay contact, timer logic, auxiliary contact, selector-switch feedback, drive-status bit, or machine-state routine. Each color is assigned a specific meaning inside the control philosophy.

• Red ON = fault, alarm, trip, stop condition, unsafe state, interlock abnormality, urgent attention required
• Blue ON = manual mode active, local control selected, service mode enabled, setup state active, command acknowledged
• OFF = no active condition, no control voltage, or state not asserted
• Flashing Red = critical alarm, unacknowledged stop, high-priority abnormality, urgent intervention required
• Flashing Blue = setup prompt, service step, local-mode reminder, transition-state cue, or maintenance workflow attention depending on logic design

Why Red / Blue Is Valuable in Real Panels

Red/blue is highly useful in industrial machine design because the two colors communicate two fundamentally different categories of information. Red means the machine is abnormal or unsafe. Blue means the machine is intentionally in a human-selected state such as manual, service, or setup mode. This prevents the common design mistake of forcing both meanings into one color, which makes panels slower to interpret.

Applications

• Manual mode / fault indication panels
• Setup-state and abnormality signaling in OEM machines
• Packaging, filling, conveyor, and automation systems
• Inspection systems, reject stations, and service workflows
• Utility panels with local-control or maintenance states
• Machine cells where operators must separate fault from service state
• Retrofit panels with improved mode-state logic
• Control stations needing clear distinction between abnormal and manual conditions

Selection Guide

Choose this model when you need:

• A compact metal pilot light for industrial panels
• Fast visual separation between fault and service/manual states
• Wide AC/DC voltage compatibility
• Multiple mounting sizes for OEM and retrofit use
• A clean black-body appearance that fits modern control panels

Choose red only for true abnormality, trip, alarm, or urgent intervention conditions.

Choose blue only for meaningful manual, setup, local, or service-related states.

Choose the voltage by actual control-circuit voltage, not by spare-part visual similarity.

Complete Alarm System Design Guide

A pilot light alone is not a complete alarm architecture. Strong industrial signaling uses multiple layers so operators can see the state locally, understand its priority, hear escalation when needed, and review event history later.

Panel Design Examples

1) Basic Machine Panel

• 1 x IL22 Red = Fault / trip / stop condition
• 1 x IL22 Blue = Manual mode / service state
• Start push button
• Stop push button
• E-stop
• Optional buzzer for unresolved red alarm escalation

2) Smart OEM Panel

• Red = Real abnormality or stop-causing condition
• Blue = Manual mode, local mode, setup state, service workflow state
• Stack light = Cell-wide visibility
• Buzzer = Timed escalation for unresolved red alarms
• HMI = Exact fault cause, mode explanation, acknowledgment, operator instructions

Typical PLC logic: red turns ON for genuine abnormal or trip conditions. Blue turns ON when the machine is intentionally placed into manual, local, setup, or service mode. Flashing red identifies unresolved or high-priority alarms. Flashing blue may be used for service prompts, setup steps, or transition cues. The buzzer activates only for selected red-priority alarms, not simply because blue mode is active.

3) Multi-Machine Line Architecture

• Local red / blue indication at each machine
• Stack light for wider cell or line visibility
• Line buzzer for synchronized alarm escalation
• SCADA dashboard for first-up fault review and mode tracking
• Andon or central display for line-state communication

Deeper Troubleshooting and Failure Analysis

Symptom 1: Red Does Not Turn ON Even Though a Fault Exists

• Fault bit not correctly mapped to the lamp output
• Alarm routine does not include the actual stop-causing condition
• PLC output failure
• Relay contact not switching
• Wrong voltage applied to the lamp
• Internal LED failure
• Alarm-priority logic unintentionally suppressing visual indication

Symptom 2: Blue Does Not Turn ON During Manual or Service Mode

• Mode bit not mapped correctly
• Selector-switch feedback not reaching the PLC
• Local/remote state logic incomplete
• Blue channel wiring fault
• Command acknowledgment tied to the wrong state bit
• Mode logic blocked by unexpected interlocks

Symptom 3: Blue Turns ON, but Operators Do Not Understand the Meaning

• Blue is not clearly labeled as manual, service, setup, or local mode
• No HMI explanation linked to the blue condition
• Operators were trained only for red/green logic
• Color philosophy is inconsistent across machines
• Blue is reused for too many unrelated states

Symptom 4: Red and Blue Behave Intermittently

• Unstable control voltage
• Poor grounding or floating common reference
• Electrical noise from drives or motor cables
• Output chatter caused by unstable feedback signals
• Crossed wiring between channels
• Poor relay quality or worn contacts

Symptom 5: Red Stays ON Even After the Fault Seems Cleared

• Latched fault bit not reset
• Safety relay or interlock still not healthy
• Reset sequence clears the HMI but not the actual control logic
• First-up fault memory remains active
• SCADA or remote logic mismatch keeps the alarm state live

Symptom 6: Operators Miss the Red Fault State

• Lamp too small for the viewing distance
• Poor mounting height or glare on the panel face
• No buzzer escalation
• No stack light for broader visibility
• Too many red points with no priority hierarchy
• No HMI acknowledgment workflow

Symptom 7: Red and Blue Appear Together and the Panel Becomes Ambiguous

• Manual mode did not suppress non-relevant automatic alarms
• Service-state masking is not properly engineered
• Expected service conditions are treated like genuine abnormal conditions
• No documented philosophy for simultaneous fault and mode display
• HMI text and pilot-light meaning are not aligned

Real Industrial Case Logic

A common real-world design error is using blue for both “manual mode active” and “hold acknowledged,” while red is tied only to a limited subset of true faults. The result is predictable: blue loses meaning, red under-reports real abnormality, and operators begin making incorrect assumptions about what the panel is telling them. Eventually, a machine may appear to be safely in service mode even while a genuine stop-causing condition is active elsewhere in the logic.

Better designs reserve red for meaningful abnormal or stop-causing conditions and blue for deliberate operator-selected or service-related states. Once that is combined with stack light escalation, buzzer logic, HMI mode text, and SCADA event history, the system becomes easier to understand, easier to maintain, and safer to operate.

Environmental Failure, IP Protection, and Outdoor Applications

Pilot lights often fail because of environment rather than light-source weakness. Typical threats include dust, oil mist, moisture, coolant vapor, thermal cycling, vibration, corrosion, UV exposure, and poor panel sealing.

• Seal compression loss over time
• Moisture ingress from rear-side panel exposure
• Corrosion at terminals or splices
• Condensation in under-ventilated enclosures
• Discoloration from sunlight or harsh cleaners
• Intermittent indication from oxidized joints or loose wiring

For outdoor use, the full assembly matters: panel cutout quality, gasket integrity, enclosure sealing, rear-side protection, cable-entry method, and weather exposure. The lamp body alone does not determine outdoor durability.

Hazardous Area, Safety Compliance, and Explosion Risk Signaling

Standard industrial pilot lights should not be assumed suitable for hazardous-area use. If combustible gas, vapor, or dust is present, the pilot light, enclosure, wiring method, and protection concept must match the application requirements.

The safe engineering position is simple: treat this IL22 Black Body Metal Pilot Light Red/Blue variant as a standard industrial panel indicator unless the exact hazardous-area certified version is explicitly confirmed.

PLC Integration, SCADA Alarm Logic, and Predictive Maintenance

Suggested PLC tags:

• PL_RB_Red_Fault
• PL_RB_Blue_Manual
• PL_RB_RedFlashEnable
• PL_RB_BlueFlashEnable
• PL_RB_LampTest
• Alarm_Critical_Active
• Alarm_Critical_Ack
• Mode_Manual_Active
• Mode_Local_Active
• Alarm_HornMute

Recommended control philosophy:

• Red turns ON only for true abnormal, stop-causing, or urgent attention conditions
• Blue turns ON only for deliberate manual, service, local, or setup states
• Flashing red identifies unresolved or high-priority alarms
• Flashing blue may indicate service prompts, transition states, or acknowledgment-related operator tasks
• Buzzer activates only for selected red-priority alarms, not merely because blue mode is active
• SCADA should track first-up fault, manual-mode duration, repeat-event frequency, and response time

Predictive maintenance examples:

• Fault frequency rising before major downtime begins
• Manual-mode intervention increasing on a specific machine
• Setup-state duration growing over time
• Repeated unresolved red states following similar load conditions
• Mode-change frequency indicating deeper instability in process setup

Multi-Machine Synchronization, IoT Integration, and Industry 4.0 Signaling

In connected production systems, one machine’s fault or manual state can affect upstream and downstream equipment. That means the signaling philosophy must work at both machine level and line level.

• Local red = machine-level abnormality or stop condition
• Local blue = machine-level service, local, or manual mode
• Stack light = wider visibility across the cell or line
• Buzzer = escalation when delayed operator response becomes risky
• SCADA = first-up fault review and mode-state tracking
• IoT / dashboards = remote visibility for stop trends, manual-intervention frequency, response time, and predictive maintenance patterns

Frequently Asked Questions