Hardware and Software Requirements and Typical System Topology

Requirements:

• For any hardware and software requirements of the analyzer, refer to the Wireless Protocol Suite User Manual.

• TCP/IP network

The typical system topology includes one (1) server machine running one (1) instance of the analyzer application (reference the analyzer documentation for Windows Operating Systems requirements) and one (1) client machine running one (1) client application. The server, analyzer and client applications may all be run from the same machine.

The only requirement for the client application is that a TCP socket connection can be established with the server machine to communicate using the Automation Server ASCII protocol described later in this document.

The server machine must be in a logged-in state with a user profile that has the security privileges to launch the analyzer application.

Traditionally, an automation session would be initiated by a client by starting the FTSAutoServer application that is co-located with the installed version of the analyzer it is desired to run. The server port would be edited in the FTSAutoServer.exe.config file, which must be in the same directory as the FTSAutoServer application. The FTSAutoServer application in turn would launch the analyzer application, which would start the automation service, which would listen on any available network interface on the specified port. For example, on Windows the FtsAutoServerExe.config path would be:

C:\Program Files (x86)\Teledyne LeCroy Wireless\<installation directory>\Executables\Core\FtsAutoServerExe.config

On macOS, for Wireless Protocol Suite.app located in an area accessible by the user,

<path to Wireless Protocol Suite.app>/Contents/SharedSupport/wirelessprotocolsuite/support/wps/drive_c/Program Files (x86)/Teledyne LeCroy Wireless/Wireless Protocol Suite/Executables/Core/FtsAutoServerExe.config

On Linux after installation of the Wireless Protocol Suite deb file:

/opt/wirelessprotocolsuite/support/wps/drive_c/Program Files (x86)/Teledyne LeCroy Wireless/Wireless Protocol Suite/Executables/Core/FtsAutoServerExe.config

To run FtsAutoServer.exe from command line on Windows and use the port in the configuration file, the command line would be:

 C:\Program Files (x86)\Teledyne LeCroy Wireless\<installation directory>\Executables\Core\FtsAutoServer.exe

On macOS, the command would be:

 /Applications/Wireless Protocol Suite.app/Contents/SharedSupport/wirelessprotocolsuite/bin/wine --enable-alt-loader=macdrv --wait-children --bottle=default --workdir 'C:/Program Files (x86)/Teledyne LeCroy Wireless/Wireless Protocol Suite/Executables/Core' FtsAutoServer.exe

On Linux, the command would be:

 /opt/wirelessprotocolsuite/bin/wine --enable-alt-loader=macdrv --wait-children --bottle=default --workdir 'C:/Program Files (x86)/Teledyne LeCroy Wireless/Wireless Protocol Suite/Executables/Core' FtsAutoServer.exe

 An alternate way to run the automation server is to run the analyzer application, fts.exe, directly in automation-mode. The application may be launched from a command line, or from a client, by including the following arguments:

•  /automation – Indicates the user wishes to start an automation session.

• /automationport=<port> – Port the server will listen on for any available network interface.

 For example, on Windows to start automation and have the server listen on port 30332:

 “C:\Program Files (x86)\Teledyne LeCroy Wireless\Wireless Protocol Suite 7.0\Executables\Core\fts.exe” /automation /automationport=30332

 On macOS:

 /Applications/Wireless Protocol Suite.app/Contents/SharedSupport/wirelessprotocolsuite/bin/run_wps /automation /automationport=30332

 On Linux:

 /opt/wirelessprotocolsuite/bin/run_wps /automation /automationport=30332

Capture Files

 The analyzer can open and create (save) capture files. There are four file types supported for file open and one type is supported for save: