Thank you panic mode.
If I summaries,
a) duplicate or incorrect BrkeTestDrv.o
1.Check driver calls in motiondrv.ini, path C:\KRC\Roboter\init, in the section [OTHER_DRIVER] BRKTST, BrakeTestDrv.o.
2.Delete entries in the [TOOL_DRIVER] section.
=> I do not have the folder C:\KRC\Roboter\init on the KR 300 KSS 8.3 robot, expert mode is on.
b) Brake test is deactivated
Log in as Expert, make sure no program is selected then activate brake test
1.Open the file motiondrv.ini in C:\KRC\ROBOTER\Config\User\Common\MotionDrivers.
2.Check whether the driver BRAKE_TEST,mdrBrakeTest.o is deactivated (remove semicolon).
;BRAKE_TEST,mdrBrakeTest.o
3.Perform cold start
We tried activating the brake test, the brake test is OK, we just had an issue with our E1 external axis, a rail.
So, we deactivated brake test for external axis, then brake test is OK.
With this robot, we always work with break test deactivated. Does it have to be activated for FTC to work ?
c) Missing entries in the RSI configuration
The following entries must be present in the file C:\KRC\Roboter\Config\User\Common\MotionDrivers\motiondrv.ini:
[EMI_DRIVER]STANDSTILL_RSI,mdrStandStill.oThe following entries must be present in the file C:\KRC\Roboter\Config\User\Common\MotionDrivers\mdrStandStill.ini:
[STANDSTILL_RSI]MOTION_CLASS=CARTESIAN;WAIT_STOP_ACK=FALSEMON_RAMP_STOP=5000MON_EM_STOP=1000
We added the missing configuration lines,
[STANDSTILL_RSI]MOTION_CLASS=CARTESIAN;WAIT_STOP_ACK=FALSEMON_RAMP_STOP=5000MON_EM_STOP=1000
the previous line was present however with a different section name (I do not remember it, I will see this on monday).
We tried to change the section name, add a new section with this name, have both in the same file, all three cases failed.
d) defective driver - exchange missing or incorrect file
=> How to detect a driver is faulty ? and exchange files ? We should reload a new robot version from workvisual ?
e) driver for brake test commented out:
edit ini file and perform cold start with "reload files"
C:\KRC\ROBOTER\Config\User\Common\MotionDrivers\motiondrv.ini
At each step, we did a cold start with "reload files".
We joined Kuka-support for support, what they proposed to us is similar to what we tried following your advices.
Still the same error. I will get back to it on Monday. I'll keep you updated.
Thanks again for the step by step, it saved us some time to try it before contacting Kuka.
Best Regards,
Alex