Author Topic: How to remotely control a Tektronix TLA715 Logic Analyzer under MS Win 7  (Read 3798 times)

0 Members and 1 Guest are viewing this topic.

Offline THDplusN_badTopic starter

  • Regular Contributor
  • *
  • Posts: 160
  • Country: de
Good Day,

The TLA715 and other Logic Analyzers can be remotely controlled via LAN from a PC, using Tektronix' TLA700 Software.

However, I have found a few postings here and in other forums where a remotely-connected PC fails to detect the Logic Analyzer modules installed in a TLA704/714/715/721. See below how I have fixed this problem.

Cheers,

THD+N_bad

Failure symptom:

  • TLA700 Software connects to the TLA mainframe, but only detects the mainframe itself
  • The TLA700 software fails to detect any Logic Analyzer modules installed, although these are properly installed. The TLA server application on the mainframe detects the remote connection flawlessly.

I have encountered similar issues, and have found the following solution.
Remote PC runs OS MS Windows 7 Enterprise 64-bit.

I finally, finally got Tek TLA release version 5.8.151.0 working after these modifications.

  • Installed TLA release version 5.8.151.0 on the remote PC, then copied all files from the new Firmware folder to the local TLA715.
  • Then used the Firmware loader to upgrade the TLA7N4 Firmware to release 5.5.001.
  • Changed MS Windows Firewall settings to allow *all protocols* and *edge traversal* of packages for the TLA application and TekVISA and related tools. Screenshot included below.
  • I had to change the TLA700 settings for "TLA network search" to the pure TCP/IP address, i.e. no friendly name, see screenshot.
  • I still have to toggle between offline operation and the TLA715 system after starting the TLA700 software, but it detects the module reliably now. Very happy, after all...
« Last Edit: December 16, 2017, 12:30:40 pm by THDplusN_bad »
 

Offline papafuse

  • Newbie
  • Posts: 1
  • Country: us
THD, I've spent a few hours following your instructions. Thanks for posting them! Your instructions got me running.

My TLA715/7AA4 is running XP with version 5.1 application.

Following your advice, I installed TLA App 6.1.127.0 on my Windows 10 PC. I copied this newer /Firmware folder to the TLA715, after renaming the existing /Firmware folder on the '715 to "Firmware_5_1" to retain the original. After this swap, I updated the 7AA4 module to version 5.8.

I followed your advice, opening the Advanced Firewall in Windows 10 and allowing edge traversal and all private permissions for the TLA application, TekVISA, and tlnkmonsvc .exe's. It seems these three are all that were needed.

On the Windows 10 PC, in the newer TLA App, entered in the IP address I'd assigned to the TLA715. Like you said, automatic assignment did not work; the app would locate the TLA715 but not its modules. Static IP is necessary.

I found that running the TekVISA app and clicking "update" was a faster method to test the LAN connection while trying to make it work. When I got it right, the TekVISA will recognize the TLA715 and its 7AA4 module.

Thank you very much for your post! I am very happy running the TLA Application on Windows 10 on the same PC I am coding the FPGA  :D

Another thread on this forum taught me how to unlock the 450MHz / 32MB capacity of the 7AA4 module. How awesome is that!

Thank you,

papafuse
« Last Edit: March 20, 2018, 07:16:54 am by papafuse »
 

Offline THDplusN_badTopic starter

  • Regular Contributor
  • *
  • Posts: 160
  • Country: de
Good Day,

THD, I've spent a few hours following your instructions. Thanks for posting them! Your instructions got me running.

[..]

Thank you very much for your post! I am very happy running the TLA Application on Windows 10 on the same PC I am coding the FPGA  :D
[..]
Thank you,

papafuse

papafuse, you are most welcome. I am always glad to help and it is great to hear that you got an even newer TLA Application release version 6.xyz running under "the latest OS" Windows 10!
I suppose this is a great example for the use of some older equipment such as the TLA715 even today. Very happy for you.

Cheers,

THDplusN_bad
 

Offline rl78family

  • Newbie
  • Posts: 9
  • Country: ua
Hello!
I recently purchased a TLA714 and a TLA7N3 capture module.
Modifications:
- I changed the motherboard to the one removed from the TLA721 module
- Added cooling (heat pipe and a cooler) from a Asus z99h laptop
- Just in case, I flashed BIOS 1.00.02 (it was the same version)
- Installed D-Link DGE-660TD Gigabit adapter
- updated TLA7N3 firmware to version 5.5.001 and unlocked access to 4Mb and 200MHz
- Installed IDE HDD from AppleTV gen 1 (Samsung 160Gb, model HM160HC). The disk is displayed incorrectly in the BIOS, but the boot goes smoothly and Windows sees the entire volume.
- Installed Windows XP SP3 + TLA SW 5.1

I want to use the logic analyzer remotely, from another computer running Windows 10 and control software version 6.1, but the software stubbornly refuses to see the TLA7N3 module, moreover: when connected remotely, the software shows that it has connected to a TLA7012 with 13 empty slots, although the software Power Flex and Firmware Loader from a remote computer work fine with the TLA7N3.

I managed to run this bundle of SW 5.1 on TLA715 + SW 6.1 on a desktop computer running Windows 10 a couple of times at the beginning of the experiments and the TLA7N3 module was seen and worked when controlled from the desktop, but after some experiments with TLA715 everything stopped working. Suspicious operations included updating the BIOS (but the version is the same) and reinstalling Windows XP (changed the file system type from FAT to NTFS, as it is more resistant to unexpected power outages).

I tried to install different software versions on a desktop computer: versions 5.6, 5.8 normally see the capture module in TLA715, versions 6.0, 6.1 do not see the module. Firewall configured, and even disabled during the tests.

So I have a few questions for those who have a similar bundle working:
1) Is the file system type (FAŠ¢/NTFS) important on TLA715?
2) Is it mandatory to run as a user named "Administrator" on the TLA715 or is it still possible to create a custom user and give it administrator rights?
3) Is it necessary to copy the capture module firmware file (TLA7NPQ.lod) to TLA715 if the module is already flashed with the correct version? In other words: does the *.lod file need only for flashing or for regular work too?
« Last Edit: June 11, 2023, 03:38:09 pm by rl78family »
 

Offline nctnico

  • Super Contributor
  • ***
  • Posts: 28429
  • Country: nl
    • NCT Developments
Did you start the TLA software with the 'run as remote server' option set? IIRC this is necessary to operate the TLA714 remotely. Additionally you'll need to update the module firmware to version 6.1 if you are going to use that remotely. With the local software running, there is no remote access possible. The TLA7012 is a demo mode with a simulated logic analyser.
« Last Edit: June 11, 2023, 03:23:13 pm by nctnico »
There are small lies, big lies and then there is what is on the screen of your oscilloscope.
 
The following users thanked this post: rl78family

Offline rl78family

  • Newbie
  • Posts: 9
  • Country: ua
Did you start the TLA software with the 'run as remote server' option set? IIRC this is necessary to operate the TLA714 remotely.
Yes, it's enabled, if you mean this setting:
1804157-0
Additionally you'll need to update the module firmware to version 6.1 if you are going to use that remotely.
TLA7N3 is an old module, there is no firmware for it in SW 6.1. I was installing SW 5.8 to be able to upgrade the TLA7N3 firmware to version 5.5.001.
Maybe I'll just get a more modern capture module.
 


Share me

Digg  Facebook  SlashDot  Delicious  Technorati  Twitter  Google  Yahoo
Smf