ansys maxwell

Maxwell v16.0 ============================================= Supported Platforms =================== Supported Operating Systems (Windows versions): 32-bit Installation: -------------------- - Windows XP 32-bit Service Pack 2 - Windows 7 Business Editions 32-bit, Service Pack 1 64-bit Installation: -------------------- - Windows XP 64-bit Service Pack 2 - Windows HPC Server 2008 R2 - Windows 7 Business Editions 64-bit, Service Pack 1 Requirements ============ 32-Bit System Requirements Minimum System Requirements: Processor: All fully compatible 686 (or later) instruction set processors, 500 MHz Hard Drive Space (for Maxwell software): 200 MB RAM: 512 MB Recommended Minimum Configuration (for Optimal Performance): Processor: All fully compatible 786 (or later) instruction set processors, 1 GHz Video card: 128-bit SVGA or PCI Express video card Hard Drive Space (for Maxwell software and temporary files): 500 MB RAM: 2 GB 64-bit System Requirements Minimum System Requirements: Supported processors: AMD Athlon 64, AMD Opteron, Intel Xeon with Intel EM64T support, Intel Pentium 4 with Intel EM64T support Hard Drive Space (for Maxwell software): 200 MB RAM: 2 GB Recommended Minimum Configuration (for Optimal Performance): Supported processors: AMD Athlon 64, AMD Opteron, Intel Xeon with Intel EM64T support, Intel Pentium 4 with Intel EM64T support Video card: 128-bit SVGA or PCI Express video card Hard Drive Space (for Maxwell software and temporary files): 700 MB RAM: 8 GB Technical and Installation Support ================================== For technical support, please contact the Ansoft support office nearest to your location. The Ansoft support offices can be found by accessing http://www.ansoft.com/contact.cfm Alternately log on to the ANSYS Customer Portal to download software, find knowledge resources, examples, and best practices. http://www.ansys.com/customerportal Please provide the following information when you contact us: - Your name and affiliation - Version number of Maxwell - The type of hardware and operating system you are using - A description of what happened and what you were doing when the problem occurred as well as the exact wording of any messages that appeared on the screen Installation Changes for Maxwell 16.0 ===================================== The default installation directory on Windows has changed from "\Program Files\Ansoft\" to "\Program Files\AnsysEM\", and the start menu folder will be named "ANSYS Electromagnetics". If you have installed a build of Maxwell v16 dated earlier than the Preview 2 release, you will be forced to uninstall that build before installing newer builds of Maxwell v16. New Licenses in Maxwell 15.0.1 and 16.0 ======================================= Beginning in Maxwell v15.0.1 there are new license features (named "m2dfs_qs_solve" and "m3dfs_qs_solve") required to solve Maxwell2D and Maxwell3D designs. These features are added to provide support for a new, lower-priced Quasi-Static Maxwell license package that can solve static and eddy current solutions, but not transient. Because of this change all users will need to updated licenses if they received their Maxwell licenses with the original v15.0 release (or earlier). Other Licensing Changes in Maxwell v16.0: ========================================= The license time out behavior has changed. Formerly desktop licenses time out and checked in after 2 hours of inactivity (by default). Now, the default behavior will be not to time out, but customers can set the FLEXlm time out setting and it will be honored correctly. On 64-bit versions of Windows, support has been added for node-locked licenses locked to USB dongles. Other significant changes in Maxwell 16.0 ========================================= The ACIS version has been updated to ACIS 22.2 (beginning with Preview 2) Known defects in Maxwell 16.0 ============================= DE38576 – When mapping losses from Maxwell2D RZ designs into Fluent, in at least 1 case the mapped loss values from Maxwell appear to be incorrect in Fluent (negative loss values near the Z-axis). DE44353 & DE46894 - In Maxwell2D when using the new “Clone Mesh” feature, there have been a few cases in which the clone mesh operation has produced a solver2d error when applied. In one case, the failure happened when using the TAU mesher for the initial mesh method, but did not happen if the initial mesh method was set to ‘Ansoft Classic Mesh’ (the default initial mesh method). DE42281 – In Maxwell3D, when using true surface objects, the mesh refinement does not always correctly pull new mesh points to the correct surface. DE44501 – In Maxwell3D, mesh quality sometimes gets worse after mesh refinement even if the initial mesh quality was good. In a few cases the mesh quality can became poor enough that the solver will exit with the message: "Mesh quality of some elements is not accepted by solver." DE45563 - When working under WorkBench with a Maxwell design linked to Mechanical system, if you delete the Maxwell design without first removing the links the WorkBench project can become corrupted. The Maxwell design can be deleted correctly if the links are removed first. DE47191 – In RMxprt when using the generic rotating machine model and the Position Control box is not checked in the Stator settings, the solver will do an analysis for a synchronous machine. However, when generating reports or quick reports the interface will incorrectly list “Speed” as a domain, but will not list the domains that it should list (Angle and ElectricalDegree). This allows you to create plots of quantities vs. RSpeed that make no sense for a synchronous machine. You can see the correct plots by using the “Curves” tab in the solution dialog. DE47986 - In Maxwell3D magnetostatic and eddy current solutions, if you have a conduction path that branches and you have multiple internal terminals, you should only have to specify the current in N-1 branches (with the software determining the current in the 3rd branch). In Maxwell v15 and v16.0, the current distribution is not always correct under these circumstances. In some cases, you can workaround by explicitly specifying the current in the remaining branch.