Robotics > KUKA industrial robots and cobots
Robotics
How a written procedure could drive robot work
Section titled “How a written procedure could drive robot work”Tallyfy runs the steps people follow. Write a procedure once as a template, and each launch becomes a process with tasks, owners, deadlines and an activity log of who did what.
Some robot makers let outside software read a robot’s status or send it work. Where they do, a small program your developer writes could join the two, so a robot fault launches the right Tallyfy process. Boston Dynamics describes the same idea for Spot: an application that creates a work order whenever the robot finds an anomaly ↗[1]. Tallyfy doesn’t build or ship that program.
What a link would take
Section titled “What a link would take”Your developer would need three things. The robot maker has to publish an interface, a documented way for a program to read the robot’s status or send it work. Tallyfy’s side exists today: another system can launch a process through the API or complete a task, and Tallyfy sends a webhook (a message to another system) when a task is completed or a process launches.
The program has to reach both sides, so plan where it runs with your IT team. NIST’s guide to operational technology security ↗[2] recommends keeping the networks that run physical equipment apart from the corporate network, with a buffer zone called a DMZ between them.
Before you buy, ask the robot maker in writing what your software may connect to. Some interfaces need an extra controller option, as FANUC’s driver does ↗[3].
Where each robot maker stands
Section titled “Where each robot maker stands”As of October 2026, these seven have a page of their own:
- Apptronik Apollo humanoid robots - Apptronik makes the Apollo humanoid robot ↗[4]. It publishes no way for outside software to send it work or read its status, as an independent API catalogue ↗[5] also found.
- Boston Dynamics Spot, Stretch and Atlas - Boston Dynamics makes Spot, a mobile robot for industrial inspection ↗[6]. Its Orbit software ↗[7] lets outside software schedule Spot’s missions, read the results and get a webhook when Spot completes an action.
- Universal Robots collaborative arms - Universal Robots makes collaborative robot arms, or cobots ↗[8]. Outside software can start and stop a program ↗[9] and stream live robot data ↗[10].
- KUKA industrial robots and cobots - KUKA makes industrial robots ↗[11]. Outside software can read a robot’s status over OPC UA ↗[12], and can send work to a program on the controller through an add-on KUKA sells, such as KUKA.Ethernet KRL ↗[13].
- Unitree quadruped and humanoid robots - Unitree makes four-legged and humanoid robots ↗[14]. Its developer kit ↗[15] reads a robot’s status and controls it, though not every edition supports it ↗[16].
- ABB industrial robots, cobots and controllers - ABB Robotics makes industrial and collaborative robots and controllers ↗[17]. Its Robot Web Services ↗[18] API can start and stop a robot program, read the controller’s state and report changes.
- FANUC industrial robots and CRX cobots - FANUC makes industrial robots ↗[19] and CRX cobots ↗[20]. Its ROS 2 driver ↗[21] can read a robot’s status and errors, set its signals and send it motion commands ↗[22].
Makers with no page here
Section titled “Makers with no page here”As of October 2026, these four make humanoid robots but publish no developer interface we could find, so we found nothing documented for outside software to call.
- Agility Robotics. Agility says its Digit 4 humanoid has logged more than 65,000 hours of work at customer sites in North America ↗[23], and Digit 5 is in development ↗[24]. It said in 2024 that its Arc fleet software would provide industry standard APIs ↗[25], but we found no documentation for them.
- Figure. Figure says its Figure 03 robot takes care of household tasks like laundry, cleaning and doing dishes ↗[26]. It said in April 2026 that the robots it builds go to its research teams, data collection, housework trials and commercial use-case development ↗[27].
- Tesla (Optimus). Tesla’s annual report to the SEC calls Optimus “a general purpose, autonomous humanoid robot in development” ↗[28]. Its July 2026 investor update says production lines are being installed ↗[29].
- 1X. 1X sells NEO, a robot for chores around the house ↗[30], on pre-order with US deliveries due in 2026 ↗[31]. It wrote in June 2026 of a “recently announced developer platform” ↗[32], but we found no developer kit, API or documentation for it.
Safety standards for industrial robots
Section titled “Safety standards for industrial robots”As of October 2026, the standards bodies list these editions of the industrial robot safety standards:
- ISO 10218-1:2025, Robotics - Safety requirements - Part 1: Industrial robots. Edition 3, February 2025 ↗[33].
- ISO 10218-2:2025, Robotics - Safety requirements - Part 2: Industrial robot applications and robot cells. Edition 2, February 2025 ↗[34].
- ISO/TS 15066:2016, Robots and robotic devices - Collaborative robots. Edition 1, February 2016 ↗[35], which ISO marked in June 2025 to be revised.
- ANSI/A3 R15.06-2025, the US safety standard for industrial robots. A3 released it in September 2025 ↗[36]. It aligns with ISO 10218 Parts 1 and 2, replaces the 2012 edition and folds in the ISO/TS 15066 guidance.
Technical details
Section titled “Technical details”(Skip this unless you’re setting up the technical side.)
Three shared ways to move robot data, as of October 2026:
- OPC UA is the OPC Foundation’s industrial interoperability standard ↗[37] for machine data. ABB offers it through its IoT Gateway ↗[38], KUKA through KUKA.DeviceConnector on the KR C5 ↗[39] and FANUC as an OPC UA Server option ↗[40]. Siemens SIMATIC S7-1200 and S7-1500 controllers can act as an OPC UA server ↗[41].
- ROS 2, the Robot Operating System, is “a set of software libraries and tools for building robot applications” ↗[42]. Its documentation says it’s primarily built on top of DDS ↗[43], an industry standard for passing data between programs, and now supports other middleware such as Zenoh.
- MQTT is a lightweight OASIS standard messaging protocol ↗[44] for the Internet of Things, now at version 5 ↗[45]. FANUC sells an MQTT option ↗[46] for its controllers, and ABB’s IoT Gateway ↗[47] supports it.
Related articles
Section titled “Related articles”Robotics > FANUC industrial robots and CRX cobots
Robotics > Apptronik Apollo humanoid robots
Robotics > ABB industrial robots, cobots and controllers