wiki Discussion ^{charly29160 wiki (Discussion)}
Forum for wiki comments
Last updated: 2026-06-15

blog Discussion ^{charly29160 blog (Discussion)}
Forum for blog comments
Last updated: 2026-06-15

Home ^{charly29160 wiki (WikiPage)}
Project Members: charly29160 (admin)
Last updated: 2026-06-15

(no subject) ^{charly29160 wiki (Thread)}
Last updated: 2026-06-15

Post by charly29160 on WebVisu scaling regression in V3.5.22 P2: frame size jumps when switching visualizations ^{CODESYS Forge talk (Post)}
Environment: - CODESYS V3.5.22 Patch 2 - CODESYS Control for Raspberry Pi MC SL - WebVisu in browser Problem: When switching between visualizations using a Register element (Registerkarten), the displayed frame size jumps incorrectly after returning to a previously viewed visualization. This behavior was introduced in V3.5.22 Patch 2. The same project worked correctly in V3.5.21 Patch 4. WebVisu settings in V3.5.21 (working): - Scaling: Isotropisch - Automatisch ermittelte Clientgröße verwenden: active - All visualizations: Automatisch erkannte Visualisierungsgröße Workaround?
Last updated: 2026-06-15

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

Visualisierungswerkzeuge ^{CODESYS Forge talk (Thread)}
Visualisierungswerkzeuge
Last updated: 2026-06-15

wiki Discussion ^{meke001 wiki (Discussion)}
Forum for wiki comments
Last updated: 2026-06-15

blog Discussion ^{meke001 blog (Discussion)}
Forum for blog comments
Last updated: 2026-06-15

(no subject) ^{meke001 wiki (Thread)}
Last updated: 2026-06-15

Home ^{meke001 wiki (WikiPage)}
Project Members: meke001 (admin)
Last updated: 2026-06-15

Post by baotthitawat on Using SCADA Data and C# Integration for Real-Time Production KPI Monitoring ^{CODESYS Forge talk (Post)}
In modern manufacturing, machines and sensors generate a large amount of data every day. PLC systems collect signals from the production line. SCADA systems display machine status, alarms, process values, runtime, downtime, and operating conditions in real time. But for many factories, the challenge is not only collecting data. The bigger challenge is turning that data into useful production insight. This is where ATSCADA iLean can support real-time production KPI monitoring. Why SCADA Data Matters for KPI Monitoring Traditional SCADA systems are mainly used to monitor equipment status, process values, alarms, and control screens. However, production teams often need more than basic monitoring. They need to understand: How efficiently machines are running How much downtime is happening Which process creates bottlenecks Whether production performance is meeting the target How machine data can support continuous improvement ATSCADA iLean helps transform SCADA data into real-time production KPIs such as OEE, Availability, Performance, Quality, machine runtime, machine downtime, utilization rate, and production efficiency. This allows factories to move from simple monitoring to performance-based production management. The Role of PLC and SCADA Communication A real-time KPI system depends heavily on reliable data communication. If PLC data is not collected correctly, KPI calculation will not be accurate. Machine runtime, downtime, production count, alarm status, and process values must be transferred clearly from the field layer to the SCADA system. For developers and automation engineers, this is where system integration becomes important. In many industrial projects, C# can be used to build custom SCADA logic, connect PLC data, process values, and extend monitoring functions based on project requirements. For more details about this topic, this article about PLC communication with SCADA using C# is a useful reference for understanding industrial data communication and SCADA integration. From Data Collection to Real-Time Dashboards A typical production KPI monitoring flow can look like this: Machines and sensors generate field data. PLCs collect signals such as running status, stop status, count values, and process data. SCADA receives and monitors the data in real time. ATSCADA iLean calculates production KPIs. Dashboards show OEE, downtime, utilization, and performance. Operators and managers use the data to improve production decisions. This structure helps reduce dependency on manual Excel reports or delayed shift summaries. Instead of waiting until the end of the day to review production performance, factories can monitor KPI values while production is still running. How ATSCADA iLean Supports Smart Manufacturing ATSCADA iLean is not only a visualization tool. It helps factories use SCADA data for production analysis, KPI tracking, downtime review, and operational improvement. With real-time KPI monitoring, manufacturing teams can identify bottlenecks faster, reduce unnecessary downtime, improve equipment efficiency, and understand production performance more clearly. This is important for Industry 4.0 because factory data should not only be stored or displayed. It should be used to support better decisions. Environmental Data Can Also Be Part of the System In some factories, production quality is also affected by environmental conditions such as temperature and humidity. This is common in electronics manufacturing, food production, pharmaceutical environments, precision manufacturing, and storage areas. For example, if quality issues appear during a certain time period, the cause may not only come from machine performance. It may also be related to unstable temperature, humidity, or production area conditions. That is why a temperature and humidity monitoring system based on SCADA can be useful when factories want to manage environmental data together with production KPI data. When production data and environmental data are viewed in the same monitoring system, engineers can analyze problems from a wider and more accurate perspective. Final Thoughts SCADA is no longer only a local monitoring screen. With tools like ATSCADA iLean, SCADA data can become the foundation for real-time KPI dashboards, production performance analysis, downtime tracking, reporting, and smart manufacturing improvement. For developers and automation engineers, this also creates more opportunities to build flexible industrial applications using PLC data, SCADA systems, C# integration, and real-time dashboards. The main goal is simple: Use industrial data not only to see what is happening, but to understand how efficiently production is running.
Last updated: 2026-06-16

Post by hezhikui on Codesys 3.5.21 fails to copy file to USB ^{CODESYS Forge talk (Post)}
Hi,Canplum,did you solved this problem?
Last updated: 2026-06-16

Automation Server 🇬🇧 ^{CODESYS Forge talk (Discussion)}
The Industry 4.0 administration platform for users and operators of CODESYS compatible controllers
Last updated: 2026-06-16

Using SCADA Data and C# Integration for Real-Time Production KPI Monitoring ^{CODESYS Forge talk (Thread)}
Using SCADA Data and C# Integration for Real-Time Production KPI Monitoring
Last updated: 2026-06-16

Codesys 3.5.21 fails to copy file to USB ^{CODESYS Forge talk (Thread)}
Codesys 3.5.21 fails to copy file to USB
Last updated: 2026-06-16

Post by hezhikui on Codesys 3.5.21 fails to copy file to USB ^{CODESYS Forge talk (Post)}
Hi,Canplum,did you solved this problem?
Last updated: 2026-06-16

XY Chart causes extremely long cycle in Visu Task ^{CODESYS Forge talk (Thread)}
XY Chart causes extremely long cycle in Visu Task
Last updated: 2026-06-16

Post by manuknecht on XY Chart causes extremely long cycle in Visu Task ^{CODESYS Forge talk (Post)}
I am using the visualization element "Cartesian XY Chart" in a visualization template within a library to display recorded position values. I managed to configure the chart as desired and it displays the values like it should. A problem occurs when clicking on the chart to move the cursor, zoom or pan. Upon clicking the visualization element for the first time, the task in which the visualization is run spikes to a cycle time of around 5'000 to 15'000 ms (the configured cycle time is 100 ms). Sometimes this even completely crashes the web-visualization. After this very long cycle, the visu task normalizes again and the chart can be interacted with as usual. Another spike in cycle time occurs once the visualization is switched to a frame that does not contain the chart. I did reduce the data array to only a few values and tried changing the update behaviour of the chart, but it did not change the problems I am facing. Did anyone experience a similar issue or even has a solution for this?
Last updated: 2026-06-16

wiki Discussion ^{anthony-p wiki (Discussion)}
Forum for wiki comments
Last updated: 2026-06-16

blog Discussion ^{anthony-p blog (Discussion)}
Forum for blog comments
Last updated: 2026-06-16

(no subject) ^{anthony-p wiki (Thread)}
Last updated: 2026-06-16

TCP communication and TCP Streams ^{CODESYS Forge talk (Thread)}
TCP communication and TCP Streams
Last updated: 2026-06-16

Home (version 1) discussion ^{anthony-p wiki (Thread)}
Home (version 1) discussion
Last updated: 2026-06-16

wiki Discussion ^{krgerecke7 wiki (Discussion)}
Forum for wiki comments
Last updated: 2026-06-16

Sort by relevance or date