I am wanting to run automated backups on the KRC4. Currently these are done using windows batch scripts, but .bat scripts really begin to show their age when you need to do anything beyond very basic tasks. As we would like these scripts to be more robust, I have played with the idea of doing a Python install on the KRC4. I ave tested the setup on an OfficeLite machine to see if RAM is ok. It appears that we still have more than enough headroom in this regard. Is there something I'm not considering? Are all my robots going to crash if they're running small python scripts intermittently?
Python on KRC4
-
empireryan -
August 11, 2016 at 12:30 AM -
Thread is marked as Resolved.
-
-
When you run the scripts (whether Windows batch or Python scripts), files you archived are from the hard drive, maybe they are different to files in the ram disk.
See if this suits your need :https://www.robot-forum.com/robotforum/kuk…69075/#msg69075
-
Hello Empireryan,
KUKA provides tech-pack for auto backup or else Its possible with ethrnet connection for that you need to make a network connectivity with line-PC. if you have then just follow the below settings.
please go through the following settings
c_KRC_UTIL_NETWORKCONNECTIVITY
NETWORKCONNECTIVITY.ini
Type=1
LokalPfad=
disableNetwork=false
Networkadapter=Intel(R)[UserData1]
Kennwort=operator
Domaine=operator
Benutzer=LinePCSupervisor ()
Pfad=x: \\172.27.45.240 (follow with robot id)Hope this is helpful to your requirements.
-
KSS 8.3 has an auto-backup option by default, which can be pointed to network locations. Look under FILE>BACKUP MANAGER>BACKUP CONFIGURATION.
However, it makes "backups" by essentially saving all the WorkVisual projects on the robot, which is much bulkier than the usual Archive zip files.
I used to have an AutoIT script (based on Asimo's in the Manuals Software and Tools sub-forum) that, as a Windows Scheduled Task, would trigger the Archive All on a regular basis, and do things like remove any Archive older than X days (to avoid running out of hard drive space). But the later builds of KSS 8.3 (or rather, the Windows version that came with them) appears to have broken Windows Scheduled Tasks somehow, and I haven't had the time or motivation to figure out a workaround.
Bottom line: the KUKA auto-backup TP is probably the most robust choice, with the built-in autobackup taking second place. A roll-your-own solution can be fun (or hellishly aggravating), but often isn't worth the effort and potential trouble.
-
Right, we would like to not use Kuka's built-in automatic backups as they tend to hang if no network connection is available. Rolling our own scripts with batch files has been a decent solution, but Python would alow for more robustness/better error handling. Concerning RAM, I'm aware that the archives live in non-volatile memory on the disk. I have heard that there is a known memory leak issue on the Kuka robots we use. This issue is treated with intermittent power cycling, and my worry is that installing additional tools will exacerbate our memory issue. Some experimentation on an OfficeLite machine reveals that we should be ok from a RAM standpoint if we decide to run Python. Thanks for the input.