Numeric Input test

Property

Default setting or default display

Allows

APPEARANCE

Label

[blank]

Enter text for a description. This Label will be displayed to the user.

If the SPCStandardSelection property is set to PickAtRuntime, this Label will be replaced by the name of the Standard that the user selects.

Tip: If you need to provide a very long label or user instructions, add a Text test above the Numeric Input test. The PC Collect module can only display the first 43 characters of this Label.

BEHAVIOR

CheckFailureResponse

[Blank]

Mobile: A pop-up message displays after a failed check.

PC: No message displays after a failed check.

Enter an email address to enable sending an email notification after a failed check. Multiple addresses should be separated by commas. (A semicolon used to separate e-mail addresses will be automatically corrected to a comma.)

[Mobile]: Assumes the device's email is configured correctly.

[PC]:

• Uses system-wide e-mail settings and user e-mail settings that are configured in the System Administration module. The user e-mail settings determine the "From" address used to send the e-mail message.

• If sub-inspection displays any charts, those charts can be included in the e-mail.

• Depending on the AutoSendRTFEmail property, the inspector may be able to change the email message, the recipient email addresses, and the charts included.

• If the sub-inspection has the CombinedFailureResponse property enabled, it will still send an email for all the failures on the sub-inspection (regardless of how this test property is set).

SPCStandardSelection

PickAheadOfTime. Limits the inspector to a specific standard for this test.

[See SingleSPCStandard property.]

PickAtRuntime requires the inspector to select an SPC Standard from a list during data entry.
For PC data entry, you can use the SPCStandardSearchString property to narrow the list of standards displayed to the inspector.
If using a DeviceProfile, the user will not be able to start entering data until an SPC Standard has been selected.

DoNotStore provides one data field and does not store the number the operator enters when data is submitted, which can be useful if the number is used in a calculation.
When using this option, you can execute a Python script that sets inspect.cursubi.ni(idx).subgroupsize to a different subgroup size. Common practice is to execute this type of command in a Formula test with the FormulaMode property set to Pre.
Selecting the SPC standard ("part number") for the numeric input test will reset the subgroup size to the value in the standard.
When using this option, any side panel charts linked to this test will not be refreshed when the sub-inspection is Submitted.

DATA

SingleSPCStandard

[blank]

Select a single SPC standard to store with the test data. Use this property in conjunction with the PickAheadOfTime setting of the SPCStandardSelection property.

You can double-click on the Numeric Input test to edit this property.

[Mobile only]: The Numeric Input test is limited to storing data for a subgroup size of 8 or less.

MOBILE

CheckAgainstIndividualGates

[Mobile only; device must be in online mode]

False. The test data is not checked against individual upper/lower gates.

True. Checks the test data against individual upper/lower gates.

CheckAgainstSpecs

[Mobile only; device must be in online mode]

False. The test data is not checked against individual upper/lower specifications.

True. Checks the test data against individual upper/lower specifications

CheckAgainstSubgroupGates

[Mobile only; device must be in online mode]

False. The test data is not checked against subgroup upper/lower gates.

True. checks the test data against subgroup upper/lower gates.

CustomPropertyName

[Mobile only]

[blank]

Enter the name of a custom property that has been set using another numeric input.

Use this property to access a calculated value that is based on other input set by the FormulaAfterEntry property.

FormulaAfterEntry

[Mobile only]

[blank]

Enter LiveCode code to execute calculations after the data is entered for this test.

KeyboardInput

[Mobile only]

True. The numeric input can be edited using the keyboard.

False. The numeric input cannot be edited using the keyboard.

LocalDataRead

[Mobile only]

[blank]

Enter LiveCode code to prefill the numeric input text box with a stored value from the local database.

[See LocalDataStorage property.]

LocalDataStorage

[Mobile only]

[blank]

Enter LiveCode code to store a value in the local database to be read at a later time.

PrepText

[Mobile only]

[blank]

Prefill the numeric input box with this value.

SPCStandardList

[Mobile only]

[blank]

Select an SPC standard list for operator to choose from at run-time.
[Must be used with the SPCStandardSelection property set to PickAtRuntime.]

[Set the list using a SPC Standard Lists category property on the Properties grid for a sub-inspection.]

PC

AutoSendRTFEmail

DoNotSendAutomatically. The Inspector can edit real-time failure e-mails before sending them.

Used only when CheckFailureResponse property contains a valid email address.

(In GainSeeker versions previous to version 9.3, this setting was False.)

SendLinkedCharts: The Inspector cannot interact with real-time failure e-mails. These e-mails are sent automatically and include all SPC charts that are linked to this Numeric Input test.

SendAllCharts:The Inspector cannot interact with real-time failure e-mails. These e-mails are sent automatically and include all charts for the sub-inspection.
(In GainSeeker versions previous to version 9.3, this setting was True.)

Both settings are only used when CheckFailureResponse property contains a valid email address.

DataReferenceRead

[blank]

The reference key used to retrieve data points for this test. The reference key is appended to the inspection's Unique ID for retrieval from the control table in the database.

DataReferenceStorage

[blank]

Reference key used to store data points for this test. The reference key is appended to the inspection's Unique ID for retrieval from the control table in the database.

DeviceProfile

[blank]

Use keyboard input for this test.

Select a Device Profile configured for direct data entry from a connected RS-232 measuring device.

Having a Device Profile selected puts the Numeric Input test into serial input mode.

When the cursor is on any data cell in the subgroup – either automatically when the focus enters the cell, or manually when the user clicks on the cell – this Device Profile will automatically be run to collect a measurement from the device (or if using Keyboard mode, the keyboard prompt will automatically be launched). The only time this does not apply is if the highlighted cell already contains a value (not the Data Entry Constant) – in this case, the user can delete the current cell contents to re-start the Device Profile.

Best practice is to avoid setting a Data Entry Constant in the SPC standard if that standard will be used in a Numeric Input test that runs a Device Profile.

In PC Collect, the Device Profile is unloaded from memory when the inspection is closed and the user is returned to the list of inspections.

Filter

[blank]

No filter is applied when retrieving the most recent data to calculate statistics for real-time failure checks.

You can filter the data that will be retrieved to calculate statistics (such as Control limits, Mean, R-bar, 2SD, and 3SD) for real-time failure checks. This can be a Quick filter or a saved filter.

In some cases, you may wish to filter for a traceability value that was entered in this inspection – by the TestSpecificTrace property on this Numeric Input test, a Traceability test in a previous sub-inspection or the current sub-inspection, a Planned Inspection, or a Formula test.

For example, you might wish to filter for:

• a Lot number that the user enters during data entry

• a Machine ID that you preset with a Planned Inspection or Formula test

To filter for such a traceability value – which may vary from one data entry session to the next – you must create a Quick filter or a saved filter that looks for a blank value in that traceability field. For an example of this type of filter, and for more information, see Filtering for inspection traceability values.
(When using this type of filter, avoid using the Python command inspect.settracevalue() as it will not re-filter the data for this new traceability value. Use inspect.cursubi.trace().value or inspect.cursubi.ni().settrace() instead.)

Please note: GainSeeker also limits the data retrieved by the Default date period for SPC Data Entry and the default Maximum count for retrieval (both set in the System Administration module) - whether or not this property sets a filter.

For any inspection that was last edited before GainSeeker version 9.3, a filter set for SPC Chart groups linked to this test will automatically be applied to this property when you edit or run the inspection. You can still edit the inspection to remove or change this filter.

ForceNote

Use Sub-Inspection Settings.

Apply the settings from the sub-inspection ForceNote property to this test.

Click the ForceNote property and then click the button to choose a combination of options on the ForceNote window for this test. For details, see Setting the ForceNote property.

NoValue

RequireEntry

All data cells must contain numeric values and/or asterisks ( * denotes a missing value) before the user can Submit the sub-inspection.

This property is only applied when the Numeric Input test is visible.

The options below allow the user to leave this Numeric Input test completely blank and still Submit the sub-inspection:

StoreSentinel

If all data cells are blank when the sub-inspection is Submitted, store a record for this Numeric Input test with an asterisk ( * denotes a missing value) in each data cell.

DoNotStore

If all data cells are blank when the sub-inspection is Submitted, do not store a record for this Numeric Input test.

Note: the Data Entry constant is not a blank value, and a Numeric Input test with all cells set to the Data Entry constant will store those values as valid numbers.

SolartronSettings

[blank]

You can use this property to configure settings for direct data entry from a connected Solartron Orbit 3 module.

Note: To actually trigger data collection from the specified Solartron module in PC Collect, you must use a Formula test that executes solartron Python commands.

1. Enter the Solartron Module ID that will send data to this Numeric Input test.
   
   To automatically detect the Module ID from the next module that sends data to the computer, click Listen. (If GainSeeker cannot connect to the Solartron network, this button is not available.) Alternately, if you know the Module ID that is programmed for the desired module, you can type it manually. Also, if the desired Module ID has already been detected for this inspection, you can select it from the list.

2. Set the appropriate Addend 1, Factor, and Addend 2 to arrive at the desired Calculated Value, which will be stored as the measurement value for this Numeric Input test.
   
   When Addend 1 = 0, Factor = 1, and Addend 2 = 0 (the default settings), the Calculated Value will equal the raw data value that is read from the specified Solartron module. To calculate a different value, set the Addend 1, Factor, and Addend 2 such that Factor * (Reading + Addend1) + Addend2 equals the Calculated Value you want to store as the measurement value for this Numeric Input test.
   
   To verify your results, enter a raw data value for the Current Reading. You can either type a value or click Read to read the value of the selected Module ID. (If GainSeeker cannot connect to the Solartron network, this button is not available.) GainSeeker will display a Calculated Value based on the Current Reading and Addend 1, Factor, and Addend 2.

SPCStandardSearchString

[blank]

Enter a search string to specify what displays in the SPC standard list when the SPCStandardSelection property is set to PickAtRuntime.

You can also enter a regular expression for this search. To do so, your search must begin with  R:  followed by the regular expression, like the following examples:

• To find all standards that begin with "TEMP", enter  R:^TEMP  as the search string.

• To find all standards that end with "TEMP", enter  R:TEMP$  as the search string.

• To find all standards that contain "Angle" or "Bracket", enter  R:Angle|Bracket  as the search string.

TabDirection

Across

After a measurement has been entered, automatically advance to the next measurement in the subgroup for the current Numeric Input Test.

This is useful when you want to measure one characteristic for all parts in the subgroup, then measure another characteristic for all parts in the subgroup, and so on.

Down

If two or more Numeric Input tests are contiguous (no other tests between them), automatically advance to the same position in the next Numeric Input test on this sub-inspection.

This option is useful when you want to measure several key characteristics on the first part in a subgroup, before proceeding to measure the same characteristics on the second part in the subgroup. This often happens in inspections with RS-232 input for multiple characteristics of a part (see Device Profile above).

This option may trigger more OnChange formulas than the Across option, because you are more likely to move from one test to another after changing the value in the first test.

TestID

A unique TestID number is automatically assigned to each test in the inspection, but you can change this number to a more meaningful name.

The TestID property is only used in Python scripts for PC Collect inspections.

For more information, see About the TestID property

Enter a name for the TestID.

TestSpecificTrace

[blank]

You can specify one or more traceability values that will be applied only to this Numeric Input test on this sub-inspection.

These values will not be displayed to the inspector during data entry.

If you want to store this test's TestID property as a traceability value, enter [testid] .

Any traceability values you set here will override values set by Traceability tests, Inspection properties, Planned Inspection traceability values, etc.

VerticalSize

Regular. Test is full-sized.

Short. Helps you to fit more tests on the screen. Test may be shorter, and white space above and below this test may be reduced.