Creating a Running Test Log - VN0002
The standard Tables option can be used in combination with the Test Notes window to create a running log of the test.
How can you keep a running log of a test?
The Tables option is designed specifically for this situation. Tables are defined on the Tables tab on the test setting dialog. The tab for a Sine test is shown below.
For each test, up to five tables can be defined. A table is simply a collection of data about the test. This data is generated by evaluating repot parameters in the Formatted Parameter Strings input box at specified intervals. The resulting text is stored in the data file. These tables can later be included in reports.
- Step 1
Use the help file to find the parameters to put into the five rows:
- Bring up the help file by selecting the <F1> key
- Select the plus <+> next to Reports and Forms
- Select the plus <+> next to Report parameters names
- Select either <Overview> or a specific test type. Overview includes parameters that are common to all tests. The specific test contains only parameters that are specific to that test type.
The values to enter in the rows will all look like [PARAM:something]. This will get replaced with the actual value of the parameter.
- Step 2
To setup a running log of G’s and Frequency for Channels 1 – 3 first find the parameters to use in the help file.
- Acceleration for channel 1 is [PARAM:Ch1Accel]
- Current frequency is [PARAM:Frequency]
- Use \t to enter a tab to get things to line up correctly
- If applicable, include the time when these reading were taken by adding the [PARAM:TIME] parameter
- The resulting format string will look like: [PARAM:TIME]\t[PARAM:Ch1Accel]\t[PARAM:Ch3Accel]
- Step 3
Specify how often to take these readings by using the check boxes below the parameter strings:
- To take a reading every 15 seconds check the box next to Every (hh:mm:ss) and enter < 00:00:15 >. < 15s > can be entered as a shortcut for 15 seconds, < 15m > for 15 minutes, or < 15h > for 15 hours.
- The final thing to do here is select the < Append to Test Notes > check box. That is what allows the live updates
- Notice: each row represents a unique table and has its own update interval settings. If after entering a string of parameters they are not updating as often as specified, or not appearing in the test notes, click on that row and then check to be sure that the update settings are correct.
- When the < every (hh:mm:ss) > check box is selected, the [PARAM:] fields in row 1 are replaced with values. This tests the parameter string to see if it is valid. If the parameters are valid, they are replaced with current values. When the row is selected, the parameters are again displayed.
- Step 4
Log every change in the test status. Click on row 2 and then select < every change in test status > check box. Row 2 was populated with [PARAM:TIME]\t[PARAM:STOPCODE]
VibrationVIEW tries to enter some reasonable default whenever possible. Select < Append to Test Notes > and select the < Apply > button for the test to run. Below are screenshots of how the tables should be setup.
Testing the Solution
Start running the test and bring up the Test Notes by selecting < Test Notes > from the view menu. There are readings for the parameters that were entered. Below is an example screen shot. After about 45 seconds the control channel disconnected so the test would abort. (There also was no accelerometer on channel 3.)
One final note, the results of these parameter strings can be included in reports. To put all of the values displayed by the first string in a report, use the [PARAM:Table1] parameter. For the second row, use [PARAM:Table2].
Other Test Notes Hints
- To manually enter test observations, type in the Test Notes window
- Press < T > to enter a date and time stamp in the test notes
- The font and color of lines can be changed, allowing you to highlight specific test notes
- To include the Test Notes in your report use [TESTNOTES]