cancel
Showing results for 
Search instead for 
Did you mean: 

Unstable Connection - Node Red OPC UA Node

Unstable Connection - Node Red OPC UA Node

E_Stapel
Established Member

Hello everyone,

as you can see in the screenshot, I tested two different OPC UA Nodes (IoT and Standard Node). Both have the same endpoint configuration but the standard OPC UA node sometimes didn´t connect while the IoT Node is connected.

E_Stapel_1-1707730045522.png

Did somebody have experience with that nodes? 

Thanks you!

5 REPLIES 5

Sgilk
Contributor

Hello @E_Stapel ,

Can you please post the configuration of the OPC UA Client node? Also, what versions of ctrlX OS and Node-RED are you using?

I walk through configuration of these nodes in this video starting at ~9:15.

E_Stapel
Established Member

Hello @Sgilk ,

I´m using the CtrlX V1.20 and the NodeRed-App with Version 1.20.0+3.0.2-ctrlx.
The configurations should be right because it has already worked and the IoT-OPC-UA-Client-Node has the same Endpoint configuration and is working aswell. The only Problem is that the Standard-OPC-UA-Node sometimes didn´t connect. Here is a Screenshot of the IOT-Node:

E_Stapel_0-1707812287349.pngE_Stapel_2-1707812494682.png

 

And in the following is the configuration of the standard-OPCUA-Node:

E_Stapel_1-1707812379687.png

 

Thank you!

@E_Stapel ,

Is the OPC UA server running on the ctrlX CORE? You said you can sometimes connect without error using the current configuration? The connection is just lost sometimes?

E_Stapel
Established Member

Hello @Sgilk ,

no the OPC UA Server is running externally on a PLC. The Server is stable because the OPC UA Client App is with this server connected aswell as the IoT-OPCUA-Client-Node in Node Red. The only Client which lost the connection sometimes is the standard-OPCUA-Client-Node. 

@E_Stapel ,

I have never seen this problem. As this is a third party node, it may be difficult to provide you a solid answer. The open source code can be found here. Line 408 generates the first message in your debug window. My next suggestion would be to SSH the ctrlX CORE and retrieve the node-red verbose logs. 

If you could provide your server configuration, I could test this on my end.

Icon--AD-black-48x48Icon--address-consumer-data-black-48x48Icon--appointment-black-48x48Icon--back-left-black-48x48Icon--calendar-black-48x48Icon--center-alignedIcon--Checkbox-checkIcon--clock-black-48x48Icon--close-black-48x48Icon--compare-black-48x48Icon--confirmation-black-48x48Icon--dealer-details-black-48x48Icon--delete-black-48x48Icon--delivery-black-48x48Icon--down-black-48x48Icon--download-black-48x48Ic-OverlayAlertIcon--externallink-black-48x48Icon-Filledforward-right_adjustedIcon--grid-view-black-48x48IC_gd_Check-Circle170821_Icons_Community170823_Bosch_Icons170823_Bosch_Icons170821_Icons_CommunityIC-logout170821_Icons_Community170825_Bosch_Icons170821_Icons_CommunityIC-shopping-cart2170821_Icons_CommunityIC-upIC_UserIcon--imageIcon--info-i-black-48x48Icon--left-alignedIcon--Less-minimize-black-48x48Icon-FilledIcon--List-Check-grennIcon--List-Check-blackIcon--List-Cross-blackIcon--list-view-mobile-black-48x48Icon--list-view-black-48x48Icon--More-Maximize-black-48x48Icon--my-product-black-48x48Icon--newsletter-black-48x48Icon--payment-black-48x48Icon--print-black-48x48Icon--promotion-black-48x48Icon--registration-black-48x48Icon--Reset-black-48x48Icon--right-alignedshare-circle1Icon--share-black-48x48Icon--shopping-bag-black-48x48Icon-shopping-cartIcon--start-play-black-48x48Icon--store-locator-black-48x48Ic-OverlayAlertIcon--summary-black-48x48tumblrIcon-FilledvineIc-OverlayAlertwhishlist