Difference between revisions of "Serial port"
m (→USB to Serial converter chipsets: More details on SiLabs and general.) |
(→USB to Serial converter chipsets: Remark concerning #FTDIgate) |
||
Line 166: | Line 166: | ||
|- | |- | ||
| rowspan="6" | FTDI | | rowspan="6" | FTDI<small>1</small> | ||
| many | | many | ||
| | | | ||
Line 306: | Line 306: | ||
| 2.0 | | 2.0 | ||
| device-dependant | | device-dependant | ||
| style="text-align:center" | —<small> | | style="text-align:center" | —<small>2</small> | ||
| 300? | | 300? | ||
| up to 2 Mbps | | up to 2 Mbps | ||
Line 318: | Line 318: | ||
| 2.0 | | 2.0 | ||
| 5,6,7,8 | | 5,6,7,8 | ||
| style="text-align:center" | —<small> | | style="text-align:center" | —<small>2</small> | ||
| 300 | | 300 | ||
| 1 Mbps | | 1 Mbps | ||
Line 373: | Line 373: | ||
Many USB devices that use a custom USB identity are based on these chips, too. Most manufacturers offer tools that allow setting USB properties like Vendor ID, Product ID, Product Description String, Power Descriptor, Device Release Number and Device Serial number. | Many USB devices that use a custom USB identity are based on these chips, too. Most manufacturers offer tools that allow setting USB properties like Vendor ID, Product ID, Product Description String, Power Descriptor, Device Release Number and Device Serial number. | ||
<small>1</small>: The CP2102 and CP2103 offer aliasing a std baud rate to a non-std baud rate by using the manufacturer's customization tool. | <small>1</small>: In October 2014 FTDI published Windows drivers version 2.11.0 and 2.12.0.0 that will check for fake FTDI chips. If these drivers suspect a chip to be a fake, they will overwrite the USB manufacturer and device ID of the device to 0, effectively [http://en.wikipedia.org/wiki/Brick_(electronics) bricking] the device. Installation of these driver versions (that were distributed via Windows Update automatically for some time) is strongly discouraged! See [http://www.eevblog.com/2014/10/27/eevblog-676-rant-ftdi-bricking-counterfeit-chips/ EEVblog #676] or [https://twitter.com/hashtag/FTDIGate #FTDIgate] for further information. | ||
<small>2</small>: The CP2102 and CP2103 offer aliasing a std baud rate to a non-std baud rate by using the manufacturer's customization tool. | |||
== Common Serial to RS232 Line Driver/Receiver Chipset Manufacturers == | == Common Serial to RS232 Line Driver/Receiver Chipset Manufacturers == |
Revision as of 11:50, 30 October 2014
Serial Ports are a common way to communicate with devices. The most common serial ports, as used by devices like Metex/Voltcraft multimeters, are RS-232 interfaces.
USB to Serial Converters
To operate devices that have RS-232 or TTL serial interfaces on computers that have only USB interfaces, converters are available. Many different chipsets exist that have slightly different properties, often supporting only a subset of what common UARTs like the 8250/16550A can do. Please note that a chipset-specific driver for the respective operating system is required (sometimes included in the OS already, e.g. mostly for Linux). Chipset and driver need to be seen as a union. The problems with some chipsets mostly seem to be more related to the quality of the driver than that of the hardware. Many original USB cables from OEM manufacturers use these converters, too, either with the chip manufacturer's or a custom USB ID.
Most of the USB to serial converter chipsets deliver 3.3 V or 5V TTL level signals and an additional converter chip between signal levels usually called a Line Driver/Receiver, e.g. a Maxim MAX232, is required to interface to a RS232 or other interface that uses different signal levels.
The RS232 standard allows quite a huge span of 3 to 15 V resp. -3 to -15 V for the two signal levels. Some RS232 devices won't work on USB-RS232 converters because these converters tend to be at the lower end of these voltages and the devices need need a higher RS232 signal voltage to work, e.g. to drive optocouplers in the interface. Sometimes a device might work on a converter of type A and won't on a converter of type B, depending on the chips used and other parameters chosen by the manufacturer.
USB to Serial converter chipsets
Manufacturer | Type | USB | Data Bits | Custom baud | Baud min. | max. | Modem | Drivers | Homepage | Remarks |
---|---|---|---|---|---|---|---|---|---|---|
Asix (former MOSChip) | MCS7840 | 2.0 | 5,6,7,8 | yes; broken on Mac | [1] | 4 serial ports | ||||
MCS7820 | 2.0 | [2] | 2 serial ports | |||||||
MCS7810 | 2.0 | [3] | 1 serial port | |||||||
MCS7720 | 1.1 | [4] | 2 serial ports | |||||||
MCS7717 | 1.1 | [5] | 1 serial, 1 parallel port and 3-port USB hub; out of production | |||||||
MCS7715 | 1.1 | [6] | 1 serial, 1 parallel port | |||||||
MCS7710 | 1.1 | [7] | 1 serial port; out of production
| |||||||
MCS7703 | 1.1 | [8] | 1 serial port; out of production
| |||||||
Cypress | CY7C64225 | 2.0 | 8 | — | 300 | 230400 | 4 | Win | [9] | HW Handshake supported only up to 1150200 baud. |
CY7C65211 | 2.0 | 7,8 | —? | 300 | 3 Mbaud | 4 | Android, Linux, Mac, WinCE, Win XP-8 | [10] | 1x I2C, 1x SPI, 10x GPIO | |
CY7C65213 | 2.0 | 7,8 | [11] | 8 x GPIO | ||||||
CY7C65215 | 2.0 | 7,8 | [12] | 2 serial ports, 2x I2C, 2x SPI, 17x GPIO | ||||||
FTDI1 | many | 7,8 | [13] | FTDI chips have 2 different driver models, one allowing bit-banging and other exotic features with appropriate chips. | ||||||
FT230X | 2.0 | 7,8 | ● | 183.1 | 3 Mbaud | 2 | Linux, Mac, WinCE 4.2-6, WinXP-8, others | [14] | ||
FT231X | 2.0 | 7,8 | ● | 183.1 | 3 Mbaud | 6 | Linux, Mac, WinCE 4.2-6, WinXP-8, others | [15] | ||
FT232H | 2.0 | 7,8 | ● | 183.1 | 12 Mbaud | 6 | Linux, Mac, WinCE 4.2-6, WinXP-8, others | [16] | Allows many protocols, including UART, JTAG, I2C, SPI, FT1248, bit-bang | |
FT234X | 2.0 | 7,8 | ● | 183.1 | 3 Mbaud | 2 | Linux, Mac, WinCE 4.2-6, WinXP-8, others | [17] | ||
FT4234H | 2.0 | 7,8 | ● | 183.1 | 12 Mbaud | 6 | Linux, Mac, WinCE 4.2-6, WinXP-8, others | [18] | 4x UART, 2x MPSSE (FTDI), 32x GPIO | |
Microchip | MCP2200 | 2.0 | 8; others? | ● | 300 | 1 Mbaud | 2 | Linux, WinXP, WinVista, Win7 | [19] | 8x GPIO; custom baud rates set in non-std way using DLL/USB cmd. There exists information on the net that it is based on a PIC18F14K50 microcontroller. |
Prolific | PL-2303x | 5,6,7,8 | 300 | 115200 | 6 | Linux, Mac, WinCE5, WinXP, WinVista-8.1 | [20] | There has been critique concerning the quality of the driver (for which OSses?). | ||
PL-2303HX | 1.1 | 5,6,7,8 | ● (driver!) | 75 | 6 (12) Mbps | 6 | Linux, Mac, WinCE4.2-7, Win2000, XP, Vista, 8 | [21] | 4x GPIO, 4x Aux GPIO; >115200 baud without control lines; Custom baud rates seem to require special driver from manufacturer | |
PL-2303RA | 1.1 | 5,6,7,8 | ● (driver!) | 75 | 921600 | 6 | Linux, Mac, WinCE4.2-7, Win2000, XP, Vista, 8 | [22] | With RS232 transceiver; 4x GPIO; Custom baud rates seem to require special driver from manufacturer | |
Prolific Fake | (PL-2303) | It seems that fakes of Prolific chips with limited reliability exist.1 | ||||||||
SiLabs | CP21xx | 2.0 | device-dependant | —2 | 300? | up to 2 Mbps | device-dependant | Linux, Mac, Windows | [23] | Family of several devices, 1-4 serial ports. |
CP2102 | 2.0 | 5,6,7,8 | —2 | 300 | 1 Mbps | 6 | Linux, Mac, Windows | [24] | ||
Sunplus | SPCP825 | 1.1 | 8 | - | 300 | 115200 | - | Windows 98-XP | [25] [26] | Seems to be used by old versions of the V&A VA4000 device cable. English home page broken. |
Texas Instruments | TUSB3410 | 2.0 | 5,6,7,8 | 50 (I)/1200 | 2 Mbps | 6 | Linux?, Mac?; Win | [27] | Integrated 8052 microcontroller, I2C, IrDA up to 115200 baud, auto handshake, internal test & diagnostics, 4x GPIO; Linux and Mac drivers seem to require (free) | |
WCH IC | CH340x, CH341x | 2.0 | 8 | — | 50 | 2 Mbps | 6 | Win98-Win7; (Linux) | [28] | IrDA SIR, ... |
Modem: Not all USB to serial converters support all lines used for modem status and hardware handshake. 6 means that RTS, CTS, DTR, DSR, DCD, and RI are present. 4 means that RTS, CTS, DTR, DSR are present, 2 means RTS, CTS only.
The list above tries to include all manufacturers of such converter chips. It does not include all variants because some manufacturers have over 100!
Many USB devices that use a custom USB identity are based on these chips, too. Most manufacturers offer tools that allow setting USB properties like Vendor ID, Product ID, Product Description String, Power Descriptor, Device Release Number and Device Serial number.
1: In October 2014 FTDI published Windows drivers version 2.11.0 and 2.12.0.0 that will check for fake FTDI chips. If these drivers suspect a chip to be a fake, they will overwrite the USB manufacturer and device ID of the device to 0, effectively bricking the device. Installation of these driver versions (that were distributed via Windows Update automatically for some time) is strongly discouraged! See EEVblog #676 or #FTDIgate for further information.
2: The CP2102 and CP2103 offer aliasing a std baud rate to a non-std baud rate by using the manufacturer's customization tool.
Common Serial to RS232 Line Driver/Receiver Chipset Manufacturers
USB to HID converter chipsets
These devices are based on the USB HID device class and have no serial interface/RS232 emulation.
Manufacturer | Type | USB | Drivers | Homepage | Remarks |
---|---|---|---|---|---|
Hoitek | HE2325U | 1.1 | * | [31] | Seems to be used by older versions of the UNI-T UT-D04 device cable. |
Unmarked | SO-20 chip | ? | ? | Found e.g. in the Victor 70C DMM, or the Victor 86C cable. | |
WCH | CH9325 | ? | * | Seems to be used by newer versions of the UNI-T UT-D04 device cable. |