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. Problem with a data from UDP
Forum Updated to NodeBB v4.3 + New Features

Problem with a data from UDP

Scheduled Pinned Locked Moved Solved General and Desktop
28 Posts 4 Posters 3.4k 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.
  • J jenya7

    @KroMignon said in Problem with a data from UDP:

    @jenya7 said in Problem with a data from UDP:

    socket->readDatagram( *(uint8_t ) udp_buffer.data(), udp_buffer.size(), &sender, &senderPort);

    This should be: socket->readDatagram( (uint8_t *) udp_buffer.data(), udp_buffer.size(), &sender, &senderPort);

    It is. The editor's problem

    JonBJ Online
    JonBJ Online
    JonB
    wrote on last edited by
    #11

    @jenya7 said in Problem with a data from UDP:

    The editor's problem

    What does this mean?! :)

    1 Reply Last reply
    0
    • J jenya7

      @KroMignon said in Problem with a data from UDP:

      @jenya7 said in Problem with a data from UDP:

      socket->readDatagram( *(uint8_t ) udp_buffer.data(), udp_buffer.size(), &sender, &senderPort);

      This should be: socket->readDatagram( (uint8_t *) udp_buffer.data(), udp_buffer.size(), &sender, &senderPort);

      It is. The editor's problem

      KroMignonK Offline
      KroMignonK Offline
      KroMignon
      wrote on last edited by
      #12

      @jenya7 said in Problem with a data from UDP:

      It is. The editor's problem

      Sorry, posted to quickly: remove the cast which is false / not required

      It is an old maxim of mine that when you have excluded the impossible, whatever remains, however improbable, must be the truth. (Sherlock Holmes)

      1 Reply Last reply
      0
      • J Offline
        J Offline
        jenya7
        wrote on last edited by
        #13

        @KroMignon said in Problem with a data from UDP:

        socket->readDatagram( udp_buffer.data(), udp_buffer.size(), &sender, &senderPort);

        This way I get array of chars I have to cast every byte.

        socket->readDatagram((uint8_t *)udp_buffer.data(), udp_buffer.size(),  &sender, &senderPort);
        

        This way - error: cannot initialize a parameter of type 'char *' with an rvalue of type 'uint8_t *' (aka 'unsigned char *')

        JonBJ KroMignonK 2 Replies Last reply
        0
        • sierdzioS Offline
          sierdzioS Offline
          sierdzio
          Moderators
          wrote on last edited by
          #14

          You can use QDataStream to automatically convert all data to whatever format you require. To get a suitable device for it, use QBuffer.

          (Z(:^

          1 Reply Last reply
          0
          • J jenya7

            @KroMignon said in Problem with a data from UDP:

            socket->readDatagram( udp_buffer.data(), udp_buffer.size(), &sender, &senderPort);

            This way I get array of chars I have to cast every byte.

            socket->readDatagram((uint8_t *)udp_buffer.data(), udp_buffer.size(),  &sender, &senderPort);
            

            This way - error: cannot initialize a parameter of type 'char *' with an rvalue of type 'uint8_t *' (aka 'unsigned char *')

            JonBJ Online
            JonBJ Online
            JonB
            wrote on last edited by
            #15

            @jenya7
            You are misunderstanding C++. Going readDatagram((uint8_t *)udp_buffer.data() does not "make" the data actually be unsigned chars, it has no effect on "This way I get array of chars I have to cast every byte".

            1 Reply Last reply
            0
            • J jenya7

              @KroMignon said in Problem with a data from UDP:

              socket->readDatagram( udp_buffer.data(), udp_buffer.size(), &sender, &senderPort);

              This way I get array of chars I have to cast every byte.

              socket->readDatagram((uint8_t *)udp_buffer.data(), udp_buffer.size(),  &sender, &senderPort);
              

              This way - error: cannot initialize a parameter of type 'char *' with an rvalue of type 'uint8_t *' (aka 'unsigned char *')

              KroMignonK Offline
              KroMignonK Offline
              KroMignon
              wrote on last edited by KroMignon
              #16

              @jenya7 said in Problem with a data from UDP:

              his way - error: cannot initialize a parameter of type 'char *' with an rvalue of type 'uint8_t *' (aka 'unsigned char *')

              What are you doing?
              socket is as instance of QUdpSocket and udp_buffer an instance of QByteArray or not?

              This must work, as I always do it!

                  QByteArray datagram(socket->pendingDatagramSize(), 0);
                  QHostAddress sender;
                  quint16 senderPort;
              
                  socket->readDatagram(datagram.data(), datagram.size(), &sender, &senderPort);
              

              It is an old maxim of mine that when you have excluded the impossible, whatever remains, however improbable, must be the truth. (Sherlock Holmes)

              J 1 Reply Last reply
              1
              • KroMignonK KroMignon

                @jenya7 said in Problem with a data from UDP:

                his way - error: cannot initialize a parameter of type 'char *' with an rvalue of type 'uint8_t *' (aka 'unsigned char *')

                What are you doing?
                socket is as instance of QUdpSocket and udp_buffer an instance of QByteArray or not?

                This must work, as I always do it!

                    QByteArray datagram(socket->pendingDatagramSize(), 0);
                    QHostAddress sender;
                    quint16 senderPort;
                
                    socket->readDatagram(datagram.data(), datagram.size(), &sender, &senderPort);
                
                J Offline
                J Offline
                jenya7
                wrote on last edited by jenya7
                #17

                What are you doing?
                socket is as instance of QUdpSocket and udp_buffer an instance of QByteArray or not?

                Yes it is.
                But taking char by char form datagram.data()
                I have to cast - uint8_t b0 = static_cast<uint8_t>(datagram[0]);

                KroMignonK JonBJ 2 Replies Last reply
                0
                • J jenya7

                  What are you doing?
                  socket is as instance of QUdpSocket and udp_buffer an instance of QByteArray or not?

                  Yes it is.
                  But taking char by char form datagram.data()
                  I have to cast - uint8_t b0 = static_cast<uint8_t>(datagram[0]);

                  KroMignonK Offline
                  KroMignonK Offline
                  KroMignon
                  wrote on last edited by KroMignon
                  #18

                  @jenya7 said in Problem with a data from UDP:

                  Yes it is.
                  But taking char by char form datagram.data()
                  I have to cast - byte b0 = static_cast<uint8_t>(datagram[0]);

                  No:

                  for(const auto b : datagram)
                  {
                     qDebug() << "Byte value:" << quint8(b);
                  }
                  

                  EDIT
                  or

                  uint8_t* myPoint = static_cast<uint8_t*>(datagram.data());
                  
                  

                  It is an old maxim of mine that when you have excluded the impossible, whatever remains, however improbable, must be the truth. (Sherlock Holmes)

                  J 1 Reply Last reply
                  0
                  • J jenya7

                    What are you doing?
                    socket is as instance of QUdpSocket and udp_buffer an instance of QByteArray or not?

                    Yes it is.
                    But taking char by char form datagram.data()
                    I have to cast - uint8_t b0 = static_cast<uint8_t>(datagram[0]);

                    JonBJ Online
                    JonBJ Online
                    JonB
                    wrote on last edited by JonB
                    #19

                    @jenya7
                    I will contribute one more time. I already told you what to do if you want to reduce repeated casting:

                    If you don't like having to explicitly do casting each time, you could, say, write your own utility function for "the i'th element of a QByteArray as unsigned char/uint_t", or the whole data as uint_t *.

                    Same applies anywhere else.

                    For the record: I believe there have been discussions over the years about how some people would have preferred QByteArray to hold unsigned chars instead of chars. It stays with chars due (at least partly) to it's (slightly weird) determination to end the data with \0 and allow it to interchange fairly free with QString. This is not convenient for your case, but it is what it is, so you're going to have to work with it.

                    J 1 Reply Last reply
                    0
                    • JonBJ JonB

                      @jenya7
                      I will contribute one more time. I already told you what to do if you want to reduce repeated casting:

                      If you don't like having to explicitly do casting each time, you could, say, write your own utility function for "the i'th element of a QByteArray as unsigned char/uint_t", or the whole data as uint_t *.

                      Same applies anywhere else.

                      For the record: I believe there have been discussions over the years about how some people would have preferred QByteArray to hold unsigned chars instead of chars. It stays with chars due (at least partly) to it's (slightly weird) determination to end the data with \0 and allow it to interchange fairly free with QString. This is not convenient for your case, but it is what it is, so you're going to have to work with it.

                      J Offline
                      J Offline
                      jenya7
                      wrote on last edited by
                      #20

                      @JonB said in Problem with a data from UDP:

                      @jenya7
                      I will contribute one more time. I already told you what to do if you want to reduce repeated casting:

                      If you don't like having to explicitly do casting each time, you could, say, write your own utility function for "the i'th element of a QByteArray as unsigned char/uint_t", or the whole data as uint_t *.

                      Same applies anywhere else.

                      To cast each element in a loop? It makes even worse, waste of run time.

                      KroMignonK JonBJ 2 Replies Last reply
                      0
                      • J jenya7

                        @JonB said in Problem with a data from UDP:

                        @jenya7
                        I will contribute one more time. I already told you what to do if you want to reduce repeated casting:

                        If you don't like having to explicitly do casting each time, you could, say, write your own utility function for "the i'th element of a QByteArray as unsigned char/uint_t", or the whole data as uint_t *.

                        Same applies anywhere else.

                        To cast each element in a loop? It makes even worse, waste of run time.

                        KroMignonK Offline
                        KroMignonK Offline
                        KroMignon
                        wrote on last edited by KroMignon
                        #21

                        @jenya7 said in Problem with a data from UDP:

                        To cast each element in a loop? It makes even worse, waste of run time.

                        Casting does not have any impact at runtime... it is only long to write!

                        It is an old maxim of mine that when you have excluded the impossible, whatever remains, however improbable, must be the truth. (Sherlock Holmes)

                        1 Reply Last reply
                        2
                        • J jenya7

                          @JonB said in Problem with a data from UDP:

                          @jenya7
                          I will contribute one more time. I already told you what to do if you want to reduce repeated casting:

                          If you don't like having to explicitly do casting each time, you could, say, write your own utility function for "the i'th element of a QByteArray as unsigned char/uint_t", or the whole data as uint_t *.

                          Same applies anywhere else.

                          To cast each element in a loop? It makes even worse, waste of run time.

                          JonBJ Online
                          JonBJ Online
                          JonB
                          wrote on last edited by JonB
                          #22

                          @jenya7
                          No, I already explained it's to get rid of the explicit cast each time you access it. At some point you have to cast because of the different types, but you can reduce how often you do that. I don't know what else to say. This is straightforward C++ stuff. Oh, and as @KroMignon says, static casting has no runtime code.

                          1 Reply Last reply
                          0
                          • J Offline
                            J Offline
                            jenya7
                            wrote on last edited by jenya7
                            #23

                            @JonB said in Problem with a data from UDP:

                            For the record: I believe there have been discussions over the years about how some people would have preferred QByteArray to hold unsigned chars instead of chars. It stays with chars due (at least partly) to it's (slightly weird) determination to end the data with \0 and allow it to interchange fairly free with QString. This is not convenient for your case, but it is what it is, so you're going to have to work with it.

                            Every embedded stack like LWIP, uIP and others - point to (uint8_t *).
                            Visual Studio - point to (uint8_t *).
                            VxWorks - point to (uint8_t *).
                            Don't remember any project I worked with TCP/UDP and got a string. And if it has to be a string it's very ease - strlen((char *) bytes) - strlen doesn't accuse me - error: cannot initialize a parameter of type...

                            JonBJ KroMignonK 2 Replies Last reply
                            0
                            • J jenya7

                              @JonB said in Problem with a data from UDP:

                              For the record: I believe there have been discussions over the years about how some people would have preferred QByteArray to hold unsigned chars instead of chars. It stays with chars due (at least partly) to it's (slightly weird) determination to end the data with \0 and allow it to interchange fairly free with QString. This is not convenient for your case, but it is what it is, so you're going to have to work with it.

                              Every embedded stack like LWIP, uIP and others - point to (uint8_t *).
                              Visual Studio - point to (uint8_t *).
                              VxWorks - point to (uint8_t *).
                              Don't remember any project I worked with TCP/UDP and got a string. And if it has to be a string it's very ease - strlen((char *) bytes) - strlen doesn't accuse me - error: cannot initialize a parameter of type...

                              JonBJ Online
                              JonBJ Online
                              JonB
                              wrote on last edited by JonB
                              #24

                              @jenya7
                              Jenya, what is your point here? Qt is written as it is. What do you want me or anyone to do about it because you don't like it or it works differently from something else?

                              I've suggested some typing-saving workarounds for you, up to you whether you take advantage or ignore them. It's your code.

                              1 Reply Last reply
                              2
                              • J jenya7

                                @JonB said in Problem with a data from UDP:

                                For the record: I believe there have been discussions over the years about how some people would have preferred QByteArray to hold unsigned chars instead of chars. It stays with chars due (at least partly) to it's (slightly weird) determination to end the data with \0 and allow it to interchange fairly free with QString. This is not convenient for your case, but it is what it is, so you're going to have to work with it.

                                Every embedded stack like LWIP, uIP and others - point to (uint8_t *).
                                Visual Studio - point to (uint8_t *).
                                VxWorks - point to (uint8_t *).
                                Don't remember any project I worked with TCP/UDP and got a string. And if it has to be a string it's very ease - strlen((char *) bytes) - strlen doesn't accuse me - error: cannot initialize a parameter of type...

                                KroMignonK Offline
                                KroMignonK Offline
                                KroMignon
                                wrote on last edited by
                                #25

                                @jenya7 said in Problem with a data from UDP:

                                Every embedded stack like LWIP, uIP and others - point to (uint8_t *).
                                Visual Studio - point to (uint8_t *).
                                VxWorks - point to (uint8_t *).
                                Don't remember any project I worked with TCP/UDP and got string. Ans if it has to be string it's very ease - strlen((char *) bytes) - strlen doesn't accuse me - error: cannot initialize a parameter of type...

                                Maybe, but your are using Qt, so you have to adapt your code to Qt or use another framework.

                                It is an old maxim of mine that when you have excluded the impossible, whatever remains, however improbable, must be the truth. (Sherlock Holmes)

                                1 Reply Last reply
                                0
                                • KroMignonK KroMignon

                                  @jenya7 said in Problem with a data from UDP:

                                  Yes it is.
                                  But taking char by char form datagram.data()
                                  I have to cast - byte b0 = static_cast<uint8_t>(datagram[0]);

                                  No:

                                  for(const auto b : datagram)
                                  {
                                     qDebug() << "Byte value:" << quint8(b);
                                  }
                                  

                                  EDIT
                                  or

                                  uint8_t* myPoint = static_cast<uint8_t*>(datagram.data());
                                  
                                  
                                  J Offline
                                  J Offline
                                  jenya7
                                  wrote on last edited by jenya7
                                  #26

                                  @KroMignon said in Problem with a data from UDP:

                                  @jenya7 said in Problem with a data from UDP:

                                  Yes it is.
                                  But taking char by char form datagram.data()
                                  I have to cast - byte b0 = static_cast<uint8_t>(datagram[0]);

                                  No:

                                  for(const auto b : datagram)
                                  {
                                     qDebug() << "Byte value:" << quint8(b);
                                  }
                                  

                                  EDIT
                                  or

                                  uint8_t* myPoint = static_cast<uint8_t*>(datagram.data());
                                  
                                  

                                  That's good! - uint8_t* myPoint = static_cast<uint8_t*>(datagram.data());

                                  but

                                  uint32_t MSGPARSER::ParseMessage(QByteArray data, MESSAGE * sens_msg)
                                  {
                                      uint8_t *data_u8 = static_cast<uint8_t*>(data.data());
                                  }
                                  

                                  I get

                                  error: static_cast from 'char *' to 'uint8_t *' (aka 'unsigned char *') is not allowed

                                  This way
                                  uint8_t data_u8 = (uint8_t)(data.data());
                                  no error but

                                  warning: use of old-style cast

                                  KroMignonK 1 Reply Last reply
                                  0
                                  • J jenya7

                                    @KroMignon said in Problem with a data from UDP:

                                    @jenya7 said in Problem with a data from UDP:

                                    Yes it is.
                                    But taking char by char form datagram.data()
                                    I have to cast - byte b0 = static_cast<uint8_t>(datagram[0]);

                                    No:

                                    for(const auto b : datagram)
                                    {
                                       qDebug() << "Byte value:" << quint8(b);
                                    }
                                    

                                    EDIT
                                    or

                                    uint8_t* myPoint = static_cast<uint8_t*>(datagram.data());
                                    
                                    

                                    That's good! - uint8_t* myPoint = static_cast<uint8_t*>(datagram.data());

                                    but

                                    uint32_t MSGPARSER::ParseMessage(QByteArray data, MESSAGE * sens_msg)
                                    {
                                        uint8_t *data_u8 = static_cast<uint8_t*>(data.data());
                                    }
                                    

                                    I get

                                    error: static_cast from 'char *' to 'uint8_t *' (aka 'unsigned char *') is not allowed

                                    This way
                                    uint8_t data_u8 = (uint8_t)(data.data());
                                    no error but

                                    warning: use of old-style cast

                                    KroMignonK Offline
                                    KroMignonK Offline
                                    KroMignon
                                    wrote on last edited by
                                    #27

                                    @jenya7 said in Problem with a data from UDP:

                                    error: static_cast from 'char *' to 'uint8_t *' (aka 'unsigned char *') is not allowed

                                    Sorry, I am a little bit tired today.. should be reinterpret_cast<>() and not static_cast<>()

                                    It is an old maxim of mine that when you have excluded the impossible, whatever remains, however improbable, must be the truth. (Sherlock Holmes)

                                    J 1 Reply Last reply
                                    3
                                    • KroMignonK KroMignon

                                      @jenya7 said in Problem with a data from UDP:

                                      error: static_cast from 'char *' to 'uint8_t *' (aka 'unsigned char *') is not allowed

                                      Sorry, I am a little bit tired today.. should be reinterpret_cast<>() and not static_cast<>()

                                      J Offline
                                      J Offline
                                      jenya7
                                      wrote on last edited by jenya7
                                      #28

                                      @KroMignon said in Problem with a data from UDP:

                                      reinterpret_cast

                                      Thanks a lot. Looks like a great solution.

                                      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