Jump to content


  • Content Count

  • Joined

  • Last visited

About Burner2k

  • Rank
    Expert User

Profile Information

  • Are you University user?

Recent Profile Visitors

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

  1. Thanks Adriano for your reply. I wish HM/HW makes it more simpler to modify or select DOFs of both independent & dependent nodes of RBE3 during creation process itself. A drop down menu like "Advanced" can be provided for modifying Independent nodes DOFs to ensure users know what they are doing.
  2. Tried Googling for this as well as help in HM but is there way to specify DOFs for RBE3 Independent Nodes using GUI (RBE3 panel)? I know one can set Dependent Nodes DOFs but not able to do the similar actions for Independent nodes.
  3. Robert, Thanks for the reply. The 2nd picture from the last shows resulting surface after deleting the original offending one. The right surface of the inner hole (the non-highlighted one in the 2nd pic from the last) is good in terms of definition. I was able to deleted the original one, recreate it and resulting surface matched exactly as expected. Perhaps, I need to delete & recreate a bunch of surfaces surrounding the offending one (including the offending one as well). This is what I was hoping to avoid since it would involve a lot of work. May be, I'll try to defeature the model in CAD software itself. I don't know... Thanks for identifying another plane of symmetry in the model...missed that one.
  4. Hello, Firstly, happy new year wishes to ya'll. I've encountered this issue before. I was trying to Hex mesh a connecting rod component. The original component was of solid geometry imported as a STEP file. I've split the part to take advantage of the symmetry followed by defeaturing of the same. I had to manually remove many of the fillets and after the defeaturing process was done, the resulting entity (ies) were no longer a "solid". They were a bunch of surfaces enclosing. I tried to convert in to a solid using Solid -> Bounding Surfaces option, but I get an error "no closed volume found" with a red dot. I've tried the usual methods of identifying if any open or free edges are there in the model, but I could not identify any! I have a hunch the red dot means that there is an error with the surface and hence a solid cannot be constructed using that particular geometry. Hoping for some tips on how to resolve the red dot issue. FYI, I tried deleting that surface and reconstructing but the resulting surface is highly distorted from what it is supposed to be. To be honest, trying to repair or reconstruct the surface any further would involve a lot of work...
  5. One more bug I discovered earlier today. Was assigning elemental properties in HWX through map thickness command and HWX was creating thicknesses for elements in web erroneously. Many of the elements were assigned thickness equal to the width of the flange (as measured from web inside surface). The component in question was a simple C-Channel with many pads along the web & flange. The same midsurface with mesh assigned property thicknesses correctly in HW module. I am not able to post any comparison pictures of the above but this is not the first time that the above is happening. It happened a couple of days earlier as well.
  6. I like HWX...the geometry clean up is a breeze compared to HW and so is meshing (for most part). And I agree that it will take some time to reach comfortable usage stage. And I will try to do whatever little I can to help it make better
  7. Think around 3 years...of course on & off. Why did you ask this?
  8. Few things about HWX. Would it be possible to add a mouse short cut to access most recently used commands? May be I am not using it correctly, but I feel like I am losing a lot of time having to move the mouse cursor to recently used command on the ribbon bar. If its already there, can it be pointed out? So far, I have not come across this. Need to look in to this in more detail to see if I can assign key board short cuts to HWX specific functions like 2D meshing etc. If that is possible, then the above suggestion of shortcut is desirable but optional I guess. I am not sure how the Assembly tree behaved in 2018/2017 & earlier versions, but it would be great if the tree structure could be the same as defined in the CAD. This pertains to both HWX & HW. Currently, I feel that reviewing existing defined plate pairs before Midsurfacing is not very intuitive. I have a hard time figuring out which face pairs are paired together. I do think that HW/HWX is trying to display pairs in different colors but it is very hard to make it out. I think I've pointed this out before, but please do an option of assigning properties to both elements & components in HWX module as well. As of HWX 2019.1, the only way of assigning properties is by using map thickness option. Becomes tedious to switch between HWX & HW versions just to assign/create property cards. One more thing (probably applicable to both HWX & HW)...please add an option to make individual components or sub-assemblies transparent. At least in HWX, up on clicking a component, a window pops up below the model tree. In this window, under visualiztion, please add option of transparency and also a slider to adjust the level of it. And I am not 100% sure of this, but I do think in HWX, the program some times does not remember recently used settings in various commands. For example, in Midsurfacing command, if I've used previously to place the newly created surface in a sorted component and up on relaunching the same command (if not immediately after a while), the default settings are reverted (i.e. surface being placed in a Midsurface component).
  9. @joekI know you guys don't like to discuss product road maps on a forum like this, but will be there be another major dot release of 2019 HW suite (like 2019.2) before arrival of 2020 release (if we go by 2019 release time frame, it could happen almost 5-6 months in to next year)? There are lot of bugs and features missing, especially in HWX. I realize not all can be added or rectified but I am hoping for another major dot release to make HWX little more usable until 2020 release. Thanks...
  10. In HW 2019 and older, after extracting mid-surfaces from a solid, the parent solid would turn transparent automatically. In HWX, this is not happening. Still not implemented or perhaps an issue on my end? What would be ideal is to have a transparency slider for each component. After mid-surfacing, the parent solid/surfaces would go to default 50% transparent but the user has option to adjust transparency as desired.
  11. I tried both the methods on a couple of very simple problems and the results matched with each other as well as my hand calc values. I will try to post the input deck files some time this week.
  12. Actually, Cables are capable of resisting Tension loads only. Personally, I've never modeled cable structures in FEA but I can think of a couple of ways in which it could be represented. 1. Use regular beam elements (CBAR or CBEAM) with DOF release option. Essentially, this option will tell FEA solver that you want the beam element to not resist specified DOFs. For example, you can release TY, TZ, RX, RY & RZ DOFs on each node of beam element. So the solver will *apply* only TX (axial) stiffness to your beam element which would simulate typical cables behaviour. I am sure if you search on this forum or in general, you will find tutorials or videos on how to specify & define DOFs release. 2. Use CGAP elements. I believe you can specify stiffness values in PGAP for compression & tension. In your case, you will make the compression stiffness value 0 and enter tension stiffness value only. To calculate axial stiffness, use the formula EA/L...for unit length, the expression reduces to just EA i.e. value of Young's Modulus in to Area of Cross-Section of your cable. I would suggest you to read up on usage of CGAP/PGAP elements. Quick internet search led me to these non-altair links. I am pretty sure there are good documentation from Altair as well on CGAP/PGAP elements. https://knowledge.autodesk.com/support/nastran/learn-explore/caas/CloudHelp/cloudhelp/2019/ENU/NSTRN-Reference/files/GUID-13853503-EF40-4D01-A1E3-988C54BEEA64-htm.html Okay on 2nd thought: Some one has posted cable query right on this site: https://forum.altair.com/topic/14261-cable-elements/ Hope the above helps. Do simple tests using the above elements. Simple enough where you know the forces in your cables through hand calc and verify the same in your FE model. Once you get a reasonably good hang of the elements usage & confidence, the same can be applied to your actual model.
  13. Wanted to point out a feature which is existing in HW 2019 but not in HWX yet. Left image is of HW 2019 & the right one of HWX. In HW 2019, it is easy to change material definitions of similar cards in one go but this feature is missing in HWX currently.
  14. Sorry can't share the model. It is proprietary. Will find out if I can post screenshots though...
  15. Hi, Does HW/HWX has a feature where it can point out why a particular geometry is not hex meshable? Doing a complicated solid and I've broken the solid down to a lot of divisions and HWX is showing me that it is mappable. But when I try to generate Hex meshes using Solid Map -> Multivolume Solids option, during mapping detect ability, HW/HWX gives me an error saying that certain solids are not mappable. What would be a nice feature is for HW to tell us why it is not mappable (may be opposite faces are not matching..some thing like that). Would be easier to correct. Also, I am getting a lot of segmentation error during solid splitting, especially when the view is set to mappable.
  • Create New...