|
In keeping with our commitment to standards,
we have implemented SEMI Interface A (SEMI PR8/3563). This
Equipment Data Acquisition (EDA) standard serves equipment data
to multiple host connections using web technologies. It
can be your stepping stone to deploying
e-Diagnostics. Our offering is a
high-performance application component that provides you enhanced integration
flexibility and productivity.
Complete Documentation
APPLICATION
The Hume Interface A
component can be combined with an existing SECS/GEM
implementation of another vendor or deployed with a SECS/GEM
interface developed using the Hume Datahub SDK. High-level commands are exposed in a Tcl
programming environment to support rapid deployment and fast
updates. The core functionality is implemented in C for peak
efficiency. DMH message system libraries for connectivity with
other programming platforms such as .NET, Visual Basic, C, and Java
let you build an integrated solution with custom logic expressed
in the platform of your choice.
PORTABILITY
Our Interface A component supports a variety of
operating systems and hardware including Windows XP/2000,
Linux, HP-UX, and Solaris.
CONNECTIVITY
Included in the toolset are packages to provide communications
using the web technologies of XML, SOAP, and HTTP as specified by the
standard. Our thin HTTP server/client classes can be used
separately to facilitate any web services application (detailed
information in new browser windows is available here for the
client and
server).
DEMONSTRATION / VALIDATION
A pair of demonstration/test applications for Interface A are
included in the component toolset. These programs are
used to exercise, demonstrate, and/or test various aspects of
the standard. There is a version for equipment and a version
for clients.
EQUIPMENT: The equipment
application can be configured to concurrently operate with any
number of clients. Menu functions are provided to initiate
sending all of the basic EDA message types to the clients. The
equipment application is able to receive and process all
standard EDA messages initiated by the client including those
for Data Collection Plan management. The data exchanged and
diagnostic status information can be displayed and optionally
saved to files. The server's configuration including the names
of Data Collection Plans can be saved and re-used in future
sessions.
CLIENT: The
client application is designed to initiate messages to a single
equipment instance at a time. You typically run multiple
instances of the application, on multiple computer
systems, to exercise the equipment's ability to support multiple
simultaneous clients. Because the client application receives
messages through an HTTP interface, it can actually receive EDA
messages from any number of equipment servers simultaneously.
So it is possible to use a single instance of the client
application, and in sequence activate Data Collection Plans with
multiple equipment instances, and then collect the resultant
data messages at the single client application instance.
Contact us today for
details.
|
