Kuka krc4 drivers are not activated (waiting passively)

Can you describe a bit more in detail what exactly you are doing to enable the drives and which error messages occur. Those two screenshots tell nothing!

Fubini

How did you copy your files.

They are marked as text files and not as src or dat files

Do you have more error messages - just open the window to show all of them

What method did you use to enable drives? Are we talking T1or T2 or AUT ....?

What error messages do you have.

What happens when you turn the key switch and try to enable drives?

...

Limitless possibilities. Reposting your previous insufficient description will not help.

Fubini

Quote from paulfile

The first picture is the screen of the non-working system, and the second picture is the screen of the working system. What do you think is the problem_

Quote from paulfile

In the other, the place where the driver should be active says 'O' and I cannot select and run the available programs.

Which picture is actually showing the problem (11.jpg or 22.jpg)?

I see a problem actually in both pictures! In the picture with "I" the button actually should be green.

It is gray which means that $MOVE_ENABLE is set to false

In your second picture you only have text files

They were copied to directly to the R1\Program folder and this does not work.

They have be copied within the GUI

Quote from paulfile

normally all src. and dat. was registered as such. After some operations, it turned into text.

Define "some operations." Details matter.

While I was working for kuka (long time ago) and something did not work, the anwser always was:
we have not done anything, but ... (my experience they screwed everything up) ?

@SkyeFire

hasch du de glaschgugl? i hob se net! hasch du de ibersetzung fir "After some operations"? i hab se net!

@ paulfile

solled so mer widermacha? odr do sagscht os wos des "some operations" moine doad?

Would say: revert 'some operations'

OT:

Quote from MOM

@ paulfile

solled so mer widermacha? odr do sagscht os wos des "some operations" moin

Cooler Dialekt , aber ob er das versteht?

Hm... one time (and only one!), I saw a KRC4 (running early KSS 8.2) that had part of $CONFIG.DAT overwritten by what looked like logging data from the operating system. I'm guessing it was a memory pointer error or buffer overflow.

I've never seen it happen to multiple files, though. Given that a Cold Boot with Reload Files fixed the problem, my guess is that your KRC had some sort of one-shot bug during the load or compile/link of the files during boot. This must have set all the internal flags indicating that the files were not valid KRL modules, but (forunately!) without corrupting the module contents.

On the KRC4 I mentioned above, the corrupted $CONFIG.DAT had been copied to the hard drive. And the robot's owner turned out to not have any backups... at all... on a robot that had been running for over 5 years!