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: Wed, 5 Nov 2014 19:36:20 -0800 [thread overview]
Message-ID: <20141106033620.GA16661@kroah.com> (raw)
In-Reply-To: <545ADCD8.3020702@grapecity.mn>
On Thu, Nov 06, 2014 at 10:28:40AM +0800, Batdelger.O wrote:
>
> >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?
> Actually, baud rate is 9600. 4800 was one of my attempts.
> >> )
> >>
> >> # 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?
> I think so. The Features section of device doc contains line: "Automatic hardware flow control with CTS/RTS
>". But I'm not sure. How to know exactly it does?.
You usually need to set this up on the device itself. The manual for
the device should say how to do this.
> >>
> >> 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.
> Device is working fine on windows 7. My simple python scripts is working
> fine without setting any options except port name (on win7).
Again, please try running minicom on Linux which sets up the line
settings in a "known manner" before blaming the kernel driver :)
thanks,
greg k-h
next prev parent reply other threads:[~2014-11-06 3:36 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
2014-11-06 2:28 ` Batdelger.O
2014-11-06 3:36 ` Greg KH [this message]
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=20141106033620.GA16661@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