Post by blitz on SMC_ERROR SMC_CGR_INVALID_POSPERIOD ^{CODESYS Forge talk (Post)}
Codesys - SMC_ERROR SMC_CGR_INVALID_POSPERIOD - Invalid modulo period less than or equal to zero or greater than half the bus bandwidth. Has anyone seen this error and actually understands what it means and how to get rid of it? I tried to work around it by reducing the number of increments on the drive but then the drive itself starts throwing errors.
Last updated: 2025-12-15

Post by farren on Codesys complains about matching versions ^{CODESYS Forge talk (Post)}
Thanks -- I'll try that.... -Farren
Last updated: 2025-12-16

Post by farren on Codesys complains about matching versions ^{CODESYS Forge talk (Post)}
Success!! Thanks! -Farren
Last updated: 2025-12-16

Codesys complains about matching versions ^{CODESYS Forge talk (Thread)}
Codesys complains about matching versions
Last updated: 2025-12-16

Post by bertus on Can't get SMC_SmoothPath to work ^{CODESYS Forge talk (Post)}
Hello all, I am trying to run a XY trajectory from a static G-Code file. Everything works except the smoothing/blending of the corners. My setup: Codesys v3.5sp18 Raspberry Pi 4 CODESYS Control for Raspberry Pi SL, using demo license. Zero axes (only using the interpolator). The order of processing for my decoding is: SMC_NCDecoder (ok) SMC_SmoothMerge (ok) SMC_SmoothPath (not ok) SMC_LimitDynamics SMC_CheckVelocities I created following instances and buffers: fbNCDecoder: SMC_NCDecoder; fbSmoothMerge: SMC_SmoothMerge; fbSmoothPath: SMC_SmoothPath; fbLimitDynamics: SMC_LimitDynamics; fbCheckVelocities: SMC_CheckVelocities; aNCDecoderBuffer: ARRAY[0..49] OF SMC_GeoInfo; // buffer stage 1 (fbNCDecoder) aSmoothMergeBuffer: ARRAY[0..19] OF SMC_GeoInfo; // buffer stage 2 (fbSmoothMerge) aSmoothPathBuffer: ARRAY[0..99] OF SMC_GeoInfo; // buffer stage 3 (fbSmoothPath) aLimitDynamicsBuffer: ARRAY[0..39] OF SMC_GeoInfo; // buffer stage 4 (fbLimitDynamics) My original G-Code file has a lot of short G1 elements but this example, I reduced it to a simple square: N000 G51 D10 N010 G38 O1 N020 G00 X0 Y0 F50 E1000 E-1000 N030 G01 X0 Y-37.5 N040 G01 X-75 Y-37.5 N050 G01 X-75 Y37.5 N060 G01 X0 Y37.5 N070 G01 X0 Y0 N080 G50 N090 G39 O1 In the Codesys CNC settings, I have these instances activated: SMC_SmoothMerge SMC_SmoothPath SMC_LimitDynamics SMC_CheckVelocities And with those settings (and the path-preprocessing button actived), the G-Code viewer shows the square with nicely blended corners (see attached picture). However, when running it on the PLC, it doesn't blend the corners at all. Below the relevant part of my code. The process is started with bDecode. // stage 1: decoding G-code fbNCDecoder( ncprog := square, bExecute:= bDecode, bAbort:= NOT bDecode, nSizeOutQueue := SIZEOF(aNCDecoderBuffer), pbyBufferOutQueue := ADR(aNCDecoderBuffer) ); // stage 2: merge short linear segments fbSmoothMerge( bExecute := bDecode, poqDataIn := fbNCDecoder.poqDataOut, nSizeOutQueue := SIZEOF(aSmoothMergeBuffer), pbyBufferOutQueue := ADR(aSmoothMergeBuffer), piMaxDifference := PI_MAX_DIFFERENCE, usiMaxDegree := 5, wFeatureFlag := 1, wAdditionalParamNumber := 0, dMinimumCurvatureRadius := D_MIN_CURVATURE_RADIUS ); // stage 3: smooth corners fbSmoothPath( bExecute := bDecode, bAbort := NOT bDecode, poqDataIn := fbSmoothMerge.poqDataOut, eMode := SMC_SMOOTHPATHMODE.SP_SPLINE5_MIN_CURVATURE, eAddAxMode := SMC_SMOOTHPATHADDAXMODE.SPAA_NONE, nSizeOutQueue := SIZEOF(aSmoothPathBuffer), pbyBufferOutQueue := ADR(aSmoothPathBuffer), dAngleTol := D_ANGLE_TOL, bSymmetricalDistances := TRUE, bImprovedSymmetricCuts := TRUE ); // stage 4: keep acc/dec and velocity within limits fbLimitDynamics( bExecute := bDecode, bAbort := NOT bDecode, poqDataIn := fbSmoothPath.poqDataOut, wAxis := 16#07, nSizeOutQueue := SIZEOF(aLimitDynamicsBuffer), pbyBufferOutQueue := ADR(aLimitDynamicsBuffer), bIncludePathSettings := TRUE, dMaxVel := 2500, dMaxAccDec := 10000 ); // stage 5: check the path speed fbCheckVelocities( bExecute := bDecode, bAbort := NOT bDecode, poqDataIn := fbLimitDynamics.poqDataOut, dAngleTol := D_ANGLE_TOL); pathQueue := fbCheckVelocities.poqDataOut; // repeat until MaxDuration ... Any idea what I'm doing wrong? Is smooth path supposed to work at all when using a demo license? Thanks.
Last updated: 2025-12-17

C0138: No matching 'FB_Init' method found for instantiation of VisuClientObjectMgr ^{CODESYS Forge talk (Thread)}
C0138: No matching 'FB_Init' method found for instantiation of VisuClientObjectMgr
Last updated: 2025-12-18

Post by bertus on Can't get SMC_SmoothPath to work ^{CODESYS Forge talk (Post)}
Hi Georg, thanks for your time. What is the value of D_ANGLE_TOL? It is set to 0.01. Do you need the assignment bAbort := NOT bDecoder? Does it help to leave it out? This seems to make no difference. Any errors (e.g. SMC_SmoothPath.Error/ErrorID) or PLC log messages? No errors or log messages. What if you comment out SMC_SmoothMerge and SMC_LimtiDynamics, is corner smoothing still not working? Indeed. Is bDecode written from a different task (e.g. visu)? Then I would recommend to assign to a local variable (bDecodeLocal := bDecode) and use that for all FBs. Otherwise, FBs might see different values of bDecode in a single cycle, which will cause problems. It is a local variable, written from a state machine inside this program. But there is new information: During some trial and error, I tried skipping "stage 2: merge short linear segments" (SMC_SmoothMerge). And suddenly it rounds the corners, see attached image. Looking a bit closer, I noticed that (with the original program) after a download (cold start?), it in fact did round the corners, but only once. Ever next cycle in which the NC program was executed, the corners where not rounded. Not sure if there is any relation, but SMC_SmoothMerge is also the only FB which has no bAbort input. Perhaps I need to reset it (or any buffers) by other means?
Last updated: 2025-12-18

Library documentation up to date ^{CODESYS Forge talk (Thread)}
Library documentation up to date
Last updated: 2025-12-22

Trend legend naming and access/config to/of trend/legend-variables ^{CODESYS Forge talk (Thread)}
Trend legend naming and access/config to/of trend/legend-variables
Last updated: 2025-12-22

Post by nguyenkhoi on Estun servo with codesys ^{CODESYS Forge talk (Post)}
Have you found it yet? I'm also searching for the EtherCat file config about the Estun Pronet Servo.
Last updated: 2025-12-23

Change Git local repository folder name ^{CODESYS Forge talk (Thread)}
Change Git local repository folder name
Last updated: 2025-12-23

Estun servo with codesys ^{CODESYS Forge talk (Thread)}
Estun servo with codesys
Last updated: 2025-12-23

Post by reinier-geers on wEBCLIENT Post data api ^{CODESYS Forge talk (Post)}
Ive got the webclient axample. If i put https://reversed.notion.site/Marktprijzen-API-89ce600a88ac4abe8c2ad89d3167a83e example to https://reqbin.com/post-online then i get data. If i do the same in Webclient example i get " not a valid graphql request. Why ? sUrl := 'https://graphql.frankenergie.nl/' Request_type_post Contenttype = 1 (json ) Postvalue := '{"query":{"query":"query MarketPrices {\n marketPrices(date:\"2025-12-25\") {\n electricityPrices {\n from\n till\n marketPrice\n marketPriceTax\n sourcingMarkupPrice\n energyTaxPrice\n perUnit\n }\n gasPrices {\n from\n till\n marketPrice\n marketPriceTax\n sourcingMarkupPrice\n energyTaxPrice\n perUnit\n }\n }\n}' I tranfer the postvalue from String to WSTRING
Last updated: 2025-12-25

SM3_CNC Sentence modifier ^{CODESYS Forge talk (Thread)}
SM3_CNC Sentence modifier
Last updated: 2025-12-25

Post by danamocca on SM3_CNC Sentence modifier ^{CODESYS Forge talk (Post)}
Hi! Does anyone have an example of ReadNCFile2 with Sentence Modifier? Current examples on CODESYS help page are outdated and have a lot of errors, like "SMC_CNC_LibParams.MAX_SUBPROGRAM_NESTING_DEPTH" calls, which are not present in current version of SMC3_CNC library.
Last updated: 2025-12-25

wEBCLIENT Post data api ^{CODESYS Forge talk (Thread)}
wEBCLIENT Post data api
Last updated: 2025-12-25

Deploying to raspberry pi 5 hangs ^{CODESYS Forge talk (Thread)}
Deploying to raspberry pi 5 hangs
Last updated: 2025-12-25

Post by bmatlove on Re-create CoE online window in Visu ^{CODESYS Forge talk (Post)}
Hello, I am trying to re-create the CoE online window within a Visu for purposes of checking and interacting with device parameters occasionally for maintenance purposes. To minimize reliance on using the IDE for misc interactions. Ideally, I would like to exactly mimic the CoE online window within the IDE. I assume that it uses a few tricks to minimize overhead, such as only polling registers which are within the visual scope, for example. I'm afraid it might be too much to ask for a pre-built drop-in Visu module to exist for this task. Do I have any options aside from manually re-creating all the logic to do this, relying heavily on SdoInfo function blocks? Is there a way for me to reference the device ESI file to shortcut the process of determining how many registers there are and getting the address for each?
Last updated: 2025-12-27

Re-create CoE online window in Visu ^{CODESYS Forge talk (Thread)}
Re-create CoE online window in Visu
Last updated: 2025-12-26

Post by karsonsv on CODESYS HMI and 2 monitors ^{CODESYS Forge talk (Post)}
I need open visualization on two monitors (every monitor 19201080). In TargetVisu i configure Scaling Options as Fixed 38401080. But visualization open onli main monitor and onli half.
Last updated: 2026-01-02

Alarmgruppenvorlage kann über Kontextmenü keine weitere Latch Variable hinzugefügt werden ^{CODESYS Forge talk (Thread)}
Alarmgruppenvorlage kann über Kontextmenü keine weitere Latch Variable hinzugefügt werden
Last updated: 2026-01-05

Post by worker69 on Alarmgruppenvorlage kann über Kontextmenü keine weitere Latch Variable hinzugefügt werden ^{CODESYS Forge talk (Post)}
Hallo, ich habe das problem, dass ich in einer Alarmgruppenvorlage keine wietere LATCh Variable hinzufügen kann. Wenn ich dies über das Kontextmenü versuche, dann erscheint folgende Fehlermeldung "Der Objektverweis wurde nicht auf eine Objektinstanz festgelegt". Ich verwende Codesys V3.5.19 P0 und 23.5.19 P7 Was mache ich falsch
Last updated: 2026-01-05

Post by tobiassantos on History of Alarms ^{CODESYS Forge talk (Post)}
I am running tests using the Windows runtime environment. The alarm history is not being logged and displays the error: "Some kind of disk I/O error occurred. Check disk space" in the alarm table. Furthermore, it is not possible to export the alarms. I have already tried to find a configuration field in Alarm storage and Alarm configuration to fix this problem, but I haven't found any related fields.
Last updated: 2026-01-05

Post by alexgooi on Codesys KNX implementation ^{CODESYS Forge talk (Post)}
Dear forum, We are currently doing some research on the Codesys KNX implementation (https://store.codesys.com/en/codesys-knx-sl.html). We almost have it working but we are missing the last part. The setup: We have a Codesys virtual control container running on docker (4.17.0.0), the I/O is running over an Ethernet IP coupler (Weidmüller), and this is running fine. As far as I’m concerned this tells me that the ethernet device is working properly (the container has access to the outside world, including multicast). Underneath this ethernet adapter the KNX module is added (see picture). In the KNX device (Codesys) 2 input variables are added (see picture), and these are exported to ETS (ETS 5). In ETS A Codesys KNX device has been imported and the Codesys export was imported, afterwards the group addresses are attached to the variables (see picture). Afterwards this configuration is downloaded to the Codesys controller (Container) via ETS. ETS asks for the pressing of the programming button, when the virtual programming button is pressed the download starts and finishes without any errors. This tells me that ETS is communicating with the Codesys controller, and that the download process is ok (so far so good). Now the part where we are struggling with, somehow we need to convert the KNX TP to KNX IP. For this we have the following interface: Zenio KIPI SC (https://www.zennio.com/product/kipi-sc/) this is a KNX TP to IP interface. We have the following setup for this device (see picture) (an IP in the same subnet is used). We tried multiple combinations of IP addresses but the TP devices are simply not communicating to the Codesys container. Does anyone has any advice on what to try next. To make the question more explicit how can we link the TP bus to the Codesys device? Kind Regards Alex
Last updated: 2026-01-05

History of Alarms ^{CODESYS Forge talk (Thread)}
History of Alarms
Last updated: 2026-01-05

Sort by relevance or date