|
Post by reesecutler on Jun 8, 2018 12:45:00 GMT -8
Hi BP,
The system did fail with the AM2315 in place, with corrupted data. I seem to remember that it also locked up at times, but I mistrust my memory of that. Sorry.
Incidentally, my original system is running in the house and it does not seem to lock up. Note that these two systems had different local IP addresses, so should be orthogonal.
-Reese
|
|
|
Post by reesecutler on Jun 11, 2018 10:59:26 GMT -8
Hi BP,
So far I've sent back 3 AM2315 units (two that I bought and one that you sent me). Have these units been tested, and if so what was the result?
-Reese
|
|
|
Post by SDL on Jun 12, 2018 5:19:36 GMT -8
Reese,
Did you give us the results for the one we sent you? Did it do what the others did?
I believe that there is nothing wrong with the AM2315 units and we are looking at something else here. I'm starting to suspect noise in your system.
Do you have any AM2315s at all now?
John has still not tested them, but he promised me today that he will get to that today or tomorrow.
He was off at meetings in Santa Fe last week and stayed the weekend.
BP
|
|
|
Post by reesecutler on Jun 12, 2018 17:13:18 GMT -8
BP,
Yes, I reported the results of the unit you sent me, the third one that I had. It corrupted the data in the system (e.g. the time an date were reported wrong).
Presently, I have no AM2315s.
-Reese
|
|
|
Post by SDL on Jun 15, 2018 11:18:56 GMT -8
Great. Now we have all the information. Considering we sell thousands of these things, it is most likely not an AM2315 problem. We will check out the 3 AM2315s (we just got the third back).
Question: If you don't have the clock plugged in, does the system still corrupt data?
BP
|
|
|
Post by reesecutler on Jun 19, 2018 18:06:37 GMT -8
Hi BP,
I went back to postings on May 7th. Even without the clock in place, other data in the system got corrupted.
What have you found with the 3 AM2315s I've sent back?
-Reese
|
|
|
Post by SDL on Jun 21, 2018 7:48:18 GMT -8
Reese,
Your AM2315's work fine according to our tests. However, these aren't long term tests that would identify a long term problem. But, we sell 1000's of these sensor and there isn't a systemic problem with the sensors. We would know about it.
We have sent them back to you.
So back to your issue. Something is different in your setup. Did you try the additional pullup resistors (makes the I2C bus more immune to noise).
The other thing that is so odd is the corruption of the clock. That is really tough to do.
I wonder if this is a power supply issue?
BP
|
|
|
Post by reesecutler on Jun 21, 2018 9:43:32 GMT -8
Hi BP,
I await the temperature sensors. Once they arrive, I'll configure my system with a battery based 5 volt supply and see if that is better than the AC supply that came in the kit. If it's okay, I'll hold onto the extra controller board and clock for now in case they are useful for more debugging. Eventually, I'll return them to you.
If the battery backup +5V still fails, I'll try a beefy bench supply.
Regards,
-Reese
PS: One of the experiments (that I did not report) involved adding pull up resistors to the I2C lines. Same problem. -R
|
|
|
Post by SDL on Jun 21, 2018 9:49:23 GMT -8
Reesce,
I forgot you had second controller. So, you have swapped everything out completely and you still see the same problem.
Do you have any giant sources of RF energy in the area (like a radio tower or a Ham station)?
Did the pullup resistors make any difference in the frequency of the problem? What pullup values did you use?
BP
|
|
|
Post by reesecutler on Jul 25, 2018 8:32:13 GMT -8
Hi BP,
Sorry for the long delay. I'd come to the conclusion that there are software issues with the complete weather system. This means that for me, your product is broken, presumably this is true for some other customers.
So for the last month (at a retired person's pace) I've cobbled together an Arduino system to get data from the Am2315. This work has just completed, and the sensor seems to work just fine. I did notice one thing, when accessing the sensor too rapidly in succession, I managed to get peculiar data. This could be an artifact of my Arduino software skills. I did implement CRC checking and at a normal pace, I've experienced no errors so far.
During our interaction on this forum, you sent me an additional Complete Weather board, an extra AM2315 and an RTC module. Let me know if you want them back.
Regards,
-Reese
|
|
|
Post by SDL on Jul 25, 2018 13:29:21 GMT -8
Reese,
Have you tried the latest WeatherPlus software? We have seen NO uncorrected errors from the AM2315 on the OurWeather. It's something with your setup or hardware. Doesn't mean it's not our fault, but I can't conclude it is a software problem given what we are seeing.
BP
|
|
|
Post by SDL on Jul 25, 2018 16:27:43 GMT -8
One more thing I thought of this afternoon. If you can recompile the Weather Plus code, you can turn on debug by changing this variable:
#undef DEBUGPRINT
change to:
#define DEBUGPRINT
And this is then what you get out on the serial port. Lots of REAL information about what is going on with the AM2315
AOK=1
Temp: 24.00
Hum: 36.60
DwPt: 11.32
-----------------
AM2315 Statistics
-----------------
goodReads = 536
badReads = 0
badCRCReads = 0
badSpikeReads = 0
badMessageReads = 0
highTemp = 24.00
lowTemp = 23.50
lastGoodTemp = 24.00
highSingleBadReadCount =0
:0:0:0:0:0:0:0:0:0:0:
-----------------
This should get us to the real issues. But not if it is real lockup. Then we are back to thinking some kind of noise.
BP
|
|