Nano not communicating with computer

The four nano's were fresh, out of the box, never used units. And yes, I do know how to handle static sensitive devices, after servicing and designing computer controlled devices for 20 years.

Hi,
Can you see on the Nano, what USB IC they are using?

Tom... :grinning: :+1: :coffee: :australia:

Hi @chasrie,

I had the same problem with four new Nanos a while back. I solved it by upgrading the IDE, changing the board to "Arduino Nano (Old Bootloader)", and changing out the USB cable. That was for the driver being CH340 (they are most of the time). Also some USB cables are only power cords that don't include D+ or D- lines. You couldn't tell the difference usually.

Unfortunately, unlike chips of years ago which are well marked, these aren't. I've tried using a magnifying glass, illuminating them off angle, and even trying to photograph them with my camera (an old trick I use) but couldn't raise the markings. it's a bad practice, as I know that it may not be the same chip as what is on the boards, but the schematic says it's a ATSMD11D14A. I even briefly played with the idea of bypassing the chip and trying to communicate via the ttl side. But that couldn't be easily done either. In thinking about it, I don't think that there is a bad USB Ic with four different boards.

The ATSMD11D14A usually looks like this:

Screen Shot 2021-10-28 at 8.39.34 AM

But the CH340 looks like this:

Screen Shot 2021-10-28 at 8.40.51 AM

Aftermarket Nanos are NEVER the ATSMD11D14A.

I upgraded the IDE from version 1.8.12 to version 1.8.17, thinking that maybe the problem would be resolved with an update of the IDE. I'm leaning towards a bad cable since I tried two. One cable came with an order of five NANO's, so I would assume that it would be good, But we all know what "to assume" really means. The other works in updating my Garmin GPS, but again, I can't really guarantee that it is wired correctly. I really don't like the contacts either make with the "A" Connector to the computer. I've orders an adapter to go from the "B" connector for the Uno to the Mini connector of the Nano. Hopefully, that'll solve the problem. At least I'll know I'll be working with a good data cable. Thanks for the suggestion.

Again, I couldn't raise the part number but the Chip looks like the CH340. I was barely able to raise the WK.. on the chip. Thank you

Do your nanos show up in device manager when you plug them in? As 'unknown device' or as 'USB comport'?
We had a similar question recently, so I post the same question/advice:

Can you see the VID and PID identifiers in device manager? These can usually be found - even with 'unknown devices' - under properties->details. ( I don't have an english version of windows so I don't know exactly where to find )
VID and PID ( Vendor-ID and product ID ) identify the USB chip and windows uses these to know which driver to use.
This page can be used to identify a chip by its VID and PID. The example entries in the link are for a CH340

The ports show up in device manager, but no driver. In th Properties under the device manager it shows up as "Standard Serial over Bluetooth link (Com5)" I don't see a VID or PID under the "Properties details", Thank you.

To be honest, I really suspect that I have a bad communications cable. It really doesn't fit tightly into the USB port on the computer, no matter which one I try.

Thanks for the suggestion.

That's very weird. I cannot imagine how this could be a 'Bluetooth link' if a USB device is plugged in. VID and PID are shown only for USB devices. Are you sure this is your nano? The VID/PID is shown under details as Hardware-ID

Have you tried putting isopropyl or acetone or methylated spirits on the IC and observing it as the liquid dries?

Tom.... :grinning: :+1: :coffee: :australia:

In the dropdown box, select Hardware Ids.

I've done both of those, the IDE shows Com5 and Com6 on the "Tools/Ports" but no board associated with them, either plugged in or not. Device manager shows Com5 as being active but not as a Nano. It has substituted a Windows driver for Bluetooth. I can't read the marking on the chip but it look like it might be a CH340. I'm seriously leaning towards as bad data cable, but can't be sure until I get some parts next week, so the project is on hold for the moment

No, I haven't, but that's a good idea. I'm reasonably sure that it is the CH340 from your description and what I could raise. I'll try the isopropyl alcohol and/or acetone next time I dig into it. Thanks.

I'm reasonably sure that they are a Nano. I tried four out of ten, and all four have the same reaction, no communication, with either of two data cables from the computer to the Nano board. BTW the two were purchased in lots of five from two different vendors. Each group have the same components of them but different markings on the silk screen of the board, making them either a different iteration of the board or a different manufacturer. If the one of the cables were good, the chances of one set communicating are pretty good. I didn't commit the other six to a test for fear that I may have damaged the first four (two from each batch) with a bad cable. The project is on hold until I get some new parts (data cables and adapters for type C "printer" to mini-B for the Nano) in next week. One of those should work. I'll let you all know. Thanks all.

Weird? Yes, my thoughts exactly, but with Microshit who knows what it may substitute if it doesn't see the USB interface. Funny thing, the computer does recognize a USB device plugged in, but giving the USB plugin notification sound and the USB unplugged notification sound.

I've done both of those, the IDE shows Com5 and Com6 on the "Tools/Ports" but no board associated with them, either plugged in or not. Device manager shows Com5 as being active but not as a Nano. It has substituted a Windows driver for Bluetooth. I can't read the marking on the chip but it look like it might be a CH340. I'm seriously leaning towards as bad data cable, but can't be sure until I get some parts next week, so the project is on hold for the moment

Update, on my problem. PROBLEM SOLVED. As per usual with MicroShit, when it updated my Windows10 last time, it clobbered the driver for the USB detection of the Nano for some reason. Uno works fine. I had to download an updated driver detection file from Microshit. I'm surprised that, they detected the problem so fast, since the last full update was about a week ago. Device manager now shows "USB-Serial Device CH340(Com4) and I was able to upload "BLINKER" to the processor after setting the Processor to "OLDBOOTLOADER". Thank you to all of your wonderful suggestions. Who knew Microshit would F***up things. lol