05-24-2016, 04:57 PM
(This post was last modified: 05-24-2016, 05:01 PM by Brewskie.)
SleepyHead ver 1.0b2 not syncing w/oximeter
After updating to sh1.0 beta 2 my oximeter is not synced with my CPAP.
I always turn on my ResMed S9 first then turn on the recording on my Contec CMS50FW 3.7 oximeter. I also turn off my oximeter before I turn off my CPAP.
What's been happening is that SleepyHead shows that the oximeter keeps recording for several hours longer than it actually was.
In the image attached you can see how the meter keeps running past the time I stopped the CPAP.
Any ideas what's happening here?
Win10
SleepyHead 1.0 beta 2
Resmed S9
Contec CMS 50FW 3.7
RE: SleepyHead ver 1.0b2 not syncing w/oximeter
Anyone have any idea what to do about this?
Last Wednesday my doc said he can't use the printout over this.
Thanks!
06-07-2016, 05:43 PM
(This post was last modified: 06-07-2016, 05:44 PM by Crimson Nape.)
RE: SleepyHead ver 1.0b2 not syncing w/oximeter
It's a known bug. The work-around is to use the SpO2 Assistant to download the data from the CMS-50 then import the .spo2 file into SleepyHead.
You will also need to purge the old oximeter data in SleepyHead before you re-download the data.
RE: SleepyHead ver 1.0b2 not syncing w/oximeter
Oh great
I've never been able to get SP02 to work.
It says it's connected and getting data then just sits there.
I reinstalled it after going to Win10 too.
I think it's ver 1.5 but I don't know whether there's an update.
Any ideas?
RE: SleepyHead ver 1.0b2 not syncing w/oximeter
OK! Here is another idea. SH version 0.9.8.1-T3-Testing works correctly.
Here is the link if you don't have the older version:
http://www.apneaboard.com/SH-old/
My SpO2 Assistant is version 2.7.
You can download a newer version (2.4) from
Supplier #19. For some reason I seem to be the only one with version 2.7 number.
I hope this may help.
RE: SleepyHead ver 1.0b2 not syncing w/oximeter
I was using the T3 ver before and I verified that it does work correctly.
I wish I would have thought of using the earlier ver :/
I'm glad to know that it's a known issue and will wait for an update
Thank you!