Resscan 3.14 leak data does NOT match graph data

[mck]

Hello everybody,

For the last few days I have noticed that the on the screen leak data of the S9 does not match the detailed graph data on Resscan 3.14.

For example this morning the S9 screen data indicated a 95% leak of 12 but when I looked at the detailed graph for leaks- it shows that it never went above 5 for the entire night, and I always make sure that I turn the machine on after I have the mask ON. ( I looked at the detailed graph minute by minute)

The summary graph is also wrong it indicates a maximum leak of 24 but again the leak for the entire night never went above 5. Summary graph also shows a 95% leak
of 12 which is what is on the S9 screen but is NOT what the detailed leak graph says.

Has anyone had this problem?
Does the machine need to be calibrated? or is it broken?

[Otter]

Hello everybody,

For the last few days I have noticed that the on the screen leak data of the S9 does not much the detailed graph data on Resscan 3.14.

For example this morning the S9 screen data indicated a 95% leak of 12 but when I looked at the detailed graph for leaks- it shows that it never went above 5 for the entire night, and I always make sure that I turn the machine on after I have the mask ON. ( I looked at the detailed graph minute by minute)

The summary graph is also wrong it indicates a maximum leak of 24 but again the leak for the entire night never went above 5. Summary graph also shows a 95% leak
of 12 which is what is on the S9 screen but is NOT what the detailed leak graph says.

Is the period on the s9's display set to "day"? If not, that would explain the discrepancy. It does not explain the summary graph, but maybe you're eye caught the wrong day there?

[mck]

Thank you Otter for responding, but yes the S9 display is set to DAY- and NO in the Summary I did not look at the wrong day.

[Pugsy]

On the off chance you are a victim of the weird data thing, try unplugging the machine. Then plug it back in forcing a firmware reboot. Then see if the data tomorrow AM seems to match the graphs from tonight. Hurts nothing to try.

[Otter]

I think we're probably both just missing something obvious, but it wouldn't hurt to reboot your machine. Just hold down the power button for three seconds, unplug, wait a little bit, and plug back in. That won't do anything for days already recorded, but if it is a firmware bug, power cycling will probably fix it for days to come.

[mck]

Thank you Otter and Pugsy I just did a reeboot of the machine I hope it works. I will report tomorrow.

[Otter]

Thank you Otter and Pugsy I just did a reeboot of the machine I hope it works. I will report tomorrow.

Please post your result either way. This is quite a puzzle, but I wouldn't be surprised if it happened to someone else eventually too.

[mck]

Thank you Otter and Pugsy I just did a reeboot of the machine I hope it works. I will report tomorrow.

Please post your result either way. This is quite a puzzle, but I wouldn't be surprised if it happened to someone else eventually too.

The reboot worked!

It looks like this is an ongoing issue with Resmed machines- in the past I had rebooted a few times for other data issues (AHI, Leak, time running not changing from the previous day reading).

It looks like is a good idea to reboot every day just to be sure.

[Pugsy]

The reboot worked!

It looks like this is an ongoing issue with Resmed machines- in the past I had rebooted a few times for other data issues (AHI, Leak, time running not changing from the previous day reading).

It looks like is a good idea to reboot every day just to be sure.

Glad that mystery is cleared up. Though your comment about having to reboot for other data issues is troubling. I don't think people should have to reboot daily. It would tend to make me suspect all data to have a machine that acts squirrelly often. Rare occasion I could live with. There are ResMed machines that never need the reboot. That is the way they are supposed to act.

[Otter]

I'm glad that's all it took. I used to reboot every three or four days. Now that I'm using Sleepyhead, which they say isn't affected by Resmed's skew bug (I really need to verify that for myself one of these days.), I'll go up to a week. This seems to keep the bugs at bay.

It's really too bad that Resmed isn't interested in debugging their firmware.

[mck]

The reboot worked!

It looks like this is an ongoing issue with Resmed machines- in the past I had rebooted a few times for other data issues (AHI, Leak, time running not changing from the previous day reading).

It looks like is a good idea to reboot every day just to be sure.

Glad that mystery is cleared up. Though your comment about having to reboot for other data issues is troubling. I don't think people should have to reboot daily. It would tend to make me suspect all data to have a machine that acts squirrelly often. Rare occasion I could live with. There are ResMed machines that never need the reboot. That is the way they are supposed to act.

Pugsy, I think you are right- I should not have to reboot every day, from now on I will just watch and see how it goes, if it starts happening often I guess I will have to talk to DME.