1. WeatherDuino Forum
  2. Weather Stations - WeatherDuino Pro2 Line
  3. Software Questions
Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5

Threaded Mode
Not progressing past Gathering Data
mikeyk
WeatherDuino User
****
Posts: 22
Threads: 4
Joined: Jun 2017
Weather Station: Yarramalong
Country: Australia
#1

01-01-2023, 11:04
Hi,
I have been using my Weatherduino Pro2 Plus since 2018 without any issues, it has been great.
Unfortunately due to a lack of free time, I only have one TX board with temp and humidity (SHT31).
I had plans to add a second TX board for rain and wind.
And onboard the RX board I have for Temp/Humidity HTU21D and BMP180 for Barometric.
This has been working well, including with Wunderground.

Now with some free time during holidays I noticed that at some point in past year it stopped updating Wunderground.
If I restart RX, I've noticed that it gets stuck on "Gathering Data Please Wait!" although I can move past this by pressing the touch screen.
There are also three indicators on top left of screen, first is green, followed by red then yellow.
The in built web server is working OK and displaying the data from the TX and RX board.

I re-flashed both TX and RX boards (fixed a date issue mentioned in another thread).
I've tried turning on debugging but it doesn't show anything about the WU Uploading process. I'm also unsure if some of the other debug options are working.

I should also mention the TX board temp had stopped working a while ago (TMP36) so I disabled that when I re-flashed the TX firmware. So not sure if this all could be caused by a hardware issue.
I also tried moving back to V8.2 from v9.

These are the debugs I turned on.
Code:
#define PRINT_DEBUG_WIFI
#define PRINT_DEBUG_NTP_UPDATE      
#define PRINT_DEBUG_WU_UPLOAD      
//#define PRINT_DEBUG_TS_UPLOAD
//#define PRINT_DEBUG_MYSERVER_UPLOAD
#define PRINT_DEBUG_VCHECK
#define PRINT_DEBUG_TCP_SERVER
//#define PRINT_DEBUG_AURIOL
#define PRINT_DEBUG_BIOS
#define PRINT_DEBUG_RF_MESSAGES
//#define PRINT_DEBUG_WIFI_SENSORS
#define PRINT_GENERALDEBUG

And this is a sample of the debug output.
Code:
20:38:21.287 -> ESP8266 FW Version: WIFI GOT IP
20:38:24.287 ->
20:38:24.287 -> OK
20:38:24.287 ->
20:38:30.803 -> Mode station OK
20:38:30.803 -> Multiple mux OK
20:38:35.818 -> Join AP success!
20:38:35.818 -> Connected to AP: AT+CWJAP?
20:38:35.818 -> +CWJAP:"yarra","24:xx:xx:b5:xx:xx",11,-55
20:38:35.865 ->
20:38:35.865 -> OK
20:38:35.865 ->
20:38:35.865 -> IP Address: 172.x.x.x
20:38:35.865 -> Broadcast IP: 172.x.x.255
20:38:35.865 -> Start tcp server OK
20:38:35.959 -> STATUS:2
20:38:35.959 -> Set tcp server timout 30 seconds
20:38:36.006 -> RTC current date: Jan 01 2023
20:38:36.006 -> RTC current time: 20:38:36
20:38:36.006 -> Sending NTP request to sync clock...
20:38:36.053 -> NTP replied
20:38:36.053 -> UTC time from NTP server: 09:38:36
20:38:36.053 -> Local date set to: Jan 01 2023
20:38:36.100 -> Local time set to: 20:38:36
20:38:36.100 ->
20:38:36.100 -> RTC adjusted to local time: 20:38:36
20:38:36.147 -> RTC current date: Jan 01 2023
20:38:36.147 -> RTC current time: 20:38:36
20:38:36.147 ->
20:38:36.475 -> Checking for latest software version...
20:38:37.459 -> Latest software version: P2AT2560_RX_v9.0_b004
20:38:37.506 -> WiFi connection is ON
20:38:48.287 -> 20:38:48 - Station ID: A1  Unit ID: 0  Sensor ID: 0  Full Message: A10000,A13,1AD3,0,0,
20:39:05.293 -> 20:39:05 - Station ID: A1  Unit ID: 0  Sensor ID: 0  Full Message: A10000,A13,1AD7,0,0,
20:39:22.256 -> 20:39:22 - Station ID: A1  Unit ID: 0  Sensor ID: 0  Full Message: A10000,A19,1AD7,0,0,
20:39:39.271 -> 20:39:39 - Station ID: A1  Unit ID: 0  Sensor ID: 0  Full Message: A10000,A1A,1AD7,0,0,
20:39:56.240 -> 20:39:56 - Station ID: A1  Unit ID: 0  Sensor ID: 0  Full Message: A10000,A1A,1AD4,0,0,

Cheers,
Michael
Find
Reply
mikeyk
WeatherDuino User
****
Posts: 22
Threads: 4
Joined: Jun 2017
Weather Station: Yarramalong
Country: Australia
#2

01-01-2023, 11:39
Hi Again,
I have given the TX board a clean as it's enclosure wasn't well sealed.
The RX board is now progressing past the Gathering Data screen.

I still have the Green, Red and Yellow dots on the top left of the screen, and still no WU_Upload info in the debug output.
 
Code:
21:34:29.631 -> ESP8266 FW Version: WIFI GOT IP
21:34:32.678 -> AT+GMR

21:34:32.678 -> AT version:1.2.0.0(Jul  1 2016 20:04:45)
21:34:32.678 -> SDK version:1.5.4.1(39cb9a32)
21:34:32.678 -> Ai-Thinker Technology Co. Ltd.
21:34:32.724 -> Dec  2 2016 14:21:16
21:34:32.724 -> OK
21:34:39.193 -> Mode station OK
21:34:39.193 -> Multiple mux OK
21:34:42.240 -> Join AP success!
21:34:42.240 -> Connected to AP: AT+CWJAP?

21:34:42.240 -> +CWJAP:"yarra","24:b6:57:b5:cc:40",11,-55
21:34:42.287 ->
21:34:42.287 -> OK
21:34:42.287 ->
21:34:42.287 -> IP Address: 172.17.1.20
21:34:42.287 -> Broadcast IP: 172.17.1.255
21:34:42.287 -> Start tcp server OK
21:34:42.381 -> STATUS:2
21:34:42.381 -> Set tcp server timout 30 seconds
21:34:42.428 -> RTC current date: Jan 01 2023
21:34:42.428 -> RTC current time: 21:34:42
21:34:42.428 -> Sending NTP request to sync clock...
21:34:42.475 -> NTP replied
21:34:42.475 -> UTC time from NTP server: 10:34:42

21:34:42.475 -> Local date set to: Jan 01 2023
21:34:42.521 -> Local time set to: 21:34:42
21:34:42.521 ->

21:34:42.521 -> RTC adjusted to local time: 21:34:42
21:34:42.521 -> RTC current date: Jan 01 2023
21:34:42.568 -> RTC current time: 21:34:42
21:34:42.568 ->

21:34:42.896 -> Checking for latest software version...
21:34:43.881 -> Latest software version: P2AT2560_RX_v9.0_b004
21:34:43.881 -> WiFi connection is ON
21:34:54.615 -> 21:34:54 - Station ID: A1  Unit ID: 0  Sensor ID: 2  Full Message: A10002,0,0,E1,0,
21:34:56.162 -> 21:34:55 - Station ID: A1  Unit ID: 0  Sensor ID: 0  Full Message: A10000,A3F,1BB2,0,0,
21:34:57.568 -> 21:34:57 - Station ID: A1  Unit ID: 0  Sensor ID: 2  Full Message: A10002,0,0,E1,0,
21:35:00.568 -> 21:35:00 - Station ID: A1  Unit ID: 0  Sensor ID: 2  Full Message: A10002,0,0,E1,0,
21:35:03.568 -> 21:35:03 - Station ID: A1  Unit ID: 0  Sensor ID: 2  Full Message: A10002,0,0,E1,0,
21:35:04.178 -> 21:35:03 - Station ID: A1  Unit ID: 0  Sensor ID: 5  Full Message: A10005,606,0,0,EA,
21:35:06.568 -> 21:35:06 - Station ID: A1  Unit ID: 0  Sensor ID: 2  Full Message: A10002,0,0,9AB,0,
21:35:09.568 -> 21:35:09 - Station ID: A1  Unit ID: 0  Sensor ID: 2  Full Message: A10002,0,0,E1,0,
21:35:11.021 -> 21:35:10 - Station ID: A1  Unit ID: 0  Sensor ID: 3  Full Message: A10003,118,0,F,0,
21:35:11.068 -> SystemInit2 DONE!
21:35:12.334 -> Connected to: 172.17.1.20
21:35:17.865 -> 21:35:17 - Station ID: A1  Unit ID: 0  Sensor ID: 0  Full Message: A10000,A3D,1BB6,0,0,
21:35:19.600 -> 21:35:19 - Station ID: A1  Unit ID: 0  Sensor ID: 2  Full Message: A10002,0,0,E1,0,
21:35:22.881 -> 21:35:22 - Station ID: A1  Unit ID: 0  Sensor ID: 2  Full Message: A10002,0,0,E1,0,
21:35:25.599 -> 21:35:25 - Station ID: A1  Unit ID: 0  Sensor ID: 2  Full Message: A10002,0,0,E1,0,
21:35:28.599 -> 21:35:28 - Station ID: A1  Unit ID: 0  Sensor ID: 2  Full Message: A10002,0,0,E1,0,
21:35:30.146 -> 21:35:29 - Station ID: A1  Unit ID: 0  Sensor ID: 0  Full Message: A10000,A3C,1BB9,0,0,
21:35:31.568 -> 21:35:31 - Station ID: A1  Unit ID: 0  Sensor ID: 2  Full Message: A10002,0,0,E1,0,
21:35:34.568 -> 21:35:34 - Station ID: A1  Unit ID: 0  Sensor ID: 2  Full Message: A10002,0,0,E1,0,
21:35:37.849 -> 21:35:37 - Station ID: A1  Unit ID: 0  Sensor ID: 2  Full Message: A10002,0,0,E1,0,
21:35:40.568 -> 21:35:40 - Station ID: A1  Unit ID: 0  Sensor ID: 2  Full Message: A10002,0,0,E1,0,
21:35:41.974 -> 21:35:41 - Station ID: A1  Unit ID: 0  Sensor ID: 3  Full Message: A10003,118,0,F,0,
21:35:43.568 -> 21:35:43 - Station ID: A1  Unit ID: 0  Sensor ID: 2  Full Message: A10002,0,0,E1,0,
21:35:47.131 -> 21:35:46 - Station ID: A1  Unit ID: 0  Sensor ID: 0  Full Message: A10000,A3C,1BBC,0,0,
21:35:47.881 -> 21:35:47 - Station ID: A1  Unit ID: 0  Sensor ID: 2  Full Message: A10002,0,0,E1,0,
21:35:50.553 -> 21:35:50 - Station ID: A1  Unit ID: 0  Sensor ID: 2  Full Message: A10002,0,0,E1,0,
21:35:53.553 -> 21:35:53 - Station ID: A1  Unit ID: 0  Sensor ID: 2  Full Message: A10002,0,0,E1,0,
Find
Reply
mikeyk
WeatherDuino User
****
Posts: 22
Threads: 4
Joined: Jun 2017
Weather Station: Yarramalong
Country: Australia
#3

01-01-2023, 11:48
After further TX board cleaning I now have the Wunderground update working.
The debug messages are working now, although it does say its failing yet I can see on WU that it has worked.

I will get to the shops and buy some PCB cleaner and give the TX board a though clean.

So, it looks like it is my fault for not having a well sealed TX enclosure.
 
Code:
21:39:51.490 -> 21:39:51 - Station ID: A1  Unit ID: 0  Sensor ID: 2  Full Message: A10002,0,0,E1,0,
21:39:51.912 -> Uploading to Wunderground
21:39:52.756 -> Create tcp OK
21:39:53.131 -> Waiting for WU response...
21:39:53.271 -> WU connection failed!
21:39:53.318 ->
21:39:58.709 -> 21:39:58 - Station ID: A1  Unit ID: 0  Sensor ID: 2  Full Message: A10002,0,0,E1,0,
Find
Reply
uncle_bob
Development Team
*****
Posts: 858
Threads: 30
Joined: Jul 2014
Weather Station: Conder Weather, Canberra
Country: Australia
#4

05-01-2023, 08:27
Good to see you're having some success there Mike.
Conder, Canberra Weather

Find
Reply
hornychz
Development Team
*****
Posts: 1.575
Threads: 38
Joined: Apr 2015
Weather Station: B/L Weather Station
Country: Czech Republic
#5

05-01-2023, 14:12
(01-01-2023, 11:48)mikeyk Wrote:  After further TX board cleaning I now have the Wunderground update working.
The debug messages are working now, although it does say its failing yet I can see on WU that it has worked.
I will get to the shops and buy some PCB cleaner and give the TX board a though clean.

Like
Best Regards
Zdenek

[Image: banner.php]
My outdoor AQM-I: here
Find
Reply
« Next Oldest | Next Newest »




Users browsing this thread: 2 Guest(s)
  1. WeatherDuino Forum
  2. Weather Stations - WeatherDuino Pro2 Line
  3. Software Questions