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

Release Highlights: W1461 SystemVue Core Platform

Search Tools

  • New Workspace Search tool allows users to search for objects, parts, parameters, variables, and text in workspaces.
  • New Example Explorer is provided under Help menu to explore examples and search for a keyword among examples. You can right-click on any part on a schematic or in the Part Selector and select Find Examples... to open the Example Explorer with the model(s) of the part pre-populated in the search field.
  • Part Selector now supports searching models across all libraries. Just select <All> in Current Library and use Filter By to search a keyword.

Data Flow Analysis

  • Data Flow schematics can now annotate sample rate and characterization frequency for each node of the top-level design. For more details see Sample Rate and Characterization Frequency Annotation.
  • Data Flow simulation status dialog now shows the completion percentage status for each sink.
  • Data Flow Analysis dialog has been updated to clearly specify the Predefined Workspace Variables (Start_Time, Stop_Time, Sample_Rate, Num_Samples, Time_Spacing, Freq_Resolution) set by the Data Flow Analysis.

Algorithm Design Library

Matlab Script

  • postinfo function is provided to display a message as information in the Error window.
  • Full version of MATLAB R2018a is recommended. Some functionality may not be available under certain circumstances using MATLAB R2017b.


  • Added new Tools > Options > Font settings for Graphs, Schematics, Tables, and Datasets.
  • Support "Open Containing Folder" when you right-click the workspace in the workspace tree.
  • SystemVue workspace format has been updated to be version-control-friendly.
  • Multiselect on the workspace tree is now supported
  • Defaults sizes in the Tune window have been adjusted to make values easier to tune and read.


  • The minimum autoscale level for logarithmic units (dB, dBV, dBm, etc.) for the y-axes (Y-Axis and Right Y-Axis) was changed from -400 to -200. As a result, if you have a spectrum plot with content below -200 dBm (e.g. -300 dBm), autoscaling the graph will set the Y-axis lower limit to -200 and any content below it will not be visible in the graph. You can manually set the Y-Axis range by double-clicking on the graph, selecting the Y-Axis tab, clearing the Auto-Scale checkbox, and entering the desired values in the Min and Max fields. This is a global setting that can be changed by going to Tools > Options > Graph tab and updating the Autoscale Minimum for dB units value. This setting takes effect immediately (no need to exit SystemVue and restart).

Resolved Issues

  • Resolved installer issue to properly install .NET 4.6 when an earlier version of .NET 4 exists.
  • Resolved stability issue when invoking VSA 2018 Beta versions from SystemVue.
  • Fixed issues with setdisplayunit function; it will now work for power spectral density units dBm/Hz, dBm/MHz, dBW/Hz, and dBW/MHz.

Obsolete Features

  • GraphFigure function was removed; use graph_figure instead.
  • graph_get_beamwidth function was removed; use get_beamwidth function of graph_figure object instead.

Release Highlights: Add-on Libraries and Design Kits

W1906 5G Advanced Modem Library

Features Added

  • 3GPP NR features
    • Features conform to 3GPP V15.0.0 (2017-12)
    •  The key features of NR downlink baseband sources and receivers are:
      • Support 15kHz, 30kHz, 60kHz and 120kHz numerologies
      • Support 60kHz numerology with normal cyclic prefix and extended cyclic prefix
      • Support SSB with 15kHz, 30kHz and 120kHz
      • Support SSB with different periodicity and time offset
      • Support multiple ports for each BWP
      • Support channel coding, scrambling, layer mapping, precoding, modulation in PDSCH, PDCCH, and SSB
      • Support PDSCH with PDSCH DMRS transmission
      • Support PDCCH with PDCCH DMRS transmission
      • Support CORESET RB bitmap to define CORESET
      • Support multiple BWP and one SSB with the same numerology in NR_DL_numerology_Src
      • Support multiple BWP and one SSB with different numerologies in NR_DL_Source
      • Support timing and frequency synchronization with SSB and calculate the SSB power
      • Support PBCH demodulation
      • Support PDSCH demodulation without SSB and PDSCH overlap in the frequency domain
      • Support MMSE-2D channel estimation without SSB and PDSCH overlap in the frequency domain
      • Support LDPC/polar encoder and decoder
    • The key feature of 3GPP NR uplink source:
      • Support 15kHz, 30kHz, 60kHz and 120kHz numerologies

      • Support multiple BWP and multiple ports for each BWP

      • Support PUSCH with PUSCH DMRS transmission

      • Support channel coding, scrambling, layer mapping, precoding, modulation in PUSCH

    • 3GPP NR new examples
      • NR_DL_BeamAcquisition.wsv for simulation beam sweep and beam acquisition
      • NR_DL_Throughput.wsv for throughput and BER measurement of NR downlink in frequency range 1 and frequency range 2
      • NR_DL_Tx.wsv for spectrum, EVM, ACLR, CCDF and EIRP measurements of NR downlink both in the frequency range 1 and frequency range 2 (far field).
      • NR_DL_Tx_OTA for spectrum, EVM, ACLR, and EIRP measurements of NR downlink frequency range 2 in the near-field scenario
      • NR_LDPC_BLER_Measurement.wsv for BLER vs SNR measurements to evaluate the performance of LDPC decoding for 5G NR in AWGN channel
      • NR_UL_Tx.wsv for spectrum, EVM, ACLR and CCDF measurements for an NR uplink transmitter
      • NR_UL_Tx_OTA.wsv for spectrum, EIRP (CDF) and ACLR measurements for an NR uplink transmitter with antenna beam in frequency range 2.
      • NR_Vector_IODT.wsv for IODT test vectors can be generation especially for SSB

Features Changed

  • Updated BER measurement part in V5G_DL_Throughput.wsv to support coded BER measurement, rather than payloads BER measurement, according to customers' requirement
  • Updated relevant subnet "V5G_DL_Rcv" to support above feature and also updated affected workspace "V5G_DL_Tx.wsv"

W1720 Phased Array Beamforming Kit 

  • Rx-specific Phased Array Measurements are updated as the followings:


    GoverT(Theta,Phi) = Directivity(Theta,Phi) * AntennaEfficiency / SystemTemperature



    SystemTemperature = CircuitNoiseTemperature + ArraySkyTemperature


    where ArraySkyTemperature is defined as



  • The definition of NodeInfo_Signal_<index>_<AntennaArrayBlockName>_Output and NodeInfo_Signal_Power_<index>_<AntennaArrayBlockName>_Output in Phased Array Node Info Measurements was updated to include ONLY the desired signal at the main carrier frequency. Comparing to the previous release, the results are the same when Calculate Intermod and Harmonic Spectrum option is not turned on. When this option is turned on, the NodeInfo_Signal_* variables now do not include intermods falling into the main carrier frequency. To examine total power and intermod components at the main carrier frequency, use the spectrum plot based on Spectrum_Power_<index>_<AntennaArrayBlockName>_Output.

  • Phased Array Path Measurements now include TIMP, NDCP, and CNDR.
  • The default value of the Sensitivity parameter of PhaseShifter_M is set to 1 radian (180/pi degree). With this update, the Phase output of BeamformerWeights can connect to the Control input of PhaseShifter_M without an additional change in the Sensitivity parameter.
  • ArrayMeas_Directivity_Pattern, ArrayMeas_Polarization1_Pattern, ArrayMeas_Polarization2_Pattern, and Spectrum_EIRP_Pattern_<Frequency>Hz in Phased Array Measurements support direct 3D plotting by right clicking on the dataset variable > Add to Graph > New 3D Graph.

  • New OTA_TestTx and OTA_TestRx for modeling and simulating over the air (OTA) Tx and Rx test scenarios in radiated near field as well as far field for phased array systems.
  • The following new parameters are provided in BeamPatternBeamformerWeightsAntennaArrayTxAntennaArrayRx, and ArrayAnt models.
    • CenterArrayAtOrigin: an option to shift array center to the coordinate origin for Uniform Linear Array, Uniform Rectangular Array, Rectangular Array with Triangular Grid, and Uniform Hexagonal Array configurations.
    • SaveAntennaLocation: an option to save antenna element locations to the dataset.
    • ElementPatternFileScaleFactor: a scaling factor to scale element pattern file data to represent antenna gain. 

       In prior releases, data in element pattern file was normalized into directivity, which may cause accuracy issue in signal level or when multiple element pattern files are provided. In this release, ElementPatternFileScaleFactor parameter is provided, instead, to scale data in element pattern file to represent antenna gain in electric field domain.
  • The Display Array and Display Pattern buttons are provided to visualize array configuration and element pattern in the custom UI of the following phased array models: BeamPatternBeamformerWeightsAntennaArrayTxAntennaArrayRxOTA_TestTxOTA_TestRx, and ArrayAnt models.
  • Examples\Beamforming\OscillatorCorrelatedPhaseNoise.wsv: demonstrates how to use a small set of oscillators to drive all the mixers in a phased array system and the effect of oscillator correlated phase noise on system performance.

W1905 Radar Baseband Verification Library

Features Changed

  • Clutter Modeling Models & Examples
    • Ground clutter modeling example update
    • ClutterGen Doppler feature update
  • Ambiguity Function Examples
    • AF examples for advanced waveforms (Barker, Costas, NLFM)

W1908 Automotive Radar Baseband Verification Library

Features Added

  • MIMO Radar Architecture Examples
    • CDM-MIMO radar example with FMCW chirp waveform, and realizes Field of View and SNR enhancements
    • TDM-MIMO radar example with FMCW chirp waveform, and realizes Angle of Arrival accuracy enhancement
    • CDM-MIMO radar example with PRBS coded waveform
    • TDM-MIMO radar example with PRBS coded waveform
    • TDM-MIMO radar example with alternative FMCW waveform profiles
  • RF Impairment Modeling Examples
    • RF impairment modeling for AoA measurements with different transmitter architectures
    • Phase noise modeling for automotive radar applications
  • Environmental Modeling Examples
    • Ground clutter modeling example
    • Propagation loss modeling example (77GHz)
  • Advanced Signal Processing Examples
    • Compressed sensing signal processing example

Features Changed

  • Micro-Doppler user-defined low-speed target modeling (improved with more flexibility on user-defined target trajectories)
  • Flexible FMCW waveform generation examples

W1719 RF System Design Kit (Spectrasys)

Features Added

  • Added support for LO spur self mixing where LO spurs will mix with the main LO and appear at the non LO ports of a mixer. See LO Spur LO Mixing for additional information.

Resolved Issues

  • Fixed stability issue associated with noise simulation when using the modulated RF or RF link features.
  • Fixed a frequency comb issue where high carrier count intermod envelops were not created for amplifiers when located after a mixer. This could be seen as incorrect ACPR for stages following a mixer.

Behavioral Filter Improvements

  • Behavioral filter insertion loss has always been implemented using Q. Even though this is physically what happens in real filters this causes problem at the behavioral level as the bandwidth also shrinks. Bandwidth predistortion was not accounted for. The actual filter shape given the specifications was significantly different at higher insertion loss levels. Now insertion loss simply scales the specified response preserving the bandwidth specifications. This approach aligns more closely with the ADS implementation. For additional information on insertion loss, Q, and bandwidth predistortion see chapter 6, 'Finite-Q Elements and Predistortion' in the reference below.

    H. J. Blinchikoff and A. I. Zverev, Filtering in the Time and Frequency Domains, John Wiley and Sons, New York, 1976.

Sys-Parameter Improvements

  • Interpolation between Sys-Parameter data points is now linear in its native unit rather than linear in MKS. This means that in prior release parameters that have native units for dB, for example, would be converted to linear, like linear gain, then interpolated. Parameters with dB units, like gain and NF, interpolation will now be linear in dB. For example, if we have two data points of 10 dB and 20 dB the middle data point will now be 15 dB rather than the middle of 10 to 100, which is 55 in linear units or 17.4 dB. See Sys-Parameters and Frequency Dependency for additional information.

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).
  • 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.

Licensing and Installation


  • SystemVue   requires: a) the version 2017.01 of the EEsof EDA licensing software, b) a minimum code-word version 2017.01 or above, and c) the licensing server software, lmgrd and agileesofd, to be upgraded to at least the same versions as what is included in EEsof EDA Licensing software 2017.01.  SystemVue   will not start if any of these requirements are not met. Refer to the License Codeword Version Compatibility table.
  • In the EEsof EDA License Tools version 2017.01, 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 Setup instruction 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

  • 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 $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 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