-
-
Notifications
You must be signed in to change notification settings - Fork 480
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[NODE-OPCUA-E11] message size 65537 exceeds the negotiated message size 8192 nb chunks 1 #1263
Comments
Siemens OPC UA Server? |
Hello Andreas, no, it should be an ASEM HMI30 device |
While connecting with python opcua-client the first rows in the log are:
|
usually the "MaxMessageSize" is negotiatd in the Hello/Ack Message-Handshake right at the start (first message after connect) which means the client requests a MaxMessageSize he can support and the server checks if he can support that as well if not (e.g. smaller) the server revices the "MaxMessageSize" in the Ack-Message as response to the Hello-Message reference: from your python log:
it tells you exactly that the requested limits ("MaxMessageSize") have been revised to 8192 (requested 65535) |
|
Ok, I see message in the python log. But so the problem is the opc ua client that cannot comply with the server response? Or, to be clearer, do you think there's a way to make it work? |
can you adjust your node-opcua-client code client.on("send_request", console.log)
client.on("receive_response", console.log) so the console output will show the requests and responses for further investigation!? |
Or use environment variable: |
Setting the environment variable the output complete is:
|
something goes wrong during the HEL/ACK transaction when the connection is established. You'll need to set the environment variable please use this minimalistic javascript code to just test the connection process.env.NODEOPCUADEBUG = "TRANSPORT{HELACK-CHUNK}"
const { OPCUAClient } = require("node-opcua");
// replace this line with the targeted server endpoint URL:
const endpointUrl = "opc.tcp://opcuademo.sterfive.com:26543";
;(async()=>{
const client = OPCUAClient.create({});
await client.connect(endpointUrl);
await client.disconnect();
})(); The output will look like
@ultrafab , What is yours ? |
Hello, I had the same issue
and I solved it by specifying the following configuration:
Thanks to @MicheleTogniDerga and @FabioLugatoDerga for the passionate and never-ending support |
I have a similar issue: adjusting transportSettings did not help: 10:17:38:524 MESSAGE BUILDER LIMITS maxMessageSize = 16384 maxChunkCount = 1 maxChunkSize = 16384 ( 16384 ) |
For those who are facing this issue, we encourage you to use |
fixed in node-opcua@2.200.0 |
Trying to connect to an industrial HMI with an embedded opcua server i receive this error, first time using the NodeRed OPCUA node, then trying to using directly the opcua samples
Using the Python opcua-client app or some other clients (es. uaexpert) the connection works and the server is browsable
Changing security type, anonymous, username, etc doesnt change
The text was updated successfully, but these errors were encountered: