AutoCAD Inventor :: Export Multi Value Text User Parameter
Aug 26, 2010
I created a sketch that I would like to use in an iFeature. The sketch dimensions are controlled with an ilogic rule referencing a multi value text user parameter, eg the text parameter pull down menu controls the size of the part.
Is there an easy way to get this parameter into an ifeature or derived part?
Parameters with a text value, How do I add userParameter? In iLogic
Examples. DoubleValue)
Sub Main()
Dim oCompDef As PartComponentDefinition oComDef = ThisApplication.ActiveDocument.ComponentDefinition Dim oParams As Parameters oParams = oComDef.Parameters Dim uParams As UserParameters uParams = oParams.UserParameters strVal= uParams.AddByExpression!("strVal", 0.15, "mm") iLogicVb.UpdateWhenDone = True End Sub
I am trying to make an iPart of a fitting where I can change the "Body type" and it will change all the parameters associated with that body type through iLogic. Really I am just playing around in iLogic to see if this is something worth learning. Back to the point, I would like to change a multi-value user text parameter through the iPart table but I cannot find the paramter in the parameters tab.
Since it is a user parameter I thought it would be in the "Other" folder but it isn't. I do however have the other multi-value user number parameter in that folder, which makes me think that maybe I can't use the paramter in the iParts table?
INV 2012 SP1 Windows 7 64 Bit ATI FirePro V5800 14.0 GB RAM
We are having issues with text height and variations depending on how the text is added.
I am currently adding etching to sheet metal parts by using the user parameters (which are driven by 3rd party source, excel file) and using a cut extrusion -1mm.
We have developed a marco which detects the shape of each letter and adds etching to our sheet metal program manually. We do this to get rid of the double lines when you cut text into a part. Our process is design in Inventor, unfold then convert to DXF 2004, where we import to our SM programming package (Radan).
I have noticed that when using 10mm simplex if the text is driven by parameters and 10 point text is selected the charecter height is 9.9928mm, however if the text is added manually it measures 10mm exactly. Why is this happening? It is probably of no concern to most, but we would need to add extra charecters to our macro to account for the descrepency, and in turn would take the macro longer to run.
When the text is added by user parameters, you can briefly see the 10mm text height flash to 9.99mm when finishing the edit sketch. Changing this to 10mm again has no effect.
what is causing this, or have any alternative ways of adding 10mm simplex single line etching to a dxf from an Inventor 2012 SM part?
I'm using the "Part Number" parameter inside a block of text in my drawing, but when I export it to AutoCAD DXF 2010 format, the text in the exported file shows up as "<PART NUMBER>", instead of displaying the actual part number.
I'm trying to connect the value given by a calculated User parameter to a text. I've been looking for information everywhere, none found. Is it possible to show that value in a multiline text?
Looking for sample VBA code to get all referenced documents from an assembly and add a boolean user parameter to each (parts and sub assemblies). I have been trying to modify peices of code I have found on this forum and Mod the Machine, but have had no luck so far.
There may also be standard content center parts in the assembly as well that I would like to somehow identify so I can skip over them.
Most of the time, I delete an user parameter without problem. But, in a part, I got an error for two of them and I don't understand why. I create a new parameter and redirect all dependencies from the old one to the new. (oldParam.Dependencies.Count = 0).
But when I try to delete it, I've got an error. Also, when I try to delete it by the interface, I don't see the Delete option.
We have multiple clients and each client has multiple projects. Each project gets its own master assembly that contains multiple equipment layouts. This allows us to show everything together. In each master assembly, we create LODs to display equipment layouts side by side for connecting things one to another and to avoid collisions.
Example: The master assembly may contain 8 equipment layouts. Each layout is for a sub-process within the whole process. We create LODs for different groupings of layouts so that we can zero in on anything in particular that we wish to focus on. By choosing an LOD in the open dialogue box prior to opening the master assembly, performance is improved because we're only opening what we need instead of everything.
Within an equipment layout are any number of assemblies. We can create LODs to show the layout without conveyors or to show different options we've developed to present as concepts for approval prior to detailed design. Sometimes we are adding assemblies to an existing layout so we'll create an LOD for existing, one for as built, one for purposed.
how to create or modify LODs. Therefore, we are getting LODs with users' initials or a date or "doohickey". We've got to come up with something that makes sense now and will make sense later.
Any guideline for managing LODs in a multi-user environment?
I'm having problems with the parameter menu. When I don't have a user parameter linked to a dimension in the model the parameter disappears out of the parameter menu.
I have a part file ("part1.ipt") that has a user parameter called "Height". When I open this file as a part document, I can modify the "Height" parameter to change the height of the part. This functionality works great:
Set oPartDoc = oApp.Documents.Open(sPartFileName, True) Set oParameters = oPartDoc.ComponentDefinition.Parameters 'change part height to 30 cm oParameters.Item("Height").Expression = 30
Now, I am wanting to add this part to an ASSEMBLY document, then change the parameter to 30, but have been unable to do it. I have this so far:
Dim oAsmCompDef As AssemblyComponentDefinition Set oAsmCompDef = oApp.ActiveDocument.ComponentDefinition Dim oOcc As ComponentOccurrence Set oOcc = oAsmCompDef.Occurrences.Add(sPartFileName, oMatrix)
After I add all the parts, I highlight a part in the assembly pane, I click on FxParameters but I don't see the User Parameters for the part. Are the User Parameters not available when a part is placed into an assembly?
This assembly will have multiple parts added from the same file name, but the "Height" parameter needs to be modified for each occurrence.
I have an iLogic template part that has a multi value parameter. In this case the product code can be selected from a list of 4 codes. In futre we may need 5 and the 5th may need to be available to older parts.
I would like to avoid having to add the 5th as an option to every part we've ever made when the 5th becomes required.
I'd like to have the list of codes stored in an external file (Possibly an xml) and the template part reference that file to acquire it's list of available codes. That way I can add codes to the xml and all the files will have their list of available codes updated.
Macro for writing the sheetmetal Extents width and length to the custom properties. I need to get these values into the part parameters so that they can be used in the BOM.
I can get this to work if I manually create the "SM_Length" user parameter, but how do I make the iLogic CREATE the parameters if they do not already exist? I think it would be something added below the "Catch..." just cant seem to figure out what it needs to be.
'look for custom iproperty and try to set it Try iProperties.Value("Custom", sExtLength)=Round(SheetMetal.FlatExtentsLength, iRoundValue) Parameter("SM_Length")=Round(SheetMetal.FlatExtentsLength,4)
Catch ' assume error means not found and create it customPropertySet.Add(Round(SheetMetal.FlatExtentsLength,iRoundValue), sExtLength) EndTry
I want to use iLogic to create User Parameters with Multi-Value lists filled with info from an excel spreadsheet. What is the code to create a new User Parameter?
i7-2720QM Dell Precision M6600, Win 7 Pro 64-bit, 8GB RAM Autodesk Product Design Suite Ultimate 2013 Autodesk Vault Professional 2013
I have a Multi-Value Parameter "MV" that I want to populate using a Named Range from an Excel file that is already populating other parameters for the same file.
I currently have the file working by populating "MV" by using the snippet from iLogic below...
The reason I don't like this method is because if ever that range changes... all the iLogic code will have to be updated as well. How to set a Multi-Value Parameter using a Named Range from an Excel file? I assumed the below snippet would work but I am receiving
"Array was not a one-dimensional array." as an error.
I have a users who cannot change parameter values for iLogic unless user is a local admin on the workstation. This machine has just been upgrade to Inventor 2013.
I have created a large complex assembly that is parametrically driven by a skeletal sketch ipt by means of an embedded excel spreadsheet.
I am cleaning up the models by deleting obsolete user parameters. But there is one that will just not give me the option to delete it.
I have interrogated the model inside and out but can not find anywhere that this parameter is still being used.
I go into the Parameter Dialogue Box (ƒx) and hover the cursor over the parameter and there is nothing that apears that indicates theis parameter is used anywhere in the model.
Is there an iLogic routine or some other method that will allow me to run a check or a search through the model that will point me to where the parameter might still be lingering.
I have attached a JPG if it will make things clearer.
RHRT_1 is the Parameter I am trying to get rid of.
BTW. The Models and Assemblies I create are guarded by Proprietry Laws so I am unable to send a copy to anyone.
I've created a main assembly containing several ipart components. With the following rule I can read the model parameters, but not the user parameters of the iparts:
A = Parameter("Part1:1", "d0")
If I create a component, insert it in the main assembly and make it an ipart afterwards, the user parameters can be read out with ilogic. But if I insert the same ipart again, the user parameters can not be read out anymore. Model parameters are no problem.
I am setting up a family of parts that consist of a round disc with a fixed OD and a circular pattern of notches cut into the OD. The notches must go to a certain depth from the center, so those parameters are set. My problem is that I need to control the amount of material left between the notches, along the OD, after the pattern is done. Given the fixed parameters of the major OD, minor OD (3.5" in this case) and number of notches, the only way to control the amount of material between notches is to change the angle. When I set up the sketch to do the notches, I can only get a fully constrained sketch if I assign a specific angle to the notch. I need to be able to set it up so that the angle of the notch varies so the end result is a specifc amount of material left after the circular patter is completed.
In the attached PDF, I show what I have done so far. In this case the OD of the part is 4" and the diameter of the notch at it's closest to the center is 3.5". So basically, I end up with a driven parameter of 0.443. If I assign this value the parameter of d14, I need to make it equal to a ratio of another parameter (let's call it d15) so that d14 = d15*2.. This can only be accomplished by changing the angle.
In my family, the major OD and minor OD remain the same, but the angle must change to retain a specific amount of material between the notches when the number of notches is increased or decreased.
Is there an iLogic rule I can write to control this?
Any way to modify a user form parameter's read only status using a rule?
I have a parameter that I want people to be able to edit when another parameter is set to true and to be locked if it's set to false. The only thing that comes to mind is have a rule that will just switch the value back automatically if the user changes it but it would be good if i could control the read only status.