All of lore.kernel.org
 help / color / mirror / Atom feed
From: Johan Hovold <jhovold@gmail.com>
To: Magnus <magnus-swe@telia.com>
Cc: linux-serial@vger.kernel.org, linux-usb@vger.kernel.org
Subject: Re: USB to Serial converter code pl2303
Date: Tue, 18 Feb 2014 10:09:46 +0100	[thread overview]
Message-ID: <20140218090946.GA1954@localhost> (raw)
In-Reply-To: <1392688665.7323.32.camel@mange>

[ Please make sure to CC the linux-usb list as well. ]

On Tue, Feb 18, 2014 at 02:57:45AM +0100, Magnus wrote:
> After plugging in the plexgear adapter into my linux boxes:
> Fedora 18, Debian 3.11.0-15-generic #25-Ubuntu and weezy it doesnt
> send any commands to the servo controller chip on the other side
> of the converter.
> 
> I can open the port /dev/ttyUSB0 and send to it with stty, but not
> a beep on the other side. I have also set the tty Baudrate manually to
> 2400 but this made no difference. My code does this as well including
> setting stopbit parity and so on.

First verify that the converter works by connecting it to a serial port
on your PC and using a terminal program such as minicom at 115200 baud
(and the same port settings including flow control) on both ends.

Also make sure you got the wiring right (e.g. use a null-modem cable).

> Some data i get from Linux and Plexgear converter follows:
> 
> $ lsmod | grep pl2303
> pl2303                 18527  0 
> usbserial              38603  1 pl2303
> 
> 
> $ lsusb
> Bus 005 Device 007: ID 067b:2303 Prolific Technology, Inc.
> PL2303 Serial Port
> 
> $ lsusb -v
> 
> Bus 005 Device 007: ID 067b:2303 Prolific Technology, Inc.
> PL2303 Serial Port
> 
> Couldn't open device, some information will be missing
> (My comment... hmm, but it can read from it ?)..
> 
> 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 
>   bNumConfigurations      1
>   Configuration Descriptor:
>     bLength                 9
>     bDescriptorType         2
>     wTotalLength           39
>     bNumInterfaces          1
>     bConfigurationValue     1
>     iConfiguration          0 
>     bmAttributes         0x80
>       (Bus Powered)
>     MaxPower              100mA
>     Interface Descriptor:
>       bLength                 9
>       bDescriptorType         4
>       bInterfaceNumber        0
>       bAlternateSetting       0
>       bNumEndpoints           3
>       bInterfaceClass       255 Vendor Specific Class
>       bInterfaceSubClass      0 
>       bInterfaceProtocol      0 
>       iInterface              0 
>       Endpoint Descriptor:
>         bLength                 7
>         bDescriptorType         5
>         bEndpointAddress     0x81  EP 1 IN
>         bmAttributes            3
>           Transfer Type            Interrupt
>           Synch Type               None
>           Usage Type               Data
>         wMaxPacketSize     0x000a  1x 10 bytes
>         bInterval               1
>       Endpoint Descriptor:
>         bLength                 7
>         bDescriptorType         5
>         bEndpointAddress     0x02  EP 2 OUT
>         bmAttributes            2
>           Transfer Type            Bulk
>           Synch Type               None
>           Usage Type               Data
>         wMaxPacketSize     0x0040  1x 64 bytes
>         bInterval               0
>       Endpoint Descriptor:
>         bLength                 7
>         bDescriptorType         5
>         bEndpointAddress     0x83  EP 3 IN
>         bmAttributes            2
>           Transfer Type            Bulk
>           Synch Type               None
>           Usage Type               Data
>         wMaxPacketSize     0x0040  1x 64 bytes
>         bInterval               0
> 
> I can code some, but i dont know where to start so any
> help on this is highly appreciated.
> 
> When i google to find info on adapters i read that
> "bMaxPacketSize0 64" indicates that its a counterfeit product
> but i paid 250 Swedish for it and that not very cheap for a
> univeristy student i think.

This device is likely not a clone, but should be supported by the pl2303
driver either way (at least at 115200 baud).

Good luck,
Johan

  reply	other threads:[~2014-02-18  9:10 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-18  1:57 USB to Serial converter code pl2303 Magnus
2014-02-18  9:09 ` Johan Hovold [this message]
2014-02-19 16:44   ` Magnus
2014-02-19 17:00     ` Johan Hovold
2014-02-19 17:05       ` Karsten Malcher
     [not found]         ` <5304E472.2000203-QdlBTFngBEMsCylrc8G9yg@public.gmane.org>
2014-02-19 17:14           ` Johan Hovold
2014-02-19 17:21             ` Karsten Malcher
2014-02-20 18:19             ` Frank Schäfer
     [not found]               ` <53064721.3080905-gM/Ye1E23mwN+BqQ9rBEUg@public.gmane.org>
2014-02-20 20:02                 ` Johan Hovold
2014-02-21  8:47               ` Karsten Malcher

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20140218090946.GA1954@localhost \
    --to=jhovold@gmail.com \
    --cc=linux-serial@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=magnus-swe@telia.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.