🎉Community Raffle - Win $25

An exclusive raffle opportunity for active members like you! Complete your profile, answer questions and get your first accepted badge to enter the raffle.
Join and Win

FSTOSZ Error #13: DLINK dependent DESVAR repeated in input data

User: "Turbokraken"
Altair Community Member
Updated by Turbokraken

Hello Everyone,

 

Here I am yet again with another OptiStruct issue I need your support for.

 

I am currently doing a multi-Phase Composite optimisation and I encountered a Problem with Phase 2: Size Optimisation.

When I activate the SDTOSZ command during my FreeSize optimisation, I receive faulty sizing-data. If I plug the xx.sizing.fem data back into HyperMesh and run a 'Check', I receive the following error message:

Error #13: DLINK dependent desvar repeated in input data. (17x)

 

This unfortunately happens in all other FSTOSZ data as well. I could not find any solutions or a workaround for this.

I would be very grateful if you could perhaps help me with this issue :)/emoticons/default_smile.png' srcset='/emoticons/smile@2x.png 2x' title=':)' width='20' />

 

Best Regards and a good week,

Lennart

 

Find more posts tagged with

Sort by:
1 - 10 of 101
    User: "Altair Forum User"
    Altair Employee
    Updated by Altair Forum User

    Hi Lennart,

     

    Can you sahre the complete .out file, please?

    User: "Altair Forum User"
    Altair Employee
    Updated by Altair Forum User

    also, do you have Ply balance constraint on your laminate?

     

    If yes can you remove the same and try again?

    User: "Turbokraken"
    Altair Community Member
    OP
    Updated by Turbokraken

    Hi,

     

    please find attached the OUT-Data, however there is not a lot written in it.

    I made another test with a ply Balance constraint and appearently the Problem only appears when I do have a ply Balance constraint in there.

    Is there a Workaround for when I do not use a ply Balance constraint?

     

    Best Regards,

    Lennart

    Unable to find an attachment - read this blog

    User: "Altair Forum User"
    Altair Employee
    Updated by Altair Forum User

    Hi,

     

    yes, this is a known issue with Ply balance constraint. 

     

    If possible, please share an example model file to test at our end. 

    User: "Turbokraken"
    Altair Community Member
    OP
    Updated by Turbokraken

    Hi Prakash,

     

    Thank you for your help. I looked into the data again and I noticed that I did not use a Balance constraint. What I used was a constraint that binds the thickness of two plies.

    If I use it, it works. if I don't it does not.

     

    Regards,

    Lennart

    User: "Altair Forum User"
    Altair Employee
    Updated by Altair Forum User

    What I used was a constraint that binds the thickness of two plies

    Can you share a screenshot of the card?

    User: "Turbokraken"
    Altair Community Member
    OP
    Updated by Turbokraken

    Hi,

     

    please find attached the Card with all relevant info on the Balance-Constraint.

     

    Best Regards,

    Lennart

     

     

    <?xml version="1.0" encoding="UTF-8"?>Unbenannt.PNG

    User: "Altair Forum User"
    Altair Employee
    Updated by Altair Forum User

    Hi,

     

    Yes, the issue is with Ply balance. If you have ply balance on the orientations other than 45 and -45, the analysis stops with that error. 

    User: "Turbokraken"
    Altair Community Member
    OP
    Updated by Turbokraken

    Hi,

     

    Thank you for your answer. Is this the way it is intended to be or will there be a patch in the future to include all other orientations except +/-45°?

     

    Best Regards,

    Lennart

    User: "Altair Forum User"
    Altair Employee
    Updated by Altair Forum User

    HI,

     

    Yes, this is the way it is for now. But, enhancement receipt is available to include other orientations as well :)/emoticons/default_smile.png' srcset='/emoticons/smile@2x.png 2x' title=':)' width='20'>