Truncated response from a TCP connection

Hello.

You can use the AddEndOfString method in EVENT_RECEIVE_TEXT to define a string that will be the end of the message.

Hi Vladimir,

Thanks for your reply - the AddEndOfString method seems useful, but unfortunately with the protocol

I’m using there isn’t any defined end of string character. The final byte of the message could either represent the end of the ‘data’ section or an error message, so is unknown to me in advance.

I do know that there will always be at least 10 characters received, with the 10th character representing the length of the data in the following bytes (0-128 bytes).

If you know the length of the resulting string in advance, you can save the resulting strings to variables and then concatenate. For example, in JS you count 10 characters - this is the resulting string. If the length is unknown and there is no end-of-line character, then collect all in one piece, if there is no new data more than a certain period. For example, there is no data for more than 4 seconds. So you run the risk of stability, if you constantly receive data, because you can exhaust all available memory.

This was my first thought, however I only receive data once - the '11, 02, 01, 80' that I would also expect to receive in my example above if this was the case is not seen.

Then estimate the size of the received data and if memory allows, just collect the data in one piece.

I see - thanks for your help, Vladimir

Hello, is your problem still unresolved?

Yes, the problem is resolved, thanks! I simply needed to be using the EVENT_RECEIVE_DATA listener instead to allow for 0x00 characters

Happy to help.