|
|
Post by SDL on Jan 27, 2018 9:37:58 GMT -8
Folks,
As planned, we are planning to fix some outstanding bugs in our software during the month of February.
Please report in possible problems, and I will update the bug list below.
John Shovic
1) “AM2315 randomly Not Present or bad data” on OurWeather (note to John from BP: bit flip possibly ~16 degrees difference)
Fixed in OurWeather 028. Will look at Raspberry Pi issues.
2) Rain amount is not resetting at midnight - Grove Weather Pi (Now Scheduled for April - GWP Release)
3) Sunlight Sensor Calibration or gain numbers are off in GroveWeatherPi / simplest.py (Now Scheduled for April - GWP Release)
GroveWeatherPi script:
-----------------
Sunlight Vi/IR/UV Sensor
-----------------
Sunlight Visible(Lux): 26752.46
Sunlight IR(Lux): 26754.92
Sunlight UV Index: 349.74
4) OurWeather hangs every 5 reads from Python in customer program. May be addressed in #7 below. More testing required.
5) Look at ThunderBoard on the Raspberry Pi Zero and on the Raspberry Pi 3 GroveWeatherPi detection. Raspberry Pi 3 and GroveWeatherPi addressed. See posting down the bottom. (New) This fix works on the Raspberry Pi Zero and W as we expected.
6) no logging handlers found bug in SmartPlantPi.py and listen.py. Fixed in V021 up on GitHub
7) OurWeather disconnects because of weak WiFi. Reconnects now in V030 up on GitHub.
|
|
|
|
Post by karambit on Jan 28, 2018 9:21:18 GMT -8
My DS3231 is showing the correct time, however the total rain amount is not resetting after midnight. I am using the latest 2.99 code.
|
|
|
|
Post by SDL on Feb 10, 2018 14:09:17 GMT -8
Folks, I have completed the beta version of the new SDL_ESP8266_HR_AM2315 software that should fix any (and all, I hope) of the occasional bad data reads from the AM2315 on OurWeather and other projects. It is available here. I'm running it for a few days to see if I nailed it and then I will release it to the general public. github.com/switchdoclabs/SDL_ESP8266_AM2315_BETAThis just runs an AM2315 device off of the OurWeather board and records any errors. It will show the error count and why: badCRCReads = reads witha bad CRC from the AM2315 badSpikeReads = Good CRC, but temperature spike found (greater than 15.9 degrees C in a single read) badMessageReads = good CRC, but bad message Format Example: Hum: 31.00 TempC: 21.30 ----------------- AM2315 Statistics ----------------- goodReads = 102 badReads = 0 badCRCReads = 0 badSpikeReads = 0 badMessageReads = 0 highTemp = 21.30 lowTemp = 21.10 lastGoodTemp = 21.30 highSingleBadReadCount =0 :0:0:0:0:0:0:0:0:0:0: ----------------- John |
|
|
|
Post by kbrighton on Feb 11, 2018 2:52:05 GMT -8
Glad to see this. Here are my syslogged errors for the last couple of days:
Feb 11 00:10:38 spectrumwx GroveWeatherPi.py: AM2315 crc -1 outsideTemperature -1.000 lastoutsideTemperature -5.500 tempdelta 4.500 --3
Feb 11 00:10:38 spectrumwx GroveWeatherPi.py: AM2315 bad crc -1 outsideTemperature -1.000 --2
Feb 11 00:10:38 spectrumwx GroveWeatherPi.py: AM2315 crc -1 outsideTemperature -1.000 lastoutsideTemperature -5.500 tempdelta 4.500 --3
Feb 11 00:10:38 spectrumwx GroveWeatherPi.py: AM2315 bad crc -1 outsideTemperature -1.000 --2
Feb 11 00:10:38 spectrumwx GroveWeatherPi.py: AM2315 crc -1 outsideTemperature -1.000 lastoutsideTemperature -5.500 tempdelta 4.500 --3
Feb 11 00:10:38 spectrumwx GroveWeatherPi.py: AM2315 bad crc -1 outsideTemperature -1.000 --2
Feb 11 00:10:38 spectrumwx GroveWeatherPi.py: AM2315 crc -1 outsideTemperature -1.000 lastoutsideTemperature -5.500 tempdelta 4.500 --3
Feb 11 00:10:39 spectrumwx GroveWeatherPi.py: AM2315 bad crc -1 outsideTemperature -1.000 --2
Feb 11 00:10:39 spectrumwx GroveWeatherPi.py: AM2315 crc -1 outsideTemperature -1.000 lastoutsideTemperature -5.500 tempdelta 4.500 --3
Feb 11 00:10:39 spectrumwx GroveWeatherPi.py: AM2315 bad crc -1 outsideTemperature -1.000 --2
Feb 11 00:10:39 spectrumwx GroveWeatherPi.py: AM2315 crc -1 outsideTemperature -1.000 lastoutsideTemperature -5.500 tempdelta 4.500 --3
Feb 11 00:10:39 spectrumwx GroveWeatherPi.py: AM2315 bad crc -1 outsideTemperature -1.000 --2
Feb 11 00:10:39 spectrumwx GroveWeatherPi.py: AM2315 recovered after 6 retries outsideTemperature -5.500
Feb 10 04:10:38 spectrumwx GroveWeatherPi.py: AM2315 crc 1 outsideTemperature -2868.200 --1
Feb 10 04:10:38 spectrumwx GroveWeatherPi.py: AM2315 bad temp 1 outsideTemperature -2868.200 --2
Feb 10 04:10:38 spectrumwx GroveWeatherPi.py: AM2315 recovered after 1 retries outsideTemperature -5.500
|
|
|
|
Post by SDL on Feb 11, 2018 9:56:15 GMT -8
The fix on the ESP8266 is looking good. Here are the latest results:
-----------------
AM2315 Statistics
-----------------
goodReads = 63386
badReads = 0
badCRCReads = 0
badSpikeReads = 0
badMessageReads = 0
highTemp = 23.10
lowTemp = 19.70
lastGoodTemp = 20.30
highSingleBadReadCount =0
:0:0:0:0:0:0:0:0:0:0:
-----------------
Hum: 31.00
TempC: 20.30
The driver now has auto recovery from a variety of errors built in to the driver.
John
|
|
mcinflyre
Junior Member
Posts: 53 
Raspberry Pi: Yes
Other Device: PC, Mac and Android devices.
|
Post by mcinflyre on Feb 28, 2018 19:47:56 GMT -8
Hi,
For item #5, can you include looking into issues with the Thunder Board not being detected when running the GroveWeatherPi on a Raspberry Pi 3?
The Thunder Board works when it’s the only I2C board connected to the Pi2Grover, but it is not detected when the other I2C boards are wired per the documentation.
Thanks.
|
|
|
|
Post by SDL on Mar 1, 2018 9:34:53 GMT -8
Mcnflyer,
Yes, we are working not the issue right now. We've put together a big matrix of Raspberry Pi versus the Thunerboard and are launching into the testing tomorrow.
BP
|
|
mcinflyre
Junior Member
Posts: 53
Raspberry Pi: Yes
Other Device: PC, Mac and Android devices.
|
Post by mcinflyre on Mar 1, 2018 14:45:16 GMT -8
|
|
|
|
Post by SDL on Mar 3, 2018 15:46:04 GMT -8
Folks, I have figured out what is going on. We have found some issues moving around the analog part of this board. I'm somewhat at a loss to explain how this got through testing, but it looks like we didn't run through this board through a full GroveWeatherPi test. We did run it on Arduino (several types) and on the Raspberry Pi 3 based ThunderBoard IOT Kit and everything was very cool. Now, I don't have anyone to blame but me since I wrote the test plan. BP, not your problem. Had I put the GroveWeatherPi on the test plan, we would have caught this. The issue is how the ThunderBoard behaves under certain I2C bus loading (using the I2C Mux for example). I figured this out by using a Logic Analyzer and an Oscilloscope and some intuitive thinking about the tank circuit on the ThunderBoard (the analog lightning detection circuit on the board). Here is the fix (this applies to 0240-092917-01 revision of the the ThunderBoard). To get the board to work reliably with the Raspberry Pi 3 in the GroveWeatherPi kit, you need to bypass the I2C buffer on the board. See the picture below. You do this by: 1) Take a Grove cable. 2) Cut the yellow and the white wire close to the plug 3) solder the white (SDA) wire to the upper test pad (see picture) 4) solder the yellow (SCL) wire to the lower test pad (see picture) Now GroveWeatherPi will see the ThunderBoard when connected to I2C channel 1 on the I2C Mux. The AS3935 on the ThunderBoard still does not like loaded I2C buses. It likes to be on lightly loaded I2C bus segment. But that is true of any of the boards using the AS3935. We will be reworking the new batch of Thunderboards that we just received to fix this problem (basically doing what you are doing up above, but done on the board). We will post here when we have the board back and if any of you GroveWeatherPi customers would like a replacement board, we will give you instructions on how to get one. Whew! This used a lot of my brain cells up figuring this out. Best regards, John C. Shovic, PhD CTO SwitchDoc Labs  |
|
