What Is It

The Smidnya IL22 Black Body Lead Wire Metal Pilot Light Yellow/Blue is a panel-mount metal pilot light designed for local machine-status indication. The yellow/blue combination is especially useful when operators must distinguish between attention-required conditions and intentional operator-selected states such as manual mode, local mode, service mode, or setup mode.

The lead wire format makes this version particularly practical for compact enclosures, machine doors, retrofit panels, and internal harness layouts where direct routing is simpler than terminal-style lamp arrangements. The black body finish also works well in darker fascia layouts by keeping focus on the illuminated color rather than the hardware body.

Key Specifications

How It Works

A pilot light converts an electrical signal into a visible machine-state condition. In most industrial systems, the signal is driven by 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 in the control philosophy.

• Yellow ON = warning, advisory, process deviation, waiting state, service attention, abnormal-but-not-trip condition
• Blue ON = manual mode active, service mode enabled, local control selected, setup state active, command acknowledged
• OFF = no active condition, no control voltage, or state not asserted
• Flashing Yellow = warning escalation, unresolved advisory, delayed response, or persistent abnormality
• Flashing Blue = setup prompt, service step, local-mode reminder, or transition-state attention depending on control logic

Why Yellow / Blue Is Valuable in Real Panels

Yellow/blue works extremely well in real machine design because the two colors communicate two different but equally important categories of information. Yellow means the machine needs attention. Blue means the machine is in an intentional operator-selected or service-related state. This prevents the common mistake of mixing both into one color, which creates ambiguity.

Applications

• Manual mode / warning indication panels
• Setup-state and advisory 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 warning from service state
• Door-mounted operator panels with direct harness routing
• Retrofit panels with advanced mode-state logic

Selection Guide

Choose this model when you need:

• A compact metal pilot light for industrial panels
• Fast visual separation between warning and service/manual states
• Lead wire connection for direct routing in compact or door-mounted layouts
• Wide AC/DC voltage compatibility
• A more precise status philosophy than generic red/green-only signaling

Choose yellow when the machine needs attention.

Choose blue when the machine is in a deliberate operator-selected or service-related state.

Choose the voltage by actual control-circuit voltage.

Choose the lead wire format when compact internal routing is more important than terminal-style replacement convenience.

Complete Alarm System Design Guide

A pilot light alone is not a full alarm architecture. High-quality industrial signaling uses layers so operators can see the state locally, understand its meaning, hear escalation when needed, and review event history later.

Panel Design Examples

1) Basic Machine Panel

• 1 x IL22 Yellow = Warning / attention required
• 1 x IL22 Blue = Manual mode / service state
• Start push button
• Stop push button
• E-stop
• Optional buzzer for persistent warning escalation

2) Compact Door-Mounted OEM Panel

• Lead-wire lamps routed directly into the door harness
• Yellow = Advisory, process deviation, waiting condition, maintenance attention
• Blue = Manual mode, local mode, setup state, service workflow state
• Stack light = Cell-wide visibility
• Buzzer = Timed escalation for unresolved yellow state
• HMI = Exact warning cause, mode explanation, acknowledgment, operator instructions

Typical PLC logic: yellow turns ON for meaningful attention-required conditions that are not yet full trip states. Blue turns ON when the machine is intentionally in manual, setup, or service mode. Flashing yellow identifies unresolved warnings or timer-based escalation. Flashing blue may be used for service prompts, setup steps, or transition attention. The buzzer activates only for selected warning priorities, not merely because blue mode is active.

3) Multi-Machine Line Architecture

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

Deeper Troubleshooting and Failure Analysis

Symptom 1: Yellow Does Not Turn ON Even Though a Warning Condition Exists

• Warning bit not mapped correctly to the lamp output
• Advisory routine does not include the actual condition needing attention
• PLC output failure
• Relay contact not switching
• Wrong supply voltage to the lamp
• Lead wire open circuit or conductor fatigue
• Internal LED failure

Symptom 2: Blue Turns ON, but Operators Do Not Understand the State

• 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 3: Lead Wire Version Fails Prematurely in Service

• No strain relief near the lamp body
• Door harness bends too tightly
• Repeated panel-door opening causes conductor fatigue
• Wires routed over sharp metal edges
• Heat exposure near drives, contactors, or transformers
• Poor splice protection in damp panels

Symptom 4: Yellow Stays ON Too Often and Operators Start Ignoring It

• Too many minor events are configured as warnings
• No delay, deadband, or filtering in advisory logic
• No distinction between advisory and near-trip warning
• No HMI explanation tied to the yellow state
• No nuisance-warning review after commissioning

Symptom 5: Blue Does Not Turn ON in Manual or Service Mode

• Manual mode bit not mapped correctly
• Selector-switch feedback not reaching the PLC
• Local/remote state logic incomplete
• Blue channel wiring fault
• Command acknowledgment logic tied to the wrong state bit
• Intermittent lead-wire strain causing mode loss during door movement

Symptom 6: Yellow 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 7: Operators Miss the Yellow Warning 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 local warning points with no hierarchy
• No HMI acknowledgment workflow

Symptom 8: Yellow and Blue Appear Together and the Panel Becomes Ambiguous

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

Real Industrial Case Logic

A frequent real-world design error is using blue for both “manual mode active” and “hold acknowledged,” while yellow is tied to every small fluctuation in the machine. The result is predictable: blue loses meaning, yellow becomes background noise, and operators stop reacting correctly. In compact door-mounted panels, repeated door movement may also damage the lead wires over time, creating intermittent states that make diagnosis even harder.

Better designs reserve yellow for meaningful attention-required states and blue for deliberate operator-selected or service-related states, while protecting the lead wires mechanically. Once that is combined with stack light escalation, buzzer logic, HMI advisory text, and SCADA event history, the control system becomes easier to understand, easier to maintain, and more useful for predictive maintenance.

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 splices, terminations, or wire joints
• Condensation in under-ventilated enclosures
• Insulation stress from sunlight, chemicals, or heat
• Intermittent indication from oxidized or loose electrical joints

For outdoor use, the full assembly matters: panel cutout quality, gasket integrity, enclosure sealing, cable-entry method, rear-side protection, 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 Lead Wire Metal Pilot Light Yellow/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_YB_Yellow_Warn
• PL_YB_Blue_Manual
• PL_YB_YellowFlashEnable
• PL_YB_BlueFlashEnable
• PL_YB_LampTest
• Alarm_Warning_Active
• Alarm_Warning_Ack
• Mode_Manual_Active
• Mode_Local_Active
• Alarm_HornMute

Recommended control philosophy:

• Yellow turns ON only for meaningful attention-required states
• Blue turns ON only for deliberate manual, service, local, or setup states
• Flashing yellow identifies unresolved or escalating warning conditions
• Flashing blue may indicate service prompts, transition states, or acknowledgment-related operator tasks
• Buzzer activates only for selected warning priorities, not merely because blue mode is active
• SCADA should track first-up warning, manual-mode duration, repeat-event frequency, and response time

Predictive maintenance examples:

• Warning frequency rising before real faults begin
• Manual-mode intervention increasing on a specific station
• Service-state duration growing over time
• Inspection drift causing repeated local adjustments
• Lead-wire fatigue appearing as intermittent yellow or blue indication during door movement

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

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

• Local yellow = machine-level advisory or attention-required state
• 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 warning review and mode-state tracking
• IoT / dashboards = remote visibility for warning trends, manual-intervention frequency, response time, and predictive maintenance patterns

Frequently Asked Questions