Jump to content

zoltaaaan

Members
  • Content Count

    14
  • Joined

  • Last visited

About zoltaaaan

  • Rank
    Beginner

Profile Information

  • Country
    Germany
  • Are you University user?
    Yes

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. No one knows a solution? Does anyone at least have the same "problem" or is interested in a smooth solution?
  2. If you want to create solid hexa and penta elements from a shell mesh of quads and trias, then there is a simple way for exactly that purpose: https://altairhyperworks.com/hwhelp/Altair/2017/help/hm/hmbat.htm?hm3210.htm You would not need the 'extruded' surfaces from the shell mesh edges, which you have shown in your picture. You only neet one surface mesh and using 'Mesh > Create > 3D Elements > Element Offset' and 'solid layers', you can create your solid elements. But to be honest, I am not sure, if it makes sense to simulate honeycomb with solid elements. I would rather create shell elements (quads) on those extruded surfaces from your picture.
  3. Hey everyone, sometimes I have to create area connectors (for adhesive) on sheet metal parts. Those parts mostly have flanges, an area which is parallel to an corresponding area of another part. The two parts are connected at their two flanges. I wonder how can I detect this flanges automatically and create area connectors at those flanges efficiently? For Spotwelds there is the functionality "Autopitch", which detects flanges and creates spotweld connectors according to parameters. Is there something similar for area connectors? Does someone know an efficient way of creating area connectors?
  4. Hexagons and pentagons are solid elements. Where exactly do you need solid elements? Do you want the honeycomb walls to be shell elements (quad elements) or do you want each cell of the honeycomb to be a solid element (hexa or penta). To me, the latter does not make sense. If you want the cells to have a square shape instead of triangular, I think it would be easier to adjust your initial mesh accordingly. (e.g. split geometry of base surface into rectangular surfaces to get more orthogonal mesh)
  5. Hi Rahul, thank you for your reply. My HM version is 2017.2 with user profile LS-Dyna Keyword 971_R8.0. What do you mean by query 2? I do not have error messages in hypermesh. It exports without error messages. The result from issue #1 is that there is an *INCLUDE keyword missing and the result from issue #2 is that there is an *INCLUDE keyword for a non-existant include file. The only error message I get is from LS-Dyna solver and it says it could not find the include. This is the result from issue #2 and makes sense. My questions focus on the export from hypermesh, where those two issues happen without error message.
  6. Hey everyone, I ran in some problems again and wanted to know, if there are easy fixes that prevent me from adding too many manual changes to my include keyfiles. In Hypermesh, I set up a model for LS-Dyna with a tree structure of include files. Some include files are positioned with the Transformation Manager (*INCLUDE_TRANSFORM). I have two issues at the moment: 1) Remove Transformation I imported a model as an include and then added a transformation to it. The include type changed from 'Include' to 'Include_Transform', that worked fine. After some more changes, I wanted to change the type back to 'Include'. I deleted the transformation in Transformation Manager, but the type is still 'Include_Transform' now I have the issue that upon export, there is no '*INCLUDE' or '*INCLUDE_TRANSFORM' keyword written in the keyfile. How can I change the include type back? 2) Prevent export I have an include file, which is structured in another include file (e.g. in my master file it says '*INCLUDE file_a' and in file A it says '*INCLUDE file_b'. Now I unchecked the export box in the model browser for file B, because I do not want it right now. File B is rightly not exported, but in file A it still says '*INCLUDE file_b', which gives me an error message, since file B does not exist. How can I prevent this error from happening? Edit: I found a solution. Simply check a box at 'Remove include file reference based on export status' which you can find under Export Browser > Solver Options. Thank you in advance
  7. Okay, it's not a bug. But since it was bugging me out, I kept digging. It is called solver ID and internal ID. See those TCL query commands, if you encounter this issue while scripting: hm_getsolverid hm_getinternalid There you will find more documentation.
  8. Hey everyone, I got an issue while working with Hypermesh on a car shell mesh and I am not sure, whether or not it's a bug or an intended feature. Another issue with element numbering made it necessary to write a script, which makes some changes to elements in terms of node numbering. The following issue emerged: There are elements of one part, where their internal ID does not match the shown number and their EID in the exported solver deck. I take an element ID from the solver deck, which caused an error, and used it to find this element in HM. I used "find entities > elems by id > enter id" and found the correct element. When I try to acces nodal information for my script, I use hm_getvalue. hm_getvalue entity_type <select_type>=<selection> dataname=<data name or attribute name/ID> ?row=<row_index>? ?column=<column_index>? For <select_type>=<selection>, I entered id=12345, with this being the element ID from the solver deck. This does not work and in the console it says: hm_getvalue: elems with id 12345 is not a valid entity When I keep diggin' and try to figure out the elements internal ID, I get another ID, which is completly out of the given ID range, but still works for all operations regarding element IDs... This is a problem. Because when I enter the following code... (01_Hypermesh) 86 % hm_getvalue elems id=2577577 dataname=nodes 12548061 12550870 12548063 (01_Hypermesh) 87 % *element2Dshiftnodes 2577577 1 2 0 0 0 1 (01_Hypermesh) 88 % hm_getvalue elems id=2577577 dataname=nodes 12548063 12548061 12550870 ... to change the order of the nodes in the element, it does not affect the exported solver deck. The exported elements have the other ID mentioned above and are not affected by the rotation. Oddly enough, when I use "find entities > elems by id > enter id" for the internal ID, it does not find an element. Does anyone know, if there is a general misunderstanding from my side or might this be a bug? Cheers, Niklas
  9. Hey everyone, is there a way to use a debugging mode for connector post scripts? When I normally debug a script, I open HyperMath from HyperMesh and I am able to use breakpoints and debug my code. I cannot skip user post script during connector realization, to run and debug the script separately. That is because I use some commands that have to run during realization. (e.g. hm_getprojceid) Cheers
  10. Hey everyone, I was wondering, what is a common workflow for remeshing 2D shell meshes. For example, when you work with shell meshes of sheet metals, but you do not have CAD data. You maybe have *.key or *.k files with FE model data and you want to work with this. Sometimes you have to change the mesh (add/delete openings or change the mesh size) What is a good workflow for this task? Do you see different workflows in terms of a) time needed to complete the task and b) quality of resulting mesh ? Right now, this is how I did it: 1) Import FE data to HM 2) Tools > Features: Using 'connected' gave good results Create plot elements and edit them, if necessary 3) Geometry > Surfaces > From FE: Using the feature-plot-elements 4) Delete old mesh 5) Modify surface, if necessary 6) Automesh on surface This takes quite some work. When I tried to remesh the existing elements, I had a lot of failed areas and I cannot modify the geometry that easily. The problem is, the surfaces based on a rough mesh is realy rough and not a good base for a fine mesh. I think this is a common task. Is there a better workflow?
  11. Yes, I have read the documentation about HWAT and scripting in hypermesh in general. I think it is not really clear, which coding style should be used. Also I do not think, I can get my script working, by using HWAT functions only. Therefore I use the style, described in the second link of my last post. I use a lot of those tcl modify commands (*createxyz...) and tcl query commands (hm_getmethatwhatiwant) with the occasional HWAT command (::hwat::topic::function). At the moment I do not work with real parts. I use two rectangular quad meshes of 1mm element size, which are 1,6 mm apart and I try to connect them by my weld configuration automatically. To be honest, I did not use the closest node or closest element functions because I felt, it was not specific enough. I rather used PLOTEL elements as header in the seam weld realization, to be able to extract those nodes from the hexa elements, since they are connected to one sheet by PLOTEL elements. I managed to to that, but it's quite a hassle. Figure: 1D PLOTEL elements connecting nodes of HEXA elements with nodes of QUAD shell meshes Therefor the next question: Is it possible to query elements by their type? For example in one component there are HEXA elements and PLOTEL elements, can I query then directly? What would be an efficient way, to get a list of all PLOTEL elements of one component or to get a list of all HEXA elements of one component? Okay, nevermind. I found what I needed. Data names in reference guide is a useful resource to create efficient queries. I leave this here, for others as reference.
  12. Hey, thank you, I will try that. What would you suggest to do with the closest nodes in the blue mesh? Measure distance, compare with a certain tolerance and decide, which nodes are on top and which are on bottom of the red hexas? Regarding the HWAT: I am mildly confused by the different coding styles suggested for HWAT and Hyperworks Scripting in general.
  13. Maybe this is a bit more straightforward: Does anyone know, how I can identify the set of nodes from the red hex elements, that lie on the blue shell mesh? If I can get this set of nodes, I think I can find a way to make this work.
  14. Hello everybody. To set up models efficiently and to investigate different seam weld representations, I try to put together some scripts or custom weld realizations. In the end, I want to create multiple short seam welds in a structure. Currently I am strugling to find the right tools, commands and hypermesh functions to effectively realize those seam welds with little to no user input. Manually, I am able to create the realizations, but even though I can read out the comand.tcl, there is a lot of manual selection necessary and I do not know how to automate the process with the tools I have. I quickly describe my ideas and I hope to get new ideas and suggestions, how to achive a good process of creating those welds. Current situation: A very good function of course is the connector browser. A simple seam weld with solid hexa elements is quick and easy and I use this as a starting point to connect two sheets (shell meshes). Speaking in terms of the four-stage-process, mentioned in the user guide, I want to establish a seam weld using the "Mesh dependent – adjust mesh – quad transition - imprint" process. Here I do not really know, how to create a seam weld using hexa elements and adjust the mesh accordingly, using quad transitions. But there are more aspects necessary: - solid hexa elements, connecting two shell meshes - shell meshes adjusted to hexa elements (hole in shell mesh, where the hexa elements are located) - fill hole in shell meshes with shell element row, which are in a separate component - nodes of shell meshes and shell element rows should be at the same coordinates, but do not be identical. Shell meshes and shell element rows should use separate sets of nodes. - between shell meshes and shell element rows, I want to create cohesive shell elements (here: quad shell element with zero length in one direction; node 1&3 and 2&4 have the same coordinates at the beginning of the analysis) - solid hexa elements and shell meshes should also not share any nodes, but have nodes at the same coordinates Has anyone good ideas on how to achive this kind of representation? At the moment I am strugling with very fundamental stuff. For example I try to create shell elements from the solid elements to get those two rows of shell elements, that eventually fill the holes in the two shell meshes. Those rows of shell meshes, I could use to imprint in the shell meshes and to get my set of nodes, to create the cohesive shells. Update 1: I played a bit with custom fe_configs for realization types. It looks promising, but there are two main problems: 1. When I create a custom realization type, which is totally equal to hexa adhesive (see below), I have no possibility to enter the width of the weld. 2. When I use "Mesh dependent – adjust mesh – quad transition-skip imprint", only two rows of quad elements are created (see picture, quads in red). This leads to the weird problem, where some nodes are shared between solid and (red) shell elements (orange crosses) and some nodes are douplicated and not shared (yellow crosses) CFG dyna 106 hexa (adhesive - shell gap) *filter seam *style continuous 2 *head *body 0 hex8 1 1 *post prop_dyna_matnum_seamarea.tcl
×
×
  • Create New...