blog Discussion
williamcorlin
blog
(Discussion)
Forum for blog comments
Last updated: 2026-07-14
(no subject)
williamcorlin
wiki
(Thread)
Last updated: 2026-07-14
Post by williamcorlin on The future and proper use of CAA.BOLT, CAA.SEMA,..
CODESYS Forge
talk
(Post)
I've been moving in the same direction. For new libraries, I'm trying to minimize dependencies on APIs that look like they're being phased out unless the documentation explicitly recommends them. For synchronization primitives like CAA.BOLT and CAA.SEMA, I'd love to see an official replacement or abstraction layer that's guaranteed to remain stable across runtimes. That would make library development much cleaner than relying on platform-specific SysLib* implementations or conditional compilation everywhere. Until there's clearer guidance, my approach has been to isolate the locking mechanism behind a small wrapper interface. If CODESYS changes the recommended API in the future, only that wrapper needs to be updated instead of every library that uses it. It isn't perfect, but it's made maintenance much easier. https://forge.codesys.com/forge/talk/Engineering/thread/e6c20a740e/ https://zapgames.io/
Last updated: 2026-07-14
The future and proper use of CAA.BOLT, CAA.SEMA,..
CODESYS Forge
talk
(Thread)
The future and proper use of CAA.BOLT, CAA.SEMA,..
Last updated: 2026-07-14
Home
williamcorlin
wiki
(WikiPage)
Project Members: williamcorlin (admin)
Last updated: 2026-07-14
Home
traffic-control
home
(WikiPage)
Project Members: e13740e (admin)
Last updated: 2026-07-15
(no subject)
traffic-control
home
(Thread)
Last updated: 2026-07-15
files Discussion
traffic-control
files
(Discussion)
Forum for files comments
Last updated: 2026-07-15
link Discussion
traffic-control
link
(Discussion)
Forum for link comments
Last updated: 2026-07-15
traffic-control SVN repository
traffic-control
code
(SVN Repository)
Last updated: 2026-07-15
code Discussion
traffic-control
code
(Discussion)
Forum for code comments
Last updated: 2026-07-15
Post by tristan on Codesys v3.5.22.10 - Internal error:System.AggregateException...Value cannot be null...Parameter name: expLValue
CODESYS Forge
talk
(Post)
Hi, I have exactly the same issue when I try to update from 3.5.21.50 to 3.5.22.20. Currently I didn't find where is the problem. Hope somebody can find a way. Tristan
Last updated: 2026-07-17
Home (version 1) discussion
ccorns
wiki
(Thread)
Home (version 1) discussion
Last updated: 2026-07-17
Home
mecivietnam
wiki
(WikiPage)
Project Members: mecivietnam (admin)
Last updated: 2026-07-17
Post by kuegerls on PROFINET Controller SL: WRREC remains BUSY forever, no DCE/RPC packets transmitted (RevPi Connect 5 + NORD SK205E)
CODESYS Forge
talk
(Post)
Hello , I am currently evaluating the CODESYS PROFINET Controller SL on a Revolution Pi Connect 5 and have encountered a problem with acyclic PROFINET Record Access (WRREC/RDREC). System Hardware: Revolution Pi Connect 5 Runtime: CODESYS Control 4.16.0.0 (SDK 3.5.21.10) Development System: CODESYS V3.5 SP21 (64-bit) CommFB: 3.5.17.10 ProfinetCommon: 4.6.0.0 PROFINET Controller Device: PN-Controller 4.6.0.0 PROFINET Device: NORD DRIVESYSTEMS SK205E with SK TU4-PNT GSDML: GSDML-V2.46-NORDDRIVESYSTEMS-PNT-20251016.xml Network The PROFINET network is completely separated from the office network. RevPi: eth0 → Office network eth1 → PROFINET wlan0 → Visualization The PN Controller is configured to use eth1. IP configuration: RevPi (eth1): 192.168.100.1/24 NORD Drive: 192.168.100.3 Connection is established successfully. Current Status The PN Controller reports: Controller Status = Run Online = TRUE IP Active = TRUE Connections = 1 Cyclic PROFINET IO communication works correctly. Problem I am trying to access PKW parameters via WRREC (Record Index 100). The request buffer contains: 01 14 00 04 92 00 00 00 00 00 00 which corresponds to Reference = 0x01 Request = Read Axis = 0 Parameter = 170 + 1000 Subindex = 0 Value = 0 The WRREC call is fbWRREC( REQ := xWrReq, ID := ConnectionID, INDEX := 100, LEN := 11, RECORD := ADR(TxBuffer) ); REQ is pulsed for one PLC cycle only. Observed Behaviour WRREC enters BUSY state and never finishes. Observed values: BUSY = TRUE DONE = FALSE ERROR = FALSE STATUS = 16#FFFFFFFF indefinitely. Packet Capture A Wireshark capture was taken on the PROFINET network. Observed traffic: PROFINET RT LLDP DCP Observed: successful cyclic IO Not observed: DCE/RPC Record Write Record Read RPC Bind No RPC packets are transmitted at all. Diagnostic Messages The controller repeatedly reports AR alarm.ind(err) AR CMI timeout although cyclic IO communication continues to work. Already Verified The following points have already been checked: correct Ethernet interface (eth1) correct CREATE_ID result correct Device ID correct Slot/Subslot correct GSDML correct REQ pulse RECORD buffer is larger than LEN cyclic IO communication works different Record Indices (100...104) tested Question Is there any known issue or limitation where WRREC/RDREC requests remain permanently BUSY and no RPC Record Access packets are generated? Could this behaviour be related to Runtime 4.16.0.0, PN Controller 4.6.0.0, the missing runtime license (currently running in demo mode), or any known issue with the PROFINET Controller SL? I am currently evaluating the PROFINET Controller SL and therefore the runtime is operating in demo mode. Could you please confirm whether WRREC/RDREC (acyclic Record Data services) are fully supported in demo mode, or whether a valid license is required for these services? If required, I can provide: complete project archive Wireshark capture (.pcap) GSDML online screenshots diagnostic log Thank you very much for your help. Best regards, Stefan
Last updated: 2026-07-17
wiki Discussion
mattyh451
wiki
(Discussion)
Forum for wiki comments
Last updated: 2026-07-17
blog Discussion
mattyh451
blog
(Discussion)
Forum for blog comments
Last updated: 2026-07-17
(no subject)
mattyh451
wiki
(Thread)
Last updated: 2026-07-17
Home
mattyh451
wiki
(WikiPage)
Project Members: mattyh451 (admin)
Last updated: 2026-07-17
Home (version 1) discussion
john-morgan-fs
wiki
(Thread)
Home (version 1) discussion
Last updated: 2026-07-17
Home (version 1) discussion
afrazeh2026
wiki
(Thread)
Home (version 1) discussion
Last updated: 2026-07-17
Home (version 1) discussion
broohkale
wiki
(Thread)
Home (version 1) discussion
Last updated: 2026-07-17
Home (version 1) discussion
mattyh451
wiki
(Thread)
Home (version 1) discussion
Last updated: 2026-07-17
Home (version 1) discussion
mohammad
wiki
(Thread)
Home (version 1) discussion
Last updated: 2026-07-17
Home (version 1) discussion
bigwhig
wiki
(Thread)
Home (version 1) discussion
Last updated: 2026-07-17