SYST-009

Physical inspection of all gates

Walk the entire perimeter of the robot cell and verify every gate and access door is completely closed and latched. Check for obstructions (debris, cables, air hoses) preventing full closure. Confirm positive engagement of all latch mechanisms.

Never bypass or defeat safety interlocks to clear this alarm. Ensure the cell is clear of personnel before closing gates.

Verify gate interlock switch actuation

With the gate closed, manually verify that each safety switch is being physically actuated by the gate/door mechanism. Check for misalignment, switch mounting looseness, or worn actuation cams. Safety switches typically require 3-5mm actuation travel.

Look for paint buildup, dirt, or ice accumulation on switch actuators—these can prevent proper actuation even when the gate appears closed.

Check I/O status on teach pendant

From teach pendant: MENU → I/O → Digital → select input type (typically DI or UI). Locate the *FENCE signal or specific fence inputs (common labels: FENCE1, FENCE2, SF_CLOSE). With gates closed, these inputs should show ON (1). If OFF (0), the signal is not reaching the controller.

Most systems use UI[1] *FENCE as the primary safety fence input. Some multi-zone cells use UI[2] through UI[8] for individual zones.

Test gate cycle operation

Open and close each gate individually while monitoring the corresponding I/O signal on the teach pendant. The signal should transition from OFF to ON crisply when the gate fully closes. Sluggish or bouncing transitions indicate switch or wiring problems.

Maintain visual confirmation that the cell is clear when testing gate operations.

Verify fence input configuration

From teach pendant: MENU → I/O → Configuration → select input type. Verify *FENCE or fence zone signals are properly configured. Check MENU → SYSTEM → Config → Fence Config to confirm fence I/O assignments match physical wiring. Note signal numbers and types (UI for Universal Inputs is standard).

On R-30iB controllers with DCS (Dual Check Safety), fence signals may be configured as dual-channel safety inputs requiring two redundant signals.

Check wiring at controller terminal blocks

Power down the controller (MENU → FANUCManual → CONTROLLED START → Abort). Open the cabinet and locate the safety fence input terminals (typically on IOPCB or safety I/O module). Verify tight connections, check for corrosion, broken wires, or damaged insulation. Use drawings to confirm correct terminal assignments.

LOCKOUT/TAGOUT required. Only qualified electrical personnel should access controller internals. High voltage present.

Measure continuity of fence circuit

With power isolated, use a multimeter to check continuity from the safety switch through the wiring harness to the controller terminal. For normally-closed safety switches, you should read near-zero ohms with gate closed, infinite resistance when open. Check both signal and common/return paths.

Many systems use safety relay modules (Pilz, Schmersal, etc.) between switches and robot controller. Test both input and output sides of these modules—relay failures are common after 5+ years.

Test safety switch independently

Disconnect the safety switch from the circuit and test it in isolation with an ohmmeter. Cycle the switch actuator and verify clean contact operation with no intermittent opens. Replace any switch showing erratic behavior or resistance above 1 ohm in closed state.

Modern safety switches often have diagnostic LEDs. Consult switch documentation—these LEDs can indicate switch status, wiring faults, or short circuit conditions.

Identify all configured fence zones

From teach pendant: MENU → SYSTEM → Config → Fence Config. Review the fence configuration to identify how many zones are defined and which I/O signals control each zone. Note whether Single Fence, Dual Zone, or Custom Area Group configuration is active.

Check MENU → SETUP → Payload to see if different payloads/tools have different area group assignments. The active payload determines which fence zones must be closed.

Check all zone fence inputs

Navigate to MENU → I/O → Digital and check the status of all fence-related inputs (UI[1] through UI[8] typically). In multi-zone systems, ALL zones not currently occupied must show closed status. Identify which specific zone input is showing open (OFF state).

Some integrators use custom ladder logic in PMC to combine multiple physical gates into zone-level fence signals. If standard I/O checks don't reveal the issue, examine MENU → I/O → PMC → PMC I/O.

Verify area group and payload settings

Check MENU → SETUP → Payload to confirm the correct tool/payload is selected. Then verify MENU → SYSTEM → Area Group → Current Group matches the expected zone for the current operation. Incorrect payload or area group selection can require closure of unexpected fence zones.

If the robot recently completed a tool change or pallet transfer, the payload may not have updated correctly. Re-teach or manually select the correct payload number.

Review robot program zone requirements

Examine the active robot program for PAYLOAD or Area Group instructions that may switch fence requirements mid-program. Some programs explicitly enable/disable fence zones. Check for custom fence logic in macros or background logic programs.

On R-30iB Plus controllers with enhanced safety features, check MENU → SYSTEM → Safety → Workspace Monitor to see if a software safety zone violation is being reported alongside the fence alarm.