KSS Main screen

Simplest option would be to plug in a USB mouse and grab the top bar of the KUKA HMI and double-click it, or drag it until the Max/Min/Close buttons in the top right corner are available then use those.

Without a mouse... I'm not sure this will work, but if you can log in to Expert or Admin mode, you might be able to use Alt-Space to open the min/max/move menu (you can try this on a regular Windows application to see what it should look like). Maximize should work. If not, using the Move option should let you move the window about with the arrow keys.

i would recommend to anyone to read pinned topic READ FIRST before asking for help.

btw. also for anyone wanting to do anything with the robot would be wise to invest some time to learn a bit about computers and robots, specially if when trying to make some changes (configuration or programs).

for example (generic things, not just for KUKA):

1. old computers tend to fail more frequently than new one. that's just life. therefore try to make backups more frequently and keep them safe.

2. placing copy of a file or archive on same HDD is not really a backup. if the HDD fails you lose everything including on that drive, including C:\ and D:\ and everything else stored there. proper backup means storing files to a different media (USB, another HDD etc.) and creating more than one form of backup (archive, diag, hdd image)

3. when computers throw some message - read it... every letter.

4. when they complain about come file, read complete message to identify the file, then try viewing file in a text editor. btw you failed to read the message (only part is shown).

5. it is common that one message triggers an avalanche of other messages. those follow up messages are usually much less relevant than original, sometimes even completely false.

6. if the file is indeed corrupt, replace it with good copy from recent backup. and of course, immediately create another backup.

7. be careful how you restart computer or you may lose files or get files corrupted. it is a good idea to close files before shutting down or restarting. in case of a robot it is a good idea to maintain batteries. without them any power loss could mean corrupted data.

pretty sure this would allow sorting this problem out too

i would love to help but i just do not understand what you are doing and how exactly.

1. how exactly you tried making the copy? Using KUKA USB Recovery stick? or by connecting robot's HDD to your computer via USB adapter for example? if you are trying to copy files while system is using C: (booted from it), this will not work. there may be an option to still do it this way by installing special driver (by your HDD cloning software). most people simply use mentioned USB recovery stick. it is fast, simple and image is compressed (relatively portable). using this option, means KRC boots from USB and not from HDD so accessing files on C:\ is not a problem. same is if using linux dd command etc. (careful with dd). i hope you are not trying to copy files from C:\ to whatever storage using Windows Explorer or worse - using Kuka HMI

2. as mentioned, this is probably because you are trying to copy files while KRC is booted and - none of the needed files are no D:

3. which machine data we are talking about? robot controller MADA or robot MADA? both are set of *.DAT files and therefore readable like text files. if there is a corruption it is easy to see. if needed, MADA can be easily compared to default (at least for robot) since it is on the D:\

4. if i recall *.pfc files are only present if one has files that use encryption. never really looked into that.

Quote

I copied them with simply copy/paste to Usb in KSS tree

what does that mean? you used KSS Navigator to copy files?

Quote

The first ting I tried, was to copy mada

well... it does not work like that. if you want to copy file, first you have to make sure that it is not used. this means ending any process that may be accessing it. in case of KSS that means deselecting both robot and submit interpreter. So make sure nothing else has the files open, then make sure that both robot and submit interpreter are deselected and then using KSS navgator transfer the files from D:\ to LRC:\R1\MADA

R need to be gray too

and you need to be logged in to access D:\

i don't know. but it would be helpful to see the files you are having problem with but the screenshot does not cover the part that is subject of conversation. that is one of the reasons i ask people to post screenshots that cover entire screen. (perhaps check READ FIRST). are the files in right place or already removed? are they write protected or locked somehow by one of the processes? are they corrupt? what can you tell us about those files? maybe there is a problem with KSS and restart is needed.

you can also try rebooting but on start do let KSS launch. then try to replace files using windows. and then start KSS (or reboot)

did you try to boot into windows only (without starting KSS) and check if you can manipulate those files?

Okay, let's back up a step. First, you shouldn't try to tamper with the .DAT files on the hard drive (well, only as a last resort).

During boot, a KRC copies most of its operating files from the hard drive into a RAM drive, and runs off those copies. The RAM drive is what appears as /R1 (not C:/KRC/R1!) in the KUKA Navigator. The first thing to try is examining those files in the HMI, by using the Open button on them.

Can you get log into the Expert or Amin user group in the KUKA HMI? (not Windows). Factory default password is kuka (all lowercase!). That should work, unless someone changed them.

Can you get the robot to make an Archive All backup? That should work regardless of your user rights. Then you can unzip the Archive and examine the file contents offline. Before meddling with any file contents, you really want to nail down exactly what the underlying issue is.

Also, regarding Windows admin rights, you should have them by default. However, this post has a list of Windows logins used for different Win/KSS versions. Unless someone tampered with the credentials, these should work.

But I would advice against modifying any files unless/until the root errors are well established. In fact, I would strongly recommend pulling the HDD and cloning it using Acronis or Clonezilla before trying any alterations. Otherwise, it's possible to brick the controller beyond recover, without getting original install media from KUKA.