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 yannickasselin on Lenze i950 Servo and WAGO PFC200 ^{CODESYS Forge talk (Post)}
In order to use SoftMotion Light, a servo drive needs to support CiA 402 operating modes: Profile Position (PP), Profile Velocity (PV) and Homing Mode (HM). https://content.helpme-codesys.com/en/CODESYS%20SoftMotion%20Light/_sm_light_requirements.html According to the Lenze i950 documentation you linked in your post, none of these modes are supported. Not even Homing Mode which explains why MC_Home does not work even with the full SoftMotion. The full SoftMotion uses Cyclic Synchronous Position Mode (CSP) but still uses Homing Mode (HM) when using MC_Home. You can monitor PDO 0x6060 (Mode of Operation). When using SoftMotion Light you will see it set to 1 (PP) for a MC_MoveAbsolute_SML and MC_MoveRelative_SML and to 3 (PV) for MC_MoveVelocity_SML and to 6 (HM) for MC_Home_SML. When using the SoftMotion instructions, it will pretty much always be set to 8 (CSP) except when using MC_Home, then it will be set to 6 (HM).
Last updated: 2026-02-13

How to configure CODESYSControl_User.cfg in order to use a specific network card for OPCUA Server ^{CODESYS Forge talk (Thread)}
How to configure CODESYSControl_User.cfg in order to use a specific network card for OPCUA Server
Last updated: 2023-08-28

Post by martinlithlith on CODESYS Control for Raspberry Pi SL on Raspberry Pi 4b ^{CODESYS Forge talk (Post)}
Hi! Thanks for your reply! I'll have a go then!
Last updated: 2023-09-06

Ethercat scan for devices not picking up EL7041 as a softmotion axis ^{CODESYS Forge talk (Thread)}
Ethercat scan for devices not picking up EL7041 as a softmotion axis
Last updated: 2023-09-18

Is it possible to replace a table row header for a text in a text list? ^{CODESYS Forge talk (Thread)}
Is it possible to replace a table row header for a text in a text list?
Last updated: 2021-10-21

Which kinds of data is transferred with 'Scan for devices' command? ^{CODESYS Forge talk (Thread)}
Which kinds of data is transferred with 'Scan for devices' command?
Last updated: 2020-12-14

Codesys 3.5.19 Control Win x64 - network adapter for EtherCAT master not working ^{CODESYS Forge talk (Thread)}
Codesys 3.5.19 Control Win x64 - network adapter for EtherCAT master not working
Last updated: 2023-11-22

Migration von "CODESYS Control for PFC200 SL" zu WAGO FW26 "CODESYS V3.5.19.2" ^{CODESYS Forge talk (Thread)}
Migration von "CODESYS Control for PFC200 SL" zu WAGO FW26 "CODESYS V3.5.19.2"
Last updated: 2023-11-23

How to configure gateway for programming RPi 2B using Codesys ^{CODESYS Forge talk (Thread)}
How to configure gateway for programming RPi 2B using Codesys
Last updated: 2024-07-10

Extended Alarm description for a alarm selected in Alarm Table ^{CODESYS Forge talk (Thread)}
Extended Alarm description for a alarm selected in Alarm Table
Last updated: 2024-07-16

Post by vladimirsmall on Send data to USB ^{CODESYS Forge talk (Post)}
Hello/ Need send some file ( for example Array of string) to USB. Which library need used for this. Thank you
Last updated: 2024-07-20

TargetVisu for Linux Package on runtime 4.12.0.0 install error due to Qt dependencies. ^{CODESYS Forge talk (Thread)}
TargetVisu for Linux Package on runtime 4.12.0.0 install error due to Qt dependencies.
Last updated: 2024-08-27

Post by eschwellinger on EThercat Dynamic configuration ^{CODESYS Forge talk (Post)}
start point for doing this is for sure this example here: https://content.helpme-codesys.com/en/libs/EtherCATStack/Current/EtherCATStack/pou-ETCMasterStack/DynamicConfig/fld-DynamicConfig.html
Last updated: 2024-10-16

Temu Coupon Code North Carolina {USA} ⤠ ["^act900074^"] for New and Existing Customers ^{CODESYS Forge talk (Thread)}
Temu Coupon Code North Carolina {USA} ⤠ ["^act900074^"] for New and Existing Customers
Last updated: 2024-10-25

Temu Coupon Code Missouri {USA} ➵ ["^acq615756^"] for New and Existing Customers ^{CODESYS Forge talk (Thread)}
Temu Coupon Code Missouri {USA} ➵ ["^acq615756^"] for New and Existing Customers
Last updated: 2024-10-25

Latest TopCashback deals: $35 for new members sign-up Bonus(October 2024) ^{CODESYS Forge talk (Thread)}
Latest TopCashback deals: $35 for new members sign-up Bonus(October 2024)
Last updated: 2024-10-25

Temu Coupon Code New York {USA} ⤘ ["^acq615756^"] for New App Users ^{CODESYS Forge talk (Thread)}
Temu Coupon Code New York {USA} ⤘ ["^acq615756^"] for New App Users
Last updated: 2024-10-25

Temu Coupon Code Florida {USA} ↪ ["^acq717533^"] for New and Existing Customers ^{CODESYS Forge talk (Thread)}
Temu Coupon Code Florida {USA} ↪ ["^acq717533^"] for New and Existing Customers
Last updated: 2024-10-25

Temu Coupon Code Kentucky {USA} ➤ ["^acs597987^"] for New and Existing Customers ^{CODESYS Forge talk (Thread)}
Temu Coupon Code Kentucky {USA} ➤ ["^acs597987^"] for New and Existing Customers
Last updated: 2024-10-25

Temu Coupon Code Alabama {USA} → ["^acr900074^"] for New and Existing Customers ^{CODESYS Forge talk (Thread)}
Temu Coupon Code Alabama {USA} → ["^acr900074^"] for New and Existing Customers
Last updated: 2024-10-25

Temu Coupon Code Ohio {USA} ⥓ ["^acs900074^"] for First Order + Free Shipping ^{CODESYS Forge talk (Thread)}
Temu Coupon Code Ohio {USA} ⥓ ["^acs900074^"] for First Order + Free Shipping
Last updated: 2024-10-25

Temu Coupon Code Nebraska {USA} ⟹ ["^acs615756^"] for First Order + Free Shipping ^{CODESYS Forge talk (Thread)}
Temu Coupon Code Nebraska {USA} ⟹ ["^acs615756^"] for First Order + Free Shipping
Last updated: 2024-10-25

Temu Coupon Code Oregon {USA} ⥤ ["^acq717533^"] for New and Existing Customers ^{CODESYS Forge talk (Thread)}
Temu Coupon Code Oregon {USA} ⥤ ["^acq717533^"] for New and Existing Customers
Last updated: 2024-10-25

Sort by relevance or date