Audi Report

[KlausMüller8028]

Unfortunately, the Audi report does not run through can someone tell me what the reason is

[raalteh]

Hi Klaus,

Which version of the product did you use for this? The Moldflow 2023 FCS version had some problems but we solved a lot of them in Moldflow 2023 Update 1 we released yesterday.

Hanno

[KlausMüller8028]

Hi

I have Moldflow 2023 Update 1 install

[raalteh]

Hi Klaus, 

It looks like the plotmanager has a problem finding the Fill Time result.

I tried a few things:

1) The script seems to run fine on my machine (US English OS)

2) I tried to start the script without having a Study open... there is a dialogue asking you to open a study (correct!)

3) I tried to start the script on a model without results --> it produces a dialogue indicating you need results.

4) I tried to start the scrip on a model with ONLY cooling results (no filling result) --> Crash ... but the crash is happening in a different place than yours ... Regardless .. this scenario needs error handling.

I will try to connect with you. There may be things related to the German OS that I cannot do myself. 

Hanno 

[KlausMüller8028 · Accepted solution]

So that the Audi script runs without errors, the option legacy mode must be activated under Options/General.

[juan.zamora.ruiz]

Hi Klaus,

I managed to reproduce the issue you reported. The message is raised while processing slide 7 of the report, and triggered by a preceding issue when processing slide 6.

To prevent this behavior, rename the study in Synergy before running the Audi report by using only:

• Characters in the ranges A-Z, a-z, and 0-9.
• Underscore characters instead of spaces.

Best regards,

Juan Zamora

[markus_atteneder]

I've tested the new Audi Report, but I don't get deflection results. The generator stops at slice #11 with the sinkmark result.

When I try to start at 16 (deflection results), I got only the first two slices, but no deflection result.

I've tried in english and german, same problem.

Regards Markus

[juan.zamora.ruiz]

Hallo @markus_atteneder ,

Thank you for reaching out, I'm sad to know that you're experiencing this issue. I tried to replicate myself, with all tmesh types (MP, DD, and 3D) and it worked in all cases for me. I'm running 2023 with update 2.

We may need some collaborative troubleshooting to understand what could be triggering the behavior in your environment. For an easier troubleshooting I suggest we move to a support case, and we eventually update this forum thread with the outcome.

Best regards,

Juan Zamora

[markus_atteneder]

Hello Juan.

Sounds good, please open a case.
Regards Markus