Outdoor Monitor crashing - Core 0 panic'ed (Load access fault)

#1

I’ve just received my O-1PST, but after only a few hours it can no longer stay up for more than 30 seconds.

The logs repeat this forever, I hope it helps you diagnose the issue:

ESP-ROM:esp32c3-api1-20210207
Build:Feb  7 2021
rst:0x15 (USB_UART_CHIP_RESET),boot:0xc (SPI_FAST_FLASH_BOOT)
Saved PC:0x420696ee
SPIWP:0xee
mode:DIO, clock div:1
load:0x3fcd5810,len:0x438
load:0x403cc710,len:0x918
load:0x403ce710,len:0x25f4
entry 0x403cc710
Serial nr: 84fce6099490
Detect OPEN_AIR
Server configuration: 
inF: false
inUSAQI: false
useRGBLedBar: 0
Model: O-1PS
MQTT Broker: 
S8 calibration period: -1
Firmware Version: 3.0.9
Found S8 on Serial1
Found PMS 1 on Serial0
Firmware Mode: O-1PST
Connecting to WiFi...
*wm:AutoConnect 
*wm:Connecting to SAVED AP: moncade
*wm:connectTimeout not set, ESP waitForConnectResult... 
*wm:AutoConnect: SUCCESS 
*wm:STA IP Address: 10.10.1.180
Webserver init: airgradient_84fce6099490.local
Post payload: {"wifi":-47,"boot":0}
WiFi connected!
IP address: 
10.10.1.180
Get server config: {"country":"AU","pmStandard":"ugm3","co2CalibrationRequested":false,"ledBarTestRequested":false,"ledBarMode":"off","displayMode":"on","placeOpen":false,"abcDays":8,"tvocLearningOffset":12,"noxLearningOffset":12,"temperatureUnit":"c","targetFirmware":"3.1.0","ledbarBrightness":100,"displayBrightness":100,"model":"O-1PS"}
Server configuration: 
inF: false
inUSAQI: false
useRGBLedBar: 0
Model: O-1PS
MQTT Broker: 
S8 calibration period: 8
Guru Meditation Error: Core  0 panic'ed (Load access fault). Exception was unhandled.

Core  0 register dump:
MEPC    : 0x4201cff2  RA      : 0x4201e970  SP      : 0x3fca0f20  GP      : 0x3fc8f800  
TP      : 0x3fc71844  T0      : 0x7fffffff  T1      : 0x4038d5b0  T2      : 0xffffffff  
S0/FP   : 0x3fc9d0b4  S1      : 0x3fc99420  A0      : 0x00000000  A1      : 0x00000000  
A2      : 0x3fcac9cc  A3      : 0x00000001  A4      : 0x3fc9975c  A5      : 0x00000001  
A6      : 0x3fe00000  A7      : 0x00000142  S2      : 0x00000001  S3      : 0x00000000  
S4      : 0x3fc93000  S5      : 0x3fc99000  S6      : 0x3fc92e6c  S7      : 0x3fc99000  
S8      : 0x3c0e2000  S9      : 0x3c0e13f4  S10     : 0x3fc93000  S11     : 0x00000000  
T3      : 0x0000005c  T4      : 0x00000000  T5      : 0x00000000  T6      : 0x20746547  
MSTATUS : 0x00001881  MTVEC   : 0x40380001  MCAUSE  : 0x00000005  MTVAL   : 0x00000004  
MHARTID : 0x00000000  

Stack memory:
3fca0f20: 0x3fc92e6c 0x3fc99420 0x3fca0f98 0x00000000 0x00000001 0x3fc99420 0x3fc94000 0x42006a8e
3fca0f40: 0x3c0e7e5c 0x3fcbESP-ROM:esp32c3-api1-20210207
Build:Feb  7 2021
rst:0x7 (TG0WDT_SYS_RST),boot:0xc (SPI_FAST_FLASH_BOOT)
Saved PC:0x42037956
SPIWP:0xee
#2

Can you please flash the latest beta firmware Version 3.0.10Beta 2
Available at the bottom of that page.
https://www.airgradient.com/documentation/firmwares/

Then please let me know if that fixes it.

#3

It no longer boot loops, but it also no longer posts data to the server?

[ApiClient] Warning: Ignore post data to server
[Configure] Info: Parse configure success
[Configure] Info: Set co2CalibrationRequested: 0
[Configure] Info: Set ledBarTestRequested: 0
[Configure] Info: {"country":"AU","pmStandard":"ugm3","ledBarMode":"off","displayMode":"on","abcDays":8,"tvocLearningOffset":12,"noxLearningOffset":12,"mqttBrokerUrl":"","temperatureUnit":"c","configurationControl":"both","postDataToAirGradient":false}

I see "postDataToAirGradient":false

#4

Reading more about the Local Server Documentation - I set {"postDataToAirGradient": true}, but it returns to false on reboot. I can’t see any sort of “commit” operation.

I also tried setting {"configurationControl": "cloud"} and get the reply Local configure ignored , but when I GET /config, it just shows it as "both" still.

At any rate, with the manual override of {"postDataToAirGradient": true}, it seems to be reporting again. Was the crashing a known issue?

#5

Yes the crashing was a known issue caused by the led_off setting. We are also aware of the post to server issue in the beta version.

We are in the last stretches for the next release and hopefully these things will be fixed.

#6

Excellent to hear! I look forward to the full release.