[paulhs]

I know this may be a bit long but it explains all that I have done :  sorry for the length.  
 
4PRO Dual Band RX  v3.2 RevA
 
Note I received the receiver above prior to Xmas but had issues initially with too many copies of files eg Wifi.h. etc.  and it was not compiling without many errors (on MacOS High Sierra it would not compile at all)
 
My PC was used. I was able to upload the program into the ESP32 but it would not start up without pushing the reset button many times and even when it did start it crashed into a blank white screen that was unresponsive. I thought it was most likely to be programming issues in the PC since many copies of WiFi.h etc were on this .
 
I have had more time to try again late January into now .
I used a freshly loaded macOS Catalina  on  the MacBook Pro  and the MacOS system seemed to work Ok.
Since it looked to me from my research and previous experience that the Weatherduino program needed Python3 I loaded this into the operating system.
Using the Terminal program  I erased the ESP32 completely,  just to start fresh..
I noted in config_options.h that the fonts… needed to be loaded into the SPIFF  via the tools menu :
“ ESP32 Sketch data upload”    menu option.  This worked after a bit of fiddling. Note even this upload only occurred if the reset button was pushed momentarily when the program indicated it was ready to upload to the ESP32.
 
I then put in all the data for location,  wifi details,  Receiver type :  both LoRa and 433Mhz into the files.  Note I had to fit a spare 433 Mhz receiver on the board .   I do not have a LoRa transmitter board to use the LoRa receiver.
 
After all this the program verified and compiled OK and was uploaded (again pressing the reset switch )
 
The log was like this :
 
 
Sketch uses 1062641 bytes (81%) of program storage space. Maximum is 1310720 bytes.
Global variables use 57612 bytes (17%) of dynamic memory, leaving 270068 bytes for local variables. Maximum is 327680 bytes.
esptool.py v4.5.1
Serial port /dev/cu.wchusbserial56B80097791
Connecting....
Chip is ESP32-D0WD-V3 (revision v3.1)
Features: WiFi, BT, Dual Core, 240MHz, VRef calibration in efuse, Coding Scheme None
Crystal is 40MHz
MAC: 08:d1:f9:26:62:1c
Uploading stub...
Running stub...
Stub running...
Changing baud rate to 921600
Changed.
Configuring flash size...
Flash will be erased from 0x00001000 to 0x00005fff...
Flash will be erased from 0x00008000 to 0x00008fff...
Flash will be erased from 0x0000e000 to 0x0000ffff...
Flash will be erased from 0x00010000 to 0x00114fff...
Compressed 17568 bytes to 12204...
Writing at 0x00001000... (100 %)
Wrote 17568 bytes (12204 compressed) at 0x00001000 in 0.2 seconds (effective 570.0 kbit/s)...
Hash of data verified.
Compressed 3072 bytes to 146...
Writing at 0x00008000... (100 %)
Wrote 3072 bytes (146 compressed) at 0x00008000 in 0.0 seconds (effective 1228.2 kbit/s)...
Hash of data verified.
Compressed 8192 bytes to 47...
Writing at 0x0000e000... (100 %)
Wrote 8192 bytes (47 compressed) at 0x0000e000 in 0.0 seconds (effective 1852.1 kbit/s)...
Hash of data verified.
Compressed 1068944 bytes to 681956...
Writing at 0x00010000... (2 %)
Writing at 0x00017f3c... (4 %)
Writing at 0x00023e3d... (7 %)
….
….
….
….
….
Writing at 0x0011140a... (100 %)
Wrote 1068944 bytes (681956 compressed) at 0x00010000 in 8.8 seconds (effective 973.5 kbit/s)...
Hash of data verified.
 
Leaving...
Hard resetting via RTS pin...
 
 
 
The weatherduino RX would start but needed the reset switch pushed usually multiple times to work.  It went through the windows  , linked to the Wifi and then recognized the Tx data with W T R  and then displayed the temperatures , the wind, rain and UV and solar data. It would go into the submenu windows too.  Wifi worked Ok.  The Air quality module was recognised too.
 
However it crashed often after just a few minutes at the most into a blank screen (not able to be woken) or crashed  in the normal screen but no updating happened. Note all the fonts seemed Ok.  Sometimes before crashing the time shows the same time in the seconds and then jumps eg from 15:30 15 seconds to 15:03 21 seconds after a few seconds. This is often just before it crashes,
 
I tried simplifying the config too (a new file):  just choosing the Rx modes :  both 433Mhx and LoRa (I don’t have a transmitter for the LoRa though) so the transmitter could be detected.
 
Nil Wifi chosen ,  nil settings for solar, UV ..or  WU.  Nil AQM picked either.
? This seemed to be better but it still crashed and repeatedly still.
 
I checked the voltage :  and put a 5V nonUSB input via the connector :  voltage 5V was OK drawing about 250mA (this did vary) when working.
The RTC is working and the temp /baro onboard the RX is working too.
My old transmitter has been working well for ?5years and nil issues til my old receiver failed.
 
So in summary I have sorted out any compiling and upload programming issues onto the board ,  and even tried a basic config options.h file minimising choices in the program:  The receiver initially works but varies a bit in how long it takes to crash :  anything from seconds to <5minutes usually, up to a few hours at the most (rarely).  Sometimes it restarts with a single reset but it can also refuse to start until switched off for a long period (even hours)
 
I am at a bit of a loss as to what else I can try :  suggestions would be welcomed.
 
The latest RX software  in the WeatherDuino_4PRO_DB_v6.3_b004_20240826  folder is being used.  Arduino 1.8.19 and ESP32 2.0.14 are being used as well as all the program files included in the download.   The Arduino system is loaded onto a freshly created MacOS 10.15 Catalina disc. I did this to minimise any extra file copies.    The Catalina MacOS seems to be the oldest MacOS that can be used for the weatherduino programs from what I have read on programming forums mainly due to the need for  Python 3,  which has to be loaded also in this MacOS.   The PC I used too has too many copies of Wifi.h etc to be trustworthy so is not being used.  I will probably be able to use the latest MacOS soon too in a couple of weeks.   
 
Paul

I can load the config files onto the forum but since I used a new one with minimal settings there seems no point.  videos of it starting and crashing are too large a file.

[werk_ag]

Hi Paul,


Somethings to check when compiling the software:

Board: MH ET LIVE ESP32miniKit
Flash Frequency: 80Mhz
Particion Scheme: Default with spiffs
Core debug level: none

Sometimes before crashing the time shows the same time in the seconds and then jumps eg from 15:30 15 seconds to 15:03 21 seconds after a few seconds. This is often just before it crashes,

This is an important hint.

Please attach your Config_Options.h file so I can give a look.
Do you use it with Cumulus? USB or WiFi?

I can assure that the WeatherDuino 4Pro DB firmware is very stable, so we need to discover what is happening.

Regards
Werk_AG

[paulhs]

Hi Paul,


Somethings to check when compiling the software:

Board: MH ET LIVE ESP32miniKit
Flash Frequency: 80Mhz
Particion Scheme: Default with spiffs
Core debug level: none
 

Sometimes before crashing the time shows the same time in the seconds and then jumps eg from 15:30 15 seconds to 15:03 21 seconds after a few seconds. This is often just before it crashes,

This is an important hint.

Please attach your Config_Options.h file so I can give a look.
Do you use it with Cumulus? USB or WiFi?

I can assure that the WeatherDuino 4Pro DB firmware is very stable, so we need to discover what is happening.

Regards
Werk_AG

[paulhs]

I think I have posted the Config options file (I changed the .h to txt as the system has not accepted the .h) and also another file of the uploads to the ESP32. 

I have delayed replying since  I have updated my computer and using a more current Mac with up to date MacOS 15.3.1  and used this setup to program the receiver. The settings for the board are as you listed and the Arduino is 1.8.19 ,  ESP32 library is 2.0.14.   There are no extra libraries or files from other arduino programs other than those in the original Arduino download, ESP32 library update to 2.0.14 and those included in the weatherduino download.  The libraries and tools for the weatherduino were transferred into the Arduino folder (in Documents in the Mac system). 

I have used Terminal program to erase the ESP32.  and then loaded the "SPIFF".  and then the weatherduino program .
The upload report  files are attached. There are some "errors" which I don't understand during the compiling but the program uploads Ok then.  if I redo the upload again in the same session the file is uploaded and  these compiling issues are not seen. 

I think the programming seems to have gone well  and the receiver boots up ,  recognizes the WIFI ,  recognizes the transmitter with all readouts of wind, rain , temperature , UV and  solar .  The air quality sensor is also seen. 

However the same bombing /freezing issues seem to be persisting despite changing my computer, MacOS etc . 

It bombs with either the screen freezing or it goes into a blank white screen  :  I was getting again up to half a day of readings rarely but mostly it last 10 seconds or less or maybe a minute or two.
In addition the receiver will usually not boot again if I have left it on for a longer period unless I leave it powered off for an extended period (maybe an hour or more). After this it will then usually start again when power is applied. 

weatherduino_upload_file.txt Size: 6,55 KB  Downloads: 2

Paul

[werk_ag]

Hello Paul,

Thanks for posting the files. I've been looking at the Config_Options.h file and haven't found anything wrong, but just to try to eliminate a possibility that occurred to me, I'd suggest that you try to compile the software again, but now with the reception of AQM data disabled.

Code:

#define AQ_SOURCE       9  // 0= AQM Unit 0, 1= AQM Unit 1, 9 for not used

Please inform me if this solved the reboots, if not I will replace you 4Pro DB receiver. I have sent you a PM with details for this option.

Rgs
Werk_AG

[Nmweather]

I'm having an issue with my 4Pro receiver, it crashes and will not restart unless I unplug the power, the reset button has no effect. The current set up is receiving power from a raspberry pi over the micro usb port - I've set up cumulus on the raspberry pi and use the usb connection for both data and power. 

Any guesses? I'm wondering if it is a hardware issue? I'm on the latest firmware build,

Thanks you in advance!

Zac

Edit 4/15/25: Today it was showing the 'not receiving data' error screen but the web interface was still showing up to date data, then a few minutes later the screen is not displaying anything or responding to touch but the web interface is still up to date, a few minutes after that the web interface is now down. No response when I press the reset button on the back, but it will reset when i unplug the usb power.

Edit 4/17/25: Again a blank screen and unresponsive to touch, webserver not online BUT the graph on cumulus shows it was receiving data, i.e. no flat spots, possibly it had just happened, had to unplug the usb to restart the receiver.

Edit 4/26/25: I've discontinued using the RPI, not sure if it had anything to do with my issues but it wasn't booting after I cycled the power so now power is coming directly to the receiver via the USB port. It is still crashing most days but I can reset it with the button on the receiver, so strange. Really not sure what to do but it is frustrating how often it freezes up, could it be a power supply issue? I've attached the current config.h as a .pdf

Config_Options.pdf Size: 32,6 KB  Downloads: 1

[werk_ag]

Hi Nmweather

Sorry for the late repply.
Please make sure that your USB power supply is capable to provide at least 500mA in a stable way. If possible try to power it through the main board power conector and not by USB.

Your Config_Options file seems OK.

I'm running latest firmware for months and I can assure that is is very stable.

[uncle_bob]

Hi Zac.
Can you still see if the unit is connected to WiFi when it gets in this state? I have an earlier prototype of the 4 PRO receiver and see a similar issue when I block the WiFi to it for a couple of days.

Due to the differences in hardware, this may be a red herring though, but I thought it might be worth mentioning.

Hope you get it sorted, the Weatherduino systems work very well.