Topic: FilaWinder Nano's being BRICKED!
FTDI, the manufacturers of the chips for USB coms, released a driver update 2.12.0 that could brick counterfeit FTDI chips. Since I don't keep up with the news, I figured this out first hand the hard way.
I had crossed contacts with the power supply switch and the potentiometer, and essentially fried the AtMega on the nano board. I ordered a replacement nano, got the sketch downloaded, had some issues with sensor calibration so tried the troubleshooting mode. The nano wouldn't connect like normal, had to manually assign the device driver, and the Arduino software kept claiming that the port was in use if I tried to use it. After much time investigating and other troubleshooting steps, I landed on the brick problem. Essentially FTDI recognizes counterfeit chips and rewrites their PID that prevents them from working on any device.
I found a good starting point for reversing the problem here:
reddit.com/r/arduino/comments/2k0i7x/watch_that_windows_update_ftdi_drivers_are/clgviyl
My personal experiences taught me some things though:
1. You need to get windows to stop installing drivers from the internet, otherwise when you plug in your device for the "first" time windows will continue to download the troublesome driver.
2. You need to make sure the troublesome driver is deleted from your computer, windows defaults to the most current version on your computer. This can be done by uninstalling the com port assigned to your device, and checking the remove driver option.
3. There is a second driver as the USB serial converter. make sure this is gone too.
4. In the end, I'm not really sure there is a need to change any of the files as is implied by the post in my link. It seems to me that the PID can probably be changed without assigning a driver, just as long as there's no way for the troublesome driver to come back and undo the work.
The reason I post all this here is because not only was the replacement nano I purchased bricked for the counterfeit chip, but so was the nano that came with the FilaWinder. If the troublesome driver is installed it seems you get one freebee connection to do stuff, after that there's no changing anything without a bunch of headache. FTDI says that they are going to change that somehow, but I'm venturing a guess that it's still going to cause a lot of problems. Spread the word, prevent headaches by keeping 2.12.0 off your computers.
