Skip to main content

PLC-Driven Robot Motion with the FANUC PLC Motion Interface

The FANUC PLC Motion Interface is a FANUC robot-controller option that, in FANUC's description, lets a PLC command robot motion directly while the robot controller generates and executes the motion. UTEC Industrial designs, engineers, machines, fabricates, and installs custom material handling systems for aerospace and heavy industry from its Spokane Valley, WA facility, integrating Allen-Bradley PLC and motion control with in-house CNC machining, heat treating, and stress relief. This article sets out what FANUC says the option does, how it differs from computing robot kinematics in the Logix controller itself, which functions stay with the robot controller and the safety system, and what a specification for a heavy-handling cell built this way should state. PLC-driven motion sits at the controls link of the chain, design → engineering → parts machining → fabrication → assembly → weld fatigue → stress relief → drives → controls → tuning → monitoring, where the PLC that sequences the conveyors, cars, and positioners also issues the robot's moves.

What is the FANUC PLC Motion Interface?​

FANUC America describes the PLC Motion Interface as an option that allows robots to be commanded directly from a PLC, bringing robot motion into the same logic environment as the rest of the automation system. According to FANUC's product page, the PLC issues the motion commands with standardized PLCopen function blocks or with PLC add-on instructions (AOIs); the page's detailed section calls them "PLCopen-style" function blocks. The page lists one compatible controller series, the R-30iB Plus.

A 2021 FANUC America article on the option, last updated in 2026, adds three facts:

  • It names the product the "PLC Motion Control Interface", a motion interface between the FANUC robot controller and the Rockwell Automation PLC. This article uses the product page's name.
  • It says FANUC built on its existing technologies with Rockwell Automation and PLCopen standards to develop FANUC add-on instructions for PLC motion control.
  • It dates the option's first introduction to 2018.

Both FANUC pages are product descriptions, not a technical manual. They give no add-on instruction names, handshake bit maps, update times, or payload or model limits, and no public FANUC manual for the option was found for this article. As engineering practice, those details are taken from FANUC's documentation for the specific controller and software release, through the project's FANUC design and engineering partner (FANUC America, PLC Motion Interface and I/O Interface; Dugan B 2021).

Which robot motions can a PLC command through the interface?​

FANUC's product page says the option allows a PLC to command linear, joint, and circular robot motion, manage speeds and termination types, and coordinate robot actions with conveyors, sensors, and other equipment. The page names material handling, pick-and-place, and line-level coordination as the applications it is ideal for; that is FANUC's own statement of fit. The page does not list which PLCopen function blocks are implemented, and this article does not infer them.

The robot coordinate frames those moves are expressed in are covered in the robot track and positioner article.

The rest of this answer is engineering reasoning. A linear move holds the tool point on a straight path in a robot coordinate frame, while a joint move interpolates the joint angles and does not hold a straight tool path. The PLC programmer therefore needs to know which frame every target position is expressed in. A failure mode in a heavy cell is a joint move between two safe points that swings a long part through a fixture or a conveyor guard that the equivalent linear move would have cleared (FANUC America, PLC Motion Interface and I/O Interface).

Who calculates the robot's motion when the PLC issues the command?​

FANUC's two pages split the work this way:

  • Robot controller. The product page says the robot controller automatically generates and executes motion instructions based on the PLC-issued commands.
  • Kinematics. The 2021 article says that even though FANUC manages the kinematics, programs are deployed within the PLC to perform the execution of motion commands.
  • Programming location. The same article says robot motion can be handled by the PLC using FANUC add-on instructions instead of programs developed in the robot controller as teach pendant programs.

The 2021 article also says, in its section on maintenance costs, that all motion control is now handled and executed by the PLC. Read literally, that sentence does not agree with the article's own kinematics sentence or with the product page, and this article does not rely on it.

This article reads the product page and the kinematics sentence together as follows. The PLC program decides which move runs, with which target and speed, and when. The robot controller turns that command into joint motion of the arm.

The next two sentences are engineering reasoning. The arm's dynamic model, path planning, and servo control stay inside the robot controller, even though no teach pendant program sequences the cell. A failure mode is a PLC routine written as if the PLC owned the path, for example one that assumes a commanded stop is instantaneous, when the stopping behavior is the robot controller's (FANUC America, PLC Motion Interface and I/O Interface; Dugan B 2021).

How does the FANUC route differ from robot kinematics in a Logix controller?​

Rockwell Automation documents an architecture in which the Logix controller itself computes the robot's kinematics. Its Motion Coordinate System user manual (MOTION-UM002L, 2025) describes it:

  • Coordinate systems. In the Logix Designer application, a coordinate system is a grouping of one or more primary or ancillary axes created to generate coordinated motion. The supported geometry types are Cartesian, Articulated Dependent, Articulated Independent, SCARA Independent, Delta, and SCARA Delta (p. 14).
  • Six-axis arms. The manual's type table lists Articulated Independent with the J1J2J3J4J5J6 transform definition, a transform dimension of 6 (p. 47). The six joint axes are either programmed directly in joint space with Motion Axis Move (MAM) instructions or controlled automatically by the Kinematics instructions, programmed in a Cartesian coordinate system (p. 82).
  • Instructions. Motion Coordinated Linear Move (MCLM) initiates a linear coordinated move within a Cartesian coordinate system, Motion Coordinated Circular Move (MCCM) a two- or three-dimensional circular move, and Motion Coordinated Transform (MCT) starts a transform that links two coordinate systems together (p. 11).
  • Commissioning. The procedure starts with the angle values from the robot manufacturer for joints J1 to J6 at the calibration position, the manufacturer's data on gearboxes, and axis scaling so that one revolution equals 360° (p. 84).

The next two sentences are engineering reasoning, not a statement by either manufacturer. In the Logix route the PLC project carries the arm's link lengths, offsets, and joint axes and drives them through its own motion system. In the FANUC route, as FANUC describes it, the robot controller keeps the arm model and the PLC sends commands. The Rockwell manual does not mention FANUC, and neither document compares the two routes (Rockwell Automation MOTION-UM002L-EN-P, pp. 11, 14, 47, 82 and 84; FANUC America, PLC Motion Interface and I/O Interface).

What does Logix-native kinematics add to the PLC's own workload?​

Rockwell Automation's design-considerations manual sets out how the motion planner shares a Logix controller with the user tasks:

  • Tasks. Controller tasks can be configured as either continuous, periodic, or event (Ch. 5 p. 39).
  • Motion planner priority. The motion planner interrupts all other tasks, regardless of their priority (Ch. 5 p. 42).
  • What sets its load. The number of axes and the coarse update period for the motion group affect how long and how often the motion planner executes (Ch. 5 p. 42).
  • Effect on other tasks. If the motion planner is executing when a task is triggered, the task waits until the motion planner is done (Ch. 5 p. 42).

The coordinate-system manual adds a controller condition. Its footnote limits the MCTO, MCTPO, and MCPM instructions to certain 5380- and 5580-series controller families that it lists, and states that MCT and MCTP cannot be used with SoftLogix controllers (MOTION-UM002L, p. 11).

The rest of this answer is engineering reasoning. Six robot joints, plus a track or positioner axis, in the PLC's motion group lengthen the motion planner's work in every coarse update, and the cell's periodic interlock task waits behind it. Where the robot controller generates the motion, as FANUC describes for the PLC Motion Interface, the robot's joints are not axes that the PLC's motion planner updates; the PLC's load is the command and status exchange. The controller family and the motion group's update period belong in the controls design review, not in commissioning (Rockwell Automation 1756-RM094N-EN-P-2025, Ch. 5 pp. 39 and 42; Rockwell Automation MOTION-UM002L-EN-P, p. 11).

How are motion commands and status passed between the PLC and the robot?​

FANUC's product page says motion commands are transferred through a cyclic I/O handshake that gives status feedback. Neither FANUC page names the network that the Rockwell version uses. The 2021 FANUC article says that demand led to the PLC I/O Motion Interface, which allows PLCs other than Rockwell Automation PLCs to be interfaced, including over PROFINET and EtherCAT.

The connection itself is covered in Connecting a FANUC Robot to an Allen-Bradley PLC over EtherNet/IP, which sets out the adapter registration, the requested packet interval, input buffering, and the command-and-acknowledge handshake rules for a FANUC robot on an Allen-Bradley PLC.

The rest of this answer is engineering reasoning, except the Rockwell statement in the third bullet. Motion commands that ride on cyclic I/O are subject to the same timing as any other cyclic data, and the same handshake rules apply to them:

  • Hold until acknowledged. A move command issued as a one-scan pulse can fall between two I/O updates and never reach the robot.
  • Confirm completion from status. The PLC treats a move as done only when the robot's status says so, not when a timer expires.
  • Run the command logic at a fixed period. Rockwell's manual says a periodic task performs a function at a specific time interval (Ch. 5 p. 41), which gives the command and status logic a known update rate to match to the I/O interval.

A failure mode is a cell that commands the next pick before the robot reports the previous place complete, which on a heavy part can mean releasing the gripper over the wrong station (FANUC America, PLC Motion Interface and I/O Interface; Dugan B 2021; Rockwell Automation 1756-RM094N-EN-P-2025, Ch. 5 p. 41).

What does the PLC programmer still need to know about the robot?​

FANUC's 2021 article says the option lets controls engineers develop programs in ladder logic to execute robot motion without creating the teach pendant programs that, in FANUC's words, are typically required for FANUC robot controllers. That is FANUC's description of where the motion program is written. Its broader claims, for example that robot programming knowledge is no longer necessary, are marketing statements, and this article does not treat them as facts.

Even the Logix-native route depends on robot data. Rockwell's commissioning procedure starts from the robot manufacturer's joint angles at the calibration position and the manufacturer's gearbox data (MOTION-UM002L, p. 84).

As engineering reasoning, moving the motion program into the PLC does not move the robot's own setup into the PLC, and someone on the project still has to own it. The robot controller still needs:

  • correct payload and tool data;
  • tool and user frames;
  • calibration;
  • its safety configuration.

For a heavy load, the payload data comes from the sizing work described in Sizing an Industrial Robot: Payload, Reach, Wrist Moment, and Inertia. As engineering reasoning, a failure mode is a cell commissioned with the payload set for the empty gripper, which then carries its heaviest part under the wrong load data. UTEC Industrial integrates FANUC robotic cells, including vision, with a FANUC design and engineering partner (Dugan B 2021; Rockwell Automation MOTION-UM002L-EN-P, p. 84).

What controls and sensing does a PLC-driven heavy-handling cell need?​

FANUC's product page says the option lets the PLC coordinate robot actions with conveyors, sensors, and other equipment. The layers below are engineering practice, except where a bullet names the Rockwell manual:

  • Position feedback on the handling axes. Encoders on transfer cars, positioners, and conveyors confirm that the part is where the robot's next target expects it.
  • Load confirmation. A load cell confirms the weight actually picked before the PLC commands a fast move with it.
  • Part presence and pose. Proximity or photoelectric sensors confirm presence. Where parts vary, machine vision supplies the pose that becomes the robot's target.
  • Drives. VFD and servo drives on the conveyors, cars, and positioners run under the same PLC, so their ramps and the robot's moves come from one sequence.
  • Task structure. Logix 5000 controller tasks can be configured as continuous, periodic, or event (Ch. 5 p. 39), and a periodic task performs a function at a specific time interval (Ch. 5 p. 41); the practice here is to run the permissive checks in a periodic task ahead of each motion command.

As engineering reasoning, the benefit of PLC-driven motion in this setting is that the permissive and the move command sit in the same program, so a missing encoder confirmation blocks the move directly; the risk is that a sensor fault the PLC ignores is now a robot motion fault too. UTEC Industrial, a Rockwell Automation Recognized System Integrator, builds Allen-Bradley ControlLogix and CompactLogix controls with VFD and servo drives over EtherNet/IP for the handling systems it delivers (FANUC America, PLC Motion Interface and I/O Interface; Rockwell Automation 1756-RM094N-EN-P-2025, Ch. 5 pp. 39 and 41).

Which safety functions stay outside the PLC's motion commands?​

As engineering reasoning, a motion command is a standard control signal, not a safety function, whichever controller computes the motion. The robot standards, the safety-control standard, and the Logix manual bear on that line:

  • Robot and cell standards. ISO 10218-1:2025 covers the robot and ISO 10218-2:2025 the robot application and cell, and ANSI/A3 R15.06-2025 adopts both in the United States; their scopes are set out at standard level in the robot track and positioner article.
  • Safety-related controls. ISO 13849-1:2023 specifies a methodology and provides related requirements, recommendations, and guidance for the design and integration of safety-related parts of control systems that perform safety functions. It applies to those parts for high demand and continuous modes of operation and does not apply to low demand mode of operation.
  • Travel limits in the Logix route. Rockwell's manual warns that, before the transform is turned on or the reference frame is established for an Articulated Independent six-axis robot, the soft travel limits must be set and enabled and the hard travel limits enabled for the joints of the target coordinate system. Failure to do this can allow the robot to move outside the work envelope, causing machine damage and/or serious injury or death to personnel (MOTION-UM002L, p. 81).

Neither FANUC page describes the safety functions of a cell that uses the PLC Motion Interface. As engineering reasoning, the emergency stop, guard interlocks, and any safety-rated speed or zone limits stay on hard-wired safety circuits or CIP Safety connections, separate from the cyclic motion handshake. The connection article linked above covers that split.

As engineering reasoning, stopping the robot from the PLC is not isolation either. OSHA 29 CFR 1910.147 covers the servicing and maintenance of machines and equipment in which the unexpected energization or start up of the machines or equipment, or release of stored energy, could cause injury to employees; paragraph (a)(1)(ii) lists the employment the standard does not cover, and paragraph (a)(2)(ii) limits when servicing during normal production operations is covered. In its definition of an energy isolating device, the standard states that push buttons, selector switches, and other control circuit type devices are not energy isolating devices (ISO 10218-1:2025; ISO 10218-2:2025; ANSI/A3 R15.06-2025; ISO 13849-1:2023; Rockwell Automation MOTION-UM002L-EN-P, p. 81; OSHA 29 CFR 1910.147-1989).

Where does PLC-driven robot motion sit in the build chain?​

The bullets below are engineering reasoning, except the Rockwell commissioning statement in the Tuning bullet. The choice of who owns robot motion is made at the design link and shows up at every link after it:

  • Design and engineering. The decision between a teach pendant program with a PLC handshake, the FANUC PLC Motion Interface, and Logix-native kinematics sets which team writes the motion, which controller carries the load, and which documents the cell needs.
  • Machining, fabrication, and stress relief. The robot's riser or base, a track, and the fixtures it serves are welded and machined structures. Distortion after machining moves the points that the PLC's targets assume; stress relief before final machining is covered in Stress Relief for Machine Bases and Frames Before Final Machining.
  • Drives and controls. The handling axes' drives and the robot's motion commands share one PLC sequence.
  • Tuning. In the Logix route, commissioning starts from the robot manufacturer's calibration angles and axis scaling (MOTION-UM002L, p. 84). In the FANUC route, the robot's own setup stays with the robot controller.
  • Monitoring. Trending command-to-complete times, handshake timeouts, and robot fault codes in the PLC shows drift before a missed hand-off stops the line.

UTEC Industrial carries out factory acceptance testing (FAT) and on-site commissioning; as engineering reasoning, those are the two points at which the motion ownership chosen at design is proved under load. The FANUC article dates the option's first introduction to 2018. As engineering reasoning, the software release and the support arrangement are worth confirming with the FANUC design and engineering partner before design freeze (Rockwell Automation MOTION-UM002L-EN-P, p. 84; Dugan B 2021).

What should a specification state when the PLC will command the robot?​

As engineering practice, a request for quotation that says only "PLC-controlled robot" can be read three ways, so the specification states:

  • Motion ownership. Which route applies: a teach pendant program with a PLC handshake, the FANUC PLC Motion Interface, or Logix-native kinematics.
  • Controller and option. The robot controller series, which FANUC's product page gives as R-30iB Plus for the PLC Motion Interface, and the software option and release.
  • PLC platform and network. The PLC family, and the network the motion handshake will use. FANUC's 2021 article names the Rockwell version and, for other PLCs, the PLC I/O Motion Interface with PROFINET and EtherCAT among the networks.
  • Motion types. The motion types the PLC will command, from the linear, joint, and circular moves FANUC lists, and the speed and termination settings each move uses.
  • Handshake map. The command, acknowledge, complete, and fault bits and registers, signed off by the robot and PLC teams.
  • Safety split. Which signals are safety signals, carried outside the motion handshake, and who owns the risk assessment for each interface.
  • Logix route only. The controller family, checked against the instruction availability the Rockwell manual lists, and the soft and hard travel limits required before the transform is enabled.
  • Ownership after handover. Who maintains the PLC motion routines, and who maintains the robot's payload, frame, and calibration data.

With those items stated, two bids for the same cell can be compared on the same motion architecture rather than on how each bidder read "PLC-controlled" (FANUC America, PLC Motion Interface and I/O Interface; Dugan B 2021; Rockwell Automation MOTION-UM002L-EN-P, pp. 11 and 81).

Related Articles

References​

  • FANUC America. PLC Motion Interface and I/O Interface. FANUC America Corporation (undated web documentation, accessed September 2026).
  • Dugan B. Why Controls Engineers Should Command Robots from the PLC. FANUC America Corporation, 2021 (updated 2026).
  • Rockwell Automation MOTION-UM002L-EN-P: Motion Coordinate System (User Manual). Rockwell Automation, 2025.
  • Rockwell Automation 1756-RM094N-EN-P-2025: Logix 5000 Controllers Design Considerations. Rockwell Automation, 2025.
  • ISO 10218-1:2025: Robotics — Safety requirements — Part 1: Industrial robots. ISO, 2025.
  • ISO 10218-2:2025: Robotics — Safety requirements — Part 2: Industrial robot applications and robot cells. ISO, 2025.
  • ANSI/A3 R15.06-2025: American National Standard for Industrial Robots and Robot Systems – Safety Requirements. A3/ANSI, 2025.
  • ISO 13849-1:2023: Safety of machinery — Safety-related parts of control systems — Part 1: General principles for design. International Organization for Standardization, 2023.
  • OSHA 29 CFR 1910.147-1989: The Control of Hazardous Energy (Lockout/Tagout). Occupational Safety and Health Administration, 1989.

Ready to Discuss a Material Handling System?​

UTEC Industrial designs, engineers, machines, fabricates, and installs custom material handling systems for heavy industry, from the stress-relieved structure and drives to the Allen-Bradley PLC controls, tuning, and monitoring that run them, at its Spokane Valley, WA facility. Send UTEC the application, loads, and duty cycle to start a system review.

Request a Quote →

Questions? Call (509) 922-1832 or email sales@utec.co

Last updated on