Tektronix TLA714 Logic Analyzer - Page 1
Forum section: electronics / testgear

author: cswilsn
author_rank: Contributor
timestamp: September 07, 2013, 10:04:17 pm
content: Hey Everyone,I had bestowed to me a Tektronix TLA 714 Logic Analyzer, however, I had a few issues....The hard died, after only a short period of time, I restored from an image however, i'm having a problem finding a small enough IDE hard drive.The BIOS only supports up to an 8GB Drive, I put a 40 and a 60 in the machine, which I was able to find, and no go. I do get windows installed but after about a half day of operation the hard drive starts having errors, machine locks up and scandisk finds a lot of problems.I got nowhere with Tektronix trying to buy a BIOS update, and none of the vendors online seem to carry it.is anyone out there lucky enough to have one?I'd be more than grateful to find an image!I'm not sure, but I think it may have also been included on one of the system disks?Thanks a bunch,Chris W

author: marshallh
author_rank: Unknown
timestamp: September 08, 2013, 01:13:27 am
content: Get an IDE-CF adapter and a 2-4GB compactflash card.The failures sound like old Maxtors after they've been revived from storage.

author: TiN
author_rank: Super Contributor
timestamp: September 08, 2013, 04:43:04 am
content: Let me check, but i had no issues to boot my TLA714 with 20GB drive.Is there procedure or tool which can be used to download BIOS ROM?It's soldered on PCB, so I would not desolder it yetBut after all I installed small HDD and use TLA purely via ethernet from my main workstation.Found it working remote much more easier and faster than local TLA app. Maybe stock TLA old app is fine, but I used TLA version 5.8 for better featuresAlso I do have extra working mainboard, which I don't actually need much, so let me know if u interested.

author: nctnico
author_rank: Super Contributor
timestamp: September 08, 2013, 01:59:55 pm
content: I installed a 4GB CF drive in my TLA704. Works like charm. These are pretty cheap from Dealextreme.com.

author: picburner
author_rank: Frequent Contributor
timestamp: October 11, 2013, 09:58:35 pm
content: Hi TiN,I'd be interested in buying one of your spare main board if you can sell it.Let me know, thanks.RegardsGiampiero

author: Khashoggi
author_rank: Contributor
timestamp: February 01, 2014, 11:11:34 pm
content: Quote from: TiN on September 08, 2013, 04:43:04 amI have a TLA714 upgraded with Windows XP running TLA 5.1 application. No later versions will let me install because the installshield wizard blocks the install. I can't get the files extracted to do it manually either. How did you get 5.8 onto your TLA714?Thanks for the help!

author: TiN
author_rank: Super Contributor
timestamp: February 02, 2014, 02:32:55 am
content: Let me check, but from what I remember, just installed 5.1 and then installed higher versions one by one.My LA runs Win2K Pro SP4. But I can be wrong, as I don't use TLA App on LA itself, use only remote connection. Pentium 266 is laggy when processing all that heavy GUI.As soon as server app on LA is 5.1 version, you can use even latest 6.1.0127 on remote host via PCMCIA LAN.

author: Khashoggi
author_rank: Contributor
timestamp: February 02, 2014, 05:17:12 am
content: Quote from: TiN on February 02, 2014, 02:32:55 amInteresting... The Tektronix website has versions 5.1, 5,6, 5.7, 5.8 and then the 6.x releases.The 5.1 release was a zipped archive with a setup program.The 5.6-5.8 releases all use a installshield wizard type install program. It contains all the files encrypted within, and during install checks machine type and refuses on a TLA 714.I've tried some extraction methods of the files in the installshield archive, but none have been successful to date.If you have installers for versions to take the unit up to 5.8 that don't care about the machine type, I would be very grateful to get copies.My main workstation for using the TLA is Windows 7 which requires v5.6 or higher to be compatible with Win7. Those versions require me to upgrade the firmware on the TLA module which I don't want to do unless I can run the same version on the TLA714 because they might become incompatible with the higher firmware.The fun continues with the 6.x releases. They drop support for the TDS scope I want to use with iview in combination with the TLA logic analyzer. So, I am limited to 5.8 on the Windows 7 workstation, and would like to get the TDS714 up to the same version.Thanks for your help!

author: TiN
author_rank: Super Contributor
timestamp: February 02, 2014, 10:13:42 am
content: Just got back home and checked TLA.My bad, it's running TLA App 5.1 Service pack 1, and my single 7AA4 module updated to 5.8.001 firmware (it still works fine with local TLA App 5.1).I run 6.1.127 version on my main WS (under Win2008 R2 x64). Before was running 5.8, but had issues with DDR3 support package, so updated to 6.0 and 6.1 after.As for iView, yea, they killed 7xx scopes in latest versions. Mine CSA7404 and lab TDS7704B works ok with generic NI USB-GPIB-HS, tho

author: Khashoggi
author_rank: Contributor
timestamp: February 02, 2014, 06:11:04 pm
content: Quote from: TiN on February 02, 2014, 10:13:42 amOK, that's good info! I will update the firmware on my module then so it can talk to the later version clients. Cheers!

author: nctnico
author_rank: Super Contributor
timestamp: February 02, 2014, 10:23:50 pm
content: With some hacking of installer scripts I managed to get a later version of the software working on my TLA704.

author: Khashoggi
author_rank: Contributor
timestamp: February 03, 2014, 07:18:44 pm
content: Quote from: nctnico on February 02, 2014, 10:23:50 pmI haven't looked too deeply into how to hack installshield. Trying some decompression programs on the archive didn't yield any interesting files, or the control scripts. I used zipscan.How did you hack into the scripts?

author: nctnico
author_rank: Super Contributor
timestamp: February 03, 2014, 09:56:53 pm
content: I think I used a tool called ISDCC (installshield decompiler), installshield compilers (i5comp or i6comp) and some hacking skills to create a new package. Anyway, the highest version my TLA704 supports is 4.4 which is already a major improvement over version 3.3.

author: bench_knob
author_rank: Regular Contributor
timestamp: February 22, 2014, 07:28:58 pm
content: Hi Kashoggi,QuoteI installed TLA App v5.1 on my TLA704 (using the RFDes install script tweak) which is now running Win2k Pro SP4. To do so, (following the good instructions by RF Des), I needed to unpack the SETUP.EXE file. I used a sw tool to break-out the files from the SETUP.EXE self-expanding packed install program.Having tracked down and tested dozens of unpacker tools, the only one that I found that works, is the Universal_Extractor v1.6.1.62. It is available on the 'Net.Last evening, I dugout my copy and tested the tool on TLA v5.6 & v5.8 for you:Universal_Extractor_1.6.1.62_Portable.rarWhen I downloaded the tool (01-07-2013), using McAfee AV, I scanned the unpacker tool for virii and double-checked for back-doors using a port monitor and I found nothing wrong with the version I downloaded. The program's author offers source-code so its likely safe, but if you are still uncertain, you can review the source code, and compile it yourself and, you can then test that on a don't-giva-hoot PC. In any case, verify things for yourself!!You can download the tool from here:http://depositfiles.com/files/qr0dh09gkCheers,bench knobedit: fixed lexicals

author: nctnico
author_rank: Super Contributor
timestamp: February 22, 2014, 08:32:41 pm
content: Are you sure 5.1 can run on a TLA704? I recall trying that but there where problems with the drivers to access the hardware / the software needing Windows XP to work.

author: Khashoggi
author_rank: Contributor
timestamp: February 22, 2014, 09:12:02 pm
content: Quote from: bench_knob on February 22, 2014, 07:28:58 pmThanks for the tips! I'll get that unpacker.I did get 5.1 loaded and after doing the 5.8 firmware updates on my modules, I can use v5.1 from the TLA or v5.8 remotely from Windows 7 workstations.Cheers!

author: bench_knob
author_rank: Regular Contributor
timestamp: February 23, 2014, 03:53:07 am
content: Quote from: nctnico on February 22, 2014, 08:32:41 pmHi nctnico,I do have TLA v5.1 SP1 running on a TLA-704, with Win2k Pro SP4. Much of the upgrade process was afforded by excellent information, tips and a couple of files engineerd and provided by RFDes, whom I met on the Tektronix Logic Analyzer forum, and who offered details regarding his TLA-704 upgrade efforts, which work excellently in my opinion. I have successfully implemented both an LCD upgrade and the TLA Application using RFDes's strategies.I had to upgrade the BIOS to 1.00.14, (Hani Freiwat kindly provided the image file and a phlash.exe program). This enables the RAM upto 128 Mb. My sticks required enabling ECC.Also, to implement the LCD resolution upgrade, required another BIOS image file, which RFDes also engineered and provided, ya have to remove the TLA mainframe's outside covers and the CPU cover to jumper the BIOS flash memory write-enable pins on jumper block at H2. Then flash the BIOS with RFDes's image file. The 640x480 LCD will no longer function as a display device after this operation so the LCD must be upgraded first. One may enable simul-scan in the BIOS to run an external monitor however. One might notice that the Power-On-Self-Test emits a couple of beeps after setting SimulScan in CMOS, this is not a malfunction and is described in the TLA-704 User Manual, as an aural status indication of that state setting.RFDes's strategy:Install these files in the following order:Win2k Pro SP4,IE6.0,Windows Installer 3.1, anddotNET 2.0 Redistributable Framework Runtime Library,and TLA 5.1 SP1 application (requires unpacking and replacing the SETUP.INX file with a tweaked script)I discovered that the dotNET redistributable is no longer available for download from the M$ website or they are cleverly hiding it? In anycase, I did find a website that hosts many of the older OS support files including the Windows Installer and IE60.To upgrade from Win98-SE to Win2k, also required a display resolution increase as well as I believe that you likely already know, as Win2k requires a minimum of 800x600 resolution. The TLA-704's display panel does not support that, and so the LCD panel must be replaced with a higher res version.Using JF's BIOS image and his tlaSoftOff.exe front panel soft-off power-switch driver program also resolves the snap to black screen crash with blue error halt message directly from Win2k..(bad) problem.For my LCD upgrade, I found a mechanical drop in replacement LCD, and I designed a homebrew LCD SMD-connector-to-34pin-IDC-cable-adapter PCB using Eagle 5.50 to draw the schematic and design the single-sided (Kynar wire jumpers) PCB which I PulsarFX toner/foil transfer, etched and baked in my pseudo-homebrew PID controlled reflow oven. I had to cut away about 0.5" (~12mm) of aluminum on the mainframe assembly's LCD panel back cover plate, to enable connector clearance. It's a very clean modification and it uses the same mounting standoffs that the original Tektronix cable adapter PCB utiltilized.If anyone is interested I'll share my Eagle 5.50 schematic and PCB design files as well as the parts list. I bought the new, unused NEC 10" LCD upgrade panel on eBay for $40.I'm including a couple of photos of the TLA-704 depicting Win2k logon screen and a screen shot of the TLA 5.1 App 'About' screen for ya gander at.Re; the Win2k SoftOff matter, there are additional details that need be described, involving BIOS settings and M$ Win2k APM Legacy Node drivers, else one can not use the front-panel power-switch for controlled shutdown in Win2k Pro.Incidentally, in reviewing the photos on the board after submitting post, they appear to exhibit an image artifact (cross-hatching) which is not present on the actual analyzer LCD display, I think its a camera to LCD update rate alias...like that face on Mars, a sampling alias. Heh heh.Cheersbench knobedit: forgot to mention 800x600 BIOS flash detail.

author: nctnico
author_rank: Super Contributor
timestamp: February 23, 2014, 02:44:07 pm
content: Hmm. Maybe I'll give it another try. The software (V4.4) on the logic analyser itself runs very slow even with a Pentium 200MMX overdrive upgrade so it would be nice to run it on a desktop PC. Could you post the modified setup.inx file somewhere?BTW I 'know' RFDES as well. Actually the 800x600 upgrade was my idea to begin withI hacked the GRUB bootloader to do a call to the video BIOS to switch to 800x600 before the OS gets started. RFDES hacked the BIOS which is much easier.

author: bench_knob
author_rank: Regular Contributor
timestamp: February 24, 2014, 10:42:51 am
content: Quote from: nctnico on February 23, 2014, 02:44:07 pmNico,I was working my own mods, when I read your posts way back when, and your strategy was kewl. Thanks for sharing. Later I bumped into RFDes, and I learned that his strategy was a bit further along the modification curve than any of the other strategies that I tracked down including that of my own. In any case it still took me two years to do everything. Hah. The PCB I made took forever to finish...life got in the way, but it sure does work nice. I'll include some photos for ya'll to gander at.To your point, I asked RFDes' permission to refer folks to him last week prior to posting about my TLA mods here in EEV_Blog. But, heh heh, if you're shy, just say, "hey I bumped into w.w on EEV_Blog, I'd like to ask for a copy of the .inx file" and say hello too.Yep, his LCD BIOS solution works well, no fiddling around, just turn the scope on. And remember to ask for the tlaSoftOff.exe driver, unless, you like myself, before getting his driver, ya cut holes in the TLA box to install a hard-off power-switch which is no longer needed. Mine is out of the way, I used an Alco alternating 6Amp 250VAC push-button power-switch, recessed into a 1.5" x 1.0" (38,1mm x 25,4mm) milled slot in the right-side plastic louvre cover. Frankly, its nice to be able to actually turn-off the power-supply. Win2k doesn't handle the scope's front-panel 'power-switch' hardware interrupt properly and it crashes the system. But I've reviewed & downloaded your I2C/SPI sauce-recipe over on SparkFun (yep....mighty tastey too), so its likely that you could also write your own soft-off handler, but why? When there's a perfectly functional solutionavailable simply for the asking? Me? I aint shy, I fully intend to implement your serial bus decoder and experiment with it, and hopefully to make some enhancements too. For instance in my other project, I need a Manchester serial decoder, so maybe I can hack your base code to implement this feature. Which I'll share with folks in the old InterNet tradition.Oh, lest I forget....how did you upgrade your processor and have you seen any timing artifacts attributable to the speed upgrade? However, my Ma said I was born with soldering tool in my hand...and I do have a hot-air rework station, but only a SoldaVac for suck'n solder. I'm reticent to attempt to unsolder the processor, although I do have a spare mainboard for backup in case I munch a trace. The PCB looks tight to me...thru-hole diameters. Was that your experience? Are they tight? In the old days, some folks mechanically broke-up the big IC packages, unsoldering each pin individually grabbing them from the top while heating the pin on the bottom, but I'm not certain that will work in this case. I've been considering using my mini-mill to just shave off the top, then unsolder the pins. That could work, hopefully diminishing the possibility of damaging the mainboard. Any one got any insight into something like that?So how did you get that puppy off the board? And did you stick in a socket for the MMX? Which part did you use? Got any photos of the finished mod? Does it need cooling? Not forgetting about the height. But if your's works, why would I need to solder in a socket, true?Oh, and I've been following the TLA7AAx discussion too, very interesting. I wonder if that Tek strategy is employed in the other modules? TLA-7Nx series, 128k? I understand that they go up to 4Mb, you know anything about that? All my modules are pre-counter/timer S/Ns.Thanks for sharing your code and other ideas.The photos, in no particular order:- Brendie, my lab assistant, she oversees all my lab activity making sure everything is purrrfectly proper, heh heh- Schematic & PCB Layout (Eagle v5.50 Std)- LCD 41pin to 34pin IDC cable adapter silkscreen (blue)- PCB installed onto LCD assembly, showing the inverter power cable snaking across- my homebrew reflow oven, showing blower attachment (gotta have this or it doesn't work)- screen shot of the oven control sw reflowing the PCBCheersbench_knobor ya can skipe me, at 'zeebra underscore xray', add me to your contacts list... nifty way to send files that gaaglemale doesn't track...

author: TiN
author_rank: Super Contributor
timestamp: February 24, 2014, 11:24:18 am
content: Nice mods, keep it goingI can host photos and files, if you want. Have server 24/7.

author: nctnico
author_rank: Super Contributor
timestamp: February 24, 2014, 12:01:33 pm
content: The 200MMX Overdrive replacement is among the boldest soldering jobs I did. First of all I got a used 200MMX overdrive from Ebay (there are always a few available). First I tested it in an old Pentium motherboard to make sure it worked. Then came the bold part. The original CPU is a Pentium 133 with a heatsink attached to it. The board is a 6 or 8 layer board with massive power planes. Close to the CPU there is a BGA chip (the Chipset). I suspended the board so the CPU had enough clearance to drop from the PCB and heated the board carefully using a paint stripper. This does take some practice in order not to burn the board or seperate the layers. After a while the CPU finally dropped from the board. The next job is to remove the solder from the pads which takes loads of soldering wick. Unfortunately the board did got a bit warped which is almost unavoidable.The 200MMX is just a few mm higher than the original CPU + heatsink so there is no room for a socket. I soldered the 200MMX directly into the board and turned the slotted vents in the aluminium housing into a square hole. This way the 200MMX overdrive just fits within the original housing. The last problem I recall is that the BIOS thought it was dealing with a 180MHz Pentium so it set the clock to 60MHz. IIRC I lifted a pin on the PLL chip to set it to 66MHz. I'm not quite sure a processor upgrade is worth it when you can do the heavy lifting on a remote machine.About upgrading the modules I'm still convinced attacking the Powerflex tool is the best way. The older Tektronix scopes (TDS500 series) have a password system which allows maintenance software to enable or disable options over GPIB. I wouldn't be surprised if the Powerflex tool is just decoding the option key and using the password scheme to talk to the boards in plain text GPIB commands over Visa.

author: Khashoggi
author_rank: Contributor
timestamp: February 24, 2014, 06:30:03 pm
content: Where can I find tlaSoftOff.exe?Using Windows XP on a TLA714 disables the functionality of the power switch...

author: bench_knob
author_rank: Regular Contributor
timestamp: February 25, 2014, 06:44:13 am
content: Quote from: Khashoggi on February 24, 2014, 06:30:03 pmKahshoggi,The tlaSoftOff.exe driver was written for Win2k. I don't know if it'll work on WinXP or if its ever been tested on or used on WinXP? The mods I described were specifically for TLA-704. I dropped into to this thread as some folks were talking about Win2k and problems with installing TLA app v5.1 on it, etc. I didn't intend to hi-jack the thread. However, you can ask RFDes for a copy, he is the author, as I mentioned in previous posts. PM me for RFDes' contact information or, skupe me at:1) zeebra underscore xray2) request to be added to my contact list.bench knob

author: Khashoggi
author_rank: Contributor
timestamp: March 08, 2014, 07:07:44 am
content: Thanks for the info. I did some investigating, and determined the soft-power switch was defective!The TLA714 recognizes the softpower switch as expected under Windows XP.

author: nctnico
author_rank: Super Contributor
timestamp: March 23, 2014, 10:48:32 pm
content: Quote from: nctnico on February 22, 2014, 08:32:41 pmI got the modified setup.inx from Rfdes but still no luck. I can't seem to load the hardware drivers on my TLA704 mainframe. Perhaps I have an older version of the mainframe. I feel like cryingEdit: I got it working! I had to reinstall Win2k and all the software on the mainframe. I guess Win2k got tied into a big nut.

author: bench_knob
author_rank: Regular Contributor
timestamp: March 27, 2014, 06:36:16 am
content: Quote from: nctnico on March 23, 2014, 10:48:32 pmHah...kewl...excellent.So have you got it running remote yet? I'm still struggling with mine. I got a laptop that runs my reflow-oven software, with WinXP Home Ed. I finally got the Win2k TCP/IP (static) running through a 100MBps switch over to the laptop, the TLA & the laptop can see each other, I've successully sharing a folder between'm, but I can't cause the TekVisa Instrument Mgr to see the TLA. But the question I have, is what for? I don't wanna look at my TLA using Excel. There must be something that I'm missing? So what is the application that I run on the remote PC?cheers...bench knob

author: TiN
author_rank: Super Contributor
timestamp: March 27, 2014, 08:04:12 am
content: Did you start TLA server app on frame?Firewalls?

author: nctnico
author_rank: Super Contributor
timestamp: March 27, 2014, 01:54:57 pm
content: You have to close the application on the mainframe itself and start the server (right-click on the icon in the icon tray).I got mine working remote with some trouble. I had to install the software on a fresh XP in a virtual machine because the software keeps crashing on my PC.Another problem I have is that the 3COM PCMCIA network cards I have are terribly slow. With FTP I get around 40KB/s (400kbit/s) outward and about 140KB/s inward. A different PCMCIA network card is on it's way.

author: Mark_O
author_rank: Frequent Contributor
timestamp: March 27, 2014, 06:38:25 pm
content: I don't have a TLA714, just an older TLA704 (actually 3, with one a part's mule), but perhaps some questions on it wouldn't be out of place here? If so, let me know and I'll start a separate discussion.I have a couple 7N3 modules (102 channels, 1M depth) with my TLA704's, and the thing is, I never use 102 channels.The most has been about 16!I remember reading some years back (on the Tek site) that it's possible to reconfigure these to trade off width for depth. But they had no info on how to do that, whether it was a software setting or restrapping it internally. They just indicated to "Contact your Application Engineer", and even a couple years ago this was old enough they had no interest in responding.I was wondering if any of the TLA7xx experts here had any info on that? For me, 6x the depth would be vastly more useful than 6x the width. At least 99% of the time. (Also, unlocking the 4M depth would be a nice bonus, and I've seen some discussion on that in other threads here, but haven't pursued it yet.)[My 7N3 module Firmware is v4.1.4, and Options Installed is -6S, if it matters. One of them has slower 100 MHz State clocking, so probably a -2S on that.]

author: nctnico
author_rank: Super Contributor
timestamp: March 27, 2014, 08:29:51 pm
content: You can combine the channels but only as high samplerates. AFAIK: On the TLA7L, M, N modules you can use half the channels at 1Gs/s or a quarter of the channels at 2Gs/s. There may be restricitions depending on the number of channels you have. You can download spec sheets from the modules. Those should tell you about the half/quarter channel configurations.

author: bench_knob
author_rank: Regular Contributor
timestamp: April 01, 2014, 05:38:20 am
content: Quote from: TiN on March 27, 2014, 08:04:12 amTiN & NctNico,I spoke with RFdes, he has his TLA704 running server/client TCPIP network working but said that its tricky to get things running. It would help if the Tek docs offered more value than toilet paper. RFdes told me that the server (TLA mainframe) software must be EXACTLY the same install version as the client side software, apparently the code is slightly different (silent builds?) between released versions.In any case I've seen a strange thing on my two units, the network connections are acting oddly, maybe I don't understand how to configure things?The TLA mainframe (133MHz, 128MB RAM, Win2k SP4) is running TLA App5.1, while the client is a 2.4 GHz, 4GB RAM laptop with WinXP Pro, SP3 on which TLA 5.1 App software has also been installed. The server is the TLA mainframe and the client is the laptop. I have a 100MBps 3COM EtherNet PCMCIA card installed in the TLA mainframe, and the laptop, an HP has an embedded 100MBps 3COM EtherNet port. The two machines are talking to each other through Cat5E cables into a Cisco 100MBps switch.I have configured the server (W2K) Network ID Workgroup as 'DEVNET', and the TCPIP is, 100.000.000.010, while the client's (WinXP) Workgroup is set to: 'DEVNET', and the TCPIP is: 100.000.000.011. I've shared a folder on each machine, one on the server, and the other on the client, which appear correctly on each of the other machine's network tree. As I said before, I am able to transfer files between machines, but still the client Instrument Manager does not see the TLA VXI instrument list through the network (via the switch) and neither does the client TLA app see it either.Something screwy is happening. I can transfers files between the shared folders with ease, but I can't map network drives. And popping into the cmd shell, running IPCONFIG on either the server or the client machine shows the correct TCPIPs, yet, when I ping either machine from the other, using their TCPIP address, it fails, AND, the TCPIP number is CHANGED by the system, its not the octets that I entered? What M$ magic is this? I enter, 'ping 100.000.000.010', on the 100.000.000.011 machine, and the OS changes the number to: 100.000.000.008 and fails. If I change the ping destination octets to ...008, it pings just fine, but that's not the address that's been assigned to the machine? Both machines exhibit similar behavior.I'm confused.Anyone got a clue whats happening?Thanks in advance,bench knob

author: TiN
author_rank: Super Contributor
timestamp: April 01, 2014, 05:56:33 am
content: QuoteSeem you have network setup issues.I have mapped drive from TLA no problems.Dont use any firewalls / AV software which can lock your network if.I have TLA app 5.1 on frame (but i use TLA714), and using different workstations with TLA app 5.8, 6.0 and 6.1. No issues, as soon as I close TLA app on mainframe itself (i.e. screen on TLA714 is just showing desktop) and enable TLA server app (yellow thingy near clock on taskbar)

author: nctnico
author_rank: Super Contributor
timestamp: April 01, 2014, 04:20:35 pm
content: First change the IP adresses to a private range: 10.x.x.x, 172.x.x.x or 192.168.x.x which is used by your router. Chances are your routers is routing traffic for these addresses onto internet.

author: bench_knob
author_rank: Regular Contributor
timestamp: April 02, 2014, 12:22:45 am
content: Quote from: nctnico on April 01, 2014, 04:20:35 pmHi NctNico,I forgot to mention that the switch is only connected to the server and the client machines, nothing else is attached. But, I'll try the 10.x.x.x addr for the heck of it. I do have installed a Norton antivirus SW on the client/laptop, but I have it disabled.bench knob

author: nctnico
author_rank: Super Contributor
timestamp: April 02, 2014, 12:47:03 am
content: Yeah. You need to get the network sorted first. IP addresses changing automatically is not a good sign. Make sure you can ping from one machine to the other and vice versa. If that doesn't work you have to fix the network first. Maybe you have duplicate IP addresses.

author: bench_knob
author_rank: Regular Contributor
timestamp: April 03, 2014, 07:41:32 am
content: Quote from: TiN on April 01, 2014, 05:56:33 amTiN,Something happened to my reply to you last evening? Anyway, that's interesting regarding the versions, I've heard the story from others having versions mismatch problems...maybe its not the software so much as its the TekVISA SW?Re; network, yep I was having network problems, but I've got that part working now, mapping drives, sharing folders and pinging. Heh, here's a trick question for y'all...do you know the difference between these two pings?ping 072.000.000.010<cr>andping 72.0.0.10<cr>As I understand things, nothing, except, apparently Macro$haft programmers don't know how to correctly parse strings. When I ping using the first string, the ping parser returns the wrong octet numbers, that is what was changing the numbers and was causing the ping connection failure that I last reported.In any case, I can now map drives and am having no problems transfering files back and forth but there is still a problem.I autostart the TekVISA server on the TLA704 'frame. I run the TekVISA Call-Monitor also on the 'frame' and then I run the Instrument Manager on the laptop, which does not see the network or the frame apparently, as my clicking the UPDATE button returns an empty INSTRUMENT-LIST, while on the frame, the Call-Monitor indicates that there is some network activity, apparently well enough to enable the software to interpret the commands but it emits error messages. I'm including the frame Call-Monitor log data for y'all's perusal. The main error message says that there is 'insufficient instrument location information'? I've included a blab at the top of the log file for clarity.The error message was triggered in TLA V5.1 App running on the laptop,Files > Select TLA > TLA704 (remote)<cr> This is what generated the error message on the TLA frame server.I uninstalled the TLA 5.1 App on the laptop tonight, and am currently re-installing using the exact same version that I installed on the frame....I don't what the problem is, so I'm shot-gunning...wasting a lot of time shooting in the dark hoping to drill it, heh heh.One last urge....what the hell is the deal with the TLA7PG (which I don't have), appearing in the VXI Instrument-List? Tektronix marketing? Isn't that program supposed indicate the modules that are installed in the VXI module-cage, rather than indicating ghost modules? How can ya trust software that works like that? Tek programmers smok'n crack?thanks in advance,bench knob======= TLA Frame TekVISA Call-Monitor Log Data =======TLA704 Frame (Win2k): Log Generated by TekVISA Call-Monitor running, TLA7M3 Module installed in slot 1&2, 3&4 blank. Server started, but the TLA app isn't running.Laptop (WinXP Home Ed): TLA App v5.1 running. The two machinesare connected together through a Cisco 100MBps switch via TCP/IP.14/04/02 8:49 PM 17.0344 0.0824s viOpenDefaultRM(0xbd4c20)14/04/02 8:49 PM 20.0078 2.5236s viOpen(0xbd4c20, "GPIB8::1::INSTR", 0, 0, 0x0) - (0xbfff0011) "Error - Insufficient location information or resource not present in the system"14/04/02 8:49 PM 20.0158 0.0006s viClose(0xbd4c20)14/04/02 8:49 PM 20.0258 0.0141s viOpenDefaultRM(0xbd4c20)14/04/02 8:49 PM 22.0872 2.5126s viOpen(0xbd4c20, "GPIB8::1::INSTR", 0, 0, 0x0) - (0xbfff0011) "Error - Insufficient location information or resource not present in the system"14/04/02 8:49 PM 22.0992 0.0006s viClose(0xbd4c20)14/04/02 8:49 PM 23.0113 0.0142s viOpenDefaultRM(0xbd4c20)14/04/02 8:49 PM 23.0243 0.0155s viFindRsrc(0xbd4c20, "VXI0?*", 0x134f690, 0x134f588(1), "TLA7M3")14/04/02 8:49 PM 23.0363 0.0006s viClose(0xbd5ca8)14/04/02 8:49 PM 23.0603 0.1203s viOpen(0xbd4c20, "TLA7M3", 0, 0, 0xbd5ca8)14/04/02 8:49 PM 23.0774 0.0136s viParseRsrc(0xbd4c20, "TLA7M3", 0x134f7ac(20247944), 0x134fea4(20248684))14/04/02 8:49 PM 23.0924 0.0173s viFindRsrc(0xbd4c20, "VXI0?*", 0x134f690, 0x134f58c(1), "TLA7M3")14/04/02 8:49 PM 24.0094 0.0006s viClose(0xbd9200)14/04/02 8:49 PM 24.0645 0.0956s viClose(0xbd5ca8)14/04/02 8:49 PM 24.0815 0.0005s viClose(0xbd4c20)

author: eurofox
author_rank: Unknown
timestamp: April 04, 2014, 04:22:24 pm
content: I have an option to buy a TLA714 running Windows 95All cable/pods included.I suppose it is a very old versionPlease advise buy or not for 100 Euros?eurofox

author: nctnico
author_rank: Super Contributor
timestamp: April 04, 2014, 10:57:21 pm
content: You can always upgrade to Win2k. IMHO €100 is a very good price. I'm almost tempted to wish for such an opportunity myself.

author: bench_knob
author_rank: Regular Contributor
timestamp: April 04, 2014, 11:17:10 pm
content: Quote from: eurofox on April 04, 2014, 04:22:24 pmHi there, if 100 Euros is anything similar to $100 US Bucks, I'd go for it myself, as I've just expended four years and around $1500 US Bucks to cause my TLA704 to mimic (make it act like) a TLA714, hah!You can easily, for little or no additional monetary expense, upgrade the software on the TLA714 from Win95, using Windows 2000 Pro version OS and install Tektronix TLA App version 5.1 software (free download on Tek Website). You'll likely need to increase the amount of RAM installed, (i think on the 714 it'll go upto 256Mb RAM?), install the OS, install the TLA App software and voila! You'll have yourself a nice modern really kewl logic analyzer with many advanced features. If ya got the burritos...go for it!!Just my two centavos...bench knobps..what sampling modules are in it?

author: TiN
author_rank: Super Contributor
timestamp: April 05, 2014, 04:57:42 am
content: 100euro is decent price.I paid 1K$ for mine 714 (just a frame, no modules)You can junk original OS, install Win2000, update firmwares, just like I did and you will get quite good deviceto play with. TLA software is somewhen user unfriendly, but if you know it's caveats, it will work.And you can use not so bad 7AA4 modules in TLA714, which able to capture at least 400MHz and have neatiView analog switches to your hi-speed scope714 runs Pentium MMX266 embedded, (skt7) and have 2 SO-DIMMs, but chipset cannot address dualrank modules.So I have 2x256MB in mine, and only half of memory detected and works. Still okay, as I use TLA only remotely.

author: Mark_O
author_rank: Frequent Contributor
timestamp: April 05, 2014, 06:02:49 am
content: Quote from: TiN on April 05, 2014, 04:57:42 amYeah, I like the iView on the TLA7AAx modules. Those aren't compatible with my TLA704 though, or are they?

author: eurofox
author_rank: Unknown
timestamp: April 05, 2014, 08:44:51 am
content: Quote from: nctnico on April 04, 2014, 10:57:21 pmYou got a PM in our "common language"with the email address of the person.eurofox

author: nctnico
author_rank: Super Contributor
timestamp: April 06, 2014, 12:57:21 am
content: Actually it is a TLA704 for €100 not a TLA714. Nowadays €100 is about $135 BTW@Mark_O: If you install software version 4.4 (or later) you can use TLA7AAx modules in your TLA704 mainframe. And yes the iView feature is really useful.

author: Mark_O
author_rank: Frequent Contributor
timestamp: April 06, 2014, 02:13:15 am
content: Quote from: nctnico on April 06, 2014, 12:57:21 amBut, "All cable/pods included" increases the value quite a bit. I've seen cable sets going for $200 each.QuoteThanks, Nico! That's good to know, and I'll keep it in mind.I don 't have a big need for iView currently, because I already have a 7E2 analog module in my primary 704 frame. But iView would be handy in my other frame. I could pull the 7M3 module there, and make space for a 7AAx.

author: bench_knob
author_rank: Regular Contributor
timestamp: April 19, 2014, 01:22:17 am
content: Quote from: bench_knob on April 03, 2014, 06:41:32 PM>Quote from: TiN on April 01, 2014, 04:56:33 PMbench knob said>QuoteTin saidQuotebench knob saidQuoteTiN,Hah! Well I finally got my laptop talking to my TLA704 logic analyzer...it was gruesome. I have no idear how I made it work? I tried everything, I spent weeks reading Macro$haft KnowledgeBase articles, and surfing the InterNet/YellowPages(tm)(c)(drm) searching for **FREE** information, and plodding through Tektronix marketing info. <ehhh>Initially I thought that I had a network problem, as the TekVISA/VXI-11 client-server was not communicating between the laptop (via EtherNet switch) and the TLA704 mainframe. But that then I realized that there was something else screwy that was happening, because, hah, I could map drives and pass files back & forth, but not ping? That 'problem' turned out to be a software bug, in my opinion, in the venerable Macro$haft 'ping' program. I mean, what's the technical difference between these two octet strings?192.168.001.030 and192.168.1.30Technically nothing, at least not according to any of the TCPIP books I've ever read, its just considered bad 'form' to under-populate octet entry fields. But in Macro$haft code, it misparses the information and passes the wrong numbers!!In other words, this number passed to ping.exe as:ping 192.168.001.030<cr> actually passes:192.168.10.40!! Yep, that number didn't ping.But that wasn't the problem, I got rid of the WinXP Home Edition, went out and bought a new WinXP Pro SP3 OS, installed it into the laptop, checked dotNet versions, etc. And the client/server comm still didn't work. Then I got in and started fiddling around with file permissions, finding a bunch of stuff that wasn't enabled. Something in the permissions, I think.Long story short, it works, but it was gruesome 'tho.I'm thinking that Cisco switch might be a bit slow, while the remote operation is significantly faster, things such as large memory acquisition 'processing data' still takes a bit of time and its a pain. Whats it gonna be like if I got 8Mb acquisitions? Or if ya count the negative edges on a 16K acquisition? I had hoped it would be much faster.Anyway, its working. <whew>Thanks for your comments.bench knob

author: nctnico
author_rank: Super Contributor
timestamp: April 19, 2014, 01:34:21 am
content: IMHO the way the software is written is just slow. I have a feeling they are doing everything in one loop which is executed a few times per second. In each loop iteration they process a part of the samples. This keeps the CPU load close to zero and the user wait for nothing

author: M!TYA
author_rank: Newbie
timestamp: July 26, 2017, 05:07:43 pm
content: Hello.I have TLA 714, software v 4.4, TLA7P2 (FW Ver 4.3.14), Windows 2000.When I install the software version 5.1, the program does not see the module (Runs only offline), how can I fix it? Firmware version 5.8 does not help...

author: nctnico
author_rank: Super Contributor
timestamp: July 26, 2017, 05:55:27 pm
content: Quote from: M!TYA on July 26, 2017, 05:07:43 pmVersion 5.x doesn't support the TLA714 so you need some cleverness. You can download and install version 5.6 of the software. For this you need to get a program to unpack installshield files (like uniextract) and then replace setup.inx with the setup.inx from the attached zip file. This should get the software installed. Beware though that your logic analyser is probably too slow to run this software and it is better to run use the mainframe remotely from a PC.

author: M!TYA
author_rank: Newbie
timestamp: July 26, 2017, 07:42:56 pm
content: Quote from: nctnico on July 26, 2017, 05:55:27 pmThanks for the response and help!After the file is replace:This TLA software release is not compatible with the operating system on this system. (Error in Ver 5.1 and ver 5.6)Without replacing file, installation begins.Requires installation the Windows XP ?

author: nctnico
author_rank: Super Contributor
timestamp: July 26, 2017, 09:28:11 pm
content: You might need XP indeed.If the software doesn't detect a TLA mainframe it can install itself on you get the standalone version of the software for remote control or offline usage.

author: M!TYA
author_rank: Newbie
timestamp: July 31, 2017, 10:03:08 pm
content: After update on this instructionhttps://doc.xdevs.com/doc/Tektronix/TLA/TLASWDOWN_V51SP1.pdf, driver PCI-VXI was deleted...Does anyone have a driver PCI-VXI ?Reinstalling the program version 4.4 did not help"Unable to open PCI-VXI bridge driver, Error code: 2"

author: M!TYA
author_rank: Newbie
timestamp: August 03, 2017, 06:26:37 pm
content: The problem is solved!LTA 714, TLA7P21) Format c:/2) Install Windows 2000 SP4, English3) Install TLA APPLICATION SOFTWARE V5.1 SP1 (https://xdevs.com/doc/Tektronix/TLA/TLA_V51SP1.exe)4) Install driver PCI-TLA_Bridge_V51 (https://xdevs.com/doc/Tektronix/TLA/PCI-TLA_Bridge_V51/)All works =)Thank you all for your help!

author: nctnico
author_rank: Super Contributor
timestamp: August 03, 2017, 07:08:37 pm
content: The TLA7P2 is interesting. Do you also have the probes for this pattern generator module?

author: M!TYA
author_rank: Newbie
timestamp: August 03, 2017, 09:23:51 pm
content: I have a version TLA7P2, not TLA7P2G, there is no generator, or am I mistaken?Only Tektronix P6418 probes, can make by yourself.

author: dxl
author_rank: Regular Contributor
timestamp: August 03, 2017, 09:24:30 pm
content: Quote from: nctnico on August 03, 2017, 07:08:37 pmTLA7P2 is something different - it's a 16MB Acquisition module which uses the P6417/P6418 probes. The pattern generator modules are called TLA7PG2...

author: nctnico
author_rank: Super Contributor
timestamp: August 04, 2017, 04:00:07 pm
content: Quote from: M!TYA on August 03, 2017, 09:23:51 pmYes, my mistake. I have been looking for a TLA7PG (pattern generator module) for a while and forgot they also have a P model acquisition module.BTW: I'm pretty sure there is a passive divider circuit at the end of the probes so making your own probe isn't as trivial as it looks.

author: M!TYA
author_rank: Newbie
timestamp: August 04, 2017, 04:53:22 pm
content: Yes, you are right!There are resistors 20k.

author: alm
author_rank: Super Contributor
timestamp: August 04, 2017, 05:25:30 pm
content: Plus I imagine a few pF (parasitic) capacitance engineered in parallel to compensate the divider. Does Tektronix publish a schematic for designing termination into your boards like HP did? In the case of HP, the schematic was some small amount of resistance in series with a 90 kOhm resistor in parallel with a small value cap.

author: spymac
author_rank: Contributor
timestamp: July 23, 2025, 04:26:20 pm
content: I have recently acquired a TLA714 from eBay for a good bargain, and as a cool project to get it running. I have a few notes about things that I encountered along the way. Hopefully others will find this helpful.I bought a unit that was physically in rough shape, it had a broken screen and no hard drives, etc. I meticulously took it completely apart and cleaned everything, looking for bulged caps and any other issues inside. Note that the screws are all T15 Torx, #6-32, but there areseveral different lengthsused in this unit, and it isn't noted in the service manual which length goes where! So be sure to keep track of that. Once I realized this, I used a fine-point sharpie and wrote the length next to each screw location.The unit came with a TLA 7N3 instrument module, which has 102 digital inputs. The module uses T10 screws and 1/4" hex standoffs inside. This has the IDC-style connectors, which is the same as a floppy drive ribbon with no missing pins. However, my connectors were corroded all green inside. I got the corresponding replacement connectors from Digikey. I removed the old connectors by using a small solder pot and masking the nearby stuff with cheap knockoff capton tape. The connectors removed easily without damaging the holes this way, but moisture in the PCB did cause some minor bubbling of the board. (This may have been avoidable by drying the board in a low-temperature oven for a while.) Removing the remaining solder from the holes, I used a #59 drill bit and a small pin vice to drill out the solder manually. This worked well and did not cause any visible damage the thru-holes. When I soldered in the new connectors, it helped the soldering a lot when I lightly brushed the pads with a fiberglass brush. The connectors were maybe 1mm longer than the original ones, so I carefully sanded them down without contacting the tips of the pins inside. The module contains one of those damn Dallas SRAMs with the built-in battery. I have no idea what it is used for but I'm sure it's dead by now.Everything else in the Logic Analyzer was in OK condition; it was just very dirty and the chassis was bent here and there. Just cleaning and pounding to get everything back into shape. The CMOS battery on the motherboard was dead and it is a strange one, BR2335. It is probably possible to change the holder to a normal CR2032. It starts up and runs fine with the dead battery and an external monitor (since the internal monitor is still broken).The unit has 2 hard drive bays that hold 2.5" laptop hard drives. There is an internal one behind the screen that takes an IDE/PATA 2.5" drive, and there is also a slot for another IDE/PATA drive that is removable from the outside. The sled contains a small ribbon adapter, and though the sled's connector looks like SATA, it is NOT. My unit didn't come with a sled, so I found an old 12GB PATA drive and I put it into the internal slot.When I started installing Windows 2000 SP4, I found that this hard drive always got stuck formatting at 69%, which corresponds to 8 GB. There is an option in the BIOS settings for "large disk support", and I tried it both ways and it still got stuck. So I made an 8000MB partition on the drive, leaving the rest unallocated. That made the drive work and I was able to successfully install Windows 2000 and it booted up. I did NOT try the slot for the external sled, so it is possible that the internal one has an 8GB limit and the sled doesn't have that limit. When the unit first turns on and does its memory checks, etc, it does mention the revision "2.03.11", and this page lists that revision as the latest BIOS for the TLA 714:https://www.tek.com/en/datasheet/tla700-seriesSo my theory is that there is just an 8GB limit on the internal PATA slot. (The 8GB limit was mentioned earlier in this thread with different people having different experiences.)Anyway, I went into the Windows device manager and found the 1 item that didn't have a driver. I updated the "PCI-TLA_Bridge_V51" driver mentioned earlier and it was successful.Soft Power: I did have the issue where Windows 2000 displayed the message "It is now safe to turn off your PC" after choosing Shutdown, rather than shutting itself off using the soft power properly. I fixed it this way: Control Panel -> Power Options -> APM Tab -> Enable APM (checkbox). I enabled it and that fixed the issue. I hadn't seen this solution mentioned in this thread yet.I installed TLA software v5.1 and it installed and ran fine, but it did not detect the TLA 7N3 instrument module. So I uninstalled that and put v4.4. This version did detect the TLA 7N3, but it told me that the firmware needed to be updated. So I went into the firmware update utility, and I found that it was listed in the section "Devices that CANNOT be updated". But not to be discouraged, this only means that you have to put the module into factory mode in order to do the update. I shut down the logic analyzer, removed the module, and inserted a jumper on the 2-pin header, reinstalled, and then I was able to do the firmware update. I shut it down again, removed the jumper, started it back up, and everything worked with v4.4. I am guessing now that I have done that, v5.1 may have potential of working now but I haven't tried that. So basically I have a working logic analyzer with an external screen and the internal screen is still broken.I have 2 16-channel probes, model P6417, which do look a lot different the ones pictured earlier in this thread. However, I measured and they also have the 20k series resistors on the end of the cables farthest away from the logic analyzer. The clock connections (CK0, CK1, etc), also have the 20k.So now I am working on the screen. I got a similar 800x600 LCD, Sharp LQ10DS05. This has the same data connector but a different pinout. I tested using a continuity tester to find the pattern of ground pins. Referring to this:https://datasheet4u.com/pdf-down/L/Q/1/LQ10PS21_QUADRANGLE.pdfThe TLA 714 uses the pinout of the right-most column:GND-----12----CKGND-----34----GNDHSYNC---56----VSYNCGND-----78----R0R1------910---R2R3------1112---R4R5------1314---GNDGND-----1516---GNDG0------1718---G1G2------1920---G3G4------2122---G5GND-----2324---GNDGND-----2526---B0B1------2728---B2B3------2930---B4B5------3132---GNDGND-----3334---GNDENAB----3536---VCCVCC-----3738---TST;R/LTST;U/D-3940---GNDGND-----41And the LQ10DS05 uses the other pinout:GND-----12----CKGND-----34----HSYNCVSYNC---56----GNDGND-----78----GNDR0------910----R1R2------1112----GNDR3------1314----R4R5------1516----GNDGND-----1718----GNDG0------1920----G1G2------2122----GNDG3------2324----G4G5------2526----GNDGND-----2728----GNDB0------2930----B1B2------3132----GNDB3------3334----B4B5------3536----GNDENAB----3738----R/LVCC-----3940----VCCTST;U/D-41The LQ10DS05 is almost a perfect fit and it even uses the same high-voltage backlight connector. I got the 41-pin male and female data connectors on digikey and made an adapter, however nothing worked! The backlight did not turn on. The original screen used all 3 connections, apparently for 2 bulbs. The new one only has 1 bulb. So it might need some tricking to get it to turn on. But more concerning, even using a flashlight on the panel, the image is all screwed up. It fills in lines of garbage at a slow and inconsistent rate starting from the top and working its way down. So this makes me think there is something wrong with the sync and/or clock signals. Maybe it uses different logic levels or a different VCC! I have no idea because there is very little documentation for this stuff. It is also possible that the new screen doesn't work, though it is brand-new old stock. I believe that the original screen was RGB666 format, 800x600 resolution on the TLA 714 model as well, so I wasn't really expecting any problem directly wiring up that adapter the way I did. If anyone has ideas from their experience with LCDs and anything like this happened, I would love to hear it. Anyway, that is the only part I have not solved and I can get by with the external VGA screen.Edit:I took some measurements of the LCD connector when the unit was in POST with no screens attached. (It sits and waits for me to press a button due to a bad CMOS battery.)V Sync:51.3 Hz.Positive pulse width = 32 usec (It's high for 1 full period of H Sync.)Logic levels 3.3V / 0VH Sync:32.23 kHz.Positive pulse width = 3.77 usecLogic Levels 3.3V / 0VClock:34.13 MHz, sine wave (My scope was using 500 MHz bandwidth.)High Peak = 2.2 ~ 2.6VLow Peak = 560 ~ 720 mVVCC: 3.5VIf I divide H Sync by V Sync, this gives the approximate number of scanlines (to include the V-blank area). 32230 / 51.3 = 628.27. So this basically confirms that the TLA714 model scope is naturally putting out 800x600resolution. So I think this looks OK.The clock is kind of concerning. I am guessing that the low level might be too high to be considered low by the new LCD. Should I make some attempt to buffer that signal or find a damaged buffer on the PCB and replace it? Or does that sound normal for an LCD clock signal?Edit:I also tried inverting the H Sync and V Sync signals using a 74LVC2GU04 that I had available. This did not make it work. I guess I don't know enough about the new LCD; there could be a number of things other than resolution that it doesn't like. Such as refresh rate, polarity of sync signals, polarity and logic levels of the clock signal. Since I can't find a datasheet for the new LCD, I will probably have to keep guessing and experimenting.