Fusion_v1.0.0

• Added support for Shimmer3ECGmd running BtStream v0.10.0
• Removed support for Shimmer3ECG
• Bug fix for QRS isolation algorithm when using ECG channel Vx-RL

StroKare_v1.1.0

StroKare solution v1.1.0 includes Software v1.1.0, Firmware v1.1.0 and Python example code. This release includes a fix for a bug reported by Helbling in-which certain SD data files in a session had a started time which was prior to the end time of a previous file. This issue was a result of a timestamp mismatch between 3 byte timestamp in the first packet of data and the lower 3 (of 8) bytes timestamp denoting file creation time (stored in the files header) which is needed for real-time-clock calculations. On certain occasions, the second data packet's timestamp was being used as header timestamp instead of first packet's timestamp.
This issue has been resolved in Firmware v1.1.0 and a fix has been implemented in the software v1.1.0 that corrects for this issue for any previously recorded binary data when the data is re-exported to CSVs.

Fusion_v0.5.0

S:\Applications Team\Customer\Enterprise\CIMIT\Documentation\Feedback from CIMIT\Fusion Feedback Response_RevC.docx

Consensys_v1.4.2

Consensys_v1.4.2 for RTT only.

Fusion_v0.4.0

• Various feature requests and functionality modification from CIMIT, see documentation on Jira

StroKare_v1.0.1

StroKare solution v1.0.1 includes Software v1.0.1, Firmware v1.0.0 and Python example code. This release includes additional features for the Python interface to the ConsensysAPI, namely:
• The ability to copy binary data from the Shimmers and separately to parse binary data to CSVs from a chosen path.
• The ability to delete binary data files from selected Shimmers.
• The ability to access the SD card on a particular Shimmer in a Base.

StroKare_v1.0.0

StroKare solution v1.0.0 includes Software v1.0.0, Firmware v1.0.0 and Python example code. This solution builds upon the requirements met in v0.3 along with the following additions and changes to functionality:

1. REQ_SMS_013: Auto start/stop logging
   As per version 6.0 of the “Requirements Shimmer Measurement System” document, the LED charging and discharging behaviour has been altered as per the updated specifications.
   Charging
   • The charging status of the LED’s has been updated to give the following change-over points:
   o RED (critical) - > YELLOW (medium) at 80% charged
   o YELLOW (medium) -> GREEN (full) at 98% charged status
   • Note: a value of 98% has been chosen as this takes into account degradation of battery health after extended use. It is therefore advisable to continue charging for a further 10 minutes (at the most) to ensure 100% charged status.
   Discharging
   • Section 3.5 illustrates the battery discharge curve and outlines the different battery charge states and their associated LED operations while the Shimmer is undocked and logging data.
2. RTC loss – improved robustness
   As per reports from Helbling, 3 of the 14 units under test experienced RTC loss issues around docking/undocking the units under test. With this in mind, StroKare_v1.0.0 firmware aims to mitigate some of these issues and add robustness to the Shimmer’s operation with added checks for the current RTC state of the Shimmer while logging and improved logic flow throughout the operation of the firmware.
   To help further mitigate docking issues, it has been observed that the following instructions give consistent results.
   • Docking
   o Insert the dock connector end of the cable into the Shimmer device ensuring one can hear an audible “clicking” sound upon insertion.
   o Insert the USB end of the cable into the provided USB charging port.
   • Un-docking
   o Squeeze the dock-connector end of the USB cable and gently remove the connector from the Shimmer.
   o Disconnect the USB end of the charging cable from its connected port.
3. Python interface
   The number of features supported by the Python interface has been expanded and the Python sample code has been improved to provide easier control of the StroKare software and greater feedback of on-going operations.
4. Boot options
   The available options that can be passed into the software on execution have been expanded to include an option to disable the GUI and to change the Madgewick Filter Beta constant.

StroKare_v0.3.4

1. Quaternion generation fixed for StroKare (bug related to different sampling rate for IMU sensors compared with EMG)
2. Quaternions switched back from 6DoF to 9DoF

NeuroLynQ_v0.4.3

• Bug fix for playback pause/resume
• Bug fix for event marker thread

NeuroLynQ_v0.4.2

removed casting/uncasting from long/double on timestamp