Die Inventor FAQ wird unterstützt von:

Inventor FAQ Logo


Lesenswert in KW 40 /2009

Hallo, noch schöner ist das ganze über die Intran...

via Autodesk Inventor, PSP - Tipps & Tricks von Espendiller am 03.10.09

noch schöner ist das ganze über die Intranetseite zu präsentieren. Hab zufällig gesehen, dass der Blog geändert wurde und in meinem Eintrag den Link angepasst. Vielleicht kann ja einer das simple PHP-Skript gebrauchen:
espend.de: Autodesk Inventor: aktuelle Lizenzbelegung Intranet

Inventor 2010 Ribbons API Beispiel

via espend.de von admin am 24.08.09

Ab Inventor 2010 war es endlich soweit, dass auch dieses tolle Programm die Ribbon Oberfläche ähnlich des Office Paketes bekam. Somit wurde auch die Inventor API geändert. Es stehen Ribbons für die unterschiedlichen Dokumenttypen zur Verfügung:

Reactivating expired home use licenses (HULA)

via Autodesk RSS Feed von rss@autodesk.com (autodesk) am 01.10.09


Your Home Use License has expired and you would like to know how to reauthorize it to continue working in the product.


The reauthorization process requires filling a Home Use License Agreement again and sending it to the following email:


Europe and Middle East

Asia Pacific

Because the Serial Number will remain the same, you need to eliminate the anchor between the license file and the system license data to be able to activate the product again.

To do this, you will need to first contact Product Support to obtain the name of the license .DAT file corresponding to the product you want to reactivate.

Once you receive the file name, proceed as follows:

  1. Delete the .DAT you obtained from Product Support from the following directory:
    C:\Documents and Settings\All Users\Application Data\Autodesk\Software Licenses
  2. Disconnect the machine from the Internet.
  3. Launch the product.
  4. In the Activation Request dialog, copy the Request code and Serial Number displayed to the Windows Clipboard.
  5. Send this information to Autodesk Support to receive a destruction code.
  6. When you receive the code from Autodesk, launch the the product.
  7. In the Activation Request dialog, select Enter an Authorization Code.
  8. Paste the code received from Autodesk.
  9. Reconnect the machine to the network.
  10. Run the product.
  11. Follow the activation process.

The product will now be reactivated for a new period.

Some weekend reading with Experience Manufacturing

via Autodesk Manufacturing Northern Europe - Autodesk Inventor, Showcase, Molflow, Vault etc von steve.bedder@autodesk.com (Steve Bedder) am 02.10.09

The latest edition of Experience Manufacturing is now available for download from the Experience Manufactruing website!
The quarterly free publication for users (and also non-users) of Autodesk Manufacturing technology such as Inventor, Alias and Showcase is packed full of news, reviews and tips. This quarters edition includes:

  • Sustainable design using Autodesk Alias
  • Inventor Fusion Preview
  • Inventor 2010 Simulation and Analysis
  • Autodesk Inventor Tips & Tricks
  • New Workstations
  • Plus plenty more...
Subscription for Experience Manufacturing is free and you can have your own copy delivered to your door or desk or download it in PDF format from the website. For more details, and to download the latest edition, just visit the Experience Manufacturing website:


Device Doctor: findet aktuelle Treiber eures Windows-Systems

via Caschys Blog von caschy am 02.10.09

Moin zusammen. Kleiner Tipp für Suchfaule: die kostenlose Software Device Doctorbietet euch die Möglichkeit, bei bestehender Internet-Verbindung aktuelle Treiber für euer Windows-System zu suchen. Dazu installiert ihr das Tool kurzerhand (lässt sich allerdings auch mit 7Zip entpacken und so portabel betreiben) und führt es aus:


Ihr könnt dann direkt die aktuellen Treiber herunterladen. Ach ja: bei der Installation des Tools solltet ihr eventuell die Möglichkeit der automatischen Treiberinstallation nebst dem Senden anonymer Benutzerinformationen deaktiveren. Welche Treiber man installiert möchte man sicherlich selber in der Hand haben, oder?

Visual Basic 6 Add-Ins and 64-Bit

via Mod the Machine von Brian Ekins am 01.10.09

I saw a question in the customization newsgroup where someone has an Add-In written using Visual Basic 6 and wants to use that add-in with the 64-bit version of Inventor.  In doing this there are some issues to be aware of:

  • 64-bit Windows can run both 32-bit and 64-bit applications (exe’s and dll’s).
  • Visual Basic 6 can only create 32-bit applications (exe’s and dll’s).
  • A 64-bit exe can only load 64-bit dll’s.  It cannot use 32-bit dll’s.

In this case, Inventor is a 64-bit exe and the Add-In is a dll.  A VB 6 Add-In will be a 32-bit dll.  Based on the statements above, this means that it can’t be used by 64-bit Inventor since that results in a 64-bit exe trying to load a 32-bit dll.  There are two possible solutions; change the add-in to be an exe instead of a dll or convert the add-in to .Net where you have the ability to create a 64-bit dll.

Changing a VB 6 Add-In from a DLL to an EXE
Changing an existing VB 6 Add-In from a dll to an exe is very easy.  Open the project and use the Properties command in the Project menu to display the dialog shown below.  Change the project type from “AcitveX DLL” to “ActiveX EXE”.  Recompile and now you have an exe Add-in.  However, continue reading…


There are two things to be aware of when converting a dll Add-In to an exe Add-In.  The first is that the performance of the exe Add-In won’t be as good as the dll Add-In.  A dll Add-In is loaded into Inventor’s process space and API calls are made directly.  An exe Add-In runs in its own process space and is separate from Inventor.  This requires API calls to be marshaled between the two processes which is not as efficient.  How much slower it is will differ from Add-In to Add-In because it depends on what kind of API calls you’re making.

The second issue is more of a problem and is a side-effect of the fact that data has to be marshaled between the two processes.  Inventor’s API relies on Microsoft technology to do the marshaling between the two processes.  Unfortunately, this technology doesn’t support the marshaling of bitmap data.  This means that any Inventor API calls you make where an IPictureDisp object is passed as an argument won’t work with an exe Add-In.

Their are only a few calls in Inventor’s API that work with bitmaps but one of these is a function that most Add-Ins use.  That’s the AddButtonDefinition method that’s used to create a button for the user-interface.  An exe Add-In won’t be able to have icons on its buttons because of this limitation.  Icons are optional so you can remove those arguments from the AddButtonDefinition call and then the Add-In should function correctly but you’ll only have text on the button instead of an icon.

Another area of the API where a bitmap is used is when getting or setting the thumbnail image for a document.  This will fail for an exe Add-In.

Besides the issues above, everything else should work in the exe Add-In as it did before in the dll Add-In.

Converting a Visual Basic 6 Add-In to 64-Bit
Visual Basic 6 is only capable of creating 32-bit applications.  To convert an existing project to a 64-bit application will require porting the application to VB.Net, which does support the creation of a 64-bit application.  VB.Net has a VB 6 conversion tool but I would suggest that you NOT use it.  Instead, I would use the Add-In Wizard that’s delivered as part of Inventor’s SDK to create a new Add-In and copy the code manually from VB 6 into the VB.Net project.  There are too many differences between VB 6 and VB.Net and my experience is that cleaning up the resulting code from the conversion is harder than copying over smaller portions of code at a time an manually converting it.

You’ll also need to recreate your dialogs.  The dialogs are much more powerful in VB.Net so this lets you take advantage of those new features.  The basics of converting your code is covered in this post: Converting VBA Auto Macros to an Add-In.

Inventor - Adding Threads to our Model

via Autodesk MSD CAD applications tips and tricks from INCAT CAD Geeks von noreply@blogger.com (Tata Technologies CAD/PLM Geek) am 01.10.09

At times within our design we are required to show threads on our models. These threads maybe on a shaft, stud or even internal to a hole. This post will speak about the thread command the options...
The Tata Technologies CAD geek team offers over 200 years of combined Autodesk product knowledge, with heavy focus on the Manufacturing product line. We're ready to answer your questions regarding product features, upgrading, moving to 3D, managing your product data better, and more […]

The same, but different...

via The Gear Box am 01.10.09

The same, but different... let me explain.  So, the same problem we were discussing for the last couple of weeks, namely, working with data from other sources.  If you recall, I had covered working with data from a vendor from whom I was buying components for our re-design.  This week, the problem is the same, but different in that in this case I am working not with a purchased component, but rather with an assembly that was created with a different design tool than the one I happen to use.

In the best of conditions, this presents something of a challenge, but when we find ourselves needing to change the design in some way, the level of complexity quickly increases.  Autodesk Inventor Fusion was built from the ground up to facilitate the toughest of these type of design challenges.  In this, the first of several posts featuring Inventor Fusion, we will take a look at some basic assembly manipulation and modeling techniques.

If you remember last week we finished up working on the Caster Wheel "Assembly" that we downloaded from our vendors web site.  Well now we are going to work on the brake assembly that attaches to two of those wheels... this was originally created in Pro/E, which is not a problem for us as we can open the .asm file natively.  Once open we can see that the existing torsion spring is not going to work in our new configuration, so we will select the body from the assembly, and then from the marking menu select "Isolate" to suppress all but the spring.

I can now make several non feature based edits to this part, quickly and easily.  As these changes are symmetric, I will split the part, then correct for rotation and position with the Move command.  Here I am moving the body along its mount axis so that it fits correctly in the bearing block.

Now we can address some of the feature lengths, but again, not via a feature edit, but rather with a direct manipulation of the feature face.  For example, as you can see in the figure above, the length of this element is a bit more than is required, so Press/Pull functionality is used to select the capping face and then press into the model, shortening the element.  As we split and then moved the entire body away from the center plane of symmetry, the split face is now short of the center plane by the amount of that first move.  Press/Pull is used here again, but in this instance I will select the symmetry plane after picking the capping face, and the pulled face "snaps" to that plane.

Finally, the corrected spring is mirrored about the symmetry plane and the assembly saved for use back in the top level assembly.

The thing that really hits you with Fusion is how absolutely easy it is to use.  The entire edit sequence shown above took no more than a couple of minutes... Don't take my word for it... check out the entire session for yourself in this video I shot.  As always, if you have any questions or suggestions I would love to hear them.


Corrupt CascadeInfo.cas file results in failure of cascading functionality

via Knowledge Base am 30.09.09

If the CascadeInfo.cas file is corrupt due to a power failure or any reason, cascading functionality will not be available.


Cascading functionality is lost due to a corrupt CascadeInfo.cas file.


If the CascadeInfo.cas file is corrupt due to a power failure or any reason, cascading functionality will not be available.


Given the following cascading sequence and a license server with a license for Product B & Product C:

Product A -> Product B -> Product C

Cascading failure may present itself in the following way:

Startup Problems:

Scenario 1: A product that did not have its own license and that was previously starting by using a shared license through cascading will fail to start.

Example: The Product B license is available on the server.  If the CascadeInfo.cas file is corrupt, Product A will not start on license B.

Example: The Product B license is borrowed to a system where Product A is also installed.  If the CascadeInfo.cas is corrupt, Product A will not run on the borrowed license.

Example: If Product B is already running and CascadeInfo.cas is corrupt, Product A will not share the B license and will fail to start.

Wasted licenses:

Scenario 2: An already running product will fail to cascade up to and share another license.

Example: Product B is already running then Product C starts up.  If CascadeInfo.cas is corrupt, Product B will not switch over to share product C's license after a few minutes.

Expected Log File output

Here is the expected log file output.  You should see a fatal error message with a vendor id of 10 (eVendorIDCascade) and a vendor error of 6 (ADLM_CASCADE_STATUS_DECRYPTION_ERROR).  It will also be followed by an AdlmInt error of 47 (ADLM_STATUS_ERROR_CASCADING_OPERATION).

1012 2009/09/16 15:07:20 Reason=Fatal error
1012 2009/09/16 15:07:20 ComputerName=MyComputer
1012 2009/09/16 15:07:20 OS=5.2.3790.Service Pack 2
1012 2009/09/16 15:07:20 File=AdlmIntLicense.cpp,Line=xxxx
1012 2009/09/16 15:07:20 VendorID=10
1012 2009/09/16 15:07:20 VendorError=6
1012 2009/09/16 15:07:20 Reason=Fatal error
1012 2009/09/16 15:07:20 ComputerName=MyComputer
1012 2009/09/16 15:07:20 OS=5.2.3790.Service Pack 2
1012 2009/09/16 15:07:20 File=AdlmIntNWFBLicense.cpp,Line=xxx
1012 2009/09/16 15:07:20 AdlmIntError=47


The current workaround it to rename/remove the corrupt CascadeInfo.cas file following these steps.

  1. Return any borrowed licenses

  2. Check in any checked out licenses and exit all Autodesk products

  3. Rename or delete the corrupt CascadeInfo.cas

Moldflow UI Technology Preview Now Available

via It is Alive in the Lab von Scott Sheppard am 29.09.09

"Seasons don't fear the [ribbon], nor do the wind, the sun, and the rain. We can be like they are. Come on baby, don't fear the [ribbon].
"The Reaper," Blue Oyster Cult, Agents of Fortune, 1976.

We learned a great deal when we gathered your thoughts on the Autodesk Inventor UI Technology Preview. Your feedback shaped the implementation that made its way into Inventor 2010. The process was so valuable to us that we decided to do it again.

The Moldflow User Interface Preview provides an updated interface that highlights the work flow required to run Moldflow products. For each of the products a central Home tab guides you on the functionality available, whether it’s to display results in Autodesk Moldflow Communicator or run a filling simulation in Autodesk Moldflow Adviser or Autodesk Moldflow Insight. It also groups commands based on your current task allowing you to enter as much information as you wish. In the case of Adviser, it allows novice users just interested in a filling pattern to do everything they need from the Home tab so aren't presented with unwanted options, while more advanced users can delve in to access relevant functions in a logical location. It makes many of the standard Autodesk functionalities available to the Moldflow products so users familiar to Inventor should be able to pick it up quickly.

If you have Autodesk Moldflow Communicator 2010 or Autodesk Moldflow Adviser 2010, you can take the ribbon interface for a test drive and let us know your thoughts at labs.moldflow.ui@autodesk.com. Perhaps the process can repeat itself? We are looking forward to your feedback.

Collecting user feedback to shape the future of our technology is alive in the lab.

Autodesk Showcase 2010: Calender Page for October/Oktober 2009

via Collaboration Blog von mcdbr am 30.09.09


The leaves are falling this means October is knocking at the door! This means it is time for a new Calendar Page.
This Time I got a Formula Student Race Car from my friends from the Autodesk CE office. As you may know Autodesk is participating and sponsoring Formula Student, never heared about it. -Be sure, next year there are 3 Teams that get supported by Autodesk here in EMEA.

Ladies and Gentlemen, please be prepared to start your virtual engines. :-) -BTW this time I am coming up two cause I could not decide which one looks best, I love both.

Die Blätter fallen, und somit ist es bald Oktober. Es Bedeutet auch es wird Zeit ein neue Kalenderseite zu entwerfen.
Dieses Mal habe ich ein Modell genutzt was ich von meinen Freunden im Autodesk CE Büro in München bekommen habe. Es ist das Modell eines Formular Student Rennwagens, denn Autodesk nimmt an den Veranstaltungen der Formular Student teil und sponsort auch die Veranstaltungen. Noch nie davon gehört? -Das wird sich ändern, denn nächstes Jahr werden 3 Teams hier in EMEA ihre Rennwagen mit Autodesk Produkten planen, prüfen und realisieren.

Also meine Damen und Herren machen Sie sich bereit Ihre virtuellen Motoren zu starten. :-)

-Übrigens, ich konnte mich nicht entscheiden welches Bild ich nehmen soll also überlasse ich Ihnen die Wahl.

oktober2009_1.jpg oktober2009_2.jpg

Autodesk Vault Report Template Authoring

via Autodesk Manufacturing RSS Feed von rss@autodesk.com (autodesk) am 29.09.09


Vault Collaboration 2010 and Vault Manufacturing 2010 provide the ability to generate formatted reports representing data contained in a vault. Reports can be generated for files, items, and change orders. The Vault objects that appear in a report are determined by the search options specified in the Advanced Find dialog.

Kostenlose Sicherheitslösung: Microsoft Security Essentials veröffentlicht

via Caschys Blog von caschy am 29.09.09

Bereits im Juni hatte ich die Betaversion der kostenlosen Sicherheitslösung namens Microsoft Security Essentials hier im Blog vorgestellt. Heute erschien dann die für jedermann kostenlose Finalversion. Microsoft möchte damit sicherstellen, dass auch Anwender über ein sicheres System verfügen, die vielleicht aufgrund eventueller Kosten für ein “normales” Sicherheitsprogramm lieber ungeschützt unterwegs sind.


Ganz ehrlich: es gibt viele kostenlose Sicherheitslösungen. Trotzdem werde ich dem Produkt aus dem Hause Microsoft mal eine Chance geben. Sicherlich, mit momentanen 55 Megabyte ist es kein Leichtgewicht im Arbeitsspeicher – aber who cares? ;)

Interessant ist diese Lösung auf jeden Fall für kleinere (oder auch große) Firmen: die Microsoft Security Essentials sind auch für den gewerblichen Einsatz kostenlos. Eine Einschränkung, die viele andere Lösungen aber haben. Für Firmen, die sauber bleiben wollen also definitiv ein Argument.


Ob Microsoft halten kann was es verspricht, bleibt abzuwarten. Sicherlich werden gerade Produkte von Microsoft kritischer beäugt als andere Lösungen. Ich für meinen Teil bin gespannt was die ersten “richtigen” Testergebnisse neutraler Institute so ergeben. Bis dahin bin ich mal mutig und nutze die reine Kombination aus Windows Firewall und den Microsoft Security Essentials. Wer von euch testet auch?

iLogic Do's and Don'ts

via Garin Gardiner am 29.09.09

As many of you are already aware, Autodesk released a new tool to the subscription center earlier this year called iLogic. I posted a blog post back in March it you would like to get a little more information. Inventor iLogic extends and enhances parametric design capabilities, automates tedious design tasks, and adds higher levels of design intelligence to your digital prototypes. With an easy-to-use authoring capabilities and an intuitive user interface, Inventor iLogic integrates seamlessly with Inventor.

I know many of you have downloaded it and are using it and I also know many of you haven't had a chance yet. I received a Top 10 Do's and Don'ts document from the design team that can help you get started. It is also useful if you have been using iLogic to help you make more robust models with iLogic.

Working with Catia data in Autodesk Inventor

via Autodesk Manufacturing Northern Europe - Autodesk Inventor, Showcase, Molflow, Vault etc von steve.bedder@autodesk.com (Steve Bedder) am 29.09.09

With the release of Inventor 2010 earlier this year we were given the ability to open 3D model data that was created using Catia V5 and also save 3D Inventor parts and assemblies in Catia V5 format. This gives Inventor users the ability to collaborate with clients, suppliers and colleagues who use Catia during their design process.
Within Inventor 2010, the Open dialogue box has an extensive list of file types that can be opened which includes (amongst many others) JT, UGS NX, SolidWorks, DWG, Pro/Engineer and of course Catia V5. By selecting ‘Catia V5 Files’ from the list you can select any of the .CATProduct or .CATPart files that have been created using Catia V5.
.CATProduct files are similar to Inventors .IAM assembly files and contain references to .CATPart files which are similar to Inventors .IPT part files. If you choose to open a .CATProduct file that has references to .CATPart files, all of the related data will be opened into Inventor 2010. If you choose to open a .CATPart file, the part will be opened so you can quickly re-use it and save it as an Inventor .IPT file.
When you select a Catia V5 .CATProduct or .CATPart file to open into Inventor 2010, you can change the open options that will allow you to configure what you want to import and how you want to import it. The options dialogue gives you the ability to choose whether you want to import Solids, Surfaces, Wires etc and how you want the imported data to behave e.g. do you want the assembly to be an assembly, single part, multi-body solid and do you want to import surfaces as single surfaces, composites or as a group. There are also options to Check Parts during Load and Enable Advanced Healing; both of these options are post process options that check the quality of the data and allow stitching.
Setting the options when you are opening data that originated in other software will help you when re-using it within Inventor 2010 making sure you have access to the 3D geometry quickly and easily.
When you want to share your 3D Inventor data with a Catia V5 user, just use the Export > CAD Format... option and select Catia V5 from the files of type. Once again you can set the Options which allows you to include Sketch geometry (or not) and also set the version of Catia V5 that will be using the data (R18, R17, R16 etc).

Keine Kommentare:

Kommentar veröffentlichen

War der Beitrag hilfreich oder hast du eine Ergänzung dazu?
Ist noch eine Frage offen?
Ich freue mich auf deine Rückmeldung!

Related Posts Plugin for WordPress, Blogger...
Inventor FAQ Newsletter. Emailadresse: