Syncing O2 Ring and CPAP clocks

[coldfeet7]

I use a Wellue O2 ring and a Resmed BiPAP and have a hard time keeping the clocks sync'd. I sync the ring to the PC every 3-4 days, BUT the CPAP seems to drift. I don't know why the CPAP doesn't sync with a time source since it is connected to a cell tower often. Some might argue you don't want it to change time zones if you are traveling, but it could at least adjust the minutes and seconds to stay accurate.

Has anyone come up with a way to easily set the Resmed clock? It is such a pain to watch a clock and try to get the full time set accurately. I suspect they never expected anyone would be trying to sync two devices.

Maybe someone has hacked the CPAP firmware to enable a time sync feature?

[Crimson Nape]

Yes, there is a way! Please read this Wiki on syncing your Viatom/Wellue oximeters with your CPAP in OSCAR:
http://www.apneaboard.com/wiki/index.php...with_OSCAR

- Red

[coldfeet7]

Thanks for the link. Examining my ring's files, I see some STRANGE behavior. Notice that TWO days were loaded into my April 16th data (they are overlapping in the display) YET the dates are 16 and 17 in the ring files (as seen in the open file dialog).

Doesn't this look like an OSCAR bug? I have seen it on other days as well. I am running OSCAR 1.4.0+e35d47b3. This seemed to start happening recently (last couple of months). I load my ring data twice a week to avoid over flowing the 4-day buffer. Each time, I go into the Pro app (on the PC) ring config and sync the clock with the PC to avoid clock drift.

   

Thoughts?

[Crimson Nape]

A CPAP's day is from noon to noon the next day. One was after 11PM on the 16th and the next occurred a 2AM on the 17th. These two are within the CPAP's 16th day.

- Red

[Jeff8356]

coldfeet7,

Would you mind giving us a more detailed description of how you are importing the oxi data into OSCAR.

It seems the the data on the 16th runs from 23:27:02 to ~06:20:?? and the data from the 17th runs from 02:18:33 to ~08:10:00.

Typically the only time we see two oxi data files imported on the same day is if you had the oximeter recording for more than 10 hours (the limit of wellue oximeter sessions). The second session usually starts about 5-6 minutes after the end of the 10 hour limit.

[coldfeet7]

Ahh....   so the ring (almost two years old now) messed up and somehow recorded it incorrectly. I have noticed on a couple of occasions where I have awakened in the night, checked the time and it was WAY OFF.  Like 3 PM, not 3AM. Since I sync the clock twice a week with the PC clock, using the O2 Insight Pro software, I know it should be very close to the right time. That mess up causes the time shift that puts two night's readings in the same noon to noon window I guess.

[coldfeet7]

I import the ring data into the PC using Viatom's O2 Insight Pro v1.8.0 software (latest version). I then use OSCAR's Import Viatom/Wellue Data option to retrieve the recently data. Using the earlier example (the original post) I went back and use the )2 software to check the 16th and 17th. I shows only two for the 16th (though the files are amed with the 16th and 17th) and none for the 17th. See in the capture that it reports (in the lower left corner) "The file is corrupt" when I select the 2nd 16th (the one 02:18:33 to ~08:10:00). Something stinks big time. Sounds like the ring is going flakey and their software is getting confused by the data as well.

   

This doubling up happened on May 2nd as well, however, with the 5-6 minute gap you mentioned. BUT I NEVER sleep 10 hours or otherwise wear it that long. I KNOW I used it two separate nights. So the May3rd O2 data is missing in OSCAR because it was dumped inside the noon to noon window for the 2nd.

I checked the O2 data file names and indeed the date didn't advance as expected.

You can see it in the capture below.

   

I'll need to get a new ring I guess, because I believe I am outside the warranty. Thanks for helping me figure out it is the ring. Its a shame really because the battery still lasts well and the display works (though dimmer). Maybe I'll butcher it and find a way to strap it on an ankle to measure PLMs (the most common area to be moving).


P.S.
The reason I have the movement scale for the ring data set so limited is because you can't see what appear to be PLMs otherwise. They are too slight. This capture is taken from the above capture, zoomed in, to see the period of the movements. I find it hard to believe those are artifacts.


   

P.P.S.
My jpgs are 172k but when I upload them to this site it reports them as being over 600k. Anything I can do to make this more efficient for your server space?

[Crimson Nape]

I haven't compared sizes, but OSCAR generates a PNG file when you use its F12 or Fn+F12 for a Mac
screen capture option.  Using this option also aids in formatting the Daily screen by closing certain displays while it grabs the image.

- Red

[coldfeet7]

I looked closer and found that converting from SnagIT format (172k) to jpg was over 600k. I was confused about the one I looked at. The one below is a PNG (exported from SnagIT) and it is about the same size when uploaded to this site. My bad. PNG is way better than JPG.

   

[Crimson Nape]

Out of curiosity, why aren't you using the embedded screenshot feature of OSCAR?
- Red