Please tell me about the continuous control method ^{CODESYS Forge talk (Thread)}
Please tell me about the continuous control method
Last updated: 2019-04-11

Reference: Fehler in der Hilfe? ("Method Invocation") ^{CODESYS Forge talk (Thread)}
Reference: Fehler in der Hilfe? ("Method Invocation")
Last updated: 2011-09-07

How to Hide Action or Method of FB ^{CODESYS Forge talk (Thread)}
How to Hide Action or Method of FB
Last updated: 2020-02-04

How can I use the "IoDrvEtherCAT.GetStatistics" method ^{CODESYS Forge talk (Thread)}
How can I use the "IoDrvEtherCAT.GetStatistics" method
Last updated: 2021-12-20

How to stay in a method until something is finished. ^{CODESYS Forge talk (Thread)}
How to stay in a method until something is finished.
Last updated: 2025-11-04

C0138: No matching 'FB_Init' method found for instantiation of VisuClientObjectMgr ^{CODESYS Forge talk (Thread)}
C0138: No matching 'FB_Init' method found for instantiation of VisuClientObjectMgr
Last updated: 2025-12-18

Post by alexschooneveld on OPC UA PubSub SL 1.3 — UADP WriterGroup with assigned PSS.SecurityGroup still publishes plaintext ^{CODESYS Forge talk (Post)}
I am currently investigating an OPC UA PubSub connection over UDP. When I don't use encryption, the publish and subscribe are working correctly. But with encryption it does not. Environment OPC UA PubSub SL 1.3.0.0 (namespace UADP) OPC UA PubSub Security 1.3.0.0 (namespace PSS) OPC UA PubSub Base 1.3.0.0 (namespace PSB, incl. PSS.SecurityGroup / PSS.CONFIG) Programmatic PubSub in a CFC: UADP.Configuration → UADP.Connection → UADP.writerGroup → UADP.writer → writerDataSet, plus a CyclicCall gated by xEnable. Goal: publish secured UADP, SignAndEncrypt, policy PubSub-Aes256-CTR. What I do (one-shot, before xEnable := TRUE): fbSecurityGroup.SetInitialValue( 'http://opcfoundation.org/UA/SecurityPolicy#PubSub-Aes256-CTR', PSB.SECURITY.SIGNING_AND_ENCRYPTION); stSecurityCfg := fbSecurityGroup.GetConfig(eErrorID => eError); // eError=NO_ERROR, udiEncryptionKeySize=32 eError := fbSecurityGroup.SetSecurityKeys(udiTokenId, ADR(abyKey), SIZEOF(abyKey), 2436001000); // eError=NO_ERROR, SIZEOF=68 // writerGroup.itfSecurityGroup := fbSecurityGroup -- set in the WriterGroup block's Parameters (a per-scan code write got overwritten) What I verified eError = NO_ERROR after both GetConfig and SetSecurityKeys; udiEncryptionKeySize = 32. Key length = 68 bytes (signing 32 ‖ encrypt 32 ‖ nonce 4). itfSecurityGroup is set via the WriterGroup's Parameters (so it isn't clobbered each scan). Init runs before xEnable (the writer doesn't run with xEnable=FALSE). The UADP.writerGroup FB exposes only itfSecurityGroup for security — no SecurityMode/MessageSecurityMode property. Result: the published datagrams are still plaintext — ExtendedFlags1 = 0x01 (security bit 0x10 clear), no security header: b1 01 29 00 0f 16 00 … (PublisherId 41, WriterGroupId 22, RawData, no security) Questions With UADP.writerGroup, is assigning a configured + keyed PSS.SecurityGroup to itfSecurityGroup sufficient to enable message security, or is there an additional step/property/method to switch the WriterGroup to SignAndEncrypt? At what point in the WriterGroup lifecycle is itfSecurityGroup read? Must it be assigned/keyed before xActive, and does the group need a stop→start to pick it up? Is there a required call order, and does SetSecurityKeys need to be called once or repeatedly? Should security be configured on the Connection/Configuration level rather than (or in addition to) the WriterGroup? Is there a working example of secured (SignAndEncrypt) programmatic UADP publishing with this library, or a known limitation in 1.3? How can I read back at runtime whether security is actually active (via itfDiagnostics or similar)? Additional information I can confirm that the consumer side works — i.e. a standard subscriber decrypts the same keys fine — so the keys/profile aren't the issue. The Wireshark capture of the published message is: 0000 b1 01 29 00 0f 16 00 df 0d bb 25 01 00 0e 00 1b ..).......%..... 0010 0e 00 00 00 00 00 00 00 ........
Last updated: 2026-06-22

Post by alexschooneveld on OPC UA PubSub SL 1.3 — UADP WriterGroup with assigned PSS.SecurityGroup still publishes plaintext ^{CODESYS Forge talk (Post)}
I am currently investigating an OPC UA PubSub connection over UDP. When I don't use encryption, the publish and subscribe are working correctly. But with encryption it does not. Environment OPC UA PubSub SL 1.3.0.0 (namespace UADP) OPC UA PubSub Security 1.3.0.0 (namespace PSS) OPC UA PubSub Base 1.3.0.0 (namespace PSB, incl. PSS.SecurityGroup / PSS.CONFIG) Programmatic PubSub in a CFC: UADP.Configuration → UADP.Connection → UADP.writerGroup → UADP.writer → writerDataSet, plus a CyclicCall gated by xEnable. Goal: publish secured UADP, SignAndEncrypt, policy PubSub-Aes256-CTR. What I do (one-shot, before xEnable := TRUE): fbSecurityGroup.SetInitialValue( 'http://opcfoundation.org/UA/SecurityPolicy#PubSub-Aes256-CTR', PSB.SECURITY.SIGNING_AND_ENCRYPTION); stSecurityCfg := fbSecurityGroup.GetConfig(eErrorID => eError); // eError=NO_ERROR, udiEncryptionKeySize=32 eError := fbSecurityGroup.SetSecurityKeys(udiTokenId, ADR(abyKey), SIZEOF(abyKey), 2436001000); // eError=NO_ERROR, SIZEOF=68 // writerGroup.itfSecurityGroup := fbSecurityGroup -- set in the WriterGroup block's Parameters (a per-scan code write got overwritten) What I verified eError = NO_ERROR after both GetConfig and SetSecurityKeys; udiEncryptionKeySize = 32. Key length = 68 bytes (signing 32 ‖ encrypt 32 ‖ nonce 4). itfSecurityGroup is set via the WriterGroup's Parameters (so it isn't clobbered each scan). Init runs before xEnable (the writer doesn't run with xEnable=FALSE). The UADP.writerGroup FB exposes only itfSecurityGroup for security — no SecurityMode/MessageSecurityMode property. Result: the published datagrams are still plaintext — ExtendedFlags1 = 0x01 (security bit 0x10 clear), no security header: b1 01 29 00 0f 16 00 … (PublisherId 41, WriterGroupId 22, RawData, no security) Questions With UADP.writerGroup, is assigning a configured + keyed PSS.SecurityGroup to itfSecurityGroup sufficient to enable message security, or is there an additional step/property/method to switch the WriterGroup to SignAndEncrypt? At what point in the WriterGroup lifecycle is itfSecurityGroup read? Must it be assigned/keyed before xActive, and does the group need a stop→start to pick it up? Is there a required call order, and does SetSecurityKeys need to be called once or repeatedly? Should security be configured on the Connection/Configuration level rather than (or in addition to) the WriterGroup? Is there a working example of secured (SignAndEncrypt) programmatic UADP publishing with this library, or a known limitation in 1.3? How can I read back at runtime whether security is actually active (via itfDiagnostics or similar)? Additional information I can confirm that the consumer side works — i.e. a standard subscriber decrypts the same keys fine — so the keys/profile aren't the issue. The Wireshark capture of the published message is: 0000 b1 01 29 00 0f 16 00 df 0d bb 25 01 00 0e 00 1b ..).......%..... 0010 0e 00 00 00 00 00 00 00 ........
Last updated: 2026-06-22

Post by astrum on OPC UA Information Model Error "Dimensions must be empty" ^{CODESYS Forge talk (Post)}
Hello everyone, does anyone know what this error means: Internal Error in code generation for http://opcfoundation.org/UA/DI/: Dimensions must be empty. I use the standard information models from Codesys and haven't even called the Information Model, but my program can't compile. the only thing I did was to insert the Communication Manage.
Last updated: 2025-08-11

Library download server and library update ^{CODESYS Forge talk (Thread)}
Library download server and library update
Last updated: 2021-09-14

RPI is license server down ^{CODESYS Forge talk (Thread)}
RPI is license server down
Last updated: 2023-10-30

Change modbus server parameters from program ^{CODESYS Forge talk (Thread)}
Change modbus server parameters from program
Last updated: 2024-07-16

Change modbus server parameters from program ^{CODESYS Forge talk (Thread)}
Change modbus server parameters from program
Last updated: 2024-07-17

Modbus Server TCP -error code ^{CODESYS Forge talk (Thread)}
Modbus Server TCP -error code
Last updated: 2024-10-21

MODBUS TCP SERVER DONT AUTO-STARTUP ^{CODESYS Forge talk (Thread)}
MODBUS TCP SERVER DONT AUTO-STARTUP
Last updated: 2025-07-15

MODBUS TCP SERVER DON'T AUTOMATIC STARTUP ^{CODESYS Forge talk (Thread)}
MODBUS TCP SERVER DON'T AUTOMATIC STARTUP
Last updated: 2025-07-21

MOdbus TCP Server Unit ID ^{CODESYS Forge talk (Thread)}
MOdbus TCP Server Unit ID
Last updated: 2022-07-20

Bootproject, TCP Server and booting ^{CODESYS Forge talk (Thread)}
Bootproject, TCP Server and booting
Last updated: 2017-01-13

Changing Modbus server IP in runtime ^{CODESYS Forge talk (Thread)}
Changing Modbus server IP in runtime
Last updated: 2019-10-11

Wifi/DHCP server from Rpi3 ? ^{CODESYS Forge talk (Thread)}
Wifi/DHCP server from Rpi3 ?
Last updated: 2016-06-10

FTP server and security ^{CODESYS Forge talk (Thread)}
FTP server and security
Last updated: 2017-06-29

PLC as POP3 Mail Receive Server ^{CODESYS Forge talk (Thread)}
PLC as POP3 Mail Receive Server
Last updated: 2023-06-14

Running CODESYS headless as a Server? ^{CODESYS Forge talk (Thread)}
Running CODESYS headless as a Server?
Last updated: 2021-07-07

Using your own library download server ^{CODESYS Forge talk (Thread)}
Using your own library download server
Last updated: 2019-03-07

Automation Server and e!Cockpit ^{CODESYS Forge talk (Thread)}
Automation Server and e!Cockpit
Last updated: 2020-08-04

Sort by relevance or date