variables not retained through power cycle? ^{CODESYS Forge talk (Thread)}
variables not retained through power cycle?
Last updated: 2016-07-24

Cycle Task of a SoftMotion Axis ^{CODESYS Forge talk (Thread)}
Cycle Task of a SoftMotion Axis
Last updated: 2020-12-14

Alarm Manager missing single cycle alarms ^{CODESYS Forge talk (Thread)}
Alarm Manager missing single cycle alarms
Last updated: 2022-02-24

RPI can system operation like rm in a shell have an impact on a Task cycle time ^{CODESYS Forge talk (Thread)}
RPI can system operation like rm in a shell have an impact on a Task cycle time
Last updated: 2024-09-27

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

WebVisu - displaying controller time (UTC) in local time ^{CODESYS Forge talk (Thread)}
WebVisu - displaying controller time (UTC) in local time
Last updated: 2020-07-08

Post by ton on How to create a stopwatch? ^{CODESYS Forge talk (Post)}
If you use LTIME() you will be very accurate and be able to have a normal task cycle time.
Last updated: 2023-12-16

Post by eschwellinger on RPI can system operation like rm in a shell have an impact on a Task cycle time ^{CODESYS Forge talk (Post)}
Which version exactly do you use?
Last updated: 2024-09-23

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

Multiple tasks with different task cycle times ^{CODESYS Forge talk (Thread)}
Multiple tasks with different task cycle times
Last updated: 2016-02-12

Using Profinet task as bus cycle task ^{CODESYS Forge talk (Thread)}
Using Profinet task as bus cycle task
Last updated: 2020-09-07

How to get 'Bus cycle task name' from libraries? ^{CODESYS Forge talk (Thread)}
How to get 'Bus cycle task name' from libraries?
Last updated: 2019-11-05

How to access task cycle in program ^{CODESYS Forge talk (Thread)}
How to access task cycle in program
Last updated: 2012-11-23

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

Main Task cycle too long leading to PLC Fail ^{CODESYS Forge talk (Thread)}
Main Task cycle too long leading to PLC Fail
Last updated: 2024-03-08

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

Frage zu Time(). ^{CODESYS Forge talk (Thread)}
Frage zu Time().
Last updated: 2007-07-23

Elapsed time? ^{CODESYS Forge talk (Thread)}
Elapsed time?
Last updated: 2006-10-05

Adjust display time ^{CODESYS Forge talk (Thread)}
Adjust display time
Last updated: 2019-04-09

PLC input time ^{CODESYS Forge talk (Thread)}
PLC input time
Last updated: 2018-10-23

current time from PY ^{CODESYS Forge talk (Thread)}
current time from PY
Last updated: 2016-07-17

string to time ^{CODESYS Forge talk (Thread)}
string to time
Last updated: 2010-03-08

Raspberry and local time ^{CODESYS Forge talk (Thread)}
Raspberry and local time
Last updated: 2020-05-14

Sort by relevance or date