As soon as i make these connections complete, the Arduino keeps on Rebooting. I opened the Windows Device Manager and it just keep on Resetting again and again.
Thus every time i went to start the serial monitor, it said "Port Not Found"
What could be the problem? It seems to work for others.!
The UNO's RX and TX pins are 5V logic so you are applying too much to the ESP8266. You might have damaged one or both devices.
The ESP8266 also can take fairly large spikes of current which is too much for the very small 3.3V supply inside the UNO to cope with. This could cause the voltage to drop and the UNO to reset.
You will need logic level converters and a 3.3V supply for driving the ESP8266.
gblades:
The UNO's RX and TX pins are 5V logic so you are applying too much to the ESP8266. You might have damaged one or both devices.
The ESP8266 also can take fairly large spikes of current which is too much for the very small 3.3V supply inside the UNO to cope with. This could cause the voltage to drop and the UNO to reset.
You will need logic level converters and a 3.3V supply for driving the ESP8266.
Damn it!! Is there anyway to check if I have damaged the Esp8266? The red power led still glows when connected VCC to the esp8266. But how do I check if I have ruined the Esp8266 for the worst?
If it uploads and blinks according to what you set the blink rate that would verify the processor.
// power down ESP connect LED after removing program pin from GND
// for node mcu use nodemcu1.1 esp-12E
// ensure esp cores are latest (now working)
// for
int ledPin = 2;
void setup() {
pinMode(ledPin, OUTPUT);
}
void loop() {
digitalWrite(ledPin, HIGH); // turn the LED on (HIGH is the voltage level)
delay(1000); // wait for a second
digitalWrite(ledPin, LOW); // turn the LED off by making the voltage LOW
delay(200); // wait for a second
}
After that you should be able to upload wifi scan sketch and that would check the wifi section.
You didnt say which esp btw and I used the sketch above on a node lau esp
I'm sorry for the cross-posting. I guess in the fuss of trying different troubleshooting options and overall confusion, I must have re-posted the same issue.