Quantcast
Channel: MCS Electronics Forum
Viewing all articles
Browse latest Browse all 20562

EASY TCP/IP : Problem with TCPREAD function : REPLY

$
0
0
Hi Mark, So I'm working on implementing your suggestion but it is more complicated and I'm trying to figure out why I need to do it this way. When I implement the Socketstat command, the result is the number of bytes in the complete header so it's all in the buffer but then when I use the Tcpread command in a loop to extract data from the buffer, I either get a complete line up to the CRLF or a partial string of exactly 46 bytes. This is very consistent and does not seem to match what is in the help file. It seems like if all of the data is in the buffer, the Tcpread should read up to the CRLF instead of stopping at 46 bytes if the string is longer. So do I not understand this correctly? I'm not complaining - just trying to understand why this isn't working correctly. I have been a very pleased Bacom user for a long time and am very satisfied. Thanks, Bob

Viewing all articles
Browse latest Browse all 20562

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>