You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I started getting this error. It is coming from the error branch of the RxJava code for getting ECG. It continued to get HR and RR values. It never got ECG values. I catch that exception and show an exception dialog.
It persisted. Removing the H10 from the strap did not fix it. I was eventually only able to get it working again by removing and replacing the battery. So it clobbered the H10.
I had made no significant changes to the code. The primary one was to just not call the API if all permissions were not granted. (This keeps it from crashing as in #246 if permissions are not granted, since the crashing is in the SDK, and it doesn't look like that's going to be fixed soon.) I did nothing that would affect taking EGCs. I had just checked it with no permissions granted before restoring the permissions and getting this error. Since it no longer starts the API without all permissions granted, that should not have mattered.
that occurs right before "ALREADY_IN_STATE_ERROR".
First byte (0x00) indicated ECG measurement type data frame is received on Data Characteristic of the BLE Pmd service, which explains "ALREADY_IN_STATE_ERROR" as it seems the device is already streaming ECG data.
Next 8 bytes are time stamp : D8 F2 92 9C 49 D9 BA 09 (little endian)
And next one is the frame type : 0x00 -> which is the frame type used for ECG by H10.
It doesn't seem to be a bug, I will close the ticket, but feel free to open a new one if you still have issues with getting ECG data from H10.
Platform on which you observed the bug:
Device on which you observed the bug:
I started getting this error. It is coming from the error branch of the RxJava code for getting ECG. It continued to get HR and RR values. It never got ECG values. I catch that exception and show an exception dialog.
It persisted. Removing the H10 from the strap did not fix it. I was eventually only able to get it working again by removing and replacing the battery. So it clobbered the H10.
I had made no significant changes to the code. The primary one was to just not call the API if all permissions were not granted. (This keeps it from crashing as in #246 if permissions are not granted, since the crashing is in the SDK, and it doesn't look like that's going to be fixed soon.) I did nothing that would affect taking EGCs. I had just checked it with no permissions granted before restoring the permissions and getting this error. Since it no longer starts the API without all permissions granted, that should not have mattered.
This is the Logcat output.
ERROR_ALREADY_IN_STATE-2020-03-20.txt
The text was updated successfully, but these errors were encountered: