What Is It

The Smidnya IL22 Chrome 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 where operators must distinguish between real abnormal / trip / fault conditions and manual mode / service mode / setup mode / command acknowledgment states.

In practical panel design, this makes the product more informative than simple red/green or single-color indication in applications where operator intent and machine abnormality must remain visually separate.

Key Specifications

How It Works

A pilot light converts an electrical signal into a visual condition. In most industrial machines, the signal comes from a PLC output, relay contact, timer logic, auxiliary contact, drive-status bit, or machine-state routine. Each color channel is assigned a defined meaning within the machine’s alarm philosophy.

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

Why Red / Blue Is Valuable in Real Panels

Red/blue is highly useful in real machine design because the two colors represent fundamentally different categories of information. Red is naturally understood as abnormality or danger. Blue is better suited for operator-selected states, manual mode, service mode, and confirmation logic. This reduces ambiguity and makes troubleshooting faster.

Applications

• Manual mode / fault indication panels
• Setup-mode and abnormality signaling in OEM machines
• Packaging, filling, conveyor, and automation systems
• Inspection systems, reject stations, and service-mode workflows
• Utility panels with maintenance or local-control states
• Control stations where operators must know whether the machine is in service or in fault
• Retrofit panels with more advanced mode-state logic
• Machine cells needing strong distinction between operator action and abnormal condition

Selection Guide

Choose this model when you need:

• A compact metal pilot light for industrial panels
• Fast visual distinction between fault and service/manual conditions
• Wide AC/DC voltage compatibility
• Multiple mounting sizes for OEM and retrofit use
• A cleaner status philosophy than forcing everything into red/green logic

Complete Alarm System Design Guide

A pilot light alone is not a full alarm architecture. Strong industrial signaling uses multiple layers so operators can see the condition locally, understand its meaning, hear escalation when necessary, and review the event historically.

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 fault escalation

2) Smart OEM Panel

• Red = Real abnormality or stop-causing condition
• Blue = Manual mode, local mode, or service state
• Stack light = Cell-wide visibility
• Buzzer = Timed escalation for unresolved red alarm states
• HMI = Exact fault cause, mode indication, acknowledgment, recovery instructions

Typical PLC logic: red turns ON for actual abnormal or trip conditions. Blue turns ON when the machine is intentionally placed in manual, setup, or service mode. Flashing red indicates an unacknowledged or high-priority alarm. Flashing blue can be used for service prompts or transition states. The buzzer activates only for selected priority faults, not simply because the machine is in manual mode.

3) Multi-Machine Line Architecture

• Local red / blue indication at each machine
• Stack light for cell-wide or line-wide visibility
• Line buzzer for synchronized alarm escalation
• SCADA dashboard for first-up fault analysis 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 all true stop-causing conditions
• PLC output failure
• Relay contact not changing state
• Wrong supply voltage to the lamp
• Internal LED failure
• Alarm priority logic suppressing the visual output unintentionally

Symptom 2: Blue Turns ON, but Operators Think the Machine Is Healthy

• Blue is not clearly labeled as manual or service mode
• No HMI explanation tied to blue state
• Operators were trained only for red/green-style logic
• Panel color philosophy is inconsistent between machines
• Blue is being used for too many unrelated meanings

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

• Latched alarm bit not reset
• Safety relay still not healthy
• Reset sequence only clears the HMI display, not the control logic
• First-up fault memory or hold circuit still active
• SCADA or remote logic mismatch leaving the alarm active

Symptom 4: Blue Does Not Turn ON in Manual or Setup Mode

• Manual mode bit not mapped correctly
• Selector switch feedback not reaching PLC
• Local/remote state logic incomplete
• Blue channel wiring fault
• Command acknowledgment logic tied to the wrong state bit

Symptom 5: 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 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 structure
• No HMI acknowledgment workflow

Symptom 7: Blue Is Active During Service, but Red Appears at the Same Time and Confuses Everyone

• Manual mode did not suppress non-relevant automatic alarms
• Service-state alarm masking is not properly engineered
• Interlock logic does not distinguish between expected service conditions and true faults
• No documented operating philosophy for simultaneous mode and fault display
• HMI and pilot-light meanings are not aligned

Real Industrial Case Logic

A common real-world design error is using blue for both “manual mode active” and “machine healthy confirmation,” while red is wired only to a limited subset of fault conditions. The result is serious confusion. Operators see blue and assume the machine is acceptable, even though it may be in service mode, locally isolated, or only partially functional. At the same time, some real abnormal conditions never reach the red indicator because they were not included in the alarm routine.

Better designs reserve red for true abnormality and blue for deliberate operator-selected or service-related states. Once that is combined with stack light escalation, buzzer logic, HMI fault text, and SCADA event history, the control system becomes much easier to understand and much 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 connections 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 front metal bezel alone does not guarantee 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 Red/Blue metal-body 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, setup, or local-control states
• Red flashing identifies unresolved or high-priority alarms
• Blue flashing may identify service-step attention or operator confirmation states
• Buzzer activates only for selected alarm priorities, not simply because blue mode is active
• SCADA should track first-up fault, manual-mode duration, repeat-event frequency, and mean time to recovery

Predictive maintenance examples:

• Machine repeatedly enters manual mode before a fault appears
• Service-state frequency rising over time on one station
• Inspection lighting drift causing repeated local interventions
• Valve cycle counts driving more frequent setup adjustments
• Panel temperature rise correlating with abnormal stop frequency

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 response is risky
• SCADA = first-up fault review and mode-state tracking
• IoT / dashboards = remote visibility for stop trends, manual-intervention frequency, MTTR, and predictive maintenance patterns

Frequently Asked Questions