Avatar

Please consider registering
guest

sp_LogInOut Log In sp_Registration Register

Register | Lost password?
sp_Search Search
Advanced Search
Advanced Search

— Forum Scope —




— Match —





— Forum Options —





Minimum search word length is 3 characters - maximum search word length is 84 characters

sp_Search Search
Go to Bottom
No permission to create posts
sp_Feed Topic RSS sp_TopicIcon
Unable to monitor data variables on Beckhoff PLC
February 3, 2020
16:07, EET
Avatar
John
Member
Members
Forum Posts: 5
Member Since:
February 3, 2020
sp_UserOfflineSmall Offline
Go to Top
1sp_Permalink sp_Print

HELP!!

I am using Prosys OPC UA client API to communicate with a BoschRexroth and also Beckhoff PLC. I can read/write variables on both system, however I cannot get any substriptions created having monitor data items to be monitorred on a Beckhoff PLC.

The Prosys UA Browser is also having trouble to monitor data items on a Beckhoff system. Adding an data item in the data view shows me no error but the data value, status code and so on are not updated and therefore empty. After a while, when adding another data item, it will give me an Error; Could not add MonitoredItem(s) in the Prosys UA Browser. Within the Prosys Client API it will be a Bad_SubscriptionIdInvalid error sometime with source a Bad_InternalError.

On the other hand, the UaExpert OPC Client or the TwinCAT OPC Client do not have any issue of showing live updates of the same data item. What is going wrong?

Can I somehow get more detailed logging information of the real underlying cause?

February 3, 2020
16:55, EET
Avatar
Bjarne Boström
Moderator
Moderators
Forum Posts: 983
Member Since:
April 3, 2012
sp_UserOfflineSmall Offline
Go to Top
2sp_Permalink sp_Print

Hi,

Hmm.. which version of the SDK and UA Browser you are using? Is the data “simple” i.e. e.g. Floats/Ints/Doubles/Strings etc, or do you also have custom Structures?

UA Browser does log to /.prosysopc/prosys-opc-ua-browser/log . Assuming you have the latest release version of the SDK (4.2.0) it basically most likely is doing the same thing as you are.

Usually the Bad_InternalError is a programming mistake etc., but it would be nice to know if this is given by the server or the client. Can you paste the (complete) error stacktrace here for both cases? Also one way is to use https://www.prosysopc.com/blog/opc-ua-wireshark/ to see if the response message had that as the status code. Also in general it can be used to check if we do something differently vs. other clients.

February 3, 2020
17:55, EET
Avatar
John
Member
Members
Forum Posts: 5
Member Since:
February 3, 2020
sp_UserOfflineSmall Offline
Go to Top
3sp_Permalink sp_Print

1. Monitoring a data item like a simple Boolean for example will fail, however I can read/write all data item values without any problem.
prosys-opc-ua-sdk-for-java-4.1.2-876-client-binary\lib\prosys-opc-ua-sdk-client-4.1.2-876.jar

Updated to prosys-opc-ua-sdk-for-java-4.1.2-876-client-binary\lib\prosys-opc-ua-sdk-client-4.2.0-955.jar makes no difference.

2. Using the ProsysUA Browser prosys-opc-ua-browser-windows-x64-4.0.0-200.exe

02/03/2020 16:38:12.590 INFO [main] com.prosysopc.ua.app.uabrowser.UaBrowserLauncher [] – Conf location: C:\Users\P056213\.prosysopc\prosys-opc-ua-browser\conf.xml
02/03/2020 16:38:14.210 INFO [main] com.prosysopc.fx.library.utility.managedservices.ManagedServiceManager [] – Services for start order S2_CONF_FILE_LOAD : [h [NEW]]
02/03/2020 16:38:14.217 INFO [main] com.prosysopc.fx.library.utility.managedservices.ManagedServiceManager [] – Services for start order S3_AFTER_CONF_FILE_LOAD : [b [NEW], a [NEW]]
02/03/2020 16:38:14.218 INFO [main] com.prosysopc.fx.library.utility.managedservices.ManagedServiceManager [] – Services for start order S5_UI_START : [f [NEW]]
02/03/2020 16:38:14.221 INFO [main] com.prosysopc.fx.library.utility.managedservices.ManagedServiceManager [] – Starting: {NEW=[h [NEW]]}
02/03/2020 16:38:14.255 INFO [h STARTING] com.prosysopc.ua.UaApplication [] – Prosys OPC UA SDK for Java v4.1.2-876
02/03/2020 16:38:14.256 INFO [h STARTING] com.prosysopc.ua.UaApplication [] – (c) Prosys OPC Ltd.
02/03/2020 16:38:14.258 INFO [main] com.prosysopc.fx.library.utility.managedservices.ManagedServiceManager [] – Starting: {NEW=[b [NEW], a [NEW]]}
02/03/2020 16:38:14.261 INFO [pool-3-thread-1] com.prosysopc.ua.app.uabrowser.core.a [] – Loading ApplicationInstanceCertificates
02/03/2020 16:38:14.293 INFO [main] com.prosysopc.fx.library.utility.managedservices.ManagedServiceManager [] – Starting: {NEW=[f [NEW]]}
02/03/2020 16:38:14.434 INFO [pool-3-thread-1] com.prosysopc.ua.f [] – Reading application certificate from C:\Users\P056213\.prosysopc\prosys-opc-ua-browser\PKI\CA\private\UaBrowser@SW-JVH-Z4G4_2048.der
02/03/2020 16:38:14.436 INFO [pool-3-thread-1] com.prosysopc.ua.f [] – Reading private key from keystore C:\Users\P056213\.prosysopc\prosys-opc-ua-browser\PKI\CA\private\UaBrowser@SW-JVH-Z4G4_2048.pem
02/03/2020 16:38:14.531 INFO [JavaFX Application Thread] com.prosysopc.ua.app.uabrowser.f [] – Loaded font:Font[name=Roboto, family=Roboto, style=Regular, size=12.0]
02/03/2020 16:38:14.548 INFO [JavaFX Application Thread] com.prosysopc.ua.app.uabrowser.f [] – Loaded font:Font[name=Roboto Bold, family=Roboto, style=Bold, size=12.0]
02/03/2020 16:38:14.559 INFO [JavaFX Application Thread] com.prosysopc.ua.app.uabrowser.f [] – Loaded font:Font[name=Roboto Italic, family=Roboto, style=Italic, size=12.0]
02/03/2020 16:38:14.574 INFO [JavaFX Application Thread] com.prosysopc.ua.app.uabrowser.f [] – Loaded font:Font[name=Roboto Bold Italic, family=Roboto, style=Bold Italic, size=12.0]
02/03/2020 16:38:14.764 INFO [pool-3-thread-1] com.prosysopc.ua.app.uabrowser.core.a [] – Loaded ApplicationInstanceCertificates
02/03/2020 16:38:14.821 INFO [JavaFX Application Thread] com.prosysopc.ua.app.uabrowser.f [] – Showing main window
02/03/2020 16:38:23.504 INFO [JavaFX Application Thread] com.prosysopc.ua.stack.transport.tcp.io.d [] – SW-JVH-Z420/10.3.195.35:4840 Connecting
02/03/2020 16:38:23.523 INFO [JavaFX Application Thread] com.prosysopc.ua.stack.transport.tcp.io.d [] – Connected (non-reverse), handshake completed, local=/10.3.195.165:55380, remote=SW-JVH-Z420/10.3.195.35:4840
02/03/2020 16:38:23.540 INFO [JavaFX Application Thread] com.prosysopc.ua.stack.transport.tcp.io.b [] – 904245592 Closed
02/03/2020 16:38:23.543 INFO [JavaFX Application Thread] com.prosysopc.ua.stack.transport.tcp.io.d [] – SW-JVH-Z420/10.3.195.35:4840 Closed
02/03/2020 16:38:23.543 INFO [TcpConnection/Read] com.prosysopc.ua.stack.transport.tcp.io.d [] – SW-JVH-Z420/10.3.195.35:4840 Closed (graceful)
02/03/2020 16:38:25.250 INFO [JavaFX Application Thread] com.prosysopc.ua.app.uabrowser.singleclient.securitysettings.c [] – Selected SecurityMode: [http://opcfoundation.org/UA/SecurityPolicy#None,None]
02/03/2020 16:38:25.274 INFO [JavaFX Application Thread] com.prosysopc.ua.stack.transport.tcp.io.d [] – SW-JVH-Z420/10.3.195.35:4840 Connecting
02/03/2020 16:38:25.276 INFO [JavaFX Application Thread] com.prosysopc.ua.stack.transport.tcp.io.d [] – Connected (non-reverse), handshake completed, local=/10.3.195.165:55381, remote=SW-JVH-Z420/10.3.195.35:4840
02/03/2020 16:38:25.280 INFO [JavaFX Application Thread] com.prosysopc.ua.stack.transport.tcp.io.b [] – 904245593 Closed
02/03/2020 16:38:25.280 INFO [JavaFX Application Thread] com.prosysopc.ua.stack.transport.tcp.io.d [] – SW-JVH-Z420/10.3.195.35:4840 Closed
02/03/2020 16:38:25.280 INFO [TcpConnection/Read] com.prosysopc.ua.stack.transport.tcp.io.d [] – SW-JVH-Z420/10.3.195.35:4840 Closed (graceful)
02/03/2020 16:38:25.283 INFO [JavaFX Application Thread] com.prosysopc.ua.stack.transport.tcp.io.d [] – SW-JVH-Z420/10.3.195.35:4840 Connecting
02/03/2020 16:38:25.285 INFO [JavaFX Application Thread] com.prosysopc.ua.stack.transport.tcp.io.d [] – Connected (non-reverse), handshake completed, local=/10.3.195.165:55382, remote=SW-JVH-Z420/10.3.195.35:4840
02/03/2020 16:38:26.115 INFO [JavaFX Application Thread] com.prosysopc.ua.typedictionary.i [] – TypeDictionary initialized successfully
02/03/2020 16:38:26.127 INFO [PublishTask-com.prosysopc.ua.client.x@a0c8b6a] com.prosysopc.ua.app.uabrowser.singleclient.j [] – Server opc.tcp://SW-JVH-Z420:4840 state changed to NoConfiguration
02/03/2020 16:38:30.226 WARN [JavaFX Application Thread] com.prosysopc.ua.client.a.f [] – Target of HasProperty (Source=ServerType–Target=ServerStatus) reference is not UaProperty (i.e. TypeDefinition does not refer to PropertyType)
02/03/2020 16:38:43.291 INFO [JavaFX Application Thread] com.prosysopc.ua.app.uabrowser.singleclient.dataview.h [] – Adding NodeIds: [urn:BeckhoffAutomation:Ua:Logic:Application.Data_PC.GV_sComm_Data_PC.bWatchDog]
02/03/2020 16:38:48.796 INFO [JavaFX Application Thread] com.prosysopc.ua.app.uabrowser.singleclient.dataview.h [] – Adding NodeIds: [urn:BeckhoffAutomation:Ua:Logic:Application.Data_PC.GV_sComm_Data_PC.iLoggedInLevel]
02/03/2020 16:40:18.676 INFO [JavaFX Application Thread] com.prosysopc.ua.app.uabrowser.singleclient.dataview.h [] – Adding NodeIds: [urn:BeckhoffAutomation:Ua:Logic:Application.Data_PC.GV_sComm_Data_PC.bUTCResync]
02/03/2020 16:40:18.691 ERROR [JavaFX Application Thread] com.prosysopc.ua.app.uabrowser.singleclient.dataview.h [] – Cannot add MonitoredItems
com.prosysopc.ua.G: ServiceFault [ResponseHeader=”ResponseHeader [Timestamp=”02/03/20 15:40:17.2217559 GMT”, RequestHandle=”505″, ServiceResult=”Bad_SubscriptionIdInvalid (0x80280000) “The subscription id is not valid.””, ServiceDiagnostics=”Diagnostic Info:
“, StringTable=”[]”, AdditionalHeader=”null”]”]
at com.prosysopc.ua.client.s.b(SourceFile:1068) ~[application-4.0.0-200.jar:4.0.0-200]
at com.prosysopc.ua.client.s.d(SourceFile:1604) ~[application-4.0.0-200.jar:4.0.0-200]
at com.prosysopc.ua.client.s.a(SourceFile:236) ~[application-4.0.0-200.jar:4.0.0-200]
at com.prosysopc.ua.app.uabrowser.singleclient.dataview.h.c(SourceFile:258) ~[application-4.0.0-200.jar:4.0.0-200]
at com.prosysopc.ua.app.uabrowser.singleclient.dataview.h.A(SourceFile:305) ~[application-4.0.0-200.jar:4.0.0-200]
at com.prosysopc.ua.app.uabrowser.singleclient.dataview.g.a(SourceFile:318) ~[application-4.0.0-200.jar:4.0.0-200]
at com.sun.javafx.event.CompositeEventHandler.dispatchBubblingEvent(CompositeEventHandler.java:86) ~[javafx-base-13-linux.jar:?]
at com.sun.javafx.event.EventHandlerManager.dispatchBubblingEvent(EventHandlerManager.java:238) ~[javafx-base-13-linux.jar:?]
at com.sun.javafx.event.EventHandlerManager.dispatchBubblingEvent(EventHandlerManager.java:191) ~[javafx-base-13-linux.jar:?]
at com.sun.javafx.event.CompositeEventDispatcher.dispatchBubblingEvent(CompositeEventDispatcher.java:59) ~[javafx-base-13-linux.jar:?]
at com.sun.javafx.event.BasicEventDispatcher.dispatchEvent(BasicEventDispatcher.java:58) ~[javafx-base-13-linux.jar:?]
at com.sun.javafx.event.EventDispatchChainImpl.dispatchEvent(EventDispatchChainImpl.java:114) ~[javafx-base-13-linux.jar:?]
at com.sun.javafx.event.BasicEventDispatcher.dispatchEvent(BasicEventDispatcher.java:56) ~[javafx-base-13-linux.jar:?]
at com.sun.javafx.event.EventDispatchChainImpl.dispatchEvent(EventDispatchChainImpl.java:114) ~[javafx-base-13-linux.jar:?]
at com.sun.javafx.event.BasicEventDispatcher.dispatchEvent(BasicEventDispatcher.java:56) ~[javafx-base-13-linux.jar:?]
at com.sun.javafx.event.EventDispatchChainImpl.dispatchEvent(EventDispatchChainImpl.java:114) ~[javafx-base-13-linux.jar:?]
at com.sun.javafx.event.BasicEventDispatcher.dispatchEvent(BasicEventDispatcher.java:56) ~[javafx-base-13-linux.jar:?]
at com.sun.javafx.event.EventDispatchChainImpl.dispatchEvent(EventDispatchChainImpl.java:114) ~[javafx-base-13-linux.jar:?]
at com.sun.javafx.event.BasicEventDispatcher.dispatchEvent(BasicEventDispatcher.java:56) ~[javafx-base-13-linux.jar:?]
at com.sun.javafx.event.EventDispatchChainImpl.dispatchEvent(EventDispatchChainImpl.java:114) ~[javafx-base-13-linux.jar:?]
at com.sun.javafx.event.BasicEventDispatcher.dispatchEvent(BasicEventDispatcher.java:56) ~[javafx-base-13-linux.jar:?]
at com.sun.javafx.event.EventDispatchChainImpl.dispatchEvent(EventDispatchChainImpl.java:114) ~[javafx-base-13-linux.jar:?]
at com.sun.javafx.event.BasicEventDispatcher.dispatchEvent(BasicEventDispatcher.java:56) ~[javafx-base-13-linux.jar:?]
at com.sun.javafx.event.EventDispatchChainImpl.dispatchEvent(EventDispatchChainImpl.java:114) ~[javafx-base-13-linux.jar:?]
at com.sun.javafx.event.EventUtil.fireEventImpl(EventUtil.java:74) ~[javafx-base-13-linux.jar:?]
at com.sun.javafx.event.EventUtil.fireEvent(EventUtil.java:54) ~[javafx-base-13-linux.jar:?]
at javafx.event.Event.fireEvent(Event.java:198) ~[javafx-base-13-linux.jar:?]
at javafx.scene.Scene$DnDGesture.fireEvent(Scene.java:3029) ~[javafx-graphics-13-linux.jar:?]
at javafx.scene.Scene$DnDGesture.processTargetDrop(Scene.java:3255) ~[javafx-graphics-13-linux.jar:?]
at javafx.scene.Scene$DropTargetListener.drop(Scene.java:2969) ~[javafx-graphics-13-linux.jar:?]
at com.sun.javafx.tk.quantum.GlassSceneDnDEventHandler.lambda$handleDragDrop$2(GlassSceneDnDEventHandler.java:108) ~[javafx-graphics-13-linux.jar:?]
at java.security.AccessController.doPrivileged(Native Method) ~[?:?]
at com.sun.javafx.tk.quantum.GlassSceneDnDEventHandler.handleDragDrop(GlassSceneDnDEventHandler.java:104) ~[javafx-graphics-13-linux.jar:?]
at com.sun.javafx.tk.quantum.GlassViewEventHandler.lambda$handleDragDrop$11(GlassViewEventHandler.java:766) ~[javafx-graphics-13-linux.jar:?]
at com.sun.javafx.tk.quantum.QuantumToolkit.runWithoutRenderLock(QuantumToolkit.java:412) ~[javafx-graphics-13-linux.jar:?]
at com.sun.javafx.tk.quantum.GlassViewEventHandler.handleDragDrop(GlassViewEventHandler.java:765) ~[javafx-graphics-13-linux.jar:?]
at com.sun.glass.ui.View.handleDragDrop(View.java:713) ~[javafx-graphics-13-linux.jar:?]
at com.sun.glass.ui.View.notifyDragDrop(View.java:1042) ~[javafx-graphics-13-linux.jar:?]
at com.sun.glass.ui.win.WinDnDClipboard.push(Native Method) ~[javafx-graphics-13-win.jar:?]
at com.sun.glass.ui.win.WinSystemClipboard.pushToSystem(WinSystemClipboard.java:234) ~[javafx-graphics-13-win.jar:?]
at com.sun.glass.ui.SystemClipboard.flush(SystemClipboard.java:51) ~[javafx-graphics-13-linux.jar:?]
at com.sun.glass.ui.ClipboardAssistance.flush(ClipboardAssistance.java:59) ~[javafx-graphics-13-linux.jar:?]
at com.sun.javafx.tk.quantum.QuantumClipboard.flush(QuantumClipboard.java:274) ~[javafx-graphics-13-linux.jar:?]
at com.sun.javafx.tk.quantum.QuantumToolkit.startDrag(QuantumToolkit.java:1286) ~[javafx-graphics-13-linux.jar:?]
at javafx.scene.Scene$DnDGesture.dragDetectedProcessed(Scene.java:3049) ~[javafx-graphics-13-linux.jar:?]
at javafx.scene.Scene$DnDGesture.process(Scene.java:3118) ~[javafx-graphics-13-linux.jar:?]
at javafx.scene.Scene$MouseHandler.process(Scene.java:3878) ~[javafx-graphics-13-linux.jar:?]
at javafx.scene.Scene.processMouseEvent(Scene.java:1849) ~[javafx-graphics-13-linux.jar:?]
at javafx.scene.Scene$ScenePeerListener.mouseEvent(Scene.java:2590) ~[javafx-graphics-13-linux.jar:?]
at com.sun.javafx.tk.quantum.GlassViewEventHandler$MouseEventNotification.run(GlassViewEventHandler.java:409) ~[javafx-graphics-13-linux.jar:?]
at com.sun.javafx.tk.quantum.GlassViewEventHandler$MouseEventNotification.run(GlassViewEventHandler.java:299) ~[javafx-graphics-13-linux.jar:?]
at java.security.AccessController.doPrivileged(Native Method) ~[?:?]
at com.sun.javafx.tk.quantum.GlassViewEventHandler.lambda$handleMouseEvent$2(GlassViewEventHandler.java:447) ~[javafx-graphics-13-linux.jar:?]
at com.sun.javafx.tk.quantum.QuantumToolkit.runWithoutRenderLock(QuantumToolkit.java:412) ~[javafx-graphics-13-linux.jar:?]
at com.sun.javafx.tk.quantum.GlassViewEventHandler.handleMouseEvent(GlassViewEventHandler.java:446) ~[javafx-graphics-13-linux.jar:?]
at com.sun.glass.ui.View.handleMouseEvent(View.java:556) ~[javafx-graphics-13-linux.jar:?]
at com.sun.glass.ui.View.notifyMouse(View.java:942) ~[javafx-graphics-13-linux.jar:?]
at com.sun.glass.ui.win.WinApplication._runLoop(Native Method) ~[javafx-graphics-13-win.jar:?]
at com.sun.glass.ui.win.WinApplication.lambda$runLoop$3(WinApplication.java:174) ~[javafx-graphics-13-win.jar:?]
at java.lang.Thread.run(Thread.java:834) [?:?]
Caused by: com.prosysopc.ua.stack.c.f: ServiceFault [ResponseHeader=”ResponseHeader [Timestamp=”02/03/20 15:40:17.2217559 GMT”, RequestHandle=”505″, ServiceResult=”Bad_SubscriptionIdInvalid (0x80280000) “The subscription id is not valid.””, ServiceDiagnostics=”Diagnostic Info:
“, StringTable=”[]”, AdditionalHeader=”null”]”]
at com.prosysopc.ua.stack.transport.c.a.j(SourceFile:282) ~[application-4.0.0-200.jar:4.0.0-200]
at com.prosysopc.ua.stack.transport.tcp.io.b.a(SourceFile:869) ~[application-4.0.0-200.jar:4.0.0-200]
at com.prosysopc.ua.stack.transport.tcp.io.b.a(SourceFile:808) ~[application-4.0.0-200.jar:4.0.0-200]
at com.prosysopc.ua.stack.a.j.a(SourceFile:305) ~[application-4.0.0-200.jar:4.0.0-200]
at com.prosysopc.ua.stack.transport.c.a(SourceFile:938) ~[application-4.0.0-200.jar:4.0.0-200]
at com.prosysopc.ua.client.s.b(SourceFile:1065) ~[application-4.0.0-200.jar:4.0.0-200]
… 59 more

Update to prosys-opc-ua-browser-windows-x64-4.0.2-231.exe

02/03/2020 16:54:26.246 INFO [Thread-16] com.prosysopc.ua.stack.transport.tcp.io.d [] – SW-JVH-Z420/10.3.195.35:4840 Connecting
02/03/2020 16:54:26.249 INFO [Thread-16] com.prosysopc.ua.stack.transport.tcp.io.d [] – Connected (non-reverse), handshake completed, local=/10.3.195.165:55578, remote=SW-JVH-Z420/10.3.195.35:4840
02/03/2020 16:54:26.254 INFO [Thread-16] com.prosysopc.ua.stack.transport.tcp.io.b [] – 904245606 Closed
02/03/2020 16:54:26.254 INFO [Thread-16] com.prosysopc.ua.stack.transport.tcp.io.d [] – SW-JVH-Z420/10.3.195.35:4840 Closed
02/03/2020 16:54:26.254 INFO [TcpConnection/Read] com.prosysopc.ua.stack.transport.tcp.io.d [] – SW-JVH-Z420/10.3.195.35:4840 Closed (graceful)
02/03/2020 16:54:26.256 INFO [Thread-16] com.prosysopc.ua.stack.transport.tcp.io.d [] – SW-JVH-Z420/10.3.195.35:4840 Connecting
02/03/2020 16:54:26.258 INFO [Thread-16] com.prosysopc.ua.stack.transport.tcp.io.d [] – Connected (non-reverse), handshake completed, local=/10.3.195.165:55579, remote=SW-JVH-Z420/10.3.195.35:4840
02/03/2020 16:54:26.267 WARN [Thread-16] com.prosysopc.ua.typedictionary.b [] – More than one GeneratedDataTypeDictionary contains the same dictionary TargetNamespace http://opcfoundation.org/UA/
02/03/2020 16:54:26.268 WARN [Thread-16] com.prosysopc.ua.typedictionary.b [] – More than one GeneratedDataTypeDictionary contains the same dictionary TargetNamespace http://opcfoundation.org/UA/GDS/
02/03/2020 16:54:27.416 INFO [Thread-16] com.prosysopc.ua.typedictionary.i [] – TypeDictionary initialized successfully
02/03/2020 16:54:27.417 INFO [PublishTask-com.prosysopc.ua.client.x@4b2674c6] com.prosysopc.ua.app.uabrowser.singleclient.j [] – Server opc.tcp://SW-JVH-Z420:4840 state changed to NoConfiguration

February 4, 2020
11:38, EET
Avatar
Bjarne Boström
Moderator
Moderators
Forum Posts: 983
Member Since:
April 3, 2012
sp_UserOfflineSmall Offline
Go to Top
4sp_Permalink sp_Print

Hmm, I think the last line is the key, as it shows “state changed to NoConfiguration”. This means that when the SDK automatically reads the server state (Objects/Server/ServerStatus/State) it is not “0 (Running)”. If it is not running the server is not considered to be in properly running state i.e. active and thus we are not sending any PublishRequets, thus you are not seeing any updates to the monitoreditems, as the data comes from PublishResponses.

Basically you will need to do some configuring on the server so that it would show up as “Running”. The other clients might not check this state the same way as we do, but I would/could argue that our way is the more correct one. The OPC UA Specification v.1.04 Part 5 section 12.6 ServerState Table 136 lists for the noconfiguration mode as follows:

“NO_CONFIGURATION_2 The Server is running but has no configuration information loaded and therefore does not transfer data”

Probably some improvements to the UA Browser could be made in the future to make this more clear (but the status should have been visible in the leftside are next to the address bar even now). Also it should be noted that that ServerState NoConfiguration is used very rarely.

No permission to create posts
sp_Feed All RSS
Go to top
Forum Timezone: Europe/Helsinki

Most Users Ever Online: 518

Currently Online:
10 Guest(s)

Currently Browsing this Page:
1 Guest(s)

Top Posters:

hbrackel: 135

pramanj: 86

Francesco Zambon: 81

rocket science: 77

ibrahim: 75

Sabari: 62

kapsl: 57

gjevremovic: 49

Xavier: 43

TimK: 41

Member Stats:

Guest Posters: 0

Members: 677

Moderators: 16

Admins: 1

Forum Stats:

Groups: 3

Forums: 15

Topics: 1467

Posts: 6259

Newest Members:

DonaldPooma, fidelduke938316, Jan-Pfizer, DavidROunc, fen.pang@woodside.com, aytule, rashadbrownrigg, christi10l, ahamad1

Moderators: Jouni Aro: 1009, Otso Palonen: 32, Tuomas Hiltunen: 5, Pyry: 1, Petri: 0, Bjarne Boström: 983, Heikki Tahvanainen: 402, Jukka Asikainen: 1, moldzh08: 0, Jimmy Ni: 26, Teppo Uimonen: 21, Markus Johansson: 42, Niklas Nurminen: 0, Matti Siponen: 321, Lusetti: 0, Ari-Pekka Soikkeli: 5

Administrators: admin: 1