Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Get Qt Extensions
  • Unsolved
Collapse
Brand Logo
  1. Home
  2. Qt Development
  3. General and Desktop
  4. QSerialPort and local echo
Forum Updated to NodeBB v4.3 + New Features

QSerialPort and local echo

Scheduled Pinned Locked Moved Unsolved General and Desktop
3 Posts 2 Posters 395 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.
  • S Offline
    S Offline
    Sumdood
    wrote on last edited by Sumdood
    #1

    I am using QSerialPort and it works well, does everything I expected. I am sending commands that end in '\r' to hardware. I get back my original command, minus the \r, followed by \n and the response to the command. So far, so good, but I asked the hardware developer if he was sending the original command back to me as described above, but he insists I have "local echo" turned-on. I don't think this is true. On Windows 10, qt6, would QSerialPort echo by default? I see in the documentation that QSerialPort does not offer control of "local echo", but what is the expected behavior? Would it vary based on the driver of the COM port itself? Looked into that a little, but find no reference at all to "local echo" in the driver documentation.

    mzimmersM 1 Reply Last reply
    0
    • S Sumdood

      I am using QSerialPort and it works well, does everything I expected. I am sending commands that end in '\r' to hardware. I get back my original command, minus the \r, followed by \n and the response to the command. So far, so good, but I asked the hardware developer if he was sending the original command back to me as described above, but he insists I have "local echo" turned-on. I don't think this is true. On Windows 10, qt6, would QSerialPort echo by default? I see in the documentation that QSerialPort does not offer control of "local echo", but what is the expected behavior? Would it vary based on the driver of the COM port itself? Looked into that a little, but find no reference at all to "local echo" in the driver documentation.

      mzimmersM Offline
      mzimmersM Offline
      mzimmers
      wrote on last edited by
      #2

      @Sumdood it doesn't sound like an echo issue. Somewhere along the line (either the remote app, the remote serial port driver, or your Windows serial port driver) the \r is being converted to a \n. I doubt it's happening on your machine, but if you have a communications analyzer, you could verify that.

      S 1 Reply Last reply
      0
      • mzimmersM mzimmers

        @Sumdood it doesn't sound like an echo issue. Somewhere along the line (either the remote app, the remote serial port driver, or your Windows serial port driver) the \r is being converted to a \n. I doubt it's happening on your machine, but if you have a communications analyzer, you could verify that.

        S Offline
        S Offline
        Sumdood
        wrote on last edited by
        #3

        @mzimmers Thanks for the reply! That is what I was thinking - that if something on my machine was "echoing", it would probably not be replacing the \r with a \n, and I could find nothing that indicated that QSerialPort would do such a thing - only that the ability to control local echo was not a part of the interface...which left me not knowing exaactly what to expect - read on one of these forums that I could get a "handle" for the port and maybe do something with that, but that was also a dead end. Will try an analyzer. Thanks again!

        1 Reply Last reply
        0

        • Login

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