Thanks heaps for the help, guys!
I bit the bullit and am now leaving the serial ports open all of the
time.
I still think it is a driver/hardware problem. When the ports go South
even
a reboot of the laptop the program is running on won't fix it. The
hardware
is all brand new, so it should have
phil wrote:
> I use PySerial in a 16 line data collection system
> with LOTS of threads, and yes am frustrated by read().
> This sounds excellent, keep us updated.
>
> BTW, haven't done any event driven Python except Tkinter.
> Would this a class library which would let you
> define an event and
I use PySerial in a 16 line data collection system
with LOTS of threads, and yes am frustrated by read().
This sounds excellent, keep us updated.
BTW, haven't done any event driven Python except Tkinter.
Would this a class library which would let you
define an event and a handler?
Do you have a
Neil Benn wrote:
> PySerial doesn;t have any kind of event firing to notify you when data
> is available. The way I get round this is to have a loop polling (in a
> seperate thread) to see if any data is available (it's a method on the
> interface), then read all the data in and fire this off t
Bob Greschke wrote:
> "Peter Hansen" <[EMAIL PROTECTED]> wrote in message >
>>I'd call it very unusual
>>(in my experience) to have a program open and close a serial port
>>repeatedly.
>
> One of the serial ports (there are actually two) is used to read some NMEA
> sentences from a GPS. It i
Bob Greschke wrote:
>"Peter Hansen" <[EMAIL PROTECTED]> wrote in message >
>
>
>>Actually, I'm curious why you don't do the same. I'd call it very unusual
>>(in my experience) to have a program open and close a serial port
>>repeatedly. Among other things, this means that the DSR/DTR lines a
"Peter Hansen" <[EMAIL PROTECTED]> wrote in message >
> Actually, I'm curious why you don't do the same. I'd call it very unusual
> (in my experience) to have a program open and close a serial port
> repeatedly. Among other things, this means that the DSR/DTR lines are
> toggling high and low
Bob Greschke wrote:
> I didn't write the C++ program, but it looks like it never closes the serial
> port. It opens it when it starts up, then keeps it open until it quits.
> Tsk tsk tsk. Sloppy. Maybe they did that to cover up this problem. :)
Actually, I'm curious why you don't do the same.
"Peter Hansen" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
> Bob Greschke wrote:
> > But writing anything to the port
>> quickly (not always right away...like maybe 5-6 iterations through the
>> loop?) causes the
>>
>> win32file.CloseHandle(self.hComPort)
>>
>> statement in th
Bob Greschke wrote:
> But writing anything to the port
> quickly (not always right away...like maybe 5-6 iterations through the
> loop?) causes the
>
> win32file.CloseHandle(self.hComPort)
>
> statement in the 'def close(self)' function of the serialwin32.py file of
> the pySerial package
I forgot to mention that once the Python program(s) fail, THEN the C++
program also fails to opne the port, and the equipment has to be
power-cycled to get things to work again.
Bob
--
http://mail.python.org/mailman/listinfo/python-list
We have some equipment that communicates at 57600 baud RS232. The path from
the PC is USB to a Phillips USB hub, then off of that a TUSB3410 USB/Serial
converter. The driver for the 3410 chip creates a "normal" comm port (like
COM3). There is a C++ program that has no problem talking to the e
12 matches
Mail list logo
