CONFIG CLOCK

Top  Previous  Next

Action

Configures the timer to be used for the TIME$ and DATE$ variables.

 

 

Syntax

CONFIG CLOCK = soft | USER [, GOSUB = SECTIC]

 

 

Remarks

Soft

Use SOFT for using the software based clock routines. Use USER to write/use your own code in combination with an I2C clock chip for example.

Sectic

This option allows to jump to a user routine with the label sectic.

 

Since the interrupt occurs every second you may handle various tasks in the sectic label. It is important that you use the name SECTIC and that you return with a RETURN statement from this label.

 

The usage of the optional SECTIC routine will use 30 bytes of the hardware stack. This option only works with the SOFT clock mode. It does not work in USER mode.

 

 

When you use the CONFIG CLOCK directive the compiler will DIM the following variables automatic : _sec , _min , _hour, _day , _month , _year

The variables TIME$ and DATE$ will also be dimensioned. These are special variables since they are treated different. See TIME$ and DATE$.

 

The _sec, _min and other internal variables can be changed by the user too.

But of course changing their values will change the DATE$/TIME$ variables.

 

The compiler also creates an ISR that gets updates once a second. This works only for the 8535, M163 and M103 and M603, or other AVR chips that have a timer that can work in asynchrony mode.

 

For the 90S8535, timer2 is used. It can not be used my the user anymore! This is also true for the other chips async timer.

 

Notice that you need to connect a 32768 Hz crystal in order to use the timer in async mode, the mode that is used for the clock timer.

 

When you choose the USER option, only the internal variables are created. With the USER option you need to write the clock code yourself.

 

See the datetime.bas example that shows how you can use a DS1307 clock chip for the date and time generation.

 

 

Numeric Values to calculate with Date and Time:

 

SecOfDay: (Type LONG) Seconds elapsed since Midnight. 00:00:00 start with 0 to 85399 at 23:59:59.
SysSec: (Type LONG) Seconds elapsed since begin of century (at 2000-01-01!). 00:00:00 at 2000-01-01 start with 0 to 2147483647 (overflow of LONG-Type) at 2068-01-19 03:14:07
DayOfYear: (Type WORD) Days elapsed since first January of the current year.
First January start with 0 to 364 (365 in a leap year)
SysDay: (Type WORD) Days elapsed since begin of century (at 2000-01-01!). 2000-01-01 starts with 0 to 36524 at 2099-12-31
DayOfWeek: (Type Byte) Days elapsed since Monday of current week. Monday start with 0 to Sunday = 6

 

 

With the numeric type calculations with Time and date are possible. Type 1 (discrete Bytes) and 2 (Strings) can be converted to an according numeric value. Than Seconds (at SecOfDay and SysSec) or Days (at DayOfYear, SysDay), can be added or subtracted. The Result can be converted back.

 

 

See also

TIME$ , DATE$ , CONFIG DATE

 

 

 

ASM

The following ASM routines are called from datetime.lib

_soft_clock. This is the ISR that gets called once per second.

 

 

 

Example

'-----------------------------------------------------------------------------------------

'name                     : megaclock.bas

'copyright                : (c) 1995-2005, MCS Electronics

'purpose                  : shows the new TIME$ and DATE$ reserved variables

'micro                    : Mega103

'suited for demo          : yes

'commercial addon needed  : no

'-----------------------------------------------------------------------------------------

 

$regfile = "m103def.dat"                                   ' specify the used micro

$crystal = 4000000                                         ' used crystal frequency

$baud = 19200                                               ' use baud rate

$hwstack = 32                                               ' default use 32 for the hardware stack

$swstack = 10                                               ' default use 10 for the SW stack

$framesize = 40                                             ' default use 40 for the frame space

 

'With the 8535 and timer2 or the Mega103 and TIMER0 you can

'easily implement a clock by attaching a 32768 Hz xtal to the timer

'And of course some BASCOM code

 

'This example is written for the STK300 with M103

Enable Interrupts

 

'[configure LCD]

$lcd = &HC000                                               'address for E and RS

$lcdrs = &H8000                                             'address for only E

Config Lcd = 20 * 4                                         'nice display from bg micro

Config Lcdbus = 4                                           'we run it in bus mode and I hooked up only db4-db7

Config Lcdmode = Bus                                       'tell about the bus mode

 

'[now init the clock]

Config Date = Mdy , Separator = /                         ' ANSI-Format

 

Config Clock = Soft                                         'this is how simple it is

'The above statement will bind in an ISR so you can not use the TIMER anymore!

'For the M103 in this case it means that TIMER0 can not be used by the user anymore

 

'assign the date to the reserved date$

'The format is MM/DD/YY

Date$ = "11/11/00"

 

'assign the time, format in hh:mm:ss military format(24 hours)

'You may not use 1:2:3 !! adding support for this would mean overhead

'But of course you can alter the library routines used

 

Time$ = "02:20:00"

 

'---------------------------------------------------

 

'clear the LCD display

Cls

 

Do

Home                                                     'cursor home

Lcd Date$ ; "  " ; Time$                                 'show the date and time

Loop

 

'The clock routine does use the following internal variables:

'_day , _month, _year , _sec, _hour, _min

'These are all bytes. You can assign or use them directly

_day = 1

'For the _year variable only the year is stored, not the century

End