Network Stream writer data type mismatch

[bszabo]

Hi,

I'm trying to send data through a Network Streamer from my cRIO RT moule to my PC host. I defined the data type (2D array) of my writer at the beginning, but when I try to write to it, it requires data with higher dimensions (3D array).

This happens also if I define the data type with different dimensions, it will require one more dimension all the time.

What could be the problem? Do I have to configure something differently? Or is it not advisable to stream an array and I should use a different data representation?

[Artem.SPb]

You're wrong. Actually the opposite: not a function requires 3D, but you are trying to write 3D there.

[Hooovahh]

I think something is wrong just not sure what.  If you look at the Simple Network Streams example in Help >> Find Examples you'll see that both the sender and receiver have the same number of dimensions.  The one direction sends a scalar cluster, and the other is a 1D array of waveforms.  The other ends where that data is received or written is the same.  I suspect there is a problem with the Create Endpoint or its session not making it to the writer properly.  This session data type is what defines what the data type of the Data In terminal is and what it can accept.

[crossrulz · Accepted solution]

---

@bszabo wrote:

This happens also if I define the data type with different dimensions, it will require one more dimension all the time.

---

That is exactly correct because you are using the Write Multiple Elements to Stream function.  It expects an array of whatever you state the data type is.  If the data type is already an array, it will expect 1 more dimension to the array.  Instead, use the Write Single Element to Stream function.