> On 22 Dec 2022, at 17:09, Patrick EGLOFF wrote:
>
> Hi all,
>
> I use Python 3.10.9 and Pyserial 3.5 on a Win10 machine.
>
> I'm sending datas via an USB port to a device that accept commands in the
> form of : cmd;
> The device receives and reacts to the commands sent, and it should repl
Thanks Rob.
Yes I ended up with a read(1) and use a field count and a few other checks to
make sure I don't get a partial record. Serial is the "best of times and worst
of times". Sure beats dealing with USB enumeration, power hungry ethernet
processors and a lot of other stuff. I can still "s
On 07/18/2017 12:53 PM, FS wrote:
Thank you for your response Andre. I had tried some code like that in the
document but it did not seem to work. However ever leaving my terminal for a
time the code eventually wrote out the records so apparently there is some very
deep buffering going on here.
Thank you for your response Andre. I had tried some code like that in the
document but it did not seem to work. However ever leaving my terminal for a
time the code eventually wrote out the records so apparently there is some very
deep buffering going on here. A little more searching on the web
Just take a look into the documentation:
https://docs.python.org/3/library/io.html#io.TextIOWrapper
And in the example of Pyserial:
http://pyserial.readthedocs.io/en/latest/shortintro.html#eol
I think it shold be:
sio = io.TextIOWrapper(io.BufferedRWPair(ser, ser),
newline='yourline_ending')
But
On 2016-12-11 21:29, Wanderer wrote:
On Sunday, December 11, 2016 at 12:52:04 PM UTC-5, MRAB wrote:
On 2016-12-11 16:28, Wanderer wrote:
> I have an outdoor thermometer that transmits to an indoor receiver at 433Mhz.
I also have a 433Mhz USB serial port jig from a TI development tool. I would l
Wanderer writes:
> I also have a 433Mhz USB serial port jig from a TI development
> tool The TI USB port registers as a COM port that I can access
> with pySerial.
If the TI jig has 433 mhz (LORA?) at one end and serial at the other,
you have to find the port parameters in the docs for the TI
On Sunday, December 11, 2016 at 12:52:04 PM UTC-5, MRAB wrote:
> On 2016-12-11 16:28, Wanderer wrote:
> > I have an outdoor thermometer that transmits to an indoor receiver at
> > 433Mhz. I also have a 433Mhz USB serial port jig from a TI development
> > tool. I would like to use the TI USB seria
On 2016-12-11 16:28, Wanderer wrote:
I have an outdoor thermometer that transmits to an indoor receiver at 433Mhz. I
also have a 433Mhz USB serial port jig from a TI development tool. I would like
to use the TI USB serial port to capture the temperature information. The TI
USB port registers a
On 2016-10-16, Michael Okuntsov wrote:
> is there a way, other than time.sleep(), to be sure that the command
> sent through a serial port has been fully executed?
If the remote device doesn't send a response telling you it's done
executing the command, then there is no way to know when that has
On Saturday, October 15, 2016 at 10:14:18 PM UTC-6, Michael Okuntsov wrote:
> Hello,
> is there a way, other than time.sleep(), to be sure that the command
> sent through a serial port has been fully executed? I'm interested
> specifically in SCPI commands in VA-meters such as Keithley and Tektro
Rob Gaddi wrote:
>So, this is odd. I'm running Ubuntu 14.04, and my system did a kernel
>upgrade from the repository from 3.13.0-63-generic to 3.13.0-65-generic.
>And pyserial (2.7, installed through pip) stopped working.
When KDE's "Plasma 5" appeared with Kubuntu 15.04, I found it to be to
In a message of Tue, 06 Oct 2015 21:31:02 -, Grant Edwards writes:
>On 2015-10-03, Laura Creighton wrote:
>
>> https://bugs.launchpad.net/ubuntu/+source/linux-lts-trusty/+bug/1501345
>> seems to be about a whole lot of serial ports to me, not just FTDI
>
>We just ran into the OP's problem wh
On Tue, 06 Oct 2015 21:31:02 +, Grant Edwards wrote:
> On 2015-10-03, Laura Creighton wrote:
>
>> https://bugs.launchpad.net/ubuntu/+source/linux-lts-trusty/
+bug/1501345
>> seems to be about a whole lot of serial ports to me, not just FTDI
>
> We just ran into the OP's problem where I wo
On 2015-10-03, Laura Creighton wrote:
> https://bugs.launchpad.net/ubuntu/+source/linux-lts-trusty/+bug/1501345
> seems to be about a whole lot of serial ports to me, not just FTDI
We just ran into the OP's problem where I work: Ununtu kernel updated
and all serial ports stopped working (it is
On Sat, 03 Oct 2015 11:12:28 +0200, Laura Creighton wrote:
> In a message of Sat, 03 Oct 2015 11:07:04 +0200, Laura Creighton writes:
>>In a message of Fri, 02 Oct 2015 22:36:23 -, Rob Gaddi writes:
>>>So, this is odd. I'm running Ubuntu 14.04, and my system did a kernel
>>>upgrade from the r
In a message of Sat, 03 Oct 2015 08:38:53 -0600, Michael Torrie writes:
>On 10/03/2015 03:19 AM, Laura Creighton wrote:
>> With better searching, I find this bug.
>> https://bugs.launchpad.net/ubuntu/+source/linux-lts-trusty/+bug/1501345
>>
>> Looks like that's the real one.
>
>This ubuntu bug and
On 10/03/2015 03:19 AM, Laura Creighton wrote:
> With better searching, I find this bug.
> https://bugs.launchpad.net/ubuntu/+source/linux-lts-trusty/+bug/1501345
>
> Looks like that's the real one.
This ubuntu bug and the other bug you mention seem to be about FTDI
devices. Rob said in his origi
With better searching, I find this bug.
https://bugs.launchpad.net/ubuntu/+source/linux-lts-trusty/+bug/1501345
Looks like that's the real one.
Laura
--
https://mail.python.org/mailman/listinfo/python-list
In a message of Sat, 03 Oct 2015 11:07:04 +0200, Laura Creighton writes:
>In a message of Fri, 02 Oct 2015 22:36:23 -, Rob Gaddi writes:
>>So, this is odd. I'm running Ubuntu 14.04, and my system did a kernel
>>upgrade from the repository from 3.13.0-63-generic to 3.13.0-65-generic.
>>And p
In a message of Fri, 02 Oct 2015 22:36:23 -, Rob Gaddi writes:
>So, this is odd. I'm running Ubuntu 14.04, and my system did a kernel
>upgrade from the repository from 3.13.0-63-generic to 3.13.0-65-generic.
>And pyserial (2.7, installed through pip) stopped working.
>
>Specifically, when I
On 2015-10-02, Rob Gaddi wrote:
> Also, who do I try to report this one to?
I'd try here:
https://github.com/pyserial/pyserial/issues
--
https://mail.python.org/mailman/listinfo/python-list
On Thu, Sep 17, 2015 at 11:26 PM, pozz wrote:
> How to have a non-blocking write?
>
> Maybe the problem happens when port 1 thread is in .read() (it blocks for 1
> second) and port 2 thread tries to write one byte (that was just received)
> to port 1.
I'm not sure, as I've never worked with seria
Il 17/09/2015 11:42, Chris Angelico ha scritto:
On Thu, Sep 17, 2015 at 7:28 PM, pozz wrote:
At startup I open the ports and create and start a thread to manage the
receiving. When a byte is received, I call the .write() method for all the
other ports.
It works, but sometimes it seems to block
Il 17/09/2015 15:04, Dennis Lee Bieber ha scritto:
On Thu, 17 Sep 2015 12:00:08 + (UTC), alister
declaimed the following:
I can see the data being transmitted snowballing & running away in a +ve
feedback loop very easily.
Especially if a few of the remote devices are configured
Il 17/09/2015 14:00, alister ha scritto:
I would like to know more about how many serial ports are connected
One real serial port and two virtual serial ports, created by com0com
(it's a free virtual serial port for Windows).
what the equipment they are connected to does and expects.
Ra
On Thu, 17 Sep 2015 11:28:04 +0200, pozz wrote:
> I'm trying to create a simple program in Python that opens N serial
> ports (through pyserial) and forward every byte received on one of those
> ports to the other ports.
>
> At startup I open the ports and create and start a thread to manage the
On Thu, Sep 17, 2015 at 7:28 PM, pozz wrote:
> At startup I open the ports and create and start a thread to manage the
> receiving. When a byte is received, I call the .write() method for all the
> other ports.
>
> It works, but sometimes it seems to block. I think I haven't used correctly
> the t
Ehm sorry for the neverending spam, anyway I tried from my raspberry pi and it
works there:
root@pi:/home/pi# python3 ./test.py
b's'
b'w'
b' '
b'o'
b'0'
b'1'
b' '
b'+'
b' '
b'C'
b'o'
b'm'
b'm'
b'a'
b'n'
b'd'
b' '
b'O'
b'K'
b'\r'
b'\n'
Since I need it to work on the rpi and I was using Mint only
Il giorno sabato 1 novembre 2014 16:04:06 UTC+1, Dario ha scritto:
> BUT.. plot twist: in Windows XP, the very same python code and usb adapter
> are working just right (python 2.7 and pySerial 2.7). Also with c#, no issues.
I compared the behaviour of mono and python (2.7 and 3.3) on the same h
Il giorno venerdì 31 ottobre 2014 19:00:26 UTC+1, Dennis Lee Bieber ha scritto:
> Didn't quite answer my question. If the comm line is using remote
I understand your point, I didn't mention but I also tried sending one char at
a time and listening at the same time, nothing changed.
BUT.. plot
Il giorno giovedì 30 ottobre 2014 23:57:40 UTC+1, Dennis Lee Bieber ha scritto:
> >sw o01 + <--- I send this
> How do you "send this"...
I just type or paste it in miniterm and hit return. Miniterm sends the return
as CR, but it also works with CRLF.
> >sw o01 + Command OK <--- device does wh
On 19/10/2014 16:06, Grant Edwards wrote:
On 2014-10-18, Nagy L?szl? Zsolt wrote:
Strangely, pyserial will accept the number 0, but then it tries to open
a device that exists on Linux only...
I'm sure Chris would be happy to accept a patch fixing that problem.
Sadly to some people a patch
On 2014-10-18, Nagy L?szl? Zsolt wrote:
> Strangely, pyserial will accept the number 0, but then it tries to open
> a device that exists on Linux only...
I'm sure Chris would be happy to accept a patch fixing that problem.
--
Grant
--
https://mail.python.org/mailman/listinfo/python-list
The port parameter of serial.Serial should be /dev/ttyu0 instead of
COM1, and /dev/ttyu1 instead of COM2.
Strangely, pyserial will accept the number 0, but then it tries to open
a device that exists on Linux only...
Anyway, problem solved.
--
https://mail.python.org/mailman/listinfo/python-li
On 1/1/2014 1:48 AM, Chris Angelico wrote:
On Wed, Jan 1, 2014 at 5:39 PM, Travis McGee wrote:
What OS? If Windows, did you install the -py3k version for 3.x?
Anyway, I finally got it installed, but when I try to use a statement of the
sort ser.write("string") I get an exception which seems
Travis McGee wrote:
> I've been working with a simple serial device that attaches to a USB
> port. It takes as commands short strings.
>
> I wanted to use PySerial under Python 3, and, of course had the Devil's
> own time getting it installed and working since everything is geared
> towards Pytho
On Wed, Jan 1, 2014 at 5:39 PM, Travis McGee wrote:
> Anyway, I finally got it installed, but when I try to use a statement of the
> sort ser.write("string") I get an exception which seems to imply that the
> argument needs to be an integer, rather than a string.
Quoting the full exception would
On Tue, Dec 31, 2013 at 10:39 PM, Travis McGee wrote:
> Anyway, I finally got it installed, but when I try to use a statement of the
> sort ser.write("string") I get an exception which seems to imply that the
> argument needs to be an integer, rather than a string.
You will get the most help if y
"Roel Schroeven" wrote in message
news:mailman.1618.1340910525.4697.python-l...@python.org...
> Temia Eszteri schreef:
>> Actually, I believe someone in an earlier thread in the newsgroup or
>> elsewhere pointed out that serial ports automatically open under
>> Windows. I'd have to look it back
"Grant Edwards" wrote in message
news:jshotj$s55$1...@reader1.panix.com...
> On 2012-06-28, Adam wrote:
>
>> Obviously pySerial considers the serial port open
>
> Because it's already been opened by the Python program.
>
>> and will not open an already open serial port.
>
> Pyserial will happil
Temia Eszteri schreef:
Actually, I believe someone in an earlier thread in the newsgroup or
elsewhere pointed out that serial ports automatically open under
Windows. I'd have to look it back up when I have the time, which I
don't have at the moment, unfortunately.
That doesn't have anything to
On 2012-06-28, Adam wrote:
> Obviously pySerial considers the serial port open
Because it's already been opened by the Python program.
> and will not open an already open serial port.
Pyserial will happily try if you call the open() of a port that's
already open, but Windows will return an err
"Grant Edwards" wrote in message
news:jsg4o8$o4p$1...@reader1.panix.com...
> On 2012-06-27, Adam wrote:
>>
>>> Actually, I believe someone in an earlier thread in the newsgroup or
>>> elsewhere pointed out that serial ports automatically open under
>>> Windows. I'd have to look it back up when
On 2012-06-27, Adam wrote:
>
>> Actually, I believe someone in an earlier thread in the newsgroup or
>> elsewhere pointed out that serial ports automatically open under
>> Windows. I'd have to look it back up when I have the time, which I
>> don't have at the moment, unfortunately.
What they're r
"Temia Eszteri" wrote in message
news:ra2nu7h75720i75ijhabg12dngrab75...@4ax.com...
> On Wed, 27 Jun 2012 22:18:59 + (UTC), Grant Edwards
> wrote:
>
>>> Can you post a small example showing what you're doing?
>>
>>The best way to get help is to write as small a program as possible
>>that de
On Wed, 27 Jun 2012 22:18:59 + (UTC), Grant Edwards
wrote:
>> Can you post a small example showing what you're doing?
>
>The best way to get help is to write as small a program as possible
>that demonstrates the problem, and post it. I'll help you get
>started...
>
>Does this program work?
>
On 2012-06-27, Grant Edwards wrote:
> On 2012-06-27, Adam wrote:
>> "Grant Edwards" wrote:
>>> Why do you need to open it a second time?
>>
>> As far as I can tell, the wireless hardware connected to the
>> USB-to-serial converter is receiving data (which may have the serial
>> port open?). I
On 2012-06-27, Adam wrote:
> "Grant Edwards" wrote:
>> On 2012-06-27, Adam wrote:
>>
>>> The Python script needed a call to ser.close() before ser.open() in
>>> order to work.
>>
>> IOW, the port opened OK, but when you tried to open it a second time
>> without closing it first, _that's_ when th
"Grant Edwards" wrote in message
news:jsftah$bb5$1...@reader1.panix.com...
> On 2012-06-27, Adam wrote:
>
>> The Python script needed a call to ser.close() before ser.open() in
>> order to work.
>
> IOW, the port opened OK, but when you tried to open it a second time
> without closing it first,
On 2012-06-27, Adam wrote:
> The Python script needed a call to ser.close() before ser.open() in
> order to work.
IOW, the port opened OK, but when you tried to open it a second time
without closing it first, _that's_ when the .open() call failed.
That's a restriction built in to Win32. You ca
"Paul" wrote in message
news:jsfhv2$ta9$1...@dont-email.me...
> Adam wrote:
>
>>
>> This is a tough one.
>
> Try
>
>handle -a > allhand.txt
>
> Then open the allhand.txt with Notepad and look for interesting entries.
>
> ***
>
> I tested right now, and first opened a session in HyperTerm
Adam wrote:
This is a tough one.
Try
handle -a > allhand.txt
Then open the allhand.txt with Notepad and look for interesting entries.
***
I tested right now, and first opened a session in HyperTerminal with one
of my USB to serial adapters. The second serial adapter, is connect to
"Paul" wrote in message
news:jsfatv$djt$1...@dont-email.me...
> Adam wrote:
>> "Paul" wrote in message
>> news:jseu9c$sp3$1...@dont-email.me...
>>> Adam wrote:
"John Nagle" wrote in message
news:jse604$1cq$1...@dont-email.me...
> On 6/26/2012 9:12 PM, Adam wrote:
>> Host OS
Adam wrote:
"Paul" wrote in message
news:jseu9c$sp3$1...@dont-email.me...
Adam wrote:
"John Nagle" wrote in message
news:jse604$1cq$1...@dont-email.me...
On 6/26/2012 9:12 PM, Adam wrote:
Host OS:Ubuntu 10.04 LTS
Guest OS:Windows XP Pro SP3
I am able to open port COM4 with Termina
"Paul" wrote in message
news:jseu9c$sp3$1...@dont-email.me...
> Adam wrote:
>> "John Nagle" wrote in message
>> news:jse604$1cq$1...@dont-email.me...
>>> On 6/26/2012 9:12 PM, Adam wrote:
Host OS:Ubuntu 10.04 LTS
Guest OS:Windows XP Pro SP3
I am able to open po
On 2012-06-27, David H. Lipman wrote:
> From: "Adam"
>> "John Nagle" wrote in message
>> news:jse604$1cq$1...@dont-email.me...
>>> On 6/26/2012 9:12 PM, Adam wrote:
Host OS:Ubuntu 10.04 LTS
Guest OS:Windows XP Pro SP3
I am able to open port COM4 with Terminal emulato
From: "Adam"
"John Nagle" wrote in message
news:jse604$1cq$1...@dont-email.me...
On 6/26/2012 9:12 PM, Adam wrote:
Host OS:Ubuntu 10.04 LTS
Guest OS:Windows XP Pro SP3
I am able to open port COM4 with Terminal emulator.
So, what can cause PySerial to generate the following error
Adam wrote:
"John Nagle" wrote in message
news:jse604$1cq$1...@dont-email.me...
On 6/26/2012 9:12 PM, Adam wrote:
Host OS:Ubuntu 10.04 LTS
Guest OS:Windows XP Pro SP3
I am able to open port COM4 with Terminal emulator.
So, what can cause PySerial to generate the following error ...
"John Nagle" wrote in message
news:jse604$1cq$1...@dont-email.me...
> On 6/26/2012 9:12 PM, Adam wrote:
>> Host OS:Ubuntu 10.04 LTS
>> Guest OS:Windows XP Pro SP3
>>
>>
>> I am able to open port COM4 with Terminal emulator.
>>
>> So, what can cause PySerial to generate the following erro
On 6/26/2012 9:12 PM, Adam wrote:
Host OS:Ubuntu 10.04 LTS
Guest OS:Windows XP Pro SP3
I am able to open port COM4 with Terminal emulator.
So, what can cause PySerial to generate the following error ...
C:\Wattcher>python wattcher.py
Traceback (most recent call last):
File "wattche
On Feb 4, 11:47 pm, Jean Dupont wrote:
> I need to set the following options I found in a Perl-script in Python for
> serial communication with a device (a voltmeter):
>
> $port->handshake("none");
> $port->rts_active(0);
> $port->dtr_active(1);
>
> I have thus far the following statements but I
On Sat, Feb 4, 2012 at 4:47 AM, Jean Dupont wrote:
> I need to set the following options I found in a Perl-script in Python for
> serial communication with a device (a voltmeter):
>
> $port->handshake("none");
> $port->rts_active(0);
> $port->dtr_active(1);
>
> I have thus far the following stat
On Mar 20, 9:06 pm, "Littlefield, Tyler" wrote:
> >The windows msi install fails saying there is no python install found
> >in the registry. Is there a workaround for this? Can I edit the
> >registry and manually enter the information?
> I've came to realize that the 64-bit version of python do
On Mar 20, 9:06 pm, "Littlefield, Tyler" wrote:
> >The windows msi install fails saying there is no python install found
> >in the registry. Is there a workaround for this? Can I edit the
> >registry and manually enter the information?
> I've came to realize that the 64-bit version of python do
>The windows msi install fails saying there is no python install found
>in the registry. Is there a workaround for this? Can I edit the
>registry and manually enter the information?
I've came to realize that the 64-bit version of python does not work
with 32-bit modules in terms of the installer
On 3/20/2011 8:46 PM, Manatee wrote:
The windows msi install fails saying there is no python install found
in the registry. Is there a workaround for this? Can I edit the
registry and manually enter the information?
I am running Python 2.71
There is no traceback, the installation fails immediat
The best thing I've found is this:
http://eli.thegreenplace.net/2009/05/29/storing-blobs-in-a-sqlite-db-with-pythonpysqlite/
On Mon, May 17, 2010 at 5:05 PM, jon vs. python wrote:
> Hi,
> I'm trying to store frames received via serial port (using Pyserial) into a
> sqlite database (using Pysqlit
On Mar 10, 1:07 pm, "Gabriel Genellina"
wrote:
> En Tue, 09 Mar 2010 12:01:22 -0300, kishore
> escribió:
>
>
>
>
>
> >> > Iam using python 2.5.4
> >> > pyserial 2.4
> >> > pywin32-214
> >> > on windows 7
>
> >> > i hav a small test script written to query a serial device (arduino)
> >> > and get
En Tue, 09 Mar 2010 12:01:22 -0300, kishore
escribió:
> Iam using python 2.5.4
> pyserial 2.4
> pywin32-214
> on windows 7
> i hav a small test script written to query a serial device (arduino)
> and get back reply appropriately
Thanks for your response
i tried closing idle and the followi
Hi Kishore,
Have you tried "ser=serial.Serial(port='COM2', baudrate=9600)" instead
of "port='\\.\COM2'"?
Also, I'd suggest you temporarily define some other parameters that
now you're leaving to default values. From the documentation of
pyserial:
readline(size=None, eol='\n')
You're sure that y
On Mar 9, 8:01 pm, kishore wrote:
> On Mar 9, 2:19 pm, News123 wrote:
>
>
>
> > Hi,
>
> > kishore wrote:
> > > hello there
>
> > > Iam using python 2.5.4
> > > pyserial 2.4
> > > pywin32-214
>
> > > on windows 7
>
> > > i hav a small test script written to query a serial device (arduino)
> > > a
On Mar 9, 8:01 pm, kishore wrote:
> On Mar 9, 2:19 pm, News123 wrote:
>
>
>
> > Hi,
>
> > kishore wrote:
> > > hello there
>
> > > Iam using python 2.5.4
> > > pyserial 2.4
> > > pywin32-214
>
> > > on windows 7
>
> > > i hav a small test script written to query a serial device (arduino)
> > > a
On Mar 9, 2:19 pm, News123 wrote:
> Hi,
>
>
>
> kishore wrote:
> > hello there
>
> > Iam using python 2.5.4
> > pyserial 2.4
> > pywin32-214
>
> > on windows 7
>
> > i hav a small test script written to query a serial device (arduino)
> > and get back reply appropriately
>
> > file: test.py
>
Hi,
kishore wrote:
> hello there
>
> Iam using python 2.5.4
> pyserial 2.4
> pywin32-214
>
> on windows 7
>
>
> i hav a small test script written to query a serial device (arduino)
> and get back reply appropriately
>
>
>
> file: test.py
>
> import serial
> print 'hi'
> ser=serial.Ser
Steven Woody wrote:
> 2010/1/16 John Nagle :
>> Grant Edwards wrote:
>>> On 2010-01-11, Steven Woody wrote:
>>>
I am using pyserial. But I always get the local echo after I
write some characters onto serial port
>>> I really doubt you're getting a local echo. Is the data coming
>>> out
2010/1/16 John Nagle :
> Grant Edwards wrote:
>>
>> On 2010-01-11, Steven Woody wrote:
>>
>>> I am using pyserial. But I always get the local echo after I
>>> write some characters onto serial port
>>
>> I really doubt you're getting a local echo. Is the data coming
>> out the serial port? Do y
Grant Edwards wrote:
On 2010-01-11, Steven Woody wrote:
I am using pyserial. But I always get the local echo after I
write some characters onto serial port
I really doubt you're getting a local echo. Is the data coming
out the serial port? Do you get the echo if you disconnect the
serial
On 2010-01-11, Steven Woody wrote:
> I am using pyserial. But I always get the local echo after I
> write some characters onto serial port
I really doubt you're getting a local echo. Is the data coming
out the serial port? Do you get the echo if you disconnect the
serial cable?
> and I find
On Mon, 11 Jan 2010 23:27:03 +0800, Steven Woody wrote:
> I am using pyserial. But I always get the local echo after I write
> some characters onto serial port and I find no way to disable this
> behavior. When I say 'local echo', I mean the next read operation will
> get characters that was just
Steven Woody wrote:
> Hi,
>
> I am using pyserial. But I always get the local echo after I write
> some characters onto serial port and I find no way to disable this
> behavior. When I say 'local echo', I mean the next read operation will
> get characters that was just write to the same port.
>
On Dec 11, 7:58 pm, Grant Edwards wrote:
> On 2009-12-11, Grant Edwards wrote:
>
> > On 2009-12-11, ObservantP wrote:
> >> need help. newbie. pyserial and dot matrix printer. issue-
> >> escape codes arrive at printer ( verified from hex dump) but
> >> do not get applied.
>
> > What you're sayin
On 2009-12-11, Grant Edwards wrote:
> On 2009-12-11, ObservantP wrote:
>> need help. newbie. pyserial and dot matrix printer. issue-
>> escape codes arrive at printer ( verified from hex dump) but
>> do not get applied.
>
> What you're saying is your printer isn't working correctly.
BTW, I (amon
On 2009-12-11, ObservantP wrote:
> need help. newbie. pyserial and dot matrix printer.
> issue- escape codes arrive at printer ( verified from hex dump) but do
> not get applied.
What you're saying is your printer isn't working correctly.
> printer make/model STAR POS printer SP500. oddly, prin
On Nov 30, 7:41 pm, Grant Edwards wrote:
> On 2009-11-30, a b wrote:
>
> > I have a pain in the a** problem with pyserial- it works 90%
> > of time but on the 10% of time it thorows and termios.error
> > exception with the value (5, 'Input/output error') and i
> > cannot get rid of it :(
>
> Soun
On 2009-11-30, a b wrote:
> I have a pain in the a** problem with pyserial- it works 90%
> of time but on the 10% of time it thorows and termios.error
> exception with the value (5, 'Input/output error') and i
> cannot get rid of it :(
Sounds like faulty converter or a bug in the device driver to
a b wrote:
> I have a pain in the a** problem with pyserial- it works 90% of time
> but on the 10% of time it thorows and termios.error exception with the
> value (5, 'Input/output error') and i cannot get rid of it :(
> The system works as follows:
> A device sends out rs485 data -> rs485 to rs23
In article <4af71b7e$0$1645$742ec...@news.sonic.net>,
John Nagle wrote:
> I have an application running with pyserial talking to a USB to serial
> converter on a Linux EeePC 2G Surf. This works. Until the lid on the PC is
> closed and the device suspends.
>
> The application has /dev/t
On Sat, Oct 24, 2009 at 4:53 PM, John Nagle wrote:
> Gabriel Genellina wrote:
>
>> En Fri, 23 Oct 2009 20:56:21 -0300, Ronn Ross
>> escribió:
>>
>>
>> I have tried setting the baud rate with no success. Also I'm using port
>>> #2
>>> because I"m using a usb to serial cable.
>>>
>>
>> Note that
Gabriel Genellina wrote:
En Fri, 23 Oct 2009 20:56:21 -0300, Ronn Ross
escribió:
I have tried setting the baud rate with no success. Also I'm using
port #2
because I"m using a usb to serial cable.
Note that Serial(2) is known as COM3 in Windows, is it ok?
Do you have a machine with a C
Yes, with the serial to usb adapter is located on COM3. I have been able to
use puTTY to get into the port and shoot commands at the device, but when I
try to use python I get 'You don't have permissions".
On Sat, Oct 24, 2009 at 12:50 AM, Gabriel Genellina
wrote:
> En Fri, 23 Oct 2009 20:56:21 -
En Fri, 23 Oct 2009 20:56:21 -0300, Ronn Ross
escribió:
I have tried setting the baud rate with no success. Also I'm using port
#2
because I"m using a usb to serial cable.
Note that Serial(2) is known as COM3 in Windows, is it ok?
--
Gabriel Genellina
--
http://mail.python.org/mailman/l
I have tried setting the baud rate with no success. Also I'm using port #2
because I"m using a usb to serial cable.
On Fri, Oct 23, 2009 at 7:51 PM, Chris Rebert wrote:
> On Thu, Oct 22, 2009 at 4:43 PM, Ronn Ross wrote:
> > I'm using pySerial to connect to a serial port (rs232) on a windows xp
On Thu, Oct 22, 2009 at 4:43 PM, Ronn Ross wrote:
> I'm using pySerial to connect to a serial port (rs232) on a windows xp
> machine. I'm using python interactive interpretor to interact with the
> device. I type the following:
> import serial
> ser = serial.Serial(2)
> ser.write("command")
>
> Bu
I'm using pySerial to connect to a serial port (rs232) on a windows xp
machine. I'm using python interactive interpretor to interact with the
device. I type the following:
import serial
ser = serial.Serial(2)
ser.write("command")
But this does nothing to the control. I have been able to connect vi
En Tue, 20 Oct 2009 18:02:03 -0300, Rodrigo
escribió:
Maybe this is not a bug at all, but i have installed python2.5. 3.01
and 3.1.1. In python 2.5 ser. write('this is a string') works just
fine.
On the other hand, with 3.01 and 3.1.1 (pyserial 2.5 rc1) when i do a
ser.write('this is a string
Rodrigo schrieb:
Maybe this is not a bug at all, but i have installed python2.5. 3.01
and 3.1.1. In python 2.5 ser. write('this is a string') works just
fine.
On the other hand, with 3.01 and 3.1.1 (pyserial 2.5 rc1) when i do a
ser.write('this is a string') i get the following error"
import se
oyinbo55 wrote:
On Oct 1, 11:36 am, "Richard Brodie" wrote:
"oyinbo55" wrote in message
news:2feb36fc-106c-4d7c-a697-db59971dc...@a7g2000yqo.googlegroups.com...
Using the standard 19200 baud results in gobbledegook from the
multimeter.
You aren't going to notice a 0.1% clock skew within 1
On Oct 1, 11:36 am, "Richard Brodie" wrote:
> "oyinbo55" wrote in message
>
> news:2feb36fc-106c-4d7c-a697-db59971dc...@a7g2000yqo.googlegroups.com...
>
> > Using the standard 19200 baud results in gobbledegook from the
> > multimeter.
>
> You aren't going to notice a 0.1% clock skew within 1 byt
"oyinbo55" wrote in message
news:2feb36fc-106c-4d7c-a697-db59971dc...@a7g2000yqo.googlegroups.com...
> Using the standard 19200 baud results in gobbledegook from the
> multimeter.
You aren't going to notice a 0.1% clock skew within 1 byte.
Forget about the difference between 19200 and 19230.
1 - 100 of 244 matches
Mail list logo
