![Tektronix OM4006D User Manual Download Page 184](http://html1.mh-extra.com/html/tektronix/om4006d/om4006d_user-manual_1078070184.webp)
Appendix G: The automated test equipment (ATE) interface
OUI setup for ATE
There is some setup that is done in the OUI4006 application in preparation for
an ATE application. It is necessary to add function calls that perform additional
calculations. Variables used in these function calls and shared with the ATE
application should be declared as “global” in the MATLAB Engine Command
window as shown below with the variable “ChOffset”:
The standard variables produced by CoreProcessing and any additional declared
variables will be repopulated each time a single is executed. After the data record
is acquired from the scope, the commands that are in the MATLAB Engine
Command window will be executed using that data. The variables used in these
executed commands will only be available until the next single acquisition
occurs. The ATE application should save the global variables to local storage
for processing before executing the next single acquisition. This process is
synchronized via a callback method or .NET event that is sent to the ATE
application when the processing of an acquisition is completed and the variables
are ready for storage and processing.
Thus the Data/Variable process works like this:
1.
A Single is executed
2.
Record/Block data is retrieved from the scope and saved to vBlock
3.
All commands in the MATLAB Engine Command window are executed
against the acquired data record and all variables, both standard and global,
are populated
4.
End of Block is triggered for each multiple of block size less than record size
5.
End of Record is triggered
The ATE application should implement a callback handler for each event, block
and/or record, it is interested in. In general, ATE applications will probably have
the block and record size equal so the block and record events will be one for one.
There are some additional summary variables that are populated at the end of the
record so it is best practice to attach to the Record Event when block size is
≥
record size. The example of this implementation is described in
Basic Method
for getting MATLAB variable values
Basic and advanced WCF
service interfaces for the
OUI4006
The basic service, implemented using a wsBasicHTTPBinding, exposes a
smaller subset of commands. It was implemented using a simpler binding for
compatibility with applications like MATLAB or LabView that only support the
wsBasicHTTPBinding. (See page 167,
The basic service can be referenced at the following URL:
http://localhost:9200/Optametra/OM4006/WCFServiceOM4006Basic/
160
OM4000D Series Coherent Lightwave Signal Analyzer
Summary of Contents for OM4006D
Page 2: ......
Page 6: ......
Page 22: ...Compliance information xvi OM4000D Series Coherent Lightwave Signal Analyzer...
Page 24: ...Preface xviii OM4000D Series Coherent Lightwave Signal Analyzer...
Page 100: ...Taking measurements 76 OM4000D Series Coherent Lightwave Signal Analyzer...
Page 146: ...Appendix D Automatic receiver deskew 122 OM4000D Series Coherent Lightwave Signal Analyzer...
Page 202: ...Appendix H Cleaning and maintenance 178 OM4000D Series Coherent Lightwave Signal Analyzer...
Page 205: ...Index W Waveform averaging 48 OM4000D Series Coherent Lightwave Signal Analyzer 181...