Tek CSA7404/TDS7000 repair project (Upgraded memory/CPU) - Page 1
Forum section: electronics / testgear

author: TiN
author_rank: Super Contributor
timestamp: September 15, 2013, 05:59:51 pm
content: This thread is dedicated to Tektronix TDS7000 platform based scopes (TDS7054,TDS7104,TDS7154,TDS7254,TDS7404,CSA7054,CSA7154,CSA7404)Some information can be useful for newer TDS7000Bplatform as well, as they are based on similar modules.Recently I acquired Tektronix CSA7404 scope, bought as dead for parts, at nice price. Unit come in pretty bad physical shape:All plastic exterior parts except front panel were missing. Outside aluminum shielding/case covers were bent on corners, looked that scope was dropped on angle.Despite of damages and poor look - it still was able to power on and booting Windows 98 OS. Hard drive had bad SMART status and was making clicking noise, so obviously it's going to be replaced with new HDD as one of first steps of scope restoration.While machine was able to boot OS without problems, main scope application, TekScope was unable to start. It was just showing welcome splash screen and hanging there. Downloadingfresh copy of TekScope 2.5.3 Firmware for CSA7000/TDS7000 from Tektronix siteand reinstalling application did not help either.Before we dig in, let's take a look on high-level block diagram of Tektronix CSA7404 fromservice manual:There are four main modules/boards in scope.x86 PC system (NLX motherboard, Socket 370 Celeron 850/128/100 Coppermine CPU, i810 chipset, onboard VGA, network, USB, SDRAM PC133 x 2 slots (only one used with 256MB DIMM)PowerPC system (Tektronix custom board with interface to NLX and ACQ board (had installed 256MB DIMM on it))Acquisition board (ACQ, front-end to scope channels, custom Tektronix high-speed ASICs with dedicated RAM and interface to PowerPC board)Main power supply board (cross compatible, at least with tested CSA7404 and TDS7704B)I also had access to working Tektronix TDS7704B, which come handy to check some parts and do board-level testing. Obviously both these scopes use common architecture, and share same power supply board and similar (but not interchangeable) PowerPC/x86 combo. As first measure of any electronic device troubleshooting - check power. Swap whole power supply module from TDS7704B to CSA7404 showed no functional issues or differences, which tells me that power supply to other boards from mains PSU is OK.Initial testing and debugFirst step will be visual inspection of all internals of scope to see, if any components or boards are physically damaged or missing.On acquisition board there was missing heatsink on one of big National Semi custom ASICs for channel 3. New heatsink was bought are placed on chip, hoping that it's BGA connection to board is intact.On x86 board there was leaky output electrolytic capacitor in CPU DC-DC convertor. It was replaced to new one, which is common operation for servicing old computer motherboards already for a while. As a side note, considering cost of such scopes even today it's quite unpleasant to see low-end CapXon capacitors being used.As was already stated earlier - there were no power supply board problems, as all voltages were present, and no visual damages were observed either. Swapping PSU from another scope did not make scope progress on loading app any further.Interconnect boards (P200 between PPC board and ACQ, power delivery interconnect boards) were fine too, replacing them to same from TDS7704B did not change anything. So problem lied either in acquisition board, or PowerPC board or interfacing between NLX and PPC boards or PPC/ACQ. Interesting fact, that removing interconnect board P200 from PPC to ACQ on TDS7704B did exactly same - TekScope app stopped working and hung on welcome splash screen. This gives us information, that TekScope app needs to communicate successfully with PPC and ACQ boards to be able to start.After some checks of x86 side of scope and trying to run few HDDs with Windows 2000 no obvious problems was found. CD-ROM drive was changed to DVD-RW from old laptop. Connection was standard notebook PATA. Original IBM Travelstar DARA-206000 6GB 4200RPM disk was changed to fresh IBM Travelstar IC25N020ATDA04-0 20GB drive. New Windows 2000 SP4 Professional was installed as maximum supported OS on this series scopes. Given current Celeron 850MHz CPU and 256MB this setup should run smoothly for beginning.Moving our focus to PowerPC board as main suspect. This module There is handy debug 7-segment single digit debug LED, which according to service manual have next codes:This LED is located on PPC board near riser connector and easily visible even when outer aluminum shell is installed.Our board during power up and after was rolling from ".8" code to "L", stays there for couple seconds, and then restarting from start again, and doing this infinitely in loops. On working TDS7704B post code LED was going from ".8" to "L", then when OS started goes to "P" and finally to flashing "-", staying there when TekScope application running. Looks like PowerPC board unable to finish it's booting sequence.NVRAM Failure (Scope boots, OS boots, but TekScope application hangs on welcome splash screens, front panel not respondingDue to age of these machines and usage of battery-backed NVRAM (Dallas DS1245) it's not rare that onboard 3V battery (similar to ones used in usual computers for CMOS data retention) loose it's voltage. Unluckily, boot parameters and configuration is stored in PowerPC NVRAM as well, so after battery failure scope likely to fail, due to inability to load boot ROM from x86 PC system HDD. Visual diagnosis can be done by observing TekScope application to hang on splash screen, and debug POST code indicator rolling codes over and over from 4 to L on PPC board. This is happening because when PPC boot loader lost its boot settings and cannot find correct ROM anymore, it reboots after 10 seconds to try again. That's why it's staying on "L" phase for 10 sec before it repeats loop.Quickly I found users with very same issues with their TDS7000/CSA7000 series machineshereNVRAM repair solution / fixFirst step is to replace faulty battery and allow Dallas NVRAM to be functional again.Locate NVRAM on PPC board:On CSA7404 it's near NLX riser connector, and have PowerCAP module on top of DALLAS DS1245YP-100. PowerCAP is just simple PCB with BR1632 battery soldered on and plastic cover. I replaced old battery (voltage on it was 0.7V after removal) with new Panasonic BR1632A/FA. Make sure polarity is correct when soldering battery on. Latch PowerCAP with new battery back on top of NVRAM.Now we need to reset again correct boot parameters. To do so there are few extra tools are required:* Serial interface to your host, or RS232-USB dongle* Few wires for connecting PowerPC debug serial port* Any terminal software which can work on serial portI had no RS232 on my PC, but had few UART-USB interface bridges based on Silabs CP2103. RS232 levels are converted from UART by onboardMAX232 Driver IC, which is located near NLX riser connector on PPC board. I connected GND (Pin 15), TX (Pin 11), RX (Pin 12) to Silabs CP2103 dongle inputs and connected terminal at 9600, 8N1 settings.First boot output with 9600 baud rate, 8N1 settings :Code:romPost: MPC106 Walking-one passed.romPost: MPC106 configuration passed.romPost: First PCI access passed.romPost: PC87560 Walking-one passed.romPost: PC87560 configuration passed.romPost: DEC21554 configuration passed.romPost: PERFORMING ROM CHECKSUM TEST...romPost: ROM checksum passed.romPost: PERFORMING DRAM CELL TEST...romPost: Enabling data cache...romPost: Data cache enabled.romPost: Enabling instruction cache...romPost: Instruction cache enabled.romPost: DRAM Cell test passed.romPost: Disabling data Cache...romPost: Data cache disabled.romPost: Disabling instruction cache...romPost: Instruction cache disabled.romPost: PERFORMING DRAM MARCH TEST WITH CACHE OFF...romPost: Writing address to each *address...romPost: Reading address from each *address...romPost: DRAM march test passed...romPost: PERFORMING DRAM MARCH TEST WITH CACHE ON...romPost: Enabling data cache...romPost: Data cache enabled.romPost: Enabling instruction cache...romPost: Instruction cache enabled.romPost: Writing address to each *address...romPost: Reading address from each *address...romPost: DRAM march test passed...romPost: PERFORMING DRAM WALKING-ONE TEST...romPost: DRAM Walking-one test passed.romPost: PERFORMING NV-MEMORY WALKING-ONE TEST...romPost: NV-MEMORY Walking-one test passed.romPost: Disabling data Cache...romPost: Data cache disabled.romPost: Disabling instruction cache...romPost: Instruction cache disabled.romPost: Enabling instruction cache...romPost: Instruction cache enabled.romPost: POWER-UP DIAGNOSTIC COMPLETE.HelVxWorks System BootCopyright 1984-1996 Wind River Systems, Inc.CPU: Tektronix HPP - PowerPC 740Version: 5.3.1BSP version: 1.0.4.0Creation date: Nov 2 2000, 11:03:34Press any key to stop auto-boot...7 6 5 4 3 2 1 0auto-booting...boot device : ??D?h?processor number : 0flags (f) : 0x0Network interface D¦h unknown.Can't load boot file!![VxWorks Boot]: Starting at 0xfff00100...Then it rebooted and repeated above sequence again, and again, and again.OK, so now we know that PowerPC board works, but obviously boot device "??D?h?" does not look right, thus it cannot load ROM and boot it's OS.So let's halt auto-booting process by sending any char to terminal. By doing so we can stop loop and try to interact with PPC system. Now can send "?" command:Code:[VxWorks Boot]: ?? - print this list@ - boot (load and go)p - print boot paramsc - change boot paramsl - load boot fileg adrs - go to adrsd adrs[,n] - display memorym adrs - modify memoryf adrs, nbytes, value - fill memoryt adrs, adrs, nbytes - copy memorye - print fatal exceptionn netif - print network interface device addressN - set ethernet address$dev(0,procnum)host:/file h=# e=# b=# g=# u=usr [pw=passwd] f=#tn=targetname s=script o=otherBoot flags:0x02 - load local system symbols0x04 - don't autoboot0x08 - quick autoboot (no countdown)0x20 - disable login security0x40 - use bootp to get boot parameters0x80 - use tftp to get boot image0x100 - use proxy arp0x1000 - use dio to get boot imageavailable boot devices: feippc bp smAfter some experimenting and searching web, I foundsomebody who had similar issues with CSA8000 oscilloscope. Tried very similar parameters and discovered that they work fine after minor modification for my system:Send "c" command to set settings:Code:[VxWorks Boot]: c'.' = clear field; '-' = go to previous field; ^D = quitboot device : smprocessor number : 0host name : hostfile name : c:\vxBoot\vxWorks.stinet on ethernet (e) : 192.168.0.2:ffffff00inet on backplane (b): 192.168.0.2:ffffff00host inet (h) : 192.168.0.1gateway inet (g) : 192.168.0.2user (u) : anonymousftp password (pw) (blank = use rsh): anonymousflags (f) : 0x1000target name (tn) : targetstartup script (s) : c:\vxBoot\dio_rst.vshother (o) : nvfs=0x1000I used path to standard location on my x86 HDD partition, which is hidden folder c:\vxBoot. So if your location different - path need to be corrected. Inet/network addresses are used by internal interface between x86 and PPC. No ethernet cable was connected to either network ports on scope itself.Now reboot scope.Code:...VxWorks System BootCopyright 1984-1996 Wind River Systems, Inc.CPU: Tektronix HPP - PowerPC 740Version: 5.3.1BSP version: 1.0.4.0Creation date: Nov 2 2000, 11:03:34Press any key to stop auto-boot...7 6 5 4 3 2 1 0auto-booting...Initializing backplane net with anchor at 0x1e80000... done.Backplane anchor at 0x1e80000... Attaching network interface sm0... donedone.Attaching network PC1 dio device driver installedinterface lo0... done.Attaching DIO client... done.Loading c:\vxBoot\vxWorks.st...1773516Starting at 0x200000...Initializing backplane net with anchor at 0x16e0000... done.Backplane anchor at 0x16e0000... Attaching network interface sm0... donedone.PC1 dio device driver installedAttaching network interface lo0... done.Adding 6008 symbols for standalone.]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]] ]]]] ]]]]]]]]]] ]] ]]]] (R)] ]]]]]]]]] ]]]]]] ]]]]]]]] ]] ]]]]]] ]]]]]]] ]]]]]]]] ]]]]]] ] ]] ]]]]]]] ]]]]] ] ]]] ] ]]]] ]]] ]]]]]]]]] ]]]] ]] ]]]] ]] ]]]]]]]]] ]]] ]] ] ]]] ]] ]]]]] ]]]]]] ]] ]]]]]]] ]]]] ]] ]]]]]]]]] ] ]]]] ]]]]] ]]]]]]]] ]]]] ]] ]]]] ]]]]]]] ]]]]]]]]]] ]]]]] ]]]]]] ] ]]]]] ]]]] ]] ]]]] ]]]]]]]] ]]]]]]]]]]] ]]]]] ] ]]]]]] ] ]]] ]]]] ]] ]]]] ]]]] ]]]] ]]]]]]]]]]]] ]]]]] ]]] ]]]]]]] ] ]]]]]]] ]]]] ]]]] ]]]] ]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]] Development System]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]] VxWorks version 5.3.1]]]]]]]]]]]]]]]]]]]]]]]]]] KERNEL: WIND version 2.5]]]]]]]]]]]]]]]]]]]]]]]]] Copyright Wind River Systems, Inc., 1984-1997CPU: Tektronix HPP - PowerPC 740. Processor #0.Memory Size: 0x2000000. BSP version 1.0.8.0 .WDB: Ready.usrNvFsInit: NAME=/nvram BASE=0xfd0ff100 BPB=512 BPT=8 NB=8 BO=0nvfs: WARNING: Creating new NVRAM file systemtcsTableUnpack: checksum failed on buffertcsTableLoadFromNVRAM: tcsTableUnpack failedtcsSynchronizeSensors: ERROR: Failed to create '/dev/tsAmbAcq'tcsSynchronize: ERROR: Sensor synch failedKERNEL: THERMAL CONTROL INITIATEDExecuting startup script c:\vxBoot\dio_rst.vsh ...dbFsIoctl: invalid code 3cd "pc:c:/vxboot"value = 0 = 0x0tcsLoadTableToNVRAM "setup.tcs"value = 0 = 0x0## hopefully you get this message at the end:# 'value = 0 = 0x0'# REBOOT!!!Great, now PowerPC board boots (diag POST LED shows "P" after "L" which means boot image is running). Now change dio_rst.vsh script tooriginal top-level scriptwhich was recovered from native Win98 HDD folder c:/vxBoot. I renamed topScript.hw to dio_rst.vsh to match boot settings:Code:Executing startup script c:\vxBoot\dio_rst.vsh ...dbFsIoctl: invalid code 3################### topScript starts ###############################cd "dbfs:c:/vxBoot"value = 0 = 0x0ld &lt; TekScope.ovalue = 23662048 = 0x1690de0ld &lt; TekScopeSM.ovalue = 23661408 = 0x1690b60pDbDev = ramDevCreate(0, 512, 1152, 1152, 0)new symbol "pDbDev" added to symbol table.... bla-bla ...rtlStartupvalue = 0 = 0x0tsCompvalue = 0 = 0x0Done executing startup script c:\vxBoot\dio_rst.vshKERNEL: RUNNING TIME SLICED AT 10 TICKS PER SLICE!-&gt;Now scope application able to run successfully, and I got first waveforms on screen.Also seem like this particular scope got all options enabled, but some applications required for those options are missing, as I had installed fresh OS.So system/software spec is:Code:CSA7404 (4GHz, optical hardware present) running Windows 2000 Pro SP4 RuTekScope version 2.5.3Option 4M: 32 Meg Max 8M/ChannelDisk Drive Measurements 2 (Option 48)Option 49USB 2.0 Test package (Option 50)Option 51Option 52Option 53Option 54RT-Eye Serial Compliance and AnalysisInfiniBand Compliance ModulePCI-Express Compliance ModulePretty nice set got there for use in digital/PC hardware development and debug. Scope input interface for all four channels is proprietary TekConnect, and inputs are all 50 Ohm only. So to be able use regular passive BNC probes high-impedance adapter system TCA-1MEG is required, to use 50 ohm direct interface to target environment one can useTCA-BNC or TCA-292MM or TCA-SMA. As drawbacks of high-performance capabilities of such high-speed scopes special probing accessories are required, increasing total using cost. Passive probes cannot be used without TCA-1MEG.Already got pair of Tektronix P7380 8GHz Differential probes, which are designed for high-speed signal acquisition with special solder-on tip system. Going to buy some lower speed single-ended active probes as well later.Using this probe is really using for debug hardware, like DDR interfaces on VGA/DIMMs/MB's:DDR3 DIMM clock measurementRT-Eye report:PCI-Express 1.0 reportNext steps:* Design and assemble few custom probes for high-impedance environment* Installing missing options softwareBonus:Replace LEDs behind front panel indicators and push-buttons, just like in newer DSO/MSO series.To be continued...Original wiki page on my siteThanks for reading

author: marshallh
author_rank: Unknown
timestamp: September 15, 2013, 06:36:00 pm
content: Thanks for posting, neat to see it back in action.

author: nctnico
author_rank: Super Contributor
timestamp: September 15, 2013, 09:51:07 pm
content: Drool... A wooden casing would be neat

author: onlooker
author_rank: Frequent Contributor
timestamp: September 15, 2013, 10:30:19 pm
content: Thanks, for sharing an interesting story. May I ask how much did you pay for it and from where?

author: free_electron
author_rank: Super Contributor
timestamp: September 16, 2013, 12:01:21 am
content: Careful swapping that motherboard out. The motherboard uses a custom bios that allows the VXworks to become bus master and take control over the harddisk prior to boot !Don't make the mistake of flashing a regular bios in there , it will brick the machine. I've been there and done that ! the correct bios can be found on the harddisk as well as the flash utility for it. a stock motherboard will not work. there are only two motherboards that work in this machine and the 810 is the most performant of the two. the other runs win2000....let it be ...The other annoyance is loosing the ram contents. it removes the serial number from the machine and disables all options.There is a way to restore it but you need a gpib adapter and send a commmand to the machine to contact the security manager and give it the root key.

author: Vgkid
author_rank: Super Contributor
timestamp: September 16, 2013, 12:47:09 am
content: That is a very nice writeup on the repair, very nice scope as well.

author: marshallh
author_rank: Unknown
timestamp: September 16, 2013, 02:14:11 am
content: Sooo.. can I send you a board for PCIe compliance testing

author: TiN
author_rank: Super Contributor
timestamp: September 16, 2013, 10:39:13 am
content: Ha, to do so need to have much more than just 4G scope. Even if leave alone BER measurements, just CEM boards and fixtures cost quite a money. And for PCIe Gen3 at least 16G bw required.I got scope for just little over one K$, and main reason was because could not resist grabbing it , not because real need right now. Had no scope for personal use, just thought nice to have one at home.

author: TiN
author_rank: Super Contributor
timestamp: October 04, 2013, 02:21:39 pm
content: Well, I got some update today, because received new goodies for scope.Got 512MB and 256MB PC133 SDRAM DIMMs. x86 NLX motherboard refused to detect 256Mbit 512MB DIMM, so had to install 2x256MB into PC boardand 512MB on PowerPC board.And CPUs:It's Pentium III 1000E (1000/256/100/1.75V, Coppermine-256), original Celeron 850/128/100 from scope and pair of Tualatin 1400S (1400/512/133/1.45V).Pentium III 1000E drop-in to socket and worked flawlessly, booted right in with 100MHz FSB, 1.75ish Vcore.For those who want try upgrade their TDS7000/CSA7000's - beware to use 100MHz FSB chip, not 133MHz as such will run on 100MHz only, which will give only 750MHz (100*7.5 ratio = 750 for 133MHz native CPU).But top glorious Pentium III-S 1.4GHz did not work so easily, Vcore was 1.3V, but nothing happen after power on...Obviously Intel NLX motherboard in TDS7000/CSA7000 do not support Tualatin natively and I needed to do some surgery to bypass thatYou can see already finished modified CPU bottom left on photo above.What did I do:1. Isolate pins AN3 (DYN_OE), AJ3 (RESET#2) from socket (I just desoldered pins right off CPU)2. Isolate pin AK4 and connect it with AN11 via 1Kohm resistor (on CPU package)3. Connect AM34 and AK36. (VID25mv signal tie to GND, to have correct Vcore VID operation)4. Remove pins G35, G37 ? N37.5. Connect G35,G37 and N37 together on CPU package.That's it, after these modifications on CPU - it booted up and run smooth on 100MHz BCLK (native ratio on 1400S is 10.5, so 100*10.5 = 1050MHz).Vcore voltage is correct too, 1.46V, so nothing to worry about.So far only one thing left to do - receive covers and casing parts from Tektronix to completely restore outer looks on scope.No more upgrades planned.

author: TiN
author_rank: Super Contributor
timestamp: October 09, 2013, 06:54:51 am
content: Got parts from Tektronix today

author: leafi
author_rank: Regular Contributor
timestamp: October 10, 2013, 03:14:46 am
content: so how does your scope run with the upgraded CPU? I might look into do this as my TDS7404 is slow as hell!

author: TiN
author_rank: Super Contributor
timestamp: October 10, 2013, 03:35:34 am
content: Smooth and nice (but I think that's more because I added memory to 512MB total, rather than CPU).Btw, I still have those CPUs, which I don't really need nowSo far:New covers installed. Missing label for front panel and black cover for aux inputs on front.Did not installed floppy drive (who needs them today?).And missing some screws, need find them first.So far spend around 2.5K$ on everything (including pair of P7380 probes), which is still quite a lot, but consideringthis scope level - i think it was worth every pennyUPD: Went cleap-nut and just printed labels on paper and stick them to panels.Now gotta hunt and wait patiently for good priced TCA-BNC adapters, TCA-1MEG high-impedance adapter. Already won pair of P6245 1.5GHz 1:10 active probes (for parts condition too, lol), and need think about iView (its just GPIB-USB dongle and couple BNC-BNC cables).Tried iView on my TLA714 with NI GPIB-USB-HS and worklab TDS7704B, was nice neat feature to see everything in TLA software tool, eliminating need to mess with scope controls.

author: TiN
author_rank: Super Contributor
timestamp: November 25, 2013, 01:56:32 pm
content: Just in case anyone needs drivers for TDS7000/TDS7000B/CSA7000/CSA7000B series scopes:Display driver from TDS7000B/CSA7000BUSB Front Panel driver for TDS7000/7000B/CSA7000/7000BPowerPC board driver for TDS7000/7000B/CSA7000/7000BAll drivers except display were tested on TDS7704B and CSA7404, with Windows 2000 Professional english.Display driver is only for 7000B, i did not needed it on CSA7404TekScope software itself 2.5.3 for TDS7000/CSA7000 (same as one posted on Tek website)TDS2.5.3 TekScope

author: CSmith
author_rank: Unknown
timestamp: December 01, 2013, 01:13:58 pm
content: BTW, I pulled the following out of a TDS7404 that had been under Tektronix maintenance and should be the correct default values.Code:VxWorks System BootCopyright 1984-1996 Wind River Systems, Inc.CPU: Tektronix HPP - PowerPC 740Version: 5.3.1BSP version: 1.0.4.0Creation date: Nov 2 2000, 11:03:34Press any key to stop auto-boot...1[VxWorks Boot]: ?? - print this list@ - boot (load and go)p - print boot paramsc - change boot paramsl - load boot fileg adrs - go to adrsd adrs[,n] - display memorym adrs - modify memoryf adrs, nbytes, value - fill memoryt adrs, adrs, nbytes - copy memorye - print fatal exceptionn netif - print network interface device addressN - set ethernet address$dev(0,procnum)host:/file h=# e=# b=# g=# u=usr [pw=passwd] f=#tn=targetname s=script o=otherBoot flags:0x02 - load local system symbols0x04 - don't autoboot0x08 - quick autoboot (no countdown)0x20 - disable login security0x40 - use bootp to get boot parameters0x80 - use tftp to get boot image0x100 - use proxy arp0x1000 - use dio to get boot imageavailable boot devices: feippc bp sm[VxWorks Boot]: pboot device : smprocessor number : 0file name : c:/vxboot/vxWorks.stinet on backplane (b): 192.168.0.1:ffffff00host inet (h) : 192.168.0.2gateway inet (g) : 192.168.0.1flags (f) : 0x1008target name (tn) : tds7000startup script (s) : c:/vxboot/topscript.hw[VxWorks Boot]:

author: GreyWoolfe
author_rank: Unknown
timestamp: December 02, 2013, 01:48:07 am
content: Awesome Job!Tom, NW0LF

author: Khashoggi
author_rank: Contributor
timestamp: December 09, 2013, 11:39:01 pm
content: Great job!Where can you find the system restore cd image? For a tds7054. There isn't one posted on the tek website.

author: TiN
author_rank: Super Contributor
timestamp: December 10, 2013, 01:04:45 am
content: I did not had system restore CD image.Just installed usual Win2000 OS, installed drivers for PPC board and USB Front panel (I had posted them earlier here) and downloaded TekScope 2.5.3 from tek site.

author: CSmith
author_rank: Unknown
timestamp: December 10, 2013, 01:55:43 am
content: I'll vouch for the drivers that TiN posted are the same as what's included on the hard drive after a restore from original system restore CD's. I double-checked them to see if he happened to have anything newer than what I already had, and they matched. However for those who have expanded their memory to 512MB and would like to jump to Windows XP, I'd suggest hunting down the v2.51c "release" Windows XP driver for the proprietary Chips and Technology LCD interface. The filename is "wxpv251c.zip". The other drivers are generic enough that they run under Windows XP OK. Tektronix went through a number of different NLX motherboard vendors over the production run, so depending upon your particular motherboard, you may also need to track down the Intel Ethernet driver. Replacing it with the Intel SU810 NLX motherboard guarantees Windows XP built-in driver support for all of the on-board peripherals.

author: echen1024
author_rank: Super Contributor
timestamp: December 10, 2013, 02:52:18 am
content: Quote from: Khashoggi on December 09, 2013, 11:39:01 pmYOu won that auction did you? Lucky bastard.

author: Carrington
author_rank: Super Contributor
timestamp: January 11, 2014, 06:02:27 pm
content: Hi TiN.Do you know if the software Tek AppV5.1 has support for the TDS7xx series?Thanks.

author: TiN
author_rank: Super Contributor
timestamp: January 12, 2014, 03:42:18 pm
content: Seems so, at list TDS7xx scopes and TDS694 are in the list, but probably some functions will not be working (there is extra clock, which is shown as not used in drawing diagram). On TDS7xxx it goes to EXT REF input on scope, but those older scopes don't have EXT REF input.Take this info as is, as I don't have ability to check if that combo actually work.In worst case you still can use TLA with scope, just connect trigger output from TLA to scope trigger input (even non-tektronix is fine, lol),and route analog outputs from TLA7AA4 into scope channels, and you will have signals from LA triggered on scope screen.Just not as neat as having everything in same TLA app, that's it. (Even using iView one must adjust horisontal/vertical scale on scope itself, cannot use TLA app to do those adjustments).

author: Carrington
author_rank: Super Contributor
timestamp: January 12, 2014, 05:28:53 pm
content: Quote from: TiN on January 12, 2014, 03:42:18 pmOk, thanks.But if the LA's "wfrm/s" (triggers/s) are greater than the oscilloscope's wfrm/s (rearm time), the oscilloscope will not be able to follow LA's triggers.This is a problem, because: How do you know what oscilloscope's captures goes with what LA's triggers?And if the above problem is solved the phase has to be adjusted too. So it's a mess, and better to use compatible instruments.Because surely they have already thought of this, and have fixed this.Or am I wrong?

author: TiN
author_rank: Super Contributor
timestamp: January 12, 2014, 08:56:01 pm
content: All TLA trigger setup is internal to TLA modules, and then you select output trigger to scope.Then can use skew adjustment in scope, at least that's available in TDS/CSA7404 and 7704 i tried. Dunno about other models, but should be there too.Even not adjusted, unless you watch something with hundreds of MHz, will be quite okay.I shown example non-compensated iView capturehere.TLA7AA4 outputs connected to scope inputs (thru TCA-BNC) via mismatched BNC-BNC cables and SMA-SMA (thru TCA-SMA).iView setup using recommended connections, and with generic BNC-BNC cables. Interface - NI generic GPIB-HS-USB connected to my remote machine(as I run TLA only remotely, don't even have NI-VISA on mainframe itself).

author: Carrington
author_rank: Super Contributor
timestamp: January 13, 2014, 02:28:39 pm
content: Quote from: TiN on January 12, 2014, 08:56:01 pm@TiN:At least 2us long, in the image above. All was captured without pauses? Ie are not overlapping catches?And what is the maximum length?

author: TiN
author_rank: Super Contributor
timestamp: January 14, 2014, 02:09:35 am
content: Capture on post i linked was around 100nS long.One catch, yes. You have TLA, right? Your questions seem strange, as for owner of TLA frame, as that'spretty much just TLA operation.