| Electronics > Beginners |
| CH340 / CH330 for commercial crowdfunding product |
| << < (3/4) > >> |
| Peabody:
I believe there is a problem with the new CP2102N, as opposed to the old CP2102. Something on their forum about that. Also, I believe all the CP21xx parts are strictly 3.3V, whereas the CH340x can be either. |
| mohf:
Thanks for the replies, it seems the CP21** and FTDI variants are not really better. --- Quote from: bson on April 27, 2019, 02:57:05 am --- They need a lot of external components including a crystal. --- End quote --- I'm planning on using CH330, which seems to be the same as CH340 except its SOIC-8 and only needs 1-2 decoupling caps :D |
| Rick Law:
There was a good discussion on CH340 on this forum not so long ago. You will find many other useful comments there on the user's view of the CH340. I commented in general positively about CH340 but negative-to-neutral in the non-uniquely way it ID itself to the OS. Here is exactly what I said there: --- Quote from: Rick Law on March 09, 2018, 11:54:18 pm --- --- Quote from: VEGETA on March 09, 2018, 09:39:01 pm ---... So in Windows 7 does these CH340 stuff work fine? ... --- End quote --- Yes. From personal experience these CH340 NANOs works just fine under Windows 7 (64 bit) and Windows XP sp3 (32 bit). I have at least 6 of those and so far I have no problem with any of them. My Win7 is x64, it may work with 32bit Win 7, but I cannot attest to if x32 would work as well. For both Win7/WinXP, the main issue I see with these CH340 is each instance is not unique in the windows registry, so the COM port number depends on which USB slot it is in and NOT which CH340 NANO actually plugged in. Whereas, I can make my 3 UNOs unique and change the Windows Registry so UNO1 is always COM6 regardless of which USB slot is hosting it, UNO2 is always COM7, so on. Can't do that with CH340. --- End quote --- https://www.eevblog.com/forum/beginners/problem-with-ch340-cheap-arduinos-in-windows-10/] [url]https://www.eevblog.com/forum/beginners/problem-with-ch340-cheap-arduinos-in-windows-10/[/url] |
| madires:
Isn't it the default behaviour of Windows to assign the COM port number based on the USB port? There aren't much users playing with the registry to attach a fixed COM port ID to a specific device. |
| DDunfield:
--- Quote from: madires on April 28, 2019, 10:18:40 am ---Isn't it the default behaviour of Windows to assign the COM port number based on the USB port? There aren't much users playing with the registry to attach a fixed COM port ID to a specific device. --- End quote --- Windows assigns USB->COM ports on the USB port AND the serial number of the device. Plug one device into one USB then another, you will have two serial ports reserved. Plug a different device into the same two USB ports, you will have two more (4) serial ports reserved. Windows allows a max. 256 COM ports, so if you are in an application where you attached a lot of devices, you need to clear them out from time to time. I recently did a windows based tester which interfaces to the DUT via the maintenance port (USB->Serial) and at startup and every 50 units tested, I go in and clear out all USB->Serial devices of the particular PID/VID we are using. Dave |
| Navigation |
| Message Index |
| Next page |
| Previous page |