Search results for query: *

mburlone, Thanks for the tip, i have a series of simplified reps in the assembly, so it sould be a easy test to try. I'll give it a shot, Thanks Again!!!! kgrzebien

I am having an issue with saving large files (across the network). Mostly in large assemblies that are programed. It appears like it is timing out after about 30 seconds or so then Pro crashes. The realy strange thing is if I call up the assembly, I can save it as long as I don't regenerate it...

Peterstock, Thanks again, I tried your idea and still have the same issue. Nomatter what I have tried, everytime I try to create the csys the part automaticly rebends. I have tried creating the csys in the generic, and in the instances them selves with no luck. I have a part programmed to 4...

Peterstock Thanks, thats what I thought but when I try to create the coor. sys. in the unbent part it always rebends itself. So the coor. sys is in the wrong spot. What am I missing?

I am trying to place a drawing view at the origin of the drawing sheet so that the lower left corner of the part is EXACTLY on the lower left corner of the format. I need to do this for a sheetmetal part to be DXF'ed out to our plant for manufacturing. Is there a coordinate system on the format...

Thanks, cadcamguy, that's what I was looking for!. The procedure I have is much older, this should do the trick!!

I am looking for an updated version of a process to create a coil spring along the path of a 3D curve. (a spring over a piece of nylon tubing). I have a process written for Pro/E version 21. I'm sure there must be an easier way now, Any ideas? Thanks

I just loaded Wildfire 3 and I'm having trouble hiding the Datum axis for certain features. They appear to be included in the sketch of the features now. Example I put in an Axis to revolve a feature around, then create the feature and then the axis seams to be part of the feature now and I...

tydguy, worked perfect!!! Thanks KTG

I have a text file of various paramater sets that I drop into relations. Exit relation. Reopen relation and delete the previous text. The values will be added to the paramter list Example: step 1: put the following into "relations" (copied from text file works well to reuse the values)...

I have a drawing with a dimension that I want to read as "B" (not in quotes). When I try to change the dimensions properties from @D to @S and change the name to B instead of ad293 I get a error saying "SYMBOL IS RESERVED OR ALREADY EXIST". I believe the drawing had a dimension called B before...

THANKS!!! This sounds like exactly what I need I'll give it a try!!!!

Thanks for the help but the dimensions do not exist in the model. This is a sheetmetal part in the flat pattern. We model the bent-up and let the system un-bend the flat. The parts will not have actual model dimensions to use in the drawing.

Another quick question: Can I wna to calculate a part weight based on created dimensions, example:[(&ad1 x &ad2)/ 144] * 2.133 ad1 = dimension horizontal ad2 = dimension vertical 144 = converts sq in to sq ft 2.133 = a weight factor for sheet metal (ryerson cataloge)

Thanks!!

I do some extensive programming within Pro/E, In general the only thing I like to keep in my family tables are the paramters that define each instance. For example if I have a series of parts that will change by size and material type, I will put columns in the family table for those paramters...

Where can I find a list of the system paramters that come within Wildfire2. example: "model_name" etc. For some reason I can't remember where the standard list of system paramters is. I'd like to add a peramteric note to my drawing with the weight of the part in it.

Loading the assembly into memory works, sorry I should have mentioned that, but I am not the only person who needs to use this model. If one of our other users need to access the model they would not know to load assembly_1 into memory first. WE are not running any type of management software...

I have a wierd problem with one of my assemblies (call it assembly_1.asm), it fails on installation (as a component in a larger assembly, call it: assembly_2.asm) if the working directory is not set to the directory inwhich assembly_1.asm was created. one of the instances used in the assembly...

I got it to Work!! I'd post the image if i could figure out how (sorry it's been a long week) Thanks to all for the help, Especially "telecomguy"