Description
In this tutorial, you’ll learn why the KRC diagnostic package is essential for support and troubleshooting on KUKA robot controllers. You’ll see how to create a diagnostic package using iiQWorks.Cockpit as well as directly from the HMI, including required user roles and storage options. You will also learn what data is included in the ZIP file and where it is stored on real and virtual controllers. By the end, you’ll understand how to reliably generate and interpret diagnostic packages for effective issue analysis.
The content of this video is intended solely as a supplementary aid for mitigation purposes. It is not a substitute for formal training or certified instruction required for commissioning or operational procedures.
For official training and certification, participation in a KUKA College course is required. A link to the official KUKA College website is provided in the video description: https://go.kuka.com/KUKAcollegeiIQKAOS2
What you’ll learn:
00:00 What a KRC diagnostic package is and why it matters
00:20 Creating a diagnostic package in iiQWorks.Cockpit
00:40 Selecting storage location and dump file options
01:20 Diagnostic package storage on real controllers
01:40 Creating a diagnostic package from the HMI
02:10 KRC Diag on USB drives
02:35 Viewing and locating existing diagnostic packages
03:00 Controller instance dependency and summary
03:15 Outro
Useful links:
Download iiQWorks on the my.KUKA marketplace: https://go.kuka.com/myKUKAiiQWorks
Check out the KUKA.College offerings and trainings: https://go.kuka.com/KUKAcollegeiIQKAOS2
Get more information on KUKA iiQWorks.Sim: https://go.kuka.com/iiQWorksSim
Or for further insights in the KUKA Digital Sphere: https://go.kuka.com/DigitalSphere
Don't forget to like, subscribe, and hit the bell icon for more tutorials and updates! (https://go.kuka.com/iiQWorksNews)