578 Keysight M8000 Series of BER Test Solutions User Guide
9 Utilities
• When working with additional tools to communicate with the DUT, e.g.
a debug-tool to configure the device, only one process can have control
over the COM port at a time. If the M8070A software has opened the
COM port in the DUT Control Interface script, then the external tool
cannot control the device and vice versa.
• Exceptions in the program flow may not prevent releasing the COM
port.
Best Scripting Practices
• Always implement OnUninstall and close the COM port properly.
• Create and open the COM port as late as possible in the script.
• Import all data types
• Implement all driver functionality to communicate with the device.
• Implement the required hook functions and call the device specific
functions.
• Configure and open the COM port.
The preferred place to do this is in the DUT_connect and
DUT_disconnect hooks.
• Initialize the DUT using the successfully opened COM port.
If there can be errors during the initialization phase, ensure that the
variable that provides access to the COM port is only getting invalid
after the COM port has been closed.
Communication with the M8070A Instrument Layer
Overview
The DUT Control Interface provides a functional API to allow interaction
with the instrument layer of the M8070A software.
The functional API is provided via the global symbol M8000 within the DUT
Control Interface script.
This is similar to the M8000.Scpi API in the Script Editor, but does not
allow sending remote commands to the M8070A software. Instead it
provides direct access to measurement relevant status and control of the
sequencing directly.
To Next Page
Loading...
Need help?
General
