H5 Emergency stop and ESP32 programming #243
Replies: 2 comments 4 replies
-
Hi @demsarmatjaz,
No, device needs to be power-cycled. Threads in the code end when emergency condition is reached and can not be easily restarted.
I assume you meant "until LCD is disconnected". Strange, I'm able to program ESP both when display is working and when it's not (due to insufficient power provided by just the USB cable). Not sure why there would be such a discrepancy between our setups.
Yes, I had trouble with it as well, going forward we'll probably switch to WiFi for this. |
Beta Was this translation helpful? Give feedback.
-
Hi, thanks for the fast response. Ok, all clear about the emergency stop. |
Beta Was this translation helpful? Give feedback.
-
Hi Maxim,
I have two questions. The first relates to the emergency stop; is there any other way to get out of an emergency stop than resetting ESP32? I know that that could be dangerous in some situations, but, for example, pressing a defined key on the keyboard for 5 seconds sounds okay to me.
The second one is about programming ESP32. Yesterday I received PCBs so I soldered ESP32, two dip chips, and all the connectors and put everything together on my desk. While playing with encoders and pulse wheels I decided to change pulse wheels properties in the code and found out that I can't program ESP until LCD is connected so I disconnected the 4-pin LCD header and transferred the code to the ESP. Probably RX and TX lines interfere with the UART port or am I doing wrong something? Some days ago I struggled with the G-Code sender, it couldn't get connected to ESP, I suppose that for the same reason.
BR, Matjaz D.
Beta Was this translation helpful? Give feedback.
All reactions