Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Get Qt Extensions
  • Unsolved
Collapse
Brand Logo
  1. Home
  2. Qt Development
  3. Qt for MCUs
  4. readyRead() signal is working strange
Forum Updated to NodeBB v4.3 + New Features

readyRead() signal is working strange

Scheduled Pinned Locked Moved Unsolved Qt for MCUs
qserialportreadyreadserial portrs485
14 Posts 3 Posters 3.1k Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • Crawl.WC Offline
    Crawl.WC Offline
    Crawl.W
    wrote on last edited by
    #4

    Firstly, you need to use packet capture software to see if any returned data is accepted.

    I 1 Reply Last reply
    0
    • Crawl.WC Crawl.W

      Firstly, you need to use packet capture software to see if any returned data is accepted.

      I Offline
      I Offline
      IRBaboon
      wrote on last edited by IRBaboon
      #5

      @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.WC 1 Reply Last reply
      0
      • I 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.WC Offline
        Crawl.WC Offline
        Crawl.W
        wrote on last edited by
        #6

        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

        I 1 Reply Last reply
        0
        • Crawl.WC Crawl.W

          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

          I Offline
          I Offline
          IRBaboon
          wrote on last edited by
          #7

          @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.WC 1 Reply Last reply
          0
          • I IRBaboon

            @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.WC Offline
            Crawl.WC Offline
            Crawl.W
            wrote on last edited by Crawl.W
            #8

            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.

            I Crawl.WC 2 Replies Last reply
            0
            • Crawl.WC Crawl.W

              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.

              I Offline
              I Offline
              IRBaboon
              wrote on last edited by IRBaboon
              #9
              This post is deleted!
              Crawl.WC 2 Replies Last reply
              0
              • I IRBaboon

                This post is deleted!

                Crawl.WC Offline
                Crawl.WC Offline
                Crawl.W
                wrote on last edited by
                #10
                This post is deleted!
                1 Reply Last reply
                0
                • Crawl.WC Crawl.W

                  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.

                  Crawl.WC Offline
                  Crawl.WC Offline
                  Crawl.W
                  wrote on last edited by
                  #11
                  This post is deleted!
                  1 Reply Last reply
                  0
                  • I IRBaboon

                    This post is deleted!

                    Crawl.WC Offline
                    Crawl.WC Offline
                    Crawl.W
                    wrote on last edited by
                    #12

                    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.

                    1 Reply Last reply
                    0
                    • I Offline
                      I Offline
                      IRBaboon
                      wrote on last edited by IRBaboon
                      #13

                      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...

                      Crawl.WC 1 Reply Last reply
                      0
                      • I 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...

                        Crawl.WC Offline
                        Crawl.WC Offline
                        Crawl.W
                        wrote on last edited by
                        #14

                        @IRBaboon If your PC have no obvious lagging, my issue is an error direction. Here are some ideas you can try:

                        1. 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)
                        2. try the lastest verion of QT
                        1 Reply Last reply
                        1

                        • Login

                        • Login or register to search.
                        • First post
                          Last post
                        0
                        • Categories
                        • Recent
                        • Tags
                        • Popular
                        • Users
                        • Groups
                        • Search
                        • Get Qt Extensions
                        • Unsolved