4.3.2.3 On-Line Analysis Via A Database
The AT Server software can store test results in an electronic database.
This provides a very powerful and versatile method of recording and
analyzing test results historically or on-line.
The Server uses standard Windows methods (including OLE DB and ODBC) to
connect to a variety of databases that conform to these specifications.
Once stored in a database the data may then be analysed using tools
available in the database application or tools provided by specialist
software packages such as those available for SPC (Statistical Process
Control). One example of this is to monitor in real time the trend in a
winding resistance to identify a defective drum of copper. You would then
be able to rectify the fault during production rather than producing a
large stock of QA failed transformers all wound with the defective wire.
SETTING UP DATABASE RESULTS STORAGE
From the 'Setup' menu, select 'Results' to see the dialogue
Select 'Standard Results Saving' (CSV) to save all results to a
spreadsheet compatible file. See 3.2.4.
Select 'Database Results Saving' to save results to a database. For this
feature to operate properly, a connection to the database must be set up
first.
CSV and database format results can be saved simultaneously.
Click on 'Advanced' to set up your database connection:
To connect to your database, the Server software uses a connection string
that contains (amongst other things) the name of a provider, the name and
location of the database and a valid database user name and password (if
required). You may need to consult with the database or network
administrator to obtain this information.
If a connection has already been established you will see the connection
string in the window inside this dialogue. If you wish to remove an
existing connection string, click on 'Clear Connection'.
To establish a new connection click on 'Connection Type'.
The 'Data Link Properties' dialogue is a standard one that is supplied by
Windows. You should choose the provider that will provide the connection
to the type of database that you are using.
Several different types of provider are installed along with the Server
software, others may be available if you have a database application
installed on the same PC as the Server. If the provider you need is not
available and the database is installed on another PC, ask the database
administrator for the database client tools for the Server PC.
Typical provider types are:
| Database |
Provider |
| Microsoft Access 97 |
Microsoft Jet 3.51 |
| Microsoft Access 2000 |
Microsoft Jet 4.0 |
| Oracle |
Microsoft OLE DB Provider for Oracle |
| SQL Server |
Microsoft OLE DB Provider for SQL Server |
In addition it is possible to connect to ODBC compliant databases
(including Microsoft Access) using the Microsoft OLE DB Provider for ODBC
Drivers.
Click on 'Next' when you have chosen the correct provider.
Select the database name that you will be using by clicking on 'Select'.
If you wish to create a new database for AT Server results, do so now
using your database program.
The default user name 'Admin' with no password may be adequate. Consult
your database administrator if you need a specific user name and password.
When you click on 'Test Connection' you should see something similar to:
Next, click on 'OK' of the 'Test connection succeeded' dialogue and
select the 'Advanced' tab.
Check that the 'Access permissions' for the database are as required.
'Share Deny None' is the default and is usually the most suitable setting.
Under the 'All' tab all of the individual settings can be reviewed and
adjusted if necessary.
Click on OK to complete the setting of the data link properties. A
typical AT Server advanced database results dialogue would be:
Click on OK to return to the results dialogue. At this point the AT
Server will automatically create the required database tables if they do
not already exist.
Ensure that 'Database Results Saving' is checked and click on 'OK'.
Whenever a results window is open, the results will now be stored in the
selected database.
DATABASE TABLES
The server software automatically creates the following tables in the
selected database (if they do not already exist) and stores data within
the tables using the structure defined here.
The tables store all the information that is available concerning the
results (including time, date, limits, operator etc.) in a very compact
and efficient structure.
Note that new data is not necessarily appended to the end of a table; it
may appear anywhere within.
| Table: |
tblVoltechATUnitID |
� |
| Field |
Format |
Notes |
| ATUnitID |
Text (25) |
Index ID |
| UnitType |
Text (10) |
AT3600, AT1600, ATi |
| UnitID |
Text (10) |
Unit Serial Number |
| FirmwareID |
Text (10) |
Unit Firmware Version |
| Table: |
tblVoltechATUnitID |
� |
| Field |
Format |
Notes |
| ResultID |
Text (25) |
Index ID |
| RunID |
Text (25) |
As tblVoltechRunID.RunID |
| TestID |
Text (25) |
As tblVoltechTestID.TestID |
| TestNo |
Number (Long Integer) |
Test number as in test program |
| OC_Comp |
Text (5) |
YES , NO , N/A
Open Circuit Compensation status |
| SC_Comp |
Text (5) |
YES , NO , N/A
Short Circuit Compensation status |
| Load_Comp |
Text (5) |
YES , NO , N/A
Load Compensation (future development) |
| Result |
Number (Single) |
Actual test result |
| TestStatus |
Text (5) |
DSP Status for test |
| PassFail |
Text (5) |
PASS/FAIL
Individual test pass or fail result |
| Table: |
tblVoltechATUnitID |
� |
| Field |
Format |
Notes |
| RunID |
Text (25) |
Index ID |
| Date |
Date/Time (Short Date) |
Date of Test Run |
| Time |
Date/Time (Long Time) |
Time of Test Run |
| ATUnitID |
Text (25) |
As tblVoltechATUnitID.ATUnitID |
| PartID |
Text (25) |
Part name |
| FixtureID |
Text (25) |
Fixture name |
| OperatorID |
Text (25) |
Operator name |
| BatchID |
Text (25) |
Batch name |
| TransformerSerialNo |
Text (25) |
Transformer serial number |
| OverallResult |
Text (10) |
PASS/FAIL/RE-RUN/ABORT
Overall test pass or fail result and Re- Run result. |
| Table: |
tblVoltechATUnitID |
� |
| Field |
Format |
Notes |
| TestID |
Text (25) |
Index ID |
| TestMnemonic |
Text (10) |
Individual test mnemonic |
| TestUnits |
Text (10) |
Individual test units |
| CheckType |
Text (5) |
NONE/MIN/MAX/DIFF/POL
Type of test limits (see *) |
| MinLimit |
Number (Single) |
Minimum limit for test (see *) |
| MaxLimit |
Number (Single) |
Maximum limit for test (see *) |
| * Notes: |
� |
| (CheckType = NONE) |
If there are no Min or Max limits, MinLimit = 0 and MaxLimit = 0 |
| (CheckType = MIN) |
If there is a Min limit only, MaxLimit = 0 |
| (CheckType = MAX) |
If there is a Max limit only, MinLimit = 0 |
| (CheckType = DIFF) |
If there is a Min and Max limit |
| (CheckType = POL) |
Polarity test
If Positive Polarity test, MinLimit = 0 and MaxLimit = 1
If Negative Polarity test, MinLimit = -1 and MaxLimit = 0 |
CHARTING AND ANALYSIS USING SPC / SQC SOFTWARE
Once an AT Server to database connection has been made, it is possible to
connect third party analysis software to the same database for live
on-line (or offline) data analysis.
Voltech does not recommend one package more than any other.
You should choose to use the one that best meets your needs.
�
�