ALL CLEAR about the urgent warning

Lizistired wrote:I'll just try to remember NOT to change the time in the fall.

OK, I'm not ready to let this evaporate completely forever. Sometime between now and next fall I will do some experimenting and figure out what works for setting time back. I'll post before the time change in November.

McSleepy wrote:Of course, progress is good and introducing automatic DST is nice, but trying to do the simplest thing shouldn't bring about such mayhem.

An S9 is not a PC, or PVR, or some other piece of consumer electronics..... its a therapeutic device

It doesn't know anything about which time zone it is in, let alone which set of arbitrary/arcane rules may apply to periodic offsets from "normal" time.

McSleepy wrote:As a software engineer in the area of high-tech data acquisition and control, I must say there is no excuse for the ResMed engineers to make such childish mistakes with the S9 and ResMed.

There is no excuse for making such silly statements based on nothing much at all.

billbolton wrote:It doesn't know anything about which time zone it is in, let alone which set of arbitrary/arcane rules make apply to periodic offsets from "normal" time.

But it could! The 7/24 hr programmable timer in the 120 volt house wire to my shower heater even resets its time according to DST! But I do have to tell it what time zone its in.

I wouldn't worry about it. It's really just a blip to me already. Maybe in the fall I just won't let it bother me.

idamtnboy wrote:

Lizistired wrote:I'll just try to remember NOT to change the time in the fall.

OK, I'm not ready to let this evaporate completely forever. Sometime between now and next fall I will do some experimenting and figure out what works for setting time back. I'll post before the time change in November.

billbolton wrote: An S9 is not a PC, or PVR, or some other piece of consumer electronics..... its a therapeutic device

It doesn't know anything about which time zone it is in, let alone which set of arbitrary/arcane rules make apply to periodic offsets from "normal" time.
[...]
There is no excuse for making such silly statements based on nothing much at all.

Those ramblings above are so incoherent, I'll just leave them alone. If the machine is unaware of DST, there is even less excuse for this problem. Either way, what matters is the ultimate result, which was gaps in the data and lost records. Either way, given the major scrutiny of medical equipment and software, there is no excuse for allowing such a major problem, especially stemming from such a mundane and predictable cause (like DST).
McSleepy

I have gone too long without good sleep to get up in the middle of the night to reset clocks.
We always wait until the next day to change things.--no lost sleep, no data mess-ups.
No clue it was a good idea to be lazy.

Me too! That's it, If I really want the data intact, I needed to get up at 1am to set the clock forward. I'm guessing that won't work in the fall because it would have to overwrite data when I tried to set it back. And we are still talking about 1 hour in about 1500 hours....

Mine didn't lose data, it set the clock forward for me, thus creating a blank hour and extending my sleep time. It just did it on the wrong day. I think the ResScan programmer's just did it to screw with you!

chunkyfrog wrote:I have gone too long without good sleep to get up in the middle of the night to reset clocks.
We always wait until the next day to change things.--no lost sleep, no data mess-ups.
No clue it was a good idea to be lazy.

Just a quick note - I've been able to recover all of my data. I've also done a rudimentary root cause analysis. I'll post what I've found as soon as I have time to pull the info together.

BernieRay, I'm glad that you were able to recover your data. I would be interested in your analysis of the cause once you've organized the information. Perhaps it'll help others facing the same problem in the future.

I'm a bit confused as to why this problem is so urgent. Is one hour's worth of data on a single night really that important?

As a software professional, I agree that ResMed's software is has more problems than it should. And I am also curious as to what is causing the problem.

But I really can't see how the loss of one hour of data will significantly affect anyone's therapy. If something occurred during that hour that did not happen previously and and does not reoccur, is it really worth worrying about?

And now I am going to duck.

jdm2857 wrote: And now I am going to duck.

I will duck with you. I just keep thinking that remember this software was designed for the clinics and doctors offices and they could care less about a missing hour and probably not missing days unless it affected compliance requirements and payment.
They never really expected us to be dissecting things in this fashion.

For the ducks - this isn't about the 1 hour loss. It's about losing all of my summary and stats data, which is fairly well documented in this thread. If left un-resolved, it would impact my treatment and possibly other folks down the road.

BernieRay wrote:For the ducks - this isn't about the 1 hour loss. It's about losing all of my summary and stats data, which is fairly well documented in this thread. If left un-resolved, it would impact my treatment and possibly other folks down the road.

I hear you. Your situation is unique and I fully understand. My comment was for those in general who only saw the blank one hour line and did not have the overall data loss that you experienced.

I forgot that it did start off primarily about the 1 hour break.

Now I'll be the duck!

Ditto on Pugsy's last post.