28AWG*8C, copper, , 0.3mtr/1.8mtr/3.6mtr as standard length
Self-powered from usb directly, no extra power needed.
All materials are CE, RoHS compliance
PE bag for each, then in carton
In the past you may use this DB9 RS232 to RJ45 console cable
But at present the DB9 COM port are fading step by step in PC
And in the coming days, the micro OTG cables may also be popular
Drivers are available which allow FTDI devices to work with the following operating systems:
Windows 8.1 x64
Windows 8 x64
Windows 10 32bit or 64bit
Windows Server 2008 R2
Windows 7 x64
Windows Server 2008
Windows Server 2008 x64
Windows Vista x64
Windows Server 2003
Windows Server 2003 x64
Windows XP x64
Mac OS X
Mac OS 9
Mac OS 8
Windows CE.NET (Version 4.2 and greater)
Support for WinCE7.0 Initial functional testing conducted by FTDI has shown that the FTDI drivers function as expected on Windows CE 7.0
Support for older versions of Windows Desktop
NOTE: Microsoft have ended support for certifying XP and VISTA through their WHCK test program. As such current builds will still work on XP and VISTA but are not Microsoft certified.
Differences in Driver API
For most of these operating systems two types of driver are available: Virtual COM Port (VCP) drivers and direct (D2XX) drivers. The VCP driver emulates a standard PC serial port such that the USB device may be communicated with as a standard RS232 device. The D2XX driver allows direct access to a USB device via a DLL interface.
To locate the drivers you want to install for a device, select which of the driver types you wish to use (VCPor D2XX) and then locate the appropriate operating systems. With the exception of Windows 98 and Windows ME, all devices are supported in each driver package.
Shenzhen Sinforcon Electronics Ltd is a company specialized in USB RS32 cables, USB UART cables, USB RS485 cables, panel mount cables, HDMI&DVI cables, lvds cables, etc. The integrated USB serial converters chips are FTDI FT231X, FT232RL, CP2102, PL2303HXD, PL2303TA, etc. We offer the customized cables for the customers of 50 countries and regions.
This cable is for updating DB9 to RJ45 cable, you can reference the following DB9-RJ45 cable information:
The standard formerly known as RS-232 or RS232 became EIA-232 then TIA-232. Most of the world still calls it RS232 but many names are used. RS-232D or EIA-561 defines the pin assignments for using RS-232 with RJ45 connectors. For an RJ45 male connector, the one you'll find at both ends of a Cat6 cable, pin 1 is the left most pin when you look at the connector with the tab up and the cable going away from you. It's easier to buzz out a cable with the tab down, in which case pin 1 is on the right, thus leading to a lot of potential confusion.For the DB9 female connector pin 1 is the top right and pin 6 is the bottom right when you look at the connector with the cable going away from you and the side with five pins on top. At this point it's probably good to mention that you only need three lines to have a functional cable. You'll need RD, TD and ground. All the other lines are used by software to control data. The three critical lines are handled by hardware. But most of us don't write the software at both ends, so it may wait forever for a signal transition that will never happen.
Cisco RJ45 to DB9 Serial Console Pinout
If you're familiar with Cisco routers then you've seen the RJ45 serial console connector they use, and the light blue RJ45 to DB9 cable. This does NOT follow the EIA-561 standard.
Cisco RJ45 to DB9 Serial Console Cable
Clear To Send
Data Set Ready
Data Terminal Ready
Request To Send
This cable works fine with minicom or HyperTerm because the Cisco hardware and software handles it. It's certainly possible to wire your RJ45/DB9 connectors following this pinout. If you do, please mark the connector clearly so the rest of us won't assume it's an RS-232D or EIA/TIA-561 pinout.
The only potential problem with this is that DB9 pin 1 for Carrier Detect (CD) is missing. Normally we would see pin 1 and pin 6 (CD and DSR) connected to the DTR output from the far end. But as I can attest, the cable works. And I've buzzed out the cable to confirm that pin 1 and pin 9 are not connected to anything.
Cisco uses two lines for ground to reduce crosstalk, which could be a benefit on especially long runs of cable.
About FT232RL chip:
Single chip USB to asynchronous serial data transfer interface.
Entire USB protocol handled on the chip - No USB-specific firmware programming required.
UART interface support for 7 or 8 data bits, 1 or 2 stop bits and odd / even / mark / space / no parity.
Fully assisted hardware or X-On / X-Off software handshaking.
Data transfer rates from 300 baud to 3 Megabaud (RS422 / RS485 and at TTL levels) and 300 baud to 1 Megabaud (RS232).
In-built support for event characters and line break condition.
New USB FTDIChip-ID? feature.
New configurable CBUS I/O pins.
Auto transmit buffer control for RS485 applications.
Transmit and receive LED drive signals.
New 48MHz, 24MHz,12MHz, and 6MHz clock output signal Options for driving external MCU or FPGA.
FIFO receive and transmit buffers for high data throughput.
256 Byte receive buffer and 128 Byte transmit buffer utilising buffer smoothing technology to allow for high data throughput.
Adjustable receive buffer timeout.
Synchronous and asynchronous bit bang mode interface options with RD# and WR# strobes.
New CBUS bit bang mode option.
Integrated 1024 bit internal EEPROM for I/O configuration and storing USB VID, PID, serial number and product description strings.
Device supplied preprogrammed with unique USB serial number.
Support for USB suspend / resume.
Support for bus powered, self powered, and high-power bus powered USB configurations.
Integrated 3.3V level converter for USB I/O .
Integrated level converter on UART and CBUS for interfacing to 5V - 1.8V Logic.