-
Hi:
I'm having a very strange problem with pyserial on Ubuntu Karmic (9.10). I have a program using pyserial that has worked for years with no problem but now fails to receive any data on the port. Just to make this more complicated it appears as though after "x" reboots the serial port works just fine until the next reboot. I am using the 2.5rc1 version of pyserial. I have tried using a...
2009-11-08 18:37:21 UTC by tfcarlin
-
This Tracker item was closed automatically by the system. It was
previously set to a Pending status, and the original submitter
did not respond within 14 days (the time period specified by
the administrator of this Tracker).
2009-11-05 02:20:20 UTC by sf-robot
-
This Tracker item was closed automatically by the system. It was
previously set to a Pending status, and the original submitter
did not respond within 14 days (the time period specified by
the administrator of this Tracker).
2009-11-05 02:20:19 UTC by sf-robot
-
This Tracker item was closed automatically by the system. It was
previously set to a Pending status, and the original submitter
did not respond within 14 days (the time period specified by
the administrator of this Tracker).
2009-11-04 02:21:18 UTC by sf-robot
-
This Tracker item was closed automatically by the system. It was
previously set to a Pending status, and the original submitter
did not respond within 14 days (the time period specified by
the administrator of this Tracker).
2009-11-04 02:21:17 UTC by sf-robot
-
Hum...5 reboots later this is now working. If I try to run minicom now I get, as expected, "minicom: cannot open /dev/ttyUSB3: Device or resource busy". I did change video cards/drivers for an unrelated issue. Strange.
2009-11-02 20:44:16 UTC by tfcarlin
-
I am using python 2.6.4 and pyserial 2.5.rc1.
2009-11-02 00:13:29 UTC by tfcarlin
-
I am using Ubuntu Karmic. I am unable to read from a serial port (happens to be a USB serial port). I can read the serial port when running minicom. If I run miniterm with the same setting as minicom I don't receive any data. If miniterm is running I can still open minicom. If data then arrives I receive the error:
Exception in thread Thread-1:
Traceback (most recent call last):
File...
2009-11-02 00:08:13 UTC by tfcarlin
-
I'm boosting the priority of this, because with the advent of non-standard (and higher) baud rates, it's not longer just an enhancement request. The current method of setting timeouts _is_ causing garbled data.
In particular, the use of a full _reconfigurePort after every setTimeout is causing data to get dropped. As previously, I recommend splitting out the timeout-setting code from...
2009-10-31 13:54:14 UTC by pjcreath
-
Great, this now works again.
2009-10-31 13:46:58 UTC by pjcreath
