• Announcements

    • Rahul Ponginan

      Please click here for a short but important announcement   03/26/17

      Dear Users Our Commercial and Academic users around the world can use these same forums here as before i.e. the Altair Support Forum , Commercial users from India with solver queries can go to the Solver Forum for India Commercial Users , Academic Users from India and AOC India Participants are requested to go to the Forum for India Academic Users and AOC India Participants , We will be tending to all queries in all the forums promptly as before, thank you for your understanding. 

Rahul Ponginan

Administrators
  • Content count

    2168
  • Joined

  • Last visited

  • Days Won

    47

Everything posted by Rahul Ponginan

  1. The license is found under the student edition downloads section once the license is approved (takes about 5 days) This order was approved.
  2. We see that your order was delivered, India Students must write to - edu-support@india.altair.com to get the approval of the student edition,
  3. The student edition does not allow command line solving, solvers are interfaced through the app alone.
  4. Please follow the video attached , you can contact local HyperWorks support directly for help setting up server licenses Altair License Manager Installation_12.0.3.wmv
  5. The HyperWorks student edition interfaces with solvers only through HyperMesh (HW Apps) and not through command line or solver manager, Please solve the file through the apps itself,
  6. Michal1509, Can you please confirm if the above has helped you?
  7. Use windows folder options > unhide known extensions, to make sure the file is named altair_lic.dat and not altair_lic.dat.dat, You need to confirm if the Ethernet address in the license file is the correct one and matches the one in your machine. When you open the license file in a text editor you will see an Ethernet address there in a line that says "ETHERNET = The Ethernet ID is the ID of your machine which is exactly 12 hexadecimal numbers. For example D4WRF478F398 Run ipconfig/all in command window and check for physical address under Ethernet adapter local area connection: The listed physical address under Ethernet adapter local area connection should be used to generate the license file, That means if the address provided as above does not match the one in the license file, please request for the license file again with the correct Ethernet ID. You can check your computer’s Ethernet address, by using the almutil -hostid application from the Start > Altair > Tools > Admin tools Menu and compare it with the result in the command window, Alternatively run getmac in command window to find out available Ethernet addresses to cross check as well,
  8. It is important to first try deleting the downloaded file and downloading it again from the site. To make sure the file is not damaged on download, run an md5 checksum on the downloaded file (just google md5 checksum) and make sure the checksum result matches the one given in the site where the files are downloaded from, Double click / run the Winmd5 checksum executable (download win md5 a freeware from the internet, please note we cannot be responsible for external content and info) Select the executable by clicking on the browse button or drag and drop the file into the window The AcuSolve installer extracts two 7-zip archives to install the product. In this case, it looks like only one of them got extracted. The AcuSolve directory should be about 2.4gb. Could you check the size on your customer’s PC? Could you try using the AcuSolve installer as a standalone and overwriting the current install? You might want to try cleaning up the directory that $TMP points to and rebooting the PC first,
  9. It is important to first try deleting the downloaded file and downloading it again from the site. To make sure the file is not damaged on download, run an md5 checksum on the downloaded file (just google md5 checksum) and make sure the checksum result matches the one given in the site where the files are downloaded from, Double click / run the Winmd5 checksum executable (download win md5 a freeware from the internet, please note we cannot be responsible for external content and info) Select the executable by clicking on the browse button or drag and drop the file into the window Regards
  10. Please delete the settings files as below and restart the app Please make sure you have a supported graphics card as in the list attached (and that the supported card is in use and not an onboard one instead) and the supported / latest driver version, HyperWorks_2017_Hardware_Recommendations_and_Certifications.pdf
  11. We see that you have ordered the Altair student edition from the Altair store and this was delivered to you, The software requires a license file to function, please login to your Altair Store account to download the license file. You should find the license file in the Student Edition Downloads section, After downloading the license file, rename it to altair_lic.dat and place the same in the <installation directory>/security folder If you have already done the above and still face the error, let us know and we will troubleshoot accordingly.
  12. Please request for another license with 84-EF-18-66-4A-E5 Make sure you have your wifi on when using the software,
  13. Can you confirm you have the simlab feature in the license file? you can open the license in textpad and look for a feature called FEATURE SimLabPrePost and two other features with the text simlab.
  14. Please describe the error / problem in detail, thanks.
  15. FEMFAT is a comprehensive fatigue analysis tool that provides quick and reliable answers concerning the safe operation of components. FEMFAT Showcase Video2 minute video introduction to durability and fatigue tool, FEMFAT Note: This video does not contain sound, but does include subtitles View the Video Mahindra Two Wheelers Success StoryTwo-Wheeler Designer-Manufacturer Cuts New Component “Time to Market” and Optimizes Component Design with the Altair Partner AllianceView Mahindra Success Story FEMFAT allows you to configure development tasks and production processes more efficiently and cost-effectively. It also allows to identify critical areas in the early stages of development and to simulate processes and connections. FEMFAT offers fatigue life prediction (FLP) of all vehicle components (engine, gearbox, chassis, frames, car bodies and structures) and machinery equipment based on Finite Element Analyses (FEA). Additionally to consideration of complex multi-axial loadings an assessment of welding seams as well as spot welds and self-piercing rivets in steel and aluminum can be carried out. Components undergoing thermo-mechanical loadings can be assessed considering effects of material plasticity, elevated temperature (oxidation) and creep. Strain gauge measurements could be utilized for simulation adjustment and verification. Nevertheless, FEMFAT can assist you in FLP of fibre reinforced plastics (FRP) and laminated structures. Interfaces for co-simulations and databases are under development. About Magna Powertrain Magna Powertrain Engineering Center in St. Valentin offers modular software solutions for calculation and simulation in the field of vehicle development and production. Magna Powertrain’s software solutions are deployed successfully by leading vehicle manufacturers around the globe, providing support in many fields. FEMFAT is available through the Altair Partner Alliance. –Gunther Pessl, Manager of Simulation/CAE BMW Motoren GmbH Key Features & Benefits Reliable results on the fatigue life of structures to improve critical points Virtual optimization results in less weight, higher level prototypes which consequently leads to less tests Multiple fatigue influences (notch, mean stress, manufacturing technology,…) Large range of interfaces to finite element codes Large Material Database included; verified from tests or generated according to material relations found also from guidelines like FKM, key to steels, Bargel Schulze,... Analyses results verified by countless tests in own test lab Leading fatigue analysis code in automotive industry Technical leadership in many areas (e.g. 3D-stresses, joints, production influences) High analysis speed and flexibility Open database concepts (material, joints) Easy handling: minimum of settings and methods required Best verification and blind benchmark results Gallery Conceptional study of CFRP wrapped dual use tank (picture with courtesy of TEUFELBERGER) <> Industry Applications FE-based software for fatigue analysis and optimization on components, such as: Engine crank case, cylinder head, crank shaft, and connecting rod Axles and suspension components Body in white, chassis structures with spot joints Transmission housing and transmission components Welded steel and aluminum structures Low weight frames for tractors, trucks, buses, rail transport systems, cranes, etc. Product Interfaces FEMFAT has interfaces with Altair's HyperMesh, HyperStudy, HyperView, MotionSolve and OptiStruct; as well as Converse by PART Engineering.
  16. What is stored in each of the FEKO files?
  17. FEKO projects consist of a number of files, including *.cfx, *.cfm, *.bof and *.out files. What is stored in each of these files? Which of these files are critical for reproduction of a result if I want to send the model to someone? The following table defines the data contents of each of the FEKO file types. The columns have the following meaning: · Extension lists the extension of the file that will be present in a FEKO simulation directory. · Content describes what information is stored in this file. · Required is a YES/NO boolean indicator, specifying whether this file has to be present if you want to send the minimum number of files to someone and want them to be able to reproduce your results. Extension Content Required *.cfx CADFEKO model file that stores geometry, solution specifications. Yes, when using CADFEKO. *.cfm CADFEKO mesh file that is imported by the numerical engine when it runs the simulation. No *.cfs CADFEKO session file that stores the state of the CADFEKO view that the user last used to open the same view when the model is opened again. No *.pre Text-based instructions to the FEKO numerical engine. Advanced users may edit these settings, but in typical use CADFEKO will set up this file. No, when this file was generated by CADFEKO. Yes, if this file has been edited or created by the user. *.pfs POSTFEKO session file that allows the user to save POSTFEKO sessions with views, image rotation and data representation parameters for later recall. No *.bof FEKO results file in binary format. No *.out Text-based output file. No *.fek All mesh and and solution instructions are formatted into a single FEK file that is readable by die solution engine. No *.afo Continuous frequency results created by ADAPTFEKO (continuous frequency) No *.cgm Contains the size of the residue that results from the iterative algorithm which solves the matrix equation and the number of iterations. This file is only generated when specifically requested. No *.dbg When using the UTD, it is possible to request an optional output file containing a large amount of additional data (and may therefore be very large), see the UT card. No *.efe File containing the electric field strengths. Contains both the position and the complex components of the electric field strength vectors. This file is only generated when specifically requested. No, unless used in equivalent source definition *.fek Output file from PREFEKO -- serves as the input file for FEKO. No *.ffe File containing the far field data. This file is only generated when specifically requested. No, unless used in equivalent source definition *.gfe Interpolation table of the electric field strengths for the Green's function of a layered sphere. No *.gfh Interpolation table of the magnetic field strengths for the Green's function of a layered sphere. No *.hfe File containing the magnetic field strengths. Contains both the position and the complex components of the magnetic field strength vectors. No, unless used in equivalent source definition *.inc Include file for PREFEKO. No No *.log Log file created by OPTFEKO. No *.lud File in which the elements of the LU-decomposed MoM matrix are stored. This file is only generated when specifically requested. No *.mat File in which the matrix elements of the linear equation system, are stored. This file is only generated when specifically requested. No *.opt Input file for the program OPTFEKO. No *.ofc Paging files for the array elements used with sequential and parallel out-of-core solution. No *.os File containing the surface currents and the currents in the segments. The data includes the physical position and the complex components of the current density vectors. This file is only generated when specifically requested. No *.pcr Exported ILU preconditioner for the FEM. No *.pfg POSTFEKO graph file. No *.pfs POSTFEKO session file. No *.ray When using UTD or RL-GO an optional ray file can be requested. This file is not required when visualising rays in POSTFEKO. No *.rhs File containing the right hand side vector in the system of linear equations. No *.sha File storing shadowing information for the PO. No *.snp Touchstone format S-parameter file. The n refers to the number of ports. This file is only generated when specifically requested. No *.sph Spherical wave expansion (SWE) as used by the reflector antenna code GRASP from TICRA. This file is only generated when specifically requested. No, unless used in equivalent source definition *.str File in which the solution vector of the linear equations are stored. This file can be re-used to compute more output parameters (such as far fields and nearfields) while not having to rerun the entire simulation. No *.vis When multiple reflections are used with the PO formulation FEKO determines which basis functions have line of sight visibility. Since this calculation may require significant run time, this information can be saved to a *.vis file for re-use. No *.x_t Parasolid model file. No
  18. In Suite 6.2 the voltage and current sources were extended to include a "port impedance" dialog box. This FAQ explains the function of this extension. The "port impedance" box on the voltage and current source is a post processing tool that allows for plotting the realised gain in POSTFEKO. "Realised gain" as selected in POSTFEKO includes mismatch losses whereas "Gain" does not. "Gain" in FEKO is strictly according to the IEEE definition - all losses are included except mismatch losses. When the user specifies an arbitrary impedance on the "port impedance" box, POSTFEKO will use this value when it displays the "realised gain" of the antenna. In addition, the ASCII OUT file will show, for models that contain only a single voltage or current source, the S11 for the antenna relative to this impedance. Note that this is purely a post-processing tool and plotting the source data in POSTFEKO will give the same answer for e.g. reflection coefficient regardless of the "port impedance" setting on the voltage/current sources. [A further post-processing tool is provided in POSTFEKO when plotting source data namely the "reference impedance" available on the result palette for source data. This allows plotting the reflection coefficient (or for the case of a single antenna, the S11 derived from the reflection coefficient) relative to an arbitrary impedance.] The "port impedance" setting on the voltage and current sources will not affect the "gain" or the source power or the radiated power. Note further that when multiport S-parameters are requested, a new S-parameter configuration is created in CADFEKO which does not allow for any voltage or current sources to be specified. FEKO will compute the S-parameters only and these parameters will be relative to the reference impedances specified in the S-parameter request in CADFEKO.
  19. What is the function of the "port impedance" for the voltage and current sources?
  20. "Missing" parallel licences
  21. A user has a parallel FEKO license for 96 processes. The user has 3 jobs running. The 1st job uses 16 processes, the 2nd also 16 processes and the 3rd job uses 32 processes. So there should be 32 processes left for calculation. But SECFEKO only shows 26 to be free. Where are the "missing" 6 licences? When a parallel job of FEKO is started, then the corresponding number of parallel licences are checked out (e.g. a job using 16 parallel processes will check out 16 parallel processes from the floating licence server). If this FEKO job terminates normally, these 16 parallel processes are then again returned normally. What might happen, however, is that a FEKO job terminates abnormally (e.g. a network communication failure) and then only some of the 16 processes terminate and return their licence, e.g. 10 are checked back in, but the remaining 6 processes then "hang around" and still use a licence. If these processes are killed the hard way (e.g kill -9 on Linux systems), then they will not return their parallel processes properly as they cannot execute any code if killed the hard way. These parallel instances will be checked-in automatically if for the given parallel licence there is no activity over a certain period (roughly 10 min). These can also be returned when the licence is checked-in manually using SECFEKO_GUI. However, one must realise that if the same licence is used by multiple parallel jobs, then one cannot check-in the licence, otherwise these other jobs will also terminate then with a licence error. There is presently no mechanism in the licencing mechanism to only manually return individual parallel instances of a parallel licence while this same parallel licence is still in use by other processes. Only the whole licence as such can be checked-in (or automatially, as soon as any parallel job using the same licence terminates, then after 10 min the licence will be checked in automatically).