When using the Element Collections library, is there a proper way to remove a dynamically created collection from memory? ^{CODESYS Forge talk (Thread)}
When using the Element Collections library, is there a proper way to remove a dynamically created collection from memory?
Last updated: 2022-09-08

When using the Element Collections library, is there a proper way to remove a dynamically created collection from memory? ^{CODESYS Forge talk (Thread)}
When using the Element Collections library, is there a proper way to remove a dynamically created collection from memory?
Last updated: 2023-10-31

Post by sturmghost on Find visualization elements that require a lot of computing time ^{CODESYS Forge talk (Post)}
I found out that the Codesys simulation mode is not good to measure performance. As soon as I upload the code onto the hardware PLC I can see that my visu-task needs around 60 ms to complete. I'm wondering if there is a possibility to find out which visualization/visualization element takes a lot of computing time? Then I would look for ways to decrease the long computing time.
Last updated: 2024-01-22

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 snhatton on Visu - changing auto-logout time ^{CODESYS Forge talk (Post)}
You could try using the VUM_UserGroup struct from the VisuUserManagement library. I haven't tried this, but there is a variable for tAutoLogout to set the logout time.
Last updated: 2023-12-11

Post by manuknecht on Maximum dynamic limits of MC_MoveLinearAbsolute and MC_MoveLinearRelative ^{CODESYS Forge talk (Post)}
Hello all I use an axis group with two linear axes in a kinematic system. Using MC_MoveLinearAbsolute and MC_MoveLinearRelative, I am trying to realise dynamic movements (set velocity: 1 m/s, set acceleration: 30 m/s^2) with the highest possible jerk, as I want to compare this with a movement with a trapezoidal velocity profile. However, my measurements show that the axes accelerate with a maximum jerk of approx. 800 m/s^3, even if the value in the function block was set to 10,000 m/s^3. I have already increased the dynamic limits of the two axes accordingly (Velocity: 5000 u/s, Acc-/Deceleration: 250'000 u/s^2, Jerk: 100'000'000 u/s^3, where 1 u = 1 mm), but this had no effect. I have checked the input parameters of the function blocks and the VelFactor, AccFactor and JerkFactor factors are all set to the maximum (value 1). Reducing the cycle time has resulted in a higher jerk, but as we are already working with a cycle time of 1 ms, there is nothing more that can be done here. The axes themselves are still a long way from drawing the maximum current, which is why I assume that this should not be a problem either. Are there other factors or parameters that influence the dynamic limits and therefore allow faster movements? The PLC I am using is a Raspberry Pi 4 and Codesys V3.5 SP20 with all libraries up to date. Thanks in advance Manuel
Last updated: 2024-05-08

Post by dkugler on Converting hex bytes to float ^{CODESYS Forge talk (Post)}
have a look at UNIONs. With a union you are able to write single bytes to the same adress area which belongs to a float variable at the same time. I like to do a lot of convertions belonging to interfaces and fieldbus in this way, f.eg. word / byte swapping etc.
Last updated: 2024-08-06

Post by sturmghost on Initialization of visualization variables and cyclic code execution ^{CODESYS Forge talk (Post)}
I'm looking for a smart and short way to implement initialization of visualization variables depending on the visualization input. For an easy example consider a rectangle which rests at XPos := 0 when the input state is false and at XPos := 50 when the input state is true. My visualization variables look like this: VAR_IN_OUT State : BOOL; END_VAR VAR XPos : INT; END_VAR I put this rectangle via a visualization frame element into another visualization and link a frame reference variable with the state to it. If the variable is true, the rectangle should rest at XPos := 50 and false at XPos := 0 at visualization init but how should I assign the 50 or 0 to the internal visualization variable XPos? I would need some init-methode for the visualization but I dont want a global init-method for such tasks. I want to do it inside of the visualization element but I can't see any solution for this? It would be good to be able to define ST-code within the visualization element which runs cyclic at each VISU_TASK task-cycle then I could just check the input state and change the XPos accordingly. Does someone have a solution?
Last updated: 2023-10-01

Set memory in SFC ^{CODESYS Forge talk (Thread)}
Set memory in SFC
Last updated: 2015-10-09

EtherCAT Set Slave State ^{CODESYS Forge talk (Thread)}
EtherCAT Set Slave State
Last updated: 2017-09-04

Get/Set project information ^{CODESYS Forge talk (Thread)}
Get/Set project information
Last updated: 2012-04-23

Profinet Device IP set ^{CODESYS Forge talk (Thread)}
Profinet Device IP set
Last updated: 2017-09-06

Set color ^{CODESYS Forge talk (Thread)}
Set color
Last updated: 2008-03-14

Property - Set private ^{CODESYS Forge talk (Thread)}
Property - Set private
Last updated: 2015-08-05

Sensor not set ^{CODESYS Forge talk (Thread)}
Sensor not set
Last updated: 2024-05-28

Visualization Size - Set Layout ^{CODESYS Forge talk (Thread)}
Visualization Size - Set Layout
Last updated: 4 days ago

Post by dkugler on Calculate Time Between Two Events Using RTC ^{CODESYS Forge talk (Post)}
a few seconds later with google search... https://stackoverflow.com/a/61986234 SYS_TIME is definitely an ABB AC500 specific function, included in library SysInt_AC500_V10.lib.
Last updated: 2024-08-14

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

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 mubeta on Some 'pathetic' errors in SoftMotion program ^{CODESYS Forge talk (Post)}
Yes, this point is part of my misunderstanding. Why, after the execution ot the motion FBs is set to FALSE and exsecuted at lest one time, it must be continuosly called, even if the motion control it's take from another subsequent instruction. This is what I really don't undertand, but what in fact it's happening. For example, in case of stopping a MoveVelocity FB, then Halting the motion by the related FB, the axis at spot goes into error. If there was bad trigger management, the various instructions would NEVER work.
Last updated: 2024-07-18

RPI Modbus RTU - two slave device ^{CODESYS Forge talk (Thread)}
RPI Modbus RTU - two slave device
Last updated: 2022-09-15

Compare two projects using Python Script ^{CODESYS Forge talk (Thread)}
Compare two projects using Python Script
Last updated: 2020-10-15

Two PLC's in one visualization? ^{CODESYS Forge talk (Thread)}
Two PLC's in one visualization?
Last updated: 2014-12-08

communicate two PLCs using CANOpen protocol ^{CODESYS Forge talk (Thread)}
communicate two PLCs using CANOpen protocol
Last updated: 2019-06-20

Change two vizualization by bool variable ^{CODESYS Forge talk (Thread)}
Change two vizualization by bool variable
Last updated: 2014-04-15

Sort by relevance or date