TLA7xx App Software and Firmware Upgrades beyond 5.1  ??? - Page 1
Forum section: electronics / testgear

author: Sailor
author_rank: Regular Contributor
timestamp: February 07, 2015, 06:32:37 am
content: As owners of TLA7xx LAs will know, Tektronix list the last supported versions of the TLA App S/W as 4.4 for the 714/720 and 5.1 SP1 for the 715/721. Yet I read here of people running later 5.x and even 6.1 on these machines. Are there specific issues when running the later versions, or is it just a case of memory and CPU limitations making the later s/w slow, or ...The reason I ask is that I am only now starting to come to grips with my TLA715 that I bought last year. I've max'd the memory to 512MB (wow) and installed a second disk, and I have 5.1 / XP running on the LA and on my remote PC. The networking seems to run ok.Reading 'Tektronix-Logic-Analyzer-Online-Help-Printed-Help-Document.pdf' which appears to be for the later s/w versions, it seems there are differences in window layouts and terminology (e.g. 'Compound Clocking'), but I'm wondering if there are any significant functional benefits to be had by upgrading the 715 s/w? Conversely, are there any downsides? I see that I would have to upgrade the firmware in my analyzer modules (TLA7AA2 and AA4). If I did upgrade everything, are there known circumstances where I may want to revert to 5.1, and if I did downgrade is it necessary/possible to downgrade the module firmware?Finally, I've seen comments about the need to have the same App s/w versions on the LA and on the remote computer. Is that a hard and fast requirement, or is it one of those 'it seems better' type of things?A lot of questions, I know, but I would rather learn from others than by hard experience.

author: nctnico
author_rank: Super Contributor
timestamp: February 07, 2015, 10:39:13 am
content: The software is slow no matter how fast the CPU is. It is possible to install version (IIRC) 5.1 with hacking the installer.Upgrading/downgrading the firmware in the modules is an easy process compared to installing the other software.

author: Sailor
author_rank: Regular Contributor
timestamp: February 07, 2015, 12:09:29 pm
content: Thanks for the reply. I already have 5.1 running with no problems (apart from being slow, especially the Measurements section). I was wondering if there are any particular benefits to upgrading the App s/w? If I subsequently want to go back to 5.1, it's good to know that the module firmware can also be set back to the original version. I have had things in the past that could only ever be upgraded, with no way of going back!

author: TiN
author_rank: Super Contributor
timestamp: February 07, 2015, 03:44:41 pm
content: As 714/7AA4 owner, found best myself with 5.1 on frame as server app (TLA Gui dont even have to be running, just server app) and network connection to TLA App 6.1.127 on my WS. 6.1 is nicer/more stable and little faster on remote machine, than 5.1 was. Also there are no support of old modules like 7Nx/7Mx/etc since 5.1, but it does not bother you as you have AA's.There is a bug in TLA app software, if you have used over 8Gig of RAM on your machine, App will show lack of resources errors and will be unfunctional. 6.1.127 have it , older version have it. I did not found workaround for it.

author: Sailor
author_rank: Regular Contributor
timestamp: February 07, 2015, 11:30:04 pm
content: Thanks for that TiN. Am I correct in assuming that your server code on the TLA is the standard v5.1 version? And it plays nicely with 6.1.127 on your remote machine? I'll certainly give that a try.Is there any functional change/improvement with the 'Compound Clocking' setup that isn't present in the Advanced Clocking of 5.1? Or is it just the marketing guys wanting something new to talk about?

author: avics
author_rank: Newbie
timestamp: April 02, 2019, 09:52:23 am
content: Quote from: TiN on February 07, 2015, 03:44:41 pmI also ran into the lack of resources on my Win 10 with TLA 5.8. Since it bothered me I took out IDA Pro and found the place of the message. I looked a bit further and ended up patching the binary to allow larger upper values for total_GDI_Object, GDI_Object Quota, total_USER_objects and the HandleHighWaterWarning.These internal values cap off the registry settings for GDProcessHandleQuota, USERProcessHandleQuota, HandleHighWaterWarning.These are the values before the change:.data:00BAB37C gtotal_GDI_Objects dd 58981 ; DATA XREF: CSystemMonitor__CSystemMontor+29↑r.data:00BAB380 gGDI_Objects_Quota dd 13925 ; DATA XREF: CSystemMonitor__CSystemMontor+47↑r.data:00BAB384 gtotal_USER_Objects dd 7200 ; DATA XREF: CSystemMonitor__CSystemMontor+33↑r.data:00BAB388 gHandleHighWaterWarning dd 52428 ; DATA XREF: CSystemMonitor__CSystemMontor+4F↑rand these are the values after the change..data:00BAB37C gtotal_GDI_Objects dd 124517 ; DATA XREF: CSystemMonitor__CSystemMontor+29↑r.data:00BAB380 gGDI_Objects_Quota dd 79461 ; DATA XREF: CSystemMonitor__CSystemMontor+47↑r.data:00BAB384 gtotal_USER_Objects dd 72736 ; DATA XREF: CSystemMonitor__CSystemMontor+33↑r.data:00BAB388 gHandleHighWaterWarning dd 117964 ; DATA XREF: CSystemMonitor__CSystemMontor+4F↑rMaybe this helps. At least I don't get the message any more and the TLA app seems to work.Simply changing the resources (see code snippets) didn't work as the TLA seems to maximize the allowed values.