dloggereditor
October 2020
Purpose:
The dloggereditor program is a Graphical User Interface that guides a user through steps to generate the specification file for the dlogger program.
The dloggereditor task is started from the command line.
Enter:
dloggereditor [dlogger_spec_filename] &
Where:
dlogger_spec_filename |
- Optional Argument |
|
- The pathname of the file to edit or create |
Example:
dloggereditor /specs/dlogger_spec.103 &
Execute the following steps to create a new file:
Figure 1: New-File Selection
Figure 2: New File Screen
Figure 3: Populated New File name Field
Execute the following steps to load an existing file:
Figure 4: Open File Selection
Figure 5: Populated Open File name Field
Enter dloggereditor [spec_filename] & at the command line. Refer to Overview section of this document.
A pop-up message as in Figure 6 is displayed if an invalid file is specified.
Figure 6: Invalid File Specification Message
Click OK and the Empty File screen will display as in Figure 7.
Figure 7: Empty File
Execute the following steps to set font preferences:
Figure 8: Edit - Preferences Selection
Figure 9: Editor Preferences Dialog
Hover the mouse over data in a tab screen column or row entry to display a description of that file element’s usage.
Hovering the mouse also displays error information for a file element. See the Error Counts section for related information.
The bottom row of each tab screen lists the number of errors in the currently displayed tab and total number of errors in the file as in Figure 10. Errors in the currently displayed tab screen are indicated by red text accompanied by a red‘”x”. Errors may be syntax errors, excluded or empty fields, or any other file element that fails checking.
Figure 10: Error Counts Example
Select the Keywords tab to display dlogger spec file keywords. When a new dlogger spec file is created, default values appear within the screen for several of the required spec file keywords as in Figure 11.
Figure 11: Keywords Tab Screen
Refer to the following sub-sections for descriptions of Keywords tab screen functions.
Execute the following steps to edit applicable Value column information:
Figure 12: Variable Selection Dialog
Execute the following steps to insert additional keywords into a dlogger spec file:
Figure 13: Insert Keyword Row
Figure 14: Add New Keyword
Right-click over the row to remove on the Keywords tab and select Remove Row as in Figure 15.
Figure 15: Remove a Keyword Row
Table 1 lists the keywords that can be added via the Keywords tab.
Table 1: Keywords that can be Added via the Keywords Tab
Generated Keyword In Spec File |
Definition |
Type |
*@DLOGGER |
Identifies this is a dlogger spec file |
String |
*@DESCRIPTION |
A title to be written to the output file |
Computed Expression |
*@GROUP |
Measurement name in meta-data section of output file for GROUP |
String Variable |
*@MODE |
Test mode to include in the output file meta-data section for MODE |
String Variable |
*@PROGRAM |
Program name to include in the output file meta-data section for PROGRAM |
String Variable |
*@TEST_ID |
Test Id to include in the output file meta-data section for TEST ID |
String Variable |
*@TEST_TYPE |
Test Name to include int the output file meta-data section for TEST TYPE |
String Variable |
*@SCAN_INTERVAL |
Time between data samples in output file |
Literal value (<time>[units]) or Variable name |
@CLEAR_STATISTICS_EVENT |
Event to trigger statistical buffers within dlogger to reset to 0 |
Event Name - String |
@DONE_EVENT |
Name of event set at completion of data collection |
Event Name - String |
@ENABLE |
Logical variable that must be TRUE before logging can start |
Logical Variable |
@FIFO_LOG_BUFFER |
Presence of keyword signifies to activate First-In First-Out Logging |
|
@FIFO_POST_TRIGGER_INTERVAL |
Length of time to obtain scans after the FIFO trigger event (stop or release event) has been received |
|
@FIFO_POST_TRIGGER_SCANS |
Number of scans to obtain after the FIFO trigger event (stop or release event) has been received |
Integer value |
@FILENAME |
Enables a computed expression to be entered after the keyword. The expression is evaluated during each scan to see if the result has changed. If it has, then the present file is closed and transferred to DARTS, and a new file is opened. It does not affect the name of the output file, which is a fixed format that includes the date, time, and specification file name. |
Computed Expression |
@FORCE_DIRECT_FILE_WRITE |
Indicates that data should be written directly to the output file when high data rates are used |
Yes or No |
@FTP_EVENT |
Event that triggers the output file to be finalized, and initiates file transfer |
Event Name - String |
@GET_NEW_SCAN_INTERVAL |
Event that triggers a re-evaluation of the SCAN_INTERVAL computed expression |
Event Name – String |
@LOG_DIGITAL_DESCRIPTION |
Flag used to determine if logical variable descriptions for all logical variables should be logged instead of 0 or 1 |
Yes or No |
@LOG_STATISTICS |
Flag used to specify that statistics should be computed for the variables specified via the @SCAN_LIST keyword |
Yes or No |
@LOGGING_ACTIVE_LABEL |
The name of a CyFlex logical variable that indicates dlogger is actively collecting data and logging it. |
Logical Variable |
@MAX_SCANS |
Maximum number of samples in a sampling session |
Integer value |
@MAX_STATISTICAL_SCANS |
Maximum number of scans when the @LOG_STATISTICS keyword is specified |
Integer value |
@OUTPUT_PATH |
Directory path to the output file |
String variables or Directory Path - String |
@DARTS_STEADY_STATE |
Presence of keyword signifies the darts_ss_specs file variables should be included in the scan list |
|
@READ_SPEC_FILE_EVENT |
Event that triggers the dlogger to re-read the spec file |
Event Name - String |
@REG_NAME |
Name that identifies the instance of dlogger within the OS |
String |
@RELEASE_EVENT |
Event that signals the end of a sampling interval and terminates the dlogger task after the data files are written |
Event Name - String |
@RUNNING_AVERAGE |
Window width of a running average window in units of time and the event that causes the data to be logged |
Note: The second and third column are used to enter information for this keyword. The Value column should contain the window_width[units]. The right most column should contain the name of the event that causes the averages to be written to the output file. |
@SEND_ON_PATH_CHANGE |
By default, the existing file is closed, transferred to DARTS, and a new file is opened when one of the following values change: ·Mode ·Test ID ·Test type ·Program ·Group Select No from the drop-down to disable the default behavior. |
Yes or No |
@START_EVENT |
Event that triggers the start of a sampling interval |
Event Name - String |
@STOP_EVENT |
Event that triggers the end of a sampling interval |
Event Name - String |
@SYNC_EVENT |
Event that triggers a scan of all channels |
Event Name - String |
* - Denotes required keyword |
Figure 16: Scan List Dummy Row
This dummy row is available to edit and add rows to the Scan List; refer to Figure 17.
Execute the following steps to edit a Scan List dummy variable row:
Figure 17: Scan List Variable Selection Dialog
Figure 18: Scan List SubVariable Selection
Figure 19: LOG_DIGITAL_DESC Selection
Figure 20: Scan List Select PAM Keyword
Right-click a table row within the Scan List tab and select Insert Row from the pop-up menu as in Figure 21.
Figure 21: Insert Scan List Row
Right-click a table row within the Scan List tab and select Remove Row from the pop-up menu as in Figure 22.
Figure 22: Remove Scan List Row
Table 2 lists the keyword that can be added via the Scan List tab.
Table 2: Keywords that can be Added via the Scan List Tab
Generated Keyword In Spec File |
Definition |
*@SCAN_LIST |
PAM keyword names correlating to CyFlex Variable Names to be logged |
* - Denotes required keyword |
Select the Meta Data List tab to display the meta data list of PAM keywords and associated CyFlex variables. When a new dlogger spec file is created by dloggereditor, a default dummy variable row is added to the Meta Data List Tab as in Figure 23.
Figure 23: Meta Data List Dummy Row
This dummy row is available to edit and get additional rows added to the Meta Data List; refer to Figure 24.
Execute the following steps to edit a default Meta Data List dummy variable row:
Figure 24: PAM Keywords List
Figure 25: Meta Data List Variable Selection – Add Corresponding Variable
Figure 26: Meta Data List Variable Selection – Add Literal Value
Right-click a table row within the Meta Data List tab and select Insert Row from the pop-up menu as in Figure 27.
Figure 27: Insert Meta Data List Row
Right-click a table row within the Meta Data List tab and select Remove Row from the pop-up menu as in Figure 28.
Figure 28: Remove Meta Data List Row
Table 3 lists the keyword that can be added via the Meta Data List tab.
Table 3: Keywords that can be Added via the Meta Data List Tab
Generated Keyword In Spec File |
Definition |
* @META_DATA |
List of specified PAM Keywords and corresponding CyFlex variable names where the CyFlex variable values will be captured once when the dlogger output file is written. |
* - Denotes required keyword |
Select the Scan List Aux User tab to display CyFlex Variables and associated Alternate Names.
Right-click a table row within the Scan List Aux User tab and select Insert Row from the pop-up menu as in Figure 29.
Figure 29: Insert Scan List Aux User Row
Execute the following steps to edit data in a Scan List Aux User row:
Figure 30: Scan List Aux User Variable Selection
Figure 31: Edit Alternate Name
Right-click a table row within the Scan List Aux User tab and select Remove Row from the pop-up menu as in Figure 32.
Figure 32: Remove Scan List Aux User Row
Table 4 lists the keyword that can be added via the Scan List Aux User tab.
Table 4: Keywords that can be Added via the Scan List AUX User Tab
Generated Keyword In Spec File |
Definition |
@SCAN_LIST_AUX_USER |
List of CyFlex variable values that are logged within the dlogger output file as the Alternate Name if one is specified. If the Alternate Name is not specified, the CyFlex Variable is referenced as the CyFlex Variable in the output file. |
Select the ECM List tab to display Ext. Numbers and associated ASAM Specs Paths.
Right-click a table row within the ECM List tab and select Insert Row from the pop-up menu as in Figure 33.
Figure 33: Insert ECM List Row
Execute the following steps to edit data in an ECM List row:
Figure 34: ASAM3 File Selection
Right-click a table row within the ECM List tab and select Remove Row from the pop-up menu as in Figure 35.
Figure 35: Remove ECM List User Row
Table 5 lists the keyword that can be added via the Scan List Aux User tab.
Table 5: Keywords that can be Added via the ECM List Tab
Generated Keyword In Spec File |
Definition |
@ECM_LIST |
Location and filename of an ECM spec file where ECM variables names will be read to add to the list of variables that are logged within the dlogger output file |