Jump to content

Nitin Jain

  • Content Count

  • Joined

  • Last visited

1 Follower

About Nitin Jain

  • Rank

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 @Pooja S I am using Hexa (tapered T) type seam weld and I gave desired properties to it. Thanks @Ivan I ran the simulation again with switching off Spotflag. It solved my problem. But is my contact now simulating the exact condition of spot weld or not. Because from Altair manuals, I learned that Spotflag=1 represents the condition for spot welds, etc. How accurate are the results with Spotflag= off. Thanks and Regards Nitin Jain
  2. Hello everyone, Greetings!! I have made seam weld elements between 2 components. Then I made tied contact (Type 2 contact) between these components by considering seam elements as master component. But when I ran the crash simulation mass of 720 kg was added in these seam elements, which made the entire mass of my crash sled 3.5 times heavier than the actual weight. I have to use tied 2 contact as I wanted to use the contact interface for spot welds. I cant omit DT/NODA/CST, otherwise my simulation time is increasing exponentially. Because of crash simulation, some elements are deforming to a very small length. Thanks in advance. Regards Nitin Jain
  3. Hello everyone, Does someone know how to solve the above mentioned problem?? Thanks in advance. Regards Nitin Jain
  4. Thanks @Pranav Hari and @Ivan, I think making surface and then spot weld is time consuming process. Moreover I request you to please teach me, if I connect the extracted surface with connector: then solids will be connected as well or it will connect only extracted surfaces. Right now, I am trying to make the Seam weld connections (Hexa Tapered T type) but I am getting the distorted elements: I am avoiding edge nodes for better results. But still some elements are not as desired. Regards Nitin Jain
  5. Hello @Pranav Hari, I have uploaded the file on the shared link. But I have deleted some parts and Boundary conditions. Please assign boundary condition as per your convenience. Regards Nitin Jain
  6. Hello Everyone, I am trying to establish spot weld between Solid Hexa8N elements. I have tried to use 'plot', 'Type 2 spring' and 'HC Hexa' type. But in all the cases I am having following issues: 1) Type (Plot): Simulation ran but solid elements were not connected 2) Type [Spring (Type 2)]: Solver not able to identify the surface to create a spring elements. 3) Type HC Hexa: Contact interface defined by solver itself is not correct. Apart from aforementioned problem I also want to give the max tensile strength of spot weld as as 40% of base material. Thanks in advance. Nitin Jain
  7. Hello All, I have a query regarding the use of filters in Hypergraph. I am concerned about the peak force observed from my data as it can damage experimental crash sledge. With Raw data I am getting peak force as high as 924 kN. After applying SAE J211/1 filter with CFC 600, it has reduced to 431 kN. Please find following graph for more details: I request you to please guide me which value is more reliable. If i consider unfiltered force as true value, then it will damage Load cell as well as crash sledge. Regards Nitin Jain
  8. Hi @Ivan I cant move the component in z direction. As I wanted to simulate them with touch condition (gap in z direction is 0). Moreover entire geometry consist of more than 35 parts which will be a big task to align all of them again. I am having same problem with almost all the parts. I have also tried to give Type 20 contact but interference is still there. May you please share the recommended parameters for Type 20 contact for Crash Application. Regards Nitin Jain
  9. Hi All, I want to create 2 solid blocks touching each other and bolted together. I meshed them and when I import the same in Hypercrash and checked for intersections, it shows me an intersection. I have tried to resolve this by Remove intersections option or 3D mesh editing, but could not remove this intersection. Can you please help me how to remove such intersections and corresponding penetration. Thanks in advance. Regards Nitin Jain
  10. Thanks a ton @Rahul R. Hyperview is a very powerful post processing tool. Regards Nitin Jain
  11. Hello All, I want to compare the behavior of deformation of beam in Simulation and Experiment. I am using Hyperview to run animation of my simulation and MediaView to run the recorded video of experiment. Now I want to sync both of them in one window to observe the deformation behavior at different point of time. Is there any tutorial available on how to sync Hyperview and Mediaview windows in single page?? Regards Nitin Jain
  12. Hi @Ivan Thank you for your reply. It has answered my query. Regards Nitin Jain
  13. Hi Pranav Hari, Here my problem lies. If I select ''ms'' as strain rate unit, then the difference between simulation results and physical testing results is very high. On the other hand, if I take ''sec'' as strain rate unit, then the difference is acceptable. My concern is Altair has missed to assign unit system to Strain rate and by default it took values only in ''sec''. Please share your opinion. Regards Nitin Jain
  14. Hi Pranav Hari, I believe that is not the case with Hypercrash. When you start HyperCrash, you have an option to select Units system. Please find following screen shot for more details: Regards Nitin Jain
  15. Hello All, Greetings!! I am using mm, kg, ms units system in HyperCrash and using Mat Law 36 or PLAS_TAB for different parts. Therefore I have taken strain rate unit as 1/ms. But general standard unit for the strain rate is 1/sec. Therefore I ran simulation with units as 1/sec as well. Results: Simulation results of Strain rate with 1/sec units are closer to experimental results as compare to 1/ms simulation results. Above screen shot is from Radioss_10.0_Reference_Guide2. Please guide me what unit (1/sec or 1/ms) to use for accurate material modelling in Radioss. Thanks and Regards Nitin Jain
  • Create New...