I think he is referring to Drives Configuration in WorkVisual. External axis setup on 8.2 software was a bit more involved... (load correct WaggonDriver). Then WorkVisual got improved. Have not tried new WorkVisual on KSS8.2...
Posts by panic mode
-
-
-
-
That is better but still no details. KSS version is important... Message programming is different on different KSS .
-
check manual, every time you use EKI instruction, you get result telling what happened (if instruction was successful or not).
you should evaluate result before proceeding and decide on recovery options...
for example if you failed to open connection, there is no point in trying to read or send data - you WILL get an error.about the interrupts - if you plan on using RESUME command, program that may be interrupted must be in a subroutine, at least one level lower than program where interrupt is declared. your entire program is same level as where interrupt is declared.
-
you have no error handling. your interrupt cannot work like that either
-
[size=2]
load always has effect on every aspect of robot performance including its accuracy. for best accuracy and long service life of the robot it is important to enter and use correct load. note that load info is not just mass, it is also center of gravity, inertia values and orientation of inertial axes.default values for loads are indicated by setting mass to negative value. this means that robot will assume it is working with factory load (dead weight which is equal to or maybe a bit greater than rated payload). you do not want use those values...
for a light load, you may want to enter mass before running LDD.[/size]
-
in KRL names are limited to 24 characters...
-
-
-
i would say post real code instead of making it up.
that cannot even compile.... -
not sure if this is same for all types of flange but as i recall that is just energy supply (cables and hoses extending from base of the robot to flange). you would need to add I/O and valve banks yourself and do the plumbing...
-
Profinet manual does not go this far, you need system integrator manual.
your robot should have all the manuals but many are also in the download section of the forum.
robot supports up to four operating modes (T1, T2, AUT and EXT). in first three all control is done by human. in EXT control is done by PLC. System integrator manual will have description of signals and timing diagrams. but before you get to this, you need to have working interface (data exchange) with PLC which - you have accomplished already.
note that some signals are edge triggered (not all). idea is to power up drives, clear messages, issue start and CELL.SRC will run. after this you need to specify which program number you want robot to execute and tell robot when it is ok to read the program number.if you search for AutoExternal or CELL you will find bunch of discussions on the forum.
-
"cannot find documentation" means you did not try and you did not read topic READ FIRST.
system integrator manual covers this in detail.
it is also covered in KUKA course "Programming1". -
without RSI you may play with program override
-
i would recommend to read topic READ FIRST
-
[size=2]did you read topic READ FIRST?
what is the KSS version?[/size]
-
then use WorkVisual to configure master/slave parameters. make sure to check manuals and axes configuration (same direction?)
-
[size=2]
it is impossible to help you based on what you shared, you are leaving all vital data out [/size]
[size=2]https://www.robot-forum.com/robotforum/kuk…rum/read-first/in general, using vision on a robot means one of two things - navigation or inspection.
your application is navigation. this means you must at least have:
* camera system configured and interfaced with the robot.
* camera system calibrated (must have coordinate system and scaling setup correctly)
* camera system must have valid program for all model(s) to be found
* robot must have base that matches camera coordinate system
* robot must have model vector of the reference part
* robot must have valid program to select camera system program, issue trigger, get data from camera and apply robot offset.this is a forum, it is used to answer questions, not to replace comprehensive training.
if you need help here, you need to be specific and [/size][size=small]that is why you are not getting answers you expect... [/size] -
the way i interpret your drawing, robot is fixed on the bridge. Both external axes motors are moving together (they are ONE axis). this means you need to setup master/slave relationship. one motor will be master, the other will be slave and follow whatever master does. this requires choosing how exactly slave is controlled. it could be position or torque. in this case i would say slave need to duplicate master position, not torque (or you will end up in a jam).