Penetration Tool as in HW14.0

Hi,

which option would you like?

I see thickness option is 'component thickness' which is same as in v14

v2017 can check it base on contact so I think it's better

It just hides the original panel. If you still want to use it, try enter commands (in menu View>Command Window):

hm_setpanelproc hm_resetmenu

hm_pushpanel penetration

Hi,

You can use the traditional way by going to Tool Page>> Penetration panel

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

But that is not available in HW2017.

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

I searched in buildup menu also. But it is not there.<?xml version="1.0" encoding="UTF-8"?>

Hi tinh,

Thanks for your reply. But it says following error.

Actually 14.0 is very helpful for checking initial penetrations

Hi Udhay,

Select the Penetration Check tool from the Tools Menu.

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

Yeah George. It is there. But it is not traditional way. Same components i check in 14 and 2017 showing different results. This is happening in LS dyna profile.

2017

14.0

Hi Udhay,

I'm not sure, there might be some modifications in the latest penetration check tool.

Can you try the same in HyperCrash?.

Hi tinh,

 

Thanks for your reply. But it says following error.

 

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

 

Actually 14.0 is very helpful for checking initial penetrations

Hi,

I said above, you need to enter 2 commands:

hm_setpanelproc hm_resetmenu

hm_pushpanel penetration

Yeah tinh...

Thanks for your help..

It worked in Hyperworks2017

George,

I am not well versed in hypercrash... Sorry

Yes, but I advise you to use new style and check with 'contact'

traditional style cannot check all penetrations for lsdyna model, this problem I faced from 2007, and until 2017 they just attach the checking method by contact, you should use it.

Yeah tinh...

Thanks for your advise. I am checking that also but  using Lsdyna d3hsp file.  I will try to use this from now onwards.

 Once again thanks.

Yeah tinh...

 

Thanks for your advise. I am checking that also but  using Lsdyna d3hsp file.  I will try to use this from now onwards.

 

 Once again thanks.

I had a macro to parse d3hsp and mark penetrated nodes by depth value

Oh great.. if you are okay. share the details with me....

Hi,

script like this

proc p_ParseD3hsp {FilePath} {
    if {[file exists $FilePath]} {
        if {[catch {
            set fpt [open $FilePath]
            set buffer [read -nonewline $fpt]

            close $fpt
        }]} {
            return -code error $::errorInfo
        }
        set LineList [split $buffer \n]
        array set PenValue {}
        set MismatchedModel 0
        foreach Line $LineList {
            set Line [string trim $Line]
            switch -glob -- $Line {
                'penetrating node # *=*' {
                    set NodeId [string trim [string range $Line 28 end]]
                    if {![hm_entityinfo exist nodes $NodeId]} {
                        set MismatchedModel 1
                        break
                    }
                }
                'penetration *=*' {
                    set PenValue($NodeId) [string trim [string range $Line 28 end]]
                    catch {
                        *tagcreate nodes $NodeId [format %.2f $PenValue($NodeId)] $NodeId 2
                    }
                }
            }
        }
        if {$MismatchedModel} {
            return -code error 'The d3hsp mismatched with opening model'
        }
        #return [array get PenValue]
    } else {
        return -code error 'File not existing '$FilePath''
    }
}

Thanks a lot tinh... I will check this..../emoticons/default_smile.png' srcset='/emoticons/smile@2x.png 2x' title=':)' width='20' />

hiii...explain again