Robot build date 2006
KR 240 l210-2
KPC ed05
KR C V5.2.12 HF5
Xpe V1.1.0 build 10
Robot has not been used for 4-5 years Robot runtime shows 12414645.00 h. Is this minutes or what? Runing almoust 24 years in six years. Time vortex or what
Robot build date 2006
KR 240 l210-2
KPC ed05
KR C V5.2.12 HF5
Xpe V1.1.0 build 10
Robot has not been used for 4-5 years Robot runtime shows 12414645.00 h. Is this minutes or what? Runing almoust 24 years in six years. Time vortex or what
its hours...
RDC data corrupt?
i have a similar situation with a kr16 krc2 , the robot was bought new to kuka arround 5 , 6 years ago
but , just worked 1 year and shows robruntime arround 7, 8 years working 24/7
robruntime counts every hour since the robot its on even moves or not ? or just count when the robot its working? , count when i programming or configuring ?
exactly what meaning "service hours " on my kr16 its arround 150
BR
runtime is counting up as long as drives are enabled, does not matter if robot is moving or not....
Robot runtime shows 12414645.00 h. Is this minutes or what? Runing almoust 24 years in six years. Time vortex or what
The value shown will be in minutes of runtime. Hours = $ROBRUNTIME/60
no... there is a unit of time after the number and it is "h" for hours. when HDD or robot or RDC are exchanged incorrectly, data gets corrupted and one can see crazy values like this.
The value shown will be in minutes of runtime. Hours = $ROBRUNTIME/60
older software versions are in minutes yes
of course "the leg"
here an example :
$robruntime=23890
23890/60=398.16 time working robot on hours
so , on KRC4 also $robruntime was showed on minutes