Post by oi18ct on ARM SL Development Board Recommendation ^{CODESYS Forge talk (Post)}
Hello codesys forum, My company is looking at developing a solution with Codesys ARM SL. The requirements will not tax the capabilities of Codesys. I would like to buy an AMR 7 or 8 Dev Board for experimenting. I am looking for a recommendation as I have minimal experience with Linux. Any input from the forum would be most appreciated as the hardware requirements as provided by Codesys for ARM SL seem pretty minimal (basically a arm7 or 8 with Debian is all). Our needs are small in scale- something like 8 digital inputs, 6 digital outputs, 2 analog inputs and 1 analog output. A small gui will be published via web visualization for external display (no local display). Communications with ModbusTCP and uart/RS485. It may be necessary to access i2c and make c or python calls to some existing code that is pretty small. Something like the EMCraft STM32MP1 SOM Starter Kit or Octavo Systems OSD32MP1-RED development board? Ideally something that has a path to a SoM for production. Kontron appears to have some interesting options too. Just having a hard time deciding where to start. Thanks in advance... LC
Last updated: 2023-11-11

Post by timvh on License problem gateway ^{CODESYS Forge talk (Post)}
What we are trying to explain is that, yes CODESYS creates the software, but Epis decides how they implement it on their hardware, which runtime version they use and they decide which functionality they support. So it is always a combination of the two. What CODESYS provides is a runtime with options for e.g. visualization or softmotion. Epis could add this softmotion license as default to their controller, but if they don't then CODESYS provides another option with a single license in a "Wibu CodeMeter" container. Eventhough the feature exists, Epis has to add this "CodeMeter" software on their controller to be able to access the licenses in the container. We don't know if they did this. Then finally it depends on what type of runtime is on this controller and which license Epis is using. So if they have an OEM license (not an application based license), then most likely you will need the Softmotion license (not a number of axis). See https://store.codesys.com/en/codesys-softmotion-sl-bundle.html. But to be sure if this is supported by the Epis controller, you must ask Epis.
Last updated: 2024-04-30

Post by meke001 on Visualisierungswerkzeuge ^{CODESYS Forge talk (Post)}
Hallo zusammen, ich habe ein hartnäckiges Problem mit der CODESYS-Visualisierung und hoffe auf eure Expertise. In meinem Projekt wird die Toolbox ("Werkzeuge") für die Visualisierung komplett leer angezeigt, es lassen sich also keine Basis-Elemente wie Rechtecke oder Kreise in die Zeichenfläche ziehen. Mein System: CODESYS V3.5 SP22 Patch 2 (64-bit) Device / Compiler-Version: 3.5.22.20 Das Kuriose:Das eigentliche Projekt läuft absolut einwandfrei. Mein Programmcode lässt sich ohne Probleme übersetzen, die SPS-Logik funktioniert fehlerfrei und auch die Simulation läuft einwandfrei durch. Nur das "Gesicht" des Projekts fehlt. Zwischendurch tauchte in den Meldungen der Fehler auf: Die Bibliothek '#System_VisuElems' konnte nicht aufgelöst werden. Was ich bereits zur Fehlerbehebung versucht habe: Installer-Check: Im CODESYS Installer geprüft, ob das Add-on "CODESYS Visualization" installiert ist (ist vorhanden und aktiv). Profil erzwungen: Im Visualisierungsmanager das Visualisierungsprofil manuell auf die aktuellste Version gesetzt. Gerät aktualisiert: Das Device im Projektbaum per Rechtsklick sauber auf die Version 3.5.22.20 hochgezogen. Clean Build: Mehrfach "Alles bereinigen" ausgeführt und neu übersetzt. Neues Projekt: Selbst wenn ich ein komplett neues Standardprojekt anlege, fehlen die Werkzeuge in der Visualisierung weiterhin. Hat jemand von euch eine Idee, woran das noch liegen könnte? Gibt es unter Windows eventuell einen versteckten Cache-Ordner für die Visualisierungs-Bibliotheken, den man manuell leeren muss? Für jeden Tipp wäre ich sehr dankbar! Viele Grüße
Last updated: 2026-06-15

Post by yannickasselin on CloseTargetVisu ^{CODESYS Forge talk (Post)}
To shutdown the TargetVisu: Add the VisuElemBase library to your project then call VisuElemBase.Visu_PRG.RemoveAllTargetVisuClients(); Exemple: PROGRAM PLC_PRG VAR xShutdownTargetVisu: BOOL; END_VAR ---------------------------------- IF xShutdownTargetVisu THEN xShutdownTargetVisu := FALSE; VisuElemBase.Visu_PRG.RemoveAllTargetVisuClients(); END_IF I tried calling RemoveAllTargetVisuClients() directly from a button mouse click event but it makes the Visu crash. So better using the code above and just set xShutdownTargetVisu to TRUE from the button. Works fine for me. To start the TargetVisu: From a cmd prompt. This will start the TargetVisu C:\Program Files\CODESYS\CODESYS Control RTE3>VisualClientController.exe --application=Application --flags=1 You can then place a .bat file on the desktop and put this inside: CD "C:\Program Files\CODESYS\CODESYS Control RTE3" VisualClientController.exe --application=Application --flags=1 exit Double clicking the .bat file will start the TargetVisu. You may need to replace the Application name by your own application name. Good to know: In the cmd above, if you replace --flags=1 by --flags=2, it will shutdown the TargetVisu.
Last updated: 2026-03-11

Post by timvh on Detect "Cancel" Press in FileOpenSave Dialog ^{CODESYS Forge talk (Post)}
Maybe there is a better way, but a long time ago I created a test application that worked like this: With a button I opened the dialog and I added a "Input configuration - OnDialogClosed" "Execute ST-Code" action to this same button which called the following Function when the dialog was closed: F_OnFileDialogClosed(pClientData); Below this Function which handled the result: // This function is called from the visualization when the dialog is closed. FUNCTION F_OnFileDialogClosed : BOOL VAR_INPUT pClientData : POINTER TO VisuElems.VisuStructClientData; END_VAR VAR dialogMan : VisuElems.IDialogManager; FileOpenCloseDialog : VisuElems.IVisualisationDialog; result : VisuElems.Visu_DialogResult; _sFileName : STRING(255); END_VAR // the DialogManager is provided via the implicitly available VisuManager dialogMan := VisuElems.g_VisuManager.GetDialogManager(); IF dialogMan <> 0 AND pClientData <> 0 THEN FileOpenCloseDialog := dialogMan.GetDialog('VisuDialogs.FileOpenSave'); // gets the FileOpenSave dialog IF FileOpenCloseDialog <> 0 THEN result := FileOpenCloseDialog.GetResult(); // gets the result (OK, Cancel) of the dialog IF result = VisuElems.Visu_DialogResult.OK THEN // Original code gvlFile.FileListProvider(); _sFileName := CONCAT(gvlFile.FileListProvider._stDirectory, gvlFile.FileListProvider.stFile); // do something with this file name... END_IF END_IF END_IF
Last updated: 2023-09-19

Post by cihangur on C0138: No matching 'FB_Init' method found for instantiation of VisuClientObjectMgr ^{CODESYS Forge talk (Post)}
This "FB_Init" error has become very annoying lately. It's usually related to webvisu and is resolved by deleting all objects and related libraries. Of course, you need to re-add the deleted objects. Lately, we've generally been managing by not upgrading, but this problem persists in every version since SP20 and should be resolved. I updated a project from SP 19 to SP 21 and found 116 similar errors. [ERROR] alarmmanager, 4.7.0.0 (intern): ReplaceAlarmPlaceholdersConverted: C0138: No matching 'FB_Init' method found for instantiation of CharBufferString [ERROR] visuelemsalarm, 4.7.0.0 (system): protDrawRowHeader [VisuFbElemAlarmTable]: C0138: No matching 'FB_Init' method found for instantiation of CharBufferString [ERROR] alarmmanager, 4.7.0.0 (intern): AnalyzePlaceholders2 [Alarm]: C0138: No matching 'FB_Init' method found for instantiation of CharBufferString If you have an ERROR related VisuClientObjectMgr you can try to disable "Visualization Manager - Settings - Support client animations and overlay of native elements " selection "C0138: No matching 'FB_Init' method found for instantiation of VisuClientObjectMgr" etc
Last updated: 2025-10-10

communication ^{CODESYS Forge talk (Thread)}
communication
Last updated: 2023-08-19

NETVAR_UDP ^{CODESYS Forge talk (Thread)}
NETVAR_UDP
Last updated: 2023-08-29

Post by eschwellinger on CODESYS Automation Server Connector for 3.5 SP11 ^{CODESYS Forge talk (Post)}
https://store.codesys.com/en/codesys-automation-server-connector.html Programming System CODESYS Development System V3.5.15.0 or higher
Last updated: 2023-08-30

VPN ^{CODESYS Forge talk (Thread)}
VPN
Last updated: 2023-09-06

VPN ^{CODESYS Forge talk (Thread)}
VPN
Last updated: 2023-09-06

VPN ^{CODESYS Forge talk (Thread)}
VPN
Last updated: 2023-09-06

ernesto881124 ^{CODESYS Forge talk (Thread)}
ernesto881124
Last updated: 2023-09-14

Benutzeranmeldung ^{CODESYS Forge talk (Thread)}
Benutzeranmeldung
Last updated: 2009-01-19

Trend ^{CODESYS Forge talk (Thread)}
Trend
Last updated: 2021-11-26

Warten ^{CODESYS Forge talk (Thread)}
Warten
Last updated: 2009-09-17

(no subject) ^{CODESYS Forge talk (Thread)}
Last updated: 2007-09-28

IJSONData.FindAllElementsByKey ^{CODESYS Forge talk (Thread)}
IJSONData.FindAllElementsByKey
Last updated: 2021-12-09

SysDir ^{CODESYS Forge talk (Thread)}
SysDir
Last updated: 2022-02-15

MaxNodesPerRead ^{CODESYS Forge talk (Thread)}
MaxNodesPerRead
Last updated: 2018-03-16

Sprachumschaltung ^{CODESYS Forge talk (Thread)}
Sprachumschaltung
Last updated: 2009-06-10

Reglersimulation ^{CODESYS Forge talk (Thread)}
Reglersimulation
Last updated: 2018-01-16

CODESYSControl.cfg ^{CODESYS Forge talk (Thread)}
CODESYSControl.cfg
Last updated: 2015-06-02

how to run the machine using CNC editor in codesys ^{CODESYS Forge talk (Thread)}
how to run the machine using CNC editor in codesys
Last updated: 2007-10-24

ESP8266 ^{CODESYS Forge talk (Thread)}
ESP8266
Last updated: 2016-10-29

Sort by relevance or date