Line | |
---|
1 | WARPLab 7 was built with user extensions in mind. This directory serves as an example of how to extend |
---|
2 | the capabilities of WARPLab without having to directly modify the existing framework. |
---|
3 | |
---|
4 | This directory contains two files: (a) user_extension_example_class.m and (b) user_extension_script.m |
---|
5 | |
---|
6 | (a) user_extension_example_class.m |
---|
7 | This file is an example user extension object that implements two new kinds of WARPLab commands |
---|
8 | (commands for writing and reading the EEPROM located on the WARP board). To add these commands, |
---|
9 | nothing inside the rest of the M_CODE_REFERENCE folder that contains the WARPLab framework was |
---|
10 | modified. This allows user extensions to seamlessly attach to new versions of WARPLab as they are |
---|
11 | released. |
---|
12 | |
---|
13 | (b) user_extension_script.m |
---|
14 | This file is an example script that knows how to use the user extension example class. It first will |
---|
15 | read from the EEPROM and print any string that is stored there. It then overwrites that part of the EEPROM |
---|
16 | with a new string. After written, the board can be unplugged and reconfigured. Despite the power loss, |
---|
17 | the script is able to read the stored EEPROM string. |
---|
Note: See
TracBrowser
for help on using the repository browser.