Posts by TheKetteringKid

Another thing you could do if all the points need shifted is shift the userframe (if one is being used). Last year I setup a robot loading on and off of a turntable with a separate userframe per side so that long term if the guides get set different I can adjust the userframe for the entire side of the turntable vs retouching all of my points.

The other thing that has not been said is you could add a PR offset and simply adjust your offset every time an adjustment is needed.

Just like YakawFabb said adjusting points on the fly is not super safe if a mistake is made especially large mistakes. For instance forgetting or adding a "-" can make huge difference and is a very easy mistake to make...

The mask was exactly what I needed. Thanks Nation

We use a recovery sub program. We write the position to a position register and then use IF statements to determine if the robot is in a location it can be recovered as well as recoverin it. If the robot is not in an area and pose that has a recovery procedure it throws a user alarm and must have a technicain recover. An example of a non recoverable area would be shared spaces or in machines.

I am working on a project that uses a servo gripper for a palletizing process. I have no experience with a servo gripper only pneumatic. I have setup the servo gripper to be G2 A1. I am using extended axis control and multi-group motion. I am working on roboguide and have noticed points I make (using PRs) move both motion groups. Is there a way to not move both motion groups? For different material I will have a different servo position and I do not want unique points for all the clearance and prep moves for each servo position... I might be asking how to not use multip group motion is certain programs.

If your goal is to protect different tooling from hitting machinery or fixturing I would recemend using the toolchange function. You can toggle different user models based on the usertool frame.

For the Cartesian Position Check you should select "Tool Change" instead of the user model. For the current tool you could simply use IO to toggle the correct one on, I choose to use a background program to see the currently selected tool and set the IO accordingly (this way if a tech is manually changing the usertool it will select the correct usermodel). Under the toolframe screen only 1 model can be selected at a time and it is very picky (part of why a background program works well here). There is a lot on the back side of this, I would recommend getting a copy of the DCS manual it is very helpful in setting this up.

Also, if you are trying to protect anything other than machinery dont use NSI's, they are not rated for anything but that.

You can do this in a macro for moving in T1 or you could add this to a program for running in auto. Make a position register the current position, then change the Z value to your desired height, then move to that position register.

PR[??]=LPOS

PR[??,3]=Desired Height

L PR[??]

Did you ever find a resolution to this? I have the exact same scenario that is going on...