OPC Communication Problems at startup ^{CODESYS Forge talk (Thread)}
OPC Communication Problems at startup
Last updated: 2011-09-16

Codesys 2 OPC server C++ exapmles ^{CODESYS Forge talk (Thread)}
Codesys 2 OPC server C++ exapmles
Last updated: 2017-04-20

OPC Server Codesys Version 3 ^{CODESYS Forge talk (Thread)}
OPC Server Codesys Version 3
Last updated: 2021-05-04

CoDeSys-OPC und die Gateway Files ^{CODESYS Forge talk (Thread)}
CoDeSys-OPC und die Gateway Files
Last updated: 2010-08-16

CODESYS 3.5.14.10 - Installation OPC-Server ^{CODESYS Forge talk (Thread)}
CODESYS 3.5.14.10 - Installation OPC-Server
Last updated: 2019-05-30

Windows Server 2008 R2 and OPC ^{CODESYS Forge talk (Thread)}
Windows Server 2008 R2 and OPC
Last updated: 2013-09-10

OPC server problem - all data bad ^{CODESYS Forge talk (Thread)}
OPC server problem - all data bad
Last updated: 2012-05-13

OPC server for CoDeSys v2.3 ^{CODESYS Forge talk (Thread)}
OPC server for CoDeSys v2.3
Last updated: 2010-01-14

SoftPLC to OPC Server ^{CODESYS Forge talk (Thread)}
SoftPLC to OPC Server
Last updated: 2015-10-30

OPC Server V 3.5, symbole file ^{CODESYS Forge talk (Thread)}
OPC Server V 3.5, symbole file
Last updated: 2012-05-13

Steuerung mit OPC an Panel ^{CODESYS Forge talk (Thread)}
Steuerung mit OPC an Panel
Last updated: 2006-10-25

Visualisierung mit WinCC über OPC-Server ^{CODESYS Forge talk (Thread)}
Visualisierung mit WinCC über OPC-Server
Last updated: 2007-10-11

opc server loads old symbols ^{CODESYS Forge talk (Thread)}
opc server loads old symbols
Last updated: 2011-05-31

CoDeSyS OPC DA stops working ^{CODESYS Forge talk (Thread)}
CoDeSyS OPC DA stops working
Last updated: 2023-12-21

How to change OPC NodeId IdentifierType ^{CODESYS Forge talk (Thread)}
How to change OPC NodeId IdentifierType
Last updated: 2024-09-20

OPC server crashes the PLC ^{CODESYS Forge talk (Thread)}
OPC server crashes the PLC
Last updated: 2024-11-27

Codesys als Softsps mit UA expert verbinden ^{CODESYS Forge talk (Thread)}
Codesys als Softsps mit UA expert verbinden
Last updated: 2022-05-16

Post by mainak on Opaque NodeId in the OPC UA server ^{CODESYS Forge talk (Post)}
Hello all, I am using the OPC UA server with my custom information model. I have used the communication manager to add my information model under my application and created instances from OPC UA types. I see that the created instances in the OPC UA server has some opaque nodeid (attached screenshot) and I want to change that. Therefore I have the following questions: 1. Is there a way to configure the NodeIds of instances in the OPC UA server? I tried to edit it using the UaExpert client but got error "BadNotWriteable". is it possible to configure it somewhere so that the nodeids can be changed using an external client? 2. Is there a way to define the rule for creating instance nodeids within the codesys IDE? 3. Is it possible to create the instances before e.g. using a modelling tool like UaModeler and import them as part of the information model and use them later? Using the communication manager, I can only create instances from types. I couldn't find a way to map my existing instances to plc tags from my application. It would be nice if someone could help me with these issues. Thanks in advance. :)
Last updated: 2024-10-19

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 peterned on Programatically restart Codesys OPC UA server? ^{CODESYS Forge talk (Post)}
Hi, I'm using a Festo Codesys PLC (CPX-CEC-C1-V3), which is connected to a HMI panel. Both exchange data via OPC UA. Occasionally, the HMI stops displaying data, and looks as if there is no connection. If the HMI stops, the only way to make it work again is to restart the PLC. Restarting HMI has no effect. When the PLC is restarted, HMI starts working normally again. Is it possible to restart the OPC UA server from PLC code? I hope this will make fixing the HMI possible without a PLC restart. Thanks
Last updated: 2024-07-19

Post by alimans on OPC-UA Server, Symbol Set: Raise an error: Object reference not set to an instance of an object. ^{CODESYS Forge talk (Post)}
Hi everyone, I just created a very simple library without any code and, added it to my very simple project. after adding this library, I get an error when I try to open "Symbol Set" in "OPC UA Server" in "Communication Manager". Here is the code of my POU in the library: FUNCTION_BLOCK POU VAR eCommand : (CMD_NONE:=0, CMD_RESET:=-1) INT := CMD_NONE; END_VAR Attached is the error that I get. I also noticed that by removing the enumeration variable above (eCommand), I can open the "Symbol Set" again. Anybody has any idea why this error is raised and how could I use enumeration variables without error in "OPC UA Symbol Set"?
Last updated: 2024-08-08

Post by vformanek on Datasource OPC UA Client error ID:7012 ^{CODESYS Forge talk (Post)}
Hey, I am facing the same problem. Basically UA Expert and other programs work fine with the login credentials. But codesys can not use them properly. I can see the server login to it manually but when I download the program and run the datasource never runs... Currently I am facing the same Error ID: 7012 and cant get it running properly.
Last updated: 2023-11-21

Post by anuj9326 on OPC-UA Client connection, Linux SL /Raspberry Pi ^{CODESYS Forge talk (Post)}
hello edwin i have did the same and i could connect the opc-ua server but i dont see anything in the resources tree, in the application i linked my variables to the symbol configuration but i dont see that in the uaexpert. if i use the same application with a non linux system i can get those variables values and see the complete tree structure. What could be the problem ?
Last updated: 2024-08-21

Post by anuj9326 on OPC-UA Client connection, Linux SL /Raspberry Pi ^{CODESYS Forge talk (Post)}
hello edwin i have did the same and i could connect the opc-ua server but i dont see anything in the resources tree, in the application i linked my variables to the symbol configuration but i dont see that in the uaexpert. if i use the same application with a non linux system i can get those variables values and see the complete tree structure. What could be the problem ?
Last updated: 2024-08-21

Post by thn-power on How to change OPC NodeId IdentifierType ^{CODESYS Forge talk (Post)}
Hi Yet another OPC UA question. When setting up a OPC server using "Communcation manager" (Symbol set and information model) in Codesys the NodeId is always given as "opaque" type. At least when browsing using UAExpert. Other standard OPC objects use numeric (or string) identifier, but for some reason my variables seems to get opaque/binary type. See attached photo. How can I change this? I can't see that this is a parameter in the CodesysControl.cfg. Can this be specified in the information model nodeset? And is it possible to specify the exact numeric or string NodeId for each instance? And on a related topic, is there a way to export the OPC server nodeId's with variable name so that it can be imported in a OPC Client? The .xml files in the project folder does not seem to contain the NodeId.
Last updated: 2024-09-20

Sort by relevance or date