Qt Forum

    • Login
    • Search
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    • Unsolved

    Update: Forum Guidelines & Code of Conduct


    Qt World Summit: Early-Bird Tickets

    Solved error: "Cannot configure TxEcho for open device" QCanBusDevice

    General and Desktop
    qcanbusdevice can bus
    2
    11
    594
    Loading More Posts
    • 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.
    • B
      Babs last edited by

      Hello i'm working with QCanBusDevice class and a systeccan plugin. I create my CanDevice in my class constructor and send messages to the device using writeFrame function.
      I get the error "Cannot configure TxEcho for open device" each time i send a message.
      Can anyone help?

      aha_1980 1 Reply Last reply Reply Quote 0
      • aha_1980
        aha_1980 Lifetime Qt Champion @Babs last edited by

        Hi @Babs,

        which Qt version are you using?

        Please check with the CAN Example (you can compile and run it from QtCreator). You should not get this message on every frame write, maximum once on open().

        Regards

        Qt has to stay free or it will die.

        B 1 Reply Last reply Reply Quote 2
        • B
          Babs @aha_1980 last edited by

          @aha_1980 I'm using Qt 5.12.0.
          If i understand well i must get this error when i call setConfigurationParameter after i connect my device. I'm not doing so and setConfiguration Parameters in my class constructor before connecting the device.

          aha_1980 1 Reply Last reply Reply Quote 0
          • aha_1980
            aha_1980 Lifetime Qt Champion @Babs last edited by

            @Babs Please check with the CAN Example and report the results here.

            Qt has to stay free or it will die.

            B 2 Replies Last reply Reply Quote 0
            • B
              Babs @aha_1980 last edited by

              @aha_1980 I get the same error when i try to send a message via CAN example.[link text](0_1554898958966_error.PNG link url)
              0_1554898966685_compil.PNG

              1 Reply Last reply Reply Quote 0
              • B
                Babs @aha_1980 last edited by

                @aha_1980 I get the same error even with the CAN example

                aha_1980 1 Reply Last reply Reply Quote 0
                • aha_1980
                  aha_1980 Lifetime Qt Champion @Babs last edited by

                  @Babs Ok, but do you get it every time you send a frame or once after open?

                  I need this information to fix the plugin.

                  Qt has to stay free or it will die.

                  B 1 Reply Last reply Reply Quote 0
                  • B
                    Babs @aha_1980 last edited by

                    @aha_1980 I get the error every time i send a frame.

                    aha_1980 2 Replies Last reply Reply Quote 0
                    • aha_1980
                      aha_1980 Lifetime Qt Champion @Babs last edited by

                      Hi @Babs,

                      I just tried but I cannot reproduce your problem with Qt 5.13 Beta.

                      So please, give the exact configuration you did, otherwise it's impossible to reproduce this error.
                      0_1554919692071_892d3a58-9df4-4899-83a2-f5da2c8adb0d-grafik.png

                      My configuration:
                      0_1554919746260_47d77f82-8a22-489f-9eb3-d9dcbeb494be-grafik.png
                      Regards

                      Qt has to stay free or it will die.

                      1 Reply Last reply Reply Quote 0
                      • aha_1980
                        aha_1980 Lifetime Qt Champion @Babs last edited by

                        @Babs

                        Update: I was partly able to reproduce your problem! The error happens when you open the device (one time, as I already assumed) and I pushed a fix for review: https://codereview.qt-project.org/258740

                        If everything goes well, this fix will be in Qt 5.12.4

                        Regards

                        Qt has to stay free or it will die.

                        B 1 Reply Last reply Reply Quote 2
                        • B
                          Babs @aha_1980 last edited by

                          @aha_1980 Thanks you.
                          Regards,

                          1 Reply Last reply Reply Quote 0
                          • First post
                            Last post