readyRead() signal is working strange
-
wrote on 19 Nov 2020, 04:00 last edited by
Firstly, you need to use packet capture software to see if any returned data is accepted.
-
wrote on 19 Nov 2020, 05:21 last edited by IRBaboon
@Crawl-W good day!
I have used terminal to check if data is accepted correctly.
All data send by the device was successfully received. -
@Crawl-W good day!
I have used terminal to check if data is accepted correctly.
All data send by the device was successfully received.wrote on 19 Nov 2020, 05:38 last edited byOk,it is basically certain that your main thread is occupied. Reference to my topic. QSerialport did not emit readyRead () signal，but USB monitor data received.Only occasionally problem
-
Ok,it is basically certain that your main thread is occupied. Reference to my topic. QSerialport did not emit readyRead () signal，but USB monitor data received.Only occasionally problem
wrote on 19 Nov 2020, 07:19 last edited by@Crawl-W hello!
I have read all through your topic. Seems that problem is very similar but I do not get what can occupy the thread.
My programm is working as a terminal in this mode and is suposed to just wait the bytes to be received... -
@Crawl-W hello!
I have read all through your topic. Seems that problem is very similar but I do not get what can occupy the thread.
My programm is working as a terminal in this mode and is suposed to just wait the bytes to be received...wrote on 19 Nov 2020, 07:31 last edited by Crawl.WYou need to make sure that your main thread is idle when the signal is triggered.
Firstly, exclude qt lib version bugs.
Then, peel off serial port read and write code, and you should decouple code.
In general, for such questions can only provide experience and possibilities. The rest is still have to rely on yourself. -
You need to make sure that your main thread is idle when the signal is triggered.
Firstly, exclude qt lib version bugs.
Then, peel off serial port read and write code, and you should decouple code.
In general, for such questions can only provide experience and possibilities. The rest is still have to rely on yourself.wrote on 19 Nov 2020, 07:40 last edited by IRBaboonThis post is deleted! -
wrote on 19 Nov 2020, 07:42 last edited byThis post is deleted!
-
You need to make sure that your main thread is idle when the signal is triggered.
Firstly, exclude qt lib version bugs.
Then, peel off serial port read and write code, and you should decouple code.
In general, for such questions can only provide experience and possibilities. The rest is still have to rely on yourself.wrote on 19 Nov 2020, 07:42 last edited byThis post is deleted! -
wrote on 19 Nov 2020, 09:15 last edited by
You need solve it rather than evade it, especially when there is already a problem.
There is a Chinese idiom called 欲盖弥彰. But you can put the problem aside and solve it later.
-
wrote on 19 Nov 2020, 22:15 last edited by IRBaboon
I have just tested a simple terminal with terminal 1.9b via com0com - it worked in both directions on my work, and....
It is working the same strange way on my personal PC! I can simply send bytes via my QT software and I cannot receive anything via it until I send a new parcel again.
So it is something on the PC... -
I have just tested a simple terminal with terminal 1.9b via com0com - it worked in both directions on my work, and....
It is working the same strange way on my personal PC! I can simply send bytes via my QT software and I cannot receive anything via it until I send a new parcel again.
So it is something on the PC...wrote on 24 Nov 2020, 06:51 last edited by@IRBaboon If your PC have no obvious lagging, my issue is an error direction. Here are some ideas you can try:
- read help doc seriously or test one other poeple's credible demo on your devie, is it possible to call it incorrectly?(for serial device, It is difficult for others to run your demo)
- try the lastest verion of QT
13/14