Installing KUKA.Ethernet IP 1.1 Scanner/Adapter

    I am going to purchase KUKA.Ethernet IP for communications to an existing KRC4 and wanted to know if there is any information out there as to the steps on how to install this package successfully.

    I told KUKA that on the TP it said I have KSS V8.2.18 but they checked the Serial Number for a Robot from 2013 and said they checked with the Serial Number and that I actually do have V8.3, so makes me a bit worried.

    But in any case when I get the Package I want to have read a manual or write up on how this should be done.

    Any hints or suggestions much appreciated.

    Thanks,

    There was no KSS8.3 in year 2013 and screenshot clearly states that you are using KSS 8.2.18

    I would guess there was some typo somewhere and they ended up looked at wrong record.

    installation is very simple though menu options may be named slightly differently so to be safe use correct manual.

    in your case that would be KSS_82_SI_en.pdf, i have version 7 from 2014 and instructions are in chapter 13.3

    if you get the software on USB it is ready to install. if you get download link, it will be ZIP file with some long name.

    Prepare empty USB stick and extract content of the ZIP file to a root of empty USB stick (it could be in a directory too but then you need to change path).

    1) read pinned topic: READ FIRST...

    2) if you have an issue with robot, post question in the correct forum section... do NOT contact me directly

    3) read 1 and 2

    Thanks panic mode, I know, I sent them the picture and she was looking at it as she was checking the Serial Number of the Sticker that I sent her.

    So will Ethernet IP not work on anything earlier than v8.3, why are they so worried that i have to have this version. From the controller it is clearly not v8.3 but I will Install and see what happens. I typically always get my controllers with Ethernet IP because I am used to using this type of communications but this robot has only the standard Ethercat.

    Question, Is it best practice and the only safe method to have a good backup, that I must use a Kuka USB Stick? Can I use a Normal USB Stick to get Image and Archive and be Safe, or should I purchase the KUKA Stick?

    wait what...? how did you conclude that EtherentIP may not work on KSS8.2?

    why not check documentation? you can access all manuals for free on Xpert portal, simply by registering. then you can see what options are compatible with your KSS or what KSS is compatible with EtherentIP 1.1

    https://xpert.kuka.com/ID/AR2116

    1) read pinned topic: READ FIRST...

    2) if you have an issue with robot, post question in the correct forum section... do NOT contact me directly

    3) read 1 and 2

    there are different types of backup and they all contain varying amount of data. hence to be safe it is a good idea to make several different backups. there are overlaps so one can extract one or another info from different types of backup.

    here are the common types of backup:

    1. you can copy individual file or program to a USB or some shared folder. this form of backup is as small as it gets. for programs, this is usually 2-200kb.

    2. you can collect current WoV project. this is pretty good - if complete. but projects could be also incomplete (in that case controller automatically loads missing parts from Base Project). this is usually 2-10Mb

    3. then there are backups created by Backup Manager. content of this backup varies from one KSS to another. key advantage is that it can be automated to generate and keep several backups. in the past this "backup" was archive, nowdays it is is working project and Options... so size can vary and you can have up to 50 backups

    4. you can create archive to a USB or whatever drive. if you choose option "Archive All" you get all programs, machine data sets (both for robot and controller), all WoV project (not just working one) and software logs. Archie created through WorkVisual is slimmer, named differently and only contains working project but it can be more conveninet to do if you have bunch of robots. archives are usually 2-20Mb. one can also create partial archive that only contains logs or programs or mada. i was never fan of those until i encountered system that could not generate full archive. then parical archie was very helpful to identify and fix the issue.

    5. you can create KRCDiag. on some system versions the very first created Diag is overblown and is usually ignored (does not clean up some temporary files) so it is recommended to just create second one. Diag file contains programs, machine data, screenshot, software logs, hardware logs, some other logs and working project (but not others). ormally Diag is created when doing hardware update (installing newer firmware) or in case of problems where archive content is not providing enough of clues. size is usually 50-250Mb

    6. controller image. this is complete backup of the HDD including both partitions and boot sector. this contains literally everything (Windows, Installed software, etc.). it is possible to create HDD image using different tools but the official tool is the KUKA USB Recovery stick. It is not cheap but it is very handy. This stick is bootable so during use controller boots from it, not from HDD. during USB recovery stick use you cannot use smartPad so ignore messages on it ("timeout" or whatever). But if your controller does not have CPS on the cabinet door, smartPAd is still very useful as a "lightbulb" for indicating that operation is in progress. when operation is complete and controller goes to sleep, smartPad goes dark. size of image is usually 2.5-6Gb

    i do most of work at home so when i am finally in front of robot there is usually tons of changes prepared. so i make full backup. At very least for me that is Archive + Image + KRCDiag because i may want to check something later on when i am no longer on site and while there is uusally plenty of overlap ... no single form of backup contains everything.

    for example HDD image is the most complete form of backup but it still does not contain hardware logs. KrcDiag does not contain all WoV projects. And if system was not setup explicitly to take care of them, many important files do not make it into WoV project or Archive. i don't like that because i found about it the hard way. I want usual forms of backup (Archive and WoV project) to contain ALL important files. that includes CustomMon.ini, custom configurations, files, menues, options etc. this takes just a bit of work to setup but - effort is well worth it.

    1) read pinned topic: READ FIRST...

    2) if you have an issue with robot, post question in the correct forum section... do NOT contact me directly

    3) read 1 and 2

    yes, KUKA USB Recovery stick is a tool, it is not tied to specific controller so same stick can be used on any KRC4 and many KRC2 controllers.

    note that it need to be configured before use so check the documentation.

    1) read pinned topic: READ FIRST...

    2) if you have an issue with robot, post question in the correct forum section... do NOT contact me directly

    3) read 1 and 2

Advertising from our partners