[Coco] Clock "Timing".
Dave Philipsen
dave at davebiz.com
Tue Apr 4 15:07:26 EDT 2017
Art brought up the use of the TIMER function which I had completely
forgotten. Sounds like your best bet. You may still have to test it
and trim it to increase accuracy.
Dave
On 4/4/2017 2:03 PM, John Lochey via Coco wrote:
> Hi Dave,
> Whew! I hope to go in that direction, but for now Machine code is on the back burner, but that does seem like the way to get super accurate.
> Thanks,
>
> Johnny
>
>
> From: Dave Philipsen <dave at davebiz.com>
> To: CoCoList for Color Computer Enthusiasts <coco at maltedmedia.com>
> Sent: Tuesday, April 4, 2017 2:59 PM
> Subject: Re: [Coco] Clock "Timing".
>
> You would probably get a more accurate timebase by using an interrupt
> routine which would be derived from timing based upon the crystal
> frequency. Even with that you would probably want a way to trim it for
> accuracy. It can all be done from an Extended BASIC command set however
> a knowledge of machine code would be essential.
>
> Dave
>
>
> On 4/4/2017 1:50 PM, John Lochey via Coco wrote:
>> Hi all,
>> I'm making a binary clock for the CoCo2 via emulation (XRoar at the moment).
>>
>> As far as I know (from reading "Getting Started...Color Basic"), the way to time an actual second of time on a Color Computer 2 is to use a For...Next loop that corresponds as closely to an "actual" second as possible.
>> Is there a better way using just the Extended BASIC command set?
>> Also, provided that the emulator has the same settings as the original CoCo2, will the same timing loop work via emulation and hardware?
>>
>> Or am I a dreamer! ;)
>>
>> Johnny
>>
>>
>
More information about the Coco
mailing list