LabGateway

Approved

It is now possible to stop an ongoing recording by sending a trigger of 0 seconds (via webinterface or via API).
An ongoing recording is continued if the Gateway experiences any issues or is rebooted during the recording.
Internal improvements.

In some occasions the green LED was blinking but the Gateway was not recording any data.

Sensor errors are now reported to the server and displayed in different places of the web interface (e.g. if the PPG Signal is too low due to a defect):
1. The serial number of the sensor in the dash view will turn red (you may click on it to go directly to the sensor's detailed view).
2. In the sensor' detailed view, all found errors for this sensor are listed.
3. In the device overview, all devices with errors are marked with a red indicator.
- Please note that in some occasions the sensor may still be functioning correctly when the error is reported but it might be a loose contact in an initial stage. In that case please have an eye on the sensor if its condition is worsening.
Server: “HELP” link in the navigation bar now leads to public wiki page.

Data upload bug of LabGateway. If connected the LabGateway will upload all data previously available - independent from the currently assigned person.
Restarting loop of LabGateway.

Live data (feature on request). Known Issue: Sometimes no data is sent, especially when recording two sensors simultaneously.
Acceleration data. Please note: Sometimes acceleration data is sent patchy and time-delayed, causing a shift between PPG and ACC data especially during long recordings. Newest sensor firmware required (°Two 3.0.0, c-med° alpha upcoming).

Enable WiFi for the LabGateway. Technical Guide: here.
Modified advertising packets. More information available under: Select Device > advertising info.

The c-med° alpha and the °Two shall no longer be used in Standard Mode with the LabGateway if the sensor firmware is higher than 2.0.2.