runtime received SIGABRT ^{CODESYS Forge talk (Thread)}
runtime received SIGABRT
Last updated: 2025-04-17

Post by andrax on CodeSys Raspberry pi I2C driver not found ^{CODESYS Forge talk (Post)}
This is the operating system and has nothing to do with the runtime. Unless you use 64bit commands. You can see for yourself that you have errors with 64bit compilers
Last updated: 2024-11-09

Post by andrej on POU - Access to runtime ^{CODESYS Forge talk (Post)}
Hello all, when creating a POU, the Codesys IDE allows the setting "Enable System Call" (in the Settings, Property -> Build), see picture. The name suggest, that runtime functionalities i.e. functions of codesyscontrol such as "stop plc" etc. can be directly called. I tried various approches without success, the following does, unsurprisingly not work. FUNCTION accessRTE: BOOL; ****************************** codesyscontrol.stop(); Can you please tell me how I can make a system call to codesyscontrol from a POU. Or could you provide me with a use case for this setting. Many thanks for your feedback and kind regards Andrej
Last updated: 2024-03-02

Post by andre-luis on Check if Codesys runtime is on 'Running' or 'Stopped' state? ^{CODESYS Forge talk (Post)}
It's already there, the service get started as default. I missed to say that sometimes it happens w/o even the system get restarted. Anyway, the main issue here is to know the state of the runtime. We collect a lot of informations about the whole system, and it would be nice to have a way to detect the runtime state.
Last updated: 2024-07-02

Post by lsislsis on SIGABRT Error ^{CODESYS Forge talk (Post)}
2024-11-08T13:39:07.354Z, 0x00000103, 65544, 1, 0, runtime received SIGABRT - system may be in an inconsistent state* We recommend a reboot of the controller now! 2024-11-08T13:39:07.354Z, 0x00000111, 8, 260, 3, #### Exception: More than 2 exceptions in CH_COMM_CYCLE: Stop logging 2024-11-08T14:36:33.126Z, 0x0000100d, 1, 0, 0, Demo mode expired. 2024-11-08T15:35:49.253Z, 0x00000103, 65544, 1, 0, runtime received SIGABRT - system may be in an inconsistent state We recommend a reboot of the controller now! 2024-11-08T15:42:54.664Z, 0x00000103, 65544, 1, 0, runtime received SIGABRT - system may be in an inconsistent state We recommend a reboot of the controller now! *
Last updated: 2024-11-08

Post by paulg on CODESYSControl_User.cfg - link to documentation? ^{CODESYS Forge talk (Post)}
Is there somewhere in the Codesys help files that generally details what configuration options are available for this file, and what details it logs regarding the configuration file? Or is that going to differ by libraries being used? Thanks!
Last updated: 2024-06-11

Post by struccc on Wish: CODESYSControl.cfg - again ^{CODESYS Forge talk (Post)}
Before creating this topic, I was browsing the search results for CodesysControl.cfg - many results, and I remember very well, it's a problematic issue for a long time. To summarize: there were many requests for documentation on this file - the most comprehensive reply is: https://forge.codesys.com/forge/talk/Runtime/thread/ebbf851a3d/#eb85 Hi, not really, this is covered by the manual which you get if you use a runtime toolkit which is not free of charge. Maybe we need to extract the config file part from that documentation if that is possible. BR Edwin I am not sure how much is this relevant, since we buy SL License directly from CODESYS... I think it is a reasonable demand, to get documentation on the configuration entries affecting the documented behaviour of the runtime system and it's components The actual reason I bring up this issue again can be read here: https://forge.codesys.com/forge/talk/Runtime/thread/febad3cc40/#0e12 but mostly my frustration about noticing some new, unknown and undocumented entries in my configuration file. Again. And this happens a lot recently. Just some examples: Changes with SysFile - and mandatory use of IEC path Introduction of Mandatory user management File transfer service now disabled by default SysProcess - allowed commands The above mentioned CmpApp parameters... And finally (Regaridng windows install): With the newer versions, the installation directory (together with the configuration file) tends to hide itself to some super silly location under the roaming profile data of local system account. I am not sure if this change was documented somewhere, but was a very unpleasant one. Someone could please explain the reason and the concept of the introduction of this release specific directories (I am sure, there is a good reason) - how to use them properly? - How to re-introduce user configuration (to preserve configuration data between versions)? - How to do version - to version migrations properly? - How to keep old version of runtime available and ready to start with it's original configuration and application? - ... Therefore, the lack a regularly updated description of CodesysControl .cfg , including all the configuration entries, together with their default values for different runtime versions is really a big deficiency.* This should be done for all components storing or just seeking data from this file... (Maybe there is such thing but I failed to find???) It is regularly causing trouble when introducing a new version (together with the long awaited bug fixes and enhancements), what has changed it's default behaviour for security or other practical reasons. I agree this is very important, and it is logical to change the default options: But it must be documented historically, and make it easily available, so we can prepare better for the upgrade of the runtime. Forge talk is a great source, but not very practical for this kind of documentation purposes... Thanks in advance for CODESYS staff 🙏🙏🙏 (Ps.: It would look rather silly, if some members of the user community prepares this documentation on a Forge Wiki page... Or??? Should we?)
Last updated: 2024-11-21

Post by dhumphries on Minimum system requirements for codesys control standard S ^{CODESYS Forge talk (Post)}
I'm working on a low cost project and I'm considering installing the Codesys runtime on a PC running Linux Debian instead of buying a PLC with a pre-installed runtime. For my needs the Control Standard S license should be capable of running some IO over ethernet/ip, and a webvisu. The PC I am considering has a AMD GX-424CC 2.4GHz processor (4 core/4 thread) and 4GB RAM. This may compare to a raspberry pi4, but I know an X86 processor doesn't directly compare to an ARM processor, and a processor can have a high clock speed but other factors like L2/L3 cache can influence the overall performance. I can't find any published specs for the processor and RAM requirements to run the Codesys Control runtime, does anybody have a link to the minimum system requirements or experience using devices that are at or below the minimum system requirements. A raspberry pi with the control for raspberry pi SL runtime license would be the lowest cost option, but the license is not for commerical use. This restriction is somewhat vague, can anybody clarify if this means I can use a raspberry Pi runtime for in-house automation, what about if I am selling an integrated system that uses a raspberry Pi as a controller?
Last updated: 2023-12-25

Post by kumareasu on Persistent variable storage ^{CODESYS Forge talk (Post)}
Is there any function function block which can store the persistent variable in HDD/SSD immediatley. My observation is that the persistent variable is getting stored when we shut down or restart the system (Windows+ CoDeSys RTE SL ). the persistent variables are not stored in HDD/SSD, if I power off the system without proper shutdown. Seeking your feedback.
Last updated: 2024-06-12

Post by appling on License status of Linux 64Bit runtime via CLI ^{CODESYS Forge talk (Post)}
Hi, I have a Linux 64Bit system with a Codesys application running on it. It stops after 2hours and a few minutes, which makes me think something is wrong with the installed license. (in my last timing it stopped after 2h4min, on the codesys website it is stated that runtimes without a license stop after 2h) I installed the license via a USB license dongle that I activated on my workstation with the Codesys IDE a while ago. Now the system is shipped at not accessible physically, only remotely via SSH. So is there a way to check the status of the License of the Codesys runtime when it is running on the system? Running the codesyscontrol script with "status" just tells me that it is running, but does not provide any license information. Best regards
Last updated: 2023-12-04

Problems connecting to Codesys 4.9.0.0 runtime on my Wago PFC200 ^{CODESYS Forge talk (Thread)}
Problems connecting to Codesys 4.9.0.0 runtime on my Wago PFC200
Last updated: 2023-08-26

ooops... this runtime was built for RASPBERRYPI (-22, 0x00000BB8, 0xFFFFFFFB) ^{CODESYS Forge talk (Thread)}
ooops... this runtime was built for RASPBERRYPI (-22, 0x00000BB8, 0xFFFFFFFB)
Last updated: 2023-06-30

What licenses are required for runtime on raspberry pi cm4 ^{CODESYS Forge talk (Thread)}
What licenses are required for runtime on raspberry pi cm4
Last updated: 2023-10-17

Codesys Raspberry Runtime 4.10.0.0 and RSM Utility 3.5.19.0 ^{CODESYS Forge talk (Thread)}
Codesys Raspberry Runtime 4.10.0.0 and RSM Utility 3.5.19.0
Last updated: 2023-11-21

License status of Linux 64Bit runtime via CLI ^{CODESYS Forge talk (Thread)}
License status of Linux 64Bit runtime via CLI
Last updated: 2023-12-04

No Communication Manager for Raspberry Pi Runtime ^{CODESYS Forge talk (Thread)}
No Communication Manager for Raspberry Pi Runtime
Last updated: 2021-05-06

RaspberrPi 4 Compute Module: Runtime "SL" available? ^{CODESYS Forge talk (Thread)}
RaspberrPi 4 Compute Module: Runtime "SL" available?
Last updated: 2021-02-02

ac_datalog causes runtime exception on RPi after a while ^{CODESYS Forge talk (Thread)}
ac_datalog causes runtime exception on RPi after a while
Last updated: 2021-09-01

Needs for a simple PLC runtime on an Hilscher's netPI ^{CODESYS Forge talk (Thread)}
Needs for a simple PLC runtime on an Hilscher's netPI
Last updated: 2022-06-29

Dynamically change device assembly bytes at runtime ^{CODESYS Forge talk (Thread)}
Dynamically change device assembly bytes at runtime
Last updated: 2022-03-02

Control Linux SL runtime - segmentaton fault on startup ^{CODESYS Forge talk (Thread)}
Control Linux SL runtime - segmentaton fault on startup
Last updated: 2022-05-25

ooops... this runtime was built for RASPBERRYPI (-8, 0x00000BB8, 0xFFFFFFFB) ^{CODESYS Forge talk (Thread)}
ooops... this runtime was built for RASPBERRYPI (-8, 0x00000BB8, 0xFFFFFFFB)
Last updated: 2023-06-30

Cannot add OPC UA-Server as Datasource to RTE Runtime ^{CODESYS Forge talk (Thread)}
Cannot add OPC UA-Server as Datasource to RTE Runtime
Last updated: 2021-10-12

Codesys Runtime in Raspberry PI 4 requires syslog ^{CODESYS Forge talk (Thread)}
Codesys Runtime in Raspberry PI 4 requires syslog
Last updated: 2022-02-18

Raspberry Pi Runtime shutdown with "Ooops ...." message ^{CODESYS Forge talk (Thread)}
Raspberry Pi Runtime shutdown with "Ooops ...." message
Last updated: 2022-01-24

Sort by relevance or date