Post by yoeri on Python script: Launch Codesys, Execute Script, Exit Codesys
CODESYS Forge
talk
(Post)
For whoever finds this old thread. Instead of System.exit(0), use system.exit(0) without capital 'S', this worked for me. I use these imports from future import print_function import sys import os
Last updated: 2026-02-12
Python script: Launch Codesys, Execute Script, Exit Codesys
CODESYS Forge
talk
(Thread)
Python script: Launch Codesys, Execute Script, Exit Codesys
Last updated: 2026-02-12
Home (version 1) discussion
dvmaris
wiki
(Thread)
Home (version 1) discussion
Last updated: 2026-02-12
Post by konstantin on CAM Motion Recover after STO
CODESYS Forge
talk
(Post)
Hello, one of the projects I work on is about a racetrack collator with two independent belts on it - two different servo motors. Both motors share the same mechanical frame and there is a train on a belt that collects items from the input conveyor. The way the motion is performed is the following - there is a virutal master axis and both real axis are synchronised with different cam motion profiles. The problem is when an STO is triggered on any of the slave axis, the synchronization process starts from position 0 of the slaves. How can I force the slaves to retain their current position until the master passes their position? Then the slaves should catch up with the master according to the profile, the slaves should not start synchronization from 0 position. Best Regards Konstantin Kolev
Last updated: 2026-02-12
Post by dvmaris on Control for Linux ARM64-User Management issue
CODESYS Forge
talk
(Post)
It was just that easy. Thanks @eschwellinger
Last updated: 2026-02-12
Control for Linux ARM64-User Management issue
CODESYS Forge
talk
(Thread)
Control for Linux ARM64-User Management issue
Last updated: 2026-02-12
Home (version 1) discussion
ppeychinov
wiki
(Thread)
Home (version 1) discussion
Last updated: 2026-02-12
Home (version 1) discussion
lunardi
wiki
(Thread)
Home (version 1) discussion
Last updated: 2026-02-12
Home (version 1) discussion
agedik
wiki
(Thread)
Home (version 1) discussion
Last updated: 2026-02-12
Home (version 1) discussion
muhammedraiz
wiki
(Thread)
Home (version 1) discussion
Last updated: 2026-02-12
Home (version 1) discussion
chuck
wiki
(Thread)
Home (version 1) discussion
Last updated: 2026-02-13
wiki Discussion
starday
wiki
(Discussion)
Forum for wiki comments
Last updated: 2026-02-12
blog Discussion
starday
blog
(Discussion)
Forum for blog comments
Last updated: 2026-02-12
(no subject)
starday
wiki
(Thread)
Last updated: 2026-02-12
Home
starday
wiki
(WikiPage)
Project Members: starday (admin)
Last updated: 2026-02-12
wiki Discussion
nirav1992
wiki
(Discussion)
Forum for wiki comments
Last updated: 2026-02-13
blog Discussion
nirav1992
blog
(Discussion)
Forum for blog comments
Last updated: 2026-02-13
(no subject)
nirav1992
wiki
(Thread)
Last updated: 2026-02-13
Home
nirav1992
wiki
(WikiPage)
Project Members: nirav1992 (admin)
Last updated: 2026-02-13
Post by gseidel on CAM Motion Recover after STO
CODESYS Forge
talk
(Post)
Dear Mr. Kolev, can you please explain a little more: what happens at an STO? I assume the slave axes will be stopped and retain their current position? How, then, do you call MC_CamIn after the STO? Do you restart it with a new rising edge, but on the same master position as before the STO? Which StartMode are you using, is the cam slave absolute or relative, master absolute or relative? Are the slave axes modulo or finite axes? Best regards, Georg Seidel
Last updated: 2026-02-13
Post by risele on dynamic modbus devices
CODESYS Forge
talk
(Post)
Have the same issue: I'm making a test setup for modbus devices testing and calibration. One is run for every possible address, and it starts with minimal request: if the device is found, it continue to work with it, otherwise it's set to Disabled temporary. Those state machines are running under FOR cycle, and disabled are just skipped. Every instance have its own timer for not running too frequently and a start delay, so the actual requests are separate in time. I also check not for a single error, but have some timer to allow one-two timeouts. The small program disables and re-enables devices temporary (manually, since i could not iterate over MB devices). VAR Reset:ARRAY[1..GVL_MB.MD_COUNT] OF R_TRIG; i:INT; END_VAR {IF hasconstantvalue(GVL_MB.MD_COUNT, 1, >= )} i:=1; MD_1.Enable:=GVL_MB.MDPortsEnable[i]; Reset[i](CLK:=GVL_MB.MDPortsEnable[i]); MD_1.xReset:=Reset[i].Q; {END_IF} {IF hasconstantvalue(GVL_MB.MD_COUNT, 2, >= )} i:=2; MD_2.Enable:=GVL_MB.MDPortsEnable[i]; Reset[i](CLK:=GVL_MB.MDPortsEnable[i]); MD_2.xReset:=Reset[i].Q; {END_IF} There is also program to re-enable devices periodically. METHOD ScanBus VAR_INPUT END_VAR VAR j:INT; (*block auto scanning if calibration is running for any device since it's data-reach process that should not be interrupted with modbus timeouts *) CalibrationBusy:BOOL:=FALSE; END_VAR CalibrationBusy:=FALSE; FOR j:=1 TO GVL_MB.MD_COUNT DO CalibrationBusy:=CalibrationBusy OR MD_Calibrate.AutoTesters[j].xBusy; END_FOR; IF CalibrationBusy THEN RETURN; END_IF tBusScanSchedule(IN:=(NOT tBusScanSchedule.Q), PT:=tBusScanPeriod); IF (NOT tBusScanDelayer.Q) AND (tBusScanSchedule.Q OR (NOT xFirstScanPerforemed)) THEN xBusScanBusy:=TRUE; MissingCounter:=0; xFirstScanPerforemed:=TRUE; FOR j:=1 TO GVL_MB.MD_COUNT DO (* MD_Calibrate is main calibration program. Identifiers - is array of State machines mentioned above Phase_Faulted is a state of Identifiers where I'm sure device is missing on the bus *) IF MD_Calibrate.Identifiers[j].state=eStateMDIdentifier.Phase_Faulted THEN MD_Calibrate.Identifiers[j].Rescan(); MissingCounter:=MissingCounter+1; END_IF END_FOR END_IF tBusScanPauser(IN:=tBusScanDelayer.Q AND (MissingCounter>0),PT:=tBusScanDelay*MissingCounter); xBusScanBusy:=tBusScanPauser.Q; xFirstScanPerforemed:=xFirstScanPerforemed OR tBusScanPauser.ET>=tBusScanPauser.PT; Also the GUI have buttons for each address possible that re-enables the device if required.
Last updated: 2026-02-13
Post by yannickasselin on Lenze i950 Servo and WAGO PFC200
CODESYS Forge
talk
(Post)
In order to use SoftMotion Light, a servo drive needs to support CiA 402 operating modes: Profile Position (PP), Profile Velocity (PV) and Homing Mode (HM). https://content.helpme-codesys.com/en/CODESYS%20SoftMotion%20Light/_sm_light_requirements.html According to the Lenze i950 documentation you linked in your post, none of these modes are supported. Not even Homing Mode which explains why MC_Home does not work even with the full SoftMotion. The full SoftMotion uses Cyclic Synchronous Position Mode (CSP) but still uses Homing Mode (HM) when using MC_Home. You can monitor PDO 0x6060 (Mode of Operation). When using SoftMotion Light you will see it set to 1 (PP) for a MC_MoveAbsolute_SML and MC_MoveRelative_SML and to 3 (PV) for MC_MoveVelocity_SML and to 6 (HM) for MC_Home_SML. When using the SoftMotion instructions, it will pretty much always be set to 8 (CSP) except when using MC_Home, then it will be set to 6 (HM).
Last updated: 2026-02-13
Codesys V2.3 🇬🇧
CODESYS Forge
talk
(Discussion)
Forum about V2.3
Last updated: 2026-02-13
Post by risele on AI + Programming
CODESYS Forge
talk
(Post)
It's already fine to use, with help of exporting/importing as PLC_Open, at least CODEX is good in editing directly at XML and/or providing changes description separately.
Last updated: 2026-02-13
CODESYS and Github Copilot
CODESYS Forge
talk
(Thread)
CODESYS and Github Copilot
Last updated: 2026-02-13