Open udellc opened 2 years ago
Fixed, Hypnos on Chime 4 is different version and CS pin assignment.
Nevermind, WeatherChimes continues to hard fault as described in the original post. The system recovers with the reset and will operate a while before faulting again. Logs to SD and MQTT are successful. But on SD, data is distributed to a lot of files because a new file is created each time the system resets. New files are not a big deal, but we need to figure out the hardfault issue.
Describe the bug WeatherChimes project; System runs as expected for hours, to many days, then experiences periodic Hard Faults.
Example of Errors file output: name | instance | Problem. | Corrupted | Failures | File_Source | Line_Number Chime | 4. | Hard_Fault | 0 | 1 | SD.cpp | 360
Data continues to log to CSV file after Hard Faults While SD data looks good, the system should not experience known hard faults before release to field operation.
Hardware in Use Chime #4 (Chime #3 seems to be experiencing additional SDI-12 related hardware issues) Feather M0 WiFi Hypnos Board: SD, DS3231 RTC, 3v 5v Power rail switching TSL2591 GS3 (SDI-12 soil moisture sensor by Meter) SHT-30 Air Temp, Humidity
To Reproduce Steps to reproduce the behavior: Change WiFi router info in arduino_secrets for: SECRET_SSID, SECRET_PASS for your internet router Ask Will or Chet for arduino secrets for MQTT broker and input Upload attached WeatherChimesV4SDSleepMQTT.ino and config.h to WeatherChimes Hardware
Expected behavior System should measure sensors, log to SD, and publish data to MongoDB via MQTT with no hard faults or hanging.
Code
Config
MQTT.h
arduino_secrets.h
Additional context Add any other context about the problem here.
Errors.csv chimes170.csv