Hello Inventor Users,
Did you know that Autodesk Answer Day is coming up on Sept 21st, 2017, as the second installment of the Autodesk Answer Days (Asia Pacific Series) ? This time we’ll be answering questions on Four of our most popular Products : AutoCAD, AutoCAD Mechanical, Inventor, Revit.
Head over to the Autodesk Answer Day homepage (Asia Pacific Series) for more information. We hope to see you there for this live Q&A online event hosted right here in the Autodesk Community!
AutoCAD Tutorials (Live & On-demand)
Join us at the AutoCAD Knowledge webinars to learn AutoCAD from Product Experts.
AutoCAD Knowledge webinars are regular online tutorial series hosted by the Autodesk AutoCAD Product Experts to help users learn AutoCAD and create innovative 2D and 3D designs through interactive live webinars or on-demand tutorials.
Learn more at www.autodesk.com.au/campaigns/autocad-tutorials
Hello Inventor Users,
Did you know that Autodesk Answer Day is coming up on July 13th, 2017, as the first installment of the Autodesk Answer Days (Asia Pacific Series) ? This time we’ll be answering questions on Four of our most popular Products : AutoCAD, AutoCAD Mechanical, Inventor, Revit.
Head over to the Autodesk Answer Day homepage (Asia Pacific Series) for more information. We hope to see you there for this live Q&A online event hosted right here in the Autodesk Community!
This came up recently with a customer where they’d like to see all of the different volumes at one time for an iPart’s members. This could be used for mass or other property. The only limitation is your creativity with it.
The scope is: we want to get the volumes for all the elaborated members of an iPart factory at one time and this rule does that when we add a custom “Volume” parameter to the iPart table, trigger the rule to fire on any parameter change and edit the table via a spreadsheet. Problem: Cubic inches (or any other distance type) doesn’t have a predefined enum. So we need to use a workaround and build up a string that defines the desired units. There is the issue of the unit type changing from document to document so we won’t want to hard-code the unit value but instead be able to set it dynamically. We also want to make sure that, if the parameter exists, we’re not duplicating it and it’s correct for the current member. Here’s how the code looks:
'Dimension a variable for user paramaters
oMyParameter= _
ThisApplication.ActiveDocument.ComponentDefinition.Parameters.UserParameters
'test to see if the parameter is already there and, if so, that it matches the correct
'volume of the member using the embedded if/then/end if block
Dim param As Parameter
On Error Resume Next
param = oMyParameter.Item("Volume")
If Parameter("Volume") <> iProperties.Volume Then
Parameter("Volume") = iProperties.Volume
End If
On Error Goto 0
'If it doesn't exist, create it so that we can add it to the table. We have to concatenate
'Units of measure as a string b/c there is no enum for ^3 inches but no problem, it still
'can be had and dynamic the way we'll set it up
If param Is Nothing Then
'Get the document's units of meausure, comcatenate that with a volumetric string of ^3
'in order to show the units as volume units
Dim uom As UnitsOfMeasure = ThisApplication.ActiveDocument.UnitsOfMeasure
Dim volUnits As String = uom.GetStringFromType(uom.LengthUnits) & "^3"
'Set a parameter equal to the current properties volume adding the units of
'measure in volume units from above
Dim Vol = iProperties.Volume
oParameter=oMyParameter.AddByExpression("Volume", Vol, volUnits)
End If
iLogicVb.UpdateWhenDone = True
‘Then, once this rule is run, it’s just a matter of adding the new “Volume” user
‘parameter column (from other) we’ve created to our iPart table – just once.
I’m sure there are probably other ways to do it but it really works out pretty well with very little actual code. As a note, when you change members, you’ll get a dialog that you should answer yes to, that states the values in the active row do not match. It is asking you if you'd like to update the table with the new value before continuing. Answering yes will reflect the volume for the new member's cell value in the table in both the iPart table in Inventor as well as in the Excel spreadsheet.
Once they've all been activated and the dialogs have been answered "Yes", your values will be reflected in the table/spreadsheet.
-Daren
(1st line of code edited with underscore to fit in the provided space)
Please, find in the link below more details and possible workarounds for this regression introduced by the with "Update 1 for Inventor 2016" and "Update 6 for Inventor 2014 Service Pack 2"
The issue will be addressed in the next Updates for the products.
Inventor 2015 Service Pack 2 is now available.
Please, read the Readme file for the installation instructions and the summary of the additional issues fixed by this Service Pack.
Users reported that deleting components in assembly can end up creating "ghost" references.
This issue is resolved in Inventor 2016, but it only prevents new “ghost” references.
In this article below you can find all information for preventing this situation in older releases and how to clean an affected assembly.
Special thanks to Dennis Ossadnik for writing the article.
After splitting a hole table on a metric drawing template and moving it to a different drawing sheet.The values get changed automatically.
You could use the following steps to reproduce it :
1. New drawing and place view with holes
2. Create hole table and split the table
3. Drag split part of the table to second drawing sheet
4. Both XDIM & YDIM values change
Before moving the Hole table :
After moving the Hole table :
This happens when mm template is used, coordinates in split table on second sheet change from mm to inch and precision changes from 0.00 to 0.000. If inch template is used, only precision is changed.
Workaround : Upon moving the split table to next sheet, right click on the table and select Edit Hole Table.
This should reset both XDIM and YDIM to the correct value.
Say if you are using other options in the hole table dialog, In this instance combine notes, you can toggle back to combine notes, you will see both the XDIM & YDIM values remain unaltered.
This issue is being considered for a fix in SP2 for Inventor 2015 which will be slated for release soon.