Closed japloi closed 5 years ago
Hi Biancode, I posted this issue on another forum, it was all sorted, it was the server sync time between IBH server and our computer server time. After i sync it both to the companies time, the time out was gone.
Heres the link to the other forum https://github.com/mikakaraila/node-red-contrib-opcua/issues/107#issuecomment-478993894
I'm submitting a ... (check one with "x")
Problem
Information
Current behaviour OPCUA client disconnect and sometimes reconnects with the following message
" Timeout .... waiting for response for ReadRequest { /RequestHeader/ authenticationToken / NodeId /: ns=0;i=389813714 timeStamp / UtcTime /: 2019-03-27T10:25:11.693 requestHandle / IntegerId /: 532 0x214 returnDiagnostics / UInt32 /: 0 0x0 auditEntryId / UAString /: timeoutHint / UInt32 /: 0 0x0 additionalHeader / ExtensionObject /: null }; Timeout .... waiting for response for ReadRequest { /RequestHeader/ authenticationToken / NodeId /: ns=0;i=389813714 timeStamp / UtcTime /: 2019-03-27T10:25:12.206 requestHandle / IntegerId /: 533 0x215 returnDiagnostics / UInt32 /: 0 0x0 auditEntryId / UAString /: timeoutHint / UInt32 /: 0 0x0 additionalHeader / ExtensionObject /: null };
Expected behaviour Keep running with no disconnects
Minimal reproduction of the problem with instructions
Your Environment
Using node red opcua client i gather data from a IBH opcua server and sent it to the influx data base
(x ) I am using just the Node-RED package and got node-opcua installed with it
( x) I have installed node-opcua global from source (using git clone)
( x) I have installed node-opcua as a global package (using npm i -g)
Device :
( ) macOS: v
( ) Linux: v
( x) Windows: window server 2012 R2
( ) Raspbian: v
( ) Other:
Description of the connecting OPC UA system: