Siemens 840D 5 axis Rotary Head over Rotary Table post problem

[Anonymous]

I have a Chiron 5 axis rotary (ZX plane around Y axis) head over rotary (ZY plane around X axis) table

I have reviewed as many of the existing posted comments as seemed appropriate and can't find a solution to my post issue. My problem lies in the output of the CYCLE800 line. I have attached the post I'm working with.

The output that I’m looking for is: (posted using Siemens NX - tested code)

CYCLE800(1,"KOPF_TISCH_BA",0,57,0,0,0,13.06431,7.43547,0,0,0,0,1,1)

The output I’m getting is: (posted using Inventor HSM - untested code)

CYCLE800(1,"KOPF_TISCH_BA",0,57,0,0,0,13.171,7.242,1.69,0,0,0,-1) – different A and B values, unwanted C rotation

Thank you for any assistance anyone may be able to provide.

[bob.schultz · Accepted solution]

Hello,

I noticed you changed the calculation mode from 27 (ZYX) in the generic post to 57 (XYZ) in your version.  These are Euler angle calculations and the order of the calculations must match the mode that is used in the CYCLE800 block.  Here is a link that points to an article concerning Euler angles.  I would suggest that you use the new getEuler2 function that correctly calculates the Euler angles given the order specified.

https://forums.autodesk.com/t5/hsm-post-processor-forum/calculating-euler-angles/m-p/6688480#M11715

Please read over this article and see if it makes sense to you.  If you are still having problems, then you will need to provide a test case, since without the forward and right vectors that generate the CYCLE800 block I cannot make any determination.

[Anonymous]

Exactly what I was looking for! Although I've not tested yet at the machine the code matches proven code. Thank you very much for your assistance.

[Anonymous]

Thanks Bob, I've been working with Vince on this post.  We have tested it and Traori is not working correctly.  It's also outputting Traori paths for milling when they could be Swivel instead.  I have been comparing the HSM output to what our NX post outputs and it appears we are still off a bit.  It appears to me our Plane transformation is off.  When tested at the machine it appears the motion is correct or close anyway, but just not in the right spot.  I have attached our test file and the NX output file as well. I think we need some logic to look at whether its truly a five axis move or if the five axis move is just a position move for a swivel milling operation (which is turning traori on).  Maybe the logic is there in the post and I don't see it.  Could you take a look and see what we may need to do?

Thanks, Dan

[bob.schultz]

You will need to provide the HSM post processor that you are currently using to correctly analyze the output.  As far as TRAORI vs CYCLE800 goes, the post is setup to always output Multi-Axis Contour style operations using TRAORI, even if the operation is at a fixed tool axis.  If you want this style of operation output using CYCLE800 (3+2), then use a 2D Milling or 3D Milling operation instead.

[Anonymous]

Thanks Bob,

      Post is attached. I had to change the extension in order to attach it!

      I'm ok with it in TRAORI for the milling.  Ok, I didn't notice, but the paths I was expecting to be SWIVEL were in fact multi axis paths, my mistake.  However, all the TRAORI paths do not cut in the correct spots  on the part so something else is wrong with the post I think.  Maybe you can see what's wrong with the post

Thanks, Dan

[bob.schultz]

Hello Dan,

The TRAORI feature in the Siemens' control allows for Tool Control Point (TCP) programming.  In your post you enable the rotation of the tool tip coordinates for the rotary axes in the following command.

optimizeMachineAngles2(1); // map tip mode 1 is tcp mode on

Setting this value to 1 actually disables TCP mode.  You should set it to 0.

optimizeMachineAngles2(0); // map tip mode 0 is tcp mode on

I also noticed that you moved the TRAORI command to after the initial point is output in onSection (maybe because of the TCP setting).  I would suggest you move this back prior to the output of the initial position, since this position will now be output using the tool end point coordinates.

I hope this helps.

Bob