Post by testyhalftime on Version management ^{CODESYS Forge talk (Post)}
Hi Suyash! To avoid library mismatch errors in CODESYS, always use the same IDE version your project was created with. Use the Library Manager to check and update libraries. For consistent results, keep a record of project and library versions, and avoid auto-updates unless necessary. https://forge.codesys.com/forge/talk/Engineering/thread/ea1bdacd28/Geometry Dash
Last updated: 2025-12-14

Post by buarq12 on Version management ^{CODESYS Forge talk (Post)}
Play on a reliable Pakistan casino gaming site offering secure access and exciting gameplay. Enjoy real-money games, smooth performance, and trusted payouts. https://royalxcasinoz.pk/
Last updated: 2025-12-14

Post by farren on Codesys complains about matching versions ^{CODESYS Forge talk (Post)}
I'm building up a 2nd PC to match an existing developer PC. Installed the same SP and Patch levels but when I open a project that was created on the existing PC, Codesys complains that it's not the same version. Attaching a screenshot..... What else is there to match? Also, can all of the libraries that are on the existing machine be copied from it to the new machine and if so, how? (So I get the same versions) Which files/folders do I copy? Thanks! -Farren
Last updated: 2025-12-14

Post by timvh on Codesys complains about matching versions ^{CODESYS Forge talk (Post)}
Open the CODESYS Installer. Create an export file from your current PC from your current version. Then on the other PC Open the installer and install a new version based on the same essentials version, but additionally select the export file which you have created on the first PC. Or just install (import) it within the already existing version. For the installer, you can install it from: https://store.codesys.com/en/codesys-installer.html For help see: https://content.helpme-codesys.com/en/CODESYS%20Installer/_inst_install_setups_and_addons.html On PC 1, save the project as projectarchive (which will then include all the libraries and devices). Then extract this projectarchive on PC 2.
Last updated: 2025-12-15

Post by ph0010421 on Codesys complains about matching versions ^{CODESYS Forge talk (Post)}
hi I don't have an answer but I have the same message with that version, too.
Last updated: 2025-12-15

Post by ph0010421 on Codesys complains about matching versions ^{CODESYS Forge talk (Post)}
hi I don't have an answer but I have the same message with that version, too.
Last updated: 2025-12-15

(no subject) ^{Trend API Example home (Thread)}
Last updated: 2025-12-15

Home ^{Trend API Example home (WikiPage)}
Download project Trend API Example Product description More information System requirements and restrictions Trend API Example The "Trend API Example" demonstrates how the VisuTrendStorageAccess library provides function blocks for reading trend data. This document illustrates how to use the library. Product description The sample project demonstrates how trend data can be read by means of the VisuTrendStorageAccess library. In this example, trend data is saved by the trend recording manager and then read as ST code by the VisuTrendStorageAccess API. In addition to querying historical data, active messaging is also possible when saving new data. The trend data can then be exported (example: CSV file) for later processing by other applications, for example by using the IIoT Libraries SL from the CODESYS Store. More information In the sample project "TrendStorage API Example.project", four tasks are defined. The "Standard task" calls the PLC_PRG program for simulating data. The simulated data is saved to the database by the "TrendRecordingTask" and the Trend Recording Manager. The "VISU_TASK" is responsible for updating the visualization. The actual reading of trend data is performed by "Task200ms", the "TrendStorageAPI_TestProg" program, and the "TrendStorageReader" function block. The ITrendStorageWriterListener interface is used for active messaging of new data. For this purpose, the TrendStorageWriterListener function block implements the ITrendStorageWriterListener interface and is registered for the TrendStorageReader function block. If new data has been saved, then the DataWritten method is called with the start and end time stamps and the number of saved data records. The TrendStorageReader and the Read method are used for searching for data records. eError2 := instTrendStorageReader.Read( liTimstampFrom := liTimstampFrom2, liTimstampTo := liTimstampTo2, itfTrendStorageReaderConsumer := instTrendStorageReaderConsumer); The TimeStampRead and ValueRead methods are then called automatically for each value. In the example, the TrendStorageReaderConsumer function block implements the ITrendStorageReaderConsumer interface and writes the values to the controller console in CSV format. If the size of the returned data would block the database too long, then ETrendStorageReaderErrors.AdditionalReadCallRequired is returned as error code and the read process must be continued at a later time by calling the ContinueReading method with the same parameters. Description of the visualization The simulated signals are displayed in a trend element in the upper area of the visualization. The minimum and maximum time stamps of the trend data are displayed in the "Min/Max Time" tab (see Figure 1). The current values of the DataWritten method are displayed in "New Data" (see Figure 2). Values are searched in the "Read Values" tab (see Figure 3). The start time stamp is displayed in the upper field and the end time stamp in the lower field. The "Compute timestamps" button converts the specified data into the corresponding time stamp (reverse function: "Compute date/time"). Then the search can be started by clicking the "Read Trend Storage" button. Clicking "Stop Reading" will cancel the read process. If the "Detailed output" button is active, then the data is printed to the controller console (do not start CODESYS Control Win V3 via SysTray). Otherwise, the number of data records is displayed in the "count rows" field. System requirements and restrictions System requirements and restrictions Info Programming System CODESYS Development System Version 3.5.14.0 or higher Runtime System CODESYS Control Version 3.5.14.0 Required Accessories - Tab "Min/Max Time" Tab "New Data" Tab "Read Values"
Last updated: 2025-12-15

Home (version 1) discussion ^{todorovtt wiki (Thread)}
Home (version 1) discussion
Last updated: 2025-12-15

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 pernockham on Discussion for Home page ^{Trend API Example home (Post)}
Trying to use the example, but get compiler error (1), not sure how to solve it? Searching for ITypeVisitor in the project yields nothing. Reason for checking example is I need to find a way to display "custom" names on trend signals ie/example: "Inlet temp heater" instead of programmatic reference "PLC_prog.input.temp_inlet_heater" Edit: Managed to download a working version through the "Codesys installer". Not sure it brought me closer to understanding how I should implement the custom naming in the trend legend though.
Last updated: 2025-12-16

Home (version 1) discussion ^{anuarbedhief01 wiki (Thread)}
Home (version 1) discussion
Last updated: 2025-12-16

Home (version 1) discussion ^{seikosta wiki (Thread)}
Home (version 1) discussion
Last updated: 2025-12-16

Home (version 1) discussion ^{gjiorg wiki (Thread)}
Home (version 1) discussion
Last updated: 2025-12-16

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

wiki Discussion ^{willebro wiki (Discussion)}
Forum for wiki comments
Last updated: 2025-12-16

blog Discussion ^{willebro blog (Discussion)}
Forum for blog comments
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

Post by willebro on "Distributed clocks are not synchronized, Rea time problem on hardware" ? ^{CODESYS Forge talk (Post)}
Last updated: 2025-12-17

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

Home (version 1) discussion ^{ahmtplt wiki (Thread)}
Home (version 1) discussion
Last updated: 2025-12-17

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

wiki Discussion ^{bertus wiki (Discussion)}
Forum for wiki comments
Last updated: 2025-12-17

blog Discussion ^{bertus blog (Discussion)}
Forum for blog comments
Last updated: 2025-12-17

(no subject) ^{bertus wiki (Thread)}
Last updated: 2025-12-17

Sort by relevance or date