Teledyne LeCroy PeRT3 Software Interface - Manual (Page 6)

 “127.0.0.1” is the IP address of the host pc that the hardware is plugged into. The software should be
installed on that pc and you should verify that it is running. If your test executive is running on the
same pc, then “127.0.0.1” is the loopback address and should work provided there is no problem with
firewall settings on that pc. You can run the test executive on a pc separate from the one the PeRT
3
hardware is plugged into, just make sure the PeRT
3
software package is installed on both machines
and that you provide the IP address of the target pc.
 “My Test Script” is the exact name of a test script that you have defined on the hardware using the
user interface that comes with the software. Within a test script, you can select protocol and DUT
initialization (or omit the DUT initialization) and specify jitter settings and patterns to send.

Note: As currently written, the LCPeRT_RunTestScript() function does not return until the script
finishes running. If your test executive is a single threaded environment and you are just using the
script to configure patterns and jitter settings, you can set the termination condition on the script to be
“Elapsed Time” and the time to “0:00:01” (1 second) so that it configures the PeRT
3
and returns right
away. If you have a multi-threaded environment, then you might instead set the termination
condition to “Run Forever” and then use the LCPeRT_Stop() function to stop the script in another
thread, before starting the next one.
What is the format for the test scripts?
There are XML files that are installed with the software. XML isn't the actual internal format of the
scripts and patterns that the device is using -- they are actually stored internally as objects in a database.
XML is the format that is used to import/export them from the device.
It's generally a lot easier to create/edit a test script or pattern using the UI software then it is to edit the
XML. However, there is no reason you can't cut and paste and modify the XML in a text editor and
import it into the software via the UI import menu if you find that easier.
The example XML files are collections of TestScripts and TestPatterns. You can also create files that
just contain a single TestScript or TestPattern without the top level
node and import them.
There is currently no mechanism for uploading a pattern or test script to the PeRT
3
from the LCPeRT
API. This is planned as a future enhancement.
Currently you need to either create patterns and test scripts in the PeRT
3
user interface, or import them
using it. Once the pattern or test script is loaded in the PeRT 3 database you can access it by name from
the API. See the header file for functions for enumerating the names of scripts and patterns currently in
the database.
Once you've created a script or pattern you can duplicate it in other PeRT
3
's by exporting to XML and
then importing it on the other PeRT
3
's.
How do I specify a test script?
You need to either import the XML or create the script in the text editor and save it. It will then show up
in the drop down box in the main control panel (the box at the top of the first panel on the left of most of
the ribbon tabs) and in the Test Script pane in the Library Window. If the script appears with "*" next to