Inventor Nesting issues galore!

[fridtjofZM5ME]

For some reason I'm having loads of issues with Inventor Nesting:

1. Preformance is extremely slow, and apparently somewhat unstable.
2. Custom CC parts are attempted to be added, those should be skipped.
3. Parts designated as Reference or Phantom in the BOM structure are added to the nest, and should be skipped just like parts designated as Purchased.
4. Custom frame members authored as sheet metal parts do get added to the nest, but are defaulted with a quatity of zero, forcing me to enter the correct value for each part manually one by one.
5. Add sources from Vault isn't working anymore.

Are all of these known issues, or are there known ways to med these problems?

[fridtjofZM5ME]

For some reason I'm having loads of issues with Inventor Nesting:

1. Preformance is extremely slow, and apparently somewhat unstable.
2. Custom CC parts are attempted to be added, those should be skipped.
3. Parts designated as Reference or Phantom in the BOM structure are added to the nest, and should be skipped just like parts designated as Purchased.
4. Custom frame members authored as sheet metal parts do get added to the nest, but are defaulted with a quatity of zero, forcing me to enter the correct value for each part manually one by one.
5. Add sources from Vault isn't working anymore.

Are all of these known issues, or are there known ways to med these problems?

[AmyLiu]

Hi @fridtjofZM5ME 

thanks for your feedback, could you please provide more details:

1. for performance, what's the workflow you did? and if possible to share your data for us to do investigate?
2. item 2 and item 3, for CC and Part designated as Reference or Phantom, these are not supported yet as known issues. 
3. for item 4, please check the BOM QTY,  when nesting, the default value is set as same as BOM QTY. you could change QTY there. 
4. for add from Vault command, any details, is there any message/information how it doesn't work? and what's the vault version

[AmyLiu]

Hi @fridtjofZM5ME 

thanks for your feedback, could you please provide more details:

1. for performance, what's the workflow you did? and if possible to share your data for us to do investigate?
2. item 2 and item 3, for CC and Part designated as Reference or Phantom, these are not supported yet as known issues. 
3. for item 4, please check the BOM QTY,  when nesting, the default value is set as same as BOM QTY. you could change QTY there. 
4. for add from Vault command, any details, is there any message/information how it doesn't work? and what's the vault version

[fridtjofZM5ME]

@AmyLiuI've uploaded the files to Autodesk Drive, I would need an email adress to share the folder with.

Regarding the Zero-QTY in nesting, the main assembly BOM looks like this:

The circled items are custom frame members authored as sheet metal parts.

The work flow is as follows:

1. open iLogic configurator and make changes.

2. check in files to Vault

3. copy design with new file names

4. open assembly -> right click top level of assembly tree -> create nest

5. repeat steps 1.-3. as needed for the number of unique production items.

6. open assembly -> right click top level of assembly tree -> create nest -> add to open *.inest file

I eventually managed to create a nesting study yesterday but opening it today the following happens:

After openAfter refresh

The sources appear to randomly disappear when refreshing. It's not consistent, and doesen't happen to every assembly. Even if they all are generated by Copy Design from the same iLogic configurator.

Adding from Vault:

At some point this error showed up and has been persistent for quite some time. At least since the 2021 version. The current version for both Inventor, Vault Basic client, and Vault basic server is 2022.2.

Regarding the preformance, everything froze the first time I tried this, but this time I got it to work(-ish). Sometimes when Nesting starts calculating the nest, the process just stays at 0%, and sometimes the system is just unresponsive for up to a minute before something happens.

[fridtjofZM5ME]

@AmyLiuI've uploaded the files to Autodesk Drive, I would need an email adress to share the folder with.

Regarding the Zero-QTY in nesting, the main assembly BOM looks like this:

The circled items are custom frame members authored as sheet metal parts.

The work flow is as follows:

1. open iLogic configurator and make changes.

2. check in files to Vault

3. copy design with new file names

4. open assembly -> right click top level of assembly tree -> create nest

5. repeat steps 1.-3. as needed for the number of unique production items.

6. open assembly -> right click top level of assembly tree -> create nest -> add to open *.inest file

I eventually managed to create a nesting study yesterday but opening it today the following happens:

After openAfter refresh

The sources appear to randomly disappear when refreshing. It's not consistent, and doesen't happen to every assembly. Even if they all are generated by Copy Design from the same iLogic configurator.

Adding from Vault:

At some point this error showed up and has been persistent for quite some time. At least since the 2021 version. The current version for both Inventor, Vault Basic client, and Vault basic server is 2022.2.

Regarding the preformance, everything froze the first time I tried this, but this time I got it to work(-ish). Sometimes when Nesting starts calculating the nest, the process just stays at 0%, and sometimes the system is just unresponsive for up to a minute before something happens.

[fridtjofZM5ME]

@AmyLiu Another issue I forgot to mention is that it appears that Nesting doesen't like file names with commas in them. I had one that didn't work, and renamed the files replacing the comma with a dash, and it worked after that.

[fridtjofZM5ME]

@AmyLiu Another issue I forgot to mention is that it appears that Nesting doesen't like file names with commas in them. I had one that didn't work, and renamed the files replacing the comma with a dash, and it worked after that.

[AmyLiu]

@fridtjofZM5ME 

thanks for the details, I will look into and try to reproduce the issues you met.

about the email, you could send to "cui.liu@autodesk.com".

[AmyLiu]

@fridtjofZM5ME 

thanks for the details, I will look into and try to reproduce the issues you met.

about the email, you could send to "cui.liu@autodesk.com".