Codesys Raspberry Runtime 4.10.0.0 and RSM Utility 3.5.19.0 ^{CODESYS Forge talk (Thread)}
Codesys Raspberry Runtime 4.10.0.0 and RSM Utility 3.5.19.0
Last updated: 2023-11-21

Post by vincentd on Datasource OPC UA Client error ID:7012 ^{CODESYS Forge talk (Post)}
I had some help from Codesys to debug this problem. It seems there was a problem within the target (a bug?). I only used for a proof of concept. Possibly it will work with a new version of the target
Last updated: 2023-11-21

Post by baldeep on Codesys Raspberry Runtime 4.10.0.0 and RSM Utility 3.5.19.0 ^{CODESYS Forge talk (Post)}
I had been using Codesys Raspberry 4.9.0.0 Runtime for a Project with CAA File 3.5.19.0. But now with Update 4.10.0.0 and Raspberry pi 64 Bit.....i cannot compile my code as RSM Utility 3.5.19.0 is not recognised. Any help? Regards
Last updated: 2023-11-20

Raspberry Pi GPIO mapping ^{CODESYS Forge talk (Thread)}
Raspberry Pi GPIO mapping
Last updated: 2023-11-21

Post by bahrt on Raspberry Pi GPIO mapping ^{CODESYS Forge talk (Post)}
Hi I am about to configure ALL GPIOs on a Raspberry Pi 3 model B V1.2. It seems that I have limited understanding of why not all the IO’s become available with the corresponding mapped IO’s – the 'dwInUse' contains mapping of the inputs from GPIO0 to GPIO27. But 'dwInputs' are only showing GPIO0 to GPIO8 and GPIO15 as available inputs. These mentioned inputs work fine You will be able to watch the limited mapped IO activity here: https://drive.google.com/file/d/1zz4PBNBfRZBF2YkiJ2VQxw6L9MBVji7R/view?usp=sharing Can you please bring your best idea on why GPIO09 to GPIO14 and GPIO16 to GPIO27 state are not active (at a fixed zero state) in the dwInputs register? Thanks in advance. Best regards Andreas Bahrt
Last updated: 2023-11-21

Post by drno on AlarmMgr Database Error in method WriteToStorage: Error code = 30531, Action = 1030 ^{CODESYS Forge talk (Post)}
Hallo zusammen, auf einer Industriesteuerung (Target-Version 3.5.5.0) läuft unter anderem eine Alarmverwaltung mit Alarmspeicherung. Offensichtlich kann kein Schreibzugriff auf das .sqlite File durchgeführt werden, daher ist die Alarmhistorie nicht mehr verfügbar. Versuche mit unterschiedlichen Unterverzeichnissen führten nicht zum Erfolg. Die Datei "application.alarmstorage.sqlite" wird zwar angelegt, aber es erfolgen keine Einträge. Hat jemand eine Idee dazu? Die Steuerung ist ca. 8 Jahre in Betrieb, die Alarmhistorie hat früher mal funktioniert. Danke, LG
Last updated: 2023-11-21

Post by felipemsgarcia on Edge Gateway online, but PLC is not online ^{CODESYS Forge talk (Post)}
Hello, Up until yesterday (2023/11/20) I was able to connect to the PLC remotely with no issues through Edge Gateway. However, today I can see the Edge Gateway online but I can find the PLC even if I do a network scan. Following the same path as janber0206 @ https://forge.codesys.com/forge/talk/automation_server/thread/e78b11d7e9/, I looked into certificates and found that one of the Trusted publisher certificates has expired earlier today (2023/11/21). Please see image. Questions are: Does it affect the connection to the PLC through Edge Gateway? How do I fix it? Thank you very much in advance!
Last updated: 2023-11-21

Post by eschwellinger on Codesys Raspberry Runtime 4.10.0.0 and RSM Utility 3.5.19.0 ^{CODESYS Forge talk (Post)}
use 'download missing libraries' in the lib manager
Last updated: 2023-11-21

AlarmMgr Database Error in method WriteToStorage: Error code = 30531, Action = 1030 ^{CODESYS Forge talk (Thread)}
AlarmMgr Database Error in method WriteToStorage: Error code = 30531, Action = 1030
Last updated: 2023-11-21

Post by fred on Rasperry Control Debian 12 ^{CODESYS Forge talk (Post)}
Hi, I have Proxmox running on a Rasperry 4 and have debian 12 ARM installed here. I wanted to install Codesys Control for Raspberry on it. According to the messages, the runtime environment and the gateway were installed successfully, but I can't find a device to downplay a program. The sudo service codesys start command fails. (see image) Does somebody has any idea? Thank you for your help! Greetings Fred
Last updated: 2023-11-22

Post by pflot59 on Migration von "CODESYS Control for PFC200 SL" zu WAGO FW26 "CODESYS V3.5.19.2" ^{CODESYS Forge talk (Post)}
You can find a guide here : https://techdocs.wago.com/Software/eCOCKPIT_Migration/en-US/index.html
Last updated: 2023-11-21

Codesys 3.5.19 Control Win x64 - network adapter for EtherCAT master not working ^{CODESYS Forge talk (Thread)}
Codesys 3.5.19 Control Win x64 - network adapter for EtherCAT master not working
Last updated: 2023-11-22

Post by tomgr on Codesys 3.5.19 Control Win x64 - network adapter for EtherCAT master not working ^{CODESYS Forge talk (Post)}
Hi guys I am trying to run on my laptop Codesys 3.5.19 Control Win x64 where I created a EtherCAT master. I have defined the controler, specified network adapter (my docking station) and everything worked as expected. Later I needed to test it on site (without docking station) so I changed the network adapter by EC master to my laptop network card. After that it shows "Network adapter opened" but no device can be found by scanning and in LOG is saying "SysEthernet: packet could not be sent, error code: -1". Same error with USB network card, but if I switch back to docking station, all is working again... Any idea what I'm doing wrong?
Last updated: 2023-11-22

Post by pflot59 on Migration von "CODESYS Control for PFC200 SL" zu WAGO FW26 "CODESYS V3.5.19.2" ^{CODESYS Forge talk (Post)}
You can find a guide here : https://techdocs.wago.com/Software/eCOCKPIT_Migration/en-US/index.html
Last updated: 2023-11-21

Post by ewi04 on Git with visu ^{CODESYS Forge talk (Post)}
Hi, I have several problems with the git extension. Situation: I am working with Codesys v3.5 SP19 Patch 1 and Git V1.2.1.0. The remote repository is GitLab Community Edition v16.1.2. I am working on a project with one other person. Problems: 1: After each start of Codesys all of the visu pages are marked as modified. So we have to discard all changes first. Otherwise the history is not clean and the merge request becomes more complex. I tested it with a new project and only local. I made the observation, that a page is not marked as modified when it is committed a second time (after a restart of codesys). But this is necessary after every change of a page. However, since we are working in a team, it seems we are playing ping-pong and so all pages are marked as modified on each startup. 2: Each image pool causes a parent child conflict. Also in my local project. The only solution that I have found, is to ignore the issue. Does anyone have the same problems? I think it looks more like bugs. Thanks ewi04
Last updated: 2023-11-22

Post by ct-f on SP19 Runtime Zugriff auf lokales Dateisystem ^{CODESYS Forge talk (Post)}
Hallo, bin auf das gleiche Problem gestoßen und würde mich sehr über einen Lösungsansatz freuen. Habe ein umfangreiches Projekt, wo mehrere Datenein gelesen und geschrieben werden. Nach Umzug auf SP 19 funktioniert leider nichts mehr. Es gibt keine Fehlermeldungen, die Ursache ist nicht erkennbar. VG Falk
Last updated: 2023-11-22

Post by ewi04 on Git - User identification data is lost when codesys is closed ^{CODESYS Forge talk (Post)}
Hallo, it's not a big problem, but it is a bit annoying. The git user identification data is lost when codesys is closed. So I have to enter the information again and again. Is there a way to save the data? Environment: Codesys V3.5 SP19 Patch 4 (64Bit), Git 1.3.0.0 Thanks
Last updated: 2023-11-22

Post by simotion on Axis_Ref_SM3.perfTimers ^{CODESYS Forge talk (Post)}
What is the exact meaning of the variables that measure the softmotion performance : Axis_Ref_SM3.perfTimers.udiAI_ns Axis_Ref_SM3.perfTimers.udiAO_ns Axis_Ref_SM3.perfTimers.udiBI_ns Axis_Ref_SM3.perfTimers.udiBO_ns
Last updated: 2023-11-22

SP19 Runtime Zugriff auf lokales Dateisystem ^{CODESYS Forge talk (Thread)}
SP19 Runtime Zugriff auf lokales Dateisystem
Last updated: 2023-11-22

Post by captaincookie on SP19 Runtime Zugriff auf lokales Dateisystem ^{CODESYS Forge talk (Post)}
Hallo, das konkrete Problem konnte ich seither leider nicht lösen, allerdings habe ich mit SP19 Patch 4 einen Workaround gefunden, der zumindest für meine Anwendung funktioniert: Zunächst besteht das Problem nicht für alle Funktionalitäten gleichermaßen. Die Anzeige einer .bmp oder .tiff-Datei im Visu-Elementtyp Bild beispielsweise funktioniert aus dem lokalen Dateisystem. Die Anzeige von .cnc-Dateien in einer Tabelle dagegen nicht. Allerdings funktioniert das wiederum, wenn der Dateipfad in den Ordner der PLC führt, genannt '_cnc'. In der PLC wird dieser Ordner über den Pfad _cnc/ erreicht. Auch lohnt es sich einen Blick in die PLC Config-Datei zu werfen und ggf. Anpassungen vorzunehmen. Einzelne Einträge definieren Zugriffsrechte und ähnliches. Die beschriebene Lösung ist nicht sonderlich schön und es erklärt das Problem nicht. Vielleicht kann das noch jemand anders beantworten.
Last updated: 2023-11-22

Post by eschwellinger on SP19 Runtime Zugriff auf lokales Dateisystem ^{CODESYS Forge talk (Post)}
seit SP19 nur noch im PLcLogic pfad. c:\ProgramData\CODESYS...usw datein schreiben lesen [SysFile] PlaceholderFilePath.1=/tmp, $TMP$ PlaceholderFilePath.2=/media/usb, $USB$ PlaceholderFilePath.2.Volatile=1 Seit der Behebung kann der IEC-Code aus Security-Gründen nur noch auf das Arbeitsverzeichnis PLCLogic zugreifen. Sollte auf Dateien außerhalb dieses Pfades zugegriffen werden müssen, dann können diese per Platzhalter bekannt gemacht werden und sind dann zugreifbar. Darüber hinaus kann weiterhin ForceIecFilePath=0 gesetzt werden, um das bisherige Verhalten wiederherzustellen. Von letzterem raten wir aber dringend ab, da dann der IEC-Code wieder auf das gesamte Filesystem zugreifen kann. Daher sollte beides nur nach einer eingehenden Securitybewertung erfolgen.
Last updated: 2023-11-23

Post by annd on Migration von "CODESYS Control for PFC200 SL" zu WAGO FW26 "CODESYS V3.5.19.2" ^{CODESYS Forge talk (Post)}
@pflot59: Thanks, I know this guide but there a slight differences in migrating from eCockpit or from Codesys SL. It is still fine as I wrote above. BR annD
Last updated: 2023-11-23

Post by ulvis on How to do horizontal scroll in CFC editor? ^{CODESYS Forge talk (Post)}
No. UX & GUI is not a Codesys GmbH priority, it seems :-(
Last updated: 2023-11-23

Post by tk096 on Axis_Ref_SM3.perfTimers ^{CODESYS Forge talk (Post)}
Hi, these variables are internal members of the axis. They measure the duration of some internal function calls.
Last updated: 2023-11-23

Migration von "CODESYS Control for PFC200 SL" zu WAGO FW26 "CODESYS V3.5.19.2" ^{CODESYS Forge talk (Thread)}
Migration von "CODESYS Control for PFC200 SL" zu WAGO FW26 "CODESYS V3.5.19.2"
Last updated: 2023-11-23

Sort by relevance or date