E1 Axis Velocity and Acc Not Progrmmed !!!

An the controller is absolutely right: You set the velocity for E1 in line 31 which obviously is after your initial PTP in line 27.

Also you miss out completely on setting the Acceleration on E1 using $ACC_EXTAX[1]. Again the controller speaks the truth.

Fubini

Quote

And in other programs I didnt declared these variables though working

In the other programs you probably had a INI fold included at the beginning.Then these values are set using bas.src calls inside the INI-Fold.

The program template you get by creating a new program using the SmartHMI always has a INI Fold you probably did not notice until now.

Thats the difference between the simple user interface using Inline forms and trying to use plain KRL in expert mode. In the first case pretty much all necessary steps are hidden inside the Inline forms and system folds. If you want to use expert programming mode your programs can be a lot more flexible but on the downside you have to take care for everything yourself.

Fubini

Sorry. Can you be a bit more specific. I do not understand what your question is here.

There is no definitive fixed answer to this question. It all depends on your specific application program. But of cours you should be familiar with Status and Turn and be able to react if problems arise from your application and how to handle them. For example if you hit a software limit switch in your application it is usually a Turn issue that needs to be resolved. Even if you do not explicitly state Status and Turn in your application there are rules how the system substitutes them. These rules have been talked about many times in this forum so I will not reiterate them here. Just use forum search with keywords Status and/or Turn and you will find many topics dealing with these two and how to solve problems arising from them.

Fubini

I know this thread is from last year, but I didn't want to create one with the same issue. I tried using the solution here in combination with the Kuka manual, but couldn't solce the problem.

DECL REAL CompressionForce,LaserPower,LaserAngle,TapeFeed

$APO.CDIS = 10          
$VEL.CP = 0.2            
$VEL_EXTAX[1] = 1        
$ACC_EXTAX[1] = 50        

CompressionForce = 200
LaserPower= 0
LaserAngle = 0
TapeFeed= 120

CompressionForceValue(CompressionForce)
SetLaserPowerValue(LaserPower)
SetTapeFeedValue(TapeFeed)
SetLaserAngleValue(LaserAngle)

LIN {x -565.568,y 1501.898, z 496.859, a 85.5, b 0.0, c 0.0, e1 0.0 }        

The programms which are called (CompressionForceValue etc.) only communicate with the attached tool by reading/writing in and ouputs, so I doubt the issue comes from there. This Programm is the only place where I actually try to move the robot and the external axis. After getting the error about the axis E1 Velocity not being programmed I found this Forum, checked the Kuka manual added $VEL_EXTAX[1] = 1 and $ACC_EXTAX[1] = 50 but I still get the same issue.

Can anyone tell me what I'm doing wrong?

Thanks in Advance!

And what about the other axes? You only set vel/acc for the first external axis! Robot axes want to know their vel/acc as well.

$VEL_AXIS[<1 to 6>] = *

$ACC_AXIS[<1 to 6>] = *

Fubini

Thanks for your fast reply!

I though with

$VEL.CP = 0.2

I would set the velocity for the robot axes. Is that assumption wrong?

I also assumed the error message "Axis E1 Velocity not programmed" referred to the first external axis…

So I would add

FOR I = 1 TO 6
    $VEL_AXIS[I] = 10
    $ACC_AXIS[I] = 100
ENDFOR

or do I need anything else?

Quote from Narma1368

$VEL.CP = 0.2

Only fot LINs and CIRCs. I do not know what your routine does additionally. You posted only a subset of it and this also contains some subroutines that we do know nothing about. So what do you expect? Does it work when you use an INI-Fold?

I only use LINs in my routine. Basically I have more LINs and at the end I call

LaserOff()
LaserLineLaserOff()
CutTape()
CompressionForceOff()

As I mentioned in my first post, none of the subroutines has any movement in it. They only write values to outputs which are send through EtherCAT to my tool.

Do I even need the

$VEL_EXTAX[1] = 1
$ACC_EXTAX[1] = 50

when I only use LINs?

Sure. If you have an external axis you have a redundant robot (more overall degrees of freedom than Cartesian position). Hence to reach the desired Cartesian postion seven degrees of freedom need to be commanded. Each commanded degree of freedom needs a defined vel/acc.

Where is your external kinematic: in robroot or in base?

Fubini

In base

So I will keep

3$APO.CDIS = 10          
4$VEL.CP = 0.2            
5$VEL_EXTAX[1] = 1        
6$ACC_EXTAX[1] = 50  

But then all axes should have both velocity and acceleration or am I wrong?

If you do not have any further additional axes. Probably. I have no access to any controllers anymore. So I repeat as asked before: Does it work with INI at the beginning? INI fold initializes all components.

Fubini

Quote from Narma1368

In base

So I will keep

Code

3$APO.CDIS = 10          
4$VEL.CP = 0.2            
5$VEL_EXTAX[1] = 1        
6$ACC_EXTAX[1] = 50  

But then all axes should have both velocity and acceleration or am I wrong?

you are wrong...

system can have up to 12 axes... 6 for robot arm (A1-A6) and 6 external (E1-E6).

and you need to initialize values for all of them... or at least ones that are present in your case.

better initialize them all - all the time. that way you do not need to worry if your programs will work when client changes configuration and adds another axis.

your post only shows code initializing velocity and acceleration for axis E1.

so for external axes you need:

$VEL_EXTAX[1] = 1 ; E1 (axis 7)
$VEL_EXTAX[2] = 1 ; E2 (axis 8)
$VEL_EXTAX[3] = 1 ; E3 (axis 9) etc.
$VEL_EXTAX[4] = 1
$VEL_EXTAX[5] = 1
$VEL_EXTAX[6] = 1 ; E6 (axis 12)


$ACC_EXTAX[1] = 50 ; E1
$ACC_EXTAX[2] = 50 ; E2
$ACC_EXTAX[3] = 50 ; E3 etc.
$ACC_EXTAX[4] = 50
$ACC_EXTAX[5] = 50
$ACC_EXTAX[6] = 50

of course you can wrap it all in a loop. i write in long form to make is very obvious what you are missing.