after postprocessing I get different solid angles for the same operation posted in one program. Swiveling is calculated with Auto3D option. Post is a Heidenhain TNC based on sim07.
Operation 1: PLANE SPATIAL SPA+0.0 SPB-6. SPC+90.
Operation 2: PLANE SPATIAL SPA+0.0 SPB+6. SPC-90.
Operation 3: PLANE SPATIAL SPA+0.0 SPB-6. SPC+90.
Operation 4: PLANE SPATIAL SPA+0.0 SPB+6. SPC-90.
and so on...
How can I prevent the postprocessor from calculating different angles?
Thanks in advance,
Solved! Go to Solution.
probalby there is previous operation with some angle and then in the next operation is generated shortest path solution
and if you pp has limit thats contain 2 alternative solutions so you can get alternative solution affected by shortest motion.
Try to reset motion vars to zero.
You can find CMD in some OOTB posts "..reload_all_motion_variables_to_zero...."
and put this CMD in the end of operation sequence.
Thanks for the quick response.
I already reset all motion variables to zero.
I will check, if it works by limiting the 4th axis.
Limiting range - could be a solution too.
But reseting vars to zero via mentioned cmd above - you have the same starting contitions (x0,y0,z0, 4th.0,5t.0)
But pp is ootb and we dont know what the logic. PP based on a generic template is better to me.
hope it helps then
I don't get it!!
I limited the 4th axis from
-110 - 10
110 - 0.
Now I removed the limitation and it still works. Dunno why. It just does.
maybe that is why I dont use ootb posts or advanced template posts
but as I said I would use reseting and reloading motion vars at first step