Difference between revisions of "HANcoder/STM32/Blocks/File Logger Close"
m (Jasonvankolfschoten moved page HANcoder/File Logger Close to HANcoder/STM32/Blocks/File Logger Close without leaving a redirect) |
|||
Line 21: | Line 21: | ||
{{HANcoder/BlockFooter| | {{HANcoder/BlockFooter| | ||
− | |SeeAlso = [[HANcoder/File_Logger_Init|File logger init]] {{!}} [[HANcoder/File_Logger_Signal|File logger signal]] | + | |SeeAlso = [[HANcoder/STM32/Blocks/File_Logger_Init|File logger init]] {{!}} [[HANcoder/STM32/Blocks/File_Logger_Signal|File logger signal]] |
}} | }} |
Latest revision as of 10:20, 5 May 2017
Supported Targets: Olimexino, E407, P405
Contents
General information about File Logger Close
With the File Logger module active, the data values of the configured signals are sampled at a fixed time interval and written to the log-file on the SD-card. The log-file needs to be explicitly closed at the end of a logging session for the log-file to actually appear on the SD-card. Ideally, this block is called during software shutdown for example when the ignition signal goes low in automotive applications. An external trigger can also be used such as a button press event or CAN message reception.
Block
Mask
Block inputs (inports)
Trigger input: When the value of this signal changes from 0 to 1 the file logger close block will be executed and the file on the SD card will be closed.