Post by eschwellinger on onewire bus master stop working after 4.8.0.0 upgrade ^{CODESYS Forge talk (Post)}
du musst Onewire in einer eigenen Task aufrufen, das sind blockierende Aufrufe das geht nur in eigener Task, hab hier mal im Forum ein Beispiel gepostet
Last updated: 2023-09-20

Saving variable values on power cycle (RevPi Connect) ^{CODESYS Forge talk (Thread)}
Saving variable values on power cycle (RevPi Connect)
Last updated: 2023-12-04

data exchange at the end of each CoDeSys cycle ^{CODESYS Forge talk (Thread)}
data exchange at the end of each CoDeSys cycle
Last updated: 2010-07-12

Read PLC cycle time and change freewheeling sleep time ^{CODESYS Forge talk (Thread)}
Read PLC cycle time and change freewheeling sleep time
Last updated: 2018-10-11

how to determine the cycle time of a POU? ^{CODESYS Forge talk (Thread)}
how to determine the cycle time of a POU?
Last updated: 2010-03-01

Turck HMI needs to reload program on every power cycle ^{CODESYS Forge talk (Thread)}
Turck HMI needs to reload program on every power cycle
Last updated: 2022-09-22

High Cycle Times for SoftMotion_PlanningTask when using AxisGroup ^{CODESYS Forge talk (Thread)}
High Cycle Times for SoftMotion_PlanningTask when using AxisGroup
Last updated: 2024-03-22

EtherCAT drive going into fault mode require power cycle everytime ^{CODESYS Forge talk (Thread)}
EtherCAT drive going into fault mode require power cycle everytime
Last updated: 2024-09-11

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 davidbo on RPI can system operation like rm in a shell have an impact on a Task cycle time ^{CODESYS Forge talk (Post)}
CODESYS Control for Raspberry Pi MC SL v4.4.0.0 CANopen_Manager 4.2.0.0 I did not call rm directly from my TASK-i2c, it was trough the attached python script. It is not always a problem happens, but sometimes a rm takes a long time. I reduced the amount of calls to logi2c.py but I don't understand why TASK-i2c sometimes can cause problems for TASK-CAN
Last updated: 2024-09-27

Post by davidbo on RPI can system operation like rm in a shell have an impact on a Task cycle time ^{CODESYS Forge talk (Post)}
CODESYS Control for Raspberry Pi MC SL v4.4.0.0 CANopen_Manager 4.2.0.0 I did not call rm directly from my TASK-i2c, it was trough the attached python script. It is not always a problem happens, but sometimes a rm takes a long time. I reduced the amount of calls to logi2c.py but I don't understand why TASK-i2c sometimes can cause problems for TASK-CAN
Last updated: 2024-09-27

Post by installwhat on Ethercat and profinet on together ^{CODESYS Forge talk (Post)}
I'm curious about the impact of having profinet and Ethercat (specifically softmotion so frame at start of task?) running together. Since it's advised to access the data from the bus task should have both profinet io and ethercat on the same task? Are there any implications around this one should be aware of especially since the frame at task start is just, so far as I'm aware, an ethercat thing? Thanks
Last updated: 2025-04-08

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 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

onewire bus master stop working after 4.8.0.0 upgrade ^{CODESYS Forge talk (Thread)}
onewire bus master stop working after 4.8.0.0 upgrade
Last updated: 2023-09-21

no synchronization via field bus(Raspberry Sl softmotion) ^{CODESYS Forge talk (Thread)}
no synchronization via field bus(Raspberry Sl softmotion)
Last updated: 2018-05-29

CANbus Status Bus Load (and other values) not updating ^{CODESYS Forge talk (Thread)}
CANbus Status Bus Load (and other values) not updating
Last updated: 2020-11-12

How to map to values in CAN BUS ^{CODESYS Forge talk (Thread)}
How to map to values in CAN BUS
Last updated: 2021-04-29

KNX-Bus läuft nicht mehr nach Update 3.5.16 auf 3.5.18 ^{CODESYS Forge talk (Thread)}
KNX-Bus läuft nicht mehr nach Update 3.5.16 auf 3.5.18
Last updated: 2022-08-28

EtherCAT and Profinet Field bus on CodeSys V3.3 ^{CODESYS Forge talk (Thread)}
EtherCAT and Profinet Field bus on CodeSys V3.3
Last updated: 2009-03-20

Can Bus Teilnehmer mit einer Steuerung simulieren... ^{CODESYS Forge talk (Thread)}
Can Bus Teilnehmer mit einer Steuerung simulieren...
Last updated: 2012-06-06

Slaves einbinden in AS-i Bus Steuerung ^{CODESYS Forge talk (Thread)}
Slaves einbinden in AS-i Bus Steuerung
Last updated: 2007-11-26

CoDeSys SM 3.4.3 with ServoC CAN bus slaves via EtherCat ^{CODESYS Forge talk (Thread)}
CoDeSys SM 3.4.3 with ServoC CAN bus slaves via EtherCat
Last updated: 2011-07-08

1-Wire, ID eines Bus Teilnehmers über Variable setzen ^{CODESYS Forge talk (Thread)}
1-Wire, ID eines Bus Teilnehmers über Variable setzen
Last updated: 2015-09-28

Wago 758-870 keine Komunikation im K-Bus ^{CODESYS Forge talk (Thread)}
Wago 758-870 keine Komunikation im K-Bus
Last updated: 2012-11-27

Sort by relevance or date