New to Version 1.2

This version updates the way the CSV file and TDMS files are configured and stored, and adds TDMS file path columns to the CSV file (one for each test). Furthermore, it now allows configuring a timestamp format.

As before, a new CSV file is generated each time the plugin is launched, and each test run during the life of the plugin is recorded with a row in that CSV file. However, when tests are complete, this plugin now copies the TDMS data files from their original generation location into a new, specified location and those file paths are captured in the CSV file accordingly for each test run.

Below is a sample configuration snippet showing the new configuration options (where notably, the logFolder has been replaced by the csvFilePath which allows more flexibility in naming the CSV file):

"timestampFormat": "%Y-%m-%d %H.%M.%S%.3u",
"csvFilePath": "\\JADE_LOGS\\@VAR{instanceName}\\csv\\Test-Results-@VAR{timestamp}.csv",
"tdmsFileHandling": {
    "signal1": {
        "copyFromPath": "\\JADE_LOGS\\Signal 1 Acquisition\\Signal-1.tdms",
        "copyToPath": "\\JADE_LOGS\\@VAR{instanceName}\\tdms\\Signal-1-@VAR{serialNumber}-@VAR{operator}-@VAR{timestamp}.tdms"
    },
    "signal2": {
        "copyFromPath": "\\JADE_LOGS\\Signal 2 Acquisition\\Signal-2.tdms",
        "copyToPath": "\\JADE_LOGS\\@VAR{instanceName}\\tdms\\Signal-2-@VAR{serialNumber}-@VAR{operator}-@VAR{timestamp}.tdms"
    },
    "signal3": {
        "copyFromPath": "\\JADE_LOGS\\Signal 3 Acquisition\\Signal-3.tdms",
        "copyToPath": "\\JADE_LOGS\\@VAR{instanceName}\\tdms\\Signal-3-@VAR{serialNumber}-@VAR{operator}-@VAR{timestamp}.tdms"
    }
}

Notice the timestampFormat is now configurable. Also notice the csvFilePath is configurable and may use the @VAR{instanceName} and @VAR{timestamp} variables, where the timestamp here is taken when the CSV file is created. Finally, observe that the tdmsFileHandling configuration holds the copyFromPath and copyToPath information for each signal / test. The copyToPath entires can include variables: @VAR{instanceName}, @VAR{serialNumber}, @VAR{operator}, and @VAR{timestamp} where the timestamp here is taken when the operator initiates a given test run (more specifically, if the operator selects to Run All Tests then the timestamp will be the same for all 3 TDMS files for that test run; think of it as the test run start time).

The columns in the CSV file are now:

• Timestamp
• Operator
• Serial Number
• R1
• R2
• R3
• R4
• R5
• R6
• Test 1 Result
• Test 2 Result
• Test 3 Result
• Test 1 TDMS File Path
• Test 2 TDMS File Path
• Test 3 TDMS File Path

Overview

This is a custom plugin which captures the test interface for the Sandia Load Box Test. It is intended to be straightforward and provide steps for the operator to follow when executing steps. In step 1, the operator must select or enter their name and a serial number before proceeding. The operator may optionally enter values for resistors here as well. In step 2, they may then choose to run any of the 3 defined tests, or all of the tests (which will then run in sequence). In step 3, after tests are complete, the operator can then indicate the test result as a pass or fail for each test. Finally, in step 4, the operator must click the Reinitialize button before beginning a new test. Data from the test or tests just run will remain visible until the Reinitialize button is pressed. The user will then be back at step 1 and will need to enter a serial number again, at the very least, before proceeding.

User Interface

The following shows the user interface and the 4 steps described above.

Configuration Example

Configuration Details

[]

[]