Post by wbj0t on Global variable access by Programms and Modbus Devices (attach device to bus) ^{CODESYS Forge talk (Post)}
Hi everyone. I use Raspberry Pi 4, one core codesys SL. I have a question about global variable access via programm when I glued the same variable to MODBUS SERIAL/TCP DEVICE holding register. So, the question: what behavior of this modifying? When I set "Always update variables (in bus cycle)" and set some task as bus for the Device, then in another task I cant change this varible (can, but immediatly the old value setted again). But the same things works with MODBUS SLAVE: again "Always update..." and master attached to some task, then I change variable in another task and all works. I cant set up my variables from retains file at PrepareStart event because of this behavior with MODBUS SERIAL/TCP DEVICE. Thanks, wbj0t.
Last updated: 2024-07-18

Post by tk096 on High Cycle Times for SoftMotion_PlanningTask when using AxisGroup ^{CODESYS Forge talk (Post)}
Hi, under this circumstances the performance of a Raspberry Pi 4 should be sufficient to run a Softmotion robotics application. A closer look at the project would be required. Maybe you could contact the codesys support? Usually it is recommended to run the planning task cyclically every 2ms with task priority of 0 on a dedicated core. In the task configuration you can have a look at the average and maximum execution time of the planning task. You could use the function block SMC_TuneCPKernel (https://content.helpme-codesys.com/en/libs/SM3_Robotics/Current/SM3_Robotics/POUs/AdministrativeConfiguration/Computation/SMC_TuneCPKernel.html) to define suitable values for the parameters 'fSyncBufferDuration' and 'fPlanningInterval'. However, as previously mentioned, the performance of a Raspberry Pi 4 with realtime patch should be sufficient. The 'fPlanningInterval' parameter specifies the maximum planning step width in seconds. The cycle time of the planning task should not permanently exceed this value. A higher value reduces the computational effort, but can lead to a violation or no full utilization of the set limit values for velocity, acceleration and jerk. From a starting value of 0.016 seconds, the value should be increased gradually until the performance is acceptable. The parameter 'fSyncBufferDuration' specifies the size (in seconds) of the buffer between the planning and fieldbus task. The cycle time of the planning task must not exceed this value at peak times (this will lead to the error SMC_CP_QUEUE_UNDERRUN). A higher value can compensate for peaks in the cycle time of the planning task. At the same time, however, this also increases the latency for executing interrupts and aborting movements.
Last updated: 2024-03-22

Post by hbuitrago on CmpIecTask-program loaded exception ^{CODESYS Forge talk (Post)}
I'm facing an error that show on the codesys and the PLC that dont let either the PLC run or access it using the remote software, Error: program loaded exception Log: exception position:IP=0x0xfffffffe (no IEC context could be retrieved) component: CmpIecTask exception [accessviolation] ocurred: APP=[application], Task=[Task] POU changed, that inhibits an online change, Plase let me know if there is a solution for this issue, Best regards,
Last updated: 2024-09-06

Post by rossanoparis on RevPi CONNECT+, CODESYS, EtherCAT master "Filedbus lost synchronicity" ^{CODESYS Forge talk (Post)}
Hello @rmaas I assume, you've already verified and tuned everything regarding the EtherCAT network. In my case the problem was due to a wrong core assignement. I suggest to not use the core #0 for your EtherCAT task. The OS realtime patch, which is present on RevPi OS, uses the core #0 for its porpouses and it mustn't be used by any other task which requires realtime and deterministic features. regards Rossano
Last updated: 2024-04-11

Post by s1mon on Two OneWireMaster on one Raspberry PI 5 ^{CODESYS Forge talk (Post)}
All Sensors from the OneWire Master are assigned already to a seperate task with low prio (26) that runs with 1s cycle time. My EtherCat Task is running with Prio 1. It all works fine, until I adjust the CODESYScontrol.cfg or the CODESYScontrol_Usr.cfg files so that it supports a 2nd OneWire Master in the Codeys Runtime. If I change something in this config file and reboot my EtherCat Master stops working.
Last updated: 2025-10-19

Post by manuknecht on High Cycle Times for SoftMotion_PlanningTask when using AxisGroup ^{CODESYS Forge talk (Post)}
Hi, we did install the real-time kernel patch on the RPI and also performed the additional optimizations including isolating the cores. Changing the configuration of the planning task e.g. running it on a separate core, changing the cycle times and mode from cyclic to freewheeling did not show any improvements.
Last updated: 2024-03-14

Post by rmaas on Fieldbus has lost synchronicity ^{CODESYS Forge talk (Post)}
Hi, On a gantry system with 2 axis i am getting the following error: SMC_DI_FIELDBUS_LOST_SYNCRONICITY This happens random, sometimes it happens every 5 minutes and sometimes no error for 2 hours... The Setup: - Using codesys 3.5 SP20 with all latest libs... - Kontron AL Pi-Tron CM4 with Preempt realtime patch (Raspberry Pi 4) - Codesys runtime 4.11.0.0 (single core) - CODESYS Control for Raspberry Pi SL licensed - Softmotion + CNC + Robotics licensed - 2x Leadshine EL8-EC400 servo drives - Axis group for a 2-axis T-Gantry Ethercat network wiring: Ethercat master softmotion -> Beckhoff EK1100 -> Servo drive #1 -> Servo drive #2 Ethercat Cycle time = 4ms Max Jitter = 140~150 What i have tried so far: - changed the sync offset from 20% to 30% - changed ethercat task priority from 1 to 0 Running tasks: - Ethercat tast: Prio = 0, Interval = 4ms - Main task: Prio = 1, Interval = 8ms - Visu task: Prio = 31, Interval = 100ms - Softmotion planning task: Prio = 15, Freewheeling - 3 other default tasks that were created by AC_Persist Motion fb's are called in the ethercat task... Does anyone have an idea how to fix this? Any help is greatly appreciated!
Last updated: 2024-04-11

Post by dasch on eCockpit - unable to start simulation ^{CODESYS Forge talk (Post)}
This is a known bug in e!Cockpit. See Release notes of V 1.11: 1 e!Cockpit Release Version 1.11 (2022-07) ATTENTION: If a library that uses asynchronous tasks (e.g. WagoAppConfigTool, WagoAppCloud or function modules such as Dali-Master) is dragged into the project, the simulation cannot be started. It is already sufficient to add the library to the project (an FB does not even have to be instantiated). I guess you are using one of these libraries/modules in your project. We e.G. often use PWM modules, these are also affected.
Last updated: 2023-09-05

Post by siggi95 on Übersetzungsfehler J1939 changeAdress (4.1.0.0) ^{CODESYS Forge talk (Post)}
Hallo zusammen, für den Aufruf VAR deviceDiag: J1939.IJ1939LocalECU; END_VAR deviceDiag.ChangeAddress(5); gibt es mit der Version 4.1.0.0 der Lib IoDrvJ1939 Übersetzungsfehler - C0035: Programmname, Funktion oder Funktionsbausteinstanz an Stelle von 'deviceDiag.ChangeAddress' erwartet - C0004: 'ChangeAddress' ist keine Komponente von 'IJ1939LocalECU__Union' Mit der bisher verwendeten Lib-version 3.5.17.0 nicht und auch das Setzen der device adress hat funktioniert. Lt. Release notes ("J1939: ChangeAddress method does not work properly.") wurde hier verbessert. Leider habe ich keine Beschbreibung dazu gefunden. Wie muss der Aufruf angepasst werden? Vieeln Dank und beste Grüße Siggi
Last updated: 2023-11-29

Post by hismoon on CodeSys SVN funktionert nicht ^{CODESYS Forge talk (Post)}
Das CODESYS SVN AddOn hat Minimal-Versions-Vorgaben. In SP9 funktioniert wohl die neueste SVN Version nicht. Da mal am besten im Store auf die Release Notes auf der Download-Seite schauen. Da steht meistens, ab wann Minimal-Versionen erhöht wurden. (Required CODESYS version) V4.2.6.0 vom SVN AddOn scheint die letzte zu sein, die mit SP9 offiziell funktioniert. Eigentlich sollte das der CODESYS Installer / Package Manager abfangen, aber hmm.
Last updated: 2024-06-04

Post by trusty-squire on SysProcessCreate2 on Linux runtime ^{CODESYS Forge talk (Post)}
Hi, I'm trying to launch a continuously running python script from Codesys and monitor the script status inside the Codesys runtime (running on a Linux enviroment). For now I'm testing with the below to emulate a continuously running Python script: #test.py i = 0 while True: i += 1 I'm able to successfully run the script using SysProcessExecuteCommand2 (I can see the Python process running in the task manager). However, this "freezes" the Codesys execution of the task - it sits on that command and will not continue until the Python script ends. I've proven this works by using the task monitor to kill the process, then Codesys continues on happily through the task. What I want to do is use SysProcessCreate2 to set up the Python script as a background task and monitor the process using SysProcessGetState. This always results in the error "ERR_OPERATION_DENIED". I know that I'm able to execute commands (as above), so my config should be correct. Is SysProcessCreate2 functional on a Linux environment? Is there something in the config file I'm missing? Here's my "working" code that uses SysProcessExecuteCommand2: VAR bTest : BOOL; sCommand : STRING := '/usr/bin/python3 /var/opt/codesys/PlcLogic/Application/test.py'; refCommand : REFERENCE TO STRING REF= sCommand; sOutput : STRING; refOutput : REFERENCE TO STRING REF= sOutput; result : RTS_IEC_RESULT; END_VAR IF bTest THEN SysProcessExecuteCommand2( pszCommand:= refCommand, pszStdOut:= refOutput, udiStdOutLen:= SIZEOF(sOutput), pResult:= ADR(result) ); bTest:= FALSE; END_IF And here's the code that always results in the ERR_OPERATION_DENIED error: VAR bTest : BOOL; sApp : STRING := '/usr/bin/python3'; sCommand : STRING := '/var/opt/codesys/PlcLogic/Application/test.py'; refApp : REFERENCE TO STRING REF= sApp; refCommand : REFERENCE TO STRING REF= sCommand; hResult : SysProcess.RTS_IEC_RESULT; hHandle : SysProcess.RTS_IEC_HANDLE; END_VAR IF bTest THEN hHandle := SysProcessCreate2( pszApplication:= refApp, pszCommandLine:= refCommand, ulFlags:=SYSPROCESS_CREATEFLAG_HIDDEN, pResult:= ADR(hResult) ); bTest:= FALSE; END_IF Here's the relevant section from the config file at /etc/codesyscontrol/CODESYSControl.cfg: [SysProcess] Command=AllowAll Appreciate any support or ideas. Thanks!
Last updated: 2025-03-16

Post by i-campbell on Official MQTT-Client: MAX_RECEIVE_BUFFER_SIZE_EXCEEDED ^{CODESYS Forge talk (Post)}
256MB for the protocol yes, but the default value for this library parameter limits the library to 6kB per task scan.
Last updated: 2023-09-27

Post by andrax on Prüfen ob Datei existiert wenn nicht neu erstellen ^{CODESYS Forge talk (Post)}
Auch wenn es bissl spät ist, DANKESCHÖN. Dann hatte ich mir das richtig gedacht. Aus Sicherheitsgründen habe ich die Task gegenseitig verriegelt
Last updated: 2024-07-01

Post by pietrobalint on Retain / Persistent Variables in Codesys for Raspberry Pi ^{CODESYS Forge talk (Post)}
Ok, I figured out that I do not call the program in the main task. Thank you for the source code, it works!
Last updated: 2024-08-17

Post by micik on Retain / Persistent Variables in Codesys for Raspberry Pi ^{CODESYS Forge talk (Post)}
Hello pietrobalint, could you please how exactly you call this program? if not in the main task? Caould you please share a screenshot of how exactly you made it work? Thank you!
Last updated: 2024-08-20

Post by eschwellinger on Problem with edge gateway config mode ^{CODESYS Forge talk (Post)}
if this does not work, you could install the 3.5.20.0 Gateway from the CODESYS Store. https://store.codesys.com/de/codesys-edge-gateway-for-windows.html then it is possible to enable it by righclick inthr task tray
Last updated: 2024-10-21

Post by davidbo on AC_Datalog DataLogChannel Save Cyclic is not working ^{CODESYS Forge talk (Post)}
"Save Cyclic" is set to 30s, but in my log I can see my variables are logged every 500ms which equals the cyclic time for my Task. Why is "Save Cyclic" ignored
Last updated: 2025-07-11

Post by open on How to create a stopwatch? ^{CODESYS Forge talk (Post)}
Thanks everyone for your input, I am using persistent variables to retain the timer value after machine shutdown, and main task to be as low as possible for the seconds TON to be accurate.
Last updated: 2023-12-14

Post by acc00 on Variable Sync Issue In Soft Plc Redundancy ^{CODESYS Forge talk (Post)}
Hi arundara, I'm also experimenting with Redundandcy. Is the sync variable function the following: "RedundancySynchronizeData()" ? Does the Task time increase a lot when you activate the sync function?
Last updated: 2024-03-11

Post by tk096 on High Cycle Times for SoftMotion_PlanningTask when using AxisGroup ^{CODESYS Forge talk (Post)}
Hi, you need a realtime capable plc. Codesys Control WinV3 is not realtime capable. https://content.helpme-codesys.com/en/CODESYS%20Control/_rtsl_performance_optimization_linux.html The last chapter of https://content.helpme-codesys.com/en/CODESYS%20SoftMotion/_sm_robotics_diagnosis_movement_problems.html deals with how to configure the planning task.
Last updated: 2024-03-13

Post by alex-at-xana on EThercat Dynamic configuration ^{CODESYS Forge talk (Post)}
Ah - forgot another question as it may be related to the PLL problem: I am executing a 4ms cycle. I do not call (from what I know) the Ethercat_MAster periodically in my program. The bus cycle task is set to the Ethercat task. I would assume that the master should send 250 frames per second. Yet, the status of the master says it transmits 500 frames per second which would indicate that the master is called twice. Any ideas there?
Last updated: 2024-09-10

Post by acc00 on Main Task cycle too long leading to PLC Fail ^{CODESYS Forge talk (Post)}
I have 2 Wago PFC200 PLC, running with Runtime SP19 Patch 5, with the Redundant application. The PLC communicates as Modbus Master with at this moment 15 Modbus Slaves -later there will be 28 in total- (Drives, Power management units,...). These devices are connected in 2 rings (1 ring of Drives, 1 ring of Power Management units), with 2 Managed Moxa Switches being part of the ring. Each PLC is connected to one of these switches. The issue I'm encountering is that the Cycle time of the Active PLC goes very high when I'm closing the Drive ring (simulating an issue on one Cabinet supply, resulting in that one Drive shut down, which can happen on field quite often). As a result of this long cycle, the PLC fails and goes to Exception, and the Passive PLC does not take control of the system. A normal cycle is around 30ms for the Main task, and a few ms for the Ethercat task. When I monitor with Profiler, I see that in this Maximum Cycle, the main Task is only taking 13ms, so I'm not sure where the PLC is hanging for so long. Is the remaining cycle time the Redundant management/sync or something else? Thank you in advance.
Last updated: 2024-03-08

Post by marekxc on Compiling Errors with Ethernet/IP Scanner ^{CODESYS Forge talk (Post)}
Update the Device: Right-click on the device icon in the project tree. Select the “Update Device” option. Recompile the Project: After updating the device, recompile the project from scratch to ensure that all changes are included. Check Task Settings: Go to the “Tasks” tab in the project. Check the priority settings for the tasks to ensure they are configured correctly.
Last updated: 2024-11-09

Post by ben1 on How to stay in a method until something is finished. ^{CODESYS Forge talk (Post)}
Why must you use a method? Top of my head can't you just use the button to turn on a bit and use it in a normal task? Just turn a bit on with the button, and run a TON from it in code, and turn it back off with the ton. And then just log the pressure on both the rising & falling edge?
Last updated: 2025-11-03

Post by struccc on Multiple applications on one device sharing variables. ^{CODESYS Forge talk (Post)}
I don't exactly recall where (I think some release notes), but I read the information that this multiple application / sub application feature is to be discontinued. Please, correct me, if I'm not right about this I am a bit sad about that - I was using that feature with more or less success. However I understand the reason behind the change: it introduces huge complexity, especially when dealing with multicore and safety support... AS I understand, it's to be replaced with the new virtual plc architecture, and standard ways for synchronizing / sharing data... So, for now the "Add application" context menu item was removed, but behind the scene it is still supported... Hint: if you still want to experiment with it, might try copy-paste things within the PLCLogic tree...
Last updated: 2025-02-28

Sort by relevance or date