Avatar

Please consider registering
guest

sp_LogInOut Log In sp_Registration Register

Register | Lost password?
Advanced Search

— Forum Scope —




— Match —





— Forum Options —





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

sp_Feed Topic RSS sp_TopicIcon
About the phenomenon that the acquisition time increases when acquiring event data continuously
February 19, 2025
2:16, EET
Avatar
miya2024
Member
Members
Forum Posts: 6
Member Since:
December 9, 2024
sp_UserOfflineSmall Offline

Hello

Event data is acquired continuously at 5-second intervals from the Prosys OPC Simulation Server using uaClient.historyReadEvents().

> HistoryReadResult[] results = uaClient.historyReadEvents(nodeIds, DateTimeUtil
> DateTimeUtil.toDateTime(readEndDate), UnsignedInteger.valueOf(0), even
> TimestampsToReturn.Source);

The event data to be acquired is defined as standard in the Prosys OPC Simulation Server
Address Space tab, Objects>MyObjects>MyDevice, and alarm data is acquired.
The number of events to be acquired is 200 items of data for the same MyDevice.

When acquiring event data continuously for 7 hours under the above conditions, the acquisition time tends to increase gradually, and it was about 15 milliseconds at the first time, but after 7 hours it has increased to about 59 milliseconds. It has increased by 44 milliseconds in 7 hours. I estimate that these differences will exceed 5 seconds after 113 hours have passed.

Are these issues limited to the free version of Prosys OPC Simulation Server?
Has this been resolved in the paid version?

The version of Prosys OPC Simulation Server used is as follows.
Product Version:5.5.2-362
SDK Version:5.2.8-159

Thanks,
Miya

February 19, 2025
11:34, EET
Avatar
Bjarne Boström
Moderator
Moderators
Forum Posts: 1037
Member Since:
April 3, 2012
sp_UserOfflineSmall Offline

Hi,

Those nodes in question (i.e. nodes that are not part of the ‘Objects’ tab) are outside of the “simulated nodes” i.e. main features of the application. They are kinda “extra nodes” and are the same nodes that are in the SDK’s SampleConsoleServer example. They are part of the application, because it originally started (just) as a SampleConsoleServer with an UI. That node is the only one for which we support event history thus we have kept them just to have any, but the implementation is the same (or a bit older) than in the SampleConsoleServer: It stores last 10000 events and does a naive looping of the events for history read purposes. Thus once more events have happened, the lookup for the history will get slower, that is expected.

February 19, 2025
15:28, EET
Avatar
miya2024
Member
Members
Forum Posts: 6
Member Since:
December 9, 2024
sp_UserOfflineSmall Offline

Hi.

Thank you for your reply.
Smile
>It stores last 10000 events and does a naive looping of the events
>for history read purposes.
>Thus once more events have happened, the lookup for the history will
>get slower, that is expected.

I’ve got it.

Thanks,
Miya

Forum Timezone: Europe/Helsinki

Most Users Ever Online: 1919

Currently Online:
66 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: 791

Moderators: 7

Admins: 1

Forum Stats:

Groups: 3

Forums: 15

Topics: 1538

Posts: 6493

Newest Members:

Phillipbus, Oscarsat, WilliamJer, WilliamTunse, mvsjonah79, RaymondSmutt, Merlin AI pap, patlawrence98, opcua_1232141232321, DavidGaday

Moderators: Jouni Aro: 1027, Pyry: 1, Petri: 0, Bjarne Boström: 1037, Jimmy Ni: 26, Matti Siponen: 353, Lusetti: 0

Administrators: admin: 1