|
Replies:
58
-
Last Post:
Oct 30, 2008 3:16 AM
Last Post By: cadchimp
|
|
|
Posts:
37
Registered:
07/08/08
|
|
|
|
ATTENTION Inventor Developers! This part has repeatable crash
Posted:
Oct 23, 2008 10:16 PM
|
|
|
|
Open this part, unsuppress fillet12 (just above EOP). This action causes features 25 steps previous to fail. How does a fillet reach back in time to corrupt other features?
I couldn't find the email address for anyone to just send this to. If you are a developer who deals with this kind of problem, please post your email or an email I can just send parts to rather than posting. This time I will write the email down on my monitor with sharpie.
Okay- I cannot post the part here!
"The content type of the file 'Corrupt Part.ipt' is not allowed"
So if someone wants to reply with their email contact, I will be happy to send the corrupt part. Thanks Phil
|
|
|
|
Posts:
12,130
Registered:
04/20/06
|
|
|
|
Re: ATTENTION Inventor Developers! This part has repeatable crash
Posted:
Oct 23, 2008 10:18 PM
in response to: philpdx
|
|
|
The content type of the file 'Corrupt Part.ipt' is not allowed In Windows Explorer right click on the file name and select Send to Compressed (zipped) folder. Attach the *.zip file here.
|
|
|
|
|
Posts:
37
Registered:
07/08/08
|
|
|
|
Re: ATTENTION Inventor Developers! This part has repeatable crash
Posted:
Oct 23, 2008 10:27 PM
in response to: philpdx
|
|
|
|
|
|
For some reason I didn't see that instruction when attaching..... Here you go.
Only now you have to move EOP to the bottom on your own.
|
|
|
|
|
|
|
|
|
Re: ATTENTION Inventor Developers! This part has repeatable crash
Posted:
Oct 23, 2008 11:45 PM
in response to: philpdx
|
|
|
Hi Phil, When I unsuppressed the last fillet, I got a string of errors, but no crash. I noticed that from the iProperties that you have SP1 installed. I haven't loaded the service pack on this machine, so it may be an issue with the service pack. I will get this logged into our system so development can take a look at it. Loren Jahraus Autodesk Inventor Product Design
|
|
|
|
|
|
|
|
|
Re: ATTENTION Inventor Developers! This part has repeatable crash
Posted:
Oct 23, 2008 10:52 PM
in response to: philpdx
|
|
|
|
|
I did not get a crash, I got the attached error message, I'd start at the top of the list and fix one at a time until the error goes away. You have multiple adaptive features in this part. Why? This part could have been built with far less features. Many of your sketches starting with sketch 2 are unconstrained. Why? Unconstrained sketches can cause all sorts of problems. Software developers cannot help a poor design workflow. Need to work on that area. What is the Design Intent in this model? -- Dennis Jeffrey, Autodesk Inventor Certified Expert Autodesk Manufacturing Implementation Certified Expert. Instructor/Author/Sr. App Engr. AIP 2008 SP2, AIP 2009-SP1 PcCillin AV HP zv5000 AMD64 2GB - Geforce Go 440, Driver: .8185 XP Pro SP2, Windows XP Silver Theme http://teknigroup.com
|
|
|
|
|
Posts:
37
Registered:
07/08/08
|
|
|
|
Re: ATTENTION Inventor Developers! This part has repeatable crash
Posted:
Oct 23, 2008 11:11 PM
in response to: Dennis Jeffrey
|
|
|
|
Thank you for your prompt reply. I will try to answer your questions. I also have a few more for you. If you don't consider the attached image to be a "crash", what is it? When updating a part, and having to remake certain features, a fillet with new inputs causes features 25 steps previous to fail, what do you call that? Even if I suck at modeling, as you have stated, I have a thousand parts on my machine that didn't fail in this fashion. This is new behaviour for IV. Are you telling me this is a predictable outcome and only my awful skills at modeling have caused this? If this is a bonafide function of IV, I'd like to know who thought it would be a good idea to do this to people every now and then, and why. Yes I have adaptive features. Isn't that what IV is supposed to do when you model in assembly? Isn't that the default mode for IV? Relating one part in the assembly with the others is what adaptivity is, or no? Thanks for the review of my model. Please forward the slim and trim version to me ASAP so I can see how a real expert does it. Unconstrained sketches... how do they relate to a fillet? Do they reach forward in time to find out if they are problems 25 steps later? Thousands of parts with unconstrained sketches have never failed this way, nor failed to be made into fine consumer products either, BTW. Sorry to bother you. I guess I should go back to school and get a better work flow. Do you have any suggestions of where I can get instruction in this matter?
Edited by: Discussion_Admin on Oct 29, 2008 10:13 AM
|
|
|
|
|
|
|
|
|
Re: ATTENTION Inventor Developers! This part has repeatable crash
Posted:
Oct 23, 2008 11:51 PM
in response to: philpdx
|
|
|
No offense given or taken. I was providing advice. Un (under)constrained sketches can allow features built on them to sort of float. I provided sound advice. You have a LOT of projected geometry in this part. And, yes, this part could be simplified, and in that, more stable. So, what "workaround" did use use to fix this? -- Dennis Jeffrey, Autodesk Inventor Certified Expert Autodesk Manufacturing Implementation Certified Expert. Instructor/Author/Sr. App Engr. AIP 2008 SP2, AIP 2009-SP1 PcCillin AV HP zv5000 AMD64 2GB - Geforce Go 440, Driver: .8185 XP Pro SP2, Windows XP Silver Theme http://teknigroup.com
|
|
|
|
|
Posts:
37
Registered:
07/08/08
|
|
|
|
Re: ATTENTION Inventor Developers! This part has repeatable crash
Posted:
Oct 24, 2008 12:09 AM
in response to: Dennis Jeffrey
|
|
|
|
I simply put the correct fillet onto the part, and deleted the suppressed one.
Autodesk should consider that people like me, who have been using Inventor for years and years (R4), do not necessarily do things "the right way". What do you think a nube would think? Put it back in the box and send it back perhaps.
I have seen a lot over the years. Stuff works one day, doesn't the next release out. Waiting to install until SP1, etc. When something like this happens it is EXTREMELY rare, and noteworthy as such. Often I cannot get crashes to repeat. When I can, I want to share the parts with people who might make IV run a little better next release.
In my business- we test products before we sell them. Worst case scenarios for: user knowledge, install integrity, proper use of, and unforseeable user actions ABSOLUTELY have to be anticipated, planned for, and designed in. Otherwise, people's houses and cars burn down. Bummer.
Can Autodesk, or you, honestly say that IV hasn't cost any business money because of things like this, and the lack of foresight to produce something that can work no matter how poorly the work flow is laid out? Caveat Emptor, I understand. But then, who likes to know their products might cost jobs, create stressful situations, heck, even cost lives for the medical community that uses IV?
GIGO is not an answer anymore. This is not DOS.
Thanks
Phil
|
|
|
|
|
Posts:
37
Registered:
07/08/08
|
|
|
|
Re: ATTENTION Inventor Developers! This part has repeatable crash
Posted:
Oct 23, 2008 11:13 PM
in response to: Dennis Jeffrey
|
|
|
|
Did you mean "far fewer" features?
The workaround went just fine. Part is now finished without rebuilding or constraining my sketches or good work flow. Some people just do it different I guess.
|
|
|
|
|
Posts:
113
Registered:
05/09/08
|
|
|
|
Re: ATTENTION Inventor Developers! This part has repeatable crash
Posted:
Oct 24, 2008 6:56 AM
in response to: philpdx
|
|
|
|
I'm not a certified professional, nor would I say I'm an expert INV user, but I do know from experience that constraining sketches completely (which doesn't take much extra time at the start), keeping projected items to a minimum and having as few adaptive parts as possible, make the end product so much more stable and makes it possible to go back and change stuff without problems. When I started playing around with INV, I didn't know how to constrain sketches properly and was getting a long way through the design before something would move and I would have to go back and fix it all up. Leaving something unconstrained is like leaving a ball sitting on the edge of a shelf, the slightest movement and it will come crashing to the floor. It has to make sense that constrained sketches and parts can't move without you wanting them to. Constraining from the start saves time in the future. Just my 2c worth.
|
|
|
|
|
|
|
|
|
Re: ATTENTION Inventor Developers! This part has repeatable crash
Posted:
Oct 24, 2008 5:35 PM
in response to: philpdx
|
|
|
Hi Phil, As I mentioned in an earlier message, I have sent this to development. I agree that it is odd that the errors only show up when you add that last fillet. Loren Jahraus Autodesk Inventor Product Design
|
|
|
|
|
Posts:
12,130
Registered:
04/20/06
|
|
|
|
Re: ATTENTION Inventor Developers! This part has repeatable crash
Posted:
Oct 24, 2008 5:45 PM
in response to: philpdx
|
|
|
I don't really need a lesson in how to model with IV Based only on this file as evidence I would recommend that you get more training. You may very well have 999 other files that better demonstrate your techniques.
been using Inventor for years and years (R4) I can't imagine how someone can use the software since R4 designing thousands of parts can start out on a part of this complexity and not even bother to constrain the first sketch. (Some of the arcs in Sketch1 aren't even tangent - Inventor does this for you, no extra work.) Especially considering the mirrored symmetry from left to right.
Do you have any suggestions of where I can get instruction in this matter? I offer many industry classes on using Inventor. Where are you located? I could suggest this book as well http://www.amazon.com/gp/p roduct/0470293144?ie=UTF8&tag=mc02c-20&linkCode=as2&camp=1789&creative=9325&crea tiveASIN=0470293144 there are many tips in there about creating robust parts. Seems to me I recall Sean having something to say about constrained sketches. You might also read this document http://home.pc t.edu/~jmather/AU2007/MA105-1L%20Mather.pdf
There is nothing inherently wrong with using adaptive parts, but building a house of cards on top of quicksand is probably not the best way to ensure a robust part. It might sound like the comments here are "kicking sand" but more like an attempt to lend a helping hand out of the quicksand.
Can Autodesk, or you, honestly say that IV hasn't cost any business money because of things like this, and the lack of foresight to produce something that can work no matter how poorly the work flow is laid out? I'm quite sure I could sit down with you and demonstrate how less than disciplined modeling techniques are costing your company thousands of dollars. You should be able to easily recoup my fee on the first project.
So Autodesk is demonstrating a, "lack of foresight to produce something that can work no matter how poorly... ...laid out", but you seem to be rejecting the same principle in your work.
GIGO is not an answer anymore. GIGO is always relevant. Your part is garbage. Nice looking garbage, but all the same garbage. Yes you should have been given a warning much sooner. (Sketch16 has sick geometry.) Maybe we will see something like SolidWorks has in a future Inventor. In SolidWorks there is a switch that can be set to not allow features to be created from unconstrained sketches. Of course for the most part very few unconstrained sketches should make it out of a first parametric modeling class.
But then, who likes to know their products might cost jobs, create stressful situations, heck, even cost lives When professional people ignore GIGO we have bridges collapse into rivers, cranes collapse onto apartment buildings and school buildings collapse onto children. Your designs might not have such concern for GIGO, but it is no less relevant.
I agree that I learn much about the program from unconventional techniques and I would encourage you to submit problems such as this one. But at the same time I would listen to the comments. An open forum like this brings together many different experiences that enlighten us all. Sometimes it is a little messy and argumentative but in the end there should be something of value within the arguments.
|
|
|
|
|
Posts:
5
Registered:
09/03/08
|
|
|
|
Re: ATTENTION Inventor Developers! This part has repeatable crash
Posted:
Oct 24, 2008 7:23 PM
in response to: JDMather
|
|
|
|
Full constraint of sketches isn't a unique requirement of Inventor. It is a basic part of good solid modeling technique.
Inventor is a sophisticated tool, with its own unique limitations and quirks at the limits of capabilities. Unpredictable behavior due to broken/poorly constrained geometry is hardly surprising.
|
|
|
|
|
|
|
|
|
Re: ATTENTION Inventor Developers! This part has repeatable crash
Posted:
Oct 24, 2008 8:25 PM
in response to: JDMather
|
|
|
On Fri, 24 Oct 2008 18:31:26 +0000 philpdx wrote: I SENT THIS IN BECAUSE THE DEVELOPERS NEED TO SEE THINGS LIKE THIS. I agree with the other side of the fence. JD and DJ have given very good advice to you and many others here over and over. I'm wondering what the developers think when they see the underconstrained sketches, it would be nice if we could get some of that feedback here, in this topic. SW was the first solid modeling software I was trained on many yrs ago (read, I am not an expert) but I remember one thing from that training that I practice with Inventor - *always fully constrain your sketches* at least to the point they cannot move in a direction you cannot have in a design. Good luck with your "mission" philpdx. I hope *somebody* learns something from this. I have, now where is the ole plonk button at... -- Inventor 10 Series SP3a + TS1069046 (Inventor Text Broken By Microsoft update)
|
|
|
|
|
Posts:
4
Registered:
09/23/08
|
|
|
|
Re: ATTENTION Inventor Developers! This part has repeatable crash
Posted:
Oct 25, 2008 4:46 PM
in response to: philpdx
|
|
|
|
So far, it appears that no one has "fixed" the sketches to see if the fillet failure still occurs. That would be interesting, no ? I can't for the life of me comprehend how a feature that's created later in time (Inventor is a feature/history based modeler, after all) can cause previously created features to fail. That is a bug and Autodesk does need to look at it. I think Loren agrees with that as well as he stayed out of the bickering side of this discussion.
|
|
|
|
|
|
|
|
|
Re: ATTENTION Inventor Developers! This part has repeatable crash
Posted:
Oct 25, 2008 6:53 PM
in response to: hall_stevenson
|
|
|
So far, it appears that no one has "fixed" the sketches to see if the fillet failure still occurs. That would be interesting, no ? Yes it would. It would happen if more of the people here were more interested in fact and comprehension than appearance and sales. I can't for the life of me comprehend how a feature that's created later in time (Inventor is a feature/history based modeler, after all) can cause previously created features to fail. That is a bug and Autodesk does need to look at it. It would seem so, at least based on experience with other history based modelers. Either a bug or a "unique" set of data processing and solver algorithms. Memory grows dim but it seems IV does allow certain operations that would result in circular references in other systems indicating the possibility of unique algorithms and possibly unique requirements such as manually fully constraining sketches (good practice but if there is necessity it should be understood). One always has to consider what happens behind the buttons to understand the nature of failures. One could hope for factory explanations / documentation / demonstration but I think there's still an unresolved question regarding nonmanifold failures with multiple region sketches floating around. That should be a simple one. Beware those that don the mantle of "expert" and, especially, the fans and true believers. ;^)
|
|
|
|
|
Posts:
12,130
Registered:
04/20/06
|
|
|
|
Re: ATTENTION Inventor Developers! This part has repeatable crash
Posted:
Oct 26, 2008 10:02 PM
in response to: cadchimp
|
|
|
So far, it appears that no one has "fixed" the sketches to see if the fillet failure still occurs. That would be interesting, no ?Yes it would. It would happen if more of the people here were more interested in fact and comprehension... I used to learn a lot from the unconventional techniques you used post here. But in this case I see no real indication that the OP is really interested in the 10 hours or so that it would take me to go through the convoluted mess and fix it up. I routinely do just that for those who are interested and just for my own interest. Obviously the first sketch has nothing to do with the problem reported - that is a separate matter. But I see the first sketch as just the first of many indications I see of a bit of thrashing about. I estimate I could create the same part with at least half as many features. I would definately start over clean rather than try to use this file. From my experience this much thrashing around is bound to cause problems. Better to take what is learned about the geometry along the way and start over. If anyone wants to try to fix it up I think I saw Sketch16 - well back in the history tree - had sick geometry (pink). Might be a place to start.
|
|
|
|
|
|
|
|
|
Re: ATTENTION Inventor Developers! This part has repeatable crash
Posted:
Oct 27, 2008 3:47 AM
in response to: JDMather
|
|
|
the convoluted mess and fix it up. I routinely do just that for those who are interested and just for my own interest. I understand and anyone and everyone should appreciate that effort be grateful for the leg up on sound modeling practices and procedures. In this instance however I think the goal ~should~ be to establish whether or not adding or unsuppressing a feature at or near the end of the history tree normally causes previous features to regenerate and, in this case, fail. If the full regen is normal (hard to imagine but ...?) then I guess we might be back to some ragged edge geometry definitions. Even then, if they are causing a crash (abnormal program termination) Autodesk should be happy to receive the data set for examination. Less than ideal geometry definitions are a fact of life and any insinuation (not pointing at you) that it's ok for that to take down a system needs to be examined. And, well... you know; I have a preternatural tendency to question things. ;^)
|
|
|
|
|
Posts:
953
Registered:
01/15/06
|
|
|
|
Re: ATTENTION Inventor Developers! This part has repeatable crash
Posted:
Oct 26, 2008 8:09 AM
in response to: philpdx
|
|
|
|
I dont make any money off of helping people, andIi spend about 10 hours each week helping others on my time. No one in these replies has suggested that you are "wrong" or "bad at your job " . There are hundreds of ways to skin each cat.
That being said there are some ways that result in a happier cat.
This forum is for constructive results , you take what you want and leave the rest. Its obvious you got your feelings hurt and no one intended to do that at all.
I have not yet looked at your file because it wont download, but I will be glad to send back my naked cat as soon as I can.
I personally have found that I save significant time when keeping slim and trim. and if the stuff I design fails people die.
never stop learning , and definitely never stop calling autodesk to task for things that cause you to lose productivity.
feel free to send it to me at chenry@engineersupportservice.seeohhmmm
|
|
|
|
|
Posts:
37
Registered:
07/08/08
|
|
|
|
Re: ATTENTION Inventor Developers! This part has repeatable crash
Posted:
Oct 27, 2008 7:23 PM
in response to: philpdx
|
|
|
|
Well, I saved you all "10 hours" or so of untangling things.
Ha, ha. It only took 20 minutes of auto dimensioning and constraining each sketch. I also deleted any extra geometry that was hanging out, for good measure. I also didn't find any adaptive geometry. I did break link with all projected cut geometry.
Results: the part didn't crash. I still had to manually rebuild the last fillet since the root edge for it was now different.
Lesson learned: sure, I could be more disciplined in my modeling.
But then, this odd behaviour would not have raised it's ugly head, I wouldn't have had a file to send in, and I would have been done with this project HOURS AGO.
You see- funny thing here- by constraining all my sketches, and doing my best to have a clean part, I SAVED NO TIME. Funny how that works- once I am done with a part I rarely edit it, and therefore don't waste any time because of this sloppy work on my part. Even with the sketches un-constrained, the editing time is the same.
So what I learned is it just doesn't matter that much to me. (the part is the same no matter how many constraints it has in it's build)
And I don't curse Inventor (I think that's what JD and DJ were on about to begin with- thinking I was blaming their sweetheart IV when I am a mere sloppy constrainer), I have had very good luck, productivity, creativity, and learned a lot from IV over the years. So next time I post a corrupt part, don't lecture me, enjoy the chance to see a real pro in action- breaking the program. (another thing about my business- we are very happy to find out just how things break- poor use is no reason to blame the user)
Breaking the program is a good thing, in other words.
Now- am I going to make parts this complex in the future? You bet. Am I going to constrain the heck out of everything? Only with fingers crossed that the CAD gods smile on my efforts.
And this time I mean it: thanks for pointing, uh, shoving me in the right direction.
|
|
|
|
|
Posts:
216
Registered:
09/29/08
|
|
|
|
Re: ATTENTION Inventor Developers! This part has repeatable crash
Posted:
Oct 28, 2008 12:52 PM
in response to: philpdx
|
|
|
|
Does anyone have the originally posted model ?
|
|
|
|
|
Posts:
12,130
Registered:
04/20/06
|
|
|
|
Re: ATTENTION Inventor Developers! This part has repeatable crash
Posted:
Oct 28, 2008 12:55 PM
in response to: HallStevenson
|
|
|
|
You should see it attached to the third post. If not, send me a email and I'll forward to you. I have examined the file in some detail and will post a lengthy synopsis when I get a chance. It is trivially easy to get the fillet in if the suppressed fillet is deleted and the EOP rolled up to just under Extrusion15 and the fillet added at that point in the history. Unroll the EOP and the part rebuilds without errors. But that doesn't answer the question of why it fails in the original attached.
Edited by: JDMather on Oct 28, 2008 9:02 AM
|
|
|
|
|
Posts:
216
Registered:
09/29/08
|
|
|
|
Re: ATTENTION Inventor Developers! This part has repeatable crash
Posted:
Oct 28, 2008 1:13 PM
in response to: JDMather
|
|
|
|
"But that doesn't answer the question of why it fails in the original attached."
That's what I'm interested in as should Autodesk.
|
|
|
|
|
Posts:
12,130
Registered:
04/20/06
|
|
|
|
Re: ATTENTION Inventor Developers! This part has repeatable crash
Posted:
Oct 28, 2008 1:19 PM
in response to: HallStevenson
|
|
|
That's what I'm interested in as should Autodesk. I would caution the apparent assumption by the OP that I was suggesting a cause and effect between the unconstrained sketches and the failed fillet. The unconstrained sketches were just my observation as an obvious to see symptom of deeper problem in the overall technique. And I did agree that Autodesk should be interested in the file because it causes features earlier in the history to fail.
|
|
|
|
|
|
|
|
|
Re: ATTENTION Inventor Developers! This part has repeatable crash
Posted:
Oct 28, 2008 3:51 PM
in response to: JDMather
|
|
|
|
Andy, Loren and I had a discussion about this thread yesterday.
There are design scenarios that require you to try things and start over...
...if we all knew where a design was going when it was started, life would be a lot easier I suspect.
Like Phil, I will routinely rely on "sloppy design practices" and usually get away with them. I would hate to send any of my work to JD because a majority of my sketches are under constrained and poorly dimensioned.
That said, if I know that I'm building something that will more than likely need to be edited again later and/or given to another designer as an example or as a foundation to build upon, I really try to nail things down. I have also been bitten by my own sloppy assumptions - spent way more time that warranted looking for a problem that was the result of sloppy habits.
Loren has already grabbed the original file and he has logged it for QA and Dev review. Getting these sorts of issues to us is important and appreciated.
Thanks Phil!
-- Gary R. Smith Autodesk Manufacturing Solutions Division Technical Publications - Subject Matter Expert Portland, OR 2.33GHz 2GB IBM ThinkPad T60p; XP pro SP2 ATI Mobility FireGL V5250 driver: 8.293.1.0
|
|
|
|
|
Posts:
5,400
Registered:
09/21/04
|
|
|
|
Re: ATTENTION Inventor Developers! This part has repeatable crash
Posted:
Oct 28, 2008 4:41 PM
in response to: Gary R Smith \(...
|
|
|
Like Phil, I will routinely rely on "sloppy design practices" and usually get away with them.
This is an attitude that reflects your company's culture. If you are sloppy in one aspect of your work, you will usually be sloppy in others. This also affects the work of your peers. This is nothing more than laziness. It is has become very obvious that ADSK does not practice continuous improvement or Six Sigma and relies on "good enough and lets hope they don't notice". The release of sloppy code and half-implemented features is a regular occurrence. Features are not fully documented. Websites are updated with broken interfaces. It is all connected. I would suggest reviewing your attitudes and culture otherwise you will continue to lose customers to other companies that continually strive for excellence.
|
|
|
|
|
|
|
|
|
Re: ATTENTION Inventor Developers! This part has repeatable crash
Posted:
Oct 28, 2008 5:28 PM
in response to: Josh_Petitt
|
|
|
|
I don't do part/assembly design for a living. The models that I make are for illustration purposes only - nobody sees the IPT or IAM files, so my modeling practices are completely appropriate for their purposes.
|
|
|
|
|
Posts:
1,751
Registered:
12/12/06
|
|
|
|
Re: ATTENTION Inventor Developers! This part has repeatable crash
Posted:
Oct 28, 2008 8:33 PM
in response to: Gary R Smith \(...
|
|
|
|
I think it's inappropriate for him to be jumping on you, but poor practice is poor practice, and he's trying to say that sloppiness in any aspect of one's work might not reflect well upon the rest. (But then again, if a cluttered desk equals a cluttered mind what does an empty desk mean?)
|
|
|
|
|
Posts:
5,400
Registered:
09/21/04
|
|
|
|
Re: ATTENTION Inventor Developers! This part has repeatable crash
Posted:
Oct 28, 2008 10:21 PM
in response to: dan_inv09
|
|
|
he's trying to say that sloppiness in any aspect of one's work might not reflect well upon the rest.
To Gary, and Dan, yes that is what I was trying to say. Gary you've been a fantastic wealth of information on this forum, and I do thank you for that. I just hated to hear the justification for sloppiness coming from you. But then again, if a cluttered desk equals a cluttered mind what does an empty desk mean?
A clear mind ;-)
|
|
|
|
|
|
|
|
|
Re: ATTENTION Inventor Developers! This part has repeatable crash
Posted:
Oct 28, 2008 5:31 PM
in response to: Josh_Petitt
|
|
|
Let me poke in here if I may I do agree with Josh that we have seen lots of half implemented features and some sloppy interface designs with the release of IV over the years, but I don't for a second think that we all can and will have drawings that are textbook perfect, and pass JD's inspection. (sorry to point you out JD) It's just not economically possible or appropriate to go back and redraw a part just because you made some changes on it later on in the process. We design a large variety of different equipment here, and not a lot of each either. So when a change is made it may be a year or 2 and IV has improved, our own skills have improved, the way we would have modeled it may have changed depending on the change, but it's still not economical to redraw the part. Why well that would require us to re-constrain the part in the assy, or assy's We have lots of parts in multiple assy's. It might then require us to readjust in an ipn file, and then we might have to re-balloon, and reattach measurements in an idw. I mean changing one part could literally take up my entire day, when it was really only budgeted to take up 1/2hour. I am not saying that we should be careless in our drawings, or sloppy, but I don't think all our drawings will be perfect and that is just life. I don't think I am lazy Josh for drawings that not perfect, instead I like to think that I am doing the best job I can in the time allocated to me. Would that not just make me efficient. >Like Phil, I will routinely rely on "sloppy design practices" and usually get away with them.
This is an attitude that reflects your company's culture. If you are sloppy in one aspect of your work, you will usually be sloppy in others. This also affects the work of your peers. This is nothing more than laziness.
It is has become very obvious that ADSK does not practice continuous improvement or Six Sigma and relies on "good enough and lets hope they don't notice". The release of sloppy code and half-implemented features is a regular occurrence. Features are not fully documented. Websites are updated with broken interfaces. It is all connected.
I would suggest reviewing your attitudes and culture otherwise you will continue to lose customers to other companies that continually strive for excellence.
|
|
|
|
|
|
|
|
|
Re: ATTENTION Inventor Developers! This part has repeatable crash
Posted:
Oct 28, 2008 5:57 PM
in response to: Troy Grose
|
|
|
Troy, I don't think that JD or I ever have said that underconstrained geometry is the cause of all problems. However, when a part goes "South" for no apparent reason, it's one of the first places to look. We had a term when I was doing and teaching computer programming back in the 70's and '80's, called "Spaghetti Code" which described coding ( programming) that became so convoluted that it was next to impossible to locate the real cause of a problem. The solution to that issue was to teach a "structured" programming workflow. When code is simplified and structured, it is more stable, faster, and generally easier to troubleshoot. The same applies to modeling techniques..... BTW, the term GIGO (Garbage In Garbage Out) was coined by programmers who finally realized that it takes LESS time to properly program ( "model" ) than to fix issues later ( that is IF you can unravel the problem ). I'll agree, that an issue like this rarely rears it's head.... but as I stated in another post: "Kinda like smoking while fueling your vehicle. I see people doing that every day also. Sometimes there's an explosion......" -- Dennis Jeffrey, Autodesk Inventor Certified Expert Autodesk Manufacturing Implementation Certified Expert. Instructor/Author/Sr. App Engr. AIP 2008 SP2, AIP 2009-SP1 PcCillin AV HP zv5000 AMD64 2GB - Geforce Go 440, Driver: .8185 XP Pro SP2, Windows XP Silver Theme http://teknigroup.com
|
|
|
|
|
|
|
|
|
Re: ATTENTION Inventor Developers! This part has repeatable crash
Posted:
Oct 28, 2008 6:29 PM
in response to: Dennis Jeffrey
|
|
|
I don't think that I ever said the you said that under constrained geometry was the cause of all the problems. I completely agree that the simpler a part is modeled the greater the chances are that the part will never see an issue. I am just saying that its not always efficient to re-make the part simple. You need to balance the pros and cons of redrawing a part before you do it. Will the results be worth the work?
Troy, I don't think that JD or I ever have said that underconstrained geometry is the cause of all problems. However, when a part goes "South" for no apparent reason, it's one of the first places to look. We had a term when I was doing and teaching computer programming back in the 70's and '80's, called "Spaghetti Code" which described coding ( programming) that became so convoluted that it was next to impossible to locate the real cause of a problem. The solution to that issue was to teach a "structured" programming workflow. When code is simplified and structured, it is more stable, faster, and generally easier to troubleshoot. The same applies to modeling techniques..... BTW, the term GIGO (Garbage In Garbage Out) was coined by programmers who finally realized that it takes LESS time to properly program ( "model" ) than to fix issues later ( that is IF you can unravel the problem ). I'll agree, that an issue like this rarely rears it's head.... but as I stated in another post: "Kinda like smoking while fueling your vehicle. I see people doing that every day also. Sometimes there's an explosion......" -- Dennis Jeffrey, Autodesk Inventor Certified Expert Autodesk Manufacturing Implementation Certified Expert. Instructor/Author/Sr. App Engr. AIP 2008 SP2, AIP 2009-SP1 PcCillin AV HP zv5000 AMD64 2GB - Geforce Go 440, Driver: .8185 XP Pro SP2, Windows XP Silver Theme http://teknigroup.com
|
|
|
|
|
Posts:
12,130
Registered:
04/20/06
|
|
|
|
Re: ATTENTION Inventor Developers! This part has repeatable crash
Posted:
Oct 28, 2008 6:25 PM
in response to: Troy Grose
|
|
|
It's just not economically possible or appropriate to go back and redraw a part... ....but it's still not economical to redraw the part. I agree, in some cases, but not this one. I'm commenting on this particular part. This is a challenging part for Inventor. I see plenty of evidence that only leads me to wonder why it didn't fail much earlier.
|
|
|
|
|
Posts:
1,751
Registered:
12/12/06
|
|
|
|
Re: ATTENTION Inventor Developers! This part has repeatable crash
Posted:
Oct 28, 2008 8:21 PM
in response to: JDMather
|
|
|
|
I think that most of the time it is economical to redraw the part, unfortunately you will not know when until it is to late. You see it after you spend an hour or two and still have not fixed what would have taken you 20 or 30 minutes to reconstruct better.
Someone else mentioned all the trouble reconstraining and finding what other assemblies it's used in, but the whole point is not to wait until it's too late. If you stop and redo it immediately after your first try you will be placing your better, more robust model and you shouldn't need to fix it after it's in a couple of assemblies.
I still have the mindset of just a little adjustment here and there and it will be all better. I'm working on being able to start over from scratch, I know for a fact that it's really hard, but I can also see the benefits. And the time it saves when you do need it will far outweigh the time you spend when you don't.
|
|
|
|
|
Posts:
37
Registered:
07/08/08
|
|
|
|
Re: ATTENTION Inventor Developers! This part has repeatable crash
Posted:
Oct 28, 2008 6:56 PM
in response to: Josh_Petitt
|
|
|
|
Total laziness... I always get around to relaxing my standards and bringing down my workmates right after writing manuals, designing tradeshow booths, building the booth, qualifying vendor parts, creating new designs, documenting those new designs, translating them to SW for the Chinese, troubleshooting returned product, unloading trucks... yeah, total laziness. Must be nice to work somewhere you only have to push the right buttons all day.
|
|
|
|
|
Posts:
216
Registered:
09/29/08
|
|
|
|
Re: ATTENTION Inventor Developers! This part has repeatable crash
Posted:
Oct 28, 2008 4:18 PM
in response to: JDMather
|
|
|
|
Just re-read the first few responses and have to admit, you didn't .... this time. It was Dennis who suggested it was related.
I still can't download the file either (???). Tried with Internet Explorer, Firefox, and Chrome. Oh well, I'm not gonna worry about it anymore.
|
|
|
|
|
|
|
|
|
Re: ATTENTION Inventor Developers! This part has repeatable crash
Posted:
Oct 28, 2008 5:12 PM
in response to: HallStevenson
|
|
|
I'll stand by my brief analysis. I din not dig any deeper after viewing all the garbage in the file. I agree with JD's final analysis of this file dated today. -- Dennis Jeffrey, Autodesk Inventor Certified Expert Autodesk Manufacturing Implementation Certified Expert. Instructor/Author/Sr. App Engr. AIP 2008 SP2, AIP 2009-SP1 PcCillin AV HP zv5000 AMD64 2GB - Geforce Go 440, Driver: .8185 XP Pro SP2, Windows XP Silver Theme http://teknigroup.com
|
|
|
|
|
Posts:
216
Registered:
09/29/08
|
|
|
|
Re: ATTENTION Inventor Developers! This part has repeatable crash
Posted:
Oct 28, 2008 1:14 PM
in response to: JDMather
|
|
|
|
It doesn't seem to be available anymore.... I get "Error An general error occurred while processing your request."
|
|
|
|
|
Posts:
12,130
Registered:
04/20/06
|
|
|
|
Re: ATTENTION Inventor Developers! This part has repeatable crash
Posted:
Oct 28, 2008 1:20 PM
in response to: HallStevenson
|
|
|
It doesn't seem to be available anymore.... I get "Error An general error occurred while processing your request." I just downloaded it again a couple of minutes ago.
|
|
|
|
|
Posts:
12,130
Registered:
04/20/06
|
|
|
|
Re: ATTENTION Inventor Developers! This part has repeatable crash
Posted:
Oct 28, 2008 4:39 PM
in response to: philpdx
|
|
|
You see- funny thing here- by constraining all my sketches, and doing my best to have a clean part, I SAVED NO TIME.
In my experience all the evidence I have seen is that constraining most sketches and using a disciplined modeling technique saves time.
I took a look at the file. As indicated earlier in the thread no other changes other than adding the fillet after Extrusion15 the part would rebuild without errors. I don't believe I ever indicated that there was a cause and effect between the unconstrained sketches and the fillet. I believe I did indicate that this was an interesting file because a fillet feature caused errors earlier in the history tree.
I frequently take interesting problems from this discussion group and analyze them see if I can reproduce the geometry in a more efficient manner - particularly those problems that might reveal a re-producible bug or feature missing from Inventor. I identify with the book iWoz by Steve Wozniak on how I enjoy these challenges.
It was pointed out recently that while I might post a more elegant, robust solution I never take the time to explain why it is more robust or elegant. It would probably take a book to go much beneath the surface, and I am basically a machinist, ill equipped for the task. The first thing a machinist does when making a part is identify data for reference.
I checked iProperties and it indicated the file was started in Inventor 2008 and last saved in Inventor 2009.
I opened your file and created a new user Workplane Inventor assigned Workplane23.
On the workplane I created a new sketch Inventor assigned Sketch107.
In the new sketch I created a rectangle and added a dimension, Inventor assigned d872.
I Project Geometry a Loop, Inventor assigned Project Loop60.
I Project Geometry a Cut Edges, Inventor assigned Cut Edges28.
I extruded the sketch and Inventor assigned Extrusion87.
When I go through a problem I try many many iterations in quick succession getting to understand the geometry. I start many new files rather than building on top of the earlier garbage that I have accumulated and then discarded. A couple of interesting reads along this line are Seymour Papert's Mindstorms: Children, Computers, and Powerful Ideas, and The Children's Machine: Rethinking School in the Age of the Computer. To paraphrase Papert, "I need the unsuccessful early trials to get a feel for the later successful solution."
Workplane23
In your file there remains 9 user workplanes. Three of these are duplicates of the origin workplanes.
The only time I duplicate the origin workplanes is if I need to Flip Normal or if the design indicates that I might want to offset later for some reason. In other words, very very rarely. I feel like I might be mis-interpreted here, I didn't say I don't create user workplanes, I said I don't duplicate workplanes that already exist.
Sketch107
In your file there remains 42 sketches and 3 suppressed sketches. Many to most are under constrained, often lacking auto constraints or any dimensions at all. It would actually take me more time rather than less time to do the unconstrained/undimensioned sketches. To me this is the "quicksand" that can lead to even inadvertent changes to the model even if you were very careful in the initial construction. Even if you will have absolutely no need to change later. Within those sketches is evidence that is of more concern to me than the dimensioning/constraining - after all we didn't have constraints or driving dimensions on the drawing board or even AutoCAD.
Project Loop60
I failed to record how many projected loops you have remaining, but I almost never ever use projected loops. They are particularly prone to failure if the underlying geometry changes too much. Do an experiment. Project a loop on a face and then sketch a circle. Extrude the circle. Now try to Copy the cylindrical extruded feature. You cannot copy a feature that contains projected loop. (Projected Loop is generated when the Project Geometry is used on a part face rather than on the edges.) It gets even more fragile if build a child feature whose parent has a projected loop. Only use projected loop on top level features that will never change and no use as iFeature or Copy in the future.
Cut Edges28
I failed to record how many projected cut edge sketches you have remaining. Similar to projected loops, projected edges are prone to failure if the underlying geometry changes too much. But unlike projected loops which can be entirely avoided in any case that I can think of off-hand, projected cut edges are sometimes very valuable. They should be used only where absolutely needed and with caution. Until recently they weren't eve associative in Inventor. (I feel the need to point out to the less experienced Inventor user that Cut Edges28 does not mean there are 27 previous entities created - each instance of a project cut edge usually (always) results in multiple entities created - each of which could fail).
Extrude87In your file there remains 31 extrusions and 3 suppressed extrusions. I estimate that I could model the same part with about half the number of features. That is less important than the sketch concerns already indicated, but as much as (efficiently) possible I try to avoid parent/child relationships. The more complex the part the more I try to avoid these relationships. On a simple part it probably isn't worth the effort. In Billy Vaughn Koen's , Discussion of the Method: Conducting the Engineer's Approach to Problem Solving he has an interesting discussion on the difficulty of programming the game of chess. The board has only 64 squares and the initial possible moves are known. The rules are well defined. I would argue that design is far more difficult than chess with many more possible interactions. I am a machinist, not a software programmer. My views are simply based on observation and experience.
|
|
|
|
|
|
|
|
|
Re: ATTENTION Inventor Developers! This part has repeatable crash
Posted:
Oct 28, 2008 5:23 PM
in response to: JDMather
|
|
|
JD, I totally agree. If others realized how many hundreds or thousands of BAD files that instructors see in 22 years of working with parametric relationships they would understand that sloppiness invites problems. I did not even bother to spend more time on the file to try to unwind the dependencies with the final fillet. Total waste of time, even if I were getting "paid" for the analysis, which I'm not. PTC - Pro/E used to require that sketches were fully constrained before creating features, otherwise, the part might become unstable. I understand that the newer ones fully "autoconstrain" if you do not do your job. Inventor has that option. You just have to use it. MDT - Best practice from day 1 was that all sketches "should be" fully constrained. SW - Same as MDT IV - Same as MDT In fact all parametric programs RECOMMEND fully constraining. There is a reason. Kinda like smoking while fueling your vehicle. I see people doing that every day also. Sometimes there's an explosion...... -- Dennis Jeffrey, Autodesk Inventor Certified Expert Autodesk Manufacturing Implementation Certified Expert. Instructor/Author/Sr. App Engr. AIP 2008 SP2, AIP 2009-SP1 PcCillin AV HP zv5000 AMD64 2GB - Geforce Go 440, Driver: .8185 XP Pro SP2, Windows XP Silver Theme http://teknigroup.com
|
|
|
|
|
Posts:
4
Registered:
09/23/08
|
|
|
|
Re: ATTENTION Inventor Developers! This part has repeatable crash
Posted:
Oct 28, 2008 5:34 PM
in response to: JDMather
|
|
|
|
JD, for the record, I agree pretty much with all of your "bold" points. Things like Projected Loops, I *never* use. I do, very rarely, use "Project Cut Edges, but I always turn it all into construction lines and then "draw over" the bits and pieces I need. Creating workplanes right on top of the existing ones ? See it all the time (here) and NEVER understand why people do it !
|
|
|
|
|
|
|
|
|
Re: ATTENTION Inventor Developers! This part has repeatable crash
Posted:
Oct 28, 2008 7:26 PM
in response to: hall_stevenson
|
|
|
Creating workplanes right on top of the existing ones ? See it all the time (here) and NEVER understand why people do it ! With no attempt to make a case one way or the other; [1] Redundant work features are consistent with so called 'horizontal modeling' techniques, which are sometimes a good idea. [2] If (a) unsure, due to lack of query functions or indications, of existing work features' dependencies and orientations, where applicable, or (b) relatively sure a reroute will never be required, the safe thing to do is create new ones dedicated to the purpose at hand.
|
|
|
|
|
Posts:
37
Registered:
07/08/08
|
|
|
|
Re: ATTENTION Inventor Developers! This part has repeatable crash
Posted:
Oct 28, 2008 7:42 PM
in response to: JDMather
|
|
|
|
JD- Thanks for taking the time to look at this.
Perhaps some explaining of my process will help.
This part is designed to mate with several off the shelf components. I get those from vendors, standard parts in 3D format. The parts are mathematically related to each other. I place them into an assembly in the proper spatial relationship accordingly.
There is an envelope size I must match. This part has to be no larger or smaller than a pre-determined size. Other than these pre-set definitions, there are standard shapes which must be used per vendor/industry standard- ingredients if you will. That's it, the rest is me being creative, not necessarily disciplined as a proper engineer or machinist need be.
The venturi type shape contains certain mathematical relationships. You can see that in the sketch with a floating cloud of points used as defining points for a spline. This flare is essential to the function of the finished assembly and therefore happens early in.
After that I hack my way right thru to the finished part. There are extra sketches and workplanes and all kinds of stuff that get in as a result of my hacking. Yes, hacking, that's how I do it. Most of those extra workplanes happened automatically and took no time to create.
Look- If I knew the finished size and shape of everything, and therefore didn't have to relate the separate parts, or project geometry back and forth, I too could create the thing with fewer features. But- the sheer number of features has no bearing in my hacking. There is no clock that says "Phil, you've got extra extrusions here, quit wasting your time." In the end, I get a part with the correct envelope size, the correct ingredients, and the correct special geometry that makes this thing so wonderful once it's a product. Along the way, I broke Inventor and all this mess started.
Consumer goods are a mix of standards, and creativity. Art. My artistic parts tend to be wilder, because I am chiefly concerned with a perfect appearance or rather, the result. The destination, not the path. All the constraints, or discipline in the world will not unlock that extra bit of creativity I get from flowing thru a part this way. IV gets a standing round of applause for letting me make these messes into things people look at and wish to purchase- bad process, extra sketches, too many workplanes later.
|
|
|
|
|
Posts:
12,130
Registered:
04/20/06
|
|
|
|
Re: ATTENTION Inventor Developers! This part has repeatable crash
Posted:
Oct 28, 2008 8:13 PM
in response to: philpdx
|
|
|
Perhaps some explaining of my process will help. After that I hack my way right thru... But- the sheer number of features has no bearing in my hacking. I take more interest in the complex stuff like this at the boundaries of what Inventor can do. But I think you are actually working too hard and probably taking more time than is necessary. I do a lot of hacking too - but only as far as it gets me in understanding the geometry. The interrelationships between projections, constraints, parent/child features can get so complex that it really pays to do your hacking and then start over. Often several times, lest the quicksand get too shakey. With the complexity of your work I'm sure you will run into more interesting problems that Autodesk should take a look at. Welcome to the forum. I hope you will share more.
|
|
|
|
|
Posts:
85
Registered:
11/13/06
|
|
|
|
Re: ATTENTION Inventor Developers! This part has repeatable crash
Posted:
Oct 28, 2008 7:55 PM
in response to: philpdx
|
|
|
|
OK so I have read this thread for the humor in it for a while now and final decided to take a look at the part in question. Where I do agree with Troy and Josh about some of the half way thought out and uncompleted features and/or upgrades ADSK has done (this website is a shining example), I also must lean toward Dennis and JD when it pertains to this actual part. Call me anal but I truly believe there is a right way and a wrong way to most anything and this modeling method leans toward the ladder. Parametric models are co-dependant on the parameters of the features in the model that were created before them. There will always come a point when the math fails in a model such as this. I am just surprised it did not happen earlier. I am just glad mechanic working on my car (extra bolts left in the engine) or framer building my house (un-nailed studs in the walls) does not have this approach to their work. I have always worked with the idea that someone coming behind me in 5 years can open one of my models and it be rock solid and ready to edit. If this model made it to completion in this state and was ever accessed again, I am sure it would fail pretty quickly. I have had to rebuild way to many models by previously engineers to get my job done in the past to let a model go through my hands that it not nailed down.
I know the original poster was not looking for a model exam here. But if you are going to post to this site for answer on a sick part, you should expect to have at least part of the answer come from your methods.
|
|
|
|
|
|
|
|
|
Re: ATTENTION Inventor Developers! This part has repeatable crash
Posted:
Oct 28, 2008 8:14 PM
in response to: tahdesign
|
|
|
Hey Phil, what curve are you using for the flare?...it kind of looks like a Traktrix... I play around with horn loading every so often and just want to keep up with the times :)
|
|
|
|
|
Posts:
37
Registered:
07/08/08
|
|
|
|
Re: ATTENTION Inventor Developers! This part has repeatable crash
Posted:
Oct 28, 2008 9:47 PM
in response to: Albert Allen
|
|
|
|
The curve is a tractrix hybrid. We will never claim that on the box, just using the good math (ironic considering.... ) and also postitioning the tweeter to time align with the woofer. Pulse testing the machined nylon frames based on this model showed a need to move the tweeter a skosh. That's when I broke IV.
Nice to see another audio guy out there!
|
|
|
|
|
|
|
|
|
Re: ATTENTION Inventor Developers! This part has repeatable crash
Posted:
Oct 28, 2008 10:14 PM
in response to: philpdx
|
|
|
So are you horn loading a high freq driver that was made originally for horn loading or did you find a good "dome tweeter" candidate for this type of loading? I have been into Audio since equipment was still advertised with "solid state" as a selling feature and they still had tube testers in stores. We have a local audio club active here in Southern Oregon if you ever want to come down to a meeting :)
|
|
|
|
|
Posts:
37
Registered:
07/08/08
|
|
|
|
Re: ATTENTION Inventor Developers! This part has repeatable crash
Posted:
Oct 29, 2008 3:08 PM
in response to: Albert Allen
|
|
|
|
It's a dome tweeter. We are using the flare as a wave guide, not so much for loading but for good pattern control to minimize room interactions and reflections.
|
|
|
|
|
Posts:
37
Registered:
07/08/08
|
|
|
|
Re: ATTENTION Inventor Developers! This part has repeatable crash
Posted:
Oct 28, 2008 10:09 PM
in response to: tahdesign
|
|
|
|
I am anal, (about some stuff) and it's "latter".
If you consider the high school dropout working on your car to be equal to the guy who designed it, you aren't anal enough. If you consider the skilled labor that stick built your house to be equal to the architect, well, you get it. I wonder if you'd take that as an excuse: "the wheel fell off because the designer had poor workflow and now I can't remember to bolt all 5 lugs..."
Seriously, do you think the people who listen to music out of my products give a flying hoot about how many unconstrained (un nailed) sketches went into it? Nobody is questioning the ability of the part to be an injection molded resin speaker frame, now are they? Apples and oranges.
I didn't post here looking for an answer to a sick part. The parts (8 different sizes all based on this very one) are all complete and on their way to production. No sick parts here. If you note the title of the post you might get a better clue. I don't mind people's input, heck, I even plan to tighten up my anal powers to work better in the future based on this advice, however, to say that these would "fail pretty quickly" is a huge bit of conjecture on your part.
My methods, the very same methods that produced this glitch, are also the same methods I use to edit parts like this, make minor changes, and move on. Nobody is going to open these and dig around later. They are all dumb solids (.step/.sat/.sldprt) by the time the mold guys get them- BTW I wouldn't want our vendors changing/ripping off my parts anyway!
Thanks for the input everyone.
|
|
|
|
|
Posts:
85
Registered:
11/13/06
|
|
|
|
Re: ATTENTION Inventor Developers! This part has repeatable crash
Posted:
Oct 29, 2008 12:05 PM
in response to: philpdx
|
|
|
|
"They are all dumb solids (.step/.sat/.sldprt) by the time the mold guys get them"
This part of the work flow is probably the only reason there has not been any manufacturing issues.
|
|
|
|
|
Posts:
37
Registered:
07/08/08
|
|
|
|
Re: ATTENTION Inventor Developers! This part has repeatable crash
Posted:
Oct 29, 2008 3:16 PM
in response to: tahdesign
|
|
|
|
Maybe. Is that a bad thing? Getting stuff made with no problems.... hmmmm... sounds like success.
|
|
|
|
|
Posts:
1,751
Registered:
12/12/06
|
|
|
|
Re: ATTENTION Inventor Developers! This part has repeatable crash
Posted:
Oct 29, 2008 5:23 PM
in response to: tahdesign
|
|
|
|
tahdesign, you think the "mold guys" are just using the dumb solids as a reference to create more usable models?
|
|
|
|
|
Posts:
85
Registered:
11/13/06
|
|
|
|
Re: ATTENTION Inventor Developers! This part has repeatable crash
Posted:
Oct 29, 2008 6:47 PM
in response to: dan_inv09
|
|
|
|
No, with a dumb solid they most likely are just importing to their cam software and using the dumb solid a base for their programming. There probably is no need to remodel anything so that is why the delivery of the dumb solid negates the original model integrity as being an issue in this case. I believe it was indicated earlier that these models are translated to SW for china. So my point was if these modeling methods were used to produce this in SW (which I doubt SW would allow) and it was then passed onto a cam software that uses the actual SW file, the models integrity would then produce issues in the design of the mold itself.
|
|
|
|
|
|
|
|
|
Re: ATTENTION Inventor Developers! This part has repeatable crash
Posted:
Oct 29, 2008 9:54 PM
in response to: tahdesign
|
|
|
dumb solid Otherwise known, to professional CAD modelers, as a b-rep solid object. I doubt anyone using Direct or Explicit Modeling techniques and software refers to the geometry as 'dumb'. Problems associated with b-rep integrity often manifest themselves as a failure to export or import or prove to be unsuitable foundations for subsequent features. If the integrity of the b-rep object (one of the reasons for "solid modelers") is in question, and perhaps it is relevant to the particular failure mode being discussed, developers should be asked about the IV equivalent of Mechanical Desktop's AMFeatCheck command / variable. So my point was if these modeling methods were used to produce this in SW (which I doubt SW would allow) and it was then passed onto a cam software that uses the actual SW file, the models integrity would then produce issues in the design of the mold itself. So many assumptions based on so little knowledge. Not only of what other programs will or won't do but the precise nature and cause of the failure is, as yet, unknown. Was a previously undetected defect in the b-rep geometry detected or one introduced due to lack of constraint or was a pointer to a referenced object lost or corrupted or ...? [I would love to see an export of the model in its original, pre-cascaded failure, state. Trying to export then import may provide a clue to what's going on, lacking the developers' (wonder if they'll ever provide any feedback re the specifics of the defects and reasons for the behavior?) debug builds and analysis tools, as well as the reason for what was apparently an existing failed fillet.]
|
|
|
|
|
Posts:
12,130
Registered:
04/20/06
|
|
|
|
|
|
|
|
|
Re: ATTENTION Inventor Developers! This part has repeatable crash
Posted:
Oct 30, 2008 3:16 AM
in response to: JDMather
|
|
|
|
Thanks for the suggestion. I occasionally recommend LT to people wanting to get their feet wet at no cost but I'd have to buy a new computer to meet the install specs. Not very cost effective for me. ;^)
|
|
|
|
|
|
|
|
|
Re: ATTENTION Inventor Developers! This part has repeatable crash
Posted:
Oct 28, 2008 11:54 PM
in response to: tahdesign
|
|
|
Call me anal but I truly believe there is a right way and a wrong way to most anything and this modeling method leans toward the ladder. Hope the guy on the ladder is wearing his safety belt.
|
|
|
|
|
|