[click images to enlarge]

CUSTOM TEST EXECUTION INTERFACE FOR OPTICAL MODULATOR MANUFACTURING AND TEST
[back to labview solutions]
CHALLENGE

To develop custom software for testing fiber optic modulators at incremental steps throughout the manufacturing process - from wafer fabrication to chip placement and packaging. Additionally, code was to be written in such a way as to permit administrators to alter the test process at key test stations without the need to modify the code itself.

SOLUTION

A concept of a 'main test utility' was introduced as a top-level interface that was seen at all key test stations throughout the facility. Users were required to login with credentials authenticated against a custom Oracle database schema. Next came a series of test routines that were specific only to their respective test stations (i.e. complex algorithms, simultaneous test sequences, etc). And finally a number of custom written drivers to harness applicable functions of all major test instruments throughout the facility (VNA's, function generators, power supplies, optical power meters, DAQ hardware, custom switches, serial devices, etc). Other functional routines such as database persistence, datasheet generation, report generation, etc were also built in.

A key feature to all custom routines and drivers is their ability to interpret incoming commands. Based on the traditional state-machine design pattern, each routine could take as input a series of text-based commands and process them accordingly (routing to the appropriate states - and sub-states). Ultimately, each were capable of handling requests common to all stations (and even those specific to as few as one station).

Lastly, all routines and drivers could be aggregated to form custom test sequences via the 'main test panel' and custom written XML scripts. Administrators were permitted to generate XML scripts either manually or via a custom written configuration utility, and direct the 'main test utility' to load and process said script(s). Defined with in the scripts were all the functions exposed via each routine (instrument drivers, database persistence, reports generation). Ultimately, administrators could control the functionality of each key test station without the need to modify code, only the need to alter a script file.

[back to labview solutions]

Like this solution? Share it!

[click images to enlarge]