Skip to content

explain why no setCentury() method is implemented #110

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
IowaDave wants to merge 1 commit into
base: master
Choose a base branch
from
Open

explain why no setCentury() method is implemented #110

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 5 additions & 0 deletions Documentation/Time-Set.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -31,6 +31,11 @@ It is the code developer's sole responsibility to upload only "sensible" values

The Library does not check the values to be set. The compiler only checks that the value is of the right size, i.e., 8 bits. A large value such as 117 will fit in 8 bits and would be passed along by the Library. Yet it makes no sense for any part of a time or a date. Code with care!

**No ```setCentury()``` Function**

The Library does not provide a method for writing a value to the Century bit in the DS3231 hardware, because that bit is only an informational output of the DS3231, and not an input to any of its internal time and date computations. In other words, for practical purposes, the Century bit should be viewed as read-only.

## Examples of Using the Functions

<h3 id="setClockMode">void setClockMode(bool h12)</h3>

Expand Down