Cumulus Support

Not sure what's happening with my Twitter set up.

For some reason I'll start my twitter upload on the hour and I've got the code to show the date and time incorporated into the tweet.

Yet for some reason the time is slipping. It started off as a mere minute so instead of 0700 the tweet was sending at 0659 but for some reason the time slip has been greater, up to 20 minutes at a time.

The PC clock is correct and the Oregon WMR88 is also correct yet this is still happening.

Any ideas of what maybe causing this please

Thanks!
Phil

What interval have you specified - 60, presumably? What's your Twitter ID?

Delete any existing debug.log file, then turn on debug log and leave it until a couple of Twitter updates have happened. Then turn off the debug log, zip up the debug.log file and ttach it here. Please also zip up the diags folder and attach it. A screen shot of your internet config screen may also be useful.

I guessed at what your Twitter ID might be. You've set an interval of 120 minutes, so it's not synchronised to the clock. I've gone back a couple of days, and I can't find any updates that aren't either on the hour or at 59 minutes past the hour. Cumulus can't synchronise the updates exactly if the interval is isn't a factor of 60.

Thanks! Will do! I've set my updates for every 120 mins as 60 was annoying my followers. My Twitter id is ThurrockWeather

So if I set it to 60 it defaults to the hour?
Even with the 120 set up I was starting it at dead on the hour and was working fine then started to slip. I'll change to an hour and see what happens

Yes, any factor of 60 will be synchronised to the minutes on the PC clock (and 60=on the hour). Any other value is subject to the vagaries of Windows timers and the exact interval will be affected by what Cumulus is doing, and may well slip slightly over time.

Excellent! Thanks for your help! I've reset to 60