I didn’t realise until today that you can’t flip a work plane’s normal in an Inventor Assembly. So using a single parameter to drive a mate constraint simultaneously, on multiple parts can prove problematic. We’ve recently been designing a rotary dining table, by turning the whole table the table sections slide out opening up a gap between them to insert another leaf. We wanted to animate that movement so we could check it worked and behaved desirably prior to commencing production. Continue Reading
I recently upgraded my design office to the 2013 release of Product Design Suite and Vault Professional. It just so happened we had dozens of drawings to release just after we had migrated. Upon transitioning to the released state the job processor was triggered to synchronise properties, update the revision block and visualisation file. Two things happened at this point, the first one I blogged about here and the second one resulted in instantaneous errors each time the job processor tried to update the revision block. Continue Reading
“Object reference not set to an instance of an object”.
As an Autodesk Vault user you will most likely have seen that non de-script message pop up a number of times. To be fair it pops up with a lot of windows software or add-ins. Well earlier this week all of the jobs in my Job Queue were instantly failing with that error. Only days before they had been working perfectly, so what had changed? I got on the phone to our reseller to talk it through, I then remembered the Job Processor is updated every year with each new release of Vault. I’d just upgraded our office to Vault 2013 but the 2012 Job Processor was set to run on windows startup. In addition Inventor 2013 instead of 2012 was registered with the operating system. As a result the 2012 job processor was trying to create dwf’s using Inventor 2013, obviously that wasn’t going to work. So I felt silly for a while, disabled the 2012 job processor and setup the 2013 one. From then on it worked perfectly. Duh! Problem solved after 10 minutes of expletives.
Early in 2012 I was wondering where Autodesk were going with two very similar products, Design Review Mobile & AutoCAD WS. At the time their functionality & real world use cases were extremely similar.
I decided to have a good look at these mobile and cloud based application by writing a 2 part blog series on the differences between the two.
Here’s another overflow blog post from my Autodesk University Class: PL1700 – A Cracking Story: Specialist Marine Interiors Experience with Autodesk® Vault Professional and Autodesk® PLM 360
After quite a lot of frustration and swearing at Vault while testing multiple scenarios, I recommend sticking with the auto generated Item numbers and removing any equivalence mapping to the Item number property from file part numbers. If you want the Part number to appear as a property within the Item then just map ‘Part Number’ to a new property called ‘Item Part Number’.
There are a few reasons why I take this approach:
Item numbers are quite simply a unique identifier. The info you really want to know about is the meta data or files associated with it
Item Numbers are non associative, even if the number is mapped from a file property. So if you change the filename & part number there is no mechanism to update the Item Number
Mapping the Part Number property to another Item Property maintains that associativity, but you do have to manually update the Item for it to happen.