Post by elektron785 on GPIO mit Codesys Virtual Control for Linux ARM64 SL ^{CODESYS Forge talk (Post)}
Hallo zusammen, ich möchte an einem Entwicklungsboard auf dem der i.MX 8M Plus von NXP aufgesteckt ist die vier zur Verfügung gestellten GPIOs als Ausgänge verwenden. Ich habe mir dazu die Readme-Datei des GPIO-Beispiels von "C:\Program Files\CODESYS 3.5.20.40\CODESYS\CODESYS Control SL Extension Package\4.14.0.0\Examples\GPIO" angeschaut Die Übersicht der verfügbaren GPIOs sieht folgendermaßen aus - wobei ich das auf die reduziert habe, die für mich von Interesse sind: gpiochip0: GPIOs 0-31, parent: platform/30200000.gpio, 30200000.gpio: gpio-0 (SODIMM206 ) gpio-1 (SODIMM208 ) gpio-2 ( ) gpio-3 ( ) gpio-4 ( |sd-vsel ) out hi gpio-5 (SODIMM210 ) gpio-6 (SODIMM212 ) gpio-7 (SODIMM216 ) gpio-8 (SODIMM218 ) gpio-9 ( ) gpio-10 ( ) gpio-11 (SODIMM16 ) gpio-12 (SODIMM155 |regulator-usb1-vbus ) out lo gpio-13 (SODIMM157 ) gpio-14 (SODIMM185 |regulator-usb2-vbus ) out hi gpio-15 (SODIMM91 )** Füge ich nun das GPIO (1 Bit)-Gerät in meinem Codesys-Programm hinzu funktioniert der Bus solange bis ich die Richtung in den GPIO-Parametern von "not used" auf "Output" stelle (siehe Bild gpio_parameter). Dann funktioniert nach Download der Bus nicht mehr. Gibt es noch eine andere Möglichkeit das zu steuern oder muss ich noch Einstellungen tätigen? Für die Zeile mit dem echo (export/unexport) aus dem Beispiel fehlen mir trotz sudo die Zugriffsrechte. "The Kernel Linux has deprecated GPIO user space SysFS. However, the kernel config CONFIGGPIOSYSFS is still enabled on Toradex's BSP to support customers using it in their legacy applications. You can check the configuration by running zcat /proc/config.gz | grep CONFIGGPIOSYSFS. For GPIO access from userspace, the new char device API, also known as libgpiod, must be used." Dies steht in der Verwendung der GPIOs - eine Ausführung des zcat-Kommandos liefert ein =y zurück.
Last updated: 2025-03-17

GPIO mit Codesys Virtual Control for Linux ARM64 SL ^{CODESYS Forge talk (Thread)}
GPIO mit Codesys Virtual Control for Linux ARM64 SL
Last updated: 2025-03-17

Post by pistola on Pause Tab Order ^{CODESYS Forge talk (Post)}
I'm programming an HMI, and on a settings page I have external buttons allow the operator to tab between various elements to select which one they want to adjust. I then use "Input Configuration" > "OnMouseClick" to select which variable to adjust. The problem is, when adjusting the variable the pointer will move to the other elements within the tab order. Is there a way to pause or prevent the pointer to move to the other elements when a variable is TRUE?
Last updated: 2025-03-17

co🔗e: A Linked List Solution has been released ^{CODESYS Forge talk (Thread)}
co🔗e: A Linked List Solution has been released
Last updated: 2025-03-17

IFM EXOR Network variable Error ^{CODESYS Forge talk (Thread)}
IFM EXOR Network variable Error
Last updated: 2025-03-17

Pause Tab Order ^{CODESYS Forge talk (Thread)}
Pause Tab Order
Last updated: 2025-03-17

Post by respl on IFM EXOR Network variable Error ^{CODESYS Forge talk (Post)}
We are connected IFM CR711S to Exor EX710. We are exchanging data using network variables. Both devices are configured on same project so no need to use file source. When tested application it works fine. But after 3 months same application not working. We are able to send data from CR711 to EX710 but data from Ex710 to CR711s works only for one scan when we cold reset CR 711S. Can somebody help to find out error.
Last updated: 2025-03-17

Post by atzcck on Issue with TargetVisu on Codesys Control Win ^{CODESYS Forge talk (Post)}
I'm having same issue. Is there any proggress to overcome this?
Last updated: 2025-03-18

Issue with TargetVisu on Codesys Control Win ^{CODESYS Forge talk (Thread)}
Issue with TargetVisu on Codesys Control Win
Last updated: 2025-03-18

Post by twofacexx on codesyscontrol.log exzessive Größe ^{CODESYS Forge talk (Post)}
Moin, kann es sein, dass dies auch schon wieder veraltet ist? Ich habe aktuell die 3.5 SP20 Patch 4 mit einem Paspberry 5 64bit SL am laufen und es wird leider nix geloggt. Muss man da etwas am Filter einstellen damit etwas geloggt wird? WÄre echt cool, wenn Codesys anfangen würde, Info´s in Form von Text einzupflegen....dann könnte man es auch nutzen. Brauche das Log bzgl. eines anderen Problems mit der "SysProcess.SysProcessExecuteCommand2", leider auch nicht gut kommentiert.
Last updated: 2025-03-18

Post by fmon on Modbus TCP client reconnection problem ^{CODESYS Forge talk (Post)}
Problem solved The client modbus cycle time was linked to a task at 500ms. Whereas the channel modbus was at 200ms. Certainly problem of packages synchronisation. I let the client modbus cycle time to be handled by itself (See attachement) --> "Use the bus cyle time parameters" (traduce from french) See attachement
Last updated: 2025-03-18

Post by gesc on Unable to compare projects containing alarm manager 4.5.0.0 ^{CODESYS Forge talk (Post)}
Last updated: 2025-03-18

Unable to compare projects containing alarm manager 4.5.0.0 ^{CODESYS Forge talk (Thread)}
Unable to compare projects containing alarm manager 4.5.0.0
Last updated: 2025-03-18

Modbus TCP client reconnection problem ^{CODESYS Forge talk (Thread)}
Modbus TCP client reconnection problem
Last updated: 2025-03-18

Post by gesc on Unable to compare projects containing alarm manager 4.5.0.0 ^{CODESYS Forge talk (Post)}
Hi, have the same problem. Tried various versions (3.5.17.0 3.5.18.5 3.5.19.0 3.5.20.1) When you compare two functions blocks inside one project, the compare function does work. Regards, Gerco
Last updated: 2025-03-18

Post by fmon on Modbus : dis- / re-connect cable: modbus does not re-start ^{CODESYS Forge talk (Post)}
Problem solved The client modbus cycle time was linked to a task at 500ms. Whereas the channel modbus was at 200ms. Certainly problem of packages synchronisation. I let the client modbus cycle time to be handled by itself (See attachement) --> "Use the bus cyle time parameters" (traduce from french) See attachement
Last updated: 2025-03-18

Modbus : dis- / re-connect cable: modbus does not re-start ^{CODESYS Forge talk (Thread)}
Modbus : dis- / re-connect cable: modbus does not re-start
Last updated: 2025-03-18

Post by atone on Change IO-Link Device Interface connected to a Profinet-Slave at Runtime ^{CODESYS Forge talk (Post)}
I need to be able to update (change) the interface of an IO-Link device at runtime. The reason is the connected sensor can be selected at runtime, and some sensors we use have a 2 byte IN interface, others have a 4 byte IN interface, others 16 byte IN, others 16 byte IN/OUT (see attached screenshot). Is it possible at all? When yes, which function should I use? Thank you!
Last updated: 2025-03-18

Post by peterkcontrols on Codesys Network driver install for Codesys Control RTE x64 ^{CODESYS Forge talk (Post)}
Sorry to clarify the issues say as per the attached image. I copied and pasted the unresolved issues from someone else who had a similar problem.
Last updated: 2025-03-18

Post by eschwellinger on codesyscontrol.log exzessive Größe ^{CODESYS Forge talk (Post)}
/var/opt/codesys/codesyscontrol.log auf dem PI.
Last updated: 2025-03-18

Post by peterkcontrols on Codesys Network driver install for Codesys Control RTE x64 ^{CODESYS Forge talk (Post)}
Hello I am trying to download my project onto my Codesys Control RTE x64 soft PLC. and I have had an issue when downloading. [FATAL ERROR] Unresolved reference: 'SYSETHERNETADAPTEROPEN' [FATAL ERROR] Unresolved reference: 'SYSETHERNETADAPTERCLOSE' [FATAL ERROR] Unresolved reference: 'GETNUMBEROFADAPTERS' [FATAL ERROR] Unresolved reference: 'GETADAPTERINFO' [FATAL ERROR] Unresolved reference: 'SYSETHERNETIPFRAMERECEIVE' [FATAL ERROR] Unresolved reference: 'SYSETHERNETETHFRAMESEND' [FATAL ERROR] Unresolved reference: 'SYSETHERNETETHFRAMERECEIVE' [FATAL ERROR] Unresolved reference: 'SYSETHERNETIPFRAMESEND' [FATAL ERROR] Unresolved reference: 'SYSETHERNETFRAMERELEASE' Looking on the forum I have found other people had to install the network driver, which I have done following this youtube video by codesysGroup: https://youtu.be/10oj4wABaKc?si=664l83JXUGQSDlAe I have added the network driver, please see attached image. I have checked my BIOS to make sure my secure boot status is disabled, see attached image. when I go to component manager, the drop down menu doesnt have the new network adapter, see attached image. I have not yet purchased or installed any licenses is that what I am missing? What other reason is there that I can't download to the runtime. Thanks
Last updated: 2025-03-18

Post by peterkcontrols on Codesys Network driver install for Codesys Control RTE x64 ^{CODESYS Forge talk (Post)}
Sorry to clarify the issues say as per the attached image. I copied and pasted the unresolved issues from someone else who had a similar problem.
Last updated: 2025-03-18

Post by peterkcontrols on Codesys Network driver install for Codesys Control RTE x64 ^{CODESYS Forge talk (Post)}
I am using Codesys Control RTE V3 Version 3.5.21.0 I am not sure what you are asking. Which hardware ID has the network interface card? I have ran ipconfig /all and attached an image. Let me know what other information I can provide to you to help troubleshoot this problem. Thank
Last updated: 2025-03-18

Post by eschwellinger on Codesys Network driver install for Codesys Control RTE x64 ^{CODESYS Forge talk (Post)}
is this latest Control RTE Version? Strange is that the component does not occure in the list of component to add.
Last updated: 2025-03-18

Post by eschwellinger on Codesys Network driver install for Codesys Control RTE x64 ^{CODESYS Forge talk (Post)}
which Hw id has your nic in the windows device manager?
Last updated: 2025-03-18

Sort by relevance or date