then messages module not unique should be gone
OK, this problem is solved
Start with the next issue
then messages module not unique should be gone
OK, this problem is solved
Start with the next issue
I could not find the iosys.ini and devnet.ini
You need only one set machine data.
Make a backup of your hard drive (image)
Then delete KL 1500K directory (then messages module not unique should be gone)
(maybe cold start neede)
yes, but the inverse() is taking these values (S & T) to calculate the axes positions or the prev axes position.
first "read first"
KSS Version and so on
actually KSS 8.6 is for KR C4 and KSS 8.7 for KR C5 controllers
Sorry: correct answer to the wrong question
I think you have to make the software update within the hmi
I would do it a bit different
For the pre_pick_pose you would need the new $AXIS_ACT (getting from pick_pose)
The same thing for your post_pick_pose and the projected _pre_pick_pose
So check for the first position and after reached use the new actual axes values to check for the next new position and so on
actually i was thinking to use VIO
This thread will be open until 23:00 UTC today or time already passed.
Afterwards only for persons with "conversations" (agreed)
I just came up with a studid idea:
esspecially in OL sometimes you want to check whether your programme is running and responding correctly.
In this case you need response from an external device (as input) to check your reaction on that
This could be a virtual PLC (taking outputs from kss *.OL and using simulated inputs from virtual plc
What do you think about this stupid idea?
I asked for the same hdd you had the problem with - otherwise I could have used one of mine
QUESTION: do you want really help
yes:
answer questions
no:
tell us as some fairy tails
We can only answer to question yes
Following post #26
where are the requested windows event files?
(I could not find any!)
just let follow the sequence what happened (finding the post is your job)!:
No problem..I give you the right to be angry
KSS version is v5.6.8..
We did not have any problems, but the factory electricity was cut off twice because it was snowing and we had this problem
My guess:
some files could not be saved and therefore you have this problem
Ergo:
checking hdd (and file management)
Result:
This was not done
To Do:
check SkyFire's suggestion from post #44 item 2
and RESPOND as asked millions of time
Remember: we want to help YOU
DO AS REQUESTED, OR LEAVE IT
As a first guess:
your problem starts with line 61
SE32_SHIFT = $NULLFRAME BASE32_SHIFT.X = XNACHALO.X BASE32_SHIFT.Y = XNACHALO.Y BASE32_SHIFT.Z = XNACHALO.Z BASE32_SHIFT.A = angle_a BASE32_SHIFT.B = angle_z BASE32_SHIFT.C = 0.0 BASE_DATA[32] = BASE32_SHIFT ; move the Base32 to the beginning of the weld vector
$Nullframe is write protected (actually you should get error messages)
If you want to change values of this frame you probably asigned as $Nullframe change them to myNullFrame (this time no write protection)
myNullFrame = {X 0.0, Y 0.0, Z 0.0 ,A 0.0, B 0.0, C 0.0}
(hint: take $ROBROOT as an example - if floor mounted!)
In post #25 Gocea recommended to take an image of the hard drive . According to your post #27 you did.
For some tests I would use the cloned one and make the checks as recommended:
- check windows event logs (post #26) or zip the event files then I can check them with Fixevt.exe
- run chkdisk.exe in order to see whether files are corrupted (broken MFT sometimes defrag will help)
- check for viruses
Doing these tests connect your hard drive to your normal computer using usb to ide
There are companies around selling refurbished kuka components or repair them.
Important: get the component you need with the same article number
As said before you can also check ebay