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
Bad_CommunicationError meaning
June 29, 2023
18:30, EEST
Avatar
martin_prosys
Member
Members
Forum Posts: 14
Member Since:
January 27, 2022
sp_UserOfflineSmall Offline

Hi everyone,

we are using Prosys’ OPC UA SDK for Java and we are sometimes getting “Bad_CommunicationError – A low level communication error occurred.” error when trying to subscribe for updates from a given PLC (all communication goes through a third-party OPC server – Tani). Can someone provide additional information about what this error means and how it can be fixed?

Thanks! 🙂

June 30, 2023
8:36, EEST
Avatar
Matti Siponen
Moderator
Members

Moderators
Forum Posts: 321
Member Since:
February 11, 2020
sp_UserOfflineSmall Offline

Hello,

The OPC UA Specification defines the following use case for StatusCode Bad_CommunicationError:

For Subscriptions that contain Conditions for which the failure applies, the effected Conditions generate an Event, if the Retain field is set to True. These Events shall have their Event fields that are associated with the communication failure contain a StatusCode of Bad_CommunicationError for the value. (https://reference.opcfoundation.org/Core/Part9/v104/docs/5.15)

That is the only defined use case for Bad_CommunicationError in the “core” OPC UA specification. Companion Specifications might define additional use cases.

The general definition for StatusCode Bad_CommunicationError is: “A low level communication error occurred” (https://reference.opcfoundation.org/Core/Part4/v104/docs/7.34.2). The specification does not define more specifically in which situations this StatusCode should be used. In the case of Prosys OPC UA SDK for JAVA, the StatusCode is used parsing a ByteString from the received chunk fails or when all SecurityTokens of a SecureChannel have expired for example. Server applications developed by other manufacturers could be using this StatusCode in different situations.

Therefore, Bad_CommunicationError does not have a well defined meaning and it is practically impossible to tell the exact error based solely on it.

Do you have any additional information on the error such as logs from the Client or the Server? Or a Wireshark capture of messages exchanged between the applications? If you do, you can send those to uajava-support at prosysopc.com so that we can take a look them.

Since you mentioned that you’re trying to subscribe to data from a PLC via a 3rd party OPC UA Server, it could be possible that this StatusCode is used to indicate that there is some communication error between that Server and the PLC, but this is purely a speculation and the real error could be something else. Though, I would recommend you to also contact the manufacturer of the 3rd party Server about this error as well.

Forum Timezone: Europe/Helsinki

Most Users Ever Online: 518

Currently Online:
7 Guest(s)

Currently Browsing this Page:
1 Guest(s)

Top Posters:

hbrackel: 135

pramanj: 86

Francesco Zambon: 81

rocket science: 77

Ibrahim: 76

Sabari: 62

kapsl: 57

gjevremovic: 49

Xavier: 43

TimK: 41

Member Stats:

Guest Posters: 0

Members: 684

Moderators: 16

Admins: 1

Forum Stats:

Groups: 3

Forums: 15

Topics: 1467

Posts: 6261

Newest Members:

LouieWreve, Kickbiche, karrimacvitie5, graciela2073, sagarchau, elviralangwell4, Donnavek, Eddiefauth, DonaldPooma, fidelduke938316

Moderators: Jouni Aro: 1010, 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