lloydrichards / mimiropen Goto Github PK

Partly as an oversight on my behave, I left off the 10K resistors on the buttons, assuming that there were internal pull up resistors on the esp32. While this is true for many of the GPIO, it might not be for the ones the buttons are attached too.

I need to test if this is an issue.

Was wondering why I wasn't getting any readings on the Battery Monitor. Realized that I had it strapped to Pin 12 which is one of the bootstrap pins and has a 51K resistor on it. Will need to change this to another pin, most likely GPIO34 on the next version. There is a chance I could hack together something to test this, but for now, it definitely won't work on GPIO12

Managed to mix up some NPN transistors for the PNP ones I need 😢 Will need to get the right part to test if the switch works correctly, but for now, I've bridged the connection with a 0-ohm resistor and got the examples working correctly.

Booked up a battery and found that no power is coming through the mosfet to the power switch. Might be cause I've got the sockie on backwards but will need to do some staring at the diagram to make sure I've not done anything silly with the wiring.

Have managed to put the LED's on GPIO 36 and 39 which can only be used an inputs. Will need to change this to something under GPIO34

Have noticed that the initial boot programs are running when the device is waking up from deepsleep. After some digging I noticed the following in the logs:

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:1044
load:0x40078000,len:8896
load:0x40080400,len:5828
entry 0x400806ac
Wakeup Reason: 4
mounted file system
reading config file
opened config file

parsed json
{"email":"[email protected]","serialNumber":"test","deviceName":"Test","userId":"ztx11HwFoJPuDJd1p7lLilvvkjg2","deviceId":"SAGvj9Ar25aG4i3Xxta1"}Initializing SD card...        
File already exists
SHT31 Success!
VEML6030 Success!
BME680 Success!
Compass Success!
Temp: 26.24
Humi: 40.96
Pres: 97136.00
Alt: 354.75
Lux: 936.00
IAQ: 25.00
eVOC: 0.50
eCO2: 500.00
Bearing: 83
Saving dataAppending to file: /testing.txt
Message appended
*WM:
*WM: AutoConnect
*WM: Connecting as wifi client...
*WM: Using last saved values, should be faster

Brownout detector was triggered

ets Jun  8 2016 00:22:57

rst:0xc (SW_CPU_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:1044
load:0x40078000,len:8896
load:0x40080400,len:5828
entry 0x400806ac

So it seems that there is a voltage loss when going into wifi mode so quickly. Will try a different USB C cable and it on the battery when I get the new MOSFET. Otherwise, I might need to change some of the capacitors to increase its stability after being asleep.

After implementing the code on the battery monitor, I realized that I was using two 1M resistors which exceed the internal impedance of the ESP32. have switched them out for 100K and will retest. If this works then will change the schematic