Roastlogger assistance

[Pretzal]

Thanks for the advice on how to fix it. I’ll have a look and see how I go....might be a few hours googling first lol

[Andy]

Well I would never have guessed that. Obvious explanation once you mentioned it.
However his time must have been out by quite a bit. A time correction should not be that much (excepting daylight savings) unless his PC CMOS battery is low and it's losing time.

I've always wondered why cutting-edge electronics in a $1500 PC can't keep time as well as a $2 watch from the market (get the same problem in my van too)


The difference was under 2 minutes which can happen pretty easily if the PC isn't online often enough for Windows to "go check". The error can accumulate over a much longer period. By default Windows only checks the time once a week (every 604800 seconds) but I think Windows 10 does it on startup (which makes more sense). You can fix it with a script or something like "D4 time sync" or maybe just go into your clock setting at midnight, manually update and then it will only happen at midnight once a week

You can fix your graph in the CSV file too as long as you are careful that Excel doesn't mess it up when you save it. You will find the time column and the step, just add the step value to the rest of the column and your graph should appear like it should.

[Pretzal]

Thanks for the replies everyone. The simplest explanation is usually the most correct. The beans were the Ethiopian Kochere sourced from a local roaster. I got very lucky with this roast - it was a good one.

[solace]

Well I would never have guessed that. Obvious explanation once you mentioned it.
However his time must have been out by quite a bit. A time correction should not be that much (excepting daylight savings) unless his PC CMOS battery is low and it's losing time.

Internet time would mean the time is being supplied from a dedicated time server. Likely the route to whatever server that was changed and the ‘new’ time server was presenting a different time or the time manager resolved back to the PC’s local time (which appears to be way behind the time server).


What were the beans Pretzal?

[speleomike]

Well I would never have guessed that. Obvious explanation once you mentioned it.
However his time must have been out by quite a bit. A time correction should not be that much (excepting daylight savings) unless his PC CMOS battery is low and it's losing time.

[Andy]

Windows changed your time in the middle of the roast!
Just bad timing.

If you turn off "Windows Internet Time" in your clock it won't happen.

[Pretzal]

Just wondering if anyone can diagnose what happened with the logging on this profile? It seems to have skewed backwards at about the 9 minute mark then continued on from there? It was a ripper roast but would be nice if I could fix the profile. Sadly can't get anymore of the beans though...