GPIO pin staying High after crash #9515
Replies: 3 comments 3 replies
-
I would want to know the answer to two questions:
The fact that these are happening suggests there is something wrong with your hardware, possibly a power supply problem. The ESP32 can take quite a lot of current when using the WiFi. With a good PSU the ESP32 is capable of long term operation. If you really can't stop it crashing you may need a hardware WDT that forces a reset. Or alternatively a hardware retriggerable monostable between the pin and the SSR so that the motor only runs if the pin is periodically pulsed. This is the brute force way to protect the motor. |
Beta Was this translation helpful? Give feedback.
-
When the device crashes, what is it's state. Does it go though a hard reset? If yes, the pin should be set to input mode. Which Pin do you use for the motor? Some pins have an internal pull-up enabled after reset. |
Beta Was this translation helpful? Give feedback.
-
What MQTT library are you using? The official ones are not very reliable in long-term running. Consider using mqtt_as which specifically addresses issues of long term running. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Using a ESP32 devKit CWRover to drive dc motor through a opto isolated relay, on a sun tracking solar array.
When the chip crashes it will leave the pin driving the Dc motor high, until I reboot it.
Have set up a WatchDog timer to catch faults and it works most of the time, but has failed twice now with not good out comes for the motor.
Is there a setting on a particular pin I can use to stop the Pin staying high after the crash.
I'm quite new to Python and ESP32 so am hoping it is just a rookie mistake.
I would appreciate any help
Thanks
Beta Was this translation helpful? Give feedback.
All reactions