Orientation Problem wrt to UF calculated Point

  • Im having orientation problem, tried to change S2C430 parameter to 1 where the orientation of T axis should be constant but still it is changing. Please look at the pictures, the orientation from roby what I will (Ori_Good) and the orientation what my Calculated Point(Ori_Bad) do’s photos

  • Люба правильно сказала.

    You have to store the reference position of robot with the proper configuration and shift it for every workpiece. Or have multiple reference positions with different robot configurations.

    By the way it's a good question, how to set RCONF to a P variable explicitly with INFORM commands.

  • Following up on this, tracking a similar issue on a DX200 controller, MH50-II robot.

    Running a palletizing operation with a pounce point above the pallet, locations are calculated based on counter integers provided by the PLC.

    When working with KUKA, I used to manage this problem by just using a MOVL move instead of a MOVJ (KUKA disregards the "status" and "turn" i.e. robot orientation for MOVL moves). It doesn't appear that it works the same way with Motoman. On this edge case, the robot tries to reorient because the location at C0 has a T orientation <180 degrees. The placement point has a T orientation > 180 degrees.

    Providing a snippet of code below. Am I able to accomplish this with the code I have, or so I need to use a SFTON / SFTOF command? For reference, the D[ ] variables are positions provided by the PLC, I[ ] variables are counters provided by the PLC. D[30] - D[32] are placeholder variables so I can move things into my position buffer P[30]. I know the orientations for X, Y, and Z are correct as I'm able to get 99% of my pallet stacked with this code. Just a weird edge case I'm trying to account for.

  • After doing some more manual reading, turns out modifying S2C430 solves my problem.

    Setting the parameter to 2 makes it work in my case. Woo. ;)

  • After doing some more manual reading, turns out modifying S2C430 solves my problem.

    Setting the parameter to 2 makes it work in my case. Woo. ;)

    Hallo paranoidandroid,

    I tried with S2C430 parameter it didnt worked out, Instead of Single refrence point now Im using multiple refrence points.



  • I’ve seen this axis flip phenomenon happen a lot when you take a job that has been written as a standard and then converted to a relative job later on. Generally when you start from the beginning with a relative job, you don’t see this as much.

    In addition to setting S2C430 to a 1, I would interlock test start through your job and modify enter on any trouble spots in the correct orientation as you encounter them. Try to avoid movements where the controller could make the decision to spin an axis one way vs the direction you anticipated. I would counter this with an intermediate point as needed to help the controller sort out the orientation throughout the job.

    Good luck.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account
Sign up for a new account in our community. It's easy!
Register a new account
Sign in
Already have an account? Sign in here.
Sign in Now