Here’s the page we think you wanted. See search results instead:

 

  

Main Support:       Knowledge Center
Documentation:   EMPro English Doc   >  Unsupported Release   >  empro201501   >  EMPro 2015.01 Release Notes

This document contains references to Agilent Technologies. Agilent's former Test and Measurement business has become Keysight Technologies. For more information, go to www.keysight.com.


Skip to end of metadata
Go to start of metadata
You should be logged in the space to access EMPro 2015 documents and links to more detailed information. Please log in using your Knowledge Center login credentials.

EMPro 2015.01 Release Notes

EMPro 2015.01 provides several FEM and FDTD simulator enhancements such as faster meshing, improved loss tangent modeling, and coaxial port support in FDTD. It also provides new add-ons and improved EMI analysis.

What's New

EMPro 2015.01 release includes the following enhancements:

In addition to these enhancements, the following fixes from EMPro 2013.07 HF1 and HF2 are also included in this release:

  • Several robustness improvements in the ADS-EMPro interoperability use model.
  • Improved robustness for sheet ports in FDTD.
  • Improvements in the snapping behavior in the 3D modeler and several other EMPro platform related issue fixes.
  • Functional CATIA import on Windows 64.
  • Project/simulation loss issue fixed when using a simulation service on the local machine.
  • Several FEM meshing issues are addressed.
  • Improvement in the selection of point/direction/plane pickers, which allows you to select edges that are hidden behind another model.
  • Improvement in the XML output for E and H fields from the Advanced Visualization window.
  • Issue fixed when using an EMPro generated result as part of an ADS schematic co-simulation.
  • Issue fixed in the entry method of changing the priority of a material.
  • Issue fixed in the Material Editor window, if the conductivity field is non-editable, the field will be greyed out.

What's New in Licensing

  • EMPro requires: a) version 2014.07 of the EEsof EDA licensing software, b) version 3.2 codewords to run, and c) the licensing server software, lmgrd and agileesofd, to be upgraded to at least the same versions as what are included in EEsof EDA Licensing software 2014.07. EMPro will not start if any of these requirements is not met. Refer to the License Codeword Version Compatibility Table.
  • In the EEsof EDA License Tools version 2014.07, licensing vendor daemon ( agileesofd ) is upgraded to sync up with FlexNet FNP 11.11.1.2 version of FLEX license manager ( lmgrd ). EMPro installer for the Windows platform will automatically set up these two new license server daemons by default for the local node-locked license users; for Linux, you need to follow the Linux/Solaris Licensing Setup instruction to complete the licensing configuration process. For more details, refer to Licensing (For Administrators).

Known Issues and Solutions

Video Drivers Compatibility Issue with EMPro

Some video drivers, such as the Intel Graphics Accelerator card and Mobile Intel(R) 4 Series Express, have known compatibility issues with EMPro. It can result in unexpected fatal errors. From the Edit menu, change the general application preferences and change the value of Rendering Options Transparency Algorithm, such as Depth Peeling.
Workaround:

  • On Windows, create the EMPro shortcut on the desktop. Right-click the EMPro shortcut and select Properties. Access the Shortcut tab and append the existing path with the following text in the Targetfield:
    • For the Intel Graphics Accelerator card, append the existing path with: --driver=direct3d. Then, launch EMPro from the shortcut itself, that is, start EMPro in DirectX mode by using the following command:
      empro.exe --driver=direct3d
    • If Mobile Intel(R) 4 Series Express chipset is your preferred graphics driver, append the existing path with --driver=msw switch ("empro.exe --driver=msw"). Then, launch EMPro from the shortcut itself.
  • On Linux, start EMPro in X11 mode by using the following command:
    startempro --driver=x11

GPU Cards Support

  • EMPro supports only CUDA enabled GPU cards. See GPU Acceleration for FDTD Simulations  for a list of supported cards. GPU cards that do not support CUDA are no longer compatible with EMPro, because Acceleware v8 legacy code is not supported. However, EMPro still supports Acceleware v9 CUDA-based hardware acceleration.
  • EMPro uses CUDA version 4.0. Due to this change, the GPU driver must be updated to the latest version in order for EMPro to detect the GPUs. You can download the latest driver from http://www.nvidia.com/Download/Find.aspx. The download version should be at least 295.73 on Windows and 295.20 on Linux, released in February 2012 or later.

CPU Compatibility

  • When running EMPro 64-bit within VirtualBox, you may get a message that the CPU is not supported. Unless the CPU of the host machine is not supported, the missing instruction can be enabled by executing the following command, where <vmname> is replaced by the name of the virtual machine:
    VBoxManage setextradata <vmname> VBoxInternal/CPUM/CMPXCHG16B 1

Installation

  • If you have not specified a HOME directory specifically for EMPro, EMPro reuses the HOME directory settings of EMPro for licensing purposes. It might interfere with the EMPro licensing settings. To avoid this problem, set the environment variable HOME to point to your preferred EMPro home directory.
  • For remote login on Linux, set the environment variable HOOPS_PICTURE to X11/myhostname.com:0.0.
  • During the Linux bit installation, if an "insert media disk" message pops up, it indicates that the Linux web download is incomplete due to a cache problem with the browser. To download the Linux bit, rename the Linux download file before saving the file on the disk drive.

Licensing

  • Unable to install Flex-10 driver if Flex-9 dongle is already plugged into a machine.
    Workaround: Before installing a Flex-10 driver for the first time, unplug the Flex-9 dongle.
  • There is a known Flexera FNP issue, whereby mixing node-locked codewords and floating codewords in one license file can result in: a) Remote simulations not working or b) A second local simulation not working in case the license is node-locked and also has incorrect version.
    Workaround: It is strongly recommended that you do not mix node-locked codewords and floating codewords in one license file nor in any configuration that ends up with node-locked codewords and floating codewords both available on the same server. In other words, put the node-locked license and the floating license on different servers, and point to the respective one based on what you need to run.
    Additionally, we also recommend you to remove expired codewords, to separate out the new and the old versions of codewords into different files and different servers, and to point to the respective one based on what you need to run.
  • Not specifying the TCP/IP port for the license server during license setup may lead to unexpected behavior and/or license checkout failure on the Windows platform. We strongly recommend you to always explicitly specify the TCP/IP port associated with each license server.
  • A node-locked and floating bundle operating on Linux cannot be shared between products using EDA License Tools version older than 2014.01 when run at the same time.
  • License Setup Wizard does not remove any previous user-configured FLEX Windows License Service manually set up by a user using FlexNet's lmtools.
    Workaround: You must remove the previous user-configured Windows License Service via lmtools.
    • Run the lmtools.exe from C:\Program Files\Agilent\EEsof_License_Tools\bin to invoke the lmtools utility. The lmtools utility window is displayed.

      If you have installed an EEsof product released before 1st August, 2014 on your system prior to installing an EEsof product released after 1st August, 2014 then the default EEsof Licensing tools path will remain C:\Program Files\Agilent\EEsof_License_Tools. On the systems that only have EEsof products released after 1st August, 2014 installed then the default EEsof Licensing tools path will be C:\Program Files\Keysight\EEsof_License_Tools.
    • In the Service/License File tab, check the Configuration using Services option. All user-configured FLEX Windows License Services will be listed.
    • Select the service you wish to remove.
    • Select the Config Services tab and click the Remove Service button to remove the service.
      To ensure that the license service or lmgrd is running, click View Log. A log window appears that confirms whether agileesofd and lmgrd are up and running.
  • While running multiple versions of prior EMPro releases together, set PRODUCT_NAME_MAXIMUM_BUNDLE_USAGE=ON in your environment so that all of them will use the same method to check out licenses. Otherwise, you might receive an error message, "Licensed number of users already reached".
  • On some Windows 7 machines, when more than one definition of an Ethernet adapter exists (duplicates), license checkouts may appear to hang up.
    Workaround: Disable the duplicate network card definitions in your network settings: Control Panel > Network and Internet > Network Connections. This issue has been acknowledged by Flexera and they have created a bug report (SIOC-000103097).
  • For LSF style distributed simulations, ensure that the PATH on the client computer points to the $HPEESOF_DIR/EEsof_License_Tools/${architecture} directory that corresponds to the EEsof release being used. This needs to be done in order to ensure that the proper version of the Flexera utilities (like lmutil ) gets picked up in the path before any older in-compatible versions (that may also be installed on a users’ system.)
  • License Setup Wizard ( aglmwizard.exe ), which is used to set up and record the license path would not work if you already have an environment variable set for PRODUCT_NAME_LICENSE_FILE.
    Workaround: You can use PRODUCT_NAME_LICENSE_FILE variable to point to license file or refer to Licensing (For Administrators).
  • The License Setup Wizard will exit or not properly configure a license server, if the server has all of its licenses currently in use.
    Workaround: Wait for a license on the server to become available as you normally would before launching the product.
  • Unable to set license in case unicode characters are used either in path or license file name because the Flex License Service does not support these characters.
  • The Product Selector tool will be unable to display the license server status properly when connected to older license server.
    Workaround: Upgrade your license server to the latest version.
  • The vendor daemon agileesofd sometimes crashes when running on remote Windows 8 machine. This crash occurs in the License Manager and Product Selector dialog boxes. EMPro can still run. Keysight is working with Flexera to resolve this issue.

    Workaround: Use a different operating system for remote license server. If you must use Windows 8, the vendor daemon may crash when viewing licenses with the License Manager or when requesting license availability from the Product Selector dialog box. The license server, lmgrd , automatically restarts the vendor daemon and license checkout can proceed normally.

Documentation Known Issues

  • To access Python Scripting API reference, select the Unfiltered option from the Filtered by drop-down list. Then, select the Python Scripting option from the left pane.
  • EMPro online help is not supported on the Google Chrome browser.
    Workaround: Use Internet Explorer or Firefox to view EMPro documentation.
  • EMPro QT search does not support [] or {} or any other text using these combinations.
  • Mozilla Firefox version 3.0.5 crashes on RHEL 5 machine while accessing protected EMPro online documentation from the Qt Help window.
  • In case EMPro help does not show any content, throws an error, or does not display any search results, you can use the following workaround:
    Workaround: Close QT Help and delete contents of the following directory.
    • On Windows 7/8: C:\Users\<Windows_Login_ID>\AppData\Local\Keysight\Help
    • On Linux: $HOME/.local/share/data/Keysight/Help

Distributed Simulations

  • Distributed FEM and FDTD simulations on one machine (local or via a Simulation Service) is not recommended except on high-end compute servers. To maximize performance, it is advised to use proper settings for the number of threads and number of parallel processes started via distributed, such that the product of these two numbers does not exceed the number of physical cores available on the compute server.
  • Distributed FEM simulations with an adaptive frequency sweep specification takes more frequency points compared to when the same adaptive frequency sweep is started in a non-distributed mode. This can be up to a factor of two. For performance reasons, it is not recommended to perform distributed FEM simulations with an adaptive frequency sweep on a single machine.
  • While distributing remote FDTD simulations, start the simulation service window from the Linux terminal instead of starting the service from the Tools menu.
  • Remote and distributed simulations are not supported on legacy format projects.
  • Distributed simulations on PBS and Sungrid clusters are not supported for library names with spaces.

Miscellaneous

  • A warning message may appear when opening malformed project models. This warning message is to recover the broken models which helps to repair the malformed objects in EMPro. It is recommended to use this option and let EMPro recover such models.
  • When simulating frequencies below the cutoff frequency of the modes of a waveguide excitation, the accuracy of the multithreaded iterative solver may degrade.
  • If meshing issues are encountered, see Troubleshooting Mesh Failures .
  • Though the Example projects are marked as read-only, you can run simulations on these projects if you use the Simple Parameter Sweep add-on or if you perform 2D waveguide port simulations. You will not be able to delete the results from these simulations from the user interface. You can manually remove them from the command line if needed. It is advised to save the Example projects in different location before doing these simulations.
  • The display of the field plots are not scaled when changing the z-scale in the EMPro Geometry window

Please help us improve
Please help us improve
Was this topic helpful? Yes No