Update robtarget in a record

Burro
✭
Answers
-
This is from the technical reference manual - Rapid overview:
A specific component of a record data can be accessed by using the name of that component, for example pos1.x := 300; assignment of the x-component of pos1.
Now if you mean by modposing the position with the pendant, I don't know.Lee Justice0 -
lemster68 said:This is from the technical reference manual - Rapid overview:
A specific component of a record data can be accessed by using the name of that component, for example pos1.x := 300; assignment of the x-component of pos1.
Now if you mean by modposing the position with the pendant, I don't know.
I feel like this should work because you can modpos a robtarget in an array atleast.0 -
Is the robtarget in question constant?Lee Justice0
-
How about in a routine as an INOUT parameter?Lee Justice0
-
Hey ...I believe that what you are trying to do is something similar to wanting to modify a position obtained through an Offs(pp,0,0,0) routine. This is not possible.The flexpendant 'modpos' function expects to receive a robtarget and not 'RECORD.robtarget' or 'Offs(robtarget, x,y,z)'.Good job.0
-
mandolas said:Hey ...I believe that what you are trying to do is something similar to wanting to modify a position obtained through an Offs(pp,0,0,0) routine. This is not possible.The flexpendant 'modpos' function expects to receive a robtarget and not 'RECORD.robtarget' or 'Offs(robtarget, x,y,z)'.Good job.0
-
@Burro I agree with your statement, however, as far as I can remember, it has always been this way.
@lemster68's idea can partially solve your problem...Some time ago, I wanted the user to be able to modify positions without interacting with or changing the code. So I 'removed' the user's permissions to edit RAPID.In a procedure, I passed a robtarget array (INOUT) and, at each iteration, asked the user if they wanted to save the position. This way, they could move the robot (using the joystick) to the desired position and respond YES to save it.In this routine, I used CRobT() to get the current position. Of course, there are some limitations, such as the Tool and Work Object used to store this position.Good work.
Post edited by mandolas on0 -
For sure it would have to be persistent or VAR, constant would not work at all.Lee Justice0
Categories
- All Categories
- 5.6K RobotStudio
- 398 UpFeed
- 20 Tutorials
- 13 RobotApps
- 299 PowerPacs
- 405 RobotStudio S4
- 1.8K Developer Tools
- 250 ScreenMaker
- 2.8K Robot Controller
- 327 IRC5
- 65 OmniCore
- 7 RCS (Realistic Controller Simulation)
- 821 RAPID Programming
- 8 AppStudio
- 3 RobotStudio AR Viewer
- 19 Wizard Easy Programming
- 105 Collaborative Robots
- 5 Job listings