USB to Serial into a Robot
I am attempting to connect a Bioloid robot into a Ubuntu 10.04 machine. it only has a serial interface cable and the machine only has USB. We got a USB to Serial cable and we have the robot physically connected. However, the program needs a COM port specified to use with the robot...the options are COM1, COM2, COM3, and COM4. Can/How can a USB port be configured through a serial converter cable to be recognized as one of those COM ports? Thanks in advance.
Allen.
Question information
- Language:
- English Edit question
- Status:
- Answered
- Assignee:
- No assignee Edit question
- Last query:
- Last reply:
Revision history for this message
![]() |
#1 |
What is the brand and model of the USB-to-serial adapter?
Revision history for this message
![]() |
#2 |
Also, with the USB-to-serial adapter plugged into the computer's serial port, please open a Terminal window (Applications > Accessories > Terminal) and run the command:
lsusb
(To run a command, paste it in, or type it carefully, and then press enter.)
Then please copy all the text from the Terminal (Edit > Select All; Edit > Copy) and paste it here.
Revision history for this message
![]() |
#3 |
All it says on the adapter is "USB to RS-232" and "Made in China". There's no brand name on it.
Here is the result of the LSUSB command.
:~$ lsusb
Bus 005 Device 002: ID 04b4:0060 Cypress Semiconductor Corp.
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 002: ID 067b:2303 Prolific Technology, Inc. PL2303 Serial Port
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 004: ID 0ace:1215 ZyDAS WLA-54L 802.11bg
Bus 001 Device 002: ID 054c:021f Sony Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
I also did it with the -v switch with the following results (I've only included the ones with something there):
Bus 004 Device 002: ID 067b:2303 Prolific Technology, Inc. PL2303 Serial Port
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 1.10
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
idVendor 0x067b Prolific Technology, Inc.
idProduct 0x2303 PL2303 Serial Port
bcdDevice 3.00
iManufacturer 1
iProduct 2
iSerial 0
bNumConfigura
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 39
bNumInterfaces 1
bConfigurat
iConfiguration 0
bmAttributes 0x80
(Bus Powered)
MaxPower 100mA
Interface Descriptor:
bLength 9
bDescript
bInterfac
bAlternat
bNumEndpoints 3
bInterfac
bInterfac
bInterfac
iInterface 0
Endpoint Descriptor:
bLength 7
Transfer Type Interrupt
Synch Type None
Usage Type Data
bInterval 1
Endpoint Descriptor:
bLength 7
Transfer Type Bulk
Synch Type None
Usage Type Data
bInterval 0
Endpoint Descriptor:
bLength 7
Transfer Type Bulk
Synch Type None
Usage Type Data
bInterval 0
cannot read device status, Operation not permitted (1)
Bus 001 Device 004: ID 0ace:1215 ZyDAS WLA-54L 802.11bg
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 255 Vendor Specific Class
bDeviceSubClass 255 Vendor Specific Subclass
bDeviceProtocol 255 Vendor Specific Protocol
bMaxPacketSize0 64
idVendor 0x0ace ZyDAS
idProduct 0x1215 WLA-54L 802.11bg
bcdDevice 48.10
iManufacturer 16
iProduct 32
iSerial 0
bNumConfigura
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 46
bNumInterfaces 1
bConfigurat
iConfiguration 0
bmAttributes 0x80
(Bus Powered)
MaxPower 500mA
Interface Descriptor:
bLength 9
bDescript
bInterfac
bAlternat
bNumEndpoints 4
bInterfac
bInterfac
bInterfac
iInterface 0
Endpoint Descriptor:
bLength 7
Transfer Type Bulk
Synch Type None
Usage Type Data
bInterval 0
Endpoint Descriptor:
bLength 7
Transfer Type Bulk
Synch Type None
Usage Type Data
bInterval 0
Endpoint Descriptor:
bLength 7
Transfer Type Interrupt
Synch Type None
Usage Type Data
bInterval 1
Endpoint Descriptor:
bLength 7
Transfer Type Interrupt
Synch Type None
Usage Type Data
bInterval 1
can't get device qualifier: Operation not permitted
can't get debug descriptor: Operation not permitted
cannot read device status, Operation not permitted (1)
Bus 001 Device 002: ID 054c:021f Sony Corp.
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
idVendor 0x054c Sony Corp.
idProduct 0x021f
bcdDevice 3.15
iManufacturer 1
iProduct 2
iSerial 3
bNumConfigura
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 39
bNumInterfaces 1
bConfigurat
iConfiguration 0
bmAttributes 0x80
(Bus Powered)
MaxPower 500mA
Interface Descriptor:
bLength 9
bDescript
bInterfac
bAlternat
bNumEndpoints 2
bInterfac
bInterfac
bInterfac
iInterface 0
Endpoint Descriptor:
bLength 7
Transfer Type Bulk
Synch Type None
Usage Type Data
bInterval 1
Endpoint Descriptor:
bLength 7
Transfer Type Bulk
Synch Type None
Usage Type Data
bInterval 0
** UNRECOGNIZED: 07 21 07 e8 03 fe ff
can't get device qualifier: Operation not permitted
can't get debug descriptor: Operation not permitted
cannot read device status, Operation not permitted (1)
Thanks.
Allen.
Revision history for this message
![]() |
#4 |
All it says on the adapter is "USB to RS-232" and "Made in China". There's no brand name on it.
Here is the result of the LSUSB command.
:~$ lsusb
Bus 005 Device 002: ID 04b4:0060 Cypress Semiconductor Corp.
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 002: ID 067b:2303 Prolific Technology, Inc. PL2303 Serial Port
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 004: ID 0ace:1215 ZyDAS WLA-54L 802.11bg
Bus 001 Device 002: ID 054c:021f Sony Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
I also did it with the -v switch with the following results (I've only included the ones with something there):
Bus 004 Device 002: ID 067b:2303 Prolific Technology, Inc. PL2303 Serial Port
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 1.10
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
idVendor 0x067b Prolific Technology, Inc.
idProduct 0x2303 PL2303 Serial Port
bcdDevice 3.00
iManufacturer 1
iProduct 2
iSerial 0
bNumConfigura
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 39
bNumInterfaces 1
bConfigurat
iConfiguration 0
bmAttributes 0x80
(Bus Powered)
MaxPower 100mA
Interface Descriptor:
bLength 9
bDescript
bInterfac
bAlternat
bNumEndpoints 3
bInterfac
bInterfac
bInterfac
iInterface 0
Endpoint Descriptor:
bLength 7
Transfer Type Interrupt
Synch Type None
Usage Type Data
bInterval 1
Endpoint Descriptor:
bLength 7
Transfer Type Bulk
Synch Type None
Usage Type Data
bInterval 0
Endpoint Descriptor:
bLength 7
Transfer Type Bulk
Synch Type None
Usage Type Data
bInterval 0
cannot read device status, Operation not permitted (1)
Bus 001 Device 004: ID 0ace:1215 ZyDAS WLA-54L 802.11bg
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 255 Vendor Specific Class
bDeviceSubClass 255 Vendor Specific Subclass
bDeviceProtocol 255 Vendor Specific Protocol
bMaxPacketSize0 64
idVendor 0x0ace ZyDAS
idProduct 0x1215 WLA-54L 802.11bg
bcdDevice 48.10
iManufacturer 16
iProduct 32
iSerial 0
bNumConfigura
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 46
bNumInterfaces 1
bConfigurat
iConfiguration 0
bmAttributes 0x80
(Bus Powered)
MaxPower 500mA
Interface Descriptor:
bLength 9
bDescript
bInterfac
bAlternat
bNumEndpoints 4
bInterfac
bInterfac
bInterfac
iInterface 0
Endpoint Descriptor:
bLength 7
Transfer Type Bulk
Synch Type None
Usage Type Data
bInterval 0
Endpoint Descriptor:
bLength 7
Transfer Type Bulk
Synch Type None
Usage Type Data
bInterval 0
Endpoint Descriptor:
bLength 7
Transfer Type Interrupt
Synch Type None
Usage Type Data
bInterval 1
Endpoint Descriptor:
bLength 7
Transfer Type Interrupt
Synch Type None
Usage Type Data
bInterval 1
can't get device qualifier: Operation not permitted
can't get debug descriptor: Operation not permitted
cannot read device status, Operation not permitted (1)
Bus 001 Device 002: ID 054c:021f Sony Corp.
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
idVendor 0x054c Sony Corp.
idProduct 0x021f
bcdDevice 3.15
iManufacturer 1
iProduct 2
iSerial 3
bNumConfigura
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 39
bNumInterfaces 1
bConfigurat
iConfiguration 0
bmAttributes 0x80
(Bus Powered)
MaxPower 500mA
Interface Descriptor:
bLength 9
bDescript
bInterfac
bAlternat
bNumEndpoints 2
bInterfac
bInterfac
bInterfac
iInterface 0
Endpoint Descriptor:
bLength 7
Transfer Type Bulk
Synch Type None
Usage Type Data
bInterval 1
Endpoint Descriptor:
bLength 7
Transfer Type Bulk
Synch Type None
Usage Type Data
bInterval 0
** UNRECOGNIZED: 07 21 07 e8 03 fe ff
can't get device qualifier: Operation not permitted
can't get debug descriptor: Operation not permitted
cannot read device status, Operation not permitted (1)
Thanks.
Allen.
Revision history for this message
![]() |
#5 |
Sorry for submitting that twice.
Revision history for this message
![]() |
#6 |
Try this: http://
If that doesn't work, or you need help with those instructions, please post again.
Revision history for this message
![]() |
#7 |
Thanks. I went through the procedures there and had the desired results. However, the program that we're using to connect to the robot wants to send the programs through a COMM port (COMM1-COMM4). Is there a way to set up that USB to Serial to be recognized as a COMM port so that the program will correctly communicate through it? I posted this on the blog site too but it's been quite a few months since anyone's posted there too. Thanks.
Revision history for this message
![]() |
#8 |
Is the software you're using to interface with the robot Windows software, which you are running through Wine?
Revision history for this message
![]() |
#9 |
It is running through Wine.
Revision history for this message
![]() |
#10 |
From the instructions at http://
Generally speaking, Wine doesn't support USB devices. However, in this case, since the USB device is acting like a serial port, I suspect that this will work. Please post again if it doesn't, and we'll keep working on the problem.
Revision history for this message
![]() |
#11 |
Hello Allen,
I have the same setup (USB/Serial converter) and am experiencing similar problems with the setup of the Bioloid CM-5 controller.
I was wondering if you were able to configure your USB port so that the Bioloid software was able to recognize it?
I have so far still received errors like "Cannot connect to CM-5" (Behavior Control Programmer) or "Can not open COM1, 57600 bps" (Robot Terminal).
Thank you in advance!
Can you help with this problem?
Provide an answer of your own, or ask Allen Moore for more information if necessary.