Test recipes encode all the information needed for an efficient measurement experience by running the measurement device and extracting both raw and meaningful data of a unit parameter test procedure. They are part of the user interface connecting the parameter test procedure and the test device.Test recipes contain information regarding measurement condition and parameters to analyze the result data. Measurement settings for test recipes either have default or preset values which may or may not be altered by the users and the information about the set condition can be saved as a data file which can also be edited for later use. The information about the test sample and the test log (information about the tester, date of test, used device etc) can also be recorded in the data file.
(Figure 1) Property for secondary battery discharge recipe.
The unit test procedure begins in accord with the measurement setting set by the tester and terminates once the measured data meets the end condition. If a ‘sequence’ – a series of multiple unit test procedures- is constructed and sent to the device instead of a single test procedure, once the end condition is met the device moves on to the next test procedure until all the tests in the sequence are executed. What is special about McScience’s measurement device is that such a sequence of tests can be executed in the device alone without the need to maintain a continuous connection with the measurement software and/or the PC. Therefore even if the connection is lost the device will independently execute the tests and save the result data within its memory, which can then be collected and recorded by the PC once the system is reconnected. Such a functionality is called ‘data-scratching’.
(Figure 2) System Configuration.
The measurement result data is collected and sorted into spreadsheet data files in ModenJay Platform. The result data is also displayed within the software user interface as graphs. A feature of ModenJay is that it also provides a metadata format which is a structured representation of the result data including the extracted data summary, characteristic parameters, and other relevant information about the test procedure which may have different formats for different test recipes. A detailed information about metadata will be provided in the next article.
- Mr.Overain is a nickname character of DONG WOON KIM ( firstname.lastname@example.org )