Hi again, It seems there's something wrong in the sample, when setting alarmtime:
var byte*3 alarmtime = 0x003007 -- actual alarmtime, init: 07:30:00 rtc_set_alarm_hhmmss_bcd(alarmtime) But: -- input: hour-minute-second in bcd format procedure rtc_set_alarm_hhmmss_bcd(byte*3 in hhmmss_bcd) is So, to set alarm @ 7h30 and 0 seconds, I would have: var byte*3 alarmtime = 0x073000 rtc_set_alarm_hhmmss_bcd(alarmtime) In doc, you say: -- PICs use little endian notation (store multi-byte variables with -- low order byte first)! So when you want to set the date to 10:07:28 -- you must specify: -- rtc_set_yymmdd(0x280710) -- 'reversed' sequence! Then why not naming the procedure rtc_set_ddmmyy(0x280710) (btw, you're setting time -- 10:07:28 --, not date in this example -- calling rtc_set_yymmdd() --) Also, you should take another date than 10/01/01 in sample, because depending on the country habits (locale), it can be read: - January 1st 2001 - October 1st 2001 - and even January 1st 2010 A little bit confusing, isn't it ? April 23rd 2011 is a good one, you can't get confused: 04/23/11 or 23/04/11. Cheers, Seb 2011/4/5 Sebastien Lelong <[email protected]> > Hi Rob, > > > 2011/4/5 Rob Hamerling <[email protected]> > > OK with me. But I would like to make a distinction between this builtin >> module and external or software RTCs. So I think I'll rename it to >> 18f26j11_rtcc_kbd_lcd.jal >> > > Then you should add "hardware" somewhere, because currently you can't know > if it's builtin or not (rtcc: real time clock/calendar) > > Cheers, > Seb > -- You received this message because you are subscribed to the Google Groups "jallib" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/jallib?hl=en.
