Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5

G2 G3 gcode changes robot configuration

#1
Adding arcs in gcode changes robot configuration on Yaskawa.
from 1,0,0,0,0,0,0,0 to 0,0,0,0,0,0,0 so it flips and flips back again on g1 moves.


Attached Files
.jbi   g2g3.jbi (Size: 43.68 KB / Downloads: 34)
.jbi   g1.jbi (Size: 353.79 KB / Downloads: 34)
.nc   g1.nc (Size: 2.43 MB / Downloads: 35)
.nc   g2g3.nc (Size: 9.56 KB / Downloads: 38)
#2
Can you provide us with the RoboDK project file? It will help us reproduce the exact same issue.
#3
yes, here you go


Attached Files
.rdk   Yaskawa1.rdk (Size: 2.82 MB / Downloads: 33)
#4
I tried generating the program using the default Motoman Cartesian post processor but it does not change the configuration flags.

It looks like you are using a custom post processor. How did you customize your post processor?

If you changed something in your program such as the coordinate system or the tool, it is likely that the configuration changes but joints do not get recalculated. To properly calculate the joints that are required (configuration), you can try right click a program and select Recalculate Targets. This will recalculate the joint values for each target so that the correct configuration flags are generated.

You can also automatically update the joint values for each program before generating the program by following these steps:
  1. Select Tools-Options
  2. Select the Program tab
  3. Check the option Recalculate Targets before generation
#5
Mine changes the robotconfig in all posts (not with pulses oc).
Added my regular post. I have done several types of these files before and never had this issue, but that was this spring.
If I changed something, which is probable. I do not know what.


Attached Files
.py   Motoman_CartesianOnly_BH.py (Size: 4.01 KB / Downloads: 26)
#6
OK I understand better what you mean now. We are improving the post processor to prevent this issue. The configuration flags should remain constant. This improvement will be available with the next update.

If you have a Professional license I recommend you to contact us if you need access to this fix before the next release. You can contact us by selecting Help-Request Support and mention this thread.
#7
Thanks Albert. I can wait
  




Users browsing this thread:
1 Guest(s)