<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Home :: byte robotics – Help</title>
    <link>https://help.byte-robotics.com/en/index.html</link>
    <description>About this manual This manual provides an overview of the OCP plugin (byte robotics – Optimized Collision-free Path Planning) for KUKA.Sim and serves as a reference guide for workflows and options. It does not replace the official KUKA.Sim documentation.&#xA;Target audience and prerequisites Target group: Commissioning engineers, simulation engineers, robot programmers Prior knowledge: Confident use of KUKA.Sim Quick Start System Requirements Installation License setup Getting started (Quick Start) Path Planning Contour Optimization Collision lists Safety Configuration FAQ &amp; Troubleshooting</description>
    <generator>Hugo</generator>
    <language>en</language>
    <atom:link href="https://help.byte-robotics.com/en/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Introduction</title>
      <link>https://help.byte-robotics.com/en/einstieg/index.html</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://help.byte-robotics.com/en/einstieg/index.html</guid>
      <description>Chapters System requirements Installation License setup Getting started (Quick Start)</description>
    </item>
    <item>
      <title>Operation</title>
      <link>https://help.byte-robotics.com/en/bedienung/index.html</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://help.byte-robotics.com/en/bedienung/index.html</guid>
      <description>Chapters OCP Tab OCP Help Collision Detectors Path Planning Robots Program Optimization Data Management Context Menu Contours Options Miscellaneous</description>
    </item>
    <item>
      <title>Workflows</title>
      <link>https://help.byte-robotics.com/en/workflows/index.html</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://help.byte-robotics.com/en/workflows/index.html</guid>
      <description>Chapters Model validation Collision lists Collision-Free Teaching of Process Points Safety Configuration for KUKA Robots Initializing the base with external axes Path Planning Contour Optimization Process Modeling</description>
    </item>
    <item>
      <title>FAQ</title>
      <link>https://help.byte-robotics.com/en/faq/index.html</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://help.byte-robotics.com/en/faq/index.html</guid>
      <description>FAQ – Frequently asked questions and troubleshooting If you encounter problems, first check Which licence version is currently active? Is the byte robotics OCP plugin activated and functional? What is the current available computer performance? Where can I find the hardware key in KUKA.Sim? Please start KUKA.Sim and navigate to File → Options → Add On → byte Robotics - Optimized Collisionfree Pathplanning. If necessary, deactivate the OCP plug-in and then reactivate it. This will ensure that the hardware key is recognised and integrated correctly.</description>
    </item>
    <item>
      <title>Release notes</title>
      <link>https://help.byte-robotics.com/en/release-notes/index.html</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://help.byte-robotics.com/en/release-notes/index.html</guid>
      <description>Changes and known issues for each release. Known issues describe the state recorded for that version.&#xA;Latest release Release 2026.10.09.54461 Version date: 2026-10-09&#xA;What changed iiQWorks 1.2/1.3 have moved from beta to full support. License activation now provides clearer feedback without freezing the interface, while subscription selections and active licenses survive failed refresh or renewal requests. VC scene loading handles controllers without linked motion nodes, without adding kinematic or planning support for unsupported controllers, and imported geometry retains its placement during joint motion. Duplicate names for components and nodes also made it impossible to start a calculation. This was fixed by adding a specific ID.</description>
    </item>
  </channel>
</rss>