Home
jasonhogan
wiki
(WikiPage)
Project Members: jasonhogan (admin)
Last updated: 2026-08-05
(no subject)
jasonhogan
wiki
(Thread)
Last updated: 2026-08-05
Post by dmb-fan on Hilscher cards CoDeSys Control RTE
CODESYS Forge
talk
(Post)
Hi! I'm currently trying to make my way through this jungle... Hilscher CIFX 50E PCIe cards: DP Master + CANopen Master If I want to run these under Control RTE, do I need a master license from Hilscher for each card? Or do they run entirely with CoDeSys drivers and parameterization tools? I can’t find any clear information on this from either manufacturer. Thanks
Last updated: 2026-08-06
wiki Discussion
dmb-fan
wiki
(Discussion)
Forum for wiki comments
Last updated: 2026-08-06
blog Discussion
dmb-fan
blog
(Discussion)
Forum for blog comments
Last updated: 2026-08-06
Home
dmb-fan
wiki
(WikiPage)
Project Members: dmb-fan (admin)
Last updated: 2026-08-06
(no subject)
dmb-fan
wiki
(Thread)
Last updated: 2026-08-06
Post by baltzer on ICertificateVerifier.VerifyCertificate doesn't appear to override an ERR_CERT_HAS_EXPIRED rejection in TCP_Client.Upgrade()
CODESYS Forge
talk
(Post)
Follow-up: working workaround found (routing TLS outside CODESYS) For anyone finding this thread later with the same problem (a third-party device presenting a self-signed and/or expired certificate that ICertificateVerifier/udiVerificationMode won't let you connect through) - we never got a working fix within NBS itself, but found a practical workaround worth sharing. Approach: run a local TLS-terminating proxy on the same host as the CODESYS runtime, and have CODESYS talk plain, unencrypted TCP to it instead of connecting to the remote device directly over TLS: CODESYS --plain TCP--> 127.0.0.1:<port> --stunnel/TLS--> <remote device>:<port> We used stunnel (client mode), with certificate verification explicitly disabled at that layer (verifyChain = no, verifyPeer = no) - a simple, well-documented one-line option, unlike anything we could get working inside NBS. Running it as a systemd service with Restart=always means it survives reboots and recovers automatically if the proxy or the remote device drops. On the CODESYS side, this required no changes beyond pointing TCP_Client at 127.0.0.1 instead of the device's real IP, and removing the TLSContext/ICertificateVerifier code entirely - the rest of our application-layer logic (framing, checksums, etc.) was completely unaffected, since none of that ever depended on where the TLS termination happened. Confirmed working end-to-end against a real device with an expired self-signed certificate, running on CODESYS Control for Raspberry Pi SL (Linux). We haven't yet set this up on Windows - stunnel does have Windows builds available, so the same general approach should be possible there too, but that combination isn't tested or confirmed by us at this point. Caveat: this only makes sense when the proxy and the CODESYS runtime are on the same trusted host (in our case, both on the same Raspberry Pi) - don't expose the proxy's plaintext side on a reachable network interface, since that would create an unauthenticated plaintext path to the device. The original question - whether there's a supported way to override an ERR_CERT_HAS_EXPIRED/self-signed rejection from within NBS's own TLSContext/ICertificateVerifier - remains open as far as we know. Still happy to hear from anyone who's solved that particular piece, since the workaround above is a practical detour rather than an actual answer to the original question.
Last updated: 2026-08-06
ICertificateVerifier.VerifyCertificate doesn't appear to override an ERR_CERT_HAS_EXPIRED rejection in TCP_Client.Upgrade()
CODESYS Forge
talk
(Thread)
ICertificateVerifier.VerifyCertificate doesn't appear to override an ERR_CERT_HAS_EXPIRED rejection in TCP_Client.Upgrade()
Last updated: 2026-08-06
wiki Discussion
lizhisheng
wiki
(Discussion)
Forum for wiki comments
Last updated: 2026-08-07
blog Discussion
lizhisheng
blog
(Discussion)
Forum for blog comments
Last updated: 2026-08-07
Post by dhumphries on Codesys Installation problem
CODESYS Forge
talk
(Post)
Installing codesys has been the biggest point of frustration for me and is the reason I'm currently working on building a VM just for the codesys engineering software so once I get a working installation I can copy the VM to new workstations instead of fighting with the installer every time I get a workstation upgrade. The best advice I've gotten in the past is to uninstall everything and start over, this is successful 50% of the time. Also don't install the latest version it's usually less stable than an older one ironically.
Last updated: 2026-08-10
Home (version 1) discussion
noryam
wiki
(Thread)
Home (version 1) discussion
Last updated: 2026-08-08
Home (version 1) discussion
mitboz
wiki
(Thread)
Home (version 1) discussion
Last updated: 2026-08-08
wiki Discussion
pruedchawat
wiki
(Discussion)
Forum for wiki comments
Last updated: 2026-08-10
blog Discussion
pruedchawat
blog
(Discussion)
Forum for blog comments
Last updated: 2026-08-10
Home
pruedchawat
wiki
(WikiPage)
Project Members: pruedchawat (admin)
Last updated: 2026-08-10
(no subject)
pruedchawat
wiki
(Thread)
Last updated: 2026-08-10
Post by timvh on Codesys Installation problem
CODESYS Forge
talk
(Post)
Instead of complete VM's, you could also create a sandbox installation using the CODESYS installer.
Last updated: 2026-08-10
Deploy Codesys Control SL to a 'secure' device
CODESYS Forge
talk
(Thread)
Deploy Codesys Control SL to a 'secure' device
Last updated: 2026-08-10
Codesys Installation problem
CODESYS Forge
talk
(Thread)
Codesys Installation problem
Last updated: 2026-08-10
Post by eschwellinger on CODESYS Control for Raspberry Pi 5 - "Hardware version or firmware version not supported" on Rev 1.1, persists across multiple runtime versions and OS images
CODESYS Forge
talk
(Post)
see here: https://www.codesys.com/eco-system/up-to-date/release-lifecycle/release-plan-roadmap/ 18.8
Last updated: 2026-08-11
Post by eschwellinger on codesys installer deletes itself instead of updating
CODESYS Forge
talk
(Post)
I would try to use: https://store.codesys.com/de/codesys-installer.html this standalone version. Seems if your version out of SP19 setup have some update problem.
Last updated: 2026-08-11
CODESYS Control for Raspberry Pi 5 - "Hardware version or firmware version not supported" on Rev 1.1, persists across multiple runtime versions and OS images
CODESYS Forge
talk
(Thread)
CODESYS Control for Raspberry Pi 5 - "Hardware version or firmware version not supported" on Rev 1.1, persists across multiple runtime versions and OS images
Last updated: 2026-08-11
codesys installer deletes itself instead of updating
CODESYS Forge
talk
(Thread)
codesys installer deletes itself instead of updating
Last updated: 2026-08-11