More SvO2 A$$t/CMS50F 'issues' -- missing session

[ShaunBlake]

Last night's sleep was interrupted by my supposed caretaker, who informed me she had an urgent need to go potty. I turned off the AS10 AS and stopped the CMS50F recording, took her out, then turned both devices back on (recording in the oximeter) and tried to sink into restful sleep for the next 3+ hours. Loaded the AS10 data into SH, then extracted the (single! <gasp>) data file from the oximeter.

I've previously successfully recorded multiple sessions on the oximeter -- but never with a break of just over 6 minutes. Do we have any oximeter bit-brains who can tell me how the SpO2 A$$istant saves files, and what circumstances cause it to begin overwriting?

Is the first session still on the device, and if so how can I access it?

Thanks for any comments, even those I don't want to hear!

[Crimson Nape]

As far as I know the "F" model only records a single session. The "I"(eye) model can record up to 14 sessions, depending on the length of each session.

[ShaunBlake]

Thank you Crimson Nape! That may be, though I remember recording and uploading several days' data a few weeks ago. (I've had an astonishingly poor memory since my childhood, and now that I'm a very old man...)

Although I realize the data are probably gone, I hope that isn't the case -- especially because the first half of the night was sound sleep (with some large and very large Large Leaks) and I would dearly like to compare the two sessions.

I know a few folks have hacked at the files, and some have done so by analyzing the CMS50F data. However, everything I've found was in support of SleepyHead. I'm not finding any development or hacking of the device's interface or storage. <sob>

[Crimson Nape]

The only software editing that I'm aware of is the bug fix that entered SH v1. Version 0.9.8 worked fine during import from either the file or the device.

[ShaunBlake]

Yep, fixed my funky SpO2 file yesterday.

Clearly there are some very clever guys who are working on xPAP devices and associated software; I was hoping to find one of them had gotten irked at the S$$istant quirks and improved or replaced it.

I've taken a peek at the d'load stream with an eye toward understanding the way the data are organized though I'm really only interested in the CMS50's interface (the app that accesses, stores and retrieves the data) OR, worst case, th internal database configuration and structure.

I'm so frustrated with the sloppy interface and the device's functionality that I wish I could develope an app to replace SpO2 Assistant.

[Crimson Nape]

You may wish to download the source code for SleepyHead and peruse the file, serialoximeter.cpp, for an insight on how the data is accessed.

[ShaunBlake]

You may wish to download the source code for SleepyHead and peruse the file, serialoximeter.cpp, for an insight on how the data is accessed.

Something strange is going on here, Crimson Nape! The older I get, the smarter and wiser you get! Egg-selent suggestion!

[Crimson Nape]

.  .  .  Egg-selent suggestion!

Egg-xactly!

[pholynyk]

Well, it's not /that/ simple... You'll want to look at the cms50F37 (I think) loader plugin as well... It gets kind of convoluted

[ShaunBlake]

Well, it's not /that/ simple... You'll want to look at the cms50F37 (I think) loader plugin as well... It gets kind of convoluted

Huh. Nothing ever is. But that's okay -- in fact, that really is great. At some point (in the far distant future?) somebody is going to jump in and cobble a decent interface for the CMS50s if for no other reason than to end my frequent tear-jerker posts. OTOH, I do believe that miracles happen, so I suppose it's within the realm of probability that I might actually accomplish it. That "one-in-a-million" one... No, perhaps probability has nothing to do with this objective.