Skip to content
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

PMS5003_logger.py on pi 2B error or not? #48

Open
ryantanaka opened this issue Jun 12, 2018 · 4 comments
Open

PMS5003_logger.py on pi 2B error or not? #48

ryantanaka opened this issue Jun 12, 2018 · 4 comments

Comments

@ryantanaka
Copy link

Looks like there may be an issue with the sensor.

Current Crontab Setup:
* * * * * /home/jason/sensors/raspberry_pi/pms5003/pms5003_check.sh

So it should have been running, however the pi_pms5003_log.csv wasn't being updated.

Running the PMS5003_logger.py by itself threw the following exception:

Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/serial/serialposix.py", line 490, in read
    'device reports readiness to read but returned no data '
serial.serialutil.SerialException: device reports readiness to read but returned no data (device disconnected or multiple access on port?)

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "PMS5003_logger.py", line 99, in <module>
    main()
  File "PMS5003_logger.py", line 64, in main
    s = ser.read(FRAME_LENGTH)
  File "/usr/lib/python3/dist-packages/serial/serialposix.py", line 497, in read
    raise SerialException('read failed: {}'.format(e))
serial.serialutil.SerialException: read failed: device reports readiness to read but returned no data (device disconnected or multiple access on port?)

For some reason, this could be because I tried to run one instance of the program manually while the crontab was trying to run (maybe this relates to the msg: multiple access on port?. Oddly, the program is now running and updating the csv so I'm not sure what was going on..

@jygh98
Copy link
Member

jygh98 commented Aug 21, 2018

@ryantanaka I will follow up on you either on Thursday or Friday this week about this.

@carlosparadis
Copy link
Member

Devote as little as possible time on this one, unless you think the data is compromised, in which it relates to issue #41 and becomes high priority.

@carlosparadis
Copy link
Member

This is @ryantanaka talking from @my computer. From August 28th until Sept 7, there was no data for some reason even though the crontab was running the program. We killed the process started by the crontab and waited for the program to run. Now there is data from Sept 7..

@carlosparadis
Copy link
Member

Jason graduated, I am transferring this issue to myself.

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

No branches or pull requests

3 participants