Inventor 2010 - Tooling

[Anonymous]

I cannot past through tutorial exercise 3 - Core and cavity considerations with Moldflow. it is all ok up to stage - Defining the patching and runoff surface - where computer start patching calculation and then sort of seized using about 25% processor capacity and approx 98% of RAM memory from total 8 GB. The process creates a lot of (sometimes hundreds and other time thousands) Hard Faults / sec - according to 'Resource Overview" monitor. Similar situation i have noticed when doing Tutorial 2 - Family mold design. I have overcame the problem by finishing all processes up to patching calculation on one part – handset top before inserting the other part – handset bottom and doing it separately.

Does somebody have any advise – resolution.

Hardware: AMD 9500 – video Quadro FX 1800 – Vista Ultimate – 8 Gb RAM.

Cheers Edited by: 2grumpy on Jun 16, 2009 10:02 AM

[Anonymous]

I cannot past through tutorial exercise 3 - Core and cavity considerations with Moldflow. it is all ok up to stage - Defining the patching and runoff surface - where computer start patching calculation and then sort of seized using about 25% processor capacity and approx 98% of RAM memory from total 8 GB. The process creates a lot of (sometimes hundreds and other time thousands) Hard Faults / sec - according to 'Resource Overview" monitor. Similar situation i have noticed when doing Tutorial 2 - Family mold design. I have overcame the problem by finishing all processes up to patching calculation on one part – handset top before inserting the other part – handset bottom and doing it separately.

Does somebody have any advise – resolution.

Hardware: AMD 9500 – video Quadro FX 1800 – Vista Ultimate – 8 Gb RAM.

Cheers Edited by: 2grumpy on Jun 16, 2009 10:02 AM

[Anonymous]

style="TEXT-JUSTIFY: inter-ideograph; TEXT-ALIGN: justify; MARGIN: 0in 0in 0pt"
class=MsoNormal>
style="FONT-FAMILY: 'Times New Roman','serif'; FONT-SIZE: 12pt; mso-fareast-font-family: 'Times New Roman'">We
tried the same workflow following the tutorial, but cannot reproduce the issue
as you mentioned. I am not very sure about the impact of the environment
configurations like Hardware or OS, we will go through the workflow on a
similar
style="FONT-FAMILY: 'Times New Roman','serif'; FONT-SIZE: 12pt">desktop
(Vista&8Gb RAM). 
style="FONT-FAMILY: 'Times New Roman','serif'; FONT-SIZE: 12pt; mso-fareast-font-family: 'Times New Roman'">Before
we get the actual reason or any conclusion, could you please check if the
Moldflow analysis is in progress while you are performing the mold commands
(Patching&Runoff surface or Core&Cavity generation)?
style="FONT-FAMILY: 'Times New Roman','serif'; FONT-SIZE: 12pt"> If so, you can
wait for the process running to end and then continue to the next steps, and see
if it could be better.

style="TEXT-JUSTIFY: inter-ideograph; TEXT-ALIGN: justify; MARGIN: 0in 0in 0pt"
class=MsoNormal>
style="FONT-FAMILY: 'Times New Roman','serif'; FONT-SIZE: 12pt; mso-fareast-font-family: 'Times New Roman'">Anyway,
we are investigating the issue and will keep an eye on it. Thanks for the
reporting.

style="TEXT-JUSTIFY: inter-ideograph; TEXT-ALIGN: justify; MARGIN: 0in 0in 0pt"
class=MsoNormal>
style="FONT-FAMILY: 'Times New Roman','serif'; FONT-SIZE: 12pt; mso-fareast-font-family: 'Times New Roman'">
face=Arial> 

style="TEXT-JUSTIFY: inter-ideograph; TEXT-ALIGN: justify; MARGIN: 0in 0in 0pt"
class=MsoNormal>
style="FONT-FAMILY: 'Times New Roman','serif'; FONT-SIZE: 12pt; mso-fareast-font-family: 'Times New Roman'">Best
regards,

style="TEXT-JUSTIFY: inter-ideograph; TEXT-ALIGN: justify; MARGIN: 0in 0in 0pt"
class=MsoNormal>
style="FONT-FAMILY: 'Times New Roman','serif'; FONT-SIZE: 12pt; mso-fareast-font-family: 'Times New Roman'">Henry

[Anonymous]

style="TEXT-JUSTIFY: inter-ideograph; TEXT-ALIGN: justify; MARGIN: 0in 0in 0pt"
class=MsoNormal>
style="FONT-FAMILY: 'Times New Roman','serif'; FONT-SIZE: 12pt; mso-fareast-font-family: 'Times New Roman'">We
tried the same workflow following the tutorial, but cannot reproduce the issue
as you mentioned. I am not very sure about the impact of the environment
configurations like Hardware or OS, we will go through the workflow on a
similar
style="FONT-FAMILY: 'Times New Roman','serif'; FONT-SIZE: 12pt">desktop
(Vista&8Gb RAM). 
style="FONT-FAMILY: 'Times New Roman','serif'; FONT-SIZE: 12pt; mso-fareast-font-family: 'Times New Roman'">Before
we get the actual reason or any conclusion, could you please check if the
Moldflow analysis is in progress while you are performing the mold commands
(Patching&Runoff surface or Core&Cavity generation)?
style="FONT-FAMILY: 'Times New Roman','serif'; FONT-SIZE: 12pt"> If so, you can
wait for the process running to end and then continue to the next steps, and see
if it could be better.

style="TEXT-JUSTIFY: inter-ideograph; TEXT-ALIGN: justify; MARGIN: 0in 0in 0pt"
class=MsoNormal>
style="FONT-FAMILY: 'Times New Roman','serif'; FONT-SIZE: 12pt; mso-fareast-font-family: 'Times New Roman'">Anyway,
we are investigating the issue and will keep an eye on it. Thanks for the
reporting.

style="TEXT-JUSTIFY: inter-ideograph; TEXT-ALIGN: justify; MARGIN: 0in 0in 0pt"
class=MsoNormal>
style="FONT-FAMILY: 'Times New Roman','serif'; FONT-SIZE: 12pt; mso-fareast-font-family: 'Times New Roman'">
face=Arial> 

style="TEXT-JUSTIFY: inter-ideograph; TEXT-ALIGN: justify; MARGIN: 0in 0in 0pt"
class=MsoNormal>
style="FONT-FAMILY: 'Times New Roman','serif'; FONT-SIZE: 12pt; mso-fareast-font-family: 'Times New Roman'">Best
regards,

style="TEXT-JUSTIFY: inter-ideograph; TEXT-ALIGN: justify; MARGIN: 0in 0in 0pt"
class=MsoNormal>
style="FONT-FAMILY: 'Times New Roman','serif'; FONT-SIZE: 12pt; mso-fareast-font-family: 'Times New Roman'">Henry

[Anonymous]

Henry,
i did try to do that exercise 3 times today progressively uninstalling some software as Astroid drivers and Adobe AIR - no results. I do not have any suspicious software installed except MS Office 2007. Adobe Acrobat and Flash Player, printers etc. I have switched off Ad-Aware during testing.
Still, can do patching to single part – takes approx 5-6 sec.) However, cannot it if two parts in.
Valdemar

[Anonymous]

Henry,
i did try to do that exercise 3 times today progressively uninstalling some software as Astroid drivers and Adobe AIR - no results. I do not have any suspicious software installed except MS Office 2007. Adobe Acrobat and Flash Player, printers etc. I have switched off Ad-Aware during testing.
Still, can do patching to single part – takes approx 5-6 sec.) However, cannot it if two parts in.
Valdemar

[Anonymous]

files attached

[Anonymous]

files attached

[Anonymous]

and remaining

[Anonymous]

and remaining

[jessepeng]

Hello,

1. For issue in tutorial 2, the problem you met happens in 64-bit system. There are 2 workarounds:

1) If you want to run in 64-bit system, you can input shrinkage value "0.49" manually in the step set part shrinkage for "Exp-Mobile Top".
2) Use 32-bit system to do exercise, then it should be OK without any workflow change.



2. For issue in tutorial 3, the problem you met happens in 64-bit system too. There are 2 workarounds:

1) If you want to run in 64-bit system, you can set isotropic part shrinakge value to intead the suggest part shrinkage value. For example, set part shrinkage as "0.5" with isotropic setting is checked.

2) Use 32-bit system to do exercise, then it should be OK without any workflow change.



These 2 issues have been raised in team and we will keep track of them. Thanks for your post.

[jessepeng]

Hello,

1. For issue in tutorial 2, the problem you met happens in 64-bit system. There are 2 workarounds:

1) If you want to run in 64-bit system, you can input shrinkage value "0.49" manually in the step set part shrinkage for "Exp-Mobile Top".
2) Use 32-bit system to do exercise, then it should be OK without any workflow change.



2. For issue in tutorial 3, the problem you met happens in 64-bit system too. There are 2 workarounds:

1) If you want to run in 64-bit system, you can set isotropic part shrinakge value to intead the suggest part shrinkage value. For example, set part shrinkage as "0.5" with isotropic setting is checked.

2) Use 32-bit system to do exercise, then it should be OK without any workflow change.



These 2 issues have been raised in team and we will keep track of them. Thanks for your post.

[Anonymous]

In the future will you have similar facility for bevel gears?
It would be fantastic

Sorry, that comment was intended for different thread Edited by: 2grumpy on Jun 25, 2009 10:45 AM

[Anonymous]

In the future will you have similar facility for bevel gears?
It would be fantastic

Sorry, that comment was intended for different thread Edited by: 2grumpy on Jun 25, 2009 10:45 AM

[Anonymous]

Another workaround (64-bit) with a non-isotropic material is to construct the patching surfaces manually.
This is a very frustration, but work and it is possible to use a shrinkage non-isotropic.

Un altro workaround (64 bit) con un materiale anisotropo è quello di costruire le superfici di chiusura manualmente.
E' una vera frustrazione, ma funziona ed è così possibile usare un ritiro anisotropo.

[Anonymous]

Another workaround (64-bit) with a non-isotropic material is to construct the patching surfaces manually.
This is a very frustration, but work and it is possible to use a shrinkage non-isotropic.

Un altro workaround (64 bit) con un materiale anisotropo è quello di costruire le superfici di chiusura manualmente.
E' una vera frustrazione, ma funziona ed è così possibile usare un ritiro anisotropo.