Discussion
| FORUM | LATEST POST | # TOPICS |
|---|---|---|
|
General Discussion Forum about anything you want to talk about. |
How to turn on a GPIO from a device function block by lwalbert 2022-09-29 |
1 |
Recent Activities
-
thejesh modified a comment on discussion Visualization 🇬🇧
Hi, HTML5 Conrtrol elements on CODESYS V3.5 SP22 Patch 2, WebVisu only (no TargetVisu). The client is Chromium 147 in kiosk mode on a Raspberry Pi CM5 panel; the runtime is CODESYS Control Win V3 x64/CODESYS Control RTE V3 x64 on a separate IPC. I have measured that changing a Frame element's switch-frame variable destroys the currently referenced visualization and fully rebuilds it on return, including all embedded HTML5 controls. We would like to know whether this lifecycle is configurable. Measurement...
-
thejesh posted a comment on discussion Visualization 🇬🇧
Hi, I urgently need some help from you to reach Codesys Support on priority On CODESYS V3.5 SP22 Patch 2, WebVisu only (no TargetVisu). The client is Chromium 147 in kiosk mode on a Raspberry Pi CM5 panel; the runtime is CODESYS Control Win V3 x64/CODESYS Control RTE V3 x64 on a separate IPC. I have measured that changing a Frame element's switch-frame variable destroys the currently referenced visualization and fully rebuilds it on return, including all embedded HTML5 controls. We would like to...
-
antony posted a comment on discussion Engineering 🇬🇧
Hi, I am facing the same “Assertion failed” error while downloading the code.
-
baltzer posted a comment on discussion Engineering 🇬🇧
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...
-
dmb-fan posted a comment on discussion Engineering 🇬🇧
Sounds good. Thx
-
TimvH posted a comment on discussion Engineering 🇬🇧
Completely managed by CODESYS, including licenses. You specifically have to set the parameters correctly in the CODESYSControl.cfg to let the RTE have access to the cards. See: https://content.helpme-codesys.com/en/CODESYS%20Control/_rtsl_windows_rte_v3_startup_cifx_hil.html
-
I was able to reproduce this by doing something wrong. I guess what you did is first create an application for the Control Win, or some other device and then switched this to the Linux SL. But then the Visualization Manager still has the "TargetVisu" component, besides the WebVisu component. The Linux SL doesn't support this TargetVisu as part of the runtime. You should run a separate process for this. So remove the TargetVisu from the Visualization Manager and then you will be able to load the ...
-
dmb-fan posted a comment on discussion Engineering 🇬🇧
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
-
lzml modified a comment on discussion Visualization 🇬🇧
Thanks for the suggestion - I updated everything via the CODESYS Installer and restarted, but I'm still hitting the same error. What I did - Updated via Tools > CODESYS Installer - Visualization system libraries (VisuElems, VisuElemsAlarm, VisuInputs, VisuNativeControl, etc.): 4.7.0.0 -> 4.10.0.0 - CODESYS Control for Linux SL: 4.15.0.0 -> 4.21.0.0 (based on CODESYS SDK 3.5.22.20) - Restarted CODESYS Development System Checked project environment (Project > Project Environment) after restart - Compiler...
-
lzml posted a comment on discussion Visualization 🇬🇧
Thanks for the suggestion - I updated everything via the CODESYS Installer and restarted, but I'm still hitting the same error. What I did - Updated via Tools > CODESYS Installer (had to trigger the update-list refresh manually, it doesn't do this automatically on open) - Visualization system libraries (VisuElems, VisuElemsAlarm, VisuInputs, VisuNativeControl, etc.): 4.7.0.0 -> 4.10.0.0 - CODESYS Control for Linux SL: 4.15.0.0 -> 4.21.0.0 (based on CODESYS SDK 3.5.22.20) - Restarted CODESYS Development...