You are not logged in. Your edit will be placed in a queue until it is peer reviewed.
We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.
-
5say goodbye to the arduino.Marko Buršič– Marko Buršič2016年05月11日 18:43:27 +00:00Commented May 11, 2016 at 18:43
-
@MarkoBuršič Could you please state a possible cause?Sushant– Sushant2016年05月11日 18:51:28 +00:00Commented May 11, 2016 at 18:51
-
2I'm not going to write a speculative answer, but you've probably shorted 12V through to something and fried the comparator, the Bluetooth module, the ATMega328 serial pins if not more of it. If you remove the ATMega328 and connect the TX RX pins together on the Arduino, then send data through the serial monitor, do you see it coming back? If not, you've probably fried the serial pins of the ATMega32U4 as well.Tom Carpenter– Tom Carpenter2016年05月11日 19:27:47 +00:00Commented May 11, 2016 at 19:27
-
Same here. I am pretty sure the damage was done when testing various things, never plugged a motor in AFAIK but it turns out capacitors on the wrong pin (eg D6) can sometimes send a spike back down into the USB chip and fry it. The actual 328P works fine in my other Arduino. Incidentally an out of spec 16MHz crystal can cause strange problems too.Conundrum– Conundrum2018年01月28日 06:33:09 +00:00Commented Jan 28, 2018 at 6:33