Altair RISE

A program to recognize and reward our most engaged community members

Nominate Yourself Now!

OSSmooth Error in 2020

Hello,

I'm running into the following error when running OSSmooth (iso surface FEA reanalysis) in HyperMesh/Hyperworks 2020 on topology optimization results from Optistruct 2020:

'BOM comments unsupported in the command.'

Nothing is imported into the model when this message is shown. This only appears to happen when using 2020 HyperMesh and Optistruct, but if one or both are the 2019 version, it works fine. I'm also able to open up the results file in Hyperview without a problem. Has anyone seen a similar issue with a workaround or solution? Ideally, I would like to be able to uninstall the old versions of the software.

Thanks,

Jacob

Find more posts tagged with

English

OptiStruct

Accepted answers

All comments

Adriano_Koga

Can you try this model? I've tried here and it worked fine in my 2020 (full commercial)

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

Unable to find an attachment - read this blog

Bocaj22

Adriano,

I appreciate your help. I tried your attached model and it worked fine. I also re-ran it through optistruct and that worked fine as well. So it appears to be an issue with my simulation file. I have run the optimization multiple times with the same result. Unfortunately I'm unable to share it directly. If it helps, here is the command file tcl excerpt when I try it on my file:

*createstringarray 2 'isosurf: 3 3 0.3 0 -1 0 0 10 30 1 0' 'other_params: 1 0 0 0 10 0'
*ossmooth_12 0 1 0 1 'E:/Altair/Temp/test.fem' 'E:/Altair/Temp/test.sh' '' 1 0 1 2

The only clues are the error that is shown in HM, 'BOM comments unsupported in the command', and a ossmooth.err file that contains the text 'Invalid input model.'

Thanks,

Jacob

Bocaj22

I've figured out the problem. When I export the FEM file from Hypermesh, a bunch of XML code gets dumped at the bottom of the file. OSSmooth doesn't like it. Deleting that part of the file fixes the problem, but I don't know why it shows up. If I run Optistruct from Hypermesh, that doesn't happen. See the attached file for the XML dump. Any ideas on why this is happening?

Unable to find an attachment - read this blog

Adriano Koga_20259

Maybe it's connector information or the parts/assembly information.