How do I get an orientation in a defined angle around the tool axis?

[denis_q]

We've implemented measuring cycles for heidenhain in our post processor.

Unfortunately, some of them only work axis parallel. (e.g. cycle 408)

So i came to following idea:

 selecting 2 edges of the pocket to define x and y axis.

But unfortunately its not that intuitive: seems as 

coordinate system displayed by HSMWorks describes an offset to the

wcs from job definition. So you have to do some magic (see attached picture).

If the operation is indexed it seems there's no chance to tackle this. 

Because the plane function only uses 2 angles

and third angle is given to setrotation!?

Forgive me if I write nonsense.

Any suggestions?

[Laurens-3DTechDraw]

---

@denis_q wrote:

We've implemented measuring cycles for heidenhain in our post processor.

Unfortunately, some of them only work axis parallel. (e.g. cycle 408)

So i came to following idea:

 selecting 2 edges of the pocket to define x and y axis.

But unfortunately its not that intuitive: seems as 

coordinate system displayed by HSMWorks describes an offset to the

wcs from job definition. So you have to do some magic (see attached picture).

If the operation is indexed it seems there's no chance to tackle this. 

Because the plane function only uses 2 angles

and third angle is given to setrotation!?

Forgive me if I write nonsense.

Any suggestions?

---

I literally don't understand what you are trying to solve.

I do know that you cannot have a rotation angle in the control when you also use Plane Spatial or Cycle 19.0.

Can you try and explain exactly what you tried and why that didn't work at the machine?

And also what you are trying to do?

[denis_q]

Given: a machine with heidenhain TNC640 control. (machineConfiguration is defined in postprocessor and 'properties.usePlane' is 'true')

Given: a pocket which edges aren't parallel to machine axis.

Wanted: measure length and width of pocket with cycle 425 (implemented in custom post processor)

problem: 425 works only axis parallel whereas pocket's edges aren't

approach: Using PLANE SPATIAL SPA+AAA SPB+BBB SPC+CCC to orientate workplane in such

way that pocket edges are axis parallel.

problem: 1. in a HSMWorks workplane definition (geometry tab in an operation) you can't (directly) specify the direction of x and y

                   axis in tilted workplane

               2. PLANE SPATIAL only get's angle around ToolAxis if it's a pure3D operation (zOriented)

hope thats better

Thanks Laurens

[Laurens-3DTechDraw]

---

@denis_q wrote:

Given: a machine with heidenhain TNC640 control. (machineConfiguration is defined in postprocessor and 'properties.usePlane' is 'true')

Given: a pocket which edges aren't parallel to machine axis.

Wanted: measure length and width of pocket with cycle 425 (implemented in custom post processor)

problem: 425 works only axis parallel whereas pocket's edges aren't

approach: Using PLANE SPATIAL SPA+AAA SPB+BBB SPC+CCC to orientate workplane in such

way that pocket edges are axis parallel.

problem: 1. in a HSMWorks workplane definition (geometry tab in an operation) you can't (directly) specify the direction of x and y

                   axis in tilted workplane

               2. PLANE SPATIAL only get's angle around ToolAxis if it's a pure3D operation (zOriented)

hope thats better

Thanks Laurens

---

Aaah,

I think I'm getting it now.

So you would want an output like 

PLANE SPATIAL SPA+90 SPB+45 SPC+33

Instead of what it does now

PLANE SPATIAL SPA+90 SPB+00 SPC+33

Because the post only makes sure the tool angle is correct but doesn't care about the other rotations in the machine.

I'm not actually sure if PLANE SPATIAL SPA+90 SPB+45 SPC+33

would work in the machine, but I like the idea.

Let's see if we can get @AchimN to help out with this.

Because before plane spatial I don't think there were machine's that would allow for such a rotation that is outside of the actual machine's rotations but can be done partially virtual.

[denis_q]

Exactly, tested it already - works 😉

[Laurens-3DTechDraw · Accepted solution]

---

@denis_q wrote:

Exactly, tested it already - works 😉

---

Wouldn't you get the output you want if you don't define your machine and use Cycle 19.0 instead of plane in the post processor?

Because it would give you Euler angles I think, which would do the trick I think.

As in in plane with machine configuration defined I get this:

21 PLANE SPATIAL SPA-90 SPB+0 SPC-89.97315 TURN FMAX SEQ- TABLE ROT

With no machine configuration defined and usePlane set to false I get this:

21 CYCL DEF 19.0 WORKING PLANE
22 CYCL DEF 19.1 A-90 B+15.70991 C-89.97315

The more I think about this is the easier you are actually making it on the post.

Because it wouldn't need to do any rotations. So this shouldn't be all too complicated if we figure out if the above works. 

[denis_q]

Thats it. Solves both problems. I will test it in the night shift.

Thank you very much.

[denis_q]

Works like a charm. Marvellous. ;-)))))