POINTER TO STRUCT ^{CODESYS Forge talk (Thread)}
POINTER TO STRUCT
Last updated: 2015-07-10

WinCC to CODESYS ^{CODESYS Forge talk (Thread)}
WinCC to CODESYS
Last updated: 2021-08-30

Access to disk_sys ^{CODESYS Forge talk (Thread)}
Access to disk_sys
Last updated: 2011-12-22

How to configure J1939ECU ^{CODESYS Forge talk (Thread)}
How to configure J1939ECU
Last updated: 2013-03-13

Unable to scan ^{CODESYS Forge talk (Thread)}
Unable to scan
Last updated: 2022-06-15

To implement G-code ^{CODESYS Forge talk (Thread)}
To implement G-code
Last updated: 2012-10-31

Limits to Visualization ^{CODESYS Forge talk (Thread)}
Limits to Visualization
Last updated: 2017-03-10

Migration to Win7 ^{CODESYS Forge talk (Thread)}
Migration to Win7
Last updated: 2011-05-31

Adding "modules" to GSDML ^{CODESYS Forge talk (Thread)}
Adding "modules" to GSDML
Last updated: 2018-11-29

conversion V2 to V3 ^{CODESYS Forge talk (Thread)}
conversion V2 to V3
Last updated: 2013-10-08

ModbusFB.ClientTcp - How to disconnect?? ^{CODESYS Forge talk (Thread)}
ModbusFB.ClientTcp - How to disconnect??
Last updated: 2022-05-27

Excel to Codesys 3.5 ^{CODESYS Forge talk (Thread)}
Excel to Codesys 3.5
Last updated: 2023-12-11

Excel to Codesys 3.5 ^{CODESYS Forge talk (Thread)}
Excel to Codesys 3.5
Last updated: 2023-12-12

Possibility to deactivate CmpBlkDrvUdp ^{CODESYS Forge talk (Thread)}
Possibility to deactivate CmpBlkDrvUdp
Last updated: 2023-12-13

Raspberry add to codesys ^{CODESYS Forge talk (Thread)}
Raspberry add to codesys
Last updated: 2024-01-08

PWM To analog ^{CODESYS Forge talk (Thread)}
PWM To analog
Last updated: 2024-01-12

POU - Access to runtime ^{CODESYS Forge talk (Thread)}
POU - Access to runtime
Last updated: 2024-03-02

How to change bHiresMode ^{CODESYS Forge talk (Thread)}
How to change bHiresMode
Last updated: 2024-03-12

CODESYSControl_User.cfg - link to documentation? ^{CODESYS Forge talk (Thread)}
CODESYSControl_User.cfg - link to documentation?
Last updated: 2024-06-11

Data to server ^{CODESYS Forge talk (Thread)}
Data to server
Last updated: 2025-11-11

Post by duvanmoreno24 on Modbus writing on value change ^{CODESYS Forge talk (Post)}
Yes, I tried to do what you put in the first code. However, I have a problem with that and that is that the inputs must be declared with the type. I have many data types running in my code (real, int, uint, bool) and I can't put them in the same function, another thing is that I need to instantiate that function for everything I want to write to the slave. You put a for to 200 but it means that it has to be the same data type and inside the array, but I want to get them individually. I'm struggling to do it in a good and efficient way like wago's E-cockpit does. in the first screenshot you can see, you simply type in value, change the package of things you want to write in value change and it does everything by itself automatically, without comparing any old and new values and even less having the need to activate a bool. , it is perfect.
Last updated: 2024-04-03

Post by davidbo on RETAIN PERSISTENT only stored at gracefully shutdown? ^{CODESYS Forge talk (Post)}
I have {attribute 'checksumnoinit_override' := '2629838988'} {attribute 'init_related_code' := '5c6efcf8-e0f4-4166-a9fa-17eadd8908df'} VAR_GLOBAL RETAIN PERSISTENT {attribute 'order_in_persistent_editor' := '0'} segmentValue: ARRAY[0..49] OF REAL; {attribute 'order_in_persistent_editor' := '1'} segmentTime: ARRAY[0..49] OF REAL; // Generated instance path of persistent variable PRG.test: INT; // Generated instance path of persistent variable PRG.nw_storage: SysSocket_Implementation.SysSocket_Interfaces.SOCK_ADAPTER_INFORMATION2; END_VAR When I have changed PRG.nw_storage it will not be stored at a power off, but if I do a: sudo systemctl restart codesycontrol and then a power off it will be stored. Is there a way to store persistent variables without a restart of codesyscontrol? Can anyone explain how and when CODESYS store persistent variables?
Last updated: 2025-11-17

Post by laurits on Max lines of code, codesys CNC ? ^{CODESYS Forge talk (Post)}
Hi, yes now its working, to get "QUEUE.bFull" to work, I've had to set the "QUEUE.nNumReservedEntries" to 3. (I tried different values here, only effect for larger values i can see is the the queue capacity gets smaller.) I've noticed the movement is slowing down when it reaches the end of the "fill Up", must be because of the "checkVelocity" can only see the current "QUEUE". Any way of solving this ? BUF : ARRAY[0..20000] OF SMC_GEOINFO; xp : ARRAY[1..100000] OF REAL; yp : ARRAY[1..100000] OF REAL; CASE iState OF 000: IF R_TRIG_bStart.Q THEN iState := iState + 1; END_IF bReady := FALSE; //initialize Queue GEO.dT1:=0; GEO.dT2:=1; GEO.dToolRadius := 0; GEO.dVel := 15000; GEO.dVelEnd := 15000; GEO.dAccel := 2000; GEO.dDecel := 2000; GEO.iObjNo := 0; GEO.piDestPos.dX := 0; GEO.piDestPos.dY := 0; QUEUE.bEndOfList := FALSE; QUEUE.nPastMarker := -1; QUEUE.nWritePos := 0; QUEUE.pbyBuffer := ADR(BUF[0]); n := 0; sMC_CheckVelocities(bExecute:= FALSE); SM3_CNC.SMC_SetQueueCapacity(ADR(QUEUE), SIZEOF(BUF)); QUEUE.nNumReservedEntries := 3; 001: FOR i := 1 TO SIZEOF(xp)/SIZEOF(xp[1]) DO xp[i] := UDINT_TO_REAL(i) * 0.01; yp[i] := UDINT_TO_REAL(i) * 0.01; END_FOR iState := iState + 1; 002: WHILE NOT QUEUE.bFull DO // when the Queue is full, wait until it has been processed by the following FBs n := n + 1; GEO.iSourceLine_No := n; GEO.piStartPos := GEO.piDestPos; // copy last destination GEO.iMoveType := LIN; // generate linear movement GEO.iObjNo := GEO.iObjNo + 1; // calculate number GEO.piDestPos.dX := xp[n]; // generate position GEO.piDestPos.dY := yp[n]; SMC_CalcLengthGeo(pg := ADR(GEO)); // calculate length of object with the help of the standard function SMC_AppendObj(poq:=ADR(QUEUE), pgi:=ADR(GEO)); //append object to queue IF n = UDINT_TO_DINT( SIZEOF(xp)/SIZEOF(xp[1])) THEN // all target positions processed QUEUE.bEndOfList := TRUE; iState := iState + 1; EXIT; END_IF END_WHILE sMC_CheckVelocities(bExecute:= TRUE, poqDataIn:= ADR(QUEUE)); bReady := TRUE; // Send message to smc_interpolator to start 003:
Last updated: 2025-06-04

Post by bmatlove on Variable Length Array - Cannot mix variable and fixed length dimensions? ^{CODESYS Forge talk (Post)}
Using Codesys 3.5.18.30 I am trying to work with an array of variable length in one dimension, but known in the other dimension. For example, using an array that represents a list of items, each with an attribute profile. I do not know how many items will be in the list, but I know that every item has 5 attributes, like size, weight, etc. Codesys does not seem to be able to accept this. I have referenced Data Type: ARRAY OF documentation page, which is not explicit if variable & fixed length array dimensions can be mixed. In the VAR_IN_OUT scope, I initially tried MY_ARRAY : ARRAY [*, *] OF REAL; which was no problem, of course. I then modified it to MY_ARRAY : ARRAY [*, 1..5] OF REAL; which throws C0006: ', or ]' expected instead of '..' among consequent downstream errors. I then used the Auto Declare -> Array Wizard, which accepted (asterisk)-(asterisk) and 1-5 for 2-dimensional lower and upper bounds. It output: MY_ARRAY: ARRAY[*..*, 1..6] OF INT; which throws the same error stream. What's the deal here? Is this possible?
Last updated: 2025-05-23

Post by axilleas on SMC_Interpolator + SMC_controAxislbyPos ^{CODESYS Forge talk (Post)}
dear all I am working on a very generic gantry system (virtual drives + win v3 control) reading gcode from external file. In order to stop the interpolator function from running when gaps are detected, SMC_controlAxisByPos FB has the bStopIpo output which according to the manual is connected to the Interpolator's bEmergencyStop. Lets assume that the axis are parked in position X1000 Y1000 and the initial G code movement is G00 X500 Y500. The normal behavior is to travel from the actual x1000 y1000 to G00 X500 Y500. The SMC_Interpolator always gets the X0 Y0 as the initial position, meaning that the bStopIpo is active until the axis are in X0 Y0 and the release the interpolator to set the new positions to X500 Y500. Is there a suggested method to solve this behavior? bonus question: I get a lot of bStopIpo during standard interpolation movements (not gaps). While working with virtual axis this is not a problem but when real axis are installed this will be an issue. What exactly triggers the bStopIpo output? Slow axis accelerations compare to Gcode defaults? Kind Regards
Last updated: 2024-02-05

Sort by relevance or date