|
Post by SDL on Jan 10, 2019 19:16:27 GMT -8
OK. That means it is probably not the Serial port.
And your program is still running correctly?
BP
|
|
perrito
New Member
Posts: 22
Raspberry Pi: Yes
|
Post by perrito on Jan 11, 2019 2:58:27 GMT -8
Yep running steady being queried every minute
|
|
|
Post by SDL on Jan 13, 2019 9:26:03 GMT -8
The thing that doesn't make sense is that I had this problem with this commit the you have gone back to. I'm putting this on the list to be investigated now.
BP
|
|
perrito
New Member
Posts: 22
Raspberry Pi: Yes
|
Post by perrito on Jan 13, 2019 10:51:47 GMT -8
MM I wonder at this point if this is not somehow due to hardware inconsistency? Are we sure that we are all using identical components? perhaps different revisions of the sensor internals? I have read the diff a dozen times and nothing stands at all that could cause this particular issue in only some systems (other than the difference in peripherals) and perhaps the clock battery but I lack hardware knowledge to be able to determine these correlations.
|
|
|
Post by SDL on Jan 13, 2019 11:28:15 GMT -8
And there is also the question of power supply noise. Tell me how your are powering your system.
BP
|
|
perrito
New Member
Posts: 22
Raspberry Pi: Yes
|
Post by perrito on Jan 13, 2019 11:36:00 GMT -8
I am using a USB power supply that was, I am pretty sure, provided with the kit, connected to 220v through an APC UPS.
|
|
|
Post by SDL on Jan 13, 2019 11:40:00 GMT -8
Hmmm. That sounds pretty solid. Especially with the UPS on the system.
What did you mean "and perhaps the clock battery"?
Best, BP
|
|
perrito
New Member
Posts: 22
Raspberry Pi: Yes
|
Post by perrito on Jan 13, 2019 11:45:49 GMT -8
The DS3231 battery, although I do not think it could affect it in a meaningful way, is about 2 years old.
|
|
|
Post by SDL on Jan 13, 2019 17:12:50 GMT -8
No, probably not. I just was curious.
BP
|
|
|
Post by utantwx on Jan 17, 2019 6:20:40 GMT -8
Watching this thread as i have the same issues w/ NaN humidity, temp issues, fixed by power cycling.
|
|
|
Post by SDL on Jan 18, 2019 9:35:54 GMT -8
utantwx,
To help us all figure this out, could you give us some details?
BP
|
|
|
Post by utantwx on Jan 18, 2019 9:48:48 GMT -8
utantwx, To help us all figure this out, could you give us some details? BP Identical details to earlier in the thread with other user I use python to do REST calls every 2 hours against the system and with the older firmware, no issue, now with v35, after sometime the unit will either a) become unresponsive ( requiring power cycle ) b) start showing bad JSON response and Humidity = NaN and Temp = 0 ( requiring power cycle )
|
|
|
Post by utantwx on Jan 18, 2019 11:12:15 GMT -8
Example output just now
{"variables": {"OurWeatherTime": "2018-12-08 22:56:42", "FullDataString": "-2.40,nan,1.08,102324.00,73.88,3.47,6.43,135.00,1.26,1.23,4.81,2.72,11.41,0.00,225.00,0,2018-12-08 22:56:42,Utantwx98,0,-1,0.00,0.00,0.00,0.00,0.00,0.00,0.00,0.00,0.00,0.00,0.00,0.00,V:1,WXLMB ,0,,,0,,,0", "FirmwareVersion": "035", "IndoorTemperature": 1.08, "BarometricPressure": 102324.00, "Altitude": 73.88, "OutdoorTemperature": -2.40, "OutdoorHumidity": nan, "CurrentWindSpeed": 3.47, "CurrentWindGust": 6.43, "CurrentWindDirection": 135.00, "EnglishOrMetric": 0, "RainTotal": 1.26, "WindSpeedMin": 1.23, "WindSpeedMax": 4.81, "WindGustMin": 2.72, "WindGustMax": 11.41, "WindDirectionMin": 0.00, "WindDirectionMax": 225.00, "AirQualitySensor": 0, "ThunderBoardLast": ",,0,,,0", "ThunderBoardParams": "", "ESP8266HeapSize": 31664}, "id": "1", "name": "OurWeather", "hardware": "esp8266", "connected": true}
|
|
|
Post by SDL on Jan 18, 2019 14:10:58 GMT -8
OK. Looks like this is something a little different though. This is not a REST iinterface issue, but an AM2315 fail. We are building a test unit right now to start debugging this problem.
BP
|
|
|
Post by utantwx on Jan 25, 2019 9:34:11 GMT -8
So to give some more data here, you are all mentioning power and power fluctuations. I had some more 'invalid JSON' responses today but even power cycling would not recover and the date was all bizarre again. The plug that comes with the USB is not a polarized type plug ( with one prong larger ) and the cord I was using to power that block doesnt fit 'snugly' - is it possible that some wiggle play in the plug may have been creating all of this noise / interference / instability? Ive since brought the station inside to test some of this ( and redo my mast which nearly snapped in half last storm ). I was going to completely reset the device but after replugging it back in on a stable level and ensuring it was in there well, it booted with all the right values.
|
|