mmccall

YES..!!.. thats how it worked... ha.. store this thread forever.. at the top of the list.. Kevin didn't help worth a rat... he gets too much credit.. HA.. get him thinking that he's the man.. HA.. he's the little man... HA.. its fun to trash kevin.. he's like that robot squeeze toy from like the 80's.. where the eyes , ears and nose bug out..

Hmmmm.... did you go into the tool button configuration.. for got what its called.. you know.. in the options where you add the algor button in IC... and make sure that button is going to the correct path.. After loading algor.. you can start algor ... and then start IC... then you close them both... i cant quite remember the order.. this is getting old in my mind.. for some reason either algor or IC is checking the system looking for the other program... so one or the other has to be opened... then you check to see if the IC mesh button works.. When you are working in IC and testing the mesh button .. the file has to be saved.. meaning.. drop in a box in a new ic scene.. save the file.. then try to mesh.. if the file hasn't been saved.. it wont go into algor.. I have made this mistake several times.. be sure to post to let me know if any of this works.. I got another machine I need to install Algor on to see if I can help you track this down..

"#7B: FAKE IT IF YOU DON'T ............I only recommend increasing this one notch at a time until there is no further performace gain. If you do change the setting Windows will let you know that you may cause other applications to crash..." HA..HA..HA... always a trap behind the door..

If you have a large assembly with linked files.. and say for instance you are working with sections.. to make several different section types within different configurations.. example.. like in this case working on the Ares rocket a concept design i needed to show some components with sections and others without.. ' I initially tried applying the sections I needed in the top assembly.. requiring several sections.. and turning them on and off in different configurations.. man.. this took a long time.. this is a big top assembly file.. and each section having to go through the entire top assembly through each of the linked files.. a real nightmare.. and the inevitable crash.. this file gets more and more buggy along the way.. but.. got to get it done in 1 day.. A better way was to place each section in the linked sub assemblies then go to the top assembly and use configurations to turn them on and off.. but this presented a problem... remember.. I created the top assembly and the links prior to creating the sections in the sub assemblies.. so in the feature tree at the top assembly level, none of the sections actually showed up.. The fix was to move the section.. or rather assemble them into the assembly at the sub assembly level.. confusing.. in other words.. I went into the sub assembly.. selected the assembly and the section and assembled them together.. this created another strange instance.. it just wouldn't work or I found some of the components no longer recognized the section feature.. so they were full volume instead of sectioned... I had to delete the section.. but you know what?.. that didn't work either.. and for some reason all those horrible section problems from back in v6 and v8 were coming back.. the file got trashed.. had to do a copy and paste to a new file and recreate the section within the sub assembly on the first try.. you don't get a second chance at this .. so get it right the first time.. !.. Now .. once you get all your sub assemblies with the sections included.. when you go to the top assembly.. your feature tree will now show the sections in each of the sub assemblies.. .. and there you have it... you are ready to create the configurations.. In this "Tip and Trick".. i figured out the whole thing with the section not showing up in the top assembly in the tree.. in the midst of forming the tip.. i ran into some bugs... and had to come up with a trick.. .. being ready to save a file with copy and paste.. The file works fine for the most part.. but any modifications needed had better be done in the individual sub assemblies.. since they seem to be a little more stable when saving.. so if my top assembly goes down.. I can simply reopen it and all the updates with be there.. and if it ever trashed completely.. I have all the sub assemblies at a default location and the top assembly can be recreated relatively easily... When working with the really large files.. I like the ease at which IC allows you to pass the geometry to the sub assemblies.. I like to use surfaces.. or copy parts and components that I am trying to dodge or design around.. and drag them into the linked sub assembly.. then I simply open the sub assembly and there it is.. and I can continue working on the smaller more user friendly file.. The problems with this file are with the large amounts of detail.. and I forgot to mention.. this is a native WildFire file.. stepped out.. lots of pockets holes.. etc.. I have done complex files all linked native IC and have not had this many problem.. so its not entirely an IC problem where speed and some instability is concerned.. I dare say things would work better if the assembly was all native IC.. but the section tool just still seems to cause problems.. I even experimented with using an assembly cut.. HA.. things got much slower.. so I wasn't really interested in that method.... the section tool is faster than the assembly cut method in this situation.. Hope this helps somebody out there..

HA..HA.. it worked now.. yeah.. it works good..

I'll do it... working on a 3 wheeled vehicle concept for a customer now.. HA.. you really wanting this?..

tom... check with Cary... for some pics he should have.. did an entire span across all industries I worked in... lots of cool stuff.. see if any of it would help.. got some rocket stuff in there also..

http://www.ptc.com/products/proe/wildfire4/index.htm HA.. notice the feature recognition stuff... Just like catia.. trying to improve the ability to work with imported geometry... http://www.ptc.com/products/proe/frt/index.htm

Everything here seems to be running relatively smooth.. I do understand the saving / crashing issue.. and we have had several instances.. I noticed that IC really loads up the temp file.. so when working for long periods I simply make sure to empty that folder.. and it has made a big difference..also of course saving repeatedly and incrementing file name... we are not working with any sort of file management system.. all hard drives.. I'm not a computer expert.. so I'm not sure if why our problems haven't been as great as some others.. but as far as using the program and its capabilities.. we run it hard and with really large files.. lots of links .. you name it.. Each company is different.. each need is different.. and each users method of operating the program is different.. everybody likes different settings.. etc.. so in our case by mere chance we may not be pecking the CAD bugs as much as other users.. in fact.. we haven't run across any more bugs in V10 than in any other version.. again.. maybe its just the way we use the system.. In the end.. I hope it works out for you... in my experience.. all the CAD programs have problems.. you cant avoid it.. and Wildfire has definitely had its share.. good luck at getting PTC to even admit there is a problem.. HA..

HMMMMM... just wondering why I haven't been able to find the instructions on the Rhino integration.. in the help menu

If you ar in an assembly.. and have linked files.. and say for instance you are working in the sub assembly files.. moving things around... And for some reason you may not be seeing the updated models.. or especially when you change positions of the components in the subassembly... regenerating the part or assembly wont do anything.. Be sure to check your configuration in the sub assembly..and simply change them and change it back... the update wont show until you change the configuration of the sub assembly then change it back.. because if you are working in a configuration, depending on the options you choose you may never see any updates fro the movements in the subassembly.. because you may have their positions stored in the top assembly configuration you are in.. HA.. sounds confusing.. But the main point is...if you are not seeing changes you may have made.. try changing the sub assembly configuration to something else and then changing it back to the configuration you are interested in seeing..

Noticed something.. I am running Rhino on a dongle key.. for some reason when I used IC and rhino together.. when I finished.. I just pulled the key.. and continued working in IC... I keep my machine in standby for long periods.. day after day.. and continue working.. When I shut the machine down.. it was still looking for the rhino connection.. said I was still on it.. I had to kill it in the task manager.. something to keep in mind..

yep.. seems to be working fine.. I am on rhino 3.0 still have you had any problems?

yep.. thats it.. works good.. thanks..

Not sure where I heard this,.. but isn't there or rather.. wasn' there supposed to be a way to run Rhino within IC.. like some sort of toggle button like my Algor icon?

HAAAA...HAAAA... TOOO FUNNY !!!

HA... November the 12th.. thats my birthday... corresponding with the release of v10.....so I was born to use IronCad... hmmmm ... so I am an IronCad prodigy.... I am the ONE !!! So surely.. from the preceding statements.. this is the best IC version ever... ever?

Put the rotary engine I did on there..

I have also used Gibbs Cam, Surf Cam and Master Cam.. The mecsoft tools are easier in my opinion.. but like anything else.. with time and effort.. any of them should do you just fine.. but then there is also cost.. and some programs can get really expensive.. look through the tools you think you really need.. and then expand later as you need.. almost all of the programs allow add-ons... so as your needs grow.. you can build your program strength.. in the end.. once you understand one.. you can almost work with any of them.. In IC .. just remember.. that if you make a set of 3D curves to use as your tool path.. be sure to assemble them.. that way you can export them out to your program if needed.. and select "curves" option when doing iges.. The 3D curve tools in IC and Rhino make setting up paths really easy..

try this http://www.mecsoft.com/Mec/ used this stuff for some time now.. easy to use and learn.. they don't run inside IC.. but they can run internal to Rhino.. or just get the Rhino versions.. they are the same.. same company, same program.. just runs internal to rhino.. so you don't have to export any of the files.. you can run your paths and just do your post from there..

Not sure about in the BOM.. but you could create a hole table.. and adjust the reporting properties to show the quantity...

PTC Still NASA Darling The Associated Press reports on the continuing controversy over NASA giving PTC a long-term contract for design software without a competition -- and now the space agency's inspector general is asking what's going on. As well, a senator from Iowa wants to know why NASA isn't open to competitions. Anyone know which CAD vendor is located in Iowa? NASA is two months overdue on reporting on the issue; the space agency is asking vendors to submit bids providing cost estimates for data conversions to new formats. Which, of course, is the problem. NASA really must stick with Pro/E as its CAD program to preserve the integrity of the file formats. With all the problems NASA is experiencing, it surely does not need an Airbus-like data problem by introducing a different CAD system. Posted by ralph grabowski at 07:57 | Permalink Comments This all assumes that NASA actually sticks to its own standards. Problem is that on smaller projects, SolidWorks and 2D AutoCAD are used because that is the experience base of the available staff at the time. Fortunately subassembly files are generally transfered in STEP file format so that it does not matter as much which software originally created it. The whole situation does benefit PTC in that each subcontractor must buy at least a couple of Pro/E seats in addition to their own preferred design software so that they can read the few native files they might get from a NASA division. Asking the other vendors to include file conversion costs puts them at a financial disadvantage, and assumes a unified design file library, which simply isn't the case. Better yet, would be standardize the unit system for all new projects, so there would be fewer metric designed subsystems fastened to inch designed platforms with both mm and inch fasteners. Posted by: John Nolin | Apr 17, 2007 at 11:17 The former EAI was headquartered in Ames, Iowa and remains as an UGS location, so there are other states that would stand to gain or lose more. The responsible use of USA government funds would benefit taxpayers and businesses in all states regardless of Senator Grassley's motives. While NASA may have good reasons to stick with PTC, there should be no shame in seeking a fair and open decision process and avoiding supplier lock-in. Posted by: Doug Vander Wilt | Apr 10, 2007 at 11:31 What none of thes dips understand is that NASA was on UG... and somebody got a new car for turning traitor.. they lied and cheated and STOLE a contract with unfair illegal practices... evil abounds... and now things are really screwed...if any of these jerks were at the Marshall facility they would know...I had better stop before I say what I really mean...will have to give Kevin an interview.. I will write another dissertation.. an he can spread it around.. Other interesting articles found here.. http://worldcadaccess.typepad.com/blog/the_courts/index.html

I just did a scale resize on an imported assembly yesterday... after resizing.. the assembly was all broken apart.. after hitting the regen it went back together...

I have seen this for a long time .. I have no idea why this happens.. I would like to hear a suggestion on this also.. I have even looked around for some options and changed kernels.. no change...

HA... yeah.. get killed just as quick im sure of it... ha.. just sitting on a bomb either way.. HA..