Troubleshooting FANUC Teach Pendant Menu Lockout Guide

The FANUC teach pendant powers up and runs the cell, but Utilities and other submenu items are missing or unavailable. You also cannot identify which DO commands the end-of-arm-tooling grippers because the DI and DO points have no useful labels.

Start here: stop treating this as a bad pendant. A restricted account or password-protection configuration can hide menus and block program or I/O changes while leaving normal production operation available.

Stop Trying the Wrong Fixes

Random navigation, mode changes, and signal forcing create risk without restoring access. Use the displayed symptom to separate permissions from hardware trouble.

Changing Auto status is therefore not the first diagnostic. First determine whether the controller is rejecting modification or presenting a reduced menu set.

Identify the Access Restriction

Attempt a non-destructive action that normally requires edit authority, such as opening an existing program for modification without saving a change. Record the exact message displayed by the pendant.

A message requesting a password, denying access, or reporting insufficient authority directs you toward password protection or the configured user role. Missing Utilities and other administrative items reinforce that diagnosis. If there is no denial message and the menus appear complete, investigate controller configuration and application-specific screen customization instead.

The exact FANUC controller, software revision, installed options, and current access level are not identified here. Menu names and authentication workflow can differ across those combinations. Read the controller identification and installed-option information from screens available to the current account, then use the matching FANUC documentation or official support channel.

Do not attempt to bypass password protection. The restriction may protect safety-related settings, production programs, calibration data, communication settings, and cell-specific recovery procedures. Obtain an authorized account or have the company responsible for the robot application perform the access change.

Separate Inputs from Outputs

DI and DO are not interchangeable diagnostic controls. A digital input normally reports a state coming into the robot controller. You observe it while actuating the associated field device; you do not ordinarily command it from the robot as if it were an output.

A digital output is commanded by the robot controller, but manual control depends on permissions, operating state, application logic, and the output path. A displayed DO may feed an interface rather than a valve directly. Interlocks outside the robot can also prevent physical motion even when the displayed output changes.

For a pneumatic gripper, trace both command and feedback. The command side may include separate open and close outputs, while the input side may report open, closed, part-present, pressure, or permissive states. Those are common architectures, not confirmed signal assignments for this installation. Wire tracing, electrical drawings, valve-manifold indicators, and controlled observations decide the mapping.

Map the Gripper Signals Safely

1. Place the cell under the approved maintenance control procedure. Prevent automatic production logic and external equipment from initiating motion.
2. Confirm that no person can be trapped, pinched, or struck by the robot, tooling, gripper, or handled part. Remove or secure stored pneumatic, hydraulic, mechanical, and gravitational energy as required by the task.
3. Obtain authorized pendant access. If the current account cannot view the required I/O screens or modify outputs, stop here rather than guessing credentials.
4. Review the robot program without editing it. Search for DO references near gripper-open, gripper-close, pick, place, clamp, release, or tool routines. Application names may differ.
5. Compare those references with the electrical schematic and valve-manifold wiring. Follow each controller output through any network adapter, remote I/O rack, relay, or interface device to the solenoid channel.
6. Observe DI states while manually operating an accessible sensor target or gripper mechanism under the approved maintenance procedure. Record which points change and whether the change matches the physical state.
7. Only after tracing the circuit, command one identified output using the controller's authorized manual-I/O method. Keep automatic application logic inactive so it cannot immediately rewrite the signal.
8. Apply a meaningful description to each confirmed point if your authorization and site change-control process permit it. Back up the controller before saving configuration or program changes.

Use one controlled change at a time. If an output changes on the screen but the solenoid does not, continue downstream through the I/O adapter, field power, interposing devices, wiring, and valve. That is an electrical or interface-path problem, not a pendant-menu problem.

Choose the Correct Operating State

Do not manually toggle tooling outputs while the cell is running in Auto. Automatic logic may command the same point, the robot may move in response to the tooling state, and other machines may treat that state as permission to continue.

Use the operating state defined by the cell risk assessment and maintenance procedure. Mode selection alone does not make the action safe: external controllers, remote I/O, stored energy, and hardwired circuits may remain active. Establish control of the whole cell before manipulating a signal.

If production logic must run to diagnose the sequence, monitor DI and DO states without forcing them. Correlate signal transitions with program execution, valve indicators, sensor indicators, and physical motion. Reserve manual output commands for a controlled test with known consequences.

Verify the Repair and Preserve Recovery

1. Log in with the authorized access level and confirm the expected Utilities and I/O functions are visible.
2. Verify that ordinary production users still have the intended restrictions. Do not leave an elevated session active at the cell.
3. Test each mapped gripper command individually in the approved maintenance state. Confirm the physical action matches the commanded DO.
4. Confirm each associated DI changes only when its physical condition is true. A gripper command is not proof that the mechanism reached position.
5. Return all forced or manually commanded points to application control before resuming automatic operation.
6. Run the normal application sequence at the site's approved reduced-risk test condition, then confirm open, close, permissive, and fault behavior.
7. Create a fresh backup and update the electrical drawings or I/O list with every verified assignment.

A successful test proves three separate paths: the controller issues the command, the actuator performs the motion, and independent feedback reports the result. If any one of those fails, diagnose that path instead of changing password settings again.

FAQ