ESP32 + RFM95W + Deep Sleep

End Devices (Nodes) Hardware
21

Here is some logging (nothing added yet). Maybe the timestamps ring a bell
It stopped again after 114 cycles.

rst:0x5 (DEEPSLEEP_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
configsip: 0, SPIWP:0xee
clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
mode:DIO, clock div:2
load:0x3fff0018,len:4
load:0x3fff001c,len:952
load:0x40078000,len:6084
load:0x40080000,len:7944
entry 0x40080310
Starting
2123278950: Chip version : 12
2123278983: Loaded sate
2123278994: state loaded
2123278998: do job
2123279001: Wake up BME and start reading
2123279645: BME started and measured
2123285966: Pressure: 103531.195312
2123286040: engineUpdate, opmode=0x908.
2123286064: Time on air : 56 ms
2123286097: TXMODE, freq=868100000, len=20, SF=7, BW=125, CR=4/5, IH=0
2123286312: Packet queued
2123289645: Not using interupt trigger 0
2123289657: Rx delay : 954 ms
2123349329: RXMODE_SINGLE, freq=868100000, SF=7, BW=125, CR=4/5, IH=0
2123355494: Not using interupt trigger 0
2123355503: No downlink data, window=RX1
2123355508: Rx delay : 1913 ms
2123409270: RXMODE_SINGLE, freq=869525000, SF=9, BW=125, CR=4/5, IH=0
2123422091: Not using interupt trigets Jun  8 2016 00:22:57

rst:0x5 (DEEPSLEEP_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
configsip: 0, SPIWP:0xee
clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
mode:DIO, clock div:2
load:0x3fff0018,len:4
load:0x3fff001c,len:952
load:0x40078000,len:6084
load:0x40080000,len:7944
entry 0x40080310
Starting
2142200711: Chip version : 12
2142200745: Loaded sate
2142200756: state loaded
2142200759: do job
2142200763: Wake up BME and start reading
2142201407: BME started and measured
2142207728: Pressure: 103520.976562
2142207801: engineUpdate, opmode=0x908.
2142207825: Time on air : 56 ms
2142207857: TXMODE, freq=868300000, len=20, SF=7, BW=125, CR=4/5, IH=0
2142208073: Packet queued
2142211406: Not using interupt trigger 0
2142211417: Rx delay : 954 ms
2142271090: RXMODE_SINGLE, freq=868300000, SF=7, BW=125, CR=4/5, IH=0
2142277255: Not using interupt trigger 0
2142277264: No downlink data, window=RX1
2142277269: Rx delay : 1913 ms
2142331030: RXMODE_SINGLE, freq=869525000, SF=9, BW=125, CR=4/5, IH=0
2142343851: Not using interupt trigets Jun  8 2016 00:22:57

rst:0x5 (DEEPSLEEP_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
configsip: 0, SPIWP:0xee
clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
mode:DIO, clock div:2
load:0x3fff0018,len:4
load:0x3fff001c,len:952
load:0x40078000,len:6084
load:0x40080000,len:7944
entry 0x40080310
Starting
2161122483: Chip version : 12
2161122516: Loaded sate
2161122527: state loaded
2161122531: do job
2161122534: Wake up BME and start reading
2161123178: BME started and measured
2161129499: Pressure: 103513.843750
2161129558: engineUpdate, opmode=0x908.
2161129583: Time on air : 56 ms
2161129614: TXMODE, freq=868500000, len=20, SF=7, BW=125, CR=4/5, IH=0
2161129831: Packet queued
2161133169: Rx delay : 954 ms
22

Hi,

I make some modification in git repository can you give it a try:

  • I remove a part of code not used in ESP32 (the part that around missing message “Not using interupt trigger 0” after last TX) It can produce long sleep.
  • I add a log message “Scheduled job at XXXXX” to see if there is task schedule to far in the future.

I think the first modification will solve the problem.

1 Like
23

Changes applied.

Test is running, lets see how far it will go.

I also started another test with an ESP32, but just using Wifi and MQTT. This is sending every 15 seconds a wake up counter, to exclude there is no bug in the ESP32 (hardware/software).

1 Like
24

@grazy it’s looking good so far buddy :wink:

25

For future reference. I had the same error for “Chip version : 0” as described in the first post.

I fixed it by modifying the platformio.ini file to match my exact board version. For example:

board = lolin_d32