<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: When in doubt&#8230; Check the mates in your subassemblies!</title>
	<atom:link href="http://gabijack.com/2008/09/when-in-doubt-check-the-mates-in-your-subassemblies/feed/" rel="self" type="application/rss+xml" />
	<link>http://gabijack.com/2008/09/when-in-doubt-check-the-mates-in-your-subassemblies/</link>
	<description>Gabi&#039;s Blog on solid modeling, design and engineering</description>
	<lastBuildDate>Tue, 07 Sep 2010 19:25:29 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=5211</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Markko</title>
		<link>http://gabijack.com/2008/09/when-in-doubt-check-the-mates-in-your-subassemblies/comment-page-1/#comment-274</link>
		<dc:creator>Markko</dc:creator>
		<pubDate>Mon, 29 Mar 2010 10:01:37 +0000</pubDate>
		<guid isPermaLink="false">http://gabijack.com/?p=123#comment-274</guid>
		<description>I just had the same kind of thing with an adjustable drop tube on a medical device. The 2 limitdistance mates in 2 nearly identical subassemblies has had me running around in circles until I found your site. The other 70-ish mates kept failing left, right and centre, and suppressing/deleting them just pushed the errors somewhere else. Maybe SW could get their act together on what is effectively an essential feature in a subassembly to make things work like &#039;real world&#039; components. The only way the limitdistance works is to put the part in the top level assembly, which effectively means that the whole thing has to be put together before the restrictions apply - not very &#039;real world&#039;

On thing I noticed though - it might depend on the &#039;level&#039; of the subassembly too. I had a limitangle in a small subassembly, which worked fine in the next up (small) assembly, but failed miserably when this was placed in the top level assembly. I found that it would not drag, or when it did, the other components would lose their (perfectly acceptable) mates and fail.

Just to bleat a bit more, I&#039;d be happy if SW stopped putting new features in their software for a bit, and started making the (very capable) stuff they already have work properly/stably. Wouldn&#039;t go down well with the marketers, but then marketers aren&#039;t engineers, are they? Rant done.

Thanks for the tips</description>
		<content:encoded><![CDATA[<p>I just had the same kind of thing with an adjustable drop tube on a medical device. The 2 limitdistance mates in 2 nearly identical subassemblies has had me running around in circles until I found your site. The other 70-ish mates kept failing left, right and centre, and suppressing/deleting them just pushed the errors somewhere else. Maybe SW could get their act together on what is effectively an essential feature in a subassembly to make things work like &#8216;real world&#8217; components. The only way the limitdistance works is to put the part in the top level assembly, which effectively means that the whole thing has to be put together before the restrictions apply &#8211; not very &#8216;real world&#8217;</p>
<p>On thing I noticed though &#8211; it might depend on the &#8216;level&#8217; of the subassembly too. I had a limitangle in a small subassembly, which worked fine in the next up (small) assembly, but failed miserably when this was placed in the top level assembly. I found that it would not drag, or when it did, the other components would lose their (perfectly acceptable) mates and fail.</p>
<p>Just to bleat a bit more, I&#8217;d be happy if SW stopped putting new features in their software for a bit, and started making the (very capable) stuff they already have work properly/stably. Wouldn&#8217;t go down well with the marketers, but then marketers aren&#8217;t engineers, are they? Rant done.</p>
<p>Thanks for the tips</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andrew Rodgers</title>
		<link>http://gabijack.com/2008/09/when-in-doubt-check-the-mates-in-your-subassemblies/comment-page-1/#comment-273</link>
		<dc:creator>Andrew Rodgers</dc:creator>
		<pubDate>Mon, 09 Mar 2009 20:18:19 +0000</pubDate>
		<guid isPermaLink="false">http://gabijack.com/?p=123#comment-273</guid>
		<description>I&#039;ve had exactly the same problem for months with an assembly that includes two pairs of cylinders.  Everything is fine as long as I suppress one of each pair. I&#039;ve become convinced that the way in which SolidWorks solves the limit distance mates is the problem.</description>
		<content:encoded><![CDATA[<p>I&#8217;ve had exactly the same problem for months with an assembly that includes two pairs of cylinders.  Everything is fine as long as I suppress one of each pair. I&#8217;ve become convinced that the way in which SolidWorks solves the limit distance mates is the problem.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michael Lord</title>
		<link>http://gabijack.com/2008/09/when-in-doubt-check-the-mates-in-your-subassemblies/comment-page-1/#comment-272</link>
		<dc:creator>Michael Lord</dc:creator>
		<pubDate>Mon, 29 Sep 2008 07:15:57 +0000</pubDate>
		<guid isPermaLink="false">http://gabijack.com/?p=123#comment-272</guid>
		<description>I get this same problem quite offer when using Limit Mates. I use quite a few gas struts, accuators and hinges.  Everthing will moves quite smoothly then out of no where a warning and error mates appear.  This is common if I use a folding hinge (similar as you have) and a gas strut pushing. I find (most times) Ctrl Q rebuilds and errors are corrected.</description>
		<content:encoded><![CDATA[<p>I get this same problem quite offer when using Limit Mates. I use quite a few gas struts, accuators and hinges.  Everthing will moves quite smoothly then out of no where a warning and error mates appear.  This is common if I use a folding hinge (similar as you have) and a gas strut pushing. I find (most times) Ctrl Q rebuilds and errors are corrected.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Gabi</title>
		<link>http://gabijack.com/2008/09/when-in-doubt-check-the-mates-in-your-subassemblies/comment-page-1/#comment-271</link>
		<dc:creator>Gabi</dc:creator>
		<pubDate>Fri, 26 Sep 2008 12:37:24 +0000</pubDate>
		<guid isPermaLink="false">http://gabijack.com/?p=123#comment-271</guid>
		<description>Thanks for the info! BTW, I was in a hurry yesterday when I answered your first comment and I swear I saw you had two of the bars constrained. Perhaps it&#039;s because in my mechanism your horizontal bar is vertical for me, so it seemed to me that you had a vertical  and a horizontal bar constrained. Anyway, I took a better look at your mechanism and you are right, it is the same. You are also right about the angle and the whole sketch getting overdefined if you try to make that angle a value of 10, for instance. However, I think this is not the reason why my assembly would become overdefined. See, try to model this using blocks or, better yet, model some bars of the same lenght of those you drew there and assemble them together. Then move the driver (L1) clockwise and observe how the mechanism behaves. When the driver and the horizontal bar are at an angle of around 30, the mechanism locks. A similar thing happens if you move the driver counterclockwise. This is the way the mechanism behaves, but unless you try to apply an ANGLE mate of less than 30 between the driver and the horizontal bar, the assembly shouldn&#039;t become overdefined.

The mate that was applied in my assembly and in the one with the cylinders was a LIMIT mate. It limits the range of motion of two components in the assembly within two values, but it doesn&#039;t constrain them to be any of those two values. Try applying a LimitAngle mate between the driver and the horizontal bar and you&#039;ll see that this doesn&#039;t overdefine the assembly either, even if you specify the limits as 0 to 50, for instance. All that you&#039;ll see is that the driver can oscillate between 50 and 30 and that&#039;s it. According to the limitangle mate, it could go all the way to 0, but because of the way the mechanism is designed, it will continue to lock at 30. Well, this is what I think, based on what I see, but I could be wrong too, of course.

If this is right, you could have one of these mechanisms pushing the flat component without causing the assembly to become overdefined, but when you add a second one (both of them with limit mates) that&#039;s when it becomes overdefined and I think it is because SW interprets it as if you were trying to apply the same mate twice.

Like I said, I could be wrong.</description>
		<content:encoded><![CDATA[<p>Thanks for the info! BTW, I was in a hurry yesterday when I answered your first comment and I swear I saw you had two of the bars constrained. Perhaps it&#8217;s because in my mechanism your horizontal bar is vertical for me, so it seemed to me that you had a vertical  and a horizontal bar constrained. Anyway, I took a better look at your mechanism and you are right, it is the same. You are also right about the angle and the whole sketch getting overdefined if you try to make that angle a value of 10, for instance. However, I think this is not the reason why my assembly would become overdefined. See, try to model this using blocks or, better yet, model some bars of the same lenght of those you drew there and assemble them together. Then move the driver (L1) clockwise and observe how the mechanism behaves. When the driver and the horizontal bar are at an angle of around 30, the mechanism locks. A similar thing happens if you move the driver counterclockwise. This is the way the mechanism behaves, but unless you try to apply an ANGLE mate of less than 30 between the driver and the horizontal bar, the assembly shouldn&#8217;t become overdefined.</p>
<p>The mate that was applied in my assembly and in the one with the cylinders was a LIMIT mate. It limits the range of motion of two components in the assembly within two values, but it doesn&#8217;t constrain them to be any of those two values. Try applying a LimitAngle mate between the driver and the horizontal bar and you&#8217;ll see that this doesn&#8217;t overdefine the assembly either, even if you specify the limits as 0 to 50, for instance. All that you&#8217;ll see is that the driver can oscillate between 50 and 30 and that&#8217;s it. According to the limitangle mate, it could go all the way to 0, but because of the way the mechanism is designed, it will continue to lock at 30. Well, this is what I think, based on what I see, but I could be wrong too, of course.</p>
<p>If this is right, you could have one of these mechanisms pushing the flat component without causing the assembly to become overdefined, but when you add a second one (both of them with limit mates) that&#8217;s when it becomes overdefined and I think it is because SW interprets it as if you were trying to apply the same mate twice.</p>
<p>Like I said, I could be wrong.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: CrazyCAD</title>
		<link>http://gabijack.com/2008/09/when-in-doubt-check-the-mates-in-your-subassemblies/comment-page-1/#comment-270</link>
		<dc:creator>CrazyCAD</dc:creator>
		<pubDate>Fri, 26 Sep 2008 04:55:25 +0000</pubDate>
		<guid isPermaLink="false">http://gabijack.com/?p=123#comment-270</guid>
		<description>this is what i found as the linkage for the wing flap mechanism. looks like two four-bar mechanisms coupled to each other.

&lt;a href=&quot;http://i36.tinypic.com/23gzpfm.jpg&quot; rel=&quot;nofollow&quot;&gt;http://i36.tinypic.com/23gzpfm.jpg&lt;/a&gt;</description>
		<content:encoded><![CDATA[<p>this is what i found as the linkage for the wing flap mechanism. looks like two four-bar mechanisms coupled to each other.</p>
<p><a href="http://i36.tinypic.com/23gzpfm.jpg" rel="nofollow">http://i36.tinypic.com/23gzpfm.jpg</a></p>
]]></content:encoded>
	</item>
</channel>
</rss>
