Skew flow bug may be due to SD card speed...

Nord wrote:Did you keep copies of these SD cards ??? Did you copy the contents into a folder ???

I copied files today but haven't in the past.

Hi FF

We'll catch it next time... other people are at work to solve this.

Nord

Thanks to those who PM'd me...I'll take a look at the files and see what I can figure out.

Back to the top...

Nord wrote: Thanks Kenneth...

As soon as you get your machine and look it over... can you come back to this thread and we can go over some stuff.
We should be able to solve this issue with all the good help we got now.

Hi, Nord!

I just got my new S9. Pretty!

I probably won't actually use it for the first time until tomorrow (Friday) night, when I don't have to be up for work in
the morning (just in case something goes wrong).

Fortunately my allergy coughing seems to be settling down a bit. I didn't even crash my S8 last night.

OK, so is there anything I can report on, look at, test out, or otherwise provide to generate any clues?

Hi Ken

Yes it is pretty but it also has some complications... so far.
Install your software if you haven't already.
Record you Ser # and Lot # of the S9... something we're just looking at.

I just thought of something... another possibility...
I'll get back to you tomorrow about the process you should follow to keep your machine clean.

I won't forget.

Thanks
Nord

Hi Ken...

Back again... don't format the SD card... leave as is in S9.
Card must be in machine to write Detailed and Hi Rez files.
Take card out once per day to DL data to ResCan
Try not to sleep over the 1200 noon time period ( so that the machine has to write over 2 sessions when that happens)
Each session lasts 24 hours from 12 to 12 noon
Most of us have found that multiple mask times (sleeps & naps) may lead to some skewing... its one theory

This is good standard practice:
• No locking of the SD card. This seems useless since the data is a non-proprietary format.
• No powering down unless I have a good reason.
• No three-second power-button power-downs.
• Hit the power button to start a mask event.
• Hit the power button to stop a mask event.
• Wait a couple minutes before removing the card - bathroom break, breakfast, whatever.
• Remove the card.
• Stick it in the SD card reader.
• Copy the Folder "201004xx" to your desktop and copy the contents of SD to folder
• Open ResScan once per day in the am.
• Wait for the quick start.
• Download the data.
• Discard duplicate data.
• Read detailed graphs.
• Save data.
• Close ResScan 3.10.
• Eject SD card.
• Remove card.
• Put card back in the S9.
• Repeat next morning.

When viewing data in ResScan... there is many things to look for that may skew.
Please come back after first day and ask questions as to what you're looking at/ for.

Thanks
Nord

Nord wrote:This is good standard practice:

Its just your personal desired practice, not any standard and by no means established that it is necessarily better or worse than other ways of using a S9

Cheers,

Bill

billbolton wrote:

Nord wrote:This is good standard practice:

Its just your personal desired practice, not any standard and by no means established that it is necessarily better or worse than other ways of using a S9

I'm sure each of us will sort out what's best for us. For example I won't normally have time to fiddle with
data cards every single day, a week at a time is the best I can do and only when I'm having trouble of
some sort.

Having said that, though, when trying to pin down a problem it's useful for as many people as are willing to
adhere to exactly the same procedures, minimizing the variables that could be affecting the experiment. So
for the time being I'll follow the procedures Nord listed (well almost, I don't store stuff to desktop; my "good
standard practice" leaves the desktop clean. ).

Did something happen to some of the postings on this thread?

Last night I recall my browser saying there were 9 pages of replies on this thread. I myself posted a reply at around midnight that is now gone.

Summary of my posting: While exploring my new S9 I accidentally turned it on for a few seconds, so my data card wasn't 100% virgin when I took it out to analyze it.

I looked at the formatting of the card. It's a no-code MBR (implying it wasn't a Windows box the formatted it), one partition, partition type 0xB (W95 FAT32), FAT32 formatted, long filename support, no volume label, format identifier "MSWIN4.1" (which in theory means it was formatted on an actual Windows box, as opposed to say OS/2 or Linux). Curiously my analysis software said the FAT tables did not match. I didn't have a real disk editor handy so I couldn't tell for sure, but a hex dump seems to show the first FAT table has a handful of short (single-cluster) files, but the second FAT table shows a few files that are multiple-cluster near the end of the partition. I don't know what's up with that, but I recall a long time ago putting a file in certain sectors was used as a copy protection mechanism (I need to review the thread on how to reload data onto a card to see if that's a possibility here).

Anyway, those having trouble might want to check how their card is formatted. Sometimes Windows formats a card FAT16; I'm not clear on what conditions it does so but I've had trouble with embedded systems in that area before.

billbolton wrote:

Nord wrote:This is good standard practice:

Its just your personal desired practice, not any standard and by no means established that it is necessarily better or worse than other ways of using a S9

Cheers,

Bill

Perhaps Bill you would enlighten us with your "good" standard practice is...

Or perhaps you could tell us what is "necessarily better or worse ways of using an S9"...

Cheers

kennethryan wrote:Did something happen to some of the postings on this thread?

Last night I recall my browser saying there were 9 pages of replies on this thread. I myself posted a reply at around midnight that is now gone.

Summary of my posting: While exploring my new S9 I accidentally turned it on for a few seconds, so my data card wasn't 100% virgin when I took it out to analyze it.

I looked at the formatting of the card. It's a no-code MBR (implying it wasn't a Windows box the formatted it), one partition, partition type 0xB (W95 FAT32), FAT32 formatted, long filename support, no volume label, format identifier "MSWIN4.1" (which in theory means it was formatted on an actual Windows box, as opposed to say OS/2 or Linux). Curiously my analysis software said the FAT tables did not match. I didn't have a real disk editor handy so I couldn't tell for sure, but a hex dump seems to show the first FAT table has a handful of short (single-cluster) files, but the second FAT table shows a few files that are multiple-cluster near the end of the partition. I don't know what's up with that, but I recall a long time ago putting a file in certain sectors was used as a copy protection mechanism (I need to review the thread on how to reload data onto a card to see if that's a possibility here).

Anyway, those having trouble might want to check how their card is formatted. Sometimes Windows formats a card FAT16; I'm not clear on what conditions it does so but I've had trouble with embedded systems in that area before.

Hi Ken

We're still learning the differences that the S9 expects. Many have used the formatting done at the factory or some have let the S9 format the SD when it had been accidentily erased. ( I haven't done that - I just use Win XP Pro through VMware... as Win 32)
I don't know if any/ many are using Win 16 as they have generally subbed larger cards.

Every time you insert a fresh card in the S9... it writes 5 different files including a blank folder "Datalog" that will contain all Detailed and Hi Rez data. We are just exploring the differences/ uses for these files as a source of minor problems in viewing data... There is a progressive SKEW in data that starts at 2 sec and works itself up to perhaps 15 sec whereupon it may/ may not lose some breath by breath viewing. It does not appear to (we think) skew any Apnea Events or lose those data.

Right now we're exploring several avenues...

1. newer machines may not skew because of hardware changes... the firmware remains constant so far. We are collecting serial numbers of those that do/ don't skew (still too soon for you yet)

2. alterego61 is also examining skewed files through .edf browser to attempt a correlation to what's happened.

3. some of us are trying subtle changes in "best practices" to isolate problem areas... myself, yourself, DreamDiver, Dave21 and a couple of others. Not too scientific, more of a hunt and peck method.

BTW: there are several threads on the same subject ( S9 Skews) that are, maybe minor, but nagging... I'll bring some others to the top page... its a bit unwieldy but its what we got.

Thanks
Nord

kennethryan wrote:Did something happen to some of the postings on this thread?

Last night I recall my browser saying there were 9 pages of replies on this thread. I myself posted a reply at around midnight that is now gone.

Summary of my posting: While exploring my new S9 I accidentally turned it on for a few seconds, so my data card wasn't 100% virgin when I took it out to analyze it.

Hi, Ken. As Nord mentioned, there are several ongoing threads regarding the S9 data skew. Very confusing, I know! I'm trying to follow them all myself.

The post that you're referring to is in another thread, here: viewtopic.php?f=1&t=50578&p=472350#p472350. I just wanted you to know that it's still there, so you didn't think you were going nuts!

DreamOn wrote:

kennethryan wrote:Did something happen to some of the postings on this thread?

Last night I recall my browser saying there were 9 pages of replies on this thread. I myself posted a reply at around midnight that is now gone.

Summary of my posting: While exploring my new S9 I accidentally turned it on for a few seconds, so my data card wasn't 100% virgin when I took it out to analyze it.

Hi, Ken. As Nord mentioned, there are several ongoing threads regarding the S9 data skew. Very confusing, I know! I'm trying to follow them all myself.

The post that you're referring to is in another thread, here: viewtopic.php?f=1&t=50578&p=472350#p472350. I just wanted you to know that it's still there, so you didn't think you were going nuts!

Thank you, DreamOn, I didn't realize I jumped threads! Nice to know I'm not crazy, only sleepy...

kennethryan wrote:Thank you, DreamOn, I didn't realize I jumped threads! Nice to know I'm not crazy, only sleepy...

Glad to help. The only reason I knew is because I had just read your post there right before coming to this thread. I'm a thread-jumper too!