06-27-2018 12:57 PM
TCP Write.vi has an output bytes written. Is it writing the correct number of bytes? You could also do a wireshark capture to make sure everything is being written correctly. If it is, then the problem is your python code is not reading the correct amount of data.
-Jordan
06-27-2018 01:13 PM
So I added a base encoder and now I'm able to send about 6/10 of the images (within the JSON) to the Python server
06-27-2018 01:20 PM
@elcalverado wrote:
TCP Write.vi has an output bytes written. Is it writing the correct number of bytes?
Just checked and my bytes written output in LabVIEW is the same value as my data_len in Python
@elcalverado wrote:
You could also do a wireshark capture to make sure everything is being written correctly. If it is, then the problem is your python code is not reading the correct amount of data.
What's a wireshark capture?
06-27-2018 01:51 PM
Wireshark is an opensource tool that lets you monitor Ethernet traffic. You can install it for free from here. Basically you start a capture that will let you see all the TCP packets being sent over your network. So what did you change with the base encoder?
-Jordan
06-27-2018 02:24 PM
@elcalverado wrote:
Wireshark is an opensource tool that lets you monitor Ethernet traffic. You can install it for free from here. Basically you start a capture that will let you see all the TCP packets being sent over your network. So what did you change with the base encoder?
-Jordan
I thought the issue might be unpacking the serialized binary, but it doesn't appear to be the case
06-27-2018 03:29 PM
So I've tried running the program with Wireshark several times now. Every time I hit capture Wireshark crashes and now I am beginning to get an error in LabVIEW:
06-27-2018 04:12 PM
I got it working! I had to add a delay in between the last write and close of the TCP connection