You can also try doing a raw read (non Qt way) on the device using open/read system calls and check if data is actually available. That'll make sure that the OS is indeed receiving data and the problem can then be isolated to QSerialPort.
HTH, -mandeep On Wed, Oct 16, 2013 at 6:25 AM, nus1998 <nus1...@yeah.net> wrote: > HI Denis, > > Thanks for the reply. > > Even if I don't use "waitForReadyRead" but polling "bytesAvailable" instead, > the later always returns 0 although there is data received and I can use > other terminal software to display it too. > > Best regards, > Je > > > > > > At 2013-10-16 01:15:36,"Denis Shienkov" <scap...@yandex.ru> wrote: > > Hi. > > Seems it is a bug, see: https://bugreports.qt-project.org/browse/QTBUG-33987 > > You can test this patch. > > Besd regards, > Denis > > > 15.10.2013 18:37, nus1998 пишет: > > > I found a strange issue, when I read from serial, first I will call > "waitForReadyRead", it returns with true in specified time, however, when I > call "read" function thereafter, I can't read even a byte. the hardware > works fine since I checked it by logic analyzer. > > env: win7 64, qt 5.1 mingw version > > thanks > Je > ---- > from iPad > > > > > _______________________________________________ > Interest mailing list > Interest@qt-project.org > http://lists.qt-project.org/mailman/listinfo/interest > > > > > > _______________________________________________ > Interest mailing list > Interest@qt-project.org > http://lists.qt-project.org/mailman/listinfo/interest > _______________________________________________ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest
