SETUP DISPENSE DIAGNOSTICS SCREEN


SETUP DISPENSE DIAGNOSTICS SCREEN

Table 1. Dispense Diagnostics Setup Items

ITEM DESCRIPTION

Default DMON schedule num

default: 1

min: 1

max: 10

This item is the active or most recently run DMON monitoring schedule.

When Auto sampling is enabled, this should be set to the DMON schedule number that is to be used to monitor / gather data.

Likewise, when Asynchronous sampling is enabled, this should be set to the DMON schedule number that is to be used to monitor / gather data.

Do not change Default DMON schedule num if an Auto sampling or Asynchronous sampling monitoring session is active. If attempting to change when a monitoring session is active then the old value will be retained and the following warning will be posted: “SEAL-372 DMON in progress, item locked”.

Auto sample each job

default: YES

min: NO

max: YES

This item enables / disables the automatic start of a DMON monitoring session at the start of each production job. The DMON monitoring session is ended when the job completes or when the job is aborted.

  • YES: Data is automatically recorded for each job per the settings defined in the DMON schedule as indicated by the Default DMON schedule num. Asynchronous sampling is not permitted.

  • NO: Data is not recorded automatically for each job. Asynchronous sampling is permitted.

Max data files stored

default: 0

min: 0

max: 999

This item is used to limit the number of DMON session data files stored on the destination device.

Max data files stored can be used for both Auto sample and Asynchronous data monitoring modes.

Do not change Max data files stored if an Auto sampling or Asynchronous sampling monitoring session is active. If attempting to change when a monitoring session is active then the old value will be retained and the following warning will be posted: “SEAL-372 DMON in progress, item locked”.

  • A value of zero does not indicate that file storage has been disabled, Rather, it indicates that file management features are not used, and that data will be stored in a single file (without an index number in the file name) as specified in the schedule and will be overwritten in subsequent sessions.

    When setting this value to zero the following warning will be posted: “SEAL-375 DMON file management disabled” and the Starting file index will also be set to zero.

    Note that this value must be set to 0 if using a utility to transfer RD:diag.dt file to a GUI.

  • A value greater than zero indicates the number of sessions for which data will be stored. You cannot change this item if an asynchronous monitoring session is active. When changing this from zero to a non-zero value the following warning will be posted: “SEAL-376 DMON file management enabled” and the Starting file index will also be set to 1.

Starting file index

default: 0

min: 0

max: 999

This item is used only when Max data files stored is not set to zero. The Starting file index value determines the starting sequential number used in the file name for the next DMON session. Setting the Starting file index will also directly set the File name index item on the DMON utility schedule setup menu for the schedule number indicated by the Default DMON schedule num item on this menu. Note that the File name index item on the DMON utility schedule setup menu can be manually changed afterward, but it will be updated when the Dispense Diagnostics menu is re-displayed or when a new DMON session begins.

Starting file index can be used for both Auto sample and Asynchronous data monitoring modes.

Do not change Starting file index if an Auto sampling or Asynchronous sampling monitoring session is active. If attempting to change when a monitoring session is active then the old value will be retained and the following warning will be posted: “SEAL-372 DMON in progress, item locked”.

  • A value of zero indicates that the file management feature is not used. This means that the data file resulting from the DMON session will be overwritten each time. For example, if the File name item on the DMON utility schedule setup menu is set to “TEST”, then the resulting file from each DMON session will be named “TEST.DT” on the file device, overwriting any previous version of that file. The Starting file index value cannot be manually set to zero - it is automatically set to zero when Max data files stored is set to zero

  • A value greater than zero indicates that the file management feature is used and the name of the file created in the first session thereafter will have a file name that includes that value. So for example, if the DMON utility schedule setup menu File name item is set to “TEST” and the File name index item is 5 (assuming that the Max data files stored is 10 and Disable after max files is NO) then the file TEST0005.DT will be created on the next DMON session. The resulting files from each subsequent DMON session will be respectively named TEST0006.DT, TEST0007.DT, TEST0008.DT, TEST0009.DT, TEST0010.DT, TEST0011.DT, TEST0012.DT, TEST0013.DT, and TEST0014.DT on the file device. The next file index would roll back around to TEST0005.DT and continue in succession again - overwriting any previous versions of those files along the way.

Disable after max files

default: NO

min: NO

max: YES

This item is used to indicate how Data Monitor will handle new data after the Max data files stored limit is reached.

  • YES - Data Monitor is disabled after maximum data files are stored. Once Data Monitor has been disabled, in order to use it again the Data monitor operation item must be re-enabled on the DMON utility setup menu.

  • NO - The file index is reset to the Starting file index value and existing data is overwritten.

Disable after max files can be used for both Auto sample and Asynchronous data monitoring modes.

Auto stop session at xxx KB

default: 200 / NO

min: 1 / NO

max: 300 / YES

If this item is set to YES, then the data monitoring session automatically stops when the estimated data file size exceeds xxx Kilobytes. You can change the value of xxx depending on the capacity of the device on which the data is being stored. This feature is disabled when the default DMON schedule has Start item or Stop item triggers enabled. If either of these are enabled then when setting this item to YES the following prompt will be displayed: “Cannot estimate file size with triggers!” and the item is reset to NO. The size of the data file is estimated based on the assumption that Data Monitor is continuously recording data during the entire session. The resulting file size may differ from this setting because the estimation is only an approximation.

If this item is set to NO, then the size of files resulting from data monitor sessions is not limited and the xxx setting has no effect.

This feature can be used along with the DMON file management (Max data files stored) in order to limit the size of multiple created files.

Auto stop session can be used for both Auto sample and Asynchronous data monitoring modes. When using Asynchronous data monitoring mode, the value for the “Sample now” item on this menu will be changed from START to STOP when the file size limit has been reached.

Asynch. start enable

default: NO

min: NO

max: YES

This item indicates whether asynchronous data monitoring is permitted.

  • YES - Asynchronous data monitoring is permitted (but not necessarily started yet). When setting to YES, if the Auto sample each job is enabled (set to YES) then this item is set to NO and a “Must Disable <Auto sample each job>” message is displayed. If a data monitor session is currently in progress, this item is set to NO and the following warning is posted: “SEAL-372 DMON in progress, item locked”. When successfully set to YES, the following warning is posted: “SEAL-374 Asynchronous DataMonitor enabled”.

  • NO - Asynchronous data monitoring is not permitted. This item is set to NO if Auto sample each job is enabled (set to YES). If changing from YES to NO then the following warning is posted: “SEAL-373 Asynchronous DataMonitor disabled”

Sample now

default: STOP

min: STOP

max: START

Setting this to START will begin an asynchronous data monitoring session using the Default DMON schedule num indicated on this screen. Setting this to STOP will end the asynchronous data monitoring session. If the Auto stop session item on this menu has been enabled, then after setting Sample now to START, START will be automatically changed to STOP once the estimated data file size exceeds xxx Kilobytes and the data monitoring session automatically stops.

In order to set this item to START, the Asynch. start enable item must first be set to YES and Auto sample each job set to NO. If they are not both set as indicated then a “SEAL-373 Asynchronous DataMonitor disabled” error will be posted and the selection will revert to STOP.