Problems with OPCua and Node-Red

#1

Hi to all...

I have a problem, when i am opening browser page with node editor, RPIs CPU is fully loaded and connection between OPCua and node-red is not workign anymore...

any suggestions?

i also get this warning and errors:

Timeout .... waiting for response for PublishRequest { /RequestHeader/
authenticationToken /* NodeId /: ns=1;i=3
timeStamp /
UtcTime /: 2018-09-1 1T13:30:40.304Z
requestHandle /
IntegerId /: 2198 0x896
returnDiagnostics /
UInt32 /: 0 0x0
auditEntryId /
UAString /:
timeoutHint /
UInt32 /: 50000 0xc350
additionalHeader /
ExtensionObject /: null
};
Timeout .... waiting for response for PublishRequest { /RequestHeader/
authenticationToken /
NodeId /: ns=1;i=3
timeStamp /
UtcTime /: 2018-09-1 1T13:30:40.343Z
requestHandle /
IntegerId /: 2199 0x897
returnDiagnostics /
UInt32 /: 0 0x0
auditEntryId /
UAString /:
timeoutHint /
UInt32 /: 50000 0xc350
additionalHeader /
ExtensionObject /: null
};
Timeout .... waiting for response for PublishRequest { /RequestHeader/
authenticationToken /
NodeId /: ns=1;i=3
timeStamp /
UtcTime /: 2018-09-1 1T13:30:40.649Z
requestHandle /
IntegerId /: 2200 0x898
returnDiagnostics /
UInt32 /: 0 0x0
auditEntryId /
UAString /:
timeoutHint /
UInt32 /: 50000 0xc350
additionalHeader /
ExtensionObject /: null
};
Timeout .... waiting for response for PublishRequest { /RequestHeader/
authenticationToken /
NodeId /: ns=1;i=3
timeStamp /
UtcTime /: 2018-09-1 1T13:30:40.799Z
requestHandle /
IntegerId /: 2201 0x899
returnDiagnostics /
UInt32 /: 0 0x0
auditEntryId /
UAString /:
timeoutHint /
UInt32 /: 50000 0xc350
additionalHeader /
ExtensionObject /: null
};
Timeout .... waiting for response for PublishRequest { /RequestHeader/
authenticationToken /
NodeId /: ns=1;i=3
timeStamp /
UtcTime /: 2018-09-1 1T13:30:40.901Z
requestHandle /
IntegerId /: 2202 0x89a
returnDiagnostics /
UInt32 /: 0 0x0
auditEntryId /
UAString /:
timeoutHint /
UInt32 /: 50000 0xc350
additionalHeader /
ExtensionObject /: null
};
warning : ClientSessionKeepAliveManager#ping_server ServiceFault returned by server { /ServiceFault/
responseHeader /
ResponseHeader /: {
timeStamp /
UtcTime /: 2018-09-1 1T13:32:06.071Z
requestHandle /
IntegerId /: 2203 0x89b
serviceResult /
StatusCode /: BadSessio nIdInvalid (0x80250000)
serviceDiagnostics /
DiagnosticInfo /: {
namespaceUri /
Int32 /: -1
symbolicId /
Int32 /: -1
locale /
Int32 /: -1
localizedText /
Int32 /: -1
additionalInfo /
String /: null
innerStatusCode /
StatusCode /: Good (0x0 0000)
innerDiagnosticInfo /
DiagnosticInfo /: {
}
}
stringTable /
String [] /: [ ] (l=1)
additionalHeader /
ExtensionObject /: null
}
};
warning : ClientSessionKeepAliveManager#ping_server ServiceFault returned by server { /ServiceFault/
responseHeader /
ResponseHeader /: {
timeStamp /
UtcTime /: 2018-09-1 1T13:32:06.073Z
requestHandle /
IntegerId /: 40 0x28
serviceResult /
StatusCode /: BadSessio nIdInvalid (0x80250000)
serviceDiagnostics /
DiagnosticInfo /: {
namespaceUri /
Int32 /: -1
symbolicId /
Int32 /: -1
locale /
Int32 /: -1
localizedText /
Int32 /: -1
additionalInfo /
String /: null
innerStatusCode /
StatusCode /: Good (0x0 0000)
innerDiagnosticInfo /
DiagnosticInfo /: {
}
}
stringTable /
String [] /: [ ] (l=1)
additionalHeader /
ExtensionObject */: null
}
};
11 Sep 13:32:07 - [warn] Communication send error: Error: not opened
11 Sep 13:32:07 - [warn] Communication send error: Error: not opened
11 Sep 13:32:07 - [warn] Communication send error: Error: not opened
11 Sep 13:32:07 - [warn] Communication send error: Error: not opened
warning : disconnection : closing pending sessions

0 Likes

#2

Have you done the basics?
Looked at the logs?
Checked you have the latest versions etc?

0 Likes

#3

Basics?

I have last versions...
I send what writes down...

Where are logs saved?

0 Likes

#4

The logs are saved in different places depending on what hardware you are running on and how you have configured Node-RED.

I'd also try googling the error to see if others have had the same issue...

0 Likes

#5

I google it but I didn’t find any solutions to this case. I found in logs same warnings as i wrote down up.

0 Likes

#6

Which node are you using? Is it this one? node-red-contrib-opcua This issue would appear to be what you are seeing https://github.com/mikakaraila/node-red-contrib-opcua/issues/36

0 Likes

#7

Similar yes... but still without solution. I am using node-red-contrib-opcua
Here is also warning on node-red start.

> [warn] [node-red-node-pi-sense-hat/sensehat] Error: Can't find Sense HAT python libraries. Run sudo apt-get install sense-hat

0 Likes

#8

so if you still have the problem, recheck that you have the latest version and then open an issue so that the developer is aware.

Your new issue is because you haven’t followed the instructions in the Nodes ReadMe. The message tells you what you need to do.

0 Likes