20250122 - v2.2.5 - Modified shell capture behavior. Previously, the SH pin had to be pulled low to access the shell even after a capture operation. Now, when the shell is captured at startup, it will remain active until reset. 20250121 - v2.2.4 Syncronized with SSR-1U 2.2.4, adding the following fixes and updates: - BugFix: Time Tagged archives failed to start with a Time Correlation Packet when opened as part of a close/open operation based on a configured file size or time costraint. - BugFix: Fixed shell issue where bad boolean options weren't rejected as syntax errors. Also made the acceptable boolean words case insensitive. - Updated the non-inverted command sources to display with a leading '+' in config and status shell output for clarity. - BugFix: Fixed relative path support in the shell for exFAT volumes. Now cd .. works and pwd provides correct results on exFAT. - The shell current working directory is now preserved after volume remount operation (e.g., card removal/insertion) if possible. - BugFix: Shell command sz included specified path with the zmodem transmitted filename and should not. - BugFix: Fixed the shell time command to correctly set times using the AM/PM designator on the 12th hour. Previously, times entered as 12AM were registered as 12PM and vice versa. - BugFix: Fixed shell to prevent extra characters from being consumed when using backspace in the middle of a command line. Line editing using backspace now works correctly. - BugFix: Fixed issue recognizing a single forward slash as a valid path in the shell. - Bug Fix: Corrected a problem that caused tagged line timestamps to be occasionally inserted soon after a new file was opened. - Bug Fix: Corrected a rare problem in which the seconds of a timestamp could be incremented prior to the fractional seconds, resulting in a timestamp sequence with seconds like: 2.907, 3.999, 3.091 20191010 - v2.1.1 - Fixed bug introduced in v2.1.0 that prevented periodic file system sync. Without periodic sync, data in unclosed files was not preserved on power loss. 20190906 - v2.1.0 - ******** NOTE ******** ** This firmware will invalidate stored configuration information ** of previous firmware versions, returning all parameters to default ** factory settings. Make note of the stored configuration of the ** SSR-1 prior to updating the firmware. ********************** - Support for exFAT, and SDXC cards - Minor performance improvements - Added support for 7 bit data frames (with even or odd parity) - Bug Fix: corrected problems with parity enabled reception - Added options to disable on-board LEDs to conserve power 20180227 - v1.2.1 - Recognize 0xA (in addition to 0xD) as a line-end for the new tagged line record type. Now, either character will trigger a timestamp on the next printable character. 20180213 - v1.2.0 - Added a new record file type 'tl' (tagged line) that does native time stamp tagging of line oriented text. Timestamps are inserted before the first printable character (ASCII 0x21 to 0x7E) following a CR (0xD). Timestamp format is YYMMDDhhmmss.sss followed by a space. To enable the mode, use the shell command 'cfg file type tl' 20170424 - v1.1.0 - Added support for card power control (power cycle reset) in future hardware revisions. - Protected card writes with CRC to improve robustness during power events. - Improved zModem file send performance. 20161122 - v1.1.0-beta - Added sz command to shell for sending files using zmodem protocol. - Increased max speed for standard configuration from 115200 to 230400 baud. - Added support for a high speed variant that can record at 460800 baud. - Modified file path parsing in the shell to allow for shell command arguments that begin with '-'. File names can no longer begin with '-'. 20160504 - v1.0.2 - Bug Fix: Time tagged archives were not getting periodically flushed so that the last several bytes received might not get preserved on loss of power. - Reduced latency between changes in the record command state and action by the logger. 20150501 - v1.0.1 - Bug Fix: Shell could not reset com channel stop bits to 1. Config erase was required to restore stop bits to default value of 1. 20140506 - v1.0.0 - First released version.