{"id":779,"date":"2013-06-01T00:00:00","date_gmt":"2013-06-01T00:00:00","guid":{"rendered":"https:\/\/fir3netwp.gmsrrpobkbd.com\/2013\/06\/01\/how-do-i-connect-to-a-serial-device-using-a-usb-to-serial-convertor-in-linux\/"},"modified":"2023-02-24T13:04:16","modified_gmt":"2023-02-24T13:04:16","slug":"how-do-i-connect-to-a-serial-device-using-a-usb-to-serial-convertor-in-linux","status":"publish","type":"post","link":"https:\/\/www.fir3net.com\/UNIX\/Linux\/how-do-i-connect-to-a-serial-device-using-a-usb-to-serial-convertor-in-linux.html","title":{"rendered":"Connect to a serial device using a USB-to-Serial Convertor in Linux"},"content":{"rendered":"
For years, I had ran my Prolific USB to Serial cable from my Windows 32bit laptop without any issues.<\/p>\n
Unfortunately, life when running Windows is never easy. After upgrading Windows 7 to 64bit I tried to install the drivers from CNET downloads.
\nThis was a HUGE mistake. Even though the CNET downloader told me it was downloading at 28K in the background it was installing 8 (yes 8 plugins and other useless crap) onto all my browsers. Finally after cleaning up my machine and finding the drivers from a source not intent in filling my machine full of rubbish I discovered that the drivers fail to work correctly for Windows 7 64bit based platforms. Back to square 1.<\/p>\n
After wasting 2 hours trying to get this working in Windows I powered up Linux Mint. Loaded the necessary kernel module and tested. Success ! All in all 20 minutes taken. So high five to Linux and I certainly wont be using CNET downloads again !<\/p>\n
So what are the steps ?<\/p>\n
Connect the cable via USB.<\/p>\n
Next, run ‘lsusb’.<\/p>\n
admin@server ~ $ lsusb\r\nBus 002 Device 002: ID 090c:37a2 Silicon Motion, Inc. - Taiwan (formerly Feiya Technology Corp.) \r\nBus 005 Device 002: ID 067b:2303<\/strong><\/span> Prolific Technology, Inc. PL2303 Serial Port\r\nBus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub\r\nBus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub<\/pre>\nThen load the kernel module via the following command. Note : To ensure this survives a reboot append this line to ‘\/etc\/modules’<\/p>\n
admin@server ~ $ sudo modprobe usbserial vendor=0x067b<\/span><\/strong> product=0x2303<\/span><\/strong><\/pre>\nYou should now see that it is now showing as attached by running ‘dmesg’.<\/p>\n
admin@server ~ $ dmesg\r\n[\u00a0 131.747013] USB Serial support registered for pl2303\r\n[\u00a0 131.747038] pl2303 5-1:1.0: >pl2303 converter detected\r\n[\u00a0 131.758965] usb 5-1: >pl2303 converter now attached<\/strong> to ttyUSB0<\/pre>\nFinally, you will need to connect through to serial device \/dev\/ttyUSB0. This easiest way to do this is via ‘minicom’. Once you have issued the following command it will present you with a menu. Change (within the ‘serial port setup’ option) the service device to \/dev\/ttyUSB0 and any other settings i.e baud rate etc. Then select the exit option and you be connected to your serial device.<\/p>\n
admin@server ~ $ sudo minicom -s<\/pre>\n <\/p>\n","protected":false},"excerpt":{"rendered":"
For years, I had ran my Prolific USB to Serial cable from my Windows 32bit laptop without any issues. Unfortunately, life when running Windows is never easy. After upgrading Windows 7 to 64bit I tried to install the drivers from CNET downloads. This was a HUGE mistake. Even though the CNET downloader told me it … Read more<\/a><\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[52],"tags":[],"yoast_head":"\nConnect to a serial device using a USB-to-Serial Convertor in Linux<\/title>\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\t\n\t\n\t\n