Post by dogulas on OPC UA C# client connecting to OPC UA CODESYS server ^{CODESYS Forge talk (Post)}
Ok, for the sake of completeness in case anyone else has this problem. I can tell you that what finally worked for me was to change the line: // create an ExtensionObject to wrap the value to be written ExtensionObject extensionObject = new ExtensionObject( new ExpandedNodeId("GVL_StructA", 5), structAData ); to: // create an ExtensionObject to wrap the value to be written ExtensionObject extensionObject = new ExtensionObject( new ExpandedNodeId("GVL_StructA|defaultbinary", 5), structAData ); I'm sure there are many other problems that could cause this very generic error, but this was my problem.
Last updated: 2024-12-30

Post by smartcoco on Opaque NodeId in the OPC UA server ^{CODESYS Forge talk (Post)}
This seems to be because when creating 'OPC UA' with 'Communication Manager', the 'IdentifierType' of 'NodeId' cannot be configured as' String 'type. This issue is not an isolated case. For this issue, CODESYS seems to have not provided guidance to users on how to proceed. We can provide feedback on this issue in the 'My Question' section of the 'CODESYS Store' to make CODESYS take it seriously.
Last updated: 2025-01-10

Post by gediminas on Datasource OPC UA client system failure ^{CODESYS Forge talk (Post)}
I am using CODESYS v3.5 SP20 Patch 3 / Control for BeagleboneBlack SL v4.13 and after some time the OPC UA Server crashes. However, Runtime still works without any issues. The events leading up to the OPC server crash are the most suspicious: 1) Mutex deadlock detected - owner thread died, and 2) Runtime received SIGABRT. And it seems very similar with this topic except used versions - issues should be fixed with previous SP's. I can't seem to find any information about these events. Need some pointers in the right direction on how I can fix this problem.
Last updated: 2024-10-25

Post by joel214 on OPC-UA / Unterschied Symbolkonfiguration, IEC-Symbolveröffentlichung und Informationsmodell ^{CODESYS Forge talk (Post)}
Hallo liebe Community, im Rahmen einer Studienarbeit gilt es ein OPC-UA-Informationsmodell in eine existierende CODESYS-Steuerung zu implementieren. Dabei sind wir auf die Frage gestoßen welcher Unterschied zwischen den folgenden Objekten besteht: - Symbolkonfiguration (veraltet?) - IEC-Symbolveröffentlichung - Veröffentlichung über zuvor erstelltes Informationsmodell In unserem Verständnis erfüllen alle Objekte die Gleiche Aufgabe nur mit unterschiedlicher Vorgehensweise und Darstellung im OPC-UA-Server. Während durch die Symbolkonfiguration die Variablen und Instanzen über lange und verschachtelte Pfade abgelegt werden, wird durch die IEC-Symbolveröffentlichung ein Ordner im Pfad der Objekte erstellt. Dort sind die Variablen und Instanzen anschließend zu finden. Bei der Verwendung von Informationsmodellen hingegen, werden die Instanzen direkt unter den Objekten abgelegt. Für welchen Anwendungsfall ist welche Vorgehensweise am besten? Vielen Dank vorab und viele Grüße Joel
Last updated: 2024-04-09

Post by msegon on OPC UA Client failed to connect ^{CODESYS Forge talk (Post)}
Hi everyone, I would appreciate your help with a problem I've been working on for a few days but haven't been able to resolve. I'm trying to read data from Tridium Niagara 4.15 OPC UA Server, but I get the error BadCertificateInvalid. As far as I understand, you need to add a CA certificate somewhere to establish a secure connection, but I don't know where. 2025-10-27T09:06:43.247Z, 0x0000008d, 4, 0, 0, * ERROR: OpcUa_Channel_BeginConnect: Cannot create secure channel without certificates! 2025-10-27T09:06:43.247Z, 0x00001090, 4, 0, 0, * ERROR: Datasource: Error Failed (268468242) in state Connecting I tried communicating without encryption, but it doesn't find the point. Has anyone managed to establish encrypted OPC UA communication?
Last updated: 2025-10-28

Post by alexgooi on Codesys OPC DA server requires more then 2 GB of ram ^{CODESYS Forge talk (Post)}
Last updated: 2024-01-25

Post by ben1 on Trying to connect Codesys OPC server to Ignition ^{CODESYS Forge talk (Post)}
The server doesn’t allow anonymous users. You need to configure a username/password for the connection.
Last updated: 2025-01-21

CODESYS connection zu UA Expert aufbauen ^{CODESYS Forge talk (Thread)}
CODESYS connection zu UA Expert aufbauen
Last updated: 2021-12-12

OPC Client not connect. ^{CODESYS Forge talk (Thread)}
OPC Client not connect.
Last updated: 2016-05-12

OPC Help needed please ^{CODESYS Forge talk (Thread)}
OPC Help needed please
Last updated: 2017-05-29

CODESYS OPC from Store ^{CODESYS Forge talk (Thread)}
CODESYS OPC from Store
Last updated: 2018-06-19

OPC codesys ^{CODESYS Forge talk (Thread)}
OPC codesys
Last updated: 2016-01-20

CoDesys <-> OPC <-> VB6 ^{CODESYS Forge talk (Thread)}
CoDesys <-> OPC <-> VB6
Last updated: 2005-06-07

OPC Visualisierung Java ^{CODESYS Forge talk (Thread)}
OPC Visualisierung Java
Last updated: 2006-06-22

New OPC-Forum ^{CODESYS Forge talk (Thread)}
New OPC-Forum
Last updated: 2011-04-29

Codesys OPC V2.3 ^{CODESYS Forge talk (Thread)}
Codesys OPC V2.3
Last updated: 2011-05-06

Timestamps in OPC Library ^{CODESYS Forge talk (Thread)}
Timestamps in OPC Library
Last updated: 2022-01-21

OPC Kommunikation SPS<->PC ^{CODESYS Forge talk (Thread)}
OPC Kommunikation SPS<->PC
Last updated: 2007-10-17

OPC symbol file ^{CODESYS Forge talk (Thread)}
OPC symbol file
Last updated: 2011-01-28

Codesys OPC client Limit ^{CODESYS Forge talk (Thread)}
Codesys OPC client Limit
Last updated: 2012-09-25

OPC raspberry ^{CODESYS Forge talk (Thread)}
OPC raspberry
Last updated: 2016-01-26

OPC Client Connection Status ^{CODESYS Forge talk (Thread)}
OPC Client Connection Status
Last updated: 2020-02-21

OPC and Symbol Entries ^{CODESYS Forge talk (Thread)}
OPC and Symbol Entries
Last updated: 2009-05-04

Kommunikation OPC ^{CODESYS Forge talk (Thread)}
Kommunikation OPC
Last updated: 2008-11-12

OPC client ^{CODESYS Forge talk (Thread)}
OPC client
Last updated: 2008-04-28

Sort by relevance or date