next topic »

[Reply #90 on:]

Uh, kinda make it hard to test

Code:

TimeAlarmsTest.cpp: In function 'void onAlarm()':
TimeAlarmsTest:37: error: 'class TimeAlarmsClass' has no member named 'getTriggeredAlarmId'
TimeAlarmsTest:51: error: 'class TimeAlarmsClass' has no member named 'free'
TimeAlarmsTest.cpp: In function 'void loop()':
TimeAlarmsTest:137: error: 'class TimeAlarmsClass' has no member named 'getNextTrigger'

[Reply #91 on:]

Oh, nevermind, found it.

[Reply #92 on:]

same issue, had to find the beta directory first :-)

missing
void TimeAlarmsClass::write(AlarmID_t ID, time_t value,dtAlarmPeriod_t period)
that I added immediatly,

The new isallocated function make code easier to read, but for the sake of my own knowledge, why a function instead of a macro ?


testing tonight and tommorow evening will send you result then.

regards

[Reply #93 on:]

It is leaking,

I have to see if it is your base code or my modification (new write function)

regards

-------------------------------
Updated:
the dtNBR_ALARMS was back to 6 (from the 8 I am currently using) and that triggered some memory leak, it was there with the previous version and I am not at all sure It come from your sketch, it is probably my code So no issue there, I restart my tests this morning without a memory leak.

[Reply #94 on:]

perfectly working on my side :-)

what about you ?

[Reply #95 on:]

I've had it going in a random fashion from a couple of years back to 5 years forward, starting over when it goes past the upper.  Both timers and alarms have been working fine.  I also ran it once to failure in the future and no problem came up.

I suggest publishing it and let other folk play with it as much as they want to.

[Reply #96 on:]

Thanks for the feedback.

I will create a new zip with the directories in the expected places so its less confusing to install and publish tomorrow for wider testing

[Reply #97 on:]

Here is a link to the beta Library that fixes the weekly alarm problem. The only change from the code I posted above is the directory structure now matches the old library so the contents can be directly copied into the libraries folder.  I also added this text in a release note:

Changes made July 5 2011:

This is a beta test version of the libraries that provides a fix for
recurring weekly alarms.

TheTime library is unchanged except for fixes to a macro in Time.h that
converts the number of days to elapsed seconds and the macros that are used
to calculate weekly alarms.

The functionality of the TimeAlarms library has changed slightly in order to
make the library easier to maintain and enhance.

In short, if your application used an Alarm method to create weekly
alarms then you should change your sketch  to use the methods that take the
explicit DayOfWeek parameter. Only the Alarm methods are affected,
Timer methods are as before.

Here are the details:
The previous version could set weekly alarms by calling the AlarmOnce method
with a value greater than one day to indicate the day and time of the weekly
alarm. This has changed and explicit calls to set weekly alarms must be used
when setting weekly alarms. If you were setting weekly alarms by calling either
   Alarm.alarmRepeat(weeklyValue,  AlarmFunction);
then you need to change this to:
  arm.alarmRepeat(DayOfWeek, Hour, Minute, Second,  AlarmFunction);
 
Also the clock must be set to a time on or after Jan1 1971 when using the Alarm methods.
Timer methods are unchanged and will function even if the clock has not been set

Lets see how this goes for a day or so and then I will circulate this more widely

Michael

p.s. viknet, note that I did not add in the enhanced write method. As explained in my earlier post, I think the library is better suited for its intended purpose without it so will need to add into your version.

[Reply #98 on:]

I posted info on the update in a new thread so people would not need to read through the seven pages of background to get to the information on the beta release.

Michael

[Reply #99 on:]

First, i am noob in arduino and just tinkering arduino.

i make a clock using :
1. Arduino UNO
2. RTC DS1307
3. LCD 16*2

this is how it is work:
==> Visual Basic set RTC time
==> Visual Basic set the Alarm and Save to Arduino EEPROM

and this is the problem that I got:
I have an interval mode alarm, this mode have value to start the alarm, end the alarm, and interval value.
when i compare RTC time and EEPROM value and start the alarm, alarm time is late.
example:
I set the alarm :
- start time : 13.00 pm
- end time : 14.00 pm
- interval :  5 minute

the alarm should 'sound' at 13.05.00 pm (HH.MM.SS), but i get the alarm sound at 13.05.30 and will continue till 14.05.30 pm.

the code is below this post:

sorry for my english

[Reply #100 on:]

the code:

deleted
junk detected

[Reply #101 on:]

copet_pitik, this thread was reporting a specific issue with the Library so this is not the best place for discussions on help using the library.

I have created a thread for that purpose here and I suggest the we move this discussion there. Can you post a shorter version of your sketch that illustrates the problem so its easer to see if your problem is with Alarms or delays in your code to write to eeprom. It would be easier to help if you can translate comments into english so I can understand the purpose of each of you functions. A summary of the purpose of your sketch and overview of the logic you used to implement it would also help in understanding what your sketch is doing.

Michael

[Reply #102 on:]

copet_pitik, this thread was reporting a specific issue with the Library so this is not the best place for discussions on help using the library.

I have created a thread for that purpose here and I suggest the we move this discussion there. Can you post a shorter version of your sketch that illustrates the problem so its easer to see if your problem is with Alarms or delays in your code to write to eeprom.

Michael

wokey