Linux Serial subsystem development
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: "Batdelger.O" <david.batdelger@grapecity.mn>
Cc: linux-serial@vger.kernel.org
Subject: Re: Fwd: Fwd: Re: pl2303 linux driver does not work
Date: Tue, 4 Nov 2014 20:29:55 -0800	[thread overview]
Message-ID: <20141105042955.GA10613@kroah.com> (raw)
In-Reply-To: <5459A354.2000006@grapecity.mn>

On Wed, Nov 05, 2014 at 12:11:00PM +0800, Batdelger.O wrote:
> 
> Thank you for your quick response.
> It's  just simple python code. I'm not sure if flow control is correct. I
> also used gtkterm and tried by every option.  I'm new at usbserial devices.
> How to know how should it be?
> 
>    import time
>    import serial
>    import sys
> 
>    ser = serial.Serial(
>         port='/dev/ttyUSB0',
>         baudrate=4800,
>         parity=serial.PARITY_ODD,
>         stopbits=serial.STOPBITS_ONE,
>         bytesize=serial.EIGHTBITS,
>         # timeout=0

That's a slow baud rate, do you mean that slow?

>    )
> 
>    # RTS 0 DTR 1. not sure it's correct one. I tried by reverse.
>    ser.setRTS(False)
>    ser.setDTR(True)

Does your device support hardware flow control?


> 
> 
>    print ser.isOpen()
> 
>    ON="\x1B\x5D"
>    ser.write(ON)
>    ser.flushOutput()
>    print "after write"
>    # read = ser.read()
>    # sys.stdout.write("RECEIVED:" + read + "\n")
>    ser.close()

Try using minicom to see if you can properly connect to your device
first, before trying to write your own code from "scratch", to determine
that the device works.

greg k-h

  reply	other threads:[~2014-11-05  4:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <5459A26A.2080204@grapecity.mn>
2014-11-05  4:11 ` Fwd: Fwd: Re: pl2303 linux driver does not work Batdelger.O
2014-11-05  4:29   ` Greg KH [this message]
2014-11-06  2:28     ` Batdelger.O
2014-11-06  3:36       ` Greg KH
2014-11-05 19:58         ` Batdelger.O

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=20141105042955.GA10613@kroah.com \
    --to=greg@kroah.com \
    --cc=david.batdelger@grapecity.mn \
    --cc=linux-serial@vger.kernel.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox