All posts

KUKA LBR iiwa Review: The Cobot KUKA Stopped Modernising

The LBR iiwa stays on Sunrise.OS while KUKA moves its other lines to iiQKA, and KUKA publishes almost no performance data for it.

By Robo2u Editorial · 11 min read

The KUKA LBR iiwa is a 7-axis torque-sensing arm that still defines what a research-grade cobot looks like. KUKA's product page describes joint torque sensors in all seven axes and an axis-specific torque accuracy of ±2% of the maximum torque. It remains listed as a current product on kuka.com, with no end-of-life notice we could find.

The thing this review is about sits underneath that. KUKA has split its cobot line by operating system. The LBR iisy runs iiQKA.OS, KUKA launched iiQKA.OS2 in 2025, and in April 2026 trade coverage reported a new KUKA robot controller shown at Global Industrie and framed around coming EU cybersecurity mandates. The iiwa appears on none of those roadmaps. It stays on Sunrise.OS, in a Sunrise Cabinet that integrator documentation and university setup guides consistently describe as Windows 7 Embedded plus a virtualised VxWorks. Windows Embedded Standard 7 lost extended support in October 2020.

The second finding is about what KUKA declines to publish. Its public LBR iiwa page gives payload, reach, IP rating, mounting, controller and torque accuracy, and no repeatability, weight, speed or price at all. Third-party listings fill the gap with numbers KUKA does not stand behind.

Companion reading: How to choose a cobot · Collaborative robots (cobots) ultimate guide · Force-torque sensing ultimate guide · Robot cybersecurity ultimate guide · Universal Robots review

Table of contents

  1. Key takeaways
  2. The controller nobody talks about
  3. What KUKA publishes, and what it omits
  4. The licence tier trap
  5. Price, and what integration actually adds
  6. KUKA the company: restructuring, ownership, exposure
  7. How it compares
  8. Who should buy it
  9. Verdict
  10. Frequently asked questions

The controller nobody talks about

The product page says the controller is "KUKA Sunrise Cabinet" and stops there. What that cabinet contains is documented mainly by integrators, robot forums and university lab setup guides rather than by KUKA: a Windows 7 Embedded host running a virtualised VxWorks real-time layer. We could not confirm this against a KUKA document, and we could not confirm whether units shipping in 2026 use a newer Windows build. Both are open questions worth putting to a KUKA sales engineer in writing.

The Fast Robot Interface, the reason most research buyers choose this arm, is cyclic UDP carrying joint state from an external PC. The open-source drivers pin it down: drake-iiwa-driver connects to the robot on UDP port 30200 over the KONI interface at 192.170.10.2/24. No authentication is documented in those driver projects or in the KUKA FAQ material we could reach. KUKA's own guidance is to attach the control PC directly to the KONI port. That is network isolation presented as a setup step.

Zero CVEs against a Windows-7-based controller of this vintage reads as an absence of audit rather than an absence of bugs. The comparison case is instructive. KUKA's own advisory for CVE-2022-2242, dated 2022-08-04, covers KUKA SystemSoftware V/KSS versions 8.2 through 8.7 across the KR C4 and KR C5 product lines. The flaw is in the WorkVisual Service Host interface: where access control is unavailable or not enabled, reading and changing the robot configuration are possible without any authentication, based solely on network access to TCP port 49003. The advisory's remedies differ by version. For KSS 8.2 (discontinued 2016) and 8.4, network isolation is required. For 8.3 (discontinued 2019) and 8.5 (discontinued 2020), a TechPackage adds access control. For 8.6 prior to 8.6.5, the fix is an upgrade. Nothing equivalent has ever been published for Sunrise, and we found no advisory naming the iiwa and no coordinated-disclosure programme covering Sunrise.

This lands into the EU Machinery Regulation 2023/1230, which applies from 20 January 2027. Trade coverage of EN ISO 10218:2025 reports that it addresses cybersecurity expectations for connected manufacturing environments. If you are specifying an iiwa for a European line that will still be running in 2028, ask KUKA for its written position on that standard before you sign.

What KUKA publishes, and what it omits

Fetched from KUKA's own LBR iiwa product page, August 2026:

Figure LBR iiwa (as published by KUKA)
Payload 7 to 14 kg across variants
Maximum reach 800 to 820 mm across variants
Axes 7, with joint torque sensors in all seven
Axis-specific torque accuracy ±2% of the maximum torque
Protection IP 54
Mounting ceiling, floor, wall (floor only for cleanroom)
Controller KUKA Sunrise Cabinet
Pose repeatability not published
Weight not published
Speed not published
Price not published

Four of the numbers a buyer needs to size a cell are simply absent. The figures that circulate instead come from resellers and simulation catalogues. RoboDK's LBR iiwa 14 R820 entry lists 0.1 mm repeatability and 30 kg weight. We could not obtain a KUKA datasheet to check either figure, so neither belongs in a specification document you will be held to. Ask KUKA for the signed datasheet and for the per-axis maximum torque table, without which the ±2% accuracy figure cannot be converted into newton-metres.

One measurement point worth holding onto regardless of the paperwork: repeatability and absolute accuracy are different quantities, and on serial arms of this class the gap is large. If your process depends on absolute positioning off a CAD frame rather than relative moves off a taught frame, budget for a calibration campaign and measure the result on your own arm.

The licence tier trap

Core capability on the iiwa arrives as separately licensed Sunrise technology packages rather than as standard firmware. Sunrise.FRI is the one most research buyers need. Its SKU pages sit behind the my.kuka.com login wall, verified by attempting them in August 2026. No public price exists, and we could not determine whether the licences are subscription or perpetual.

The practical consequence: the capability most iiwa buyers are actually paying for, real-time external torque and position control, is an add-on at an undisclosed price on top of an arm that already costs more than its obvious rivals. Development also assumes Java, through Sunrise.Workbench. Which Windows versions the current Workbench supports is not something we could verify.

Price, and what integration actually adds

KUKA publishes no price for the LBR iiwa, and we could not verify any secondary quote to a standard we would put in front of a procurement team. Aggregator and reseller listings for this arm vary widely and none of them is a list price. Treat every dollar figure you find for an iiwa as a lead to a quote request rather than as a number.

Two things you can act on. First, ask for the quote to be itemised: arm, Sunrise Cabinet, and each Sunrise technology package as a separate line, because the licences are where the undisclosed cost sits. Second, ask the integrator for the integration figure in writing at the same time, since on arms in this class integration routinely rivals the hardware line. Used and refurbished iiwa units do circulate on the secondary market, which is the cheapest way for a lab to find out whether the arm suits the work.

KUKA the company: restructuring, ownership, exposure

From the KUKA Group Annual Report 2025, 138 pages, signed in Augsburg on 27 March 2026:

Metric FY2023 FY2024 FY2025
Revenues (€m) 4,053.7 3,732.4 3,897.2
EBIT (€m) 158.2 76.5 58.7
EBIT margin 3.9% 2.0% 1.5%
Employees (FTE, 31 Dec) 14,726 14,783 14,542

Revenues rose 4.4%, against a forecast of more than 10% that was not achieved. Restructuring costs of €75.1 m hit FY2025 EBIT, and the report states: "An increase, again in the single-digit range, was expected for the EBIT margin, but this did not occur due to restructuring expenses." Current other provisions rose from €152.0 m to €208.8 m, with €22.4 m sitting in the restructuring line. Group equity fell to €1,425.9 m from €1,552.6 m. Free cash flow stayed positive at €190.2 m (2024: €223.7 m), and S&P confirmed the BBB+ rating on 1 September 2025 with a stable outlook, so this is pressure rather than distress.

Ownership context matters for anyone buying into public procurement. Midea completed its takeover in January 2017 by acquiring a 94.55% voting stake, and acquired the remaining minority in a squeeze-out completed in November 2022. The Annual Report 2025 records that Midea Group Co. Ltd holds 100% of the shares in KUKA SE & Co. KGaA. In February 2025 KUKA announced about 400 Augsburg job cuts, raised to 560 in November 2025. Bavarian state aid was under discussion in the same month, and in late January 2026 local reporting said roughly 100 of those Augsburg jobs had been saved by new investment.

Whether any future US or EU trade measure eventually captures a German-built, Chinese-owned arm is a real open question for procurement teams, and we could not resolve it from public sources. We found no measure in force today that names an industrial arm of this type.

One more thing the annual report does not do: across its 138 pages it never uses the words "iiwa", "iisy" or "iiQKA". KUKA does not break out cobot revenue, and no installed-base figure for the LBR iiwa exists in any source we could reach.

How it compares

KUKA LBR iiwa Universal Robots UR10e Franka Research 3 KUKA LBR iisy
Axes 7 6 7 6
Payload 7 to 14 kg (KUKA) vendor-published vendor-published varies by model
Reach 800 to 820 mm (KUKA) vendor-published vendor-published varies by model
Repeatability KUKA does not publish vendor-published vendor-published vendor-published
Joint torque sensing all 7 axes none (wrist F/T optional) all 7 axes KUKA does not publish
Real-time external control FRI, separately licensed RTDE, included FCI, included on Research ExternalAPI.Control
Controller OS Sunrise.OS (Windows 7 Embedded host, reported) PolyScope Linux PC iiQKA.OS
Roadmap status no successor OS announced active active active

The comparison that matters is the last two rows, and the one above them. UR and Franka both publish their performance figures and both bundle the real-time interface. KUKA publishes neither for the iiwa. The iisy is KUKA's own answer, on the operating system KUKA is investing in.

Who should buy it

Buy it if you specifically need 7-axis redundancy with genuine joint torque sensing at up to 14 kg, you have Java capability in house, and you are running an isolated research or medical-integration network where the controller's OS lineage is a documented risk rather than an unmanaged one. For contact-rich assembly research the hardware is still excellent, and used units are cheap enough that a lab can afford to find out.

Do not buy it if you are specifying a production cell that must still be compliant and supported in 2028, if your security team will have to answer for a Windows 7 Embedded host on a plant network, if you need published, warranted performance figures at quotation time, or if you mostly need reach rather than dexterity, where a longer-reach six-axis arm will serve you better. If you want a KUKA cobot on a supported OS path, look at the iisy instead.

Verdict

The LBR iiwa is very good hardware on an operating system its own maker has stopped developing. Every other KUKA line has a named successor OS. This one does not, and its controller is built on a Windows release that lost extended support in October 2020, driving a real-time interface with no documented authentication that KUKA suggests you air-gap. That combination is survivable in a lab and hard to defend in a 2027 factory audit.

Buy it as a research instrument, at used prices, with clear eyes about the licence add-ons and about the fact that KUKA will not publish a repeatability number for it. Specify something else for a line that has to pass EN ISO 10218:2025.

Frequently asked questions

What is the LBR iiwa's repeatability? KUKA does not publish one. Its public product page omits repeatability, weight, speed and price entirely, verified August 2026. Third-party catalogues quote figures (RoboDK lists 0.1 mm for the 14 R820) that we could not trace to a KUKA document. Request the datasheet from KUKA before you write a number into a specification.

Are there any published CVEs for the LBR iiwa? None that name the LBR iiwa, Sunrise.OS, Sunrise Cabinet or Sunrise.Workbench, checked against NVD in August 2026. The published KUKA CVEs we found run from 2020 to 2022 and cover the KR3R540, the Visual Components Network License Server, KUKA Sim Pro, and KR C4 / KSS system software.

Does the Fast Robot Interface have authentication? Not that we could find documented anywhere, in KUKA material or in the open-source drivers. Unverified rather than confirmed absent. KUKA's guidance to connect the external PC directly to the KONI port implies the answer.

Is FRI included with the robot? No. Sunrise.FRI is a separately licensed technology package. Pricing sits behind the my.kuka.com login wall.

Has the LBR iiwa been discontinued? No end-of-life or last-order-date notice was found, and the product is still listed as current on kuka.com as of August 2026. It is absent from KUKA's iiQKA operating-system roadmap.

Does Midea ownership create an import or procurement problem? We found no measure in force today that captures an industrial arm of this type. Midea holds 100% of KUKA SE & Co. KGaA, per the Annual Report 2025, so the question is worth putting to your own procurement counsel rather than assuming either answer.

How financially stable is KUKA? Revenues rose to €3,897.2 m in FY2025 with EBIT margin down to 1.5% after €75.1 m of restructuring costs. The parent entity, KUKA SE & Co. KGaA, posted an €83.4 m net loss against €37.8 m of net income in 2024. S&P confirmed BBB+ stable on 1 September 2025. Free cash flow remained positive at €190.2 m.

Related guides