Unless I've missed something, further HW troubleshooting would require deeper knowledge of the board and advanced tools. Check if LED would blink and/or use FTDI programmer connected on RX-TX pins. Another check would be connecting 3.3 V source to the corresponding pin directly.Also worth trying connecting it to another PC - captain obvious. Also an obvious one to make sure your cable has data lines and not just a charging cable. Don't underestimate the last one, using dodgy cables or adapters (like to USB-C) can result in brownout of your ESP ending up without receiving enough power. Simply trying to plug your board in different port or using different cable. For hardware problem easiest would be to check cable and usb port functionality. This ESP8266 NodeMCU Web Server is mobile responsive and it can be accessed with any device with a browser in your local network.If nothing new appears, I would think of hardware or connectivity problem, otherwise a driver issue. If you really think the problem is with CoolTerm try using puTTY and see what happens.R. I mainly changed the time recording from simple hours based on the millis()-funktion to an actual time using the time-library. You can do it opening Device Manager, expanding Ports (COM&LPT) and checking what you see there before and after you connected the device. Sadly I cant say what exactly caused the problems. Check if when you connect your board via USB a new device is detected.If as you said LED won't even flash ones as it should upon getting power, it is likely a hardware (HW) or wiring issue. In ESPlorer, there is an option under settings which if unchecked will stop looking checking for the version of the code.Ive found the CH340 to be much more sensitive to differences in cables whereas the CP210x seems solid with any cable I use. If it is a CH340 and its still flaky, swap the USB cable. I can think of several issues including that you board is not working. Maybe check to see if youve got the correct driver installed. On the other hand, is there a really easy way to compile/download latest NodeMCU firmware BIN file? Even one with all the modules active will be fine for me now, I'm just trying to understand and test things.I had similar issue before. Is there a way to obtain NodeMCU firmware version by software via Arduino IDE code, ESPlorer GUI or something similar? These are the most common locations for LEDs. As we can see, GPIO0 maps to pin 3, GPIO2 maps to pin 4, and GPIO5 maps to pin 1. Hey there, I am rather a noob in the world of home assistant and home automation, I’m going along and thoroughly enjoying learning, but I have encountered something that seems to be beyond my coding google-fu abilities and I just can’t find the solution, I’m hoping some kind person could help me crack this one. ![]() So you need to refer to the NodeMCU pinout diagram and check which GPIO maps to which pin. I get the following "error" when I reset the dev board:Ĭommunication with MCU.Got answer! Communication with MCU established.Ĭan't autodetect firmware, because proper answer not received (may be unknown firmware).Īt this point I'm totally clueless about what version of firmware I have. One gotcha is that NodeMCU uses the numbering system for the NodeMCU board no matter which module you use. Since I don't really know what came pre installed from China, I downloaded ESPlorer to try to determine NodeMCU version. My problem came when I wanted to update NodeMCU firmware. I have a Amica ESP-12E (v2?) dev kit connected to a DHT22 which I program using the Arduino IDE.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |