ESP-32S has to be unplugged every time to work

asked 2020-05-27 10:47:52 -0600

JK gravatar image

I'm using a NodeMCU ESP-32S in a project which works fine. Running the node responsible works, and it does everything it's supposed to. However, if I stop that node and then want to restart it, I seem to have no communication with it. Unplugging the usb cable and then restarting the node always works.

This isn't more than an annoying thing, but I would like to fix it either way. Unfortunately I don't know that much about the esp32 or serial thingies. So I'm not sure where to start looking for a fix. My guess is that it has to do with the esp32 and not the ros node, but I'm not sure.

We are using a udev rule to remap the usb connection name, but I have used this before with an Arduino, and didn't have this problem then.

I'm running Ubuntu 16.04 and ROS Kinetic. I use the Arduino IDE to program the esp32. If anyone needs to see the code, it is here: https://github.com/thentnucyborg/Cybo... , but as I'm continuing other peoples work I only know that the serial work is done in serial_communication.py, and the whole node is started in led_dome.py. I'm also not sure why they didn't decide to run the esp32 as its own node.

edit retag flag offensive close merge delete