Since NI has dropped the ENET-232/4 we have had to look else where to handle our serial communication. I am testing a B&B Electronics VERSR4x4 and 2 out of our 3 instruments use ASCII strings with termination characters. This was easy to swap the VISA functions over to TCP. However one of instruments uses hex packets. With VISA the U8 array was type cast to a string and sent via VISA Write no problem. I captured the network traffic and the data packet was 23 characters. I don't know why but VISA sandwiches the data with a bunch of other hex numbers. However when I swap over to TCP the network traffic only shows the original 5 byte hex data.
The orginal data is 7e 05 ff 19 94
Here is the successful VISA write using a ENET-232/4
Here is the unsuccessful TCP write using the B&B VESR4x4
What gives? I have tried to recreate the VISA traffic by artifically creating the full 23 byte data but it doesn't have an effect. I am not sure where the issue lies.