Jump to content


Popular Content

Showing most liked content since 09/18/18 in all areas

  1. 3 likes
    Hi, Deleting those files usually helps, Or you can write a .bat files like below: "C:/Program Files/Altair/2017.3/hm/bin/win64/hmopengl.exe" -nouserprofiledialog -uOptiStruct Search HyperMesh Startup Options in Altair Connect or in Help doc for more info.
  2. 2 likes
    Thank you very mush!I use it to check a solid.It shows Intersections found.But how can i see the intersection facets?
  3. 2 likes
    please Try this: variable list1 proc framework args \ { *createmarkpanel comps 1 "Please select the components "; hm_framework registerproc getorderedcomps graphics_selection_changed; *clearmark comps 1; } proc getorderedcomps args \ { variable list1; lappend list1 [noIntersect;]; } proc noIntersect args \ { variable list1; foreach item [hm_getmark comps 1] \ { if {$item in $list1} \ { continue; } else {set comp $item}; } return $comp } framework puts $list1
  4. 2 likes
    Okay, it kind of got solved. For everyone who has thr same issue. The System or the Mateial orientation dialog does NOT work for this. (2017.2) However you can create a coordinate system und put it into the property as CORDM. Select "USER" and choose the coordinate system. The materila will orient itself around the X-axis.
  5. 2 likes
    Hi Set w .wDemo Destroy $w Toplevel $w Wm transient $w . For {set i 1} {$i<5} {incr i} { Frame $w.f$i Label $w.f$i.lbl -text "Input $i =" Entry $w.f$i.ent Pack $w.f$i.lbl -side left -anchor w Pack $w.f$i.ent -side right -anchor e Pack $w.f$i -side top -anchor nw -fill x } Button $w.b -text Proceed Pack $w.b -side top -anchor e
  6. 2 likes
    @Vikas Kumar Absolutely, because if remove the HyperMesh-Commnet, the solver deck does not contain the any Label and Types. Like this-> So, HyperView will create the both sets of Node and Elements with labeled by ID. Thanks, Imoto
  7. 2 likes
    Hi, In your code, destroy .window11 will close the window. Not sure how to close it as soon as you enter a value.
  8. 2 likes
  9. 2 likes
    Hi @etrud011, you can record the command using F10 panel and use it accordingly, for example *createmark elements 1 "displayed" *createmark elements 2 *elementtestjacobian elements 1 0.7 2 2 0 " 2D Jacobian " *deletemark elems 2
  10. 2 likes
    1. The idea is to use the 2D mesh to impose a mesh pattern on hexa mesh. If you want a specific mesh pattern in the through-thickness direction you can also 2D mesh the sides and use nodes or elements as guides (elems to drag/match, along geom). Note that imposing mesh patterns in 2 directions requires well thought out meshing plan as it needs to be 2 directionally mappable. Maybe you will find videos on solid map helpful . 2. surf geom in the case of provided screenshot can be set to none, because it is already defined by elems to drag. Select the surface opposite to the 2D mesh as dest geom. Please hit the like button on useful tips
  11. 1 like
    Hello @John1989 The FDTD solver currently only supports wire ports and edge ports, so you could use a pin feed to excite the waveguide if you want to solve it with the FDTD. You can refer to Example A-11 in the Feko Example Guide: The model that uses a pin feed to excite the horn antenna can be switched to and solved with the FDTD. It is on the development roadmap to support waveguide ports for the FDTD solver. If this is of importance to you, or if you would like to be informed when it is supported, please request this through the official support channels - see Altair Connect for support contact details or to create a support request. Kind regards Madelé
  12. 1 like
    Glad to help. You can verify the element orientation by performing analysis on a simplified model (single element) with highly anisotropic material parameters.
  13. 1 like
    Hi, Finally the issue comes from the fact that the .dat comes from Catia v5 Can't explain why
  14. 1 like
    Hello, Massive thanks for your reply... As you undoubtly already noticed am i not such an experienced user in hyperworks. Your response is very clear and exactly what i needed Thanks a lot Ivan!!
  15. 1 like
  16. 1 like
    Hi JIAYU SUN This is because the GeForce series of Nvidia is not officially recommended by HyperWorks. However, this warninig message only appear once. You can proceed further and you may experience some graphical issues in the future. HyperWorks_2017_Hardware_Recommendations_and_Certifications.pdf
  17. 1 like
    Do you see 'fid' variable has a negative value ? if so, you might not have the 'nodes.txt' in the current working directory. can you please make sure you have the file in current working directory, if not change the working directory or have the fullpath to the file. like: fid =fopen('C:/temp/test.txt', 'r') thanks, Manoj kandukuri
  18. 1 like
    I believe you have some modelling inconsistency in your model. Upper arm thickness coincide with parte cima. Define contact between puxator and upper arm or honeycomb.Try all with freeze contact. Not sure about the graph.Is that Displacement vs Force graph? In above shared screenshot force magnitude is 3000 however in shared file it is 2500. Can you also share .out file of the run?
  19. 1 like
    Hi Bidisha From your description I assume that you would like to extract the multi-port Z-parameters. (Note that the "MoM Matrix" solved during the Method of Moments solution in Feko is also known as the "Impedance matrix" as the elements of this matrix have the the same units and impedance.) To extract the Z-parameters you should request S-parameters in CADFEKO and then, after the simulation has completed, in POSTFEKO use the Export -> Touchstone option. Under the Touchstone export dialog there is an option to select the "Network parameter type" for the export. There you should select "Z (impedance parameters)" to then export the data to a Touchstone file. Kind regards, Johan H
  20. 1 like
    Hi @RF Engineer If you would like us to check your model setup please attach it to this post.
  21. 1 like
    Thank You for your reply Mr. Tinh but still getting error "can't read "w.lugType01": no such variable" when i run the following tcl file in hypermesh #*********************************************************************************** proc ::Execlug01LUG {args} { set w .lugType01 destroy $w toplevel $w wm transient $w . frame $w.f2 #--------------------------------------- label $w.f2.labL1 -text "L1 =" entry $w.f2.entL1 pack $w.f2.labL1 -side left -anchor w pack $w.f2.entL1 -padx 15 -pady 2 -side left label $w.f2.labL2 -text "L2 =" entry $w.f2.entL2 pack $w.f2.labL2 -side left -anchor w pack $w.f2.entL2 -padx 15 -pady 2 -side left pack $w.f2 -side top -anchor nw -fill x #--------------------------------------- button $w.b -text Model -font {Helvetica -25 bold} -height 1 -width 10 -background gray75 -foreground blue -command {hm_setpanelproc ::modelclick} pack $w.b -side top -anchor nw -fill x } proc ::modelclick {args} { set w.lugType01 set l1 [$w.f2.entL1 get] set l2 [$w.f2.entL2 get] *createnode 0 0 0 0 0 0; *createnode l2 0 0 0 0 0; *createnode l2 l1 0 0 0 0; *createnode 0 l1 0 0 0 0; } #***********************************************************************************
  22. 1 like
    example with a circle and a external node, there are 2 tangent lines => so lineselected is 0 or 1 for the first and second line you have to identify the line id, instead of using hardcode
  23. 1 like
    Could you show a screenshot what you have currently and what you want?
  24. 1 like
    Ok, I see In case you want to position widgets in both row & column, use grid command if using pack, you need to pack label and entry in a sub frame, then pack subframes top side down Or you can use place command - the most freely-positioning command
  25. 1 like
    the following items were edited: -orthotropy direction was defined in global X direction -fully integrated elements were defined on properties -contact were modified to reduce initial penetrations IA_5.0_edit2.hm
  26. 1 like
    Student Editionには使用制限があり、HyperMeshの中からソルバーを実行していただく必要がございます。 多くの機能はHyprMesh内で設定可能であり、未対応のものもUnsupportedCardsに記述して頂くことで幾分カバーできると考えられます。
  27. 1 like
    Hi albertolazzeri, By looking at these images, i think you don't need inner sphere and those extended cylinders. What ever you have meshed, only those components are enough. and i also see that you have not assigned properties to the components. Make sure you assign proper properties to the components and then run the optimization. Thank you
  28. 1 like
    Hi This is possible and is exactly what time analysis in POSTFEKO does. The analysis is based on FFT/IFFT and thus the signal is inherently periodic (you can't avoid it).
  29. 1 like
    Thanks Tinh for your advice. I cannot open 2nd session even wait for hours. Actually, I already called Altair Support and found this issue only happen in user account (not full writing permission). Admin account is fine. This bug was fixed in v2017.2.2. We can close this topic.
  30. 1 like
    Hi again @Premanand Suryavanshi I tried to resolve the issue with simple model and I meshed the inner surface as well. in following I adopted linear solid mapping as shown in figure 1 and found it useful with settling issue (figure 2). Many thanks for your considered time and your extreme guidance. Sincere thanks again Good luck and blessed
  31. 1 like
    Hi Pablo I I hope you have done 2D tria mesh using Automesh. For doing an volume tetra mesh, the mesh should be an enclosed volume ie; No free edges. Try fixing the free edges and check for equivalence. Go to Tools > edges and check for free edges and equivalence nodes if any If that doesn't work, share your model please
  32. 1 like
  33. 1 like
    In current program you can use catch {unset ref_temp} in the beginning.
  34. 1 like
    I fount the problem. When MAT9ORT is defined for material, all directions of G and NU has to be filled in.
  35. 1 like
  36. 1 like
    Hello, I think somes lines are missing. You currently have input and output faces highlighted. In fact you also need to have more internal faces (4 faces are missing). In order for Flux to create theses faces, you need to create 8 more lines. This is compulsory for Flux to be able to create the meshed coil. I hope it will help. Patrick
  37. 1 like
    Hi Bachelor, I fixed the part to show up the dialog. Please find attachment. convert.tcl
  38. 1 like
    Hi @Intan Use Minimize Weighted Compliance for Constrained Volume OptiStruct provides the response type WCOMP, weighted compliance, to be defined on the DRESP1 card. In addition, you need to define the weight factors for each load case included in the weighted compliance function. Note that both the objective and constraint are global quantities (not specific to any single load case) and thus the DESOBJ and DESGLB statements occur before the load case declarations.
  39. 1 like
    Hi Ivan, Thank you a lot for you several answers and modifications, that works now much better! We're trying now to understand all what you did Guerric
  40. 1 like
    Hi @dilaawaiz, I think UserManual.pdf chapter 2.22 Sources would be a good starting point.
  41. 1 like
    Hi The corrected file is shared here. BENDING_0000.rad BENDING_0001.rad
  42. 1 like
    Hi, if the last word of STR is "second" : set STR [string range $STR 0 [string last second $STR]+5] or regsub second.* $STR second STR
  43. 1 like
    Hello Mrt, This is mostly unanswerable in a forum without the model and detailed information. Here some hints: If you have a lot of geometry, then check the geometry refinements level (Options->Graphics->Refinement Level) and set it to 1 Be sure to shade the complete (geometry) model at the beginning of the work, this will tessellates the geometry. There were already bugs that depended only on the representation of the geometry. Sometimes internally there are extremely many geometrical support points & lines, try the following: Use the Menu "Geometry->Geom Match Topology" tool, use your global geometry tolerance and run This will rebuild the geometry based on the current interpretation and fix a lot of geometry errors If you have really big models, don't use the advanced remesh topology revision option Instead, set "keep mesh" (Options->Mesh->Topology Revision->Keep Mesh), this will keep the existing mesh Otherwise Hypermesh will do crazy checks and remesh operations. Always check the geometry cleanup tolerance, global element size and node tolerance (Options->...) Avoid too small values Best Regards, Mario
  44. 1 like
    @marta in the STEPII files you shared, there is reference to .sty files (/INISTA control card). Instead, I have turned off this card and imported .sta file (with FE overwrite) from STEPI and the simulation runs fine. step2.hm step2_0000.rad step2_0001.rad STEPI_0001.sta
  45. 1 like
    Hi Andy, Something like this should help: *createmark tags 1 all set lst_tagIDs [hm_getmark tags 1] foreach tagID $lst_tagIDs { set tagval [hm_getvalue tags id=$tagID dataname=name] set tagdata [split $tagval :] set tagName [lindex $tagdata 0] //Write procedure to Modify tagname to integer if it has any string in it (Remove N-) set tagNode [lindex $tagdata 1] *clearmark nodes 1 *createmark nodes 1 $tagNode *renumbersolverid nodes 1 $tagName 1 0 0 0 0 0 }
  46. 1 like
    Hi 3D---> detach all elements (not detach from, simply detach) ---> take faces for detached elements, now give equivalence to all detached elements (shift +F3), now F10 ---> 2D --> Duplicates--> save failed Create new collector in model browser --> organize all the saved elements in the new collector by using 'retrieve elements'
  47. 1 like
    When you use hm_pushpanel to invoke panel "automesh" to help user to adjust mesh, hm_pushpanel will return soon and not wait for user finish his work. => do not use hm_pushpanel, you need to pack all remained script into hm_setpanelproc example: eval *createmark surfs 1 $::FlangeSurfs set Holes [p_GetHoles surfs 1] hm_entityrecorder surfs on p_SplitHoles $Holes hm_entityrecorder surfs off eval lappend ::FlangeSurfs [hm_entityrecorder surfs ids] hm_setpanelproc { hm_setcollector automesh [hm_getcolnumber automesh 1] surfs hm_initpanel { eval *createmark surfs 1 $::FlangeSurfs hm_activateitem [hm_getitemnumber automesh mesh] } hm_callpanel automesh eval *createmark elems 1 {"by surface"} $::FlangeSurfs p_SolidMap elems 1 }
  48. 1 like
    Sorry for the late reply. Just saw this open question. The MetaCurve will eventually be completely replaced by the Blend Curve as we add more and more features and options to it. As a result you will be able to achieve what you are looking for. And just some additional information regarding Class A surfacing. There is generally a lot of confusion about what what it is, what it means, and how to achieve it. There are "A" surfaces and "B" surfaces. "A" surfaces just means the visible/aesthetic side of the model, and "B" surfaces are the side of the model you can't see. Take a computer mouse for example: The exterior surfaces that you can see and touch are all "A" side surfaces, whereas the inside faces of those pieces are all "B" side surfaces. The confusion comes in when you start trying to define mathematically what Class A means. For every company and product the definition can be different. For some the definition can be as simple as tangential (G1) continuity as their minimum requirement, where others may require a minimum of curvature continuous (G2), or curvature continuous (G3). These are all technically Class A surfaces, but due to the automotive influence in the design culture most people associate Class A with G2 continuity or higher. But you also have to keep in mind that the higher the level of continuity the higher the chances are to introduce "wavy" surfaces because the modeler has to manage more and more points and their relationships to each other. So just because a surface is mathematically G3 doesn't necessarily mean it is the desired shape. There are a lot of things that I could get into on this, but I will leave it here for now. So can Evolve be used for Class A surfacing? Absolutely. We have customers all over the world doing this on a whole range of products. Our tools such as Loft, Sweep, Patch, Round, etc...all have options for G2 continuity. The only exception for Class A surfacing with Evolve would be automotive exterior stamped sheet-metal, which is a very special case where additional tools and control are needed and the Class A definition requirements are much higher. Hope that helps.
  49. 1 like
    2点間の距離を計測した際に、もっと細かい値まで確認したい。 プルダウンメニューView⇒Command windowを表示して、「hm_getdistance nodes 節点番号1つ目 節点番号2つ目 座標系ID(全体座標はゼロ)」と入力して下さい。 例えば、節点番号1番と2番の距離を測りたい場合は、下図のようにします。
  50. 1 like
    Class A surfacing is a methodology and modeling technique. Evolve contains some concepts of class A modeling like curvature continuity but is not the ideal tool for creating flawless surfaces, like those you see on automobiles. The inherent quality of class A surface is its ideal CV distribution. Certain tools in Evolve are based on parasolid(same engine as solidWorks) and deliver undesired CV distribution that can later be partially redistributed. Evolve has construction history, that makes it hard to redistribute points while maintaining dependencies. Most programs like Alias, leader in Class A surfacing, requires you to delete the history before manual manipulation of CVs. However, the nomenclature is slightly flawed. Everyone knows that to achieve a class A surface, the underlying curve must be of the highest quality. Therefore, your curves must contain the least number of CV's and show smooth curvature. See image attached. If you use the top curve to create surfaces, the output will be low quality. The bottom curve has a very close shape but with better CV distribution. Hence, while creating curves, use the curve plot tool - shortcut -SHFT+CTRL(CMD)+P and check the quality of the curve. For product design, class A surfacing is not a mandate, unless you are talking about Apple, that is very particular on surface quality. You can achieve good surface quality in Evolve at the expense of time.
  • Create New...