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

 

  

Main Support:       Knowledge Center
Documentation:   SystemVue English Doc   >  sv201308sp1   >  SystemVue 2013_08 SP1 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

SystemVue 2013.08 SP1 Release Notes

You should be logged in the space to access SystemVue 2013.08 SP1 documents and links to more detailed information. Please login using your Knowledge Center login credentials.

SystemVue Release Notes

 

Release Highlights: 2013.08 Service Pack 1

  • The following wireless libraries now support SystemVue Engine and Distributed Simulation : CDMA, CDMA2K, GSM, 3G W-CDMA, HSDPA, HSUPA, DigMod, DVB-x2, ISDBT, GNSS, WiMAX, DPD, WPAN, ZigBee, WLAN 802.11a, WLAN 802.11b, WLAN 802.11n and WLAN 802.11ad.
  • If you plan to use custom libraries in SystemVue Engine , the autoload directory is in $HOME/SystemVue/2013.08SP1/Autoload for SystemVueEngine in 201308SP1 release.
  • FastCircuitEnvelopeObsolete and GoldenGateCosim models have been updated to support GoldenGate 4.8 and later releases. The updated [FastCircuitEnvelopeObsolete| http://edadocs.software.keysight.com/display/sv201308sp1/FastCircuitEnvelopeObsolete model does not support FCE files extracted from GoldenGate 4.7.x and earlier releases. Similarly, the updated GoldenGateCosim model does not support GoldenGate 4.7.x and earlier releases.
  • Updates made to SVEClient API.
  • IBIS-AMI Model Generation
    • Update AMI file generation to conform with the IBIS 5.1 standard: Format Value and Default are mutually exclusive and cannot be shown together.
    • Update receiver .ibs template to have Model_type Input to conform with the IBIS 5.1 standard.
    • Cosmetic update to the Ramp specification in the transmitter .ibs template.
  • Examples
    • A new example, located in Examples\RF Architecture Design\RF Design Kit\Spectrasys\Scripting, provides a spreadsheet to Spectrasys conversion tool (Excel_to_RF_Sys.exe) along with the associated Spectrasys template workspace (Spreadsheet_Template.wsv) and the C# source code that demonstrate how to convert a cascaded analysis in a spreadsheet to a Spectrasys design.
    • Added RADAR and DigitalMod VTB workspaces in Examples\VTB.
    • Updates made to Examples\VTB workspaces, including proper SVE_Link BlockSize, SVE_Link port names, adding pass/fail results, proper graph units, deterministic BER simulation time, LTE-A design parameter update, and so on.
  • W1905 RADAR Library Enhancements
    • New RADAR_MNDetector model and RADAR_BinaryModel are used to simulate M-outof-N detector
    • New RADAR_PdMeasure model is used to improve the Pd measurement. It is recommended that use this model to measure the Pd.
    • New RADAR_MatchedFilter model is used to simulate the matched filter which can maximize the SNR.
    • New RADAR_DBF model is used to simulate the beamforming.
    • New FMCW_DSP example which can be used to measure the range and velocity of target can be found in <SystemVue_Install_Directory>/Examples/Radar/System.
    • New MatchedFilter example can be founded in <SystemVue_Install_Directory>/Examples/Radar/Basic.
    • New DBF_Basic example can be founded in <SystemVue_Install_Directory>/Examples/Radar/DAR.
    • New Radar templates for common Radar verification scenarios can be found in <SystemVue_Install_Directory>/Examples/Radar/GeneralFramework.
  • WLAN 11ad Library Enhancements
    • Supports latest WLAN 11ad-2012 version
    • Supports new MCS formats 28 ~ 31 for LPSC
    • Supports SystemVue Engine and Distributed Simulation in both Windows and Linux
    • Adds new measurement items including:
      • Estimated IQ Amplitude Imbalance indicates the gain matching of the I and Q channels (in dB), that is, IQAmplitudeImbalance.
      • Estimated LO Quadrature Error indicates how close to exactly 90° phase difference there is between the I and Q axes, that is, LOQuadratureError_degree.
      • I and Q DC Offset (in dB), that is, IandQDCOffset.
      • Estimated frequency error in the received symbol clock (in ppm), that is, SymbolClockError_ppm.
      • Error vector versus time (symbol) for the specified frame by parameter DisplayFrame , that is, the ErrorVectorTimeV.
      • Error vector versus frequency for the specified frame by parameter DisplayFrame, that is, ErrorVectorSpectrumV.
  • Resolved Issues:
    • Fixed debugging capability when debugging user-defined C++ models.
    • Resolved a memory leak issue that happens in usingMATLAB®Scriptunder SystemVue Engine .

    • Resolved a consistency issue in SystemVue Engine so "Use MKS" and "Use Display" is consistent with SystemVue.
    • Resolved a few stability issues when running SystemVue Engine using SVEClient.
    • Fixed a stability issue related to event notification.
    • Digital Modem Library:
      • Fixed the incorrect pulse shaping filter order in the sub-network models
    • LTE Library:
      • Fixed the range check of PRACH RB allocation
      • Fixed the crash issue in synchronization models with invalid inputs
      • Fixed range check of Ref_InputChannel in EVM model
    • Bluetooth Library: Fixed a memory leak issue in Bluetooth_EVM model.
    • RADAR Library: Fix bugs in RADAR_CW and RADAR_PulseCompression models.
  • Known Issues:

2013.08 Release Highlights: W1461 SystemVue Core Platform

Workspace Compatibility and Workspace Conversion Tool

In SystemVue , the workspace format has been updated for usability improvement and this update introduces workspace incompatibility. The workspaces created using the previous SystemVue releases are automatically converted when they are opened in SystemVue . The original workspace is not modified unless you overwrite it by saving (File > Save) the converted workspace.

The workspaces created using SystemVue are incompatible with previous SystemVue releases. You can use the following tools, available under the <SystemVue_Install_Directory>\bin directory, for converting workspaces between SystemVue and previous releases:

  • WorkspaceCoversionTool.exe: convert a workspace created in previous SystemVue releases to SystemVue compatible format.
  • WorkspaceBackwardConversionTool.exe: convert a SystemVue workspace to the the format that are compatible with previous SystemVue releases.

The command-line syntax of the conversion tools is as follows:
WorkspaceConversionTool.exe "SourcePath" "DestinationPath"

For example:
WorkspaceConversionTool.exe "C:\Examples\WorkspaceA_For2013_01.wsv" "C:\Examples\Converted\ConvertedWorkspaceA_For2014_03.wsv"
WorkspaceBackwardConversionTool.exe "C:\Examples\WorkspaceB_For2014_03.wsv" "C:\Examples\Converted\ConvertedWorkspaceB_For2013_01.wsv"

SystemVue Engine with Programming API

In SystemVue , a new standalone data flow simulator called SystemVue Engine is introduced. SystemVue Engine is used for distributed simulations and for co-simulation with other simulators like ADS and GoldenGate circuit simulators (see Verification Test Bench). The SystemVue Engine executable, SystemVueEngine, can be called from command line to run Data Flow Analyses in SystemVue workspaces. Advanced users can write C++ programs through the programming API to control SystemVue Engine. For more information about SystemVue Engine programming API, see the Programmer's Guide help in SystemVue installed help.

For SystemVue Windows installation, the SystemVueEngine executable comes with the SystemVue Windows installer and is located in the bin directory under SystemVue installation directory. In addition, SystemVue contains two examples that use the SystemVue Engine programming API:

  • SVEClientExample: a simple command line program to run a SystemVue workspace, located in \Examples\Tutorials\Simulation_Control_and_Scripting\Scripting\SystemVueEngine\SVEClientExample under SystemVue installation directory.
  • SVETester: a GUI demonstration application for running SystemVue workspaces, located in \bin under SystemVue installation directory.

SystemVue Engine also supports 64-bit Linux platform. The 64-bit SystemVue Engine Linux installer is available on the SystemVue download website. On Linux platform, the SystemVueEngine is located in the bin directory under the installation package.

SystemVue Engine saves simulation results as ADX files (an HDF5 compatible file format). An ADX file can be imported into SystemVue as a dataset in the workspace tree, using File > Import > ADX File option.

While each seat of the SystemVue environment already includes 1 license of this data flow simulator, additional concurrent SystemVue Engines can be enabled by purchasing the W1711 add-on product (see W1711 SystemVue Engine below).

Distributed Simulation

SystemVue supports distributed simulation for Data Flow Analysis and Sweep of data flow analyses using the following modes:

  1. Parallel runs on local computer – Simulations will be executed outside SystemVue environment using SystemVue Engine on the local computer.

    To use this mode, ensure that SystemVue is installed in a directory path containing only ASCII characters.

  2. Platform LSF – Simulations is executed using SystemVue Engine on machines from a Linux LSF cluster.

Distributed simulations are launched and monitored by the Simulation Manager – a distributed simulation utility tool among EEsof products. In the Platform LSF mode, the Simulation Manager uses Platform LSF to distribute and schedule simulation jobs across machines under the LSF cluster. On the other hand, when the distributed platform is set to the local computer, the Simulation Manager launches multiple simulation jobs in parallel to utilize multi-core (multi-processor) capabilities on the local computer and relies on the local operating system to perform job scheduling.

For a distributed sweep simulation, individual sweep points are run in parallel using SystemVue Engine , either on the local machine (Parallel runs on local computer) or on multiple machines in the LSF cluster (Platform LSF). After simulation, SystemVue merges distributed sweep results into a single sweep dataset in the workspace tree, similar to how a sweep is run inside the SystemVue environment.

A Data Flow Analysis can also use this feature to launch a standalone SystemVue Engine process outside the SystemVue environment (Parallel runs on local computer), or run a simulation remotely on a remote machine from an LSF cluster (Platform LSF).

Distributed simulation feature is not supported when SystemVue is installed on Windows XP.

Verification Test Bench

A VTB (Verification Test Bench) is a SystemVue Data Flow design that can be used to verify the performance of a circuit design in its design/simulation environment (ADS or GoldenGate). The benefits of using a VTB is that the performance of the circuit design can be verified using real world complex modulated signals conforming to wireless standards such as 2G/3G/4G. VTB is simulated in ADS and GoldenGate using the SystemVue Engine . For more details about creation and validation of VTBs, see Verification Test Bench and Verification Test Bench Tutorial.

VTB examples are provided to analyze LTE and WLAN 802.11ac transmitter and receiver characteristics. The example workspaces are available in the example directory: <SystemVue_Install_Directory>/Examples/VTB. For more information, see VTB Workspaces.

SystemC Model Library and SystemC Analysis

In SystemVue , two new features related to SystemC Modeling are introduced:

  • SystemC Model Library: An automatic mechanism to bring custom SystemC models inside SystemVue as SystemC model libraries. With this flow, custom SystemC models can be used in the same way as regular SystemVue models. For more details, see SystemC Model Library .
  • SystemC Analysis: A new SystemC simulation capability for simulating designs (schematics) containing only built-in SystemC models and custom SystemC models (created using the SystemC Model Library flow). Fore more details, see SystemC Analysis.

Other Platform Updates

  • Analysis dataset names now default to blank, which automatically constructs a dataset name based on the current analysis, design, and configuration names (if any), in the form: Analysis_Design_Config_Data.

    If left blank, the dataset name changes automatically if you rename an associated item. In addition, any existing dataset (with the old name) is retained for data comparison purposes.

  • CommandExpertLink now supports Command Expert 1.2.
  • SystemVue - Riviera Pro cosimulation supports only Riviera Pro 2013.02 and later.
  • HDL and XilinxIPIntegrator also support cosimulation with Questa TM.
  • New models SignalDownloader_M8190Env and SignalDownloader_M8190Env_1CH are introduced to support M8190 DUC (Digital UpConversion).
  • M8190 in Waveform Sequence Composer is also updated to support DUC.
  • Graph Series Wizard supports a new series type: Sample and Hold – Y vertex value is held till the next vertex.
  • PulseGen now supports optional trigger input.
  • New model PassiveMixerBB is introduced to support passive mixer with real baseband signal.
  • SpectrumAnalyzer now supports Hamming window.
  • The Add file button in HDL model now remembers the last selected directory.

2013.08 Release Highlights: Add-on Libraries and Design Kits

W1711 SystemVue Engine (New Product)

SystemVue's data flow simulation engine is now available separately as a standalone simulator for Windows and Linux 64-bit operating systems. While each seat of the SystemVue software already includes a license for 1 data flow simulation instance, the standalone SystemVue Engine can also be used for additional concurrent local simulations; for distributed computing using W1712 (see W1712 Distributed Simulation 8-pack below); and scripting.

W1712 Distributed Simulation 8-pack (New Product)

In SystemVue , a new Distributed Simulation capability is introduced. It is designed to support sweep evaluation when the simulation for each sweep point takes a long time to run. For more information, refer to Distributed Simulation and Licensing for Distributed Simulation.

W1719 RF System Design Kit (Spectrasys) Enhancements

High Carrier Count Intermods

You can now simulate nonlinear responses to hundreds of RF carriers with an innovative simulation technique. Traditionally, industries using many RF carriers, like TV, use simplified equations to predict nonlinear performance limited to in-band interference only. This new technique is fast and covers both in?band and out?of?band distortion simulation. You can now simulate hundreds of carriers.

For more information, see High Carrier Count Intermods

Residual Phase Noise

Several active devices now support residual phase noise. This noise is additive phase noise that is added noncoherently with any input phase noise. The models that support residual phase noise are:

Nonlinear Switch Updates

The nonlinear switch models now support more parameters so that signals appearing at other switch pins can be used to generate intermods.

New RF Architecture Examples

  • RF Amp Residual Phase Noise.wsv
  • Simple CATV Amplifier.wsv
  • Switch Intermods.wsv

W1902 Digital Modem Library (New Product)

  • Transmit and Receiver reference library for 18 common modulation formats
  • User-defined framing, with idle interval, preamble, payload, and guard interval
  • Direct Sequence Spread Spectrum (DSSS) support
  • Filtering and oversampling included
  • Adaptive EQ support in the reference receiver, to correct changing channel conditions
  • Corrections for Freq offset (Doppler shift), phase/mag error, IQ rotation/imbalance, AGC/normalization
  • BER and EVM measurements
  • New DigitalDemod model supports the demodulation of 41 modulations formats
  • New examples can be found in <SystemVue_Install_Directory>/Examples/Baseband Verification/DigMod.
  • Fix the uncorrect pulse shaping filter order in the sub-network models

W1905 Radar Model Library Enhancements

  • New Radar templates for common Radar verification scenarios
    • New examples can be found in <SystemVue_Install_Directory>/Examples/Radar/GeneralFramework.
  • Improved phased array modeling
    • New examples can be found in <SystemVue_Install_Directory>/Examples/Radar/DAR.
  • Improved Radar documentation

FlexOFDM Verification Library Enhancements

The data modulation formats are extended to support BPSK, QPSK, 8-PSK 16-QAM, 32-QAM, 64-QAM, 128-QAM, 256-QAM, 512-QAM, 1024-QAM, 2048-QAM, 4096-QAM and user-defined.

W1917 WLAN Baseband Verification Library Enhancements

New Bluetooth Library for "Smartphone" Test Coverage

The Bluetooth library follows Covered Core Package version:2.1 + EDR (26 July 2007), supporting both basic rate and enhanced data rate modes. It provides the following new models:

The new examples are located in the <SystemVue_Install_Directory>/Examples/Baseband Verification/WLAN/Bluetooth folder.

The Bluetooth_EVM model requires the WLAN license.

W1919 GNSS Library Enhancements

  • GPS scenario generator GPS_CA_ScenarioGen now supports Rinex format ephemeris file iput.
  • New fractional oversampling ratio for improved range precision in scenario replay.
  • Improved 1ms receiver trajectory step for high dynamic scenario support.
  • New GPS_CA_Positioning model to calculate GPS position. The new example is located in <SystemVue_Install_Directory>/Examples/Baseband Verification/GNSS/GPS.
  • New GPS_CNR_Estimation model and corresponding example are provided for GPS signal S/N0 estimation.
  • New Beidou2 scenario generator BDS_ScenarioGen and new Beidou2 single source BDS_B1I_Source. The new examples are located in <SystemVue_Install_Directory>/Examples/Baseband Verification/GNSS/BDS
  • New Beidou2 receiver models including acquisition (BDS_B1I_Acquisition), tracking (BDS_B1I_Tracking) and positioning (BDS_B1I_Positioning) models. The new examples are located in <SystemVue_Install_Directory>/Examples/Baseband Verification/GNSS/BDS

W1713/W1714 AMI Modeling Updates

  • New PhaseFreqDetector model to implement a phase and frequency detector(PFD) between input signal and reference clock VCO as a part of phase- and frequency-locked loop (PFLL).
  • New ClockRecovery model to implement clock recovery mechanisms based on either phase-locked loop (PLL) or phase-locked and frequency-locked loop (PFLL).
  • New parameter TimingMethod to specify the method of edge detection in model ClockTimes, BlindDFE, and DFE
  • New output ports voutq and clockq to produce quadrature clock outputs in VCO model
  • New example workspace SerDes_with_CDR_PFLL to demonstrate how SystemVue can be used for IBIS AMI SerDes Modeling of a 14.025 Gbps system with phase/frequency locked loop. A PAM4 transceiver system is also provided in this example for reference.
  • New ADS workspace SerDes_with_CDR_PFLL_wrk.7zads to use the AMI files generated from SerDes_System_with_CDR_PFLL.wsv
  • New VCSEL_Extractor model to implement device abstraction from the stationary measured data(such as V-I, L-I curves) by curve fitting methods.
  • Updated VCSEL model to simulate the performance of a real VCSEL device, that is the relationship Po(t; I).
  • New example workspace for VCSEL simulation located in the <SystemVue_Install_Directory>/Examples/Model Building/IBIS-AMI Modeling folder.

W1716 Digital Pre-Distortion Builder Updates

  • A new option Enable Power Backoff is added in DPD Setting. If this option is enabled, the PA input power will be backed off, that is, the PA input power with DPD in Step 4 would be lower than the original PA input power without DPD in Step 1. If this option is unchecked, the PA input power will be kept the same, that is, there is no power backoff. This option is only active when Model Type is selected as Memory Polynomial or Volterra Series. For Look-Up Table, this option is hidden and always enabled. If this option is enabled, the whole process is the same as in previous release (that is, SystemVue 2013.01).

    If this option is unchecked ( that is, there is no power backoff), there is no need to re-download the original signal in Step 5. Since the input power is the same in Step 4 and Step 2, we can just compare the results in these two steps to verify DPD response. Similarly, when Current Iteration ≥ 2, there is no need to re-capture the PA output with DPD in Step 2, because the signal is the same as which captured in Step 4 of the previous iteration.

  • A Get PA Characteristics button is added in Step 2 in the manual DPD UI. Click this button to run the analysis and get PA characteristics from the captured PA input and output data in Step 2. Similarly, a Get DPD-PA Characteristics button is added in Step 4.
  • A PAPR button is added in Step 4 to show the PAPR of the pre-distorted signal.

W1717 Hardware Design Library Enhancements

  • On <TOPHDL>_CosimWrapper.v(hd), a new clock enable signal "ce" is added that can control all sequential logics of generated HDL. Automatic Xilinx and Altera FPGA flow now uses <TOPHDL>_CosimWrapper.v(hd) as top level design. Users can use the new added ce signal to control all sequential logics of generated design.

Release Highlights: Licensing

  • SystemVue 2013.08 requires: a) version 2013.05 of the EEsof EDA licensing software and b) version 3.1 codewords to run.
  • A real-time and systematic license setup troubleshooting utility is added to the License Manager tool’s Diagnose tab. This utility also produces a detailed health report of the configuration.
  • SystemVue does not automatically release licenses after checking out. In SystemVue 2013.08, there is a new menu button Action > Release All Simulation Licenses for users to manually release all checked out simulation licenses.
  • LTE-Advanced Baseband Verification Library usage usually requires the sv_mdl_lteadv and sv_mdl_lte licenses because the top level models like Source/Receiver have LTE models inside the sub-circuits. Earlier, it required the sv_mdl_ltea license only. LTE Baseband Verification Library does not work with sv_mdl_lteadv license, earlier it used to work. For more details, refer to SystemVue Product Dependencies.

Resolved Issues

SystemVue Platform and Models

  • SData model has been updated to handle simulation sampling rate that is other than two times of the maximum frequency component in the S parameter, when the input is a real signal with characterization frequency equal to 0. For real input signal, the parameters ExtrapolationOption, ExtrapolationRollOff, and MinFFTOrder shown under ShowAdvancedParams are used.
  • Resolved a ReadSignalStudioFile issue where leading zeros are incorrectly inserted when reading out certain waveform files.
  • Resolved several Spectrasys related issues including phase noise, intermod coherency, multisource, path measurement for switch state, S-parameter and X-parameter models.
  • Improved Waveform Sequence Composer stability.
  • Addressed RF power issues in the downloaded waveform when using SignalDownloader_M9381A.
  • Restored DFE coefficient report so the computed DFE initial taps are reported in the Simulation Log.
  • Addressed IBIS AMI Linux compilation issues related to machine setups.
  • Resolved SystemVue 32-bit and ModelSim TM 32-bit Verilog cosimulation issue.
  • Improved HIL quality and stability issues.
  • Resolved FFT_Fxp HDL code generation issues.
  • Resolved stability issues related to equation debug and command windows, tuning, and duplicated dataset variables.
  • Restored =variable syntax for defining dataset name in an analysis.
  • Resolved Design Equation snapshot issue.
  • Improved SystemVue documentation.

SystemVue Applications

  • Resolved a crash defect in WLAN 802.11a EVM model when writing data to dataset.
  • Resolved a bug in WLAN 802.11ac spatial mapping matrix.
  • Resolved a bug in WLAN 802.11ac to provide EqualizerTraining option.
  • Resolved a bug in variable definition of SigBits and VHT_SIGB_CRCBit in case of SU in WLAN 802.11ac library.
  • Resolved a bug in VHT LTF generation in WLAN 802.11ac library.
  • Resolved a bug in FlexOFDM sources for reading pilot data from a file.
  • Resolved a defect to support ETM TDD demodulation in LTE_DL_EVM model.
  • Resolved a bug for measure length > 20 slots in LTE_DL_EVM.
  • Updated the model to check the buswidth of the output of LTE_DL_UESRS_Port5 model
  • Resolved a bug for TimeOffset in LTE_DL_EVM model.
  • Resolved a bug in LTE ETM model.
  • Improved Radar documentation.
  • Updated some Radar example workspaces, including Antenna, DAR_STAP, AF, DAR_STAP, PhasedArray_Tx_1D, Channelized_TxRx, EW_pulse_Hopping and ClutterGenExample.

Licensing

  • The EEsof EDA License Tools version is 2013.05. Licensing vendor daemon (agileesofd) is upgraded to sync up with FlexNet FNP 11.9.1 version of FLEX license manager (lmgrd). SystemVue 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 more details, refer to Licensing (For Administrators).
  • On windows, a possible Administrator privilege issue preventing the automatic restarting of the FlexNet license server program, lmgrd, after the PC comes out of the hibernation mode has been fixed. The FlexNet license server is now automatically restarted without any user intervention.

Known Issues

Licensing Known Issues

  • SystemVue 2013.08 requires EEsof Licensing Tools version 2013.05 or later. It will not work with older EEsof Licensing Tools versions like 2013.01 or earlier.
  • 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.
  • On the Linux platform, SYSTEMVUE_LICENSE_FILE needs to be correctly specified before starting SystemVue. Without that being set correctly, SystemVue would not start.
  • 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 or floating bundle cannot be shared between SystemVue 2013.08 and SystemVue 2011 or earlier releases when run at the same time.
  • The "Check-in failed" message occurs in the license activity log occasionally can be ignored; the license mentioned in this message is properly returned.
  • License Setup Wizard does not remove any previous user-configured FLEX Windows License Service installed 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.
    • 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).
  • If a license server is configured with two license versions, that is, version 2.8 and 2.9 node-locked license files, the license server may crash.
    Workaround: You should combine the two license files into one file, instead of using them separately.
  • For LSF style distributed simulations, in case of windows, ensure that the PATH points to the $HPEESOF_DIR/EEsof_License_Tools/${architecture} directory that corresponds to the EEsof release being used. This will ensure that the proper version of the Flexera utilities (like lmutil) gets picked up in the path before any older incompatible 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 on Linux platform 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).
  • On windows, FlexFNP license server program, lmgrd, may not be automatically restarted during EEsof application startup after PC comes out of the hibernation mode; instead the License Setup Wizard dialog box pops up.
    Workaround: Go ahead and select the Add or replace a license file and follow the guided tour. Accept the settings presented in each step to complete the license setup. Another workaround is to allow users write permissions on C:\Program Files (x86)\Agilent\EEsof_License_Tools directory.
  • If SystemVue does not start after you reboot your 64-bit Windows computer, and a license denial message is displayed, then it might be caused by a spurious registry entry. Check to see if registry entry HKEY_LOCAL_MACHINE\SOFTWARE\FLEXlm License Manager\EEsof EDA License Server exists; if it does, remove it and restart SystemVue.

Other Issues

  • Antivirus on your system may remove one or more files installed during the SytemVue installation leading to a corrupt SystemVue installation.
    Workaround: Disable antivirus and other related programs on your system before installing SystemVue. You can enable them once the SystemVue installation is complete.

Operating System Roadmap

SystemVue future releases post 2013.08 will not support Windows XP. For more details, refer to [Supported Platforms|http://edadocs.software.keysight.com/display/ engdocsv/Supported+Platforms].

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