×
INTELLIGENT WORK FORUMS
FOR ENGINEERING PROFESSIONALS

Log In

Come Join Us!

Are you an
Engineering professional?
Join Eng-Tips Forums!
  • Talk With Other Members
  • Be Notified Of Responses
    To Your Posts
  • Keyword Search
  • One-Click Access To Your
    Favorite Forums
  • Automated Signatures
    On Your Posts
  • Best Of All, It's Free!
  • Students Click Here

*Eng-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail.

Posting Guidelines

Promoting, selling, recruiting, coursework and thesis posting is forbidden.

Students Click Here

Jobs

NX3/winXp, Crosshatching question

NX3/winXp, Crosshatching question

NX3/winXp, Crosshatching question

(OP)
Another question about one of our tedious tasks.

We usually have to add a view on our drawings showing what areas of the part gets bonding.  How we achieve this is by expanding the view, extracting lines, back to the drawing and adding crosshatch to the view (using the lines we extracted or silhouette curves the drawing extracts).

This is a huge time sink.  We have to redo the cross-hatch a lot, from small minor updates to major updates to the part.

Anyone have any ideas, or deal with this that can maybe shed some light.

Thank you.

Justin Ackley
Designer

RE: NX3/winXp, Crosshatching question

I'm interested in an answer to this also.  We do as you do, except we put the xhatch in the view.

RE: NX3/winXp, Crosshatching question

(OP)
Yea some of the guys here do that as well.  I like it on the drawing so I don't have to expand to the view to update the hatch.

Justin Ackley
Designer

RE: NX3/winXp, Crosshatching question

If you have really complicated contoured parts that are bonded, painted or grained over wide areas, why not adopt a standard whereby you extract the region that is affected to a specific categorized layer and nominate where it is to be found in the 3D data as part of the drawing notes. Time comes when you can't see the whole affected area in a single view, then that's what 3D data is all about.

However, with simpler defined areas I might define the boundaries of target regions as curves, especially if edge curves aren't going to be available in the solid model for example. Where we differ is that I'd try to do this in modeling space, on a separate layer from the model. I would create the drawing mostly with just the model visible, and in the view or views where you need to call up the affected regions make the layer with the curves visible, and then use them for the hatched regions.

In order to make the regions very easy to maintain you can try using the join curves command to create a closed boundary, because it will only take one selection to crosshatch. If you create the boundary with curves or lines that you may later wish to change then why not place them on their own layer that stays hidden. then keep the joined curve associative to them. All this may sound somewhat complicated, but it sure is easier to maintain than anything that involves picking and re-picking crosshatch boundaries in drafting.

As for the hatching itself, it lives on the drawing, (i.e. expand member view is not used). Others may differ, but I find this method easy and works for me.

Best Regards

Hudson

Red Flag This Post

Please let us know here why this post is inappropriate. Reasons such as off-topic, duplicates, flames, illegal, vulgar, or students posting their homework.

Red Flag Submitted

Thank you for helping keep Eng-Tips Forums free from inappropriate posts.
The Eng-Tips staff will check this out and take appropriate action.

Reply To This Thread

Posting in the Eng-Tips forums is a member-only feature.

Click Here to join Eng-Tips and talk with other members!


Resources