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
Unable to Read History
October 2, 2021
23:41, EEST
Avatar
bibhudatta.sahu@honeywell.com
Member
Members
Forum Posts: 19
Member Since:
May 15, 2020
sp_UserOfflineSmall Offline

Hello,

We are using ProSys SDK v4.5.4. While reading the history using SDK’s API from Microcom OPCUA server we are getting the below exception.

java.security.PrivilegedActionException: com.prosysopc.ua.ServiceException: Bad_EncodingLimitsExceeded (code=0x80080000, description=”TL error 0x80080000″) ServiceResult=Bad_EncodingLimitsExceeded (0x80080000)

Could you please provide any solution to overcome the issue.

Thanks,
Bibhudatta Sahu

October 4, 2021
10:03, EEST
Avatar
Bjarne Boström
Moderator
Moderators
Forum Posts: 684
Member Since:
April 3, 2012
sp_UserOfflineSmall Offline

Hi,

The error is that the (OPC UA) Message was too large to be encoded (within the limits client and server negotiated during connection). I assume this is within the server side, since a HistoryReadRequest is typically very small, but the response typically is not.

IF you are using the HistoryRead with ReadRawModifiedDetails (https://reference.opcfoundation.org/Core/docs/Part11/6.4.3/) AND set all 3 values (startTime, endTime, numValuesPerNode), you can use a lower number in numValuesPerNode to reduce the number of values that would be put into single HistoryReadResponse. Within our Browser application, we have usually used 1000.

If you are using trying to read the history of more than a single node (more than one value in https://reference.opcfoundation.org/Core/docs/Part4/5.10.3/ nodesToRead ), you could try reducing the number of them.

Otherwise I would need to know more specifically what parameters you used in the HistoryRead call.

October 4, 2021
19:30, EEST
Avatar
bibhudatta.sahu@honeywell.com
Member
Members
Forum Posts: 19
Member Since:
May 15, 2020
sp_UserOfflineSmall Offline

Hello,

I am using below API to make HistoryRead call.

uaClient.historyReadRaw(NodeId, DateTime, DateTime, UnsignedInteger, boolean, NumericRange, TimeStampToReturn);

=> uaClient.historyReadRaw(nodeId, start_time, end_time, numOfValuesPerNode, return_bounds, index_range, timestamp_to_return);

I modified numOfValuesPerNode to 1. i.e UnsignedInteger numOfValuesPerNode=UnsignedInteger.getFromBits(1);

Still, I am facing the same exception.

Also, while reading the histories I am getting below error in server logs.

[Info] 182.198.1.11:64292: Message type ns=0;i=664 with SL state Established
[Error] Sent TL error 0x80080000
[Info] Ended connection from182.198.1.11:64292
[Info] Accepted connection from 182.198.1.11:64295
[Info] 182.198.1.11:64295: SL security token 1000 issued for channel 1 with security policy None
[Info] 182.198.1.11:64295: Message type ns=0;i=467 with SL state Opening
[Info] 182.198.1.11:64295: Message type ns=0;i=631 with SL state Established

Thanks,
Bibhudatta Sahu

October 6, 2021
10:03, EEST
Avatar
Bjarne Boström
Moderator
Moderators
Forum Posts: 684
Member Since:
April 3, 2012
sp_UserOfflineSmall Offline

Hmm…

IF you have the option to send Wireshark logs to uajava-support@prosysopc.com, we can take a look, but if it is really the server side determining the message is too large to encode I’m not sure is there much we can do. However, this would verify that it is really the server side having the problem.

What are the start and end time? Do you know by some other means how much data there would be within that period? Is a single value how large, like in practice it should not matter, unless it is some absurdly big Structure (that a single value would be too much to encode)? Do you have option to ask the manufacturer of the server? Maybe the server just ignores the numOfValuesPerNode option (just a theory though)? Can you try reading the history with a timeperiod that would just have a single value?

October 11, 2021
12:21, EEST
Avatar
bibhudatta.sahu@honeywell.com
Member
Members
Forum Posts: 19
Member Since:
May 15, 2020
sp_UserOfflineSmall Offline

Hello,

It seems the issue is on the server-side. Whenever we are using startDate as 1-1-2014 we are not able to read histories. But whenever we are giving the startData as the same date as endDate (the difference between startDate and endDate is 10hours.) then we are able to get the histories.

October 11, 2021
14:02, EEST
Avatar
Bjarne Boström
Moderator
Moderators
Forum Posts: 684
Member Since:
April 3, 2012
sp_UserOfflineSmall Offline

Ok, then I would recommend contacting the server manufacturer. I think it might just ignore the numOfValuesPerNode setting.

Forum Timezone: Europe/Helsinki

Most Users Ever Online: 267

Currently Online:
14 Guest(s)

Currently Browsing this Page:
1 Guest(s)

Top Posters:

hbrackel: 111

pramanj: 86

ibrahim: 74

kapsl: 57

gjevremovic: 49

TimK: 41

fred: 41

Xavier: 40

Fransua33: 39

rocket science: 36

Member Stats:

Guest Posters: 0

Members: 1458

Moderators: 17

Admins: 1

Forum Stats:

Groups: 3

Forums: 15

Topics: 1178

Posts: 4983

Newest Members:

ThomasM, louiecrews, wyattcutler005, kristin3354, augustawalpole3, everettpulver, arron51869, roseannagoldschm, moosm, islamaddox

Moderators: Jouni Aro: 906, Otso Palonen: 32, Tuomas Hiltunen: 5, janimakela: 0, Pyry: 1, Terho: 0, Petri: 0, Bjarne Boström: 684, Heikki Tahvanainen: 402, Jukka Asikainen: 1, moldzh08: 0, Jimmy Ni: 24, Teppo Uimonen: 21, Markus Johansson: 36, Niklas Nurminen: 0, Matti Siponen: 151, Lusetti: 0

Administrators: admin: 1