Configuring Fanuc DCS Work Zones for Robot Cell Safety

Overview

When a Fanuc robot is installed before its perimeter guarding is completed, the integrator must still prevent the manipulator from reaching the physical envelope of the cell wall, light curtain, fence post, or other fixed structure. Relying on path accuracy alone is not acceptable because any single point of teach, a TCP offset change, or a payload mismatch can push an axis into the wall. The correct engineering approach on a Fanuc R-30iB / R-30iB Plus / R-30iB Mate Plus controller is to combine World Zones (software-only, non-safety envelopes used for motion planning and indication) with Dual Check Safety (DCS) (a safety-rated, hardware-redundant position and speed checking function that hard-stops the robot if a defined Cartesian or joint limit is violated).

This article documents the proper procedure for defining a restricted work envelope around a robot cell using DCS Cartesian Position Check, validating it with World Zones, and verifying the safety function through the controller's built-in stop test. It applies to cells where the robot must never physically reach the wall, regardless of program, override, or teach pendant manipulation.

Prerequisites

• Fanuc R-30iB, R-30iB Plus, R-30iB Mate Plus, or R-30iB Mini Plus controller running V8.x or V9.x system software (DCS feature availability varies by option).
• Ordered software option A05B-2600-J924 DCS Position/Speed Check Software (or equivalent for the controller variant). Confirm the option is loaded via MENU > 0 NEXT > 4 STATUS > Version ID and the DCS menu is visible at MENU > 0 NEXT > 6 DCS.
• Robot serial number, model (e.g., M-20iA/20M, R-2000iC/210F, LR Mate 200iD), and current mastering data. Mastering must be performed and the $DMR_GRP[1].$MASTER_DONE flag must be TRUE before commissioning DCS limits.
• Mechanical layout drawing of the cell, including wall material (polycarbonate, steel mesh, brick), wall thickness, and the closest stand-off distance from the robot base flange face to the inside face of the wall.
• Risk assessment per ISO 10218-1:2011 and ISO 10218-2:2011 (industrial robot safety requirements) and ISO 13849-1:2023 for safety-related control system performance level (PL d minimum for stop functions, PL d/cat 3 typical for cell protection).
• Pendant with the DCS password (default is set by the installer) and a written authorization to modify safety-rated parameters.

Safety Architecture: DCS vs. World Zones

These two functions look similar but must not be confused:

The recommended engineering practice is to set up DCS Cartesian Position Check as the primary safety function and use a matching World Zone for the following reasons: the World Zone triggers a programmable output that can be used for indicator lamps, the World Zone fails visible to the operator in dry-run/test mode, and the World Zone gives a non-safety reference for the DCS commissioning step (so you can verify the envelope numerically before turning on the safety function).

Step 1: Define the Restricted Envelope

From the cell layout, calculate the envelope to be protected:

1. Identify the inside face of each wall (X+, X-, Y+, Y-, Z+ directions relative to the robot base frame).
2. Subtract a safety margin equal to the robot's worst-case stopping distance at 100 % override plus a minimum of 50 mm stand-off. The stop distance can be read after commissioning with the DCS stop test; until measured, a conservative value of 250 mm is typical for a 20 kg payload robot at full speed.
3. Record the limit coordinates in the robot's World Frame (UF:0, UT:0). The robot's user frame can also be used but World Frame is preferred for cell safety because it is anchored to the base mounting surface and is not affected by frame offsets.

For a square cell at 2.5 m × 2.5 m around the base of a Fanuc M-20iA, a typical DCS cube might be set to X: ±1200 mm, Y: ±1200 mm, Z: +1500 mm (downward is negative), giving 50 mm of stand-off to a 2.5 m wall.

Step 2: Configure a Non-Safety Reference World Zone

On the teach pendant:

1. Press MENU > SETUP > F1 [Type] > World Zone.
2. Select an empty zone slot (1-8) and set the following:

3. Enter the values and press F4 DONE. The zone is now active in the user's program context but not yet safety-rated.
4. Run a known-good program with the robot in teach mode and verify the zone triggers by jogging the TCP to within 50 mm of the wall boundary. The pendant should display the World Zone violation message and DO[200] should energize.

Step 3: Enable DCS Cartesian Position Check

1. Press MENU > 0 NEXT > 6 DCS. The DCS Top Menu appears.
2. Select 3 Position/Speed Check.
3. Choose an empty zone number (1-8) and select 1 Cartesian position check.
4. Enter the same envelope as the World Zone. The DCS screen displays six numerical fields (X min, X max, Y min, Y max, Z min, Z max) keyed to the World Frame.
5. Set the Stop Category to Category 1 (controlled stop, controlled by robot, then servo power removed) for the cell wall protection. Use Category 0 (immediate servo power removal) only when the application requires a hard stop and a risk assessment confirms no loss of gripper or clamping hazard.
6. Set the Reset Method to Manual. The DCS zone will not auto-reset when the TCP exits the prohibited region; the operator must press the RESET key. This prevents the robot from re-entering the area on power-on without explicit acknowledgement.
7. Set the Alarm Output to a DCS-specific DO, for example DO[201] mapped to PR[1] for an external stack light.

Step 4: Save and Cycle Power

DCS configuration is only committed to the safety MCU's non-volatile memory on a controlled save sequence. From the DCS menu:

1. Press F4 [DONE].
2. Press F5 [SAVE]. The pendant prompts for the DCS password.
3. Enter the password and press ENTER. The screen shows Saving DCS data, please wait....
4. When prompted, cycle E-Stop and then controller power. DCS data is verified at power-up; a checksum mismatch will trigger a SYST-035 alarm and the robot will not enable motion.

Step 5: Validate the Safety Function (Mandatory)

Per ISO 10218-2 §6.4, the safety-rated function must be tested at commissioning and re-tested at defined intervals (typically every 12 months or after any mechanical change). Use the following procedure for the cell wall DCS zone:

1. Jog the robot in 100 % teach mode to a position 100 mm inside the prohibited region. The pendant should immediately display MOTN-023 DCS Cartesian position limit exceeded and the robot should enter a controlled stop.
2. Verify the stop category by recording the time from violation to servo-off. Category 1 should be 200-800 ms depending on speed.
3. Repeat the test from at least four approach directions: +X, -X, +Y, -Y. Z+ and Z- are typically bounded by joint limits but should be tested if the wall has overhead structure.
4. Confirm the violation occurs before any axis reaches the physical wall. Use a dial indicator or laser distance sensor on the TCP and a witness mark on the wall to confirm physical stand-off remains after every test.
5. Document the test results in the safety validation report, signed by the integrator and the end-user safety officer. Required by ISO 13849-1 §4.7 validation.

Step 6: Programmatic Use of World Zones Inside a Job

Even with the safety-rated DCS zone in place, you can add a World Zone to the TP program to give operators a visual/audible cue when nearing the wall. The following KAREL/TP snippet disables a software zone during a home routine and re-enables it on entry to the production cycle:

!TP program CELL_SETUP
!Disable World Zone 1 during homing
WZ_DISABLE[1] ;
!Move to home position
J PR[10:HOME] 100% FINE ;
!Re-enable for production
WZ_ENABLE[1] ;
!Production routine
CALL PROG_1 ;

Note that WZ_DISABLE affects only the World Zone; the DCS Cartesian Position Check remains active in all modes. This asymmetric behavior is intentional and is the reason DCS is the only acceptable primary protection for the cell wall.

Step 7: Diagnostic Monitoring

The following signals are useful on the HMI or in a condition monitor:

Map these to your HMI tags (Pro-face, PanelView, WinCC, or FactoryTalk View) and trend the trip count. A rising trend indicates either a poor path program or a creeping mechanical issue and should trigger a maintenance review.

Troubleshooting Matrix

Maintenance and Periodic Test

Schedule a re-test of the DCS Cartesian Position Check at intervals defined by the application risk assessment, with a maximum of 12 months. After any of the following events, re-validate:

• Replacement of any motor, reducer, or absolute encoder.
• Mechanical change to the robot mounting plate, end-of-arm tool, or workpiece fixture.
• Update to controller software (V8 → V9, etc.).
• Any collision event, even one recovered by DCS.

Maintain a logbook of test results, including date, tester name, robot position at the time of the trip, the measured physical stand-off, and the time from trip to servo-off. The logbook is the audit trail required by ISO 13849-1.

Interaction with Other Cell Safety

DCS work zones do not replace other safeguards required by ISO 10218-2:

• Safety-rated reduced speed via DCS Joint Speed Check for teach mode at 250 mm/s.
• Safety-rated stop via E-Stop circuit and DCS Stop Position, redundant to the E-Stop hardware.
• Enabling device on the teach pendant.
• Area scanners for presence detection when an operator enters.
• Lockable main disconnect for maintenance lockout/tagout.

Combine the DCS Cartesian Position Check with these functions in a layered safety design. The cell wall DCS zone is the last line of defense against a programming or mechanical error; it is not a substitute for physical guarding and presence-sensing devices.