CM LA 169xx Source

CM_LA_169xx_Source

Description: Waveform output using data downloaded from an analyzer that resides in a 169xx mainframe
Library: Instruments
Class: SDFCM_LA_169xx_Source

Parameters

Name	Description	Default	Type
InstrumentHostname	Logic Analysis System hostname or IP address	la16900	string
InstrumentSetupFile	name of instrument state file		string
ModuleName	name of the Analyzer module to be used	My 168x/9x-1	string
BusSignalNames	names of bus signals in analyzer memory	MyBus1	string array
StartingSampleNumber	index of starting sample in analyzer	DefaultNumericStart	int
EndingSampleNumber	index of ending sample in analyzer	DefaultNumericStop	int
RunBeforeCapture	run new measurement before retrieving data: NO, YES	NO	enum
RepeatData	zero-pad, repeat data: SinglePass, Repeat	Repeat	enum
ControlSimulation	control simulation: NO, YES	NO	enum
TimeoutInSeconds	The length of time to wait, in seconds, before giving up on data transfer	120	int

Pin Outputs

Pin	Name	Description	Signal Type
1	output		multiple int

Notes/Equations

The CM_LA_169xx_Source model retrieves data from a Logic Analyzer module residing in a 169xx Logic Analysis (LA 169xx) mainframe and propagates the retrieved data into an ADS Ptolemy simulation.

Note
The notation LA 169xx mainframe is used here to represent all Agilent 16900-series logic analysis systems and 1680/1690-series logic analyzer mainframes. A 169xx Logic Analysis mainframe is essentially a Windows XP computer housed in a modular frame with slots that accept measurement (Analyzer) and stimulus (Pattern Generator) plug-in cards.
For more information regarding logic analysis systems, options, and modules, visit the website http://www.agilent.com/find/logic.

CM_LA_169xx_Source uses the Agilent Connection Manager (CM) architecture to communicate with the instrument. Compared to other CM-based ADS Ptolemy instrument link models, this component has notable differences that are described here.
CM_LA_169xx_Source communicates with the instrument by using the CM server to load a COM Automation Server that is pre-installed on LA 169xx mainframes (as part of the Agilent Logic Analyzer application.) The COM object provides a mechanism for controlling the Agilent Logic Analyzer application from remote computers on the LAN. To enable the CM_LA_169xx_Source to communicate with an LA 169xx mainframe, install the CM server on the LA 169xx mainframe itself.
For details regarding installing the CM server on a Windows XP PC, refer to Installing Connection Manager Server on Windows in the Windows Installation documentation.
Note that also the Agilent Logic Analyzer application can be installed and used on a Windows XP/2000 computer for remote access of 16900- or 1680/1690-series logic analyzers on the network, or for offline analysis of data captured on 16900-, 1680/1690-, or 16700-series logic analyzers. In this setup, install the CM server on the same PC on which the Agilent Logic Analyzer application resides. This documentation refers to such a Windows XP/2000 computer as the LA 169xx mainframe and its file-system as the LA 169xx mainframe file-system, although it could be a standalone Windows XP/2000 computer running the Agilent Logic Analyzer application that emulates an LA 169xx mainframe.
CM_LA_169xx_Source does not enable interactive instrument selection using the Remote Instrument Explorer (a feature common to many CM-based instrument link models). This restriction is due to the nature of IO connectivity options available in the LA mainframes that the model interacts with.
Prerequisites for using CM_LA_169xx_Source are:
- An LA 169xx mainframe with the Agilent Logic Analyzer application installed (Refer to note 1 for the definition of an LA 169xx mainframe.)
- An active Connection Manager server instance installed and running on the LA 169xx mainframe.
- Network connectivity over the LAN from the workstation running ADS to the LA 169xx mainframe.
InstrumentHostname specifies the DNS hostname or IP address of the LA 169xx mainframe to be used.
Optionally, InstrumentSetupFile specifies an LA 169xx mainframe state file. The LA 169xx mainframe enables you to save the current instrument state and/or data into a file on its file-system. Any file path specified in InstrumentSetupFile must be relative to the instrument's file system. If a full path is not provided, the program assumes that the file exists in the default config directory (usually C:\Documents and Settings\<username>\MyDocuments\Agilent Technologies\Logic Analyzer\config ).
ModuleName specifies the name of the analyzer module that you want to retrieve data from into the simulation. In Module Name Example, the module name would be My 168x/9x-1.

Module Name Example
BusSignalNames specifies a string array containing the names of the bus signals whose values you want to propagate into a simulation. The data output pin carrys one connection per bus signal name defined by this parameter. For example, to capture the bus signals in BusSignalNames Example, set BusSignalNames = MyBus1 MyBus2 MyBus3.

BusSignalNames Example
Signals are ordered from bottom to top on the schematic. To retrieve more than one signal using CM_LA_169xx_Source, you can use a BusSplit component to control the order.
For example, when using BusSplit2 and BusSignalNames = MyBus1 MyBus2, the bottom output is MyBus1.
StartingSampleNumber specifies the index value that represents the first instrument data point you want to propagate into the simulation. This value can be any valid index as shown in Start and End Sample Number Example.
EndingSampleNumber specifies the index value that represents the last instrument data point you want to propagate into the simulation. This can be any valid index value (as shown in Start and End Sample Number Example) that is greater than the index value specified by StartingSampleNumber.

Start and End Sample Number Example
RunBeforeCapture specifies whether a new measurement run is initiated before data capture.
- RunBeforeCapture = NO The simulation collects data from the instrument without a new measurement run.
- RunBeforeCapture = YES The simulation collects data from the instrument after a new measurement run.
RepeatData instructs the simulator on what to do when all the data retrieved from the LA 169xx mainframe has been propagated into the simulation.
- RepeatData = SinglePass Pad zeros until simulation end.
- RepeatData = Repeat Repeat the same data until simulation end. CM_LA_169xx_Source retrieves data again from the LA 169xx mainframe and propagates it into the simulation. To run a measurement before retrieving the data each time it is repeated, set RunBeforeCapture = YES.
If ControlSimulation = YES, the number of data points specified (EndingSampleNumber - StartingSampleNumber + 1) determines how long the simulation runs.
CM_LA_169xx_Source has one output pin of type int. However, this is a multi-output pin and can be used to propagate as many integer outputs in parallel into the simulation as needed. To see an example on how this can be set up using BusSignalNames, refer to note 7.
The Analyzer module in an LA 196xx mainframe stores data as bit vectors. For each simulation step, the bit vector associated with each signal is retrieved and interpreted as an integer. Further, no attempt is made to interpret the most significant bit as a sign bit if the vector is less than 32 bits wide. Any such interpretation can be done on the schematic using appropriate ADS Ptolemy models. Ptolemy interprets a vector with the most significant bit set to 1 as a negative integer only when the vector is exactly 32 bits wide.
To bring in data that is wider than 32 bits, split the data into multiple bus signals on the logic analyzer and propagate the data concurrently using multiple connections on the CM_LA_169xx_Source output.
To access example designs that use this model, from the ADS Main window, choose File > Example Project > Instruments > CM_LA_169xx_prj.