I/O Board

The I/O board is the controller's discrete link to the rest of the cell. Grippers, part-present sensors, air valves, PLC handshake lines, light-curtain resets. It plugs into a backplane slot or into a remote rack near the tooling and gives the robot program a bank of digital inputs and outputs mapped to physical points.

Point counts and voltage ranges vary by option. FANUC ships boards in 8, 16, 32, and 64-point flavors; some are all sourcing outputs, some sinking, some rated for 24 VDC only, others for 24V and small 120 VAC through a relay module. Mixing sinking and sourcing wiring by accident is the top cause of a whole point group going dark.

Trouble shows up as individual points that stop responding, sometimes with an audible click from an on-board relay giving up, sometimes as a whole group going dark when a shared fuse pops. Group fuses on the output side are usually socketed on the board itself; check them before assuming the silicon has failed.

Selection means matching model number to option, and matching the terminal block style to the existing field wiring. A board with the wrong connector style will bolt in but leave you re-terminating 32 wires in the field.

Confirm both the FANUC option code and the physical connector style (Phoenix versus FANUC crimp) before ordering. Getting the connector family wrong is the most expensive mistake in an otherwise routine swap.

Compatibility notes: the controller registers each I/O board's slot number and point range on power-up. Adding a board without configuring the I/O rack, slot, and start point in the pendant will show it as missing and log an INTP fault when a program tries to reference a point on it. Configuring the rack is a routine setup step that happens before the board serves any signals.

Troubleshooting: with power off, ring out the field wiring first, then power up and toggle each output from the pendant's I/O screen while measuring at the terminal. Inputs are tested by shorting the point to common and watching the pendant screen. A point that reads correctly at the board but not at the field device is a wiring or fuse issue, and stops at the terminal block.

Practical example: a cell that lost its whole 'gripper closed' input group after a lightning storm turned out to have a blown 250 mA input group fuse. The board itself was fine once the fuse was replaced and the surge path (an unshielded run through a metal conduit next to a welding cable) was cleaned up.