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
Server state changed unexpectedly
August 5, 2016
14:37, EEST
Avatar
Izak
Member
Members
Forum Posts: 3
Member Since:
August 5, 2016
sp_UserOfflineSmall Offline
Go to Top
1sp_Permalink sp_Print

Hello,
We are using Prosys and as OPC server Kepware is used. Quite frequently, at some occassions every hour we get a notification that the “server state” has been changed.
Example:
2016-08-03 05:04:16.635 WARN Server state changed unexpectedly from “Running” to “CommunicationFault” in connection state “CONNECTED”.
2016-08-03 05:04:17.802 WARN Server state changed unexpectedly from “CommunicationFault” to “Running” in connection state “CONNECTED”.
Normally it switches from Running -> CommunicationFault -> Running again within some second.
We have been trying to see why this happens from the OPC server log file but cannot connect any events there that can explain the “server state change” that Prosys is refering to.
Do you have some ideas what can trigger this server state change?

BR Andreas

August 5, 2016
15:40, EEST
Avatar
Heikki Tahvanainen
Member
Members
Forum Posts: 402
Member Since:
April 17, 2013
sp_UserOfflineSmall Offline
Go to Top
2sp_Permalink sp_Print

Hi,

The server state monitoring in the SDK is done by reading value attribute from the ServerStatus node. The ServerStatus node is a standard node which can be found by browsing Objects->Server->ServerStatus (NodeId i=2256).

As a first step, you can try setting different values to status check interval and status check timeout.

By default, the SDK does the server status checking once every second. The interval can be changed with UaClient.setStatusCheckInterval method.

The default timeout for these status checks is 10 seconds which should be long enough for all normal situations. The statusCheckTimeout can be changed with method UaClient.setStatusCheckTimeout.

Hopefully this helps to solve your issue. If not, let us know.

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

Most Users Ever Online: 1919

Currently Online:
13 Guest(s)

Currently Browsing this Page:
1 Guest(s)

Top Posters:

Heikki Tahvanainen: 402

hbrackel: 144

rocket science: 88

pramanj: 86

Francesco Zambon: 83

Ibrahim: 78

Sabari: 62

kapsl: 57

gjevremovic: 49

Xavier: 43

Member Stats:

Guest Posters: 0

Members: 737

Moderators: 7

Admins: 1

Forum Stats:

Groups: 3

Forums: 15

Topics: 1524

Posts: 6450

Newest Members:

fannielima, kristiewinkle8, rust, christamcdowall, redaahern07571, nigelbdhmp, travistimmons, AnnelCib, dalenegettinger, howardkennerley

Moderators: Jouni Aro: 1026, Pyry: 1, Petri: 0, Bjarne Boström: 1026, Jimmy Ni: 26, Matti Siponen: 346, Lusetti: 0

Administrators: admin: 1