TLA Application Software V5.6 Release Notes (A formatted version is available in the download package.) Version: 5.6.754 Date: March 30, 2010 Contents of these release notes: 1) Description of Release 2) Installation Notes 3) Software Version Table 4) Compatibility Notes 5) Operational Notes 6) Known Issues 7) Contacting Tektronix 1) DESCRIPTION OF RELEASE ========================== The TLA Application Software is the collection of software components required to run a Tektronix TLA Series Logic Analyzer. Tektronix Logic Analyzers are shipped with with this software already installed. In order to update an earlier version of TLA Application Software, or to control your logic analyzer remotely from a PC over a network connection, you must explicitly install this software. To install this software, refer to the installation notes below. If you are upgrading from a pre-V5.6 version of the TLA Application, V5.6 has the following major changes: 1. Support for new TLA7ACx, TLA7BBx, and TLA7BC4 modules 2. Completely new LA Setup window 3. iView(tm) support added for new Tektronix Oscilloscopes 4. Support for Windows 2000 discontinued 5. Update installation of the TLA Application, rather than a Remove/Add installation that requires a System Restart 6. An updated firmware image for the TLA7016 mainframe (TLA7012.upd) that fixes an occasional system crash 7. Correction of a data buffer truncation problem that affected the amount of data returned from TLA7Sxx modules 8. The ability to filter TLA7Sxx module data in Listing and Waveform windows If you are upgrading from earlier versions of V5.6, this web-only update contains the following updates: 1. Supports edge detection trigger events and Transitional Storage when prime channels are present in a TLA7Bxx module setup (see Operational Notes, below, for limitations) 2. Fixes an intermittent TLA Application crash, during repetitive acquisitions, when TLA7Sxx modules are enabled in the system 3. Fixes an LA Trigger window problem where defaulting the trigger setup disables trigger editing controls 4. Fixes a TLA Application crash when cursors are locked across data windows, and the user deletes the reference data window 5. Fixes a TLA Application toolbar restore problem that occurs when V8.0.59193 of Microsoft's Visual C++ Redistributable Package, which is included as part of a security update for Microsoft Visual Studio 2005 Service Pack 1 (KB971090), is installed on a TLA Mainframe or host PC (see Operational Notes, below, for limitations) 6. Fixes a problem where modified Setup & Hold values for LA data channels and trigger events saved to a file fail to restore when reloading the file 7. Provides a more intuitive file save and load interface that enables you to change default folder locations for TLA files quickly 8. Dynamically updates the most-recently used lists in the TLA Application file menu to reflect the order in which the files were accessed 2) INSTALLATION NOTES ====================== This version of TLA Application Software is an update to the version shipped from the factory pre-installed on TLA systems along with Windows XP Professional. Recovery media is included on a hidden partition of the hard drive of shipped systems. Refer to your TLA system's Installation manual for details on creating your own recovery media. This version of TLA Application Software can only be used with TLA7000 and TLA5000 Series Logic Analyzers. It can be installed on a TLA7012 Portable Mainframe or on a standalone PC (including the TLA7PC1) used to remotely control a TLA7016 Benchtop Mainframe. It can also be installed on any TLA5200B series, or on a TLA5200 that is running Windows XP. If you install this software on a standalone PC to control a TLA System remotely, ensure that all the TLA software and drivers (including GPIB drivers if using iView(tm)) is installed on the C: drive. Also ensure that the remote TLA System has the same version of software installed. This version requires Microsoft's .Net Framework version 2.0, which is included in the installation package. When upgrading to this software, follow these basic steps: 1. Install this version of the TLA Application Software. You may install it directly on top of an earlier version. The installation program will overwrite the old version immediately, unless it encounters a locked file. In the case of a locked file, the installer will prompt you for a restart to complete the update. 2. If using TLA7S08 or TLA7S16 modules, install the corresponding version of the TLA PCI Express Support Software (also available on the Tektronix website). You may install it directly on top of an earlier version. The TLA PCI Express Support Software has its own release notes. 3. Upgrade Mainframe firmware if needed. When you start the TLA Application a message will be displayed if a mainframe firmware upgrade is needed. (Note that in a TLA7016 expansion system, you cannot upgrade the TLA7016.upd mainframe firmware file in more than one frame at a time.) 4. Upgrade Module firmware if needed. When you start the TLA Application a message will be displayed if a module firmware upgrade is needed. Mainframe and module firmware files are copied to your TLA or PC during installation. To upgrade the firmware, click on: Start > All Programs > Tektronix Logic Analyzer > TLA Firmware Loader If using iView(tm), the NI-488.2 software must be installed separately. It is available on CD #1 of the TLA application software. TLA7012 upgrades 1. WARNING: When upgrading a TLA7012 from V5.0, do NOT turn on the TLA Server before upgrading the TekLink(tm) firmware. Doing so will corrupt the instrument firmware. The TLA Server Control is an icon in the Windows notification area (lower right), and is turned off by default after installation, indicated by a red circle. Complete all firmware upgrades before re-enabling the TLA Server. 2. On a TLA7012 running V5.0 and TekLink(tm) firmware V5.0.074, you must run the firmware loader locally to update the TekLink(tm) firmware. When connecting to a TLA7012 from a remote PC, the firmware loader fails to display "TekLink" in the choice dialog box, making it impossible to upgrade the TLA7012 remotely. 3. When upgrading a TLA7012 from V5.1, you may see a warning "Failed to register TlnkMonSvc" during removal of the old software. Ignore this warning and click OK. The upgrade will proceed normally. 3) SOFTWARE VERSION TABLE ========================== The following table shows the individual components of the TLA Application Software and their version numbers. Also shown are the other major TLA software components that are external to the TLA Application Software (i.e. installed separately). There is one column for each of the most recent releases of the TLA Application Software. Version numbers marked with an asterisk (*) are the significant updates in this latest release. Release 5.6 5.5 5.1SP1 5.1 ------------------------------------------------------------ TLA Application SW 5.6.754* 5.5.096 5.1.135 5.1.121 - TLA7Bxx FW 5.6.029 5.5.006 NA NA - TLA7Axx FW 5.6.007 5.5.002 5.0.002 5.0.002 - TLA7NAx FW 5.5.003 5.5.002 5.0.002 5.0.002 - TLA7N/P/Qx FW 5.5.001 5.5.001 4.3.14 4.3.14 - TLA520x FW 5.6.002 5.5.001 4.4.001 4.4.001 - TLA7016 FanCtl FW 5.2 5.2 5.0 5.0 - TLA7016 MF FW 5.6.004 5.5.004 5.1.188 5.1.187 - TLA7012 FW 1.3 1.3 1.2 1.2 - TekLink(tm)FW 5.5.001 5.5.001 5.1.187 5.1.187 - TL708EX FW 5.5.001 5.5.001 5.1.187 5.1.187 PatGen App SW 1.10.003 1.9.002 1.8.116 1.8.116 - PatGen FW 2.01 2.01 2.01 2.01 TekVisa(tm) 3.3.0.14 3.3.0.14 3.0.1.02 3.0.1.02 Windows XP 5.1.2600 5.1.2600 5.1.2600 5.1.2600 - SP3 SP2b SP2b SP2 MS .NET Framework 2.0.50727 1.1.4322 1.1.4322 1.1.4322 SnagIt 7.2.1 7.1.1 7.1.1 7.1.1 CheckIt Utilities 7.0 7.0 7.0 7.0 NI-488.2 * 2.3 2.3 2.3 2.3 NI-MAX 3.1.0 3.1.0 3.1.0 3.1.0 Nero 8.3 6.6.0.8 6.6.0.8 6.6.0.8 Adobe Reader 9.0 8.0 7.0 7.0 TLA5200B BIOS 4089 4078 3996 NA TLA7012 BIOS 5.0.11 5.0.11 5.0.11 5.0.11 * NI-488.2 v2.3 is the last version to support the GPIB-USB-A cable. 4) COMPATIBILITY NOTES ======================= Upgrading from Pre-V5.6 Versions Tektronix encourages TLA users to upgrade to Version 5.6, unless their use of the TLA application involves compound clocking (multiple clocks and qualifiers). Please review Section 5, Operational Notes, for more details about changes to Version 5.6 that may affect your usage. TLA Mainframe Compatibility This version of TLA Application Software should only be installed on TLA7000 or TLA5000 series mainframes or on PCs running Windows XP Professional. Module Compatibility The supported TLA module types are listed in the table above. Refer to the table to determine which module types will need firmware upgrades when you upgrade to this version of TLA Application Software. Versions 5.5 and later support the TLA7S08/S16 Serial Analyzer modules, however the software and firmware for the TLA7Sxx modules must be installed separately. Save File Compatibility TLA save files are forward-compatible from the last major release. Saved files from 5.1SP1 and earlier versions of TLA Application software should load properly on newer versions of the TLA Application Software. TLA save files from an interim release may not be forward compatible to future releases of the application. TMS Microprocessor and Bus Support Compatibility In general, all TMS microprocessor and bus support packages introduced after a given release of the TLA Application Software require that version of the TLA Application Software or higher. TPI Client Software Compatibility If you use COM-based TPI (TLA Programmatic Interface) on a remote PC, you must install this version of the TLA Application Software which includes the TPI client on that PC. Failing to do so may result compatibility problems. See the TPI Help for more information. If you are running on a PC or TLA mainframe that is running Windows XP Professional, see the Operational Notes below for information on how to configure your system to support COM-based TPI. 5) OPERATIONAL NOTES ===================== The following notes describe functions associated with this version of software that can affect how you use your Tektronix Logic Analyzer. The listed functions are high impact or frequently seen problems. Microsoft Visual C++ Redistributable Package, V8.0.59193 and TLA Application Toolbars When V8.0.59193 of Microsoft's Visual C++ Redistributable Package is installed on a TLA mainframe or host PC, the toolbar positions restored from a TLA system file can be corrupted. The problem does not occur with earlier versions of the package. To work around the problem, the TLA application currently does not attempt to restore the toolbar positions saved in the TLA system file. Instead, the current toolbar settings remain unchanged during and after a system file load. Default Channel Threshold Setting for TLA7Bxx Modules The default channel threshold setting of 1.5V shown in the LA Setup window for TLA7Bxx modules is incorrect. To use that value, you must change the displayed voltage setting to a different value, then change it back to 1.5V. Prime Channels and Edge Detection for TLA7Bxx Modules When prime channels are present in the TLA7Bxx module setup, the edge detectors used for trigger events and Transitional Storage do not distinguish between an edge seen on a base channel and an edge seen on an associated prime channel. Support Packages and TLA7Bxx Modules Narrow-width support packages will not load onto wider-width TLA7Bxx modules. Setup & Hold Storage and Triggering in TLA7Bxx Modules Setup & Hold storage and triggering are not available on TLA7Bxx modules acquiring in Custom clocking mode. Setup Window The LA Setup window is entirely new for version 5.6. It provides an enhanced user experience that is intended to be more intuitive. Exploration is encouraged. Large Systems Many multi-mainframe and merged configurations may work for this release, but only single mainframe configurations with TLA7012 and TLA5000 series have been subjected to substantial testing. Synchronous Clocking Synchronous clocking (formerly known as "External") only supports single clocking. Saved systems with compound clocking may be loaded, viewed, and used for acquisition, but the compound clocking settings may not be modified by the user. Compound clocking no longer supports the use of Clk and Qual demux channels Changes in Demux Source Channels for narrow modules For narrow modules (TLA7AA1, TLA7AA2, TLA7BB2) while in demux clocking, probes A2 & A3 are no longer source channels. In this configuration, probes C2 & C3 are used as source channels. Deskew Dashboard The Deskew Dashboard in the LA Setup Window for supporting simple automated setting of sample point offsets is disabled for this release. The S/H Analysis plug-in interface available in previous releases is available for providing this functionality. LA Setup Window Undo The Undo functionality in the LA Setup Window is disabled for this release. No Custom MagniVu Beta versions provided synthetic data termed Custom MagniVu when in Custom clocking mode. This feature has been removed and now Async/Sync MagniVu is again provided as it was in earlier versions. Anti-virus software This product is not equipped with virus protection software. If this instrument is going to be placed on a network, it is highly recommended that you add such software. Prior to leaving Tektronix, this product was checked for known viruses and to the best of Tektronix' knowledge, was considered clean of known security threats. Power configuration and settings Tektronix recommends that you not modify the power-related settings in either the BIOS or the Power Management area of Windows XP Professional. They are set at the factory to a configuration that is optimal for the logic analyzer. Windows XP user accounts If you add new user accounts on the TLA using the Windows XP User Accounts applet in the Control Panel, the new user may be set up as either a "Standard User (Power Users Group)" or a "Restricted User (Users Group)". This is configured in the Group Membership tab of the User Properties dialog box. The TLA will not operate correctly for a "Restricted User" unless the Users group is given Full Control permission for the "C:\Program Files\TLA 700\System" directory. This is because there are several dynamic files created in the System directory when the instrument boots. Multiple users Although Windows XP Professional allows multiple users to login simultaneously, only one TLA application at a time can access a TLA mainframe's hardware. To enforce this restriction, only one user at a time can log into a TLA mainframe. This restriction only applies to TLA mainframes, not to a PC controller connected to a TLA mainframe. To enforce this restriction, TLA mainframes shipped from the factory with Windows XP Professional installed have the "Use Fast User Switching" option disabled in: Control Panel > User Accounts > Select login and logoff options. Windows Desktop Search The WDS application has been found to cause the TLA application to intermittently hang during power-up of TLA7012 instruments, so it has been disabled on instruments shipped from the factory. External flat panel displays If you are using an external flat panel display with your TLA, for best operation Tektronix recommends running the monitor's AutoSet procedure which adjusts the monitor settings to be most compatible with the video signal. Refer to the documentation that comes with the monitor for details. Configuration of Windows XP Professional for COM-based TPI support ------------------------------------------------------------------ In addition to the standard steps required for setting a Windows 2000 platform for COM, you must also perform the following steps to enable COM-based TPI on a TLA mainframe running Windows XP Professional. Please note that these steps may pose a security risk. You may wish to consult your network administrator to assess the risk for your circumstances. 1. Go to START->RUN and type "gpedit.msc". In the Group Policy go to COMPUTER CONFIGURATION->WINDOWS SETTINGS->SECURITY SETTINGS->LOCAL POLICIES->SECURITY OPTIONS. Set the option "Accounts: Guest account status" to "Enabled". 2. Set the option "Accounts: Limit local account use of blank passwords to console login only" to "Disabled". 3. Now scroll further down and set the "Network access: Allow anonymous SID/name translation" to "Enabled" if permitted, if not please disregard. 4. Reboot the computer and log back in as administrator. 5. Set "Network access: Let Everyone permissions apply to anonymous users" to "Enabled". 6. Under to the "USER RIGHTS ASSIGNMENT", add to the "Access this computer from the network" the "Guest" user. 7. Make sure that the "Guest" user is removed from the "Deny access to this computer from the network" and "Deny logon locally" lists. 8. Go to START->RUN and type "dcomcnfg.exe". Expand Component Services and then expand Computers. Right click on My Computer and select Properties. 9. Under the Default Properties tab, check Enable COM Internet Services on this computer, change Default Authentication Level to Default, and change Default Impersonation Level to Anonymous. 10. Under the COM Security tab, go into all four buttons and add the user “Everyone” with all access allowed. Then restart. 6) KNOWN ISSUES ================ The following list contains information on instrument functions associated with this release of the TLA Application Software. This version of the TLA Application Software has the following known issues and workarounds. Unless noted otherwise, these issues apply to all models in the Tektronix Logic Analyzer Family. Issues that are related to the TLA7S16 Serial Analyzer module are not documented here but are in the release notes for the TLA PCI Express Support Software, located in: C:\Program Files\TLA 700\Serial\PCIe. Accessing Autodeskew after manually merging, then loading a multi-module support package crashes the TLA application -------------------------------------------------------------------------------------------------------------------- Some support packages require merged modules. Manually merging the modules before loading the support package will lead to a crash if the user attempts to access Autodeskew afterward. However, if the user allows the load operation to merge the required modules automatically, access to Autodeskew works correctly. TLA application crashes when TLA7AXX modules with different memory depths are merged ------------------------------------------------------------------------------------ For example, an acquisition using 4 TLA7AB4 64M modules merged with 1 TLA7AA4 32M module may crash the TLA application. TLA application does not exit properly after creating a graph window -------------------------------------------------------------------- If a graph window is created, then the tla700.exe process does not exit even after the user exits the application. Subsequent attempts to start the application will show the application window briefly before it exits from the screen. To recover from this problem: 1. Start the MS Windows Task Manager by pressing Ctrl-Alt-Del and then clicking on the Task Manager Button. 2. Click on the Processes Tab and find the row with the Image Name of tla700.exe 3. Right click on tla700.exe and choose End Process Tree. 4. Click on Yes for the Task Manager Warning Dialog that is presented. Hidden dialog requires 'ALT' key to continue -------------------------------------------- When loading some support packages, the user will be shown a dialog informing the need to Merge modules. Following a 'Yes' click a second dialog will be hidden and awaiting a user confirmation. The user needs to press the 'ALT' key to surface the dialog and continue the installation of the support package. Error message displayed when changing clock modes ------------------------------------------------- When changing clock modes some channel groups may become unavailable, which causes the disassembler to display an error in the status area. The warning can be safely ignored, but pressing the Details... button will then show a dialog that can be safely ignored and closed. TPI.NET ILATriggerAction interface ---------------------------------- The TPI.NET programmer's reference is missing a definition for the Arm event for the ILATriggerAction.Definition property. The BNF for ILATriggerAction.Definition requires the following updates: ::= | | | | | | | | DoNothing ::= Arm ::= "" NOTE: White space, other than a space character, and the single backquote (`) are invalid. Probe names for clocks and qualifiers are now appended with empty parenthesis () -------------------------------------------------------------------------------- This change has not yet been reflected in the TPI documentation, and may impact developers of TPI.NET client programs. VXI-11 addressing ----------------- Although VXI supports addresses from 1 to 254, VXI-11 does not support static addresses above 95. This has no impact when running the TLA Application Software locally on a TLA mainframe. However, any time the TLA Application Software runs on a TLA mainframe remotely, the Application will not see modules that have VXI static Logical Addresses from 96 to 254. The modules will not appear in the system. Workaround: Always configure LA Modules to use dynamic Addresses. This can be done by setting the address switches to FF. External Oscilloscope attenuation and input impedance with analog multiplexer ----------------------------------------------------------------------------- This issue applies only to TLA7Axx logic analyzer modules. When the Analog Output of a TLA7Axx module is connected to an oscilloscope using an iView(tm) Analog Output BNC-to-BNC cable, the attenuation of the oscilloscope channel is automatically set to 10X by the cable. However, when the TLA is set to 5X attenuation mode, the oscilloscope's vertical scale must be manually set to match. Also, the termination impedance of the oscilloscope channel is not automatically set. In order to see a proper representation of the analog signal on the oscilloscope, the input termination impedance must be manually set to 50 ohms. If a standard BNC-to-BNC cable is used to connect the logic analyzer analog output to an oscilloscope, then both the 50-ohm termination and proper attenuation must be set manually on the oscilloscope. iView(tm) adjustments to scope settings --------------------------------------- At times, an oscilloscope's settings may be incompatible with the operation of the TLA iView(tm) feature. In those cases, the TLA application modifies the oscilloscope's settings so that iView(tm) will continue to function. Among the changes that can occur are the following: * The iView(tm) feature does not support ET sampling mode on the oscilloscope. To disable ET mode, iView(tm) first sets the scope to single sample, horizontal roll off, and FastFrame 0. If the oscilloscope still remains in ET mode, iView(tm) then explicitly places the oscilloscope in IT sampling mode. * The maximum horizontal resolution iView(tm) supports is 1ps. If an oscilloscope is set to a sampling rate with more resolution than 1ps or that produces a resolution not divisible by 1ps, iView(tm) attempts to avoid rounding error by resetting the horizontal sampling rate to a resolution of 25ps. In some cases, the oscilloscope's other settings prevent it from achieving a resolution of precisely 25ps; in those cases, the oscilloscope sampling resolution will be set to a value as close to 25ps as possible (determined by the oscilloscope), and rounding errors may affect the accuracy of the iView(tm) display. TDS1000/2000 with iView(tm) ----------------------- If you take an acquisition after changing the horizontal scale setting on any TDS1000/2000 Series oscilloscope, the TLA and scope waveform edges may no longer be aligned. You can re-align them in the waveform display that contains the TDS1000/2000 data (Menubar > Data > Time Alignment). Make sure your external oscilloscope is the Data Source, then adjust the time offset to align the waveforms. The following table lists the approximate offsets for various horizontal scale settings: Horiz.Scale Time Offset 100 ns -5 ns 250 ns -11 ns 500 ns -18 ns 1 us -12 ns 2.5us -50 ns 5 us -120 ns 10 us -250 ns 25 us -650 ns iView(tm) cable with unused oscilloscope ---------------------------------------- When you are not actively using the iView(tm) feature of the TLA, it is recommended that you unplug the System Trig In connector of the iView(tm) cable from your logic analyzer. This will help avoid problems with inadvertent triggers generated by activity on the oscilloscope. It is also recommended that the System Trig In of the iView(tm) cable not be connected when the oscilloscope is turned off and the logic analyzer is in use. Data alignment is incorrect when a DSO4000 Series oscilloscope triggers a TLA logic analyzer using iView -------------------------------------------------------------------------------------------------------- When a DSO4000 Series oscilloscope triggers a TLA logic analyzer through iView(tm), the oscilloscope and logic analyzer waveform edges will appear significantly misaligned. Alignment is correct when the logic analyzer triggers the oscilloscope. To get correct data alignment when a DSO4000 Series oscilloscope triggers a TLA logic analyzer: 1. Configure iView(tm) as normal, except connect the Trig In BNC cable (red band) to External Signal In on the TLA. 2. Select the System->System Configuration menu item in the TLA Application. 3. In the External Signal In section (top-left) of the Signals tab, connect the External Signal input In to internal signal 1: 4. Set up the desired trigger on the oscilloscope. 5. In the TLA Application, go to the DPO4000 Series trigger screen and change the Trigger Event to the oscilloscope's trigger. 6. On the same screen, change the scope's Trigger Action to "Trigger TLA Too". You will get a warning message. Select Yes. 7. Go to the Trigger window of the LA module you wish the oscilloscope to trigger. 8. In the PowerTrigger tab, set the trigger to the following: State 1: If Signal 1 Is False then Trigger 9. Run an acquisition. 10. The analog and digital data still will have an offset. Adjust the time offset in the desired data window as needed by selecting the Data->Time Alignment menu item, which activates the Time Alignment dialog: Loading AutoDeskew setups ------------------------- There are several known problems with restoring information into AutoDeskew with a Load System or a Load AutoDeskew Setup operation. After such an operation, be sure to inspect the results in the AutoDeskew Properties dialog box. Detecting transitions in an LA trigger program ---------------------------------------------- The LA modules can be programmed to recognize the transition of an individual channel or a group of channels. For example, "If Channel ABC Goes High then Trigger", or "If Group XYZ Changes then Trigger". Internally, this is done using a transition recognizer which compares values at consecutive sample points. You would expect the output of the transition recognizer to be "false" for the first sample in an acquisition (because there is not a previous sample to compare with). However, for TLA7Lx/Mx/Nx/Px/Qx modules the transition recognizer output is sometimes "true" for the first sample. This means that if your trigger program is "If Channel ABC Goes High then Trigger" you may get a trigger on the first sample even though you would probably not expect it. Workaround: The workaround is to use a state in the trigger program to skip over the first sample, the sample for which the transition recognizer output is unreliable. The modified trigger program would look something like this: State 1: If Anything then Go To State 2 State 2: If Channel ABC Goes High then Trigger For TLA7Axx modules and TLA520x logic analyzers, there is never a transition detected on the first sample in an acquisition - the transition recognizer output is always "false". For trigger programs that test for a channel that "Goes High" or "Goes Low" or test for a transition recognizer that "Occurs" the extra first state in the trigger program is not necessary because the logic analyzer will never trigger on the first sample. However, a trigger program that tests for a channel which "Doesn't go High" or "Doesn't go Low" or tests for a transition recognizer that "Doesn't occur" still needs to use an extra state. For example: State 1: If Anything then Go To State 2 State 2: If Channel ABC Doesn't go High then Trigger Counter/timer readouts in the status monitor -------------------------------------------- This issue applies only to the TLA7Lx/Mx/Nx/Px/Qx modules. Under certain conditions, when a counter/timer is used as a logic analyzer module trigger event, the readout value displayed in the Status Monitor or the About Data tab of a data window property sheet is incorrect even though the logic analyzer triggered correctly. The problem occurs under the following conditions: The target value of the counter is less than 8 (or the target value of the timer is less than 32 ns); the counter/timer is incremented past the target value; and the counter is reset (or the timer is cleared). Workaround: If you need to see the above counter/timer values in the Status Monitor or About Data tab, or if you need to use the target values in the Histogram window or with a TPI application, use a second counter/timer in parallel with the first counter/timer, but do not use it in a trigger event. The readout value of the second counter/timer will be correct. TLA Programmatic Interface (COM-based) -------------------------------------- The TLA Application Software can be driven by either a local user interacting with the graphic user interface (GUI) or by a TPI (TLA Programmatic Interface) client program. In some circumstances, these two uses can conflict with each other. It is the user's responsibility to see that these conflicts do not occur. Generally, there will be no problem. One situation that can cause a problem is if a modal dialog box is open in the GUI at the time that a TPI client program issues a command or sets the value of a property. In order to avoid changing the state of the TLA application while the modal dialog box is open, any TPI command or property setting that would do so, is prohibited. Attempting to issue such a command or set a property value through TPI will return an error value of TLA700_E_MODAL_DIALOG_OPEN to the client program. For a complete list of commands that are disallowed while a modal dialog box is open, see the Version History for TPI version 4.1 in the TPI on-line help. Workaround: Ensure that the TLA application does not have a modal dialog box open when the TPI client program has control of the logic analyzer. TLA Performance Verification (PV) software compatibility with TLA7000 and V5.1 or higher ---------------------------------------------------------------------------------------- In order to control a TLACAL test fixture from a TLA7000 mainframe, you need a USB to RS232 adapter. The Belkin F5U109 has been used successfully by Tektronix, and is Tektronix Part Number 119-6837-00. The TLA Performance Verification software for TLA7Lx/Mx/Nx/Px/Qx and TLA7Dx/Ex modules has not been updated to run on a remote PC controller. If you need to verify one of those modules, you must do so in a TLA7012 or TLA700-series mainframe. Also, the PV software will display a PCI-VXI bridge error when running with TLA Application Software version 5.x, unless you first delete the Visa32.dll file from the C:\Tekcats folder. Then when you see the message "UNABLE TO ENABLE SRQ EVENTS", you can continue by pressing the Enter key twice. TLA520x and Standby mode ------------------------ Placing the TLA520x in Standby mode by selecting Standby from either the (Start > Shutdown) menu or the keyboard supplied with the TLA520x causes the system to remain in Standby mode indefinitely. You must cycle power on the system to bring it back. This will cause loss of any unsaved data or settings. This problem does not occur on TLA7000 series systems. 7) CONTACTING TEKTRONIX ======================== If you have any questions, please contact the Tektronix Technical Support Center: Email: techsupport@tektronix.com Web site: www.tektronix.com Phone: 1-800-833-9200 Option 3 6AM-5PM Pacific Time