S9 Autoset SD Card Capacity?

BernieRay wrote:I don’t know why they chose the specific 365/30/7 day limits. I just know that with their current file scheme, they couldn’t reliably, if at all, store 365 days of details and HRD on a 1 Gb SD card.

Very true, but Resmed could easily store a lot more data if they wished, or saw value in doing so. I've been using my card for close to 7 months with no reformat. It still has only just over 30 mb of space used up. But 7 months is the end for this card as I had to get a new machine the other day and the DME put in a new card. The old card would have been wiped out because of the change in machine S/N.

New data from the new card imports into my existing patient file so the machine serial number change does not affect downloading.

What is high resoultion on the s 9 data card I haven't noticed anything onthe report, except detail,summary,etc

The high resolution data refers to that collected within the last 7 days. When you open those files you can zoom in and see what's going on breath by breath in exquisite detail. Since the data density of those files is so high, the S9 only maintains those files for only 7 days. It would be nice if we could have, say, 30 days worth of high resolution data, given the low cost of memory cards.

I'd like to say thank to the OP and those that have responded to this thread. I've been doing it all wrong and just assumed that everything was working correctly because I'd still see some of the detailed charts in days that were older. First, I was using the overwrite, rather than discard during uploads and even though I was doing back-ups of my ResMed directories (thinking I was smart), I would replace previous back-up versions as new ones were done. In doing this, I didn't realize the details were being deleted as days go by. I just verified that by looked closely at the file sizes in the "Patients" directory as well as the charts displayed within ResScan.

Perhaps a "best practices" summary is in order. It might start a debate, but it could also help organize file planning for those of us that didn't have that as a priority. What is the best way to handle it? Do we reformat as there was talk in another forum of data getting off-sync the older it gets? Or, is it best just to pick the discard data option during uploads?

Again, thank you for this thread... Very helpful.

Slartybartfast wrote:It would be nice if we could have, say, 30 days worth of high resolution data, given the low cost of memory cards.

You can have years of unlimited HR data through ResScan, and clinicians on the whole really dont care much about anything more than a week old in terms of any emphemeral/intrinsically highly variable data (like OSAs events)....

Bandnuts wrote:I'd like to say thank to the OP and those that have responded to this thread. I've been doing it all wrong and just assumed that everything was working correctly because I'd still see some of the detailed charts in days that were older. First, I was using the overwrite, rather than discard during uploads and even though I was doing back-ups of my ResMed directories (thinking I was smart), I would replace previous back-up versions as new ones were done. In doing this, I didn't realize the details were being deleted as days go by. I just verified that by looked closely at the file sizes in the "Patients" directory as well as the charts displayed within ResScan.

Perhaps a "best practices" summary is in order. It might start a debate, but it could also help organize file planning for those of us that didn't have that as a priority. What is the best way to handle it? Do we reformat as there was talk in another forum of data getting off-sync the older it gets? Or, is it best just to pick the discard data option during uploads?

Again, thank you for this thread... Very helpful.

Check out wiki/index.php/ResScan and look for the link to the video tutorial. I believe it answers most of your questions with what many of us consider to be best practices with ResScan. Also, take a look at http://montfordhouse.com/cpap/resscan_t ... practices/ for how to work with the S9 card. If you follow the suggestions in these two videos, you'll be in good shape.

idamtnboy wrote:Click on discard, not overwrite. When you click on overwrite Resscan keeps only as much detail and hi-res data as there is on the card. When you select discard it tosses out the data off the card that is already in Resscan. It downloads all new data and adds it to the already stored data. It's a weird download option that doesn't really make sense, but that's the way it is. As long as you never sleep over the noon hour and download that afternoon and the next day also, you won't have any problems.

Does it give you that option ONLY on the 2nd & future downloads.

I just downloaded the 1st 9 nights & it did not give me any option to discard nor overwrite.

Is it because there was NO data yet in ResScan so it did not have any data to either discard nor overwrite.

Of course, by waiting 9 days to download (instead of 7), I lost out on 2 days of the High Resolution Data.

billbolton wrote:

Slartybartfast wrote:It would be nice if we could have, say, 30 days worth of high resolution data, given the low cost of memory cards.

You can have years of unlimited HR data through ResScan, and clinicians on the whole really dont care much about anything more than a week old in terms of any emphemeral/intrinsically highly variable data (like OSAs events)....

Do you mean you can have that data as long as you take the card out every 7 days and save the data on your computer?

I save the reports as .pdf files weekly, so I don't really need 30 days of detailed data. Once I've reviewed it and saved it as a report, there's really no need since my therapy is working and I have no other health issues. It would be convenient to not have to review the data weekly, though, and that's where I was coming from.

I'm coming up on my 18 month appointment and will probably take reports of the last week's worth of data. I also gather about 3-4 days of data from my pulse oximeter (CMS 50e) and print that out. Besides compliance, THAT's what the doc really seems to zero in on.

BernieRay wrote:I don’t know why they chose the specific 365/30/7 day limits. I just know that with their current file scheme, they couldn’t reliably, if at all, store 365 days of details and HRD on a 1 Gb SD card.

Thanks for the very useful info, BernieRay.

It still amounts to they're too stupid or uncaring to do it right. A first year C average programming student could have written a program to also create an additional file in .zip format the first session of every day and save ALL of the previous night's detail data in a single file and only take up an extra 4K each night. A first year B average programming student would append the current day's data to the existing zip file data, and only waste 4K overall.

Why not use NTFS and permit 512 byte writes, this should provide enough room for all the data, at least a much better use of memory. Larger file allocation tables, but the overhead is not that much. Or, ResMed could simply permit larger sd cards if users purchase them. I know they end up using what they feel is sufficient data storage, and cost. Now, however, sd cards are cheaper than dirt. We have come a long way since the original PC-1 had an optional about $570 list price 64K memory board, and required a bios change to access those two MONGO 20 MB ST-238 Seagate drives, that would "never" fill up, but did 5 months later. I have help files that are larger than those drives! (and use Linux Mint now about 95% of the time).

sprinklebum wrote:Why not use NTFS and permit 512 byte writes, this should provide enough room for all the data, at least a much better use of memory. Larger file allocation tables, but the overhead is not that much. Or, ResMed could simply permit larger sd cards if users purchase them. I know they end up using what they feel is sufficient data storage, and cost. Now, however, sd cards are cheaper than dirt. We have come a long way since the original PC-1 had an optional about $570 list price 64K memory board, and required a bios change to access those two MONGO 20 MB ST-238 Seagate drives, that would "never" fill up, but did 5 months later. I have help files that are larger than those drives! (and use Linux Mint now about 95% of the time).

I think you may have missed the gist of the comments above. The amount of data on the SD card has nothing to do with card capacity, at least not in the past few years. It has everything to do with how many days of data recording the Resmed engineers have programmed into the S9 data recording system. I myself believe that generally speaking doctors are not particularly interested in high resolution data more than seven days and detail data more than 30 days old. That's why Resmed doesn't record it. I suspect most doctors don't care to look back at summary data for a full year even though that is available. The engineers had to make a limit somewhere, and the current limits apparently keep the sleep doctors happy. Data recording is not designed for patient monitoring so what we want matters not one whit to Resmed.