Posts by vvelikov

can you please show some screens opf the simulation - where the start of the movement should be? For me
LIN {X 270.474,Y 2.649,Z 459.371,A 95.000,B 0.000,C 180.000,E1 0.00000}
is pretty close to the robot base as you use base very close to 0
Also - when you show messages - show all of them - as you have been advised already

Quote

I got stuck on Line 31(Motion) for programmed path reached (BCO).

that only means that the robot has reached the point programmed in your program
start key required is just that - you ned to press the start key

Quote from panic mode

if you have robot that came with KRC4 compact or KRC4 smallsize, then probably most reasonable choices are to replace entire system (robot + controller) for another one ... or ... to consider KRC4 smallsize-2. it is still a "small robot" controller but can drive large external axes

you are correct, i can see in the documentation that it allows smallsize or compact versions only, At the time for some reasons (e. g. lack of experience:) i bought it like that, without knowing it wont be possible to update to a system with a rotary positioner.
It is a welding robot i have here installed for develepment and demo purposes and will be really useful if a positioner can be added, which is hard to do with compact cabinet, almost impossible - i asked Kuka for an upgrade eventually with a drive box, but it seems no possible to work with a positioner like DKP400 for example. That was the reason for me looking for options to upgrade to larger cabinet

It happened to me to have burnt mainboard - red light on voltmon fail - just by accidentally stoping the cooling fan. The solution was to repair the motherboard - i was happy to find someone to do it. The new motherboard is expensive, you can look for exchange option - i think KUKA have this on my.kuka.com. If you buy from Kuka - they will provide some files so you can update the system. If you are planning to buy second hand - make sure it is under warranty and also it needs to be exactly the same model
WHat you need to understand in terms to be able to identify what is what in this system is that the KUKA pad is like a tablet - it have its own Windows operating system and the messages you see there (unless it is connected normally to the control cabinet) are just telling you that the Smartpad cannot connect to the Kuka cabinet - cant get IP address. It is not asking you for this - just informing you. So changing anything there is a dead end.
As it is now clear that you have damaged board - try to find someone to fix it.
And about the cooling fan - if in any case this fan stops, the robot also halts - so you need to take good care of the cooling fans.
Good luck!

May be someone have the schematics for X21-X31 for compact and fullsize cabinets?

Quote

- In the beginning of the KRC5, we had a couple of robots coming from the KUKA factory, that were not properly configured, and could not be jogged in out-of-box state. Had to connect via WorkVisual and configure the robot type, since it had some Generic-x-axis robot type. Did not see this issue anymore last year.

Last three times it was always like that, especially the systems with more axis

In general, krc5 are nice, required a bit more work with cabling, yes, and adding additional axis - one of them with 4 additional axis and it was a bit of a mess as you need one more RDC (two were provided) - of course not configured in the factory
Will be more expensive than krc4s aftermarket - that is for sure
No issues with them for about 2years i recall, so it will show in the future

Hello,

i want to swap the controller on a welding robot i have from KRC4 compact to fullsize KRC4 cabinet
Here are the robot specs:

KR 8 R1620 ARC HW YOM2018 with KRC4 compact cabinet
KSS 8.6
The full KRC cabinet is attached as a photo - it is a standard one with one KPP 600 20 3X20 and one KSP 600 3x20
I want to be able to add external rotary table on this welding robot in the future which seems impossible with the compact version of KRC4

Is that doable? What i noticed is that the X21-X31 cable is different on the compact cabinet from the standard KRC4 but i was unable to find the schematic of both to compare - it is not clear if i can just use a standard cabel or the one from the compact cabinet.
I am a bit worried not to burn something inside so i am asking if someone here done something like that or have the knowledge if it is doable?

Quote from panic mode

if it is London in Ontario, that may work out...

my bad for some reason i was thinking you are in the UK...
So, will postpone it a bit in that case

Thanks works now - i feel really stupid!
I've done several setups like that, never had an issue - i suppose it was my luck before
One more beer added to the pile you already have earned ... might better turn this to whisky bottles
I am in London between 21st and 25th - ready to buy you a drink!

the error i am receiving on the HMI
And the connection inside the cabinet

In my case i have only ek1100, two digital io modules and one analog, EL 9011 on the end
The robot is with KSS 8.6.7, KR120 R3900K ultra hp KRC4 cabinet with one additional axis (not activated)
Here i am appliyng photos of the problem - the system cannot connect to the Beckhoff EK1100 - cant see it for some reason. I tried with several different modules, including one taken form a working system but the result is the same
I am really out of ideas, thinking to change the KSS may be, not sure the reason Ethercat wont work
Any advise?

interesting it is following for more!

Quote from berendericson

hy panic mode

thanks for responding

I'm aware that the topology needs to match exactly. This is also mentioned often on this forum.

Well i believe it is matching, i asked Kuka, and they confirmed.

Other than that they are not responsive on issue i'm having.

There are no other/new devices connected to the ethercat bus that i'm aware of.

That's why i started this thread, maybe there are other known issues.

Even when i just configure the ek1100 with nothing on it (and made sure physically it has nothing on it, nothing else connected to x44, just the ek1100) the controller is still unable to communicate with it. There are no telegrams coming back. I already replaced the bus coupler, so i assume it is not a hardware problem. The ek1100 is powered, both bus and io's. So far as i know the controller should be able to communicate with it. Or at least receive a signal back. In this case i can make a active connection from work visual through the KLI, for what it's worth, but controller won't communicate with the ek1100 and i still don't understand why.

Could it be that if someone before me had a other/older/newer version of Work Visual that would cause problems when i'm using version 5? somehow mess up the (ethercat)drivers?

Display More

Hello, facing the same problem - how did you solved this?

Quote from kkaide

Did you resolve this issue? We're having the same issue with similar mains phase error codes.

Yes, it was a problem with the power supply - they had problem with the power line

Quote from Francisco Levrino

Hi, i know i'm i bit late here. I'm working on the reverse engineering of one of these robots, i can send you pictures and dimensions on Wednesday. please tell me if you need something specific about it

Hi Francisco, i also need this mastering plate. Can you help?

Thanks! WIll give it a try and write back the result

It is pricey really - 2000 eur atm

Quote from SkyeFire

Does the fan plug directly into the motherboard? If so, VOLTMON FAIL suggests that the fan failure managed to damage a voltage regulating element on the motherboard, enough that the CPU and/or peripherals are not getting correct voltage to boot.

Yes, it is plugged directly. Sounds logical, not sure how i can check it. Will look around for microelectronics specialist to try it out - cannot se other option
Thanks!

So what i tried - removed the bios battery, triyng to reset the memory somehow ... just to make sure this is not some error saved somewhere there and preventing the start of the controller.
I am planning to feed 27V voltage to the CPU fan externally (leaving it in its socket to be able to send RPM information) just to check if the lack of fan rotation is preventing the startup of the PC
What i am thinking is may be the power feed line to the fan was overloaded and may be burnt and it is unable to drive it now. Not sure where to look for this as i am struggling to find information about this motherboard - even basic manual with description of the main functions - it is Fujitsu w26361-w4143-z4-02-36 or at least that is etched on it

Hello,
i have a problem with a motherboard (D3445-K11 GS1) of a KRC4 compact cabinet, manufactured 2018. There were around working 100hrs on this robot, used only for exhibition and development purposes.
The robot was working ok, until a plastic strap went between the blades of the CPU fan. The fan stopped, so did the cabinet and never came up . When i started it up there is a red led glowing around the USB ports (photo attached) with signage next to it: VOLTMON FAIL. Attached an external monitor and there is no signal from the cabinet at all.
I tested the fan - it is working fine. Also replaced the motherboard with another one and the robot is ok.
My question is - is that a repairable damage? Is there something i can do to revive the robot or a new motherboard is needed?
I suppose the damage is due to the fan overload and eventually the voltage supply damaged/dropped or something.
Any ideas where i can look will be appreciated!
All the best!
V

Quote from Mojtaba Rezaei

Dead tin causes a voltage drop and gives the voltmon fail

Where we need to revive the tin? Which part of the motherboard?