|
|
|
|
Diagnostician Features
IntroductionThe Diagnostician is a model-based expert system that provides fault isolation call-out based upon reading the results of tests.
Applications
ArchitectureThe Diagnostician is structured as a library of functions.
This library of functions is compiled to different operating systems.
For example, in the Windows environment, the Diagnostician is compiled
as a Dynamic Link Library (DLL) or COM object. The library consists of
diagnostic services, and is implemented in a true client-server
architecture, providing automatic fault isolation services to any
client program which calls upon its functions. This allows for
tremendous flexibility for integration into actual run-time platforms
and software environments, since users can call those functions which
their application needs, when they're needed. The client reports test results to the Diagnostician, which performs inferencing based upon the diagnostic model. Fault call-out, current ambiguity group, or next best test is passed to the client program. Intelligent Diagnostics
Dynamic Diagnostics
VersionsDiagnostician for Windows DLL or OLE or COM, 16 and 32 bit versions for Windows 3.1, Windows 95, Windows NT, Windows 2000 and Windows XP environments for LabVIEW, ATEasy, HP-VEE, Visual Basic, Visual C++, AIMSS, or any other program supporting DLLs or COM. Diagnostician for LabVIEW or LabWindows CVI Diagnostician for DDE for Fluke Sigma Series Tester and other Windows-based software packages not supporting DLL. Diagnostician for DOS for any DOS program Diagnostician for VAX for any Vax-based system, fully integrated into Teradyne L200/L353 series test system software. Diagnostician for Sun Solaris 2.3 or higher Diagnostician for SCO Unix Diagnostician for Embedded Microcontroller applications Intermetrics and other customized embedded hardware environments. What Makes the Diagnostician Unique ?The Diagnostician is a truly unique implementation of model-based reasoning by virtue of the following characteristics and features: 1. The test results can be entered
into the Diagnostician from any source, in any order, and as many or
few at a time as the application warrants. This tremendous flexibility
is provided by the internal structure of the model that is used for
diagnostic reasoning - the model is in a matrix format, as opposed to a
"fault tree" structure. How is the Knowledge Base Created?The Diagnostic Knowledge Base (DKB) is created using the Diagnostic Profiler. In most cases, the input is an EDIF netlist. The Diagnostic Profiler automatically translates the design information from the EDIF netlist into a fault propagation model. The user then identifies what design locations will be implemented as test points, and makes any necessary modifications to the component coverage information supplied by the Diagnostic Profiler. The result is a powerful diagnostic model which represents both fault propagation and test coverage.
Pricing
The links below provide detailed technical information on the Diagnostic Profiler and Diagnostician
|
|
Send mail to webmaster@giordano.com
with
questions or comments about this web site.
|