End Condition Targeting a Feature Definition Both Horizontal and Vertical

RE: End Condition Targeting a Feature Definition Both Horizontal and Vertical

Abhiram Supekar — Tue, 14 Aug 2018 12:50:25 GMT

Hello,

I have exactly similar case. It is working as stated above. But, vertically it is not targeting. Do I need to give any "Vertical Offset" value?

I am targeting ditch alignment/profile which is in parts & pieces.

Suggestions please!

RE: End Condition Targeting a Feature Definition Both Horizontal and Vertical

MaryB — Fri, 07 Apr 2017 21:24:24 GMT

That is beautiful - I had no idea where to find end condition target feature. I'd only used features as point control. Nice to see where that is, and you may have just solved a couple of questions I had. Thank you!!

RE: End Condition Targeting a Feature Definition Both Horizontal and Vertical

TWalters — Fri, 07 Apr 2017 21:12:17 GMT

Maybe this will help clear it up.

RE: End Condition Targeting a Feature Definition Both Horizontal and Vertical

TWalters — Fri, 07 Apr 2017 21:00:30 GMT

Mary are you responding to me or to Marc? Was me discription any help? I can email you my template if that is helpful at all... just PM me.

RE: End Condition Targeting a Feature Definition Both Horizontal and Vertical

MaryB — Fri, 07 Apr 2017 20:06:45 GMT

How would we do that (more specifically)? Can you elaborate?

RE: End Condition Targeting a Feature Definition Both Horizontal and Vertical

TWalters — Fri, 07 Apr 2017 19:21:03 GMT

Worked like a charm! Thank you.

I set the end condition component to target the vertical of the feature definition only. Then used a horizontal feature definition overrided on the point at the end of the end condtion. This let me define the direction and search distance. Updated template and no more crossing features.

Thanks again for the help,

Terry

RE: End Condition Targeting a Feature Definition Both Horizontal and Vertical

Marc Bachand — Fri, 07 Apr 2017 11:10:59 GMT

You need to target XY first, then Z in a 2 step EC branch.