[Coco] DS1216

K. Pruitt pruittk at roadrunner.com
Thu Sep 24 05:36:54 EDT 2015


Turns out that was easier than I thought. It's done. It retains full 
functionality, plus you can just pass it the date and time now as parameter 
as well. Tested it and it works great. 6 lines of code and I think 4 labels.


----- Original Message ----- 
From: "K. Pruitt" <pruittk at roadrunner.com>
To: "CoCoList for Color Computer Enthusiasts" <coco at maltedmedia.com>
Sent: Thursday, September 24, 2015 1:59 AM
Subject: Re: [Coco] DS1216


> The source code from RTSI  was for different clock chips (RGB and Disto).
>
> I couldn't disassemble the original setclk that you and I are both using. 
> but Bill Pierce did it and passed it along to me with notes included. 
> Thanks Bill.
>
> I added a couple lines of code to make the program look at the parameter 
> directly.
>
> So...
>
> setclk 15/09/24 02:00:00
>
> is now a valid way to set the time on the clock chip.
>
> I hadn't though of it, but Bill mentioned in his notes in the source code 
> that implementing the acceptance of the date and time as a parameter might 
> be better done as an option..
>
> It would certainly preserve the original integrity and intent of the 
> software. It would just add a much needed option. So while a quick patch 
> does make it do what you want, I think it's better to put some effort in 
> to this and retain the ability to set the time from the keyboard while 
> adding the ability to accept the date and time as a parameter.
>
>
> ----- Original Message ----- 
> From: "George Ramsower" <georgera at gvtc.com>
> To: <coco at maltedmedia.com>
> Sent: Wednesday, September 23, 2015 11:34 PM
> Subject: Re: [Coco] DS1216
>
>
>>  When I'm doing what requires the system clock to be ON TIME, it is 
>> important that it be on time. Normally, the accuracy of the system clock 
>> in not very important, as long as it's pretty much on the same date.
>>  But... when the clock is required to be ON TIME, then being able to keep 
>> that smart watch on time is important.
>>  It would be very simple to set that clock on a scheduled basis and I'm 
>> looking forward to this improvement to the "setclk". As most of us 
>> already know, a clock that loses (for example) one second every day, then 
>> it will lose about 30 seconds every month. When I need more accurate time 
>> keeping, being able to reset that smart watch once a day to advance it by 
>> one second, once a day with software, is important unless I want to do 
>> this manually, on a strict schedule. This can easily be done several time 
>> a day, if necessary, with some match to calculate the timing for 
>> resetting the smart watch.
>>  That DS1216 can also break down the time to milliseconds, providing the 
>> software is written to do this.
>>  There's something to ponder!
>>
>>  I like "easy"!! After all, aren't computers  supposed to make life 
>> easier? Let them do the work!
>>  I'm looking forward to an improved "setclk" which will be easy to adjust 
>> and keep on time.
>>
>>  Of course, this will only be effective while the computer is on. 
>> Naturally, if it is off then the smartwatch will do it's thing until 
>> acted upon.
>>
>> George R.
>>
>
> <snip>
>
> -- 



More information about the Coco mailing list