PFC200 - Modbus TCP Server ^{CODESYS Forge talk (Thread)}
PFC200 - Modbus TCP Server
Last updated: 2020-08-03

Versionsverwaltung mit ENI-Server ^{CODESYS Forge talk (Thread)}
Versionsverwaltung mit ENI-Server
Last updated: 2012-11-08

TCP/IP Server Listening ^{CODESYS Forge talk (Thread)}
TCP/IP Server Listening
Last updated: 2015-06-25

FTP - Server ? ^{CODESYS Forge talk (Thread)}
FTP - Server ?
Last updated: 2009-01-09

Codesys Automation Server ^{CODESYS Forge talk (Thread)}
Codesys Automation Server
Last updated: 2018-05-30

TCP Server code ^{CODESYS Forge talk (Thread)}
TCP Server code
Last updated: 2017-06-20

Add to server ( error:ok ) ^{CODESYS Forge talk (Thread)}
Add to server ( error:ok )
Last updated: 2021-06-06

USB Dongle Server ^{CODESYS Forge talk (Thread)}
USB Dongle Server
Last updated: 2022-06-17

Getaway DDE Server ^{CODESYS Forge talk (Thread)}
Getaway DDE Server
Last updated: 2006-05-02

FTP Client-server problem ^{CODESYS Forge talk (Thread)}
FTP Client-server problem
Last updated: 2017-01-30

Gateway DDE Server ^{CODESYS Forge talk (Thread)}
Gateway DDE Server
Last updated: 2006-06-12

Softwareverwaltung mit ENI Server ^{CODESYS Forge talk (Thread)}
Softwareverwaltung mit ENI Server
Last updated: 2018-01-02

ENI Server ^{CODESYS Forge talk (Thread)}
ENI Server
Last updated: 2015-06-09

OPCUA Server Users Manager ^{CODESYS Forge talk (Thread)}
OPCUA Server Users Manager
Last updated: 2018-07-06

Beispielapplikation ENI-Server Zugriff ^{CODESYS Forge talk (Thread)}
Beispielapplikation ENI-Server Zugriff
Last updated: 2010-04-22

ENI Server Download ^{CODESYS Forge talk (Thread)}
ENI Server Download
Last updated: 2017-01-16

Uninstall ENI Server ^{CODESYS Forge talk (Thread)}
Uninstall ENI Server
Last updated: 2007-10-04

BacNet Server ^{CODESYS Forge talk (Thread)}
BacNet Server
Last updated: 2024-02-20

Continuous Build Server ^{CODESYS Forge talk (Thread)}
Continuous Build Server
Last updated: 2024-03-15

Data to server ^{CODESYS Forge talk (Thread)}
Data to server
Last updated: 2025-11-11

TCP Server ^{CODESYS Forge talk (Thread)}
TCP Server
Last updated: 2025-12-01

Post by cihangur on OpC UA server on Raspberry Pi 64 SL runtime ^{CODESYS Forge talk (Post)}
Hello everyone, I wanted to write here because it is a similar and the most up-to-date topic. I want to connect to CoDeSys Win V3 x64 - 3.5.19.50 with OPC UA using WinCC Advanced V17. (Or to a PLC with CoDeSys Version 4.10.0.0) My settings are exactly the same as the previous comment. I even tried many different settings. I can access all CoDeSys OPC UA variables via TIA Portal IDE and add them to my HMI tags. When WinCC RT Advanced is started, it gives a warning that the connection could not be established and does not update the variables. I can connect to Inovance AM600 using CoDeSys Target version 3.5.11.50. (The same version Win x64 is also connected.) However, a security setting in the current versions prevents me. I would be very happy if those who have up-to-date experience on this issue and find a solution share it. The CoDeSys Security Settings which I can access variables with TIA Portal: CommunicationPolicy: POLICY_BASICSHA256SHA256 CommunicationMode: ALL Activation: Activated UserAuthentication: ENABLED Server Certificate: Valid until 2034 Greetings.
Last updated: 2024-12-06

Post by animesh on SoftPLC (CODESYS Control x86 RTE V3 x64) OPC UA binds only to 127.0.0.1 — Not binding to LAN IP ^{CODESYS Forge talk (Post)}
Hello everyone, I am facing a persistent issue with the OPC UA Server on Advantech Soft PLC with hard realtime for Win64 (V3_5_2010_3) and need help from the community. Device Information Name: Advantech Control x86 RTE V3 x64 Vendor: Advantech Co., Ltd. Categories: PLCs Version: 3.5.20.10 Description: Advantech Soft PLC with hard realtime for Win64 (V3_5_2010_3) Problem Summary The OPC UA Server works perfectly when accessed via: opc.tcp://localhost:4842 opc.tcp://<hostname>:4842</hostname> But it does NOT work when using the LAN IP: opc.tcp://192.168.0.XX:4842 In UAExpert I get: Discovery FindServers on opc.tcp://192.168.0.XX:4842 failed (BadCommunicationError) Port is LISTENING in windows Firewall.. Tried with turning off the firewall completely. System Information Windows 10 x64 Advantech CODESYS RTE Soft-PLC (hard real-time) Network IP: 192.168.0.XX Hostname: WINDOWS-XXXXX Need your Support
Last updated: 2025-11-24

Post by rossanoparis on How to configure CODESYSControl_User.cfg in order to use a specific network card for OPCUA Server ^{CODESYS Forge talk (Post)}
Hello at all I'd like to know how to configure CODESYSControl_User.cfg in order to use a specific network card for OPCUA Server. In the past, I tried to ask in "Forge" about this topic, but I could find neither help nor document informations about it. Reading the file "codesyscontrol.log" I see these logs OPC UA Server Started: Hostname: NTLRPICTRL01, Port: 4840 URL: opc.tcp://NTLRPICTRL01:4840 Loopbackadapter activated. **All available networkadapters are used.** Multithreading activated. 3 workers used. My controller, which is a Linux PC, has got two network cards eth0 and eth1 I whant to use the card with name "eth0" as a server for OPCUA and keep the "eth1" free for other stuffs. Is it possible ? Best regards Rossano
Last updated: 2023-08-25

OPC connection with many data ^{CODESYS Forge talk (Thread)}
OPC connection with many data
Last updated: 2014-04-26

Sort by relevance or date