[Equipment] AirSense 11: Now have SD card in it

[jprestonian]

For those eagerly awaiting news, I borrowed a card reader from work, archived the AirSense 10 data off the card I have, formatted it, and the AirSense 11 seems to have been happy with FAT32 formatting. 

I'll zip up the files and hit the Dropbox link for the OSCAR folx, tomorrow. Maybe one night's data will help? 

-Jeff

[cathyf]

An A10 card has this file structure on it -- 3 files, 2 directories
All of these were created the first time the card was inserted in the machine
    Identification.crc -- a 4-byte file -- crc usually means Cyclic Redundency Check? not modified since created
    Identification.tgt -- a text file which contains serial number, product id, etc. not modified since created
    STR.edf -- a binary file, which gets modified every day at noon when the machine rolls the clock over
    DATALOG directory, which contains a series of directories with names that are dates in YYYYMMDD format
    SETTINGS directory, contains 16 pairs of files named xyz.crc and xyz.tgt, and then 9 .log files

Is what you have on the Air11 card exactly the same as the Air10 structure, pretty much the same with additions and changes (i.e. same idea, new version), or is it something completely different?

[jprestonian]

Is what you have on the Air11 card exactly the same as the Air10 structure, pretty much the same with additions and changes (i.e. same idea, new version), or is it something completely different?

I'll be able to tell you in 9-10 hours. 

-Jeff

[GuyScharf]

It will be similar, except identification.json instead of identification.tgt and all of the SETTINGS directory is now in a .json file.

In fact, if you create an identification.tgt file in the old format, using data you find in the .json file, OSCAR will run as that file is just to identify the machine. Displayed settings data will be wrong as the fields in the str.edf file have changed. ResMed has a bunch of variations on the str.edf file for different machines, and we have handled them all so far without much difficulty.

[jprestonian]

In fact, if you create an identification.tgt file in the old format, using data you find in the .json file, OSCAR will run as that file is just to identify the machine. Displayed settings data will be wrong as the fields in the str.edf file have changed.

Are you saying that in building a proper identification.tgt file, the rest of the reporting data will still be correct in OSCAR, other than  the machine settings reporting? If so, it sounds like y'all have it figured out, and you likely need no additional test data from "the field." If I've misunderstood, please DM me with that dropbox link, and I'll zip up what I have so far (only about 10 hrs. of data collection, so far). 

I eagerly await the update!

-Jeff

[Sleeper396]

In thinking about the AirSense 11 coming to market over the next few months, have you been able to get inside the clinical menu and make your adjustments? Are you comfortable that you have the same access to whatever you need, as on the AirSense 10? Any further thoughts on purchase of this new AirSense 11 vs. AirSense 10?

[cathyf]

Jeff, in response to S396’s question, maybe a new thread with something like “Airsense11, thoughts after XX days” as a title so that people will know that this is going to be about more than the card.

[GuyScharf]

Are you saying that in building a proper identification.tgt file, the rest of the reporting data will still be correct in OSCAR, other than  the machine settings reporting?

That's not been confirmed yet.  At my first glance, a few weeks ago, the graph data looked reasonable. It was immediately obvious that there were problems with the settings -- not particularly difficult ones but ones that required some work inside OSCAR. I did not examine the data further to see if there any problems in the graphs or statistics. All that needs to be tested to determine what work might be needed.

[jprestonian]

Just sent a .zip to your Dropbox link. Thanks!

-Jeff

[2albion]

Funny, my Airsense 11 was happy only with a FAT16 SD card.