Any one can share your ideas on why the route i created, the c point connect to outside bend of the elbow instead on the c point?
I was unable to determine why your RPoint is not behaving correctly, but I did find issues in the configurations of the part you provided. I added one Coincident relation to the (Sweep) ID Cut's ID Path sketch, shown here.
That allowed the part not to fail, which is important because your CPoints are defined from subsequent faces.
One other irregularity, to me, is that your CPoints are based on one sketch, and your RPoint is based on a separate sketch.
1. Place all 3 points in the CpointSketch, conveniently with the new point located at the origin. Then try defining that as the RPoint after deleting the previous RPoint1 and Sketch1, and see if it works better. At least that's what works for me, although I do not know if doing it the way that is in this part would cause it to behave so differently.
or, 2. Just delete RPoint1 and Sketch1. Select the origin from the FM tree, and Create Route Point from that. See if this works. Initial Reference Geometry is the most stable definition you can have, so I imagine that should work well.
Post the offending Elbow pleaseThere will be an error on how it's set up.
Hi....Peter sorry for the late reply...see attached elbow part, i'm not familiar with configuration of elbow fitting i just download it from internet and i used it directly on my piping projects. Hoping for your suggestion and recommendation...
The 11th was a holiday so couldn't get back to you until now.
1. The elbow in question doesn't have a design table ?!
Which means that you're missing out on a lot of things.
2. If you run the part through the Routing Component Wizard you'll notice this
That BendAngle@ElbowArc is not only kind of nice to have it's vital
3. The way that the "arc" is dimensioned is weird
If you look at catalogs, tables or whatever you'll rarely, if ever, find the arc length being given. Normally one has the angle that the Elbow will make (90°, 45°,30°,180° for instance) and the length(s) measured from where the two lines meet to the end of the elbow. The way this elbow was set up just doesn't make sense to me and I've been in piping for 17years.
In conclusion, there's lots of things wrong with the elbow part that you have up to and including a sketch that isn't fully defined (namely the one called ID Path)
I also noticed the lack of design table and strange arc measurement: it is an oddly defined elbow part. Overall, I agree that it's the BendAngle@ElbowArc that is missing. As Peter rightly points out, all Route Parts should be processed through the wizard to verify that all required references are present. After doing this a few times, you learn what to include in new parts per type before running the wizard.
Don't you find those centerlines weird aswel?
If you mean that additional sketch just so to have a means to determine the location of Rpoint then yes.
I have no issue with having sketch lines for that reason but why not simple incorporate them in the ElbowArc sketch?
In this case however the Rpoint location is identical on the origin point so it doesn't need any additional sketch lines at all which means that Sketch1 is not needed at all.
For anything you design there's half a dozen ways to do it, some are better then others but it all depends on the wanted result.
This elbow part though does contain some features that aren't just a different way to do things but that has me puzzled about how difficult they create something.
If you switch from one config to another you'll notice that all kinds of errors pop up. It more looks as if someone took a valid elbow part and started changing it without fully knowing what they were doing.
Thanks a lot for the clarification Peter.
Retrieving data ...