ChronoDot (2.0) Project done!
3 Attachment(s)
Hi! That's started with a pb's form factor for the battery :scratch: The ChronoDot ordered (v2.0) needed an little small battery than the (v2.1)'s version, as in SARPi's mini-project page! Got an idea: (as i've a tons of CR2032 cells here :D), just ordered a socket for a battery cell and i'm happy with that choice!
Happy New Year guys! :party: ps: you don't need to put an hwclock -s in rc.local, all is done in rc.S. |
Quote:
Happy New Year. :D :party: I changed the CR1632 battery in my ChronoDot v2.1 about 11 months ago, which had lasted approx. 8 years from new. I consider this to be very good battery lifespan. From looking at your images, what you've got is a "ChronoDor" which is a Chinese clone of the ChronoDot. Although I've never used the ChronoDor, it looks very similar to the ChronoDot and features a DS3231SN controller. I believe the ChronoDor uses a CR1220 battery and ChronoDot uses a CR1632 battery, which leads me to assume that the battery life on the ChronoDor may be somewhat similar to that on the ChronoPi. I doubt for most users the quality and accuracy of the ChronoDor will be of any concern. The important thing is that it's a RTC and does the job. :) A good idea for a battery holder is a CR2032 breakout board which is also available with an on/off switch. Quote:
Code:
Manual page hwclock(8) line 224 |
Thanks for replying Exaga :thumbsup: I'm surprised, didn't know about the existence of a chinese version.. And had a pb with a soldering point! Will check accuracy in time. Talking about hwclock, for you i should use hwclock -s in my rc.local? I forgot to say that i'm using the "dto" version's project. Good night ;)
|
Quote:
It's up to you what you do with rc.local or any other file(s), if anything. It's always prudent to do some testing and verify that the RTC is working as expected on (re)boot and then no further 'hwclock -s' commands are necessary. The ChronoDot RTC guide you mentioned to is 9 years old, was written for Slackware ARM 13.37/14.0, and still refers to a "disabling device-tree method", which I think is no longer used these days. So, the information in the guide is in need of a general overhaul. Basically, with the ChronoDot (or any other DS3231 based I2C RTC) all that's required is to make sure it's wired up correctly and add or uncomment 'dtoverlay=i2c-rtc,ds3231' in the /boot/config.txt file, then reboot the system. Obviously users will need to consider their own setups and configurations in order to suit their requirements. |
Ok Doc Exaga ;)
hs: as you seen in my pics, i got the RBPi mouse but this one is not moving the cursor as expected under X.Org.. The move is not very reactive! I don't have this "pb" with a basic usb mouse (w/ my x86/x86_64 configs). Is the RBPi mouse a special device? Hope you understand :D |
Quote:
|
Quote:
|
Ok mralk3 :thumbsup:
|
All times are GMT -5. The time now is 04:06 AM. |