Turn on suggestions

Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.

Showing results for

- Siemens PLM Community
- NX Manufacturing
- Discussion Forum - NX Manufacturing
- Helix move, revolutions limit

Options

- Start Article
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page

- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content

05-08-2019 09:12 AM

Hello,

When post processing a helix with a Heidenhain_conversational_advanced in PB, I realized that there is a limit of 1000 (or 360000 degrees) for revolutions.

The output is devided to equal helixes when it is more than 1000 Rev, in order to make each helix less than 1000.

Is there any way to increase it? What parameter controls this?

kind regards,

Majid

Majid

Solved! Go to Solution.

11 REPLIES 11

Re: Helix move, revolutions limit

- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content

05-08-2019 11:57 AM

Hello

As i know for Heidenhain there is a limit of 15 turns. (5400 degree). Maybe that newer HH controller TNC640 have higher limits. You have to split up a Helix move in the post.

If you use PostConfigurator then its done automatical!

Regards

Re: Helix move, revolutions limit

- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content

05-08-2019 02:00 PM - edited 05-08-2019 04:13 PM

Youre right newer Heidenhain versions have bigger limit than 5400 deg.

I test PB library Heidenhain_conversational_advanced and output is: (bigger than 5400, I think it is without limit)

CP IPA14400. IZ-8. DR+

If you want to split angle by some limiting angle you have to program logic in **pb_cmd_helix**.

In short - take whole arc angle, divide it by limiting angle (for example 5400) and per this limiting angle output CP IPA(5400) with correct Z depth(!)

Then there is some residual angle from whole angle, so at last, you have to output CP IPA(residual angle) to final Z depth(!)

CP IPA+5400 Z+0 DR+ CP IPA+5400 Z-3 DR+ CP IPA+3600 Z-5 DR+ (residual)

Postconfigurator has it working for 5400deg but dont know how to overide it.

Maybe user should overide whole output by custom proc. Dont know if it is simple.

---------------------------------------------

#♫ PB, 5ax, itnc, nx, vericut ♫ #

#♫ PB, 5ax, itnc, nx, vericut ♫ #

Re: Helix move, revolutions limit

- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content

05-08-2019 02:40 AM

Hello,

I'm not sure why my last comment was deleted!? But in brief:

Thanks for your replies.

Imagine a hole milling operation, 10 mm depth, 0.01mm axial distance. The helix will have 1000 turns (360000 degrees) as follows:

CP IPA360000. IZ-10. DR+

Changing the distance to 0.009 mm and NX will devide the helix into two identical helixes each 5 mm depth:

CP IPA200000. IZ-5. DR+

CP IPA200000. IZ-5. DR+

I need to output the second one as one helix as follows:

CP IPA400000. IZ-10. DR+

This is independent from Heidenhain IPA limitation since I made a PP that the user can choose IPA or CYCLE output. It analyzes the output for hole / boss / milling / threading and converts it to CYCL_262 / CYCL_208 / CYCL_257 / CYCL_267.

The logic works perfect as long as ONE helix is ONE event

10mm depth 0.01mm divisions makes one 360000 degrees helix:

CYCL DEF 208 Q200=0. Q201=-10. Q206=1000. Q334=0.01 Q203=0. Q204=0. Q335=10. Q342=10. Q351=1.

CYCL CALL

The same operation with 0.009mm divisions makes two helix events each 200000 degree and 5 mm depth. This is what I do NOT want in output:

CYCL DEF 208 Q200=0. Q201=-5. Q206=1000. Q334=0.009 Q203=0. Q204=0. Q335=10. Q342=10. Q351=1.

CYCL CALL

CYCL DEF 208 Q200=0. Q201=-5. Q206=1000. Q334=0.009 Q203=0. Q204=0. Q335=10. Q342=10. Q351=1.

CYCL CALL

If NX makes it one helix my output will be:

CYCL DEF 208 Q200=0. Q201=-10. Q206=1000. Q334=0.009 Q203=0. Q204=0. Q335=10. Q342=10. Q351=1.

CYCL CALL

Kind regards,

Majid

Majid

Re: Helix move, revolutions limit

- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content

05-09-2019 03:00 AM - edited 05-09-2019 03:09 AM

Hi,

I think I see what you mean.

Long helix is devided on half in NX.

So there is 2 events, thats mean 2 output of helix

I ve never did such long helix.

I think library template PP heidenhain_conversational_advanced could output helix without limitation of the angle

* CP IPA400000. IZ-10. DR+*

but NX makes 2x helix:

* CP IPA200000. IZ-5. DR+** CP IPA200000. IZ-5. DR+*

So I assume this is question for siemens

---------------------------------------------

#♫ PB, 5ax, itnc, nx, vericut ♫ #

#♫ PB, 5ax, itnc, nx, vericut ♫ #

Re: Helix move, revolutions limit

- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content

05-09-2019 03:41 AM

Hi,

Thats right. We can see it on CLS too:

CIRCLE/-17.5286,0.7213,-10.0000,0.0000000,0.0000000,-1.0000000,5.0000,0.0600,0.5000,8.0000,0.0000,TIMES,1000

comparing to:

CIRCLE/-17.5286,0.7213,-5.0000,0.0000000,0.0000000,-1.0000000,5.0000,0.0600,0.5000,8.0000,0.0000,TIMES,556

CIRCLE/-17.5286,0.7213,-10.0000,0.0000000,0.0000000,-1.0000000,5.0000,0.0600,0.5000,8.0000,0.0000,TIMES,556

So the question now is how to increase this TIMES value limitation more than 1000!?

Kind regards,

Majid

Majid

Re: Helix move, revolutions limit

- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content

05-09-2019 04:36 AM

I think we cant control how internaly is helix created

Ask GTAC for explanation or some kind of help

---------------------------------------------

#♫ PB, 5ax, itnc, nx, vericut ♫ #

#♫ PB, 5ax, itnc, nx, vericut ♫ #

- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content

05-09-2019 05:24 AM

Hello,

Thanks for the information.

I realized that when this happens, for the initial helix segments we have:

mom_pos(2) != mom_nxt_pos(2)

and for the last segment we have:

mom_pos(2) == mom_nxt_pos(2)

Using this condition, I changed my codes to output only one CYCLE with total depth of the splitted helix and works perfect.

Kind regards,

Majid

Majid

Re: Helix move, revolutions limit

- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content

05-09-2019 07:20 AM

Hi Majid,

Good to hear that were able to generate your canned hole milling cycles.

I'd like to add that nx1847 provides __preview__ functionality to generate canned hole milling cycles.

(and nx1872 provides __preview__ functionality to generate canned hole __thread__ milling cycles)

We're in the process of collecting feedback. We will probably release this in the (very) near future.

(Contact BobWijers for activation instructions in case you would like to activate and test it in nx1847)

Note that I can confirm that hole milling uses a max of 1000 turns per helix. On itself "a" limit is needed (at the time of definition 1000 had been considered large enough for the anticipated application) but the current value is more or less arbitrary....

Thanks,

Toon

Re: Helix move, revolutions limit

- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content

05-09-2019 08:02 AM

hi @ToonVdK Bob was logged last time in 2018, is there any other way to contact him ?

---------------------------------------------

#♫ PB, 5ax, itnc, nx, vericut ♫ #

#♫ PB, 5ax, itnc, nx, vericut ♫ #

**Learning Advantage** Learn NX CAM online at your own pace (Login required)

**Manufacturing Tutorials**

Already have NX CAM installed? Get hands-on with the in-software tutorials

**Product Support**

Contact Global Technical Access Center (GTAC)

Follow Siemens PLM Software

© 2019 Siemens Product Lifecycle Management Software Inc