turn on suggestions

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

Showing results for

- Navigation
- NX Design
- Forums
- Blogs
- Knowledge Bases
- Groups

- Siemens PLM Community
- NX Design
- NX Design Forum
- fail to snap "Intersection"

Options

- 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

02-06-2018 11:06 AM

I have two curves on a face. I can create a point by "Intersection Point" with them.

But I fail to snap "Intersection", e.g. in creating a line with the intersection point as the start point.

Is it a bug? Thanks!

Solved! Go to Solution.

Labels:

12 REPLIES

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

02-06-2018 12:44 PM

Starting simple....do you have the intersection filter toggled on?

-Dave

NX 11 | Teamcenter 11 | Windows 10

NX 11 | Teamcenter 11 | Windows 10

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

02-06-2018 12:47 PM

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

02-06-2018 12:57 PM - edited 02-06-2018 01:07 PM

You have a small gap between the splines. If this is as intended, use the pulldown on the Point dialog and change the Type from Inferred Point to Intersection Point then select the splines one at a time. Make sure that whichever spline you want the point to lie on is the first object selected when using this method.

If you wish to close the gap, then project Composite Curve (3) and then Snap Point will work. The curve lying on the surface's trim edge is not necessary to get an intersection with Composite Curve (3).

-Tim

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

02-06-2018 01:07 PM

Hi @surfactant,

I see no reason why the intersection fails to be identified. There is a small gap and I tried adjusting tolerances with no success. If I use Project Curve to project Composite Curve(3) to the surface the intersection is found. Similarly if I create an Intersection Curve (using the original curve to create a datum plane) the intersection is found. I created additional curves on the surface, with larger gaps than Composite Curve(3), and the intersection was found.

You might want to open a case with GTAC to have development review your part and explain why it's not possible. I did find an old PR which suggested creating an Intersection Point as an intermediate step in the case where the snap intersection was not working.

Regards, Ben

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

02-06-2018 01:46 PM

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

02-07-2018 05:08 AM

Hi all, I'm still a little confused by the issue.

In "Point" > "Intersection Point" there seems to be

- no settings of tolerance and
- no projecting mechanism to get an alternative intersection point.

**Q1**: If the gap makes snap "Intersection" fail, why doesn't the gap stop "Point" > "Intersection Point" from working?

**Q2**: What does it means when "Point" > "Intersection Point" gives an intersection point associatively (successfully)?

**Success** ("Point" > "Intersection Point")

- no alert, resulting in associative point

**Failure** ("Point" > "Intersection Point")

- alert, resulting in non-associative point

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

02-07-2018 08:51 AM

Q2 - It means that it worked as it should have and the point resides on the first curve selected, as I stated above.

In the last example with the 2 Alerts (note, this is NOT a failure just a warning or information) I assume the gap is larger than the gap tolerance yet the point is still created on the first curve selected however it cannot be Associative - get the gap smaller if you want a different result.

@BenBroad, please correct me if I'm mistaken.

-Tim

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

02-07-2018 09:04 AM

Hi @TimF Thanks a lot for more explanation and sorry for some repetition!

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

02-07-2018 09:48 AM

No problem - just drill it into your head when you choose the Intersection Point (from the Point dialog's pulldown NOT the Snap Point) that the point will lie on the first object selected of the two.

Sometimes order of selecting objects in NX is VERY important.

-Tim

Follow Siemens PLM Software

© 2019 Siemens Product Lifecycle Management Software Inc