No calculation of CMIF and stabilsation diagram when FRF selected as "unused"

Hello together,

i have expirienced multiple times now, that when using the "modal analysis" package, right after i did measurments, somehow the CMIF are not calculated and therefore no further investigation is possible. More than once i had this expierence and i did not understand why, but i think i do now.

I am aware that, if some nodes are not measured than the error messages occurs, and therefore no calculaton is possible. Ok.

At the beginning i marked them as "unused" rather than deleting them.

I noticed when playing with the data, the calculation was only possible though, when all points are measured (either used or unused). The other points must be deleted or the CMIF and so on won't be calculated.

The frustrating thing is : i thought "unused" and deleting does the same thing, but they don't. Especially annyoing is, that there is no feedback at all that something is wrong. It just doesnt calculate it.

Weidly though, once it is calcuated it seems to work "all the time" .

Please check if this can be replicated for anyone else.

Best regards

Daniel

DewesoftX

Version: 2023.1 (RELEASE-230123) (64-bit)

Build: Release

System: Windows 10 Build 19045 (64-bit Edition)

Hi Daniel,

I had several issues last autumn that could have been related to this. I don't have the time digging into those issues at the moment, but I think what you say could have been the issue there. I will look into this in the coming weeks.

Benjamin

Hi Benjamin,

just be careful i have the feeling, once it worked in a file, it keeps on working, Which would be even more weird , but it felt that way.

Just keep that in mind.

Best regards Daniel

Dear Daniel,

thank you for reporting the issue. We were able to reproduce it and we reported it as a bug to developers.

As soon as we fix it, we will let you know.

The workaround at the moment would be, to delete the FRF from the MA module, not just set it to Unused.

Best regards,

Dear Daniel,

our developers fixed the issue inside the MA module. The fixed version will be released with the official release, which is planned in the second half of February.

Best regards,