--- title: FANUC industrial robots and CRX cobots · Tallyfy Pro description: Tallyfy has no integration or partnership with FANUC. This concept page covers the industrial robots and CRX cobots FANUC sells, what its ROS 2 driver, MQTT, OPC UA and Python let outside software ask of a robot, and where a written Tallyfy procedure could track the work people do around it. lastUpdated: 2026-10-14T00:00:00.000Z source_url: html: https://tallyfy.com/products/pro/integrations/robotics/fanuc/ md: https://tallyfy.com/products/pro/integrations/robotics/fanuc/index.md --- Concept only Tallyfy has no integration or partnership with FANUC. This page is a concept and not a product. Vendor facts link to their source, read in October 2026. ## How a FANUC robot could start a Tallyfy procedure FANUC makes industrial robots and counts [more than 1 million installed worldwide ↗](https://www.fanucamerica.com/)[\[1\]](https://www.fanucamerica.com/). It also [publishes a driver ↗](https://www.fanucamerica.com/solutions/physical-ai/ros-2-driver)[\[2\]](https://www.fanucamerica.com/solutions/physical-ai/ros-2-driver) that lets other software control a robot. So when a robot stops with an error, your own software could start a written procedure in Tallyfy, with an owner and a deadline for each step. Tallyfy doesn’t sell that connection. Your team or your integrator would have to build it. ## What FANUC makes today As of October 2026: * **Cobots.** These are robots made to work alongside people. FANUC’s cobots, which include the CRX series, [carry from 3 kg to 50 kg ↗](https://www.fanucamerica.com/products/series/collaborative)[\[3\]](https://www.fanucamerica.com/products/series/collaborative). FANUC said in April 2026 that the 3 kg CRX-3iA was [available for customer order ↗](https://www.fanucamerica.com/press-releases/fanuc-america-debuts-ultra-lightweight-crx-3ia-collaborative-robot-and-new-capabilities-across-the-crx-lineup)[\[4\]](https://www.fanucamerica.com/press-releases/fanuc-america-debuts-ultra-lightweight-crx-3ia-collaborative-robot-and-new-capabilities-across-the-crx-lineup). * **Controllers.** A controller is the box that runs a robot’s programs. The CRX-10iA cobot [lists the R-30iB Plus ↗](https://www.fanucamerica.com/products/robot/crx-10ia)[\[5\]](https://www.fanucamerica.com/products/robot/crx-10ia) as its controller. FANUC calls the [R-50iA its new controller ↗](https://www.fanucamerica.com/products/controller-series/r-50ia)[\[6\]](https://www.fanucamerica.com/products/controller-series/r-50ia), and says the CRX line [will also be available on it ↗](https://www.fanucamerica.com/press-releases/fanuc-america-debuts-ultra-lightweight-crx-3ia-collaborative-robot-and-new-capabilities-across-the-crx-lineup)[\[7\]](https://www.fanucamerica.com/press-releases/fanuc-america-debuts-ultra-lightweight-crx-3ia-collaborative-robot-and-new-capabilities-across-the-crx-lineup). * **Integrators.** FANUC’s [authorized system integrators ↗](https://www.fanucamerica.com/products/series/collaborative)[\[8\]](https://www.fanucamerica.com/products/series/collaborative) design, build and support custom robot systems. ## What outside software can ask a robot to do FANUC’s driver is for ROS 2[1](#user-content-fn-1). FANUC says it’s [available now ↗](https://www.fanucamerica.com/solutions/physical-ai/ros-2-driver)[\[9\]](https://www.fanucamerica.com/solutions/physical-ai/ros-2-driver) for the CRX series and several other models, and the [source code is public ↗](https://github.com/FANUC-CORPORATION/fanuc_driver)[\[10\]](https://github.com/FANUC-CORPORATION/fanuc_driver). As of October 2026, a program using the driver can: * [Read the robot’s status ↗](https://fanuc-corporation.github.io/fanuc_driver_doc/main/docs/fanuc_driver/controller_usage.html)[\[11\]](https://fanuc-corporation.github.io/fanuc_driver_doc/main/docs/fanuc_driver/controller_usage.html), such as whether it’s in error, stopped by an emergency stop, or moving. * Read [up to 5 active error messages ↗](https://fanuc-corporation.github.io/fanuc_driver_doc/main/docs/fanuc_driver/controller_usage.html)[\[12\]](https://fanuc-corporation.github.io/fanuc_driver_doc/main/docs/fanuc_driver/controller_usage.html). * [Read and set input and output signals ↗](https://fanuc-corporation.github.io/fanuc_driver_doc/main/docs/fanuc_driver/controller_usage.html)[\[13\]](https://fanuc-corporation.github.io/fanuc_driver_doc/main/docs/fanuc_driver/controller_usage.html), along with the number registers a robot program reads. * [Send motion instructions ↗](https://fanuc-corporation.github.io/fanuc_driver_doc/main/docs/fanuc_driver/controller_usage.html)[\[14\]](https://fanuc-corporation.github.io/fanuc_driver_doc/main/docs/fanuc_driver/controller_usage.html), or call a program that’s already on the robot. * See whether the program built from those instructions is [running, paused or aborted ↗](https://fanuc-corporation.github.io/fanuc_driver_doc/main/docs/fanuc_driver/controller_usage.html)[\[15\]](https://fanuc-corporation.github.io/fanuc_driver_doc/main/docs/fanuc_driver/controller_usage.html). * [Pass motion control back ↗](https://fanuc-corporation.github.io/fanuc_driver_doc/main/docs/fanuc_driver/motion_control_authority.html)[\[16\]](https://fanuc-corporation.github.io/fanuc_driver_doc/main/docs/fanuc_driver/motion_control_authority.html) to the robot’s own programs, then take it again. FANUC documents three other routes: * **MQTT** is a standard for passing short messages between machines. With FANUC’s MQTT option, the robot [connects to a message broker ↗](https://www.fanucamerica.com/products/software/robot/mqtt)[\[17\]](https://www.fanucamerica.com/products/software/robot/mqtt) and publishes, subscribes or both. * **OPC UA** is a standard for sharing factory data. FANUC’s OPC UA Server lets [up to 10 clients ↗](https://www.fanucamerica.com/products/software/robot/hmi-device-snpx)[\[18\]](https://www.fanucamerica.com/products/software/robot/hmi-device-snpx) on the same network read, write and subscribe to robot information. * **Python** runs [on the R-50iA controller itself ↗](https://www.fanucamerica.com/solutions/physical-ai/fanuc-python-programming)[\[19\]](https://www.fanucamerica.com/solutions/physical-ai/fanuc-python-programming), as a standard feature. FANUC’s page names no other controller. A Python program can use the robot’s signals and register values. With the optional Remote Motion Interface, a Python program can also move the robot. ## What outside software can’t do All four limits are as of October 2026. * The driver’s documented [topics and services ↗](https://fanuc-corporation.github.io/fanuc_driver_doc/main/docs/fanuc_driver/controller_usage.html)[\[20\]](https://fanuc-corporation.github.io/fanuc_driver_doc/main/docs/fanuc_driver/controller_usage.html) include no job or mission call, so your software sends instructions or calls a robot program. * The driver docs describe no webhooks (messages pushed to another system’s web address). It [publishes status on ROS 2 topics ↗](https://fanuc-corporation.github.io/fanuc_driver_doc/main/docs/fanuc_driver/controller_usage.html)[\[21\]](https://fanuc-corporation.github.io/fanuc_driver_doc/main/docs/fanuc_driver/controller_usage.html), and a program has to subscribe to them. * The driver won’t run on every controller. It needs [two controller software options ↗](https://fanuc-corporation.github.io/fanuc_driver_doc/main/docs/environment/system_requirements.html)[\[22\]](https://fanuc-corporation.github.io/fanuc_driver_doc/main/docs/environment/system_requirements.html), Stream Motion and Remote Motion, or a package that includes both. If your controller lacks them, the quick start guide says to [contact FANUC to obtain them ↗](https://fanuc-corporation.github.io/fanuc_driver_doc/main/docs/quick_start/quick_start.html)[\[23\]](https://fanuc-corporation.github.io/fanuc_driver_doc/main/docs/quick_start/quick_start.html). FANUC’s pages list no price for them, so ask. * The command manual isn’t in the driver docs, which [point you to FANUC’s Remote Motion Interface manual ↗](https://fanuc-corporation.github.io/fanuc_driver_doc/main/docs/fanuc_driver/controller_usage.html)[\[24\]](https://fanuc-corporation.github.io/fanuc_driver_doc/main/docs/fanuc_driver/controller_usage.html). ## Where a written procedure in Tallyfy fits A robot can report that it stopped. People still have to find the cause, fix it and sign off. A Tallyfy [template](https://tallyfy.com/products/pro/documenting/templates/) is the written procedure for that work: the steps, who does each one, and by when. As a concept, a small connector your team writes would watch the robot’s status. When the robot reports an error, the connector would call Tallyfy’s API to [launch the matching process](https://tallyfy.com/products/pro/launching/triggers/via-api/) and put the error text into its kick-off form. Tallyfy would then assign the repair and the sign-off to named people. Once the sign-off is complete, a [Tallyfy webhook](https://tallyfy.com/products/pro/integrations/webhooks/) could tell the connector to set a signal that the robot’s own program waits for. You don’t need a connector to begin. A person can type what the robot shows into a Tallyfy [form field](https://tallyfy.com/products/pro/tracking-and-tasks/tasks/what-are-form-fields-in-tallyfy/). Keep safety with the robot’s controller and your own safety review. Tallyfy would only track the work people do. ## For developers (Skip this unless you’re setting up the technical side.) * The [driver repository ↗](https://github.com/FANUC-CORPORATION/fanuc_driver)[\[25\]](https://github.com/FANUC-CORPORATION/fanuc_driver) README says the driver is licensed under Apache-2.0, with four bundled libraries under BSD or MIT licenses. The [Apache-2.0 text ↗](https://github.com/FANUC-CORPORATION/fanuc_driver/blob/main/LICENSES/Apache-2.0.txt)[\[26\]](https://github.com/FANUC-CORPORATION/fanuc_driver/blob/main/LICENSES/Apache-2.0.txt) sits in its `LICENSES` folder. As of October 2026, the [newest releases ↗](https://github.com/FANUC-CORPORATION/fanuc_driver/releases)[\[27\]](https://github.com/FANUC-CORPORATION/fanuc_driver/releases) are v2.4.0 and v1.6.0, both dated October 1, 2026. * The [system requirements ↗](https://fanuc-corporation.github.io/fanuc_driver_doc/main/docs/environment/system_requirements.html)[\[28\]](https://fanuc-corporation.github.io/fanuc_driver_doc/main/docs/environment/system_requirements.html) list Ubuntu 22.04 with ROS 2 Humble, or Ubuntu 24.04 with ROS 2 Jazzy. Supported controllers are the R-30iB Plus, R-30iB Mate Plus, R-30iB Mini Plus, R-50iA and R-50iA Mate. The software options are J519 [Stream Motion ↗](https://www.fanucamerica.com/products/software/robot/stream-motion)[\[29\]](https://www.fanucamerica.com/products/software/robot/stream-motion) and R912 [Remote Motion ↗](https://www.fanucamerica.com/products/software/robot/remote-motion-interface)[\[30\]](https://www.fanucamerica.com/products/software/robot/remote-motion-interface), or the S636 External Control Package. * The [supported models ↗](https://fanuc-corporation.github.io/fanuc_driver_doc/main/docs/environment/supported_models.html)[\[31\]](https://fanuc-corporation.github.io/fanuc_driver_doc/main/docs/environment/supported_models.html) page covers the CRX, LR Mate, R-1000, M-10, M-20, M-710, M-800, M-810, R-2000, Paint and CR series. * The [MQTT option ↗](https://www.fanucamerica.com/products/software/robot/mqtt)[\[32\]](https://www.fanucamerica.com/products/software/robot/mqtt) supports MQTT 5.0. The [OPC UA Server ↗](https://www.fanucamerica.com/products/software/robot/hmi-device-snpx)[\[33\]](https://www.fanucamerica.com/products/software/robot/hmi-device-snpx) page gives no option number. * The [controller usage page ↗](https://fanuc-corporation.github.io/fanuc_driver_doc/main/docs/fanuc_driver/controller_usage.html)[\[34\]](https://fanuc-corporation.github.io/fanuc_driver_doc/main/docs/fanuc_driver/controller_usage.html) names each topic and service, such as `~/robot_status`, `~/read_error`, `~/set_bool_io`, `~/add_call_instruction` and `~/switch_control_state`. * On the Tallyfy side, the connector starts a process with `POST https://go.tallyfy.com/api/organizations/{org_id}/runs`. The [launch process reference](https://tallyfy.com/products/pro/integrations/open-api/code-samples/processes/launch-process/) lists the headers and fields. ## Related articles [**Integrations > Robotics**](https://tallyfy.com/products/pro/integrations/robotics/) Tallyfy has no integration or partnership with any robot maker. This concept section shows how a… [**Robotics > KUKA industrial robots and cobots**](https://tallyfy.com/products/pro/integrations/robotics/kuka/) Tallyfy has no integration with KUKA robots today. As of October 2026 KUKA’s robots carry from 3… [**Robotics > ABB industrial robots, cobots and controllers**](https://tallyfy.com/products/pro/integrations/robotics/abb/) Tallyfy has no integration or partnership with ABB. This concept page covers the industrial… [**Robotics > Universal Robots collaborative arms**](https://tallyfy.com/products/pro/integrations/robotics/universal-robots/) Tallyfy has no integration with Universal Robots, so this page describes one as a concept. It… ## Footnotes 1. ROS 2 (Robot Operating System 2) is an open-source framework and set of libraries for building robot applications. [↩](#user-content-fnref-1)