Welcome, Guest. Please login or register.
Did you miss your activation email?
May 23, 2012, 07:53:11 PM
Home Help Login Register
News: Any Problems or Experience with Industrial Robots ?
Register and place your Question / Answer to worldwide Robotexperts right here !

+  Robotforum | Support for Robotprogrammer and Users
|-+  Industrial Robot Help and Discussion Center
| |-+  KUKA Robot Forum (Moderators: Werner Hampel, Martin H, SkyeFire)
| | |-+  PTP driving axis variable?
0 Members and 1 Guest are viewing this topic. « previous next »
Pages: [1] Print
Author Topic: PTP driving axis variable?  (Read 537 times)
presage
Newbie
*
Offline Offline

Gender: Male
Posts: 10


« on: November 06, 2009, 02:58:26 AM »

I am trying to optimise cycle times in a robotic cell.

When you make a PTP move, each axis's velocity is proportial to which ever axis will take the longest to reach its destination, what I want to know is there a variable which states which axis is the DRIVING axis, which axis is basically restricting the others.  I want to log these driving axis to change my motion paths/orientations to decrease cycle time.

I know I can log the torque on each axis but as you can imaging, the log files get large fast.

Cheers
Logged
optimus_prime
Full Member
***
Offline Offline

Posts: 168


« Reply #1 on: November 06, 2009, 06:13:45 PM »

I do not think there exists such a variable..
Even if it exists..they will not be accessible to us.

Logged
SkyeFire
Global Moderator
*****
Offline Offline

Posts: 1784



« Reply #2 on: November 07, 2009, 03:06:49 AM »

Don't know any clear-cut way to do this.  The only way I can think of offhand is to do it the hard way, by logging data in realtime.

The best way to do this would be using RSI, but if you don't have that, you could probably monitor the $VEL_AXIS variables.  Possibly setting up an SPS task that logs the peak value for each axis during a given move.  Since $VEL_AXIS_whatever shows a % of the axis's max rated speed, it should give you a decent first-order approximation of the relative rates of each axis.

The most straightforward way to do this is probably to use the built-in Oscilloscope (MONITOR>DIAGNOSIS) and set it up to log axis velocity during moves.  You can automate the O-Scope to a degree by manipulating the $TRACE variable in your program.
Logged
Pages: [1] Print 
« previous next »
Jump to:  


Login with username, password and session length

Powered by MySQL Powered by PHP Powered by SMF 1.1.16 | SMF © 2011, Simple Machines Valid XHTML 1.0! Valid CSS!