<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Query Rules to create Interface to Geometry based on a Coordinate System in 3D Part &amp; Assembly Design</title>
    <link>https://www.ptcusercommunity.com/t5/3D-Part-Assembly-Design/Query-Rules-to-create-Interface-to-Geometry-based-on-a/m-p/792049#M123665</link>
    <description>&lt;P&gt;You have mentioend some good suggestions, both of which we have discussed internally at length.&amp;nbsp; This is what we have concluded:&lt;/P&gt;
&lt;OL&gt;
&lt;LI&gt;This would likely produce a giant mapkey (actually it would be 5 gient mapkeys) and I do think it would work by manually defining query placements within the mapkey and not using interfaces at all.&amp;nbsp; However, I hesitate to go in this direction as I'm concerned with the consequences of defining 5 separate constraints entirely within the mapkey or using 5 different saved queries to do similar.&amp;nbsp; It seems to me that the (5) mapkey(s) would get quite unwieldy and would be a challenge to keep updated across Creo versions.&amp;nbsp; This is at least my current perspective.&lt;/LI&gt;
&lt;LI&gt;We have several thousand (and counting) top-level assemblies.&amp;nbsp; It would not be a time saver for us to manually define surfaces in each of those to get this to work.&amp;nbsp; Although we could define this in a smaller (but still quite large) set of sub-assemblies, most of those (unfortunately) use external merge features which would likely be a highly unstable connection for named surfaces or datums.&lt;/LI&gt;
&lt;/OL&gt;
&lt;P&gt;We are also walking through the Notebook method that&amp;nbsp;&lt;a href="https://www.ptcusercommunity.com/t5/user/viewprofilepage/user-id/260992"&gt;@tbraxton&lt;/a&gt;&amp;nbsp;mentioned a few times in this thread in order to see if that gets us a little further than we currently have (and to open our eyes to new methodologies).&lt;/P&gt;</description>
    <pubDate>Tue, 26 Apr 2022 16:47:53 GMT</pubDate>
    <dc:creator>LawrenceS</dc:creator>
    <dc:date>2022-04-26T16:47:53Z</dc:date>
    <item>
      <title>Query Rules to create Interface to Geometry based on a Coordinate System</title>
      <link>https://www.ptcusercommunity.com/t5/3D-Part-Assembly-Design/Query-Rules-to-create-Interface-to-Geometry-based-on-a/m-p/790254#M123549</link>
      <description>&lt;P&gt;How do you create a component interface to Geometry feature that allow for automatic assembly (autoplace) of a component to an assembly based on a named coordinate system. We figured out how to do similar using the Interface to Interface capabilities, however that requires defining an interface in EVERY receiving assembly. We would like to do this WITHOUT adding an interface feature in every assembly.&lt;BR /&gt;&lt;BR /&gt;E.g. Align a nut to an assembly purely based off a named coordinate system using query rules defined in the component interface?&lt;BR /&gt;&lt;BR /&gt;We are using Creo4, however will be moving to Creo7 soon.&lt;/P&gt;</description>
      <pubDate>Thu, 14 Apr 2022 18:28:57 GMT</pubDate>
      <guid>https://www.ptcusercommunity.com/t5/3D-Part-Assembly-Design/Query-Rules-to-create-Interface-to-Geometry-based-on-a/m-p/790254#M123549</guid>
      <dc:creator>DayalP</dc:creator>
      <dc:date>2022-04-14T18:28:57Z</dc:date>
    </item>
    <item>
      <title>Re: Query Rules to create Interface to Geometry based on a Coordinate System</title>
      <link>https://www.ptcusercommunity.com/t5/3D-Part-Assembly-Design/Query-Rules-to-create-Interface-to-Geometry-based-on-a/m-p/790281#M123553</link>
      <description>&lt;P&gt;It is possible to enable automatic assembly using declared datums in a Notebook. No query rules or interface definitions are required to implement this using a Notebook.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Refer to this article for details and links to example models:&lt;/P&gt;
&lt;P&gt;&lt;A href="https://www.ptc.com/en/support/article/CS234134" target="_blank" rel="noopener"&gt;https://www.ptc.com/en/support/article/CS234134&lt;/A&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 14 Apr 2022 20:44:07 GMT</pubDate>
      <guid>https://www.ptcusercommunity.com/t5/3D-Part-Assembly-Design/Query-Rules-to-create-Interface-to-Geometry-based-on-a/m-p/790281#M123553</guid>
      <dc:creator>tbraxton</dc:creator>
      <dc:date>2022-04-14T20:44:07Z</dc:date>
    </item>
    <item>
      <title>Re: Query Rules to create Interface to Geometry based on a Coordinate System</title>
      <link>https://www.ptcusercommunity.com/t5/3D-Part-Assembly-Design/Query-Rules-to-create-Interface-to-Geometry-based-on-a/m-p/790506#M123567</link>
      <description>&lt;P&gt;This method worked for me:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;1) define the interface in your component and attach a query to it:&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="pausob_2-1650107262406.png" style="width: 999px;"&gt;&lt;img src="https://www.ptcusercommunity.com/t5/image/serverpage/image-id/55944i5026D880B450D528/image-size/large?v=v2&amp;amp;px=999" role="button" title="pausob_2-1650107262406.png" alt="pausob_2-1650107262406.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;2) upon assembling of this component, set it for multiple placement:&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="pausob_4-1650107505227.png" style="width: 200px;"&gt;&lt;img src="https://www.ptcusercommunity.com/t5/image/serverpage/image-id/55946i733E5C33CFF6BC89/image-size/small?v=v2&amp;amp;px=200" role="button" title="pausob_4-1650107505227.png" alt="pausob_4-1650107505227.png" /&gt;&lt;/span&gt;&amp;nbsp;-&amp;gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="pausob_6-1650107590153.png" style="width: 400px;"&gt;&lt;img src="https://www.ptcusercommunity.com/t5/image/serverpage/image-id/55948i9782F813C387330E/image-size/medium?v=v2&amp;amp;px=400" role="button" title="pausob_6-1650107590153.png" alt="pausob_6-1650107590153.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;Select the interface and click "Multiple" button.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;3) Click on the Auto Place button:&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="pausob_7-1650107672305.png" style="width: 400px;"&gt;&lt;img src="https://www.ptcusercommunity.com/t5/image/serverpage/image-id/55949iE2689D714313F833/image-size/medium?v=v2&amp;amp;px=400" role="button" title="pausob_7-1650107672305.png" alt="pausob_7-1650107672305.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;4) In the Auto Place dialog box, define the search scope (screen point method did not work for me, but selecting the top level assembly as the item did), then "Find Now", then click in the locations found list, Ctrl+A to select all, click "&amp;gt;&amp;gt;" button to transfer to the selected list:&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="pausob_8-1650107833945.png" style="width: 400px;"&gt;&lt;img src="https://www.ptcusercommunity.com/t5/image/serverpage/image-id/55950i9609B4D314A578E5/image-size/medium?v=v2&amp;amp;px=400" role="button" title="pausob_8-1650107833945.png" alt="pausob_8-1650107833945.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;5) Close the Auto Place dialog box, click the green check-mark and it is done:&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="System auto-placed the fitting according to the criteria that the mating coordinate system is named PORT*" style="width: 999px;"&gt;&lt;img src="https://www.ptcusercommunity.com/t5/image/serverpage/image-id/55951i83505C47C744A416/image-size/large?v=v2&amp;amp;px=999" role="button" title="pausob_9-1650107933998.png" alt="System auto-placed the fitting according to the criteria that the mating coordinate system is named PORT*" /&gt;&lt;span class="lia-inline-image-caption" onclick="event.preventDefault();"&gt;System auto-placed the fitting according to the criteria that the mating coordinate system is named PORT*&lt;/span&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Note: I needed to change few settings in the "Assembly" section of the Creo Parametric Options for the above dialog boxes and the "Auto Place" button to show up during the assembly process:&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="pausob_3-1650107402705.png" style="width: 400px;"&gt;&lt;img src="https://www.ptcusercommunity.com/t5/image/serverpage/image-id/55945iFD1F1A5A9FA77513/image-size/medium?v=v2&amp;amp;px=400" role="button" title="pausob_3-1650107402705.png" alt="pausob_3-1650107402705.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sat, 16 Apr 2022 11:23:35 GMT</pubDate>
      <guid>https://www.ptcusercommunity.com/t5/3D-Part-Assembly-Design/Query-Rules-to-create-Interface-to-Geometry-based-on-a/m-p/790506#M123567</guid>
      <dc:creator>pausob</dc:creator>
      <dc:date>2022-04-16T11:23:35Z</dc:date>
    </item>
    <item>
      <title>Re: Query Rules to create Interface to Geometry based on a Coordinate System</title>
      <link>https://www.ptcusercommunity.com/t5/3D-Part-Assembly-Design/Query-Rules-to-create-Interface-to-Geometry-based-on-a/m-p/790812#M123586</link>
      <description>&lt;P&gt;&lt;a href="https://www.ptcusercommunity.com/t5/user/viewprofilepage/user-id/260992"&gt;@tbraxton&lt;/a&gt;, I work with Dayal who posted this.&amp;nbsp; We have never used notebooks for anything and are totally unfamiliar with them so will have to look into them some more.&amp;nbsp; If you have any good material on using them please post if you have a moment.&amp;nbsp;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 19 Apr 2022 16:01:47 GMT</pubDate>
      <guid>https://www.ptcusercommunity.com/t5/3D-Part-Assembly-Design/Query-Rules-to-create-Interface-to-Geometry-based-on-a/m-p/790812#M123586</guid>
      <dc:creator>LawrenceS</dc:creator>
      <dc:date>2022-04-19T16:01:47Z</dc:date>
    </item>
    <item>
      <title>Re: Query Rules to create Interface to Geometry based on a Coordinate System</title>
      <link>https://www.ptcusercommunity.com/t5/3D-Part-Assembly-Design/Query-Rules-to-create-Interface-to-Geometry-based-on-a/m-p/790813#M123587</link>
      <description>&lt;P&gt;&lt;a href="https://www.ptcusercommunity.com/t5/user/viewprofilepage/user-id/274312"&gt;@pausob&lt;/a&gt;, To be clear, the method you are describing is for Interface to Geometry, not interface to interface, right?&lt;/P&gt;</description>
      <pubDate>Tue, 19 Apr 2022 16:03:42 GMT</pubDate>
      <guid>https://www.ptcusercommunity.com/t5/3D-Part-Assembly-Design/Query-Rules-to-create-Interface-to-Geometry-based-on-a/m-p/790813#M123587</guid>
      <dc:creator>LawrenceS</dc:creator>
      <dc:date>2022-04-19T16:03:42Z</dc:date>
    </item>
    <item>
      <title>Re: Query Rules to create Interface to Geometry based on a Coordinate System</title>
      <link>https://www.ptcusercommunity.com/t5/3D-Part-Assembly-Design/Query-Rules-to-create-Interface-to-Geometry-based-on-a/m-p/790824#M123588</link>
      <description>&lt;P&gt;Hi @&lt;SPAN&gt;&lt;STRONG&gt;DP_9634838,&lt;/STRONG&gt;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;&lt;STRONG&gt;Please see the attached video for more information. Hope this helps.&amp;nbsp;&lt;/STRONG&gt;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;&lt;STRONG&gt;Thanks,&lt;/STRONG&gt;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;&lt;STRONG&gt;Vipul&lt;/STRONG&gt;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;div class="lia-vid-container video-embed-center"&gt;&lt;div id="lia-vid-6304413045001w1004h540r925" class="lia-video-brightcove-player-container"&gt;&lt;video-js data-video-id="6304413045001" data-account="6058022026001" data-player="default" data-embed="default" class="vjs-fluid" controls="" data-application-id="" style="width: 100%; height: 100%;"&gt;&lt;/video-js&gt;&lt;/div&gt;&lt;script src="https://players.brightcove.net/6058022026001/default_default/index.min.js"&gt;&lt;/script&gt;&lt;script&gt;(function() {  var wrapper = document.getElementById('lia-vid-6304413045001w1004h540r925');  var videoEl = wrapper ? wrapper.querySelector('video-js') : null;  if (videoEl) {     if (window.videojs) {       window.videojs(videoEl).ready(function() {         this.on('loadedmetadata', function() {           this.el().querySelectorAll('.vjs-load-progress div[data-start]').forEach(function(bar) {             bar.setAttribute('role', 'presentation');             bar.setAttribute('aria-hidden', 'true');           });         });       });     }  }})();&lt;/script&gt;&lt;a class="video-embed-link" href="https://www.ptcusercommunity.com/t5/video/gallerypage/video-id/6304413045001"&gt;(view in My Videos)&lt;/a&gt;&lt;/div&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 19 Apr 2022 16:54:55 GMT</pubDate>
      <guid>https://www.ptcusercommunity.com/t5/3D-Part-Assembly-Design/Query-Rules-to-create-Interface-to-Geometry-based-on-a/m-p/790824#M123588</guid>
      <dc:creator>VipulT</dc:creator>
      <dc:date>2022-04-19T16:54:55Z</dc:date>
    </item>
    <item>
      <title>Re: Query Rules to create Interface to Geometry based on a Coordinate System</title>
      <link>https://www.ptcusercommunity.com/t5/3D-Part-Assembly-Design/Query-Rules-to-create-Interface-to-Geometry-based-on-a/m-p/790827#M123589</link>
      <description>&lt;P&gt;Hi &lt;a href="https://www.ptcusercommunity.com/t5/user/viewprofilepage/user-id/213661"&gt;@LawrenceS&lt;/a&gt;, I would say I showed a component with an interface being "semi-automatically" assembled to geometry in multiple places &lt;span class="lia-unicode-emoji" title=":grinning_face_with_smiling_eyes:"&gt;😄&lt;/span&gt;.&amp;nbsp; Maybe with a clever mapkey it could become a 1-button operation.&lt;/P&gt;</description>
      <pubDate>Tue, 19 Apr 2022 17:02:24 GMT</pubDate>
      <guid>https://www.ptcusercommunity.com/t5/3D-Part-Assembly-Design/Query-Rules-to-create-Interface-to-Geometry-based-on-a/m-p/790827#M123589</guid>
      <dc:creator>pausob</dc:creator>
      <dc:date>2022-04-19T17:02:24Z</dc:date>
    </item>
    <item>
      <title>Re: Query Rules to create Interface to Geometry based on a Coordinate System</title>
      <link>https://www.ptcusercommunity.com/t5/3D-Part-Assembly-Design/Query-Rules-to-create-Interface-to-Geometry-based-on-a/m-p/791299#M123631</link>
      <description>&lt;P&gt;&lt;a href="https://www.ptcusercommunity.com/t5/user/viewprofilepage/user-id/299047"&gt;@VipulT&lt;/a&gt;, Thank you very much for the video and explanation, as we have it working almost perfectly.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;After further testing we have run into a problem where it is trying to assemble to coordinate systems within other sub-components.&amp;nbsp; As far as we can tell, the multiple locations autoplace doesn't distinguish between datums within sub-components and top-level datums, nor could we figure out how to specify this in the placing component Interface feature.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;How do we specify to only use the named coordinates in the top-level assembly?&lt;/P&gt;</description>
      <pubDate>Thu, 21 Apr 2022 21:59:44 GMT</pubDate>
      <guid>https://www.ptcusercommunity.com/t5/3D-Part-Assembly-Design/Query-Rules-to-create-Interface-to-Geometry-based-on-a/m-p/791299#M123631</guid>
      <dc:creator>LawrenceS</dc:creator>
      <dc:date>2022-04-21T21:59:44Z</dc:date>
    </item>
    <item>
      <title>Re: Query Rules to create Interface to Geometry based on a Coordinate System</title>
      <link>https://www.ptcusercommunity.com/t5/3D-Part-Assembly-Design/Query-Rules-to-create-Interface-to-Geometry-based-on-a/m-p/791305#M123632</link>
      <description>&lt;P&gt;PS.&lt;/P&gt;
&lt;P&gt;We already tried using the below methods and they don't seem to work on Creo4 (M140 and M150):&lt;/P&gt;
&lt;OL&gt;
&lt;LI&gt;Creo Option: &lt;STRONG&gt;Include sub-model interfaces as possible references for interface-to-interface placement&lt;/STRONG&gt;
&lt;UL&gt;
&lt;LI&gt;Unchecking the Creo option and hitting save does not stick.&amp;nbsp; When we go back into the Creo options to verify it is unchecked we find that it has rechecked itself.&amp;nbsp; It simply does NOT save.&lt;/LI&gt;
&lt;/UL&gt;
&lt;/LI&gt;
&lt;LI&gt;Config.pro: &lt;STRONG&gt;include_sub_model_interfaces no&lt;/STRONG&gt;
&lt;UL&gt;
&lt;LI&gt;setting the config.pro option and restarting Creo doesn't control the above checkbox, and it keeps trying to assembly to the sub-component constraints.&lt;/LI&gt;
&lt;/UL&gt;
&lt;/LI&gt;
&lt;/OL&gt;
&lt;P&gt;However, for this new process to work we really need to choose top level assembly references/coordinate system only.&amp;nbsp; Any ideas?&lt;/P&gt;</description>
      <pubDate>Thu, 21 Apr 2022 23:11:24 GMT</pubDate>
      <guid>https://www.ptcusercommunity.com/t5/3D-Part-Assembly-Design/Query-Rules-to-create-Interface-to-Geometry-based-on-a/m-p/791305#M123632</guid>
      <dc:creator>LawrenceS</dc:creator>
      <dc:date>2022-04-21T23:11:24Z</dc:date>
    </item>
    <item>
      <title>Re: Query Rules to create Interface to Geometry based on a Coordinate System</title>
      <link>https://www.ptcusercommunity.com/t5/3D-Part-Assembly-Design/Query-Rules-to-create-Interface-to-Geometry-based-on-a/m-p/791322#M123633</link>
      <description>&lt;P&gt;How about activate Insert mode and do the above procedure before any other sub-component is present in your assembly?&amp;nbsp; &amp;nbsp;That way only the top-level assembly datums will be "found"...&lt;/P&gt;</description>
      <pubDate>Fri, 22 Apr 2022 02:36:07 GMT</pubDate>
      <guid>https://www.ptcusercommunity.com/t5/3D-Part-Assembly-Design/Query-Rules-to-create-Interface-to-Geometry-based-on-a/m-p/791322#M123633</guid>
      <dc:creator>pausob</dc:creator>
      <dc:date>2022-04-22T02:36:07Z</dc:date>
    </item>
    <item>
      <title>Re: Query Rules to create Interface to Geometry based on a Coordinate System</title>
      <link>https://www.ptcusercommunity.com/t5/3D-Part-Assembly-Design/Query-Rules-to-create-Interface-to-Geometry-based-on-a/m-p/791446#M123639</link>
      <description>Yes, this is a good idea for assembling the component to an EXISTING DEFAULT DATUM FEATURES. I need to use one the component surface as a constraint to locate the part.&lt;BR /&gt;</description>
      <pubDate>Fri, 22 Apr 2022 16:00:44 GMT</pubDate>
      <guid>https://www.ptcusercommunity.com/t5/3D-Part-Assembly-Design/Query-Rules-to-create-Interface-to-Geometry-based-on-a/m-p/791446#M123639</guid>
      <dc:creator>DayalP</dc:creator>
      <dc:date>2022-04-22T16:00:44Z</dc:date>
    </item>
    <item>
      <title>Re: Query Rules to create Interface to Geometry based on a Coordinate System</title>
      <link>https://www.ptcusercommunity.com/t5/3D-Part-Assembly-Design/Query-Rules-to-create-Interface-to-Geometry-based-on-a/m-p/791502#M123640</link>
      <description>&lt;P&gt;So you do want to reference the sub-component geometry?&amp;nbsp; but only 1-level deep?&amp;nbsp; Anyway, it seems that auto-place tool doesn't give you many options as far as filtering that list of found locations, so&amp;nbsp;seems you should raise a product enhancement idea...&lt;/P&gt;
&lt;P&gt;Also, this thread:&lt;/P&gt;
&lt;P&gt;&lt;A href="https://community.ptc.com/t5/3D-Part-Assembly-Design/Auto-assemble-multiple-components-by-coordinate-in-selecting/m-p/614943" target="_blank" rel="noopener"&gt;Auto assemble multiple components by coordinate in selecting multiple coordinates in top assembly&lt;/A&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;has links to other softwares that you may want to evaluate to see if they fulfill your needs.&lt;/P&gt;</description>
      <pubDate>Fri, 22 Apr 2022 19:03:15 GMT</pubDate>
      <guid>https://www.ptcusercommunity.com/t5/3D-Part-Assembly-Design/Query-Rules-to-create-Interface-to-Geometry-based-on-a/m-p/791502#M123640</guid>
      <dc:creator>pausob</dc:creator>
      <dc:date>2022-04-22T19:03:15Z</dc:date>
    </item>
    <item>
      <title>Re: Query Rules to create Interface to Geometry based on a Coordinate System</title>
      <link>https://www.ptcusercommunity.com/t5/3D-Part-Assembly-Design/Query-Rules-to-create-Interface-to-Geometry-based-on-a/m-p/791503#M123641</link>
      <description>&lt;P&gt;Using the Notebook to control auto assembly this could solve this issue. The automatic assembly would only happen if the Notebook is declared to a model. You can declare/undeclare the Notebook used to each model as required.&lt;/P&gt;</description>
      <pubDate>Fri, 22 Apr 2022 19:07:08 GMT</pubDate>
      <guid>https://www.ptcusercommunity.com/t5/3D-Part-Assembly-Design/Query-Rules-to-create-Interface-to-Geometry-based-on-a/m-p/791503#M123641</guid>
      <dc:creator>tbraxton</dc:creator>
      <dc:date>2022-04-22T19:07:08Z</dc:date>
    </item>
    <item>
      <title>Re: Query Rules to create Interface to Geometry based on a Coordinate System</title>
      <link>https://www.ptcusercommunity.com/t5/3D-Part-Assembly-Design/Query-Rules-to-create-Interface-to-Geometry-based-on-a/m-p/791741#M123642</link>
      <description>&lt;P&gt;I have been trying to understand how these Notebooks/Layouts work and it is very interesting functionality.&amp;nbsp; Thanks again for sharing it.&amp;nbsp;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Please correct me if I am wrong, but using Notebooks requires the receiving asm/prt to have a Notebook definition tied to it.&amp;nbsp; In the case we have, we have many thousands of unique receiving assemblies. In addition, we don't have a common part that could have a notebook tied to it either.&amp;nbsp; It seems we would require a Notebook for every receiving assembly, or a notebook for every component it could be tied to, which both would be a more painful solution to create/maintain than what it alleviates.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Do I understand this correctly, or is there a way around this?&lt;/P&gt;</description>
      <pubDate>Mon, 25 Apr 2022 14:50:17 GMT</pubDate>
      <guid>https://www.ptcusercommunity.com/t5/3D-Part-Assembly-Design/Query-Rules-to-create-Interface-to-Geometry-based-on-a/m-p/791741#M123642</guid>
      <dc:creator>LawrenceS</dc:creator>
      <dc:date>2022-04-25T14:50:17Z</dc:date>
    </item>
    <item>
      <title>Re: Query Rules to create Interface to Geometry based on a Coordinate System</title>
      <link>https://www.ptcusercommunity.com/t5/3D-Part-Assembly-Design/Query-Rules-to-create-Interface-to-Geometry-based-on-a/m-p/791755#M123643</link>
      <description>&lt;P&gt;&lt;a href="https://www.ptcusercommunity.com/t5/user/viewprofilepage/user-id/274312"&gt;@pausob&lt;/a&gt;, DayalP's comment on your clever workaround to suppress all components in assembly before assembling, must seem like a contradiction to our original question.&amp;nbsp; We posted on a simplified version of what we really want using only a coordinate system, as it is easier to explain and if we can get that to work then we can get the slightly more complex version to work.&amp;nbsp; We are actually assembling based on 3 consistently named datums/axis, then we remove one of the assembly constraints to allow for the user to choose an assembly surface that there is not defined as special in the actual model.&amp;nbsp; We automate this using a mapkey, so the user only clicks the mapkey, chooses the unique surface and the component is fully assembled.&amp;nbsp; We could have the mapkey suppress/insert mode but then the next part of the mapkey where the user chooses the surface wouldn't be possible.&amp;nbsp; We will look into a method of suppressing/un-suppressing while assembling but think it will complicate the mapkey tremendously.&amp;nbsp;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;That is the background on why I don't think the suppressing workaround will work in this case, however the original question of using a query to define in the component how that component will get assembled in the top level assembly still holds.&amp;nbsp; I didn't anticipate that it would be hard for Creo to query only top-level datums, as that is actually a normal query feature.&amp;nbsp; In addition, for some reason the config.pro option and the Creo assembly option doesn't seem to be working, which would allow for us to specify to only look at the top level assembly.&amp;nbsp; It seems that this functionality is broken.&amp;nbsp; We will also see how it works in Creo7...&lt;/P&gt;</description>
      <pubDate>Mon, 25 Apr 2022 15:24:05 GMT</pubDate>
      <guid>https://www.ptcusercommunity.com/t5/3D-Part-Assembly-Design/Query-Rules-to-create-Interface-to-Geometry-based-on-a/m-p/791755#M123643</guid>
      <dc:creator>LawrenceS</dc:creator>
      <dc:date>2022-04-25T15:24:05Z</dc:date>
    </item>
    <item>
      <title>Re: Query Rules to create Interface to Geometry based on a Coordinate System</title>
      <link>https://www.ptcusercommunity.com/t5/3D-Part-Assembly-Design/Query-Rules-to-create-Interface-to-Geometry-based-on-a/m-p/791764#M123644</link>
      <description>&lt;P&gt;You must create a Notebook that defines the assembly constraints for the two models to be automatically assembled. You must declare this notebook to the two models.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;If you are familiar with programming structure, think of a Notebook as a declaration of global variables and functions that can be accessed by other programs (models) when declared to the model.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Without understanding exactly how you are auto assembling I can not comment on how many Notebook files would be required. If you are clever about standardizing the assembly references in the models you should be able use a single notebook to assemble parts infinitely.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I assume you have parts that you reuse often, if so you can create a standard such that the part would auto assemble to any assembly designed to receive it once you declare the Notebook used to define the constraints to the receiving model and your library part designed for auto placement.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I present it as an option for auto assembly, it may be better than a query approach. If you post a sample data set representative of the issue then I would be able to consider what would work.&lt;/P&gt;</description>
      <pubDate>Mon, 25 Apr 2022 15:36:17 GMT</pubDate>
      <guid>https://www.ptcusercommunity.com/t5/3D-Part-Assembly-Design/Query-Rules-to-create-Interface-to-Geometry-based-on-a/m-p/791764#M123644</guid>
      <dc:creator>tbraxton</dc:creator>
      <dc:date>2022-04-25T15:36:17Z</dc:date>
    </item>
    <item>
      <title>Re: Query Rules to create Interface to Geometry based on a Coordinate System</title>
      <link>https://www.ptcusercommunity.com/t5/3D-Part-Assembly-Design/Query-Rules-to-create-Interface-to-Geometry-based-on-a/m-p/791839#M123647</link>
      <description>&lt;P&gt;As it is, I'm guessing you are auto-assembling &lt;STRONG&gt;(a single component ?)&lt;/STRONG&gt; using an interface to consistently-named datum geom, then replacing one of the constraints to be aligned with some surface of interest found in current context.&amp;nbsp;&amp;nbsp;That whole process seems challenging to encode into a mapkey without pauses, etc..., so I'd be quite interested to know how you accomplish that.&amp;nbsp; Would you be able to share a model / mapkey example?&lt;/P&gt;
&lt;P&gt;And during this process, the system presents you with unwanted locations because it finds same-named datums in other sub-components?&lt;/P&gt;
&lt;P&gt;So is the sticking point is having users specify one of several locations that come up in the auto-place function?&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I can think of two other things:&lt;/P&gt;
&lt;P&gt;1) maybe you can do this whole thing by simply incorporating search queries in your mapkey at the time of standard placement process.&amp;nbsp; The placement surface is clicked and then mapkey is run.&amp;nbsp; It brings in the component and aligns an internal named datum to the pre-selected surface.&amp;nbsp; The other two constraints are done by searching for the named datums - this can be done "in top level" only...&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;2) note that you can give names to surfaces so I am thinking of another&amp;nbsp;approach: create the placement surface in the top-level assembly (i.e. copy it from the sub-component), and name it something that matches the query criteria in your hardware component.&amp;nbsp; This can be done in a mapkey as you can look for that surface by the "last" feature made.&amp;nbsp; Though the name you give it will be static... Yeah, I think mapkeys are not very good here; this definitely seems like an abuse of their limited powers&amp;nbsp; - whole lot of extra work, and you make 1 extra feature in the model tree.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Anyway, happy hacking!&lt;/P&gt;</description>
      <pubDate>Mon, 25 Apr 2022 22:56:31 GMT</pubDate>
      <guid>https://www.ptcusercommunity.com/t5/3D-Part-Assembly-Design/Query-Rules-to-create-Interface-to-Geometry-based-on-a/m-p/791839#M123647</guid>
      <dc:creator>pausob</dc:creator>
      <dc:date>2022-04-25T22:56:31Z</dc:date>
    </item>
    <item>
      <title>Re: Query Rules to create Interface to Geometry based on a Coordinate System</title>
      <link>https://www.ptcusercommunity.com/t5/3D-Part-Assembly-Design/Query-Rules-to-create-Interface-to-Geometry-based-on-a/m-p/792011#M123661</link>
      <description>Do you have any video showing step by step process creating and declaring Notebook in assembly and part, and then add part to the assembly? If yes, please send me.&lt;BR /&gt;I need to see examples to create one myself. Thank you.&lt;BR /&gt;</description>
      <pubDate>Tue, 26 Apr 2022 14:27:59 GMT</pubDate>
      <guid>https://www.ptcusercommunity.com/t5/3D-Part-Assembly-Design/Query-Rules-to-create-Interface-to-Geometry-based-on-a/m-p/792011#M123661</guid>
      <dc:creator>DayalP</dc:creator>
      <dc:date>2022-04-26T14:27:59Z</dc:date>
    </item>
    <item>
      <title>Re: Query Rules to create Interface to Geometry based on a Coordinate System</title>
      <link>https://www.ptcusercommunity.com/t5/3D-Part-Assembly-Design/Query-Rules-to-create-Interface-to-Geometry-based-on-a/m-p/792029#M123662</link>
      <description>&lt;P&gt;I don't have anything I can share in this forum. When I get some time I will create a simple example. What version of Creo are you working in currently?&lt;/P&gt;</description>
      <pubDate>Tue, 26 Apr 2022 15:42:05 GMT</pubDate>
      <guid>https://www.ptcusercommunity.com/t5/3D-Part-Assembly-Design/Query-Rules-to-create-Interface-to-Geometry-based-on-a/m-p/792029#M123662</guid>
      <dc:creator>tbraxton</dc:creator>
      <dc:date>2022-04-26T15:42:05Z</dc:date>
    </item>
    <item>
      <title>Re: Query Rules to create Interface to Geometry based on a Coordinate System</title>
      <link>https://www.ptcusercommunity.com/t5/3D-Part-Assembly-Design/Query-Rules-to-create-Interface-to-Geometry-based-on-a/m-p/792031#M123663</link>
      <description>[cid:image001.png@01D8595A.9D3C67E0]&lt;BR /&gt;&lt;BR /&gt;Thank you.&lt;BR /&gt;</description>
      <pubDate>Tue, 26 Apr 2022 15:45:59 GMT</pubDate>
      <guid>https://www.ptcusercommunity.com/t5/3D-Part-Assembly-Design/Query-Rules-to-create-Interface-to-Geometry-based-on-a/m-p/792031#M123663</guid>
      <dc:creator>DayalP</dc:creator>
      <dc:date>2022-04-26T15:45:59Z</dc:date>
    </item>
  </channel>
</rss>

