CODEWITHSUNDEEP
c++arrayssocketsvisual-c++udp
mnelson
mnelson

Reputation: 3

Sending numeric Array via UDP using winsock vc++

RESOLVED: Problem was primarily with the simulink blockset that was reading in the UDP packet rather than data transmission.

I am trying to send a 20 byte numerical array out of a c++ program by using winsock. The issue I am running into is data packaging, in the end I want each number in the array to go out as its own byte so that my simulink model that is receiving these values does not need an additional processing script.

My array contains 14 boolean values (0|1) and then 6 values that range from -100 to 100. These are reporting the status of a controller input. for example the array would look like 

    int array msgint[20] = [1,0,1,0,0,1,1,0,0,0,0,0,0,0,50,80,-90,40,90,-20];

I have tried using typecasting and sending multiple strings but all just appear to rearrange the gibberish I am getting or cause a socket error. Currently my sendto function looks like 

        sendto(sd,message,80,0,(struct sockadd *) &server,server_length)

I know this line works as the packet makes it through it just does not appear as I would like it to. In the send to, message is the formatted string I am trying to create to properly send all of contents of the array. Currently is is arbitrary and has little significance I have it in for debugging purposes essentially.

Upvotes: 0

Views: 936

Answers (3)

ScottMcP-MVP
ScottMcP-MVP

Reputation: 10415

"in the end I want each number in the array to go out as its own byte"

Then change your array to 

char msgint[20] = ...

Upvotes: 0

SirDarius
SirDarius

Reputation: 42899

If you want to send 20 bytes, and you know that every integer value in your array will be in the [-100, +100] range, you should not use the int type, which usually contains either 32-bit or 64-bit values on modern platforms.

You might instead want to use the char type, which usually represents a 8-bit value.

For even more certainty, if you can use C++11 features, you should use the <cstdint> header, which defines the int8_t type, guaranteed to be a signed 8-bit type. See http://en.cppreference.com/w/cpp/types/integer.

Your array should look like:

#include <cstdint>
std::int8_t msgint[20] = {1,0,1,0,0,1,1,0,0,0,0,0,0,0,50,80,-90,40,90,-20};

or 

char msgint[20] = {1,0,1,0,0,1,1,0,0,0,0,0,0,0,50,80,-90,40,90,-20};

and your sendto will be:

sendto(sd,msgint,20,0,(struct sockadd *) &server,server_length);

Upvotes: 0

pm100
pm100

Reputation: 50190

you are starting at the wrong point. Network communications should start with the design of the wire protocol.

How will you represent something on the wire. Binary or text. Most 'modern' protocols use text (json or xml). A few years ago binary was hot (asn1/ber/der). I suggest json

Then how will you wrap up the payload. Do you need to say 'here is a set of xxxs. now here is a set of yyyys'. I dont know what you are doing so its hard to say what you need

Upvotes: 1

Related Questions