Skip to content

month must be in 1..12? #1

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.

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
stall7 opened this issue Jul 27, 2017 · 3 comments
Open

month must be in 1..12? #1

stall7 opened this issue Jul 27, 2017 · 3 comments

Comments

@stall7
Copy link

stall7 commented Jul 27, 2017

>>> rtc.read_datetime()
Traceback (most recent call last):
File "", line 1, in
File "/usr/local/lib/python3.4/dist-packages/pyRPiRTC-0.0.2-py3.4.egg/pyRPiRTC.py", line 151, in read_datetime
ValueError: month must be in 1..12

what's problem in thie error?

@sqasm
Copy link

sqasm commented Mar 25, 2018

same here...
Traceback (most recent call last):
File "", line 1, in
File "/usr/local/lib/python3.4/dist-packages/pyRPiRTC-0.0.2-py3.4.egg/pyRPiRTC.py", line 151, in read_datetime
ValueError: month must be in 1..12

@sourceperl
Copy link
Owner

Hi,

I have the same issue when i launch "ds1302_get_utc" without RTC clock connect to Pi.

It's probably a wiring issue or a problem with the RTC chip.

I will try to reproduce this bug with a Pi3 and another ds1302.

Have a nice day.

@sourceperl
Copy link
Owner

I check with a new Pi 3 B+ and 2 ds1302, all seem ok.

I add an explicit error message instead of the default Python ValueError except in commit 1972cf8.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants