Nothing to install on the robot
No TP program to write, no Karel, no PCDK or Robot Interface on the PC. The controller only needs the option R912 Remote Motion Interface. It also works with a ROBOGUIDE virtual robot.
Remote Motion Interface, from C# or Python
The Remote Motion Interface (RMI) of Fanuc controllers lets a PC send motions to the robot over Ethernet. The UnderAutomation Fanuc SDK speaks RMI for you: a few lines of code connect to the controller, queue joint and linear motions, wait for inputs, write outputs and follow each instruction while the robot runs. This page is a complete application built with it. Its source code is on GitHub.
Get the Fanuc SDK, free for 30 days Read the RMI documentation
No TP program to write, no Karel, no PCDK or Robot Interface on the PC. The controller only needs the option R912 Remote Motion Interface. It also works with a ROBOGUIDE virtual robot.
Palletizing with a pattern computed on the fly, pick and place guided by a camera, machine tending driven by an MES: the targets come from your software, not from taught points.
One .NET library and one pip package. Linear, joint, circular and spline motions, FINE and CNT terminations, frames, I/O, registers and payload.
The option R912 (Remote Motion Interface), the controller in AUTO mode with the teach pendant disabled, and an Ethernet link to the PC on TCP port 16001.
Yes. Without a backend, this page drives a simulated robot. With a backend, it also connects to a ROBOGUIDE virtual robot.
The page, the .NET backend and the Python backend are on GitHub. The SDK they use runs 30 days without a license key.
RMI when the controller plans a few motions that you send, like in a TP program. Stream Motion (option J519) when your PC gives the position at every cycle. The SDK does both.