You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I can get at the PDU from the IS7ConnectionParameters, that's great.
What I am missing are those magic numbers of protocol overhead for a request & per data item. I don't want to hardcode these, and since you have such well-organized data types for all your protocol code, would it be possible to expose the size of those structs somewhere, eg. in a static class?
The text was updated successfully, but these errors were encountered:
Oh and I guess just to be on the safe side: Is the overhead of sending the read request larger than the overhead required for receiving the response?
In the end the only thing that I really care about is the maximum number of bytes payload I can put into a request, whatever part in there is the limiting factor.
I want to split my large data reading/writing requests into smaller chunks, similar to https://github.com/S7NetPlus/s7netplus/blob/051091919fa80b03989f4375e364ebc4b02aabe7/S7.Net/PlcAsynchronous.cs#L106
For that I need to know at what size to split my data into chunks.
I can get at the PDU from the IS7ConnectionParameters, that's great.
What I am missing are those magic numbers of protocol overhead for a request & per data item. I don't want to hardcode these, and since you have such well-organized data types for all your protocol code, would it be possible to expose the size of those structs somewhere, eg. in a static class?
The text was updated successfully, but these errors were encountered: