The software was written in LabVIEW as a client/server style application. Using LabVIEW and a small stub of “C” code, the server portion of the software was built into a Windows Service. There is no interface to the server other than the client. The client uses the LabVIEW VI Server technology to communicate with the server. This configuration allows the technicians to check the status of any test from their desk or a remote location.
Test configuration allows the operator to be notified when alarm conditions occur or for a regularly scheduled check of the chamber. The system notifies the operator by sending an email and/or by sending a message to their pager.
All test status information is persistent in an MS Access database so if a power failure occurs, or the system goes down, the tests in progress are not lost. When the system is powered up again, the system will restart any tests that were in progress. Two days of history data is kept in memory for each test so trends can be identified.
The system can generate a number of reports, such as job status, journal events, chamber status, completed test results, and chamber utilization. For each type of report, the technicians can pick from a list of criteria to filter the requested information.