--- title: ABB industrial robots, cobots and controllers · Tallyfy Pro description: Tallyfy has no integration or partnership with ABB. This concept page covers the industrial robots, GoFa cobots and OmniCore controllers ABB Robotics sells, what its Robot Web Services API lets outside software ask of a robot controller, and where a written Tallyfy procedure could fit. lastUpdated: 2026-10-14T00:00:00.000Z source_url: html: https://tallyfy.com/products/pro/integrations/robotics/abb/ md: https://tallyfy.com/products/pro/integrations/robotics/abb/index.md --- Concept only Tallyfy has no integration or partnership with ABB. This page is a concept and not a product. Vendor facts link to their source, read in October 2026. ## How an ABB robot could start a Tallyfy procedure ABB Robotics makes [industrial and collaborative robots, controllers and software ↗](https://www.abb.com/global/en/areas/robotics)[\[1\]](https://www.abb.com/global/en/areas/robotics). Its controllers answer to [Robot Web Services ↗](https://developercenter.robotstudio.com/api/RWS)[\[2\]](https://developercenter.robotstudio.com/api/RWS), a published API[1](#user-content-fn-1) that lets other software start a robot program, read the controller’s state and hear about changes as they happen. 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 ABB Robotics makes today As of October 2026: * **Robots.** ABB’s [robot range ↗](https://www.abb.com/global/en/areas/robotics)[\[3\]](https://www.abb.com/global/en/areas/robotics) covers articulated, collaborative, delta, SCARA, paint and palletizing robots, plus autonomous mobile robots. * **Cobots.** These are robots made to work alongside people. The GoFa cobot [comes in three sizes, for 5 kg, 10 kg and 12 kg ↗](https://www.abb.com/global/en/areas/robotics/products/robots/collaborative-robots/gofa)[\[4\]](https://www.abb.com/global/en/areas/robotics/products/robots/collaborative-robots/gofa). ABB’s [cobot page ↗](https://www.abb.com/global/en/areas/robotics/products/robots/collaborative-robots)[\[5\]](https://www.abb.com/global/en/areas/robotics/products/robots/collaborative-robots) also names the single-arm YuMi. * **Controllers.** Each robot runs from a controller, the box that holds and runs its programs. OmniCore is the current generation, and ABB says it spans [five controllers on the same platform ↗](https://www.abb.com/global/en/areas/robotics/products/controllers/omnicore)[\[6\]](https://www.abb.com/global/en/areas/robotics/products/controllers/omnicore). [IRC5 is ABB’s other controller family ↗](https://www.abb.com/global/en/areas/robotics/products/software/iot-gateway)[\[7\]](https://www.abb.com/global/en/areas/robotics/products/software/iot-gateway). * **Software.** [RobotStudio ↗](https://www.abb.com/global/en/areas/robotics/products/software/robotstudio-suite)[\[8\]](https://www.abb.com/global/en/areas/robotics/products/software/robotstudio-suite) is ABB’s software for programming and simulating robots away from the factory floor. ### Who owns ABB Robotics On October 8, 2025, ABB agreed to [sell its Robotics division to SoftBank Group ↗](https://www.abb.com/global/en/news/129776/abb-to-divest-robotics-division-to-softbank-group)[\[9\]](https://www.abb.com/global/en/news/129776/abb-to-divest-robotics-division-to-softbank-group). In July 2026, ABB still expected the sale to [close in the second half of 2026 ↗](https://www.abb.com/global/en/news/137499/abb-expands-automation-offering-with-acquisition-of-rotork)[\[10\]](https://www.abb.com/global/en/news/137499/abb-expands-automation-offering-with-acquisition-of-rotork). SoftBank’s [press releases ↗](https://group.softbank/en/news/press)[\[11\]](https://group.softbank/en/news/press) show no completion as of October 14, 2026. ## What outside software can ask a robot to do As of October 2026, ABB’s [Robot Web Services 2.0 reference ↗](https://developercenter.robotstudio.com/api/RWS)[\[12\]](https://developercenter.robotstudio.com/api/RWS) lets a program written in any language: * Load a robot program, set the values it uses, then start, stop or reset it. * Read whether the program is running, along with the controller’s state and operating mode. * Read the controller’s event log. * Switch an input or output signal on or off. * Subscribe to changes. The controller sends each change at once, within 200 milliseconds, or within 5 seconds, depending on the priority the program picks. Only signals and saved program values (persistent RAPID variables) can use the fastest setting. To start a robot program, your software has to log in with a user account set up on the controller and hold what ABB calls [mastership ↗](https://developercenter.robotstudio.com/api/RWS/Swagger_Doc/RAPID_Service.yaml)[\[13\]](https://developercenter.robotstudio.com/api/RWS/Swagger_Doc/RAPID_Service.yaml), the right to change what the controller is doing. Factories that already use OPC UA[2](#user-content-fn-2) can reach the same controllers through ABB’s [IoT Gateway ↗](https://www.abb.com/global/en/areas/robotics/products/software/iot-gateway)[\[14\]](https://www.abb.com/global/en/areas/robotics/products/software/iot-gateway). It works with both IRC5 and OmniCore controllers. ## What outside software can’t do All four limits are as of October 2026. * [Robot Web Services ↗](https://developercenter.robotstudio.com/api/RWS)[\[15\]](https://developercenter.robotstudio.com/api/RWS) has no call for a whole fleet. Each call goes to one controller and works with the robot programs on it. * Version 2.0 comes with RobotWare 7, which ships on OmniCore controllers, says ABB’s [developer centre ↗](https://developercenter.robotstudio.com/webservice)[\[16\]](https://developercenter.robotstudio.com/webservice). Older RobotWare versions use version 1.0, which ABB marks as deprecated in RobotWare 7. * ABB’s older OPC server isn’t recommended for new projects. The [developer centre ↗](https://developercenter.robotstudio.com/opcserver-sdk)[\[17\]](https://developercenter.robotstudio.com/opcserver-sdk) points to the IoT Gateway instead. * None of the eight tools on ABB’s [developer centre ↗](https://developercenter.robotstudio.com/)[\[18\]](https://developercenter.robotstudio.com/) is for ROS[3](#user-content-fn-3). Other groups publish open-source drivers. Ask ABB or your integrator what your controller needs before you plan a connection. ## 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 before it runs again. 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 subscribe to the controller’s events. When the controller logs an error, the connector would call Tallyfy’s API to [launch the matching process](https://tallyfy.com/products/pro/launching/triggers/via-api/) and copy the error into its kick-off form. Tallyfy would then assign the repair to named people. The last step can be an [approve/reject task](https://tallyfy.com/products/pro/tracking-and-tasks/tasks/what-types-of-tasks-can-i-create-with-tallyfy/), so a supervisor decides whether the cell runs again. When it’s approved, a Tallyfy webhook (a message Tallyfy sends to another system when something happens) could tell the connector. Whether software may restart a robot at all is a decision for your safety review. You don’t need a connector to begin. A person can type what the controller shows into a Tallyfy [form field](https://tallyfy.com/products/pro/tracking-and-tasks/tasks/what-are-form-fields-in-tallyfy/). ## For developers (Skip this unless you’re setting up the technical side.) * ABB’s [developer centre ↗](https://developercenter.robotstudio.com/webservice)[\[19\]](https://developercenter.robotstudio.com/webservice) says version 2.0 is OpenAPI compliant, so Swagger tools can generate client code. * The [2.0 reference ↗](https://developercenter.robotstudio.com/api/RWS)[\[20\]](https://developercenter.robotstudio.com/api/RWS) is ABB document 3HAC073675-001, Revision L. Clients log in with Basic authentication, as users set up in the controller. Events arrive over secure WebSockets, up to 10 per session, with 70 sessions in total. * Calls behind the list above include [POST /rw/rapid/execution/start ↗](https://developercenter.robotstudio.com/api/RWS/Swagger_Doc/RAPID_Service.yaml)[\[21\]](https://developercenter.robotstudio.com/api/RWS/Swagger_Doc/RAPID_Service.yaml), [GET /rw/panel/ctrl-state ↗](https://developercenter.robotstudio.com/api/RWS/Swagger_Doc/Panel_Service.yaml)[\[22\]](https://developercenter.robotstudio.com/api/RWS/Swagger_Doc/Panel_Service.yaml), [GET /rw/elog ↗](https://developercenter.robotstudio.com/api/RWS/Swagger_Doc/Elog_Service.yaml)[\[23\]](https://developercenter.robotstudio.com/api/RWS/Swagger_Doc/Elog_Service.yaml) and [POST /subscription ↗](https://developercenter.robotstudio.com/api/RWS/Swagger_Doc/Subscription_Service.yaml)[\[24\]](https://developercenter.robotstudio.com/api/RWS/Swagger_Doc/Subscription_Service.yaml). * The [IoT Gateway ↗](https://www.abb.com/global/en/areas/robotics/products/software/iot-gateway)[\[25\]](https://www.abb.com/global/en/areas/robotics/products/software/iot-gateway) also supports MQTT. * Open-source projects, not ABB releases: [abb\_robot\_driver ↗](https://github.com/ros-industrial/abb_robot_driver)[\[26\]](https://github.com/ros-industrial/abb_robot_driver), a ROS driver, and [abb\_librws ↗](https://github.com/ros-industrial/abb_librws)[\[27\]](https://github.com/ros-industrial/abb_librws), the C++ library it builds on, both from ROS-Industrial. abb\_librws uses Robot Web Services 1.0 and doesn’t work with RobotWare 7. There is also [abb\_ros2 ↗](https://github.com/PickNikRobotics/abb_ros2)[\[28\]](https://github.com/PickNikRobotics/abb_ros2) from PickNik Robotics. * 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, and the [webhooks guide](https://tallyfy.com/products/pro/integrations/webhooks/) covers the other direction. ## 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 > FANUC industrial robots and CRX cobots**](https://tallyfy.com/products/pro/integrations/robotics/fanuc/) Tallyfy has no integration or partnership with FANUC. This concept page covers the industrial… [**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 > Apptronik Apollo humanoid robots**](https://tallyfy.com/products/pro/integrations/robotics/apptronik/) Tallyfy has no integration with Apptronik, and as of October 2026 Apptronik publishes no way for… ## Footnotes 1. A published way for one program to talk to another and swap data, with nobody at a screen. [↩](#user-content-fnref-1) 2. An industry standard that lets machines and software from different makers share data securely. [↩](#user-content-fnref-2) 3. ROS (Robot Operating System) is open-source software that many robot developers build on. [↩](#user-content-fnref-3)