CAN OPEN CONNECTING TO KRC4

You must use workvisual, which is the configuration software for KUKA controllers. If you have not installed it you can find it on the d drive on the controller.
Check the help file and documention on how to do this, and come back if you can't figure it out.

It is not on D: of the controller, WorkVisual comes on its own CD.
Since your KSS is 8.3, you must have WorkVisual 3.0.x (for example I am using 3.0.9)

did you try reading those messages? do you understand what they tell? you need to ensure your slave uses correct size of inputs and outputs. after that you still have to map them to robot i/o

I have not used that particular unit but I did have quite few profibus or devicenet master and slave modules. beckhoff names master and slave same way, but slave has the appendix (-0010 for example).

In a nutshell:
1. driver/bus configuration: you need to decide how many I/O you want shared between robot and whatever the other device is (master, such as PLC or another robot or whatever). regardless who is master and who is slave, I/O sizes must match on both ends. for example if the robot is master, often slaves have fixed I/O sizes (simple digital I/O etc.). whatever the sizes are, you must match that on the robot side - if slave expects 5 bytes worth of inputs and 23 bytes worth of outputs, then robot must have exactly the same size configured on its end. if robot is slave, you can choose how many I/O you want to expose (share with master) but the sizes still must match on both sides. as long as this is satisfied, drivers are happy and you will not see those error messages.
2. I/O mapping: once you have completed previous step you should also perform mapping. mapping associates physical I/O point with robot I/O. Robot can use 4096 inputs and 4096 outputs (that is default setting but using WorkVisual it can be doubled to 8192 I/O points). Robot can use only those logical I/O points. When you add some peripheries (physical I/O or devices such as VFDs, welders, PLCs, other robots etc.) to one of the robots networks, you also need to tell robot which of 4096 or 8192 inputs and outputs correspond to signals of each of those peripheries. when mapping I/O, leave left pane for example on KRC tab and change right pane to Fieldbus tab. then look at the bottom of the screen for number of signals selected on both sides, they need to match before you connect them (green icon in the middle of the screen bottom).

old versions of the work visual had very little info about its use. since you use work visual 3.0.x, read online help, it shows you how to do this...
3. deploying project to the robot.

Everything is done in WoV. I'll try to remember to attach a PDF later. I haven't got CAN but Devicenet and Profibus are similar.

Sent with my Windows Phone using Tapatalk

Quote from panic mode

It is not on D: of the controller, WorkVisual comes on its own CD.

my apologies, this is not entirely correct. while every robot I worked on had media kit with WoV on CD though copy may be placed on D: of the robot.

Sorry forget about this!!

Attached is Devicenet config with WoV, but all bus systems are pretty similar to configure. Never seen that error though.

Quote from zeev

...
what i doning wrong now?

well, spelling comes to mind but there are other things too, like failure to mention any usable details (WoV version, how did you obtain project that you get error with, steps you do, what type of safety interface you have selected, how is it configured, and so on). you should steer clear from idea of creating WoV project from scratch, just get working project from robot, save it, save it as new version (change file name by "-v2" for example), modify it and then compile/deploy.

for what it is worth, according to a list I was given, the EL 6751 is currently unsupported by WoV. Many of the gateways are unsupported, with the exception of EL6752, EL6692, EL 6731 (there are others); notably any ethernet bridge, serial interface, etc. are not supported. You can also see this by the fact that they simply won't show up when you try to import the device description.