Professional OPC
Development Tools

logos

Client.Write() Excepption, node size 19 000 Bytes

More
16 May 2017 14:39 #5155 by support
OK, thank you.

I was looking into the size limitations in the meantime. I know the issue is now resolved, but for record, here are the current default transport quotas as used by QuickOPC 2016.2
<TransportQuotas>
 
    <!-- The default timeout in milliseconds for operations (used by clients) -->
    <OperationTimeout>120000</OperationTimeout>
 
    <!-- The maximum length for a string value in any message -->
    <MaxStringLength>1048576</MaxStringLength>
 
    <!-- The maximum length for a byte string value in any message -->
    <MaxByteStringLength>4194304  </MaxByteStringLength>
 
    <!-- The maximum length for any array in a message. 
         Note that some protocols do not distinguish between bytes and arrays. 
         In these cases the binding will choose the larger of 
         MaxByteStringLength or MaxArrayLength-->
    <MaxArrayLength>65535</MaxArrayLength>
 
    <!-- The maximum size of any message -->
    <MaxMessageSize>4194304</MaxMessageSize>
 
    <!-- The maximum buffer size 
         This value controls how big a block of memory the transport layer allocates.
         Setting this value to a large value will reduce performance and use a lot of RAM -->
    <MaxBufferSize>65535</MaxBufferSize>
 
    <!-- The lifetime of a SecureChannel in milliseconds.
         This specifies how long the server will keep a broken channel around while waiting 
         for a client to reconnect.
         Not used by HTTP or .NET TCP bindings -->
    <ChannelLifetime>300000</ChannelLifetime>
 
    <!-- The lifetime of a SecurityToken in milliseconds.
         This specifies how long a security token can be used without renewal. -->
    <SecurityTokenLifetime>3600000</SecurityTokenLifetime>
  </TransportQuotas>

I was about to write that they are unlikely to be a problem, because they are relatively big.
Best regards

Please Log in or Create an account to join the conversation.

More
16 May 2017 13:54 #5154 by bmts
Solbed!
Server parse byte stream to structure and when was parsed string that has reduced Size to 20 Characters and sending size was Higher, end receiving request.


Thanks for your time

Please Log in or Create an account to join the conversation.

More
16 May 2017 13:32 #5153 by bmts
I Tried to gnererate new data with size 19671B and It Works. So In this case does not matter on size, but on Data.

I supposed that te server refuse data during writing.

Next I am going to modify the data and find the reason why it happens...

It is possible to check if the server end connection or not?

Please Log in or Create an account to join the conversation.

More
16 May 2017 12:49 #5152 by bmts
Version 2016.2
Endpoint descriptor path start with: "opc.tcp://76.86.1.10:4840 ....

Please Log in or Create an account to join the conversation.

More
16 May 2017 12:27 #5151 by support
Hello,

which version of QuickOPC are you using?

Thank you

(a memo from the phone call: protocol is opc.tcp)

Please Log in or Create an account to join the conversation.

More
16 May 2017 11:59 #5150 by bmts
I Read and write UaNode content to PLC with size about 15 - 16 KB. It take 1-2 sec but It works.

Today I need write more data 19KB, byt it throw exception, see attachment.

Have OpcLabs library some node size restriction?

Thanks for response.
Attachments:

Please Log in or Create an account to join the conversation.

Moderators: support
Time to create page: 0.181 seconds

      

 Recommend this on Google