Remote TLA Client/Server SW? - Page 1
Forum section: electronics / testgear

author: bench_knob
author_rank: Regular Contributor
timestamp: April 24, 2014, 05:35:22 am
content: Ok...I've now got my TLA 5.1 App running, remotely over a 100 MBps TCP/IP network, which significantly improves usability of the TLA704 analyzer.)In any case, I was poking around on the Tek forum and bumped into a post by a fellow who, in reply to another feller, was asked if there's a way to turn off the software re-down-loading module data each time he zoomed in or out. The answering fellow said that Tek engineers had expended much effort to improve the update speed of the software, which is significantly improved with each newer TLA App version. So, if this is true? Which of the TLA versions are the best which run on WinXP? I down-loaded various versions over the past several years, which include:v5.6.754 TLA AppV5.7.046 TLA Appv5.8.151 TLA AppAny of the TLA scopesters here on EEVblog use any of these versions? Which is recommended? Are these faster than the v5.1, running via client/server?Thanks in advancebench knobedit: fix lexical..

author: TiN
author_rank: Super Contributor
timestamp: April 24, 2014, 09:38:28 am
content: I used v5.8.151, v6.0 and last few month on v6.1.127, which I believe is latest.It does not re-download anything if zoom in/zoom out, but does recalculate if move across trigger with lots of data.P.S. TLA714 with 5.1 server app.

author: bench_knob
author_rank: Regular Contributor
timestamp: April 24, 2014, 07:32:04 pm
content: TiN,Thx for the info, it is much appreciated, and nice screen grab of the I2C traffic...is that your I2C code doing it's stuff?bench knob

author: TiN
author_rank: Super Contributor
timestamp: April 25, 2014, 04:08:38 am
content: Yea, but it's not really mine, I stolen from web somewhere and adopted for my system

author: bench_knob
author_rank: Regular Contributor
timestamp: April 26, 2014, 01:18:48 am
content: Quote from: TiN on April 24, 2014, 07:38:28 PM>QuoteHi TiN,Since my TLA704 is running Win2k/TLA5.1, the frame is remotely controllable from a laptop which is running WinXP/TLA5.1. As I understand things, I can upgrade the laptop to run a more recent version of the TLA app because it is running WinXP. Can different versions of TLA App be running and still be remotely operable? In other words, the frame is running w2k/tla5.1controlled by laptop running WinXP/tla5.8. Is this doable? The Tektronix release notes say 'no'.I know that I asked this before, but the question was in a different context...do the older version modules, such as TLA7Lx & TLA7Mx work with the later 5.8 TLA App SW?Thanks in advance,bench_knob

author: TiN
author_rank: Super Contributor
timestamp: April 26, 2014, 07:46:41 am
content: Regarding TLA7Lx & TLA7Mx, honestly, no idea. I have only single 7AA4 here.Mine setup is same, 714 running Windows 2000Pro (usual genuine OS from MSDN) with TLA Application 5.1 installed on it. I use only server app to control frame remotely via PCMCIA Intel LAN card. On remote side it's Win2008R2 or Win7 x64 machines with TLA App 6.1. I have 5.8 before, and it updated my 7AA4 Firmware to 5.8. It still recognized and works when I tried to run TLA App 5.1 directly on frame.So ,as for software, why you just don't try it and tell usIt takes only 10 minute to find out, not that difficult as it may seem for beginner.P.S. Official vendor documentation often says "no" to many things, or just don't say anything. Understandable too, obviously vendor don't want to deal with hundreds of people asking support or question about their 20-year old gear.

author: bench_knob
author_rank: Regular Contributor
timestamp: April 26, 2014, 08:22:38 am
content: Quote from: TiN onTodayat 05:46:41 PM>QuoteTiN,>So ,as for software, why you just don't try it and tell us>It takes only 10 minute to find out, not that difficult as it may seem for beginner.I have little experience with Tek SW and I am somewhat reticent to just try things. Recently I upgraded some Atmel development software which did not work well as it was too buggy for my tastes, so I down-graded SW back to the older software version I had been using, which, to my surprise would no longer install. After weeks of technical support calls/tickets and dozens of hours of trying everything Atmel tech-support suggested, and after all that failed, several re-installations of my main development computer OS, and all the SVC packs, and updates, I finally was able to get back to work. Heh...I'll give it a whirl.In any case thanks for your time and tips, it is appreciatedbench_knob

author: bench_knob
author_rank: Regular Contributor
timestamp: May 09, 2014, 01:05:33 am
content: TiN and All,I apologize re; the length of this post.Short update version:Using a TLA7NQP or a TLA7Axx version series module along with TLA-App v5.xx sw series along with TCP/IP client/server enables reasonable and acceptable user interface performance when installed in the old Tektronix TLA704, and also likely in the TLA714 series logic analyzers.Long update version:Hah!To reiterate the current TLA704 configuration, --it is running Windows 2000 Pro and Tektronix TLA Application SW v 5.1, which required a TLA704 hardware modification involving replacing the 640x480 LCD panel for an 800x600 resolution panel, and also the BIOS flash ROM image required machine-language patching to enable the higher panel resolution. The TLA704 memory needed upgrading from 16MB Up to 128 Mb and the hard-drive upgraded from 800 Mb to 4 Gb. All of that was required to enable the TLA704 Windows 95 upgrade to Windows 2000 Pro installation which is the minimum level operating system requirement to enable upgrading the Tektronix TLA704 Application v3.2 software up to TLA App v5.1 software. The TLA App v5.1 installation had to be hacked to bypass the hardware readable model number trap to enable the v5.1 SW installation onto the TLA704 mainframe.The modifications are worth the effort to upgrade the software as the newer Tektronix software resolves bunches of Tektronix design problems and poor program architecture design. And incorporating TCP/IP client/server enables the old-slow, CPU processor speed crippled (133MHz) TLA704 mainframe to be operated remotely via networked Client software loaded onto a modern, high-speed laptop/workstation and higher resolution/size LCD screens. This resolves the problem of using the TLA704 mainframe directly with the power-hungry WinOS. TCP/IP EtherNet networking is afforded by upgrading from TLA v3.2 up to v5.1. This ability significantly improves the baseline user operability of the TLA704 analyzer.The 'new' after hw/sw modification TLA704 configuration was:-- TLA704 Mainframe running W2k/TLA-App v5.1,-- laptop was running WinXP-Pro/TLA-App v5.1 also,-- TLA704 and laptop connected together through a TCP/IP network 100Mbit Cisco Switch/hubHowever, in that configuration the TLA704 mainframe still ran terribly sluggishly slow? Although its performance had improved a little bit. Any acquisition configuration using larger than 64K of RAM, caused the TLA704 Win2k OS to virtually lockup. (How could Tektronix sell stuff like that? I'll bet their sales fell through the floor.) And then every operation is sluggish. I noticed that the TCP/IP network switch link indicators are constantly flashing since I upgraded to the TLA-App v5.1 software.At the time of my upgrade efforts, my TLA704 mainframe was stuffed with two modules, a TLA7L1 (64k RAM) and a TLA7M3 (512k RAM) which I cluelessly bought several years ago, although I successfully used them for various tasks. While doing one problem solving task I discovered neither of those vintage modules incorporated counter/timers, hah! Only module serial numbers above a certain age have those features included and of course the modules I have aren't in that series range! I only paid a $100 ea for those efin door-stops!So, as per TiN's coaxing, I upgraded the laptop software from TLA-App v5.1 to TLA-App v5.8, (my initial reluctance and concern was driven by the fear that it may not work because of the version mismatch between the TLA mainframe version and laptop version, eg, v5.1 versus v5.and there was a bit of monkying around required, but it installed successfully. Unfortunately the analyzer still was running like an old slow feeble dog, it was as bad as before. User ability was minimally acceptable provided that acquisitions used less than 128k of acquisition module RAM, and anything above that memory depth would virtually render the logic analyzer unusable. Don't even think about using the drag&drop measurements feature (which ALLWAYS defaults to DISPLAY mode if enabled and so if ya have a large record on the screen it locks up for over five minutes while crunching the data...how could they sell junk like that?)So, I asked around regarding how other's TLA704s are working, I just couldn't imagine anyone using any analyzer that ran so terribly? There had to be something that I was missing that was so blatantly obvious that no one mentions the details, and that Tektronix marketing works to suppress. So I went back to the Yahoo Tek forum and I began reading ALL of the archived posts relating to TLA704, 714, 715 series analyzers, and in one of the posts was mentioned the sluggish/data-crunching lockup issues. Yep. It turns out that it WAS A BIG marketing problem, 14 ~ 11ish years ago, and that Tektronix engineers worked very hard to resolve those issues. And the Tek fixes? Client/Server software and new module hardware architectures. The sluggishness was in part due to the way the TLA7L1..4 and the TLA7M1..4 modules internally processed the data and how it passed the data to the WinOS based mainframe. The newer modules, beginning with version TLA7N1..4, TLA7Q1..4, TLA7P1..4, while each are essentially the same analyzer modules, each model having deeper memory depths, they are radically different in their operation when compared with their older cousins, TLA7Lx & TLA7Mx modules. And then the TLA7Axx1..4, apparently introduced the PowerFlex 'feature' (pay for decryption key to unlock memory manufactured into the module so that Tek no longer need maintain different models simply having larger memory capacities and speeds) are also radically different in their architecture. Collectively these series modules are considerably faster than the 7L & 7M modules. It saved their marketing butts.So as a test, I bought a TLA7N4 module ($97 on eBay this week) in lieu of a TLA7AA4 as I have no cables for it while I have a complete set for the useless modules. And I can find no reasonably priced (for a hobbyist) flying lead P6810 cable-set for use with the TLA7AA1..4 module which are currently available for reasonable (hobbiest) prices. One vendor is selling a P6810 flying lead set for $6000, hah hah hah...I wrote him and told him he is creating a museum piece, heh heh. I would have preferred a TLA7AA4 instead, but I don't have the ca$h to buy all the cables that are also needed. Bottom line is that the TLA7N4 works GREAT!! And it has counter/timers too!I learned a bit of new info also. The TLA-App ver 5.1 provides various module FW (firmware) images for the various modules that work with the application version. Version 5.1 supports, at least for the TLA7NQP version modules, FW 4.1.., and so I presumed that TLA5.8 would also provide the same module models FW version level. Hah! Not true. TLA-App v5.8 provides FW v5.50 which is the version required to work with TLA-App v5.8, yet TLA-App v5.1 works just fine with the newer firmware, while only requiring FW v4.1 for its operation. I made the mistake of installing the 'new' firmware remotely from the laptop, which installed the local firmware image located on the mainframe, after I archived the TLA7N4's old firmware. Turned out to be the same version level as provided by TLA-App v5.1. Having to install/uninstall that back of the module flash-jumper is a pain.And another interesting Tektronix marketing feature is that the firmware files do not disclose version numbers either in the name structure or via the internal properties field of the filename, that would enable one to view internal file version number via the Properties page of the WinOS file utility WinExplorer.Cheers,bench_knobp.s. May 15, 2015, US Congress is pushing (voting) to revoke US Net-Neutrality...things such as YouTube, Skype, WikiPedia, free bulletin-boards are gonna get expensive if Net-Neutrality is squashed....

author: Mark_O
author_rank: Frequent Contributor
timestamp: May 09, 2014, 06:23:29 am
content: Quote from: bench_knob on May 09, 2014, 01:05:33 amThank you! I found that very informative. I appreciate all the effort expended.