Main Support:       Knowledge Center
Documentation:   SystemVue English Doc   >  Unsupported Releases   >  SystemVue 2018 Update 1.0   >  SystemVue 2018Update1 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

Skip to end of metadata
Go to start of metadata

SystemVue 2018 Update 1.0 Release Notes

This page provides a summary of new features, enhancements, and resolved issues in SystemVue.

What's New

Here are the key features and capabilities in SystemVue.

W1461 SystemVue Core Platform

Algorithm Design Library

  • Added an option to the BeamPattern model to normalize the beam patterns that it generates.

  • Added an option to the BeamPatternOTA_TestTx, and OTA_TestRx models to specify the polarization in terms of its RHC and LHC components, or using the ellipse axial ratio and tilt.

  • Improved the readability of the HFSS antenna pattern file format 3/4 and CST format.

  • AtoD and AtoD_M models

    • Replaced the SNR_Model option Quantization_and_Thermal_Noise with Quantization_Jitter_and_Thermal_Noise to simultaneously model all three contributors to SNR.

    • Improved the model generating harmonics when DistortionModel = SNR and HarmonicsConversionType = Downsampled, and DownsamplePhase is any value other than DownsampleFactor  – 1.

    • Improved the model generating the proper amount of jitter noise in the 1st or higher Nyquist zones.


  • 3D Scatter plot symbol size is now fixed (at graph creation) regardless of the minimum distance between the points to be drawn (You can manually set the size by right-clicking on the graph, selecting Properties, going to the Traces section, and changing the symbol size).

  • A pair of 3D graphs can be locked together so that when one's camera view is changed (for example, rotated, changed between Isometric/Top/Front/Side, zoomed) the other one's view is kept in sync. To lock two 3D graphs, right-click on one of them, select Properties, go to the Plot section, and select the 3D graph you want to sync within the Sync Camera With drop-down menu.

Matlab Script

  • Added the MATLAB script function to sync views of two 3D graphs. For example, myGraph.syncView('myOtherGraphName').
  • Added support for double nested sweeps to the sweepplot function.


  • Example Explorer Updates
    • The Open Example button on the Startup screen and the Open Example menu option in the Help menu were replaced by Example Explorer.
    • Added support for the searching multiple keywords combined with and.
    • Added a button to collapse/expand the Example Explorer tree.

  • IntelliPrompt
    • When editing an equation page as soon as you type the opening parenthesis ‘(‘ after the using or getvariable function, you will be presented with a list of all the existing workspace datasets to select from. In addition, for getvariable, once the dataset is selected and you type the comma ‘,’ character, you will be presented with a list of all the available variables in the dataset to select from. 

      This feature is not supported in Command Prompt.
    • You can now type DatasetName.VariableName (with completion support after typing the dot ‘.’ character) and replace with call to getvariable.
  • Workspace
    • The items in the Workspace tree can now show the size of the data associated with them. FoldersDesigns, and Workspace will show the amount of memory required to hold the associated data. The size of the data in a Workspace file will be similar (up to twice as big) but will vary based on the Compact File Format setting in Tools Options. To enable the data size display, click the Options toolbar button at the top of the Workspace tree and left click the Show Data Sizes option.

Obsolete Features

  • Removed obsolete functionality to print or export screen captures using shortcut keys. These commands failed on multi-monitor setups. Use an app or the PrintScreen key (which copies the screen to the clipboard) to achieve the same result.

W1719 RF System Design Kit (Spectrasys)

  • Fixed issue with incorrect phase noise power.
  • Fixed issue with not being able to populate Data in Mixer Table IF=>RF tab.
  •  Improved Sources UI in the Spectrasys Properties window.

W1720 Phased Array Beamforming Kit 

  • Added an option to the ArrayAnt model to specify polarization in terms of its RHC and LHC components, or using ellipse axial ratio and tilt.

  • Improved the readability of the HFSS antenna pattern file format 3/4 and CST format for the ArrayAnt model.

  • Polarization mismatch is now included in the ArrayMeas_GoverTAtThetaPhi and ArrayMeas_TotalGainAtThetaPhi measurements. (see Phased Array Measurements)

  • Added Active Impedance measurement for Tx mode when Active Loading is set to S-Parameter File or S-Parameter Dataset. (see Phased Array Part Info)

  • Added non-linearity to the ArrayAttn model.

  • Added option in the Phased Array analysis dialog Measurements tab, to normalize (or not) the directivity and polarization patterns.

 W1906 5G Advanced Modem Library

  • Conform to 3GPP v15.3.0 (2018-09)
  • New Pioneer Solutions are provided, which can be easily scaled:
    • NR_DL_Throughput_PolarizedSystem.wsv includes the frequently used scenarios in the polarized system which focuses on the FR2 systems combined with beamforming.
    • NR_DL_Throughput.wsv is enhanced to include the FR2 solutions combined with beamforming.
    • NR_UL_Throughput.wsv is added for the reference which is easy to scale.
    • Other 5G NR examples are also enhanced to cover more test requirements.
  • Easy-to-use GUIs are added for frequently used models, including NR_DL_SourceNR_UL_SourceNR_DL_Numerology_Rcv, and NR_UL_Numerology_Rcv.
  • Resource allocation flexibility is supported in any downlink and uplink:
    • FRC (Fixed Reference Channel) in TS38.101-1 can be configured easily.
    • OCNG (OFDMA Channel Noise Generator) can be configured easily.
    • The transmission of PDSCH, PDCCH, PUSCH, PUCCH can be scheduled flexibly in time slots.
    • SSB transmission can be flexibly activated or deactivated for a specific candidate.
  • Three receiving options in the 5G library are supported:
    • NR_DL_Numerology_Rcv and NR_UL_Numerology_Rcv are original 5G library reference receiver for downlink and uplink respectively which can work well in fading channels.
    • NR_DL_EVM and NR_UL_EVM are added for downlink and uplink respectively which works well in the AWGN channel and show exactly the same results as Keysight instruments. 

      PDCCH and PUCCH receiving combined with extended CP are not supported in the current release. These two EVM models may not work well in fading channel, so use NR_DL_Numerology_Rcv and NR_UL_Numerology_Rcv instead if the fading channel is assumed.
    • VSA_89600B_Sink which needs a separate license also only works well in AWGN and show exactly the same results as Keysight instruments. Refer to NR_DL_Numerology_Rcv and NR_UL_Numerology_Rcv if the fading channel is assumed.
  • 3D MIMO channel (MIMO_3DChannel) has been updated to support 38.901 V15.0.0 (2018-06) with the following updates:
    • Updated 3D-InH channel model in TR38.901 and extended the largest distance of d3D from 100m to 150m for the LOS/NLOS state of 3D-InH in Table 7.4.1-1. (See 3GPP doc R1-1717900)
    • Improved the inconsistency between RMa and UMa/UMi in how the LOS probability is determined for indoor users. (See 3GPP doc R1-1705803)
    • Updated Table 7.5-6 for RMa (up to 7GHz) with a new column for O2I. (See 3GPP doc R1-1706381)
  • Other Performance Improvement
    • LDPC decoder is enhanced to decrease the memory consumption and speed up the simulation.
    • PTRS transmission and receiving are supported both in downlink and uplink to conquer annoying phase noise in high-frequency band transmission. 

      The uplink receiver will ignore PTRS when TransformPrecoding is enabled.
    • Spectrum shaping is added in both NR_DL_Source and NR_UL_Source for downlink signals and uplink signals respectively to suppress the out-of-band emission.
  • Other Usability Improvements
    • Support bandwidth and MCS configuration conforming to 3GPP spec.
    • VSA setup file generation is supported by NR_DL_Source and NR_UL_Source for downlink signals and uplink signals respectively.
    • Updated the inconsistent definitions of Numerology and SSB_Numerology.
  • Other Notes
    • PUCCH format 0 and format 2 waveforms can be generated by NR_UL_Source and they can be demodulated by NR_UL_EVM and VSA_89600B_Sink, but not NR_UL_Numerology_Rcv.
    • PDCCH waveform can be generated by NR_DL_Source and they can be demodulated by NR_DL_EVM and VSA_89600B_Sink, but not NR_DL_Numerology_Rcv.
  • Unsupported Features
    • For both downlink and uplink
      • Carrier resource allcoation by Grid Resource
    • For downlink
      • CSI-RS support
      • 2 codewords transmission
      • VRB mapping
      • 240kHz SSB
    • For uplink
      • PUSCH frequency hopping
      • PUCCH format 1, 3 and 4
      • SRS support

W1905 Radar Baseband Verification Library

  • The RADAR_PlotsCentroid model: Enabled preliminary target grouping (fake target elimination) after CFAR.
  • The Antenna_Tx2 model: Enhanced antenna pattern calculation capability. 
  • The ClutterGen model: Fixed a defect for K-distribution.
  • The LocInAntennaFrame model: Fixed a defect for Elevation Angle in the SimpXYZ mode.

W1908 Automotive Radar Baseband Verification Library

  • AutomotiveRadar_PlotsCentroid model
    • Enabled preliminary target grouping (fake target elimination) after CFAR.
  • VRU (Vulnerable Road User) modeling example
    • Detailed measured RCS data for Bicyclist and Pedestrian with modeling methods.
    • RCS data extracted from materials and selection strategy open to the user. 
  • Vehicle + VRU modeling example
    • 4 typical measurement scenarios from 3 world-class research institutes.
    • Detailed measured RCS data Vehicle (various types, sedans, trucks, vans etc.) + VRU (bicyclist, motorist, pedestrian).
    • RCS data extracted from materials and selection strategy open to the user. 
  • Ground clutter related examples
    • Ground clutter + road guardrail modeling example.
    • Ground clutter + manhole cover modeling example.
  •  Radar system design examples
    • SISO example with system-level parameter tuning panel.
    • TDM-MIMO example with system-level parameter tuning panel. 

Known Issues

  • If you encounter an error indicating "MATLAB Script engine failed to run" during startup, make sure the installed version of Microsoft Visual C++ 2005 Redistributable (x64) is 8.0.61000 or higher. You can download and install the latest Microsoft Visual C++ 2005 Redistributable (x64) from Microsoft Visual C++ 2005 Redistributable Package (x64).
  • Some issues with plot legends not always being created properly have been observed with MATLAB R2017b under some rare conditions so MATLAB R2018a is recommended when using MATLAB Script in Retail MATLAB mode.
  • MATLAB R2018a is unsupported in SystemVue if the current Windows user name contains non-ASCII characters. Use an earlier version of MATLAB, or an ASCII-only user name. Contact support for other possible workarounds.
  • FlexDCA_Sink does not work with FlexDCA version A.05.71.24. You can use version A.05.63 or prior, or use the version newer than A.05.71.24.
  • Some dialogs may not render properly on Windows 7 machines using 150% scaling.
  • If you see error like "Undefined function 'log2' for input arguments of type int32" when running a 5G NR workspace, you need to replace the error model with model from part library selector.

Licensing and Installation


  • SystemVue requires: a) the version 2018.04 of the EEsof EDA licensing software, b) a minimum code-word version 2018.04 or above, 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 2018.04. SystemVue 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 2018.04, licensing vendor daemon (agileesofd) is integrated with FlexNet FNP version (Windows) and FlexNet FNP version (Linux) of FlexNet license manager daemon (lmgrd). For the Windows platform, SystemVue installer will automatically set up these two new license server daemons by default for the local node-locked license users; for the Linux platform, you need to follow the Linux/Solaris Licensing Setupinstruction to complete the licensing configuration process. For more details, refer to Licensing (For Administrators).

  • SystemVue does not automatically release licenses after checking out. From SystemVue 2013.08 onwards, Action > Release All Simulation Licenses option is available to manually release all checked out simulation licenses.

Known Issues

  • License Setup wizard may not be able to start license server with many license files. During setup, it may lead to a situation where a command prompt window appears/disappears incessantly. This is due to the fact that License Setup wizard is not able to start lmgrd with a long command line and may get stuck in a loop.

    1. It is recommended to combine all license code words tied to same MAC ID into single license file to avoid setting large number of license files.
    2. Try to use a shorter path to place license files.
    3. If #1 and/or #2 does not help, start the license server (lmgrd.exe) from the command line (e.g. lmgrd.exe -c <lic-file-path> -l <license_server_log.txt>) and then set <PRODUCT>_LICENSE_FILE=<PORT-NUMBER>@localhost for product you want to use on same PC.
  • Dongle drivers for Flex-10 dongles on Linux are release specific. Installing the latest dongle drivers on Linux will function properly only for the most recent EEsof releases.
    : Install and use dongle drivers as needed.  If you need to run the most recent EEsof releases, use the latest  Flex-10 dongle driver. If you need to use older releases, uninstall the latest dongle driver and re-install the older dongle driver

  • FLO and EEsof License setup are writing server logs at different locations. However, the EEsof server log file location is updated in the License Manager > Environment tab.
  • When multiple same-named INCREMENT lines of different version exist on the license server, few advanced FlexNet options to reserve/limit licenses may not work properly. 
  • Product Selector “Check Availability“ generates incorrect results (which leads to license failure) for older releases when multiple date base versions of like-named bundles exist in the license pool.
  • In Linux, Product Selector OK and Cancel Buttons locations are reserved.
  • Starting from FlexNet Publisher 2015 (also known as version 11.13.1), the adoption of the best practice of the least-privilege security therein results in the License Server related Windows Service to run with the LocalService Account privilege (instead of the LocalSystem privilege as before.)  Running with the LocalService Account privilege, an executable can no longer access any files located in the per-user specific type of folders.  As a result, any license file placed in those folders can no longer be accessed by the License Server when the License Server is automatically started via the Windows Service upon each PC reboot. For the local node-locked license, this would not result in any disruption to the usage of EEsof applications; however, for the license installed on a network PC that is accessed by multiple client PCs, this may cause EEsof applications not to start after the network PC reboots
    Workaround: Store your license files in the Windows folders that are accessible by the LocalService Account privilege.  For example, C:\ProgramData or C:\users\public are both qualified choices.  In general, any folder that has the "Users" group listed in its Properties > Security page and this "Users" group has the read permission enabled should work. 
  • Using the default port to connect to a license server may cause a delay when checking out licenses. If no port is given in the license file, Flexera scans ports 27000 to 27009 to find the port. Starting from FlexNet Publisher 2015 (aka version 11.13.1), the default timeout for the response from each port increased from .1 seconds to 3 seconds.

    To avoid the delay, KSM now issues licenses with port 27009 instead of leaving this blank. The EEsof License Setup Wizard (from Licensing 2017.01 onwards) handles some common situations such as: where it detects license file(s) without port, when users get a new license file with port 27009, or when all license files for a vendor daemon does not have same port. 

    You will not be able to start the license server if all license files for a vendor daemon on a server does not have same port.

    Users who manually setup a license server or using EEsof License Setup Wizard with older licensing bits may need to manually edit license files to comply with the following rules:

    1. All license files for a vendor daemon on a server must use the same port (or all be blank). 

    2. Using the default port (blank) is allowed but may result in longer checkout times. 

    3. If setting up a network server, select an unused port that is not blocked by a firewall.

    Workaround: If the user cannot change the port, or wants to use the default Flexera ports, the environment variable FLEXLM_TIMEOUT can be set to .2 seconds (200000), to minimize the performance degradation. However, if the network latency is an issue in your environment, you may need to fine-tune this setting to minimize the general performance degradation while still accommodating the network latency.

  • Installation of EESof EDA tools (such as, SystemVue 2016.08, Genesys 2017.XX, or ADS 2017.XX) may hang at 4% (percentage vary based on the products) for few hours or even more on some specific machines.
    • Disable Firewall setting in Anti-Virus Software installed on the PC.
    • Download and unzip process explorer from the below link and then invoke procexp.exe.
      Right click on the wusa.exe process under <Product installer exe> and select KillProcess. Now it will continue the product installation.
  • After installing EESof EDA tools (such as, SystemVue 2016.08, Genesys 2017.XX, or ADS 2017.XX) successfully and try to invoke the software or License wizard, you may encounter “api-ms-win-crt-runtime-l1-1-0.dll” missing error.
    Workaround: Install the Update for Universal C Runtime in Windows .  On Windows 64-bit system systems, the file to install is x64 version of the Microsoft hotfix KB2999226. A copy of the Windows6.1-KB2999226-x64.msu Microsoft 64-bit hotfix installer can be found under the C:\Program Files\Keysight\EEsof_License_Tools\bin directory.  The Microsoft hotfix KB2999226 can be found under the Update for Universal C Runtime in Windows  page at as well.
  • On a newly formatted RHEL system, the EEsof Licensing tools may fail to boot. This is because the FlexNet Publisher 2015 requires a certain rpm
    Workaround: Under the EEsof product installation directory, there exists a utility script named "" under the bin directory. Run this script to find out whether any rpm is missing; run this script with a "-y" command-line option to also have all the missing rpms automatically installed if you have the sudo or root privilege.
  • License server may stop recognizing Flex-10 dongle on some systems within a few hours after starting 
    Workaround: If you experience this problem, install the latest WibuKey drivers from Wibu Systems.
  • 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 FlexNet Publisher 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.
  • If a user simultaneously runs two instances of a product and has mixed different versions of the same codeword on one license server, extra licenses may be pulled and result in unexpected “Licensed number of users already reached for this feature” errors.
    Workaround: We recommend you 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 SystemVue releases together, set SystemVue_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 HPEESOFD IREEsofL icenseT ools   {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 SystemVue_LICENSE_FILE.
    Workaround: You can use SystemVue_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.

  • EEsof Licensing Tools installer can hang on systems with McAfee LiveSafe installed and running the default firewall settings.
    Workaround:  Prior to installing EEsof Licensing Tools, temporarily turn off the McAfee LiveSafe firewall.

  • Licensing setup steps on systems with McAfee LiveSafe installed can fail.
    Workaround:  Under the McAfee LiveSafe firewall settings, under Port and Settings, allow the use of port 27001 for lmgrd.exe under the EEsof Licensing Tools installation bin directory.  Under Internet Connections for Programs , enable lmgrd.exe, aglmmgr.exe and aglmwizard.exe for all devices and turn off monitoring.

  • On Windows, EEsof product releases prior to 2014 can have boot time issues with licensing if an newer EEsof product is installed prior to installing the older product. For example, if a users installs Advanced Design System 2017 and then installs Advanced Design systems 2014.01, the user can have boot time errors with ADS 2014.01.
    Workaround:  For Advanced Design System users,  set a system environmental variable named ADS_LICENSE_FILE under the Control Panel/ System, and Security / System / Advanced system settings and under the "environmental variables".  Add an System variable named ADS_LICENESE_FILE and the value will be the path to your local license file or the port@host setting for your site.

Fixed Issues

  • The issue related to the vendor daemon agileesofd could sometimes crash while the License Manager and the Product Selector was running on a remote Windows 8 machine has now been fixed with the newer FlexNET publisher 2015 (also known as version 11.13.1) that is automatically installed by the SystemVue installer. 
Please help us improve
Please help us improve
Was this topic helpful? Yes No