TDS/CSA8000 Release Notes Product APplication Software v2.5.0.7 1 INTRODUCTION This document applies to CSA8000, CSA8200, TDS8000, and TDS8200 instruments (collectively referred to as the TDS/CSA8000 Series instruments) configured with Product Software Version 2.5 running under the Windows 2000 Professional operating system. Information provided in this document is relevant to installation and operation of the Product Software, the base Platform Software and Operating System (OS). Product Software is defined as the TDS/CSA8000 Series graphical user interface (GUI) application and embedded firmware, which is used to operate the instrument as an oscilloscope. Platform Software is defined as the necessary additional software that allows the Product Software to run on the instrument and interface with the instrument hardware. The Product Software is typically provided on a CD-ROM entitled, 8000 Series Instruments Product Software and is pre-installed on new instruments received from the factory. The latest version of the Product Software is periodically made available for download from the Internet. Please check the Sampling Oscilloscopes web page at: http://www.tek.com/Measurement/scopes/index/prodindex_sampling.html to determine the availability of Product Software updates and other downloadable software packages. The Operating System is typically provided on a set of two CD-ROM disks entitled 8000 Series Instruments Windows 2000 Operating System Restore. The operating system version supported in this release of the O/S Restore CDs is Windows 2000 Professional. Because of licensing restrictions and the significant size of the O/S Restore CDs, it is not possible to make the contents of the O/S Restore CDs available for download from the Web. New instruments are shipped from the factory with a compatible version of the operating system restore CDs. Operating system restore CDs are available for purchase as part of a Windows 2000 upgrade kit for existing instruments. Please contact your Tektronix representative for Windows 2000 upgrade kit ordering information (contact information is at the end of this document). 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. 2 INSTALLATION 2.1 Minimum System Requirements The minimum system requirements for Product Software v2.5.0.7 are: * 256+ MB of RAM * 6+ GB Hard Drive * 500+ MHz CPU * Radisys SF810 Motherboard with BIOS version 01.03.01 or later * Windows 2000 Professional operating system All TDS8000B, CSA8000B, TDS8200, CSA8200 and newer instruments are known to meet the minimum system requirements. All TDS8000 and CSA8000 instruments will require installation of a hardware upgrade kit. The part number of the hardware upgrade kit for the CSA8000 instruments is CSA8UP opt CPU (with CSA8UP opt *IF for factory installation). The part number of the hardware upgrade kit for the TDS8000 instruments is TDS8UP opt CPU (with TDS8UP opt *IF for factory installation). Please contact your Tektronix representative for ordering information (contact information is at the end of this document). NOTE: Factory installation (opt *IF) is recommended. Installation of the CPU upgrade requires substantial disassembly of the instrument and replacement of the motherboard. 2.2 Installing the Product Software Installing the Product Software requires administrative privileges since the installation routines need to modify settings that apply to all instrument users. The factory installation of the Windows 2000 Professional operating system is configured to automatically log into the "Administrator" account during the boot process. If this behavior has not been modified, then you are ready to install the Product Software. Otherwise, you will need to manually log into the instrument as an administrator. It may be necessary to disable virus scanning software, or other third party software packages, in order to reliably install the Product Software. It is not be necessary to terminate the TDS/CSA8000 Series GUI application in order to install an upgrade to the Product Software. If installation from a LAN is desirable, the contents of the Product Software CD (or the downloaded Web installer) may be copied to a file server. The file setup.exe must be executed manually to proceed with installation over the network. Although the Windows 2000 Professional operating system supports automated application deployment features such as "Systems Management Server", automated deployment of the Product Software has not been tested with this release. We do not anticipate any unique automated deployment issues with this version of the Product Software. This Product Software release has been tested for compatibility with the previous Windows 2000-based product software releases. Outside of those considerations listed above, no other special considerations are known to apply when upgrading the Product Software from previous releases. 2.3 Using the Operating System Restore CD WARNING: Using the Operating System Restore CD destroys any existing files and information that exists on the instruments hard drive. Upgrading an instrument from a previous version of the Product Software running under the Windows 98 operating system to Product Software Version 2.5 will require updating the operating system to Windows 2000 Professional using the Operating System Restore CD provided with Opt W2K. Instruments that have been configured with Windows 2000 Professional from the factory may require an operating system restore if the hard drive becomes corrupted and reinstalling the Product Software does not solve the problem. Backing up information from the hard drive to an external storage location such as a network file server before using the Operating System Restore CD may make it possible to restore important data after the O/S Restore process has completed. The O/S Restore CD provides an interactive menu to facilitate the O/S Restore process. On certain instruments, it may be necessary to attach a PS/2 compatible keyboard to the instrument to operate the O/S Restore menu. In most cases it will be possible to use the USB keyboard provided with your instrument to operate the O/S Restore menu. The following procedure may be used to perform an O/S Restore: 1. Power up the instrument. 2. Insert the TDS/CSA8000 Series Operating System Restore CD into the CD-ROM tray. 3. Select "Shutdown" from the Windows "Start" menu and shut down the instrument. 4. Power up the instrument. 5. If the O/S Restore CD boots, go to step 19 and follow the onscreen instructions. NOTE: If the O/S Restore CD does not boot at step 5, the instrument will boot into Windows from the hard drive. Proceeding with steps 6-13 should boot the instrument from the O/S Restore CD: 6. Select "Shutdown" from the Windows "Start" menu and wait for the instrument to power off. 7. Eject the removable hard drive. 8. Power up the instrument. 9. Select menu option [2] Update motherboard BIOS firmware and CMOS settings. 10. Power down the instrument using the Power button. 11. With the instrument powered off, insert the removable hard drive. 12. Power up the instrument. 13. If the O/S Restore CD boots, go to step 19 and follow the onscreen instructions. If steps 6-13 fail to boot the O/S Restore CD, it may be necessary to attach a PS2 compatible keyboard and modify the BIOS settings. The following procedure may be used to manually modify the BIOS settings to boot the O/S Restore CD: 14. Power up the instrument. 15. Press the F2 key to enter the PhoenixBIOS Setup Utility. 16. Navigate to the Boot page. 17. Modify the Boot Order such that the ATAPI CD-ROM Drive is first in the list. 18. Press the F10 key to save changes and reboot the instrument. 19. The O/S Restore CD should now boot. Follow the onscreen instructions. NOTE: It is very important to invoke the O/S Restore menu options in numerical sequence, as instructed by the O/S Restore menu onscreen instructions. NOTE: The O/S Restore process does not replace the boot sector on the hard drive. The boot sector on working Windows 98 based hard drives is compatible with Windows 2000. If the boot sector ever becomes corrupted or infected with a virus, it may be necessary to reformat the hard drive (or use a DOS utility such as FDISK.EXE /mbr to replace the master boot record) before using the O/S Restore CD NOTE: An updated Touch Screen Device Driver is included with your Product Application Software. It is only needed for users that have a Windows 2000 O/S Restore CD v2.0. Version 2.1 (and later) O/S Restore users have the most recent driver installed by the recovery CD and may disregard this note. This device driver is more recent than the one that is installed in an O/S Restore, and should be installed following an O/S Restore, but prior to installation of the Product Application Software. See section 9 - Updating The Touch Screen Device Driver for details. New TDS/CSA8200 instruments are shipped with the later version of the Touch Screen driver and this driver is restored when using O/S Restore CD v2.1 or later. 3 Benefits of Installing Product Software Release v2.5.0.7 Product Software release v2.5.0.7 has improvements and defect corrections in the following areas: * Support for the 80E07, 80E08, 80E09, and 80E10 High Bandwidth Sampling Modules (new in 2.5.0.6, improved in 2.5.0.7) * New TDR Autoset Mode * Edge & Period Autoset with Internal Clock Trigger Source * New 8.5 Gb/s Fibre Channel Optical Mask * Miscellaneous Improvements and Defect Corrections 3.1 Support for 80E07, 80E08, 80E09, & 80E10 Sampling Modules The 80E07, 80E08, 80E09, and 80E10 sampling modules are supported, including features and capabilities such as: * Dual remote sampling module configuration * Selectable bandwidth * High speed TDR operation (80E08 & 80E10) * Individual channel horizontal skew/delay (deskew and acquisition performance improvement) * Individual channel TDR step deskew (deskew improvement) NOTE: Product Software version 2.5 or later is required with these modules. Using the 80E07, 80E08, 80E09, or 80E10 modules in mainframes with older versions of product application software may cause the application to fail to start. 3.2 New TDR Autoset Mode A new TDR-specific autoset mode or type had been added such that autoset on a TDR capable channel automatically attempts to find and display the first significant reflection (if one can be found). Additional changes include a new TDR-specific autoset mode option to control placement of the TDR step incident edge at the conclusion of a TDR autoset. 3.3 Edge & Period Autoset with Internal Clock Trigger Source Edge and Period autoset now function when the trigger source is set to Internal Clock. For instance, this allows Edge autoset to be used on a signal such as the front panel Internal Clock output (or a rising edge TDR step to a different module input), which can be useful in deskewing multiple channels. Refer to the TDSCSA8000 Quick Start User Manual for further information on skew and deskewing concepts and methods. 3.4 New 8.5 Gb/s Fibre Channel Optical Mask A new 8.5 Gb/s Fibre Channel optical mask had been added per a T11 January 2006 proposal. 3.5 Miscellaneous Improvements and Defect Corrections The following are some of the notable miscellaneous improvements and defect corrections included in this release: * There is now both Coarse & Fine control for both channel Delay and TDR Step Deskew (using the front panel FINE button). * There have been updates to the on-line help system, including corrections to the programmer's Status and Error messages. * There have been updates to several of the product documentation pdf files available on the hard drive (Start->Programs->Tektronix TDSCSA8000->Documents), including a new 80E07-10 Electrical Sampling modules document. * Corrected a problem in which the *OPT? query command indicates that the Gated Trigger Option is installed (even when it is not). * Corrected an intermittent problem where the TDS/CSA8000 scope application might hang (crash) when doing a *OPT? query command. * Corrected an intermittent problem where the 80SJNB Jitter, Noise, and BER Analysis application fails to start up. 4 Known Limitations and Behavioral Changes Although many improvements and fixes were implemented, Product Software Version 2.5.0.7 has known limitations and behavioral changes compared with previous software releases: * Documentation for the CH:DELay command is missing * The VXI Plug & Play Instrument Driver has not been updated * Edge and Period autoset with Internal Clock trigger source searches for rising edge only * The PatternSync Trigger Module might not stay synchronous to the pattern for patterns longer than 215 * The AutoSync function might fail to find the correct parameters on signals with significant overshoot or undershoot * Autoset might change the horizontal scale unexpectedly when the trigger source is Pattern Sync * AutoSync fails to find data rate for rates less than 200Mbps * Conditional stop print action will not occur if the application is minimized * Under certain conditions Phase Reference Characterization may execute slowly * A harmless "parameter error" may be observed after initial installation * Changing the Appearance settings under Windows Display Properties is not recommended * Using the Windows 2000 Professional "Check Disk" feature may crash the instrument under some conditions * Using the OS Recovery CD may result in instruments with duplicate SIDs * PCMCIA (PC Card) devices are no longer supported * NRZ or RZ Autoset without a standard mask requires that the appropriate bit rate be set * Backward compatibility for recalling setup files cannot be guarantee. * Dark level calibration required to produce accurate measurements * Trigger source must be set to internal clock for TDR testing, use TDR preset * Certain math/measurement definitions may not be recalled properly * Adjusting waveform position while stopped does not update the histogram readouts * Known issues with USB-GPIB adapters * Potential problems with recall "setup from last session" or "saved setup" Start-up user preferences * LCD display brightness (gamma) may require adjustment * Scope Only - VGA Output configuration change * No External Prescale Auto Triggers * Cycle Mode Diagnostics can cause boot up failure 4.1 Documentation for the CH:DELay command is missing The CH:DELay command is missing from both the on-line Programmer Guide (accessed from the TDS/CSA8000 scope application Help system) and the TDSCSA8000 Programmer Guide pdf document. This command sets or queries the delay (i.e. time skew), in percentage, for the channel specified. Sending this command is equivalent to setting Delay in the Vertical Setup dialog for the selected channel. The set and query syntax is: CH:DELay CH:DELay? 4.2 The VXI Plug & Play Instrument Driver has not been updated A small number of commands have been modified or added in this release, but the VXI Plug & Play Instrument Driver has not been updated (remains at version 2.7). The commands modified or added are: AUTOSet:TDR:INCident { ON | OFF | 0 | 1 } (new command) AUTOSet:TDR:INCident? (new command) AUTOSet:TYPE TDR (new argument for existing command) HORizontal:BITS:STANdard FC8500D (new argument for existing command) MASK:STANdard FC8500D (new argument for existing command) 4.3 Edge and Period autoset with Internal Clock trigger source searches for rising edge only With the new functionality added for Edge and Period autoset when using Internal Clock as the trigger source, the search algorithm only attempts to find the first rising edge. 4.4 The PatternSync Trigger Module might not stay synchronous to the pattern for patterns longer than 2^15 When using the PatternSync trigger module for pattern lengths greater than 2^15, the module might not stay synchronous with the pattern when changing the Relative Trigger Bit (found in the Pattern Sync dialog). This problem does not occur if you use the 80A06 with the SlotSaver cable plugged into the trigger probe power connector. 4.5 The AutoSync function might fail to find the correct parameters on signals with significant overshoot or undershoot The AutoSync function will automatically find the data rate, pattern length and data to clock ratio for the specified input signal. However, if the signal has too much overshoot or undershoot, the function might not correctly determine all of these parameters. This might occur for an optical signal that is unfiltered. To avoid this problem, use filtering with optical signals when using the AutoSync function. 4.6 Autoset might change the horizontal scale unexpectedly when the trigger source is Pattern Sync When the trigger source is pattern sync and the horizontal Autoset option is disabled (not checked in the Autoset Properties dialog), running an Edge or Period Autoset might cause the horizontal scale to change. 4.7 AutoSync fails to find data rate for rates less than 200Mbps The AutoSync function will fail to find the data rate for any rate lower than 200Mbps. 4.8 Conditional stop print action will not occur ifthe application is minimized. When using conditional acquisition modes, print stop actions (selecting the Print Screen action either to a file or to a printer) will not occur if the application is minimized. Acquisitions will stop at the proper condition but the screen will not be printed. To avoid this problem, do not minimize the application when acquiring in this mode. 4.9 Under certain conditions Phase Reference Characterization may execute slowly Proper operation of Phase Reference Characterization in Triggered mode requires that a stable trigger be available during the entire characterization process. Under conditions where there are intermittent triggers, the characterization process may take several minutes to complete. This situation could occur, for example if the trigger input was mistakenly not connected and there is enough noise on the input to cause occasional triggers. If there are no triggers at all, the characterization process will abort after a short period of time. To avoid the problem described here, ensure that a stable trigger is available prior to initiating a Phase Reference Characterization in Triggered mode. 4.10 A harmless "parameter error" may be observed after initial installation With the introduction of the "recall setup from last session" feature, it was necessary to deploy an initial factory setup file to be recalled upon the first boot after installation. This factory setup file was prepared on an instrument with no modules installed. This setup is completely compatible with all possible module configurations, except for module configurations that include clock recovery hardware. The first time an instrument with clock recovery hardware is booted, a harmless "parameter error" may be observed. This error may be safely ignored and should not be observed on subsequent boot cycles. Similar parameter errors may be observed when the module configuration changes (modules added, removed, replaced with different module types) and are typically innocuous. When this error is observed, the associated parameter assumes the default value. 4.11 Changing Appearance settings under Windows Display Properties is not recommended Modifying Windows Appearance settings is strongly discouraged as there are many combinations of Appearance settings that are incompatible with the TDS/CSA8000 GUI application. The only Appearance scheme that is compatible with the TDS/CSA8000 GUI application is the "Windows Classic" scheme. If the "Windows Standard" scheme is selected, the background color of certain icons will contrast with the background color of the TDS/CSA8000 GUI application dialogs and a border will appear around those icons. If schemes other than "Windows Classic" are selected, it is possible that certain menus and dialogs will not be rendered properly (for example, the Help option on the main menu may be occluded). 4.12 Using the Windows 2000 Professional "Check Disk" feature may crash the instrument under some conditions Selecting the "Automatically fix file system errors" checkbox on the Check Disk dialog may result in a Windows crash upon the first reboot following the conclusion of the Check Disk operation. This crash does not affect the instrument and a subsequent reboot will execute normally. 4.13 Using the OS Recovery CD may result in instruments with duplicate SIDs With the introduction of Windows 2000 Professional to the Platform Software, the procedures needed to produce OS Recovery CDs have introduced a problem with duplicate SIDs (Security Identifiers). During the Windows 2000 Professional installation process, a unique SID is generated and recorded on the hard drive. When the hard drive is "cloned" to produce the OS Recovery CD, the SID is cloned along with the other contents of the hard drive resulting in the potential for instruments to have duplicate SIDs. NT Domain accounts are assigned SIDs by the NT Domain controller and are guaranteed to be unique within the domain. For this reason and many others, it is highly advisable to avoid using local machine accounts and peer-to-peer Workgroup networking in a secure network environment. It is worthwhile to note that "Workgroup" networking has been around since Windows 3.11 and was designed for convenience at the sacrifice of network security. There are numerous security risks with Workgroup networking, in addition to the duplicate SID concerns. The consequences of duplicate SIDs are limited to local machine accounts and peer-to-peer "Workgroup" networking topologies and do not impact "NT Domain" style network security. Because SIDs associated with local machine accounts are derived from the instrument's SID, it is possible to have local machine accounts on multiple instruments with duplicate SIDs. Local machine accounts with duplicate SIDs are able to obtain free access to each others resources. This problem is well known in the Windows NT Systems Administration field and is documented in several Microsoft resources, including Microsoft Knowledge Base Article 162001. There are numerous solutions to this problem including third party utilities that generate unique SIDs. Operating with duplicate SIDs and avoiding Workgroup networking is one possible solution, using a third party tool to generate a unique SIDs is another possible solution and using the Microsoft sysprep tool may be an option for advanced administrators. 4.14 PCMCIA (PC Card) devices are no longer supported Because of an incompatibility between the third party PCMCIA device driver and the Windows 2000 Professional operating system, PCMCIA slots are no longer supported. New instruments received from the factory will not have PCMCIA hardware. Instruments upgraded from Windows 98 to Windows 2000 Professional may have PCMCIA hardware, but the PCMCIA slots will not be functional under Windows 2000 Professional. Alternative expansion technologies such as USB and Ethernet are recommended. 4.15 NRZ or RZ Autoset without a standard mask requires that the appropriate bit rate be set Performing an NRZ or RZ Autoset without a standard mask requires that the appropriate bit rate be set before initiating the Autoset. This can be done via the UI from the Horizontal setup dialog by setting the Bit Rate field. Alternatively, you can set the bit rate via the programmer interface with the command: HORizontal:BITS:BITRate . Additionally, you must specify the signal type for Autoset. This can be done by selecting the type of signal: Under "Utilities" menu, and then selecting "Define Autoset". The signal type can also be selected via the programmer interface by using the ":AUTOSet:TYPE command. 4.16 Backward compatibility for recalling setup files While backward compatibility for recalling setup files from previous releases is desirable, it cannot be guaranteed due to the number of system parameters and constraints. Setup files from previous releases should be verified, and, if the results are not desirable, then a new setup file should be generated. 4.17 Dark level calibration required to produce accurate measurements A Dark Level Calibration should be performed on optical channels before obtaining measurement results. In particular, Extinction Ratio requires this calibration for meaningful results. Additionally, the Extinction Ratio measurement is no longer supported on electrical channels. 4.18 Trigger source must be set to Internal Clock for TDR testing This release requires that, for TDR testing, the trigger source must be set to the Internal Clock. The trigger source is not coerced to Internal Clock when TDR Step generators are manually turned on (see the TDR setup menu). Tektronix recommends using TDR Preset when setting up TDR. TDR Preset not only sets the trigger source to Internal Clock, it also turns on the TDR step generator and acquisition hardware for the selected channel, and scales and positions the signal so that the incident edge of the TDR pulse is visible on screen. The recommended process follows: 1. Connect the channels to be used (the instrument supports TDR on up to eight channels simultaneously) to the Device-Under-Test. 2. Press the TDR Preset button in the TDR setup menu for each channel used. 3. Following any TDR preset, you can specify step polarity and display units for each TDR channel as desired. 4.19 Certain math/measurement definitions may not be recalled properly This release may require that you rebuild certain Math waveform and measurement definitions, rather than just save and recall them. For example, this instrument allows you to define such sophisticated math waveform and automatic measurements as follows: Example 1: MATH1 = AVERAGE(C1-MEAS1) ;where MEAS1 = MEAN(R1) Example 2: MEAS1 = AVERAGE(M1) While this flexibility makes for very powerful math and measurement systems, it also complicates the saving and restoring of the instrument state when using either Save and Recall Setups or the *LRN? GPIB command. For our math waveform example above (Example 1), it is critical to restore the MEAS1 definition prior to restoring the MATH1 definition. However, for our automatic measurement above (Example 2), it is critical to restore the math definition prior to the measurement definition. This release of the Product Software does not attempt to rationalize the order in which it restores instrument settings using a Recall Setup operation or *LRN? command. As a result, it may be necessary to rebuild definitions such as those just discussed rather than just saving and recalling them. 4.20 Adjusting waveform position while stopped does not update the histogram readouts When the instrument is in a stopped state, changing the waveform position will not update the histogram readouts. 4.21 Known issues with USB-GPIB adapters The 8000 and 8000B series instruments do support the National Instruments USB-GPIB controller (the newer USB-GPIB-A version is not supported) If you desire to use this controller, please note the following: 1. The USB-GPIB controller receives power from the USB connection and therefore must be connected either directly to the USB port of the TDS/CSA8000 or to a powered USB hub. 2. Due to resource conflicts, it is critical that you not install the USB-GPIB driver that comes with this controller. Installing this driver may disable your instrument GPIB port. 3. In order to communicate with the USB-GPIB controller, you should install the latest NI VISA driver. 4.22 Potential problems with recall "setup from last session" or "saved setup" Start-up user preferences If the Start-up user preference is configured to recall "setup from last session" or "saved setup" on power-up and for any reason the instrument software hangs during power-up, it is possible the setup file that the instrument is attempting to recall is corrupted. If rebooting the instrument does not resolve the problem, remove the following file or remove the file specified in the "saved setup" text box: "C:\Program Files\TDSCSA8000\Setups\Current.stp". If the Start-up user preference is configured to recall "setup from last session", the File Name error displayed in the Error Message dialog may be safely ignored. Subsequent reboots should not produce this error. If the Start-up user preference is configured to recall "saved setup", save a new setup to the location specified in the "saved setup" text box. Subsequent reboots should not produce a File Name error. 4.23 LCD display brightness (gamma) may require adjustment Earlier versions of TDS/CSA8000 oscilloscopes used an LCD display that was not as bright as the display shipping with new instruments. The display driver included with Platform Software Version 1.2 has default values optimized for the new LCD display. If you have an older LCD display, you may increase the brightness by using the following procedure: 1. Minimize or exit the TDS/CSA8000 GUI application. 2. Use a mouse to right click on the Windows desktop and select Properties. 3. Select the Settings page of the Display Properties dialog. 4. Under Display: select "Default Monitor on Chips and Technologies (Asiliant) 69000" 5. Click the Advanced button on the settings page of the Display Properties dialog. 6. Select the Color page of the Advanced settings dialog. 7. Click the Restore Defaults button. 8. Drag the Brightness slider bar to the desired brightness value 4.24 Scope Only - VGA Output configuration change Configuring your instrument to replicate the scope display on an external monitor (as opposed to extending the Windows desktop to a second monitor) is somewhat more involved in Windows 2000 than under Windows 98. To set up your display to replicate the scope on an external monitor use the following steps: 1. Plug an external monitor into the SCOPE ONLY VGA OUT port on the back of your instrument. 2. Go into the Control Panel->Display menu and select the Settings tab. 3. In the white display box select "#2 Default Monitor on Chips and Technologies(Asiliant) 69000". 4. Select the Advanced button at the bottom of the screen. 5. Select the CHIPS tab at the top of the screen. 6. In the Display Device box, select the Both radio button. 7. Select OK at the bottom of the screen twice and close the control panel. 8. The display should now be replicated on the external monitor. 4.25 No External Prescale Auto Triggers Due to an internal architecture change, Auto trigger mode is disabled when External Prescale is selected as the trigger input. 4.26 Cycle Mode Diagnostics can cause boot up failure Setting the User Preferences -> Power Up Diagnostics to "Cycle mode" can cause the Product Software to fail to start on a subsequent boot up. This mode is useful only for manufacturing purposes and end-users should not select this mode and then reboot. Similarly, the "Loop" checkbox that appears on the Diagnostics dialog should not be used - for the same reasons. Access to this setting will be removed in the next release. If you have selected this "Loop" or "Cycle mode" diagnostics setting, and your instrument does not successfully initialize after a reboot, please contact Tektronix Technical Support (contact information at the end of this document) and they will assist you in correcting the problem. 5 Programmatic Interface (PI) Specific Limitations The Programmatic Interface (PI) of this release of the Product Software has the following limitations: * EAV bit is not supported, use MAV bit instead. * Caution required when controlling instrument from front panel and PI simultaneously. * Command sequencing required when specifying user masks. * Horizontal position and scale queries always return time units. * SYNC:TIMEOUT value may need to be adjusted. * The instrument software may hang if GPIB commands are received before the boot process has completed. 5.1 EAV bit is not supported, use MAV bit instead This release supports the MAV (message available) bit. It no longer supports the EAV (event available) bit. 5.2 Caution required when controlling instrument from front panel and GPIB simultaneously This release requires that you take a precaution when controlling the instrument from the GPIB and the front panel and/or graphical user interface simultaneously. Before attempting GPIB control of the instrument, make sure you do not have any dialog on screen that requires confirmation. In such a case, a GPIB timeout will occur as the instrument application will not acknowledge any other control activities until the user has responded to its confirmation request. 5.3 Command sequencing required when specifying user masks This release requires that, when you are defining a user mask over GPIB, you first send the MASK:STANdard USERMask command. After sending this command, you may specify the polygons with the MASK:MASK commands. 5.4 Horizontal position and scale queries always return time units All programming commands and queries for horizontal position and scale use time units. Bit and distance units are not supported in this release. 5.5 SYNC:TIMEOUT value may need to be adjusted Releases 1.3 and later include a mechanism to prevent a response to certain data value queries before the query is ready to provide a value consistent with the instrument state. The SYNC:TIMEOUT command sets or queries the default synchronization timeout for commands that rely upon data production by the instrument. The default timeout value of 3 seconds should be appropriate for most applications, but the user may need to adjust this timeout under certain conditions: * Slow waveform acquisition rate: When a related query is issued to the instrument, if the combination of record length, averaging, frame-scan, trigger hold-off, and trigger source repetitive rate result in a waveform acquisition rate which is slow compared to the synchronization timeout, the synchronization timeout may expire before results are produced by the instrument. * Unforeseen user configurations: Any configuration that significantly influences the rate at which the instrument produces results could potentially result in a timeout. This could include installation of third party software that consumes a significant amount of CPU cycles or system resources. 5.6 The instrument software may hang if GPIB commands are received before the boot process has completed When the instrument is booting after a power cycle or reboot operation, it is necessary to wait until the instrument has completed booting before sending GPIB commands. An indicator that the instrument has completed the boot process is the appearance of the Diagnostics results dialog. NOTE: The Diagnostics results dialog must be dismissed in order for the instrument to process GPIB commands. In the absence of a diagnostics failure, this occurs automatically in 2-3 seconds. 6 Performance Enhancement Tips While the TDS/CSA8000 Series instruments provide the highest acquisition rates of any ultra-high performance oscilloscope available today, observing the following recommendations can enhance this performance: * For the highest data acquisition rate, set the Record Length to its maximum value, using the RESOLUTION knob on the front panel. * Turn off all measurements until after you have completed data acquisition into the Waveform Database. * While Cursors can be used for approximate measurements, use the automated measurements for the most accurate measurement results. * For the best measurement results on signals with relatively fast transition times, increase the waveform record length beyond the default 500 points (use the RESOLUTION knob on the front panel). This will increase the number of points acquired on any rising or falling edge. * Enabling statistics (or to a lesser extent, annotations) for measurements on a vector trace may reduce Waveform Database accumulation rates. 7 GPIB Programming Tips The TDS/CSA8000 Series instruments use a pipelined architecture for data acquisition, control and query commands. As a result, care must be exercised to ensure that the results returned from data or measurement queries are those that were expected. A number of methods exist to flush the acquisition and control queues in these instruments and thereby ensure the expected results. A few of these are listed as programming tips below: * Be sure to set up the instrument to Stop After Acquisitions = 1 if you need to guarantee that you have acquired a new waveform. You do this using the following sequence of commands: ACQuire:STOPAfter:CONDition ACQWfms ACQuire:STOPAfter:COUNt 1 * Be sure to wait until the acquisition is complete by using any of the synchronization commands (*OPC, *OPC? *WAI, and BUSY?). The above actions are required because the amount of time required to acquire a complete waveform depends on a variety of factors: the periodic rate of the trigger signal; the specified record length; whether averaging and/or FrameScan acquisition is turned on (and, if so, how many acquisitions must be averaged); the requested Trigger Holdoff; and so on. In addition: * Be sure to include at least 100 ms of delay in the loop that queries instrument status when synchronizing your test procedure to the instrument (using a BUSY? Query, for example). If you do not set sufficient time between status queries, the instrument will have very little time to acquire waveforms and process data. * Be sure to wait for the time listed below after sending each of the following commands before querying for any results that depend on the command sent: CH:FILTer:VALue 6 seconds CH:BANdwidth:VALue 6 seconds SAVe:WAVEform 3 seconds 8 Analysis and Connectivity Software Several optional software components are available to support control and data transfer between the instrument and numerous software- development and data-analysis tools. 8.1 Overview The Analysis and Connectivity software provided with this instrument may be used to: * Gather instrument data (waveforms, measurements) and export it to familiar, off-the-shelf analysis tools, such as Microsoft Excel, MathWorks' MatLab and MathSoft's MathCad. * Interface with numerous software development environments, such as Microsoft's Visual C++ and Visual Basic, National Instruments' LabVIEW and LabWindows, along with many other Microsoft-Windows-compatible development tools. The following software components are available with this release: * VXI Plug-and-Play Instrument Driver v2.7 * TekVISA v2.03 * TekVISA ActiveX Control (TVC) * TekVISA Excel Toolbar * VXI 11.2 LAN Server 8.2 Updates Analysis and Connectivity Software updates are periodically available for this product at: http://www.tek.com/Measurement/scopes/index/prodindex_sampling.html Information on sampling instruments is available by navigating to the Oscilloscope->Sampling Oscilloscopes page. Additionally, the web site will periodically be updated with demonstration and example applications to enhance the instrument functionality. Because Sampling Oscilloscopes are significantly different in architecture than other types of oscilloscopes, the most recent release of the Analysis and Connectivity Software may not be correct for your instrument. Please only download and install updates for the Analysis and Connectivity Software that reference the TDS/CSA8000 Series instruments specifically. 8.3 Instrument Installation Analysis and Connectivity Software is pre-installed on the TDS/CSA8000 Series instruments and is included in this release of the Product Software By default, the Analysis and Connectivity Software is automatically installed when installing the product software from the Product Software CD. The Product Software CD also provides for installing the Analysis and Connectivity Software on any personal computer running Microsoft Windows (see PC Installation below). Installing the Analysis and Connectivity Software will add a TekVISA folder and a Vxipnp folder to the Start->Programs Menu. In the TekVISA folder, you will find the following items that provide additional information: * Release Notes * TekVISA ActiveX Control API * TekVISA Configuration * TekVISA Programming Manual * TekVISA Quick Reference Card * VXI-11 Server Control To install the VXI PnP Driver: 1. Open a Windows Explorer and open folder: C:\Program Files\Tektronix\VXIPNPInstall 2. Double-click on setup.exe in this folder and it will install the VXI PnP driver. After installation, a Vxipnp folder will be created for you. In the Vxipnp folder, you will find the following items that provide additional information: * tktds8k PDF Function Reference * tktds8k Help * Uninstall tktds8k Instrument Driver 8.4 PC Installation You may install TekVISA and the VXI PnP driver on a PC running Windows 98, Windows NT 4.0, Windows 2000, and Windows XP. To install: 1. Insert the product-software CD into your PC and open a Windows Explorer to your CD-ROM drive. You will see several top-level folders and you will use the TekVISA and VxiPnp folders. 2. To install TekVISA, run the TekVISA\Setup.exe program. 3. To install VXI PnP driver, run the VxiPnp\setup.exe program. Once these have been installed, your PC will have Start->Programs- >TekVISA and Start->Programs->VXIPNP folders as described above (the VXI-11 Server Control is instrument specific and will not appear on the PC). 8.5 Excel Toolbar The Toolbar was developed using Excel 2000 and runs under Office 2000. The testing under Office XP has been very limited. The Toolbar does not run under Excel '97. Again, please check for updates: http://www.tek.com/Measurement/scopes/index/prodindex_sampling.html 9 Updating the Touch Screen Device Driver for v2.0 O/S Restore Users The LCD Touch Screen device driver originally shipped with the TDS/CSA8000 series instruments has been updated to version 3.08.16P. This update provides improved performance with other USB devices, and resolves an issue related to the touch screen driver that can make the instrument appear unresponsive to user inputs for short periods of time - especially during heavy use of the touch screen. Tektronix recommends that you update the driver if you have experienced these problems. Because this update post-dates the v2.0 O/S Restore, you will need to re-install the v3.08.16P driver following an O/S Restore operation on an 8000/8000B/8200 Series instrument if you have v2.0 O/S Restore CD-ROM's. If you have v2.1 O/S Restore or later, it comes with the newest driver pre- installed and you may disregard this section. To update your touch screen device driver, please use the following steps: 1. Power up your instrument, and allow it to complete its power- on diagnostics cycle. Wait for the "Diagnostics" dialog to clear before continuing. (If you have just completed an O/S Restore, disregard this step and proceed to step 3). 2. Close the Product Application Software by selecting File->Exit from the menu. 3. Open the Windows Control Panel by selecting the Start button, then Settings->Control Panel. 4. Open the Add/Remove Programs applet by double-clicking on its icon. 5. Scroll down the list of installed applications until you locate the "Universal Pointer Device Driver" entry. Highlight this entry by clicking on it once. 6. When the entry is highlighted, the Change/Remove button will appear, click this button to begin the removal process for the old device driver. 7. The "Uninstall UPDD" dialog will appear, click the "Next" button to proceed. 8. As the uninstall progresses, you may see a "New Hardware Device Found" message, this is normal and may be disregarded. 9. When the "Uninstall Complete" dialog appears, click the OK button to finish the process. If you see a message from Windows asking to reboot the instrument, click "Yes" to allow it to do so. If the instrument is rebooted, wait for the Diagnostics dialog to clear before continuing to the next step. 10. Close the Add/Remove Programs applet, and then close the Control Panel dialog. 11. Use the Start button -> Programs selection to open the list of application shortcut groups. Verify that the "Touch Screen Utilities" group is NOT present in this list. If the group does appear, simply right-click on it and then select "delete" to remove the program group. 12. Insert the product application software CD, and allow it to load and present the "autorun menu" screen. 13. Select the "Browse CD-ROM" menu item to open a Windows Explorer window for the CD-ROM drive. 14. Locate the \UPDD_3_8_16P folder and open it with a double- click. 15. Double-click on SETUP.EXE to begin the Touch Screen Device Driver installation process. 16. The "Welcome" dialog should appear, click the "Next" button to continue 17. Accept the terms of the License Agreement and continue the installation on the next dialog by clicking the "Accept" button. 18. In the Select Folder box, enter "Touch Screen Utilities" instead of the default "UPDD". Click the "next" button to continue. 19. In the Select Destination Directory dialog, accept the default c:\Program Files\UPDD directory by clicking "Next" to continue. 20. In the Install System Tray Icons dialog, select the "Don't place items in system tray" option and then click "Next" to continue. 21. In the "Number of Devices" dialog, accept the default value of "1" by clicking "Next" to continue. 22. In the "Define Device #1" dialog, accept the "Whole Desktop" and "Device 1" default values by clicking "Next" to continue. 23. In the "Device" dialog, select the "3M Touch Systems, SC4, USB" entry at the bottom of the list and then click "Next" to continue. 24. That concludes the configuration portion of the installation wizard. Now, in the "Ready to Install" dialog, click the "Next" button to continue. 25. The installation will now proceed, it will conclude with an "Install Successful" dialog, when this appears, click the "Finish" button to conclude the installation wizard. 26. The UPDD Installer may then display a "UPDD Install" dialog asking that the instrument be rebooted. Although an error message may be described here ("Windows Failed to dynamically load the device"), this is normal and may be disregarded. Click the "Yes" button to start the shutdown/reboot sequence on your instrument. 27. At this point, there may be a request from Windows to reboot the instrument. Regardless of whether or not a message is present, reboot the instrument at this time. As before, allow it to load the Product Application Software to the point where the "Diagnostics" dialog is dismissed. 28. Minimize the Product Application Software window, and check for any Windows Messages that may be present after the reboot. IF there is a message describing newly detected devices that need the instrument to be rebooted, click the "Yes" button and re-boot once again. Again allow the instrument to load its software up until the point where the "Diagnostics" dialog is dismissed. 29. Finally, you will need to calibrate the display. To do this, select Start->Programs->Touch Screen Utilities->Calibrate to load the Screen Calibration Utility. Carefully follow the onscreen instructions to tap each crosshair target. If the screen is dismissed before you have tapped BOTH targets, then you need to run the Calibration utility again. This occurs when the screen driver interprets your action as a double-tap. The calibration is successful if you tapped two targets, one in the upper left and the other in the lower right of the display. 10 Approved Microsoft Windows 2000 Professional Updates Tektronix carefully monitors the latest service packs and patches from Microsoft for the Windows Operating System used on this product. These frequent releases from Microsoft are evaluated for applicability by our Software Engineering team on an on-going basis. Where appropriate, Microsoft OS updates are tested with the instrument software and once determined compatible, are included in planned software updates, usually available on our web site at http://www.tektronix.com In situations where Microsoft releases a critical security patch applicable to this instrument, Tektronix performs accelerated review and testing. The Tektronix Technical Support Center has a list of tested patches and the patches must be downloaded from the Microsoft web site. In situations where a Microsoft patch causes a change to the instrument software, the updated instrument software would be made available via the Tektronix web site. Customers that download and install service packs and patches that have not been tested by Tektronix do so at their own risk. If an update does adversely impact the instrument, customers can: (1) call the Tektronix Technical Support Center and ask for help in recovering, or (2) use the supplied operating system, product software and any application software that came with your instrument to return the instrument to its factory-delivered condition. The following updates have been tested and approved for use with Windows 2000-based Product Application Software v2.3.0.8, v2.4.0.4, v2.4.0.5, 2.5.0.6, and 2.5.0.7 and the 80SJNB application v1.0 on TDS/CSA8000, TDS/CSA8000B and TCS/CSA8200 Instruments: New updates in this release: * Security Update for Windows 2000 (KB896423) * Security Update for Windows 2000 (KB913580) * Windows Malicious Software Removal Tool - May 2006 (KB890830) * Security Update for Windows 2000 (KB908531) * Cumulative Security Update for Outlook Express 6 Service Pack 1 (KB911567) * Security Update for Microsoft Data Access Components 2.5 Service Pack 3 (KB911562) * Cumulative Security Update for Internet Explorer 6 Service Pack 1 (KB912812) * Security Update for Windows Media Player 9 (KB911565) * Security Update for Windows Media Player Plug-in (KB911564) * Security Update for Windows 2000 (KB908519) * Security Update for Windows 2000 (KB912919) * Security Update for Windows 2000 (KB908523) * Security Update for Windows 2000 (KB896424) * Update for Windows 2000 (KB904368) * Security Update for Internet Explorer 6 Service Pack 1 for Windows 2000 (KB905495) * Security Update for Windows 2000 (KB900725) * Security Update for Windows 2000 (KB905749) * Security Update for Windows 2000 (KB905414) * Security Update for Windows 2000 (KB899589) * Security Update for Windows 2000 (KB901017) * Security Update for DirectX 9 for Windows 2000 * Security Update for Windows 2000 (KB893756) * Security Update for Windows 2000 (KB899587) Updates from previous releases: * Windows 2000 Windows Malicious Software Removal Tool - November 2005 (KB890830) * Windows 2000 Security Update for Windows 2000 (KB896424) * Windows 2000 Update for Windows 2000 (KB904368) * Windows 2000 Security Update for Windows 2000 (KB902400) * Windows 2000 Security Update for Internet Explorer 6 Service Pack 1 for Windows 2000 (KB905495) * Windows 2000 Security Update for Windows 2000 (KB905749) * Windows 2000 Security Update for Windows 2000 (KB900725) * Windows 2000 Cumulative Security Update for Internet Explorer 6 Service Pack 1 (KB896688) * Windows 2000 Security Update for DirectX 9 for Windows 2000 (KB904706) * Windows 2000 Security Update for Windows 2000 (KB901017) * Windows 2000 Security Update for Windows 2000 (KB899589) * Windows 2000 Security Update for Windows 2000 (KB905414) * Windows 2000 Security Update for Windows 2000 (KB896423) * Windows 2000 Security Update for Windows 2000 (KB899587) * Windows 2000 Security Update for Windows 2000 (KB893756) * Windows 2000 family Update Rollup 1 for Windows 2000 Service Pack 4 (KB891861) * Windows 2000 family Security Update for JView Profiler (KB903235) * Windows 2000 family Windows Malicious Software Removal Tool - July 2005 (KB890830) * Windows 2000 family Security Update for Windows 2000 (KB901214) * Windows 2000 family Windows Genuine Advantage Validation Tool (KB892130) * Windows Microsoft Windows Installer 3.1 * Windows Security Update for Windows 2000 (KB894320) * Windows Security Update for Windows 2000 (KB896358) * Windows Security Update for Windows 2000 (KB890046) * Windows Security Update for Windows 2000 (KB896422) * Windows Security Update for Windows 2000 (KB893066) * Windows Cumulative Security Update for Internet Explorer 6 Service Pack 1 (KB883939) * Windows Cumulative Security Update for Outlook Express 6 Service Pack 1 (KB897715) * Windows Update for Background Intelligent Transfer Service (BITS) 2.0 and WinHTTP 5.1 (KB842773) * Windows Microsoft Windows Installer 3.1 * Windows Security Update for Windows 2000 (KB890859) * Windows Security Update for Windows 2000 (KB892944) * Windows Security Update for Windows 2000 (KB893086) * Windows Security Update for Windows 2000 (KB893066) * Windows Cumulative Security Update for Internet Explorer 6 Service Pack 1 (KB890923) * Windows Security Update for Windows Media Player 9 Series (KB885492) * Windows Security Update for Microsoft .NET Framework, Version 1.1 Service Pack 1 (KB886903) * Windows Security Update for Windows 2000 (KB873333) * Windows Security Update for Windows 2000 (KB888113) * Windows Security Update for Windows 2000 (KB885250) * Windows Security Update for Windows 2000 (KB891781) * Windows Cumulative Security Update for Internet Explorer 6 Service Pack 1 (KB867282) * Windows Security Update for Microsoft Data Access Components (KB832483) * Windows Security Update for Windows 2000 (KB871250) * Windows Security Update for Windows 2000 (KB891711) * Windows Security Update for Windows 2000 (KB890175) * Windows Security Update for Windows 2000 (KB885835) * Windows Security Update for Windows 2000 (KB885836) * Windows Security Update for Windows 2000 (KB873339) * Windows Cumulative Security Update for Internet Explorer 6 Service Pack 1 (KB889293) * Windows Microsoft .NET Framework 1.1 Service Pack 1 * Windows Security Update for Windows 2000 (KB824151) * Windows Security Update for Windows 2000 (KB841533) * Windows Security Update for Windows 2000 (KB840987) * Windows Security Update for Windows 2000 (KB841356) * Windows Microsoft GDI+ Detection Tool (KB873374) * Windows Security Update for Internet Explorer 6 Service Pack 1 (KB833989) * Windows Cumulative Security Update for Internet Explorer 6 Service Pack 1 (KB834707) * Windows Cumulative Security Update for Internet Explorer 6 Service Pack 1 (KB867801) * Windows Security Update for Windows 2000 (KB839645) * Windows Security Update for DirectX 9.0 (KB839643) * Windows Security Update for Windows 2000 (KB841872) * Windows Security Update for Windows 2000 (KB841873) * Windows Security Update for Windows 2000 (KB842526) * Windows Security Update for Windows 2000 (KB840315) * Windows Critical Update for ADODB.stream (KB870669) * Windows Cumulative Security Update for Outlook Express 6 SP1 (KB823353) * Windows DirectX 9.0b End-User Runtime * Windows Root Certificates Update * Windows Microsoft .NET Framework version 1.1 * Windows Recommended Update for Windows 2000 (822831) * Windows Update for Windows 2000 (KB820888) * Windows Update for Windows Media Player 9 Series (KB837272) * Windows 818043: Recommended Update for Windows 2000 * Windows Critical Update for Internet Explorer 6 Service Pack 1 (KB831167) * Windows 814078: Security Update (Microsoft Jscript version 5.6, Windows 2000, Windows XP) * Windows 816093: Security Update Microsoft Virtual Machine (Microsoft VM) * Windows Flaw In Windows Media Player May Allow Media Library Access (819639) * Windows 823559: Security Update for Microsoft Windows * Windows Security Update for Windows 2000 (KB823182) * Windows Security Update for Microsoft Windows (KB824105) * Windows Security Update for Microsoft Windows 2000 (KB826232) * Windows Security Update for Microsoft Windows 2000 (KB825119) * Windows Security Update for Microsoft Windows 2000 (KB828035) * Windows Security Update for Microsoft Windows (KB828749) * Windows Security Update for Microsoft Data Access Components (KB832483) * Windows Security Update for Windows 2000 (KB835732) * Windows Security Update for Windows 2000 (KB828741) * Windows Security Update for Windows 2000 (KB837001) * Windows Critical Update for Windows Media Player Script Commands (KB828026) * Windows Cumulative Security Update for Internet Explorer 6 Service Pack 1 (KB832894) * Windows Cumulative Security Update for Outlook Express 6 Service Pack 1 (KB837009) * Windows 2000 Service Pack 4 Express Install for End Users * Windows Q324380: Security Update (Windows 2000) * Windows Q326886: Security Update * Windows Q326830: Security Update (Windows 2000) * Windows Q323172: Security Update * Windows Q324096: Security Update (Windows 2000) * Windows Q329834: Security Update (Windows 2000) * Windows Q329115: Security Update (Windows 2000) * Windows Q327696: Internet Information Services Security Roll-up Package * Windows Microsoft Internet Explorer 6 Service Pack 1 (Windows 2000) Microsoft releases numerous such updates to the Windows 2000 operating system and related components on a continuous basis. Refer to the Sampling Oscilloscopes web pages at: http://www.tek.com/Measurement/scopes/index/prodindex_sampling.html for up-to-date information regarding which updates and service packs have been tested with and approved for use on your instrument. Due to licensing restrictions, these updates ARE NOT included in the Product Software installation, and must be downloaded directly from Microsoft. Use the Windows Update feature in the Start menu to access these updates. 11 Sample Programs These sample programs illustrate methods you can use to control the instrument from the GPIB interface. Within the product-software CD, you will find the program listings for these examples, which were written in Visual C++, version 6.0, and generated using the AppWizard program. Note: These sample programs do not use TekVISA. Samples that use TekVISA are found in directory: C:\VXIpnp\WinNT\TekVISA\VISASamples. Note: These programs do not run from within your instrument. These sample programs assume a physical GPIB connection between an external controller and the instrument. Although capabilities have been introduced to allow the instrument to operate as a controller, "loop-back" operation is not supported by physical GPIB. The TekVISA samples provide examples of applications that are capable of running within the instrument. The programs are located in a self-extracting zipped file on the CD- ROM in a folder called Samples\NI488.2 Samples (for example, if your CD-ROM drive designation is E:, then the file is located in E:\Samples\NI488.2 Samples). To extract this zipped file, simply double click on the Samples.exe file within the Samples folder. The programs will be extracted to C:\Samples by default. After unzipping this directory, you will find the source code for each example is in the Sources folder, and the programs are under a Programs folder. All the example programs assume that: * The instrument is set as DEV1 with address of 1, and the PC (controller) set as GPIB0 * A valid signal is connected to the instrument. To reassign the name of your instrument, you can use the Control Panel->System->Network Identification->Properties button (NOT Network ID) or you can enter your current device name into the Edit box within each program. This is true except for the Mask example, where the board address is 0 and it is hard coded. Four of the sample programs use any variety of Electrical Sampling module except for the following: * Mask example uses an Optical Sampling module, preferably the 80C01-CR. * TDR example requires an 80E04 Electric module. Will not work with the 80E08 or 80E10 without code modifications. The example software includes: * Meas: Performs timing or an amplitude measurement on the selected waveform and displays the measurement. * WfmTransfer: Transfer out the selected waveform's horizontal timebase and its vertical scale into a file on your PC (controller). * Capture: Captures the screen into a selected file, or a printer. Note: The saved file will be on your instrument. Please make sure that you have a default printer selected before running this program. * TDR: Displays the attached cable length in centimeters. Note: Requires an 80E04 sampling module. * Mask: Makes an eye pattern evaluation against a mask; counts mask hits, and executes an action. Note: The saved file will be on your instrument. Please make sure that you have a default printer selected before running this program. 12 Contacting Tektronix Orders And Quotes Contact for the United States The USA Customer Support Center is open to help you place orders and request quotes, Monday through Friday, 5 AM to 5 PM Pacific Standard Time (PST). Phone: (800) 833-9200 Option 1 Note: U.S. Government agencies should contact (800) 682-1210 An on-line form is available for requesting quotes on the Tektronix website www.tektronix.com. Navigate to the Buy area using the navigation bar on the www.tektronix.com homepage and select Request a Quote. Service Center Contact for the United States You can depend on Tektronix Support for your service needs. Our "Enable First" business practices eliminate fine print, exclusions, surprises or delay, ensuring you the most credible, reliable, risk mitigation commitment in the industry. Phone: (800) 833-9200 Option 2 Fax: (503) 627-6260 E-mail: meas-svc-rmarequest@tektronix.com Web: www.tektronix.com/support Technical Support Contact for the United States Highly qualified and experienced Technical Support Specialists are available to assist you in these areas: Applications, Product Operations, Software Operation, Technical Specifications and Product Replacement. Support staff are available from 6 AM to 5 PM Pacific Standard Time (PST), Monday through Friday, excluding corporate holidays. Phone: (800) 833-9200 Option 3 (503) 627-2400 Fax: (503) 627-5695 E-mail: techsupport@tektronix.com Web: www.tektronix.com/support Worldwide Headquarters Contact Information Please contact your local Tektronix Sales or Distributor office. Refer to our web site at www.tektronix.com for listings of those offices. Tektronix, Inc 14200 SW Karl Braun Drive P. O. Box 500 Beaverton, OR 97077