KUKA BOF Frozan problem

[amarprabhakar]

Hello All,
I am new for this forum and since one month i am watching and reading this.
My sincere thanks to all members, who have made all the efforts for this.

We have KRC2 and

I m Facing  KUKA BOF frozen issue since couple of weeks in a specific point of the program ( CONV_FOLLOW (1,1,Z_CANCEL_TIME_CONV,1237,TRUE,1,TRUE,R_DIST_WAIT_TRACKING,R_DIST_WAIT_TRACKING+300).

Can anyone have similar kind of issue? please share with me.

How to minimize this issue if you have continues operation?

Also my special thanks to Mr.Skyefire who gave me some important information.

This issue caused by Windows system, due to continuous process we can not power down the PC time to time.

Your feedback in this regard will be highly appreciable.

regards

[optimus_prime]

Hi Amarprabhakar,
                              Can you share your program with us? The line you have mentioned is not unclear.
Chances of virus infection are high.
Try to re-install Windows XP Embedded, then KRC.
What version of KRC software  you use? Maybe you need an upgrade

[SkyeFire]

What's weird about this problem is that (as I understand it) it's repeatable and linked to executing a particular ConveyorTech command.  A KRL command shouldn't be able to freeze the HMI.  And ConveyorTech is accessing external resolvers through the DSE/RDC cards, not anything under Windows.  The only thing I can think of is that this command is somehow freezing VxWorks, in such a way as to carry over to the HMI.

This one is sufficiently odd that I would be inclined to involve KUKA service, see if they've ever seen anything like this.

You could download and burn a copy of the free Ultimate Boot CD, boot the robot from that CD, and run some of the hardware test utilities (this *should* be safe, but as always, this is a use-at-your-own-risk suggestion).  I'm not sure how a RAM bug could cause an error that only happens for a particular ConveyorTech command, but I've seen weirder things.

Try some alternative tests of ConveyorTech and the hardware -- try syncing to the conveyor differently, from a different position.  Try some different ConveyorTech parameters, see if it changes anything.  If you've got another conveyor encoder, try replacing the one you have just to see if that has any effect.

Aside from that, I'd say Prime is right: make a full backup image of the robot's hard drive (or at least the C: partition) first just for safety, then do a full re-install starting from the XP CD.  If the problem goes away, great: you must have had a subtle bug creep into your Conveyortech, or possible the hardware driver.

[MOM]

Hallo amarprabhakar ,

as I understood you can force the krc to freeze after calling this command. Could you give me more information (archive, program running  and so on) in a pm to have some more investigation on this problem.

I never heard of it and it would interesting what is actually causing this problem.

regards

MOM