-
Notifications
You must be signed in to change notification settings - Fork 24
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
Help about new issue raised after latest update #20
Comments
Hi Carlo,
|
Hi Phil, thank you for your quick answer. I can’t powercycle it now as it’s in the country. Everything had been working fine for so many months that I can’t imagine it tied with the actual wiring (2 m). The problem raised the last time I physically worked with the RasPi to change the Davis weather receiver. Can you confirm that a problem due to applying updates to the RasPi can be totally excluded? Anyway updating/upgrading the Pi should not have upgraded your library (or has it?). As I've seen you made some update (in case I get confirmation my actual version has not updated) what is the best way to update your library to the latest? pip install RPi_AS3935 on a previous installation will be enough? Should I change something in my script due to your updates? Sorry anyway for the very noobish questions and thanks once more for your library! Carlo Da: Phil Fenstermacher [mailto:notifications@github.com] Hi Carlo,
— |
Since the issue popped up after physically messing with things, and that i2cdetect is showing intermittent failures, I suspect the problem is with either the wiring or connections. The maximum wire length is dependent on wire capacitance. At 2m it's certainly something I would look in to though. I can't rule out an update to the Pi breaking things, though I think it's very unlikely given the intermittent behavior. The error that you're getting is at a lower level than the library, and I haven't changed any of the underlying libraries or anything else that should break backwards compatibility. If you'd like to test with an older version you can install it using |
Thanks again for your precious assistance, this saved me much troubles!
I tend to exclude i2c issue as it has worked for a long time and now the CO2 sensor (which is also i2c) is currently reporting OK. I’ll powercycle it, just in case substitute the sensor, and I’ll let you know. Carlo Da: Phil Fenstermacher [mailto:notifications@github.com] Since the issue popped up after physically messing with things, and that i2cdetect is showing intermittent failures, I suspect the problem is with either the wiring or connections. The maximum wire length is dependent on wire capacitance. At 2m it's certainly something I would look in to though. I can't rule out an update to the Pi breaking things, though I think it's very unlikely given the intermittent behavior. The error that you're getting is at a lower level than the library, and I haven't changed any of the underlying libraries or anything else that should break backwards compatibility. If you'd like to test with an older version you can install it using pip install RPi-AS3935==0.1.0 (valid versions are 0.0.2-0.0.9, 0.1.0, 0.1.1) — |
Try testing it with only one device on the bus too, there's always the chance that another device isn't behaving as expected. Let us know what you find - it's always helpful in case others run in to the same issue. I'll leave the issue open a while longer until we know that the software here can be ruled out (though I'm happy to try and help even if the error isn't with this library). |
Very very much appreciated! Da: Phil Fenstermacher [mailto:notifications@github.com] Try testing it with only one device on the bus too, there's always the chance that another device isn't behaving as expected. Let us know what you find - it's always helpful in case others run in to the same issue. I'll leave the issue open a while longer until we know that the software here can be ruled out (though I'm happy to try and help even if the error isn't with this library). — |
Powercycle solved the issue! |
Glad to hear a full reset took care of it, and thanks for letting us know - I'm sure it'll help someone in the future. I'm kind of curious to know if calling the |
In case I'll try that for sure and let you know. |
Hope you could help me to better identify the problem.
I personalized your python example to receive strike alert notifications and it worked fine from november up to last week when I removed the Vantage Pro2 weather station and installed instead the Envoy console.
The Davis side worked fine, but now, a week later I'm realizing that the AS3935 is not working anymore.
Now I realized that since I finished the installation it started to try adjusting due to noise level too high nearly continuosly (1800 times in 1h30min!) and then stopped (and I think it was not able anymore to load on RasPi boot).
Now if I try to run it from telnet i get the following message:
eusotec@raspberrypi:/home/pi/logs$ sudo /etc/init.d/Run_BlitzS start
Starting BlitzSensor
eusotec@raspberrypi:/home/pi/logs$ Traceback (most recent call last):
File "/usr/local/bin/BlitzSensor.py", line 36, in
sensor.calibrate(tun_cap=0x05)
File "/usr/local/lib/python2.7/dist-packages/RPi_AS3935/RPi_AS3935.py", line 19, in calibrate
self.set_byte(0x08, (self.registers[0x08] & 0xF0) | tun_cap)
File "/usr/local/lib/python2.7/dist-packages/RPi_AS3935/RPi_AS3935.py", line 107, in set_byte
self.i2cbus.write_byte_data(self.address, register, value)
IOError: [Errno 5] Input/output error
if I
sudo i2cdetect -y 1
I see randomly 03 adress popping up, but is not costant
I have also a CO2 sensor collecting CO2 values every hour which is also i2c connected to the raspi and running with a separate python program which is still collecting data in a regular way and was totally unaffected (also in the interval when the AS3935 was continuosly adjusting). So I'm guessing the i2c wiring is still fine.
Maybe I made a also a raspi update/upgrade in that occasion (not sure 100%) which I never made before since the last september installation.
Do you have any idea or suggestion about the cause ot the issue?
(I'll be able to check it phisically only next week and I'm missing a very good time of the year for lightnings so any help would be much appreciated!)
Carlo
The text was updated successfully, but these errors were encountered: