|
Problem:
|
In SPC Direct Monitor, what does NaN stand for and how does it affect my analysis?
|
|
Solution:
|
A NaN entry can occur for one of two reasons:
- There is no data in the field when the reading is saved.
- Data saved is outside of the logical limits.
In SPC/Direct, the raw data received will always go into the database (be it out of
limits or an actual "NaN" in the received data). If the data then falls
out of limits or is a physical "NaN" that data record will not be included
in any charts which reference it.
However, SPC/Direct will not filter data in the database. It will only make sure that
the data it uses for its statistical analysis is within your limits. This design is intentional
because your limits may change if you inspect "failed" points and find out
that you've actually got wider swings in your data than you thought you would. To include
points that previously failed, all you have to do is widen the limits and SPC Direct
will work correctly with both new data and your historical data. You should always store
what you received. If you do want to alter what was received it can be done using
Database Manager at your discretion.
|
|
|
|
|
Problem:
|
The following informational message appears when the user attempts to
login to SPC Direct: This version requires database schema changes. Please
select an SQL administrator login at the next prompt.
|
|
Solution:
|
This is an internal message after an update has occurred. It implies that
a field has been added to the database. On startup, the application
detected the field was not there and needs to add it. If the SPC user does
not have enough rights to modify the database, the application will ask
for an administrative user. (Press OK and the standard login appears)
|
|
|
|
|
Problem:
|
Is there a maximum number of data points that can be entered manually in SPC Direct?
|
|
Solution:
|
The new version of SPC Direct for WindowsTM has the capabilities of
monitoring up to 120 variables without limiting the number of samples (data- points)
that can be entered.
|
|
|
|
|
Problem:
|
Can the current SPC configuration and data from the Microsoft
Access?TM version of SPC Direct be used with the Microsoft
SQL 7?TM version?
|
|
Solution:
|
No, the stations and parts will need to be redefined.
|
|
|
|
|
Problem:
|
I have checked the configuration and the rule: One point above or below the spec
limit is not functioning.
|
|
Solution:
|
Check the chart type you are using. Specification limits are not considered or
even allowed on Xbar charts. There are no spec limits for Xbar values - only
for X values. If you are interested in seeing if the product meets specs,
address that issue using an X chart - or in the case of Custom/QC, a min/Max
chart which will also allow spec limits. Spec limits are never put on an Xbar
chart since that would be comparing apples (Xbars) with oranges (Xs).
The short answer is that an Xbar chart in SPC direct will not signal on an X
point being out of specs - even if you turn on that test.
|
|
|
|
|
Problem:
|
The following error message appears when the SPC Monitor (spc.exe)
is launched: Cannot create a calculator, unable to proceed.
|
|
Solution:
|
This indicates that the stochos.dll is not present or not
registered. Stochos.dll must be registered and installed on each client PC
in the Windows\System or WinNT\System32 directories. Note: In
windows NT only the administrator has rights to register the .dll, even
though a regular user will get a successful registration message. The
command regsvr32 stochos.dll from the directory containing stochos.dll
will register the dll with the client OS.
|
|
|
|
|
Problem:
|
[Microsft][ODBC Driver Manager] Data source name not found and no default
driver specified
|
|
Solution:
|
The ODBC Data Source (SPCDirect) has not been created. Please reference
the SPC Direct installation instructions for information on creating the
SPC Direct data source.
|
|
|
|
|
Problem:
|
The following error message appears when the SPC Monitor (spc.exe) is
launched.
[Microsoft][ODBC Microsoft SQL Driver] Couldn't find data source
|
|
Solution:
|
The ODBC Data Source (SPC Direct) has been created but dose not
reference an existing SQL 7.0 database. From the ODBC Data Source
Administrator (Start|Settings|Control Panel|32 Bit ODBC), highlight the
SPC Data Source and click on Configure. Click on Select and choose the
target SQL 7.0 database.
|
|
|
|
|
Problem:
|
SPC Direct for WindowsTM does not alarm me when a point is out of spec.
|
|
Solution:
|
Each chart needs to be configured for the alarms you would like set.
How to set alarms in SPC Direct:
1) Run the database manager.
2) Select the chart tab. (be sure to have the correct Station/Part highlighted)
3) Select the chart in which you would like to apply the rule.
4) Click on the "Additional Control Tests" button.
5) Check the appropriate alarm boxes and click OK.
6) Click <Apply>.
Remember, these settings are per chart, so you need to be sure to highlight and apply
the rules for each chart that you would like the alarms set.
|
