The suggestion to introduce a method to manage the deltaT is interesting. I will work on it. You’re right when you say that floats should be used only in particular situations becuase their implementation heavily affects the MCU’s performances.

BTW I studied LeOS too and I may go for that one. I’m just not sure 100% whether it’s better to use leOS, looper, rtduinos, chibios or similar… And I’m a bit afraid of clashes between leOS and swRTC (and panstamp stack) regarding use of timers and interrupts

I created one panstamp register (array of 7 bytes) for the clock. Since registers are usually BE, I chose to order them as “century, year, month, day,hour, minute, second”. Then a sette and getter method allows me to query and set the clock using teh SWAP stack wirelessly. Works fine. Note that since panstamps use the internal 8MHz clock, there is a serious drift of clock. My first tested panstamp had a deviation of 13 minutes/day, close to the “840.0″ seconds max.

Also note that I will have to/you should add a “getDeltaT” method so that it is possible to query the status of deltaT variable. Also a setDeltaT accepting an integer should be interesting, I try to avoid floats as much as I can on Arduino.

I also added an “automatic deltaT setting”, that tunes deltaT each time you manually set the clock. But after a while I commented it out because I wasn’t convinced of its effectiveness.