Socket communication with username and password ^{CODESYS Forge talk (Thread)}
Socket communication with username and password
Last updated: 2024-02-24

Post by camilloo on Control for Linux SL on Ubuntu Core ^{CODESYS Forge talk (Post)}
Hello, Has anyone tried running CODESYS Linux on Ubuntu Core? I'm having problems installing the runtime. The connection to UC cannot be established. I used the instruction: https://content.helpme-codesys.com/en/CODESYS%20Control/_rtsl_linux_public_key_authentification.html I can connect to UC using SSH (putty, shell). Codesys can't. Do any of you have an idea?
Last updated: 2024-02-24

Post by spiessli on Raspberry Pi 4 with Legacy Drivers and Codesys 3.5.19 Patch 4 ^{CODESYS Forge talk (Post)}
If I remember well, first you need to delete the current version. Then clicking through the tree as indicated in the previous post, lets you choose the "outdated" libraries.
Last updated: 2024-02-24

Post by timvh on Toolbox missing item ^{CODESYS Forge talk (Post)}
You have selected the new Ladder editor. This only has these items in the toolbox.
Last updated: 2024-02-24

Post by tobse on Raspberry Pi 4 with Legacy Drivers and Codesys 3.5.19 Patch 4 ^{CODESYS Forge talk (Post)}
I have the same problem. How can I get the library version 4.14. Is there a download link? I am working with Codesys for the first time in a long time.
Last updated: 2024-02-24

Post by smeitink on Timeout Error in Modbus Communication with WAGO PFC200 and iEM2050 Meter using 750-652 Module ^{CODESYS Forge talk (Post)}
Hi all, I'm looking for help with an issue I've come across while trying to facilitate Modbus communication between a WAGO PFC200 PLC using a 750-652 communication module and an iEM2050 Series Single Phase Energy Meter. I believe to have everything wired and setup correcty, but I keep running into a "Error time out" message, and by now I don't really know what else to try. My setup is as follows: A PFC200 Wago PLC, which has 2 750-652 Serial Interfaces extension modules connected to its field bus. I'm using one of these to talk to a Schneider iEM2050 - kWh-meter over modbus. I have connected terminal 23 (A) of the iEM2050 to connector 6 (A) on the 750-652. I have connected terminal 24 (B) of the iEM2050 to connector 2 (B) of the 750-652. I'm using 200mm of twisted together wires to connected them both, and I have placed a 120 ohm resistor between A and B at both ends. I've attached relevant pinout images to this post. I then wrote a simple program that configures the Mobus port, as per the datasheet of the iEM2050. You can find an image of the relavent page attached to this post too. This is my program: PROGRAM PLC_PRG VAR Master: FbMbMasterSerial; xIsConnected: BOOL; xError: BOOL; iIndex: INT := 1; xTrigger: BOOL; utQuery : typMbQuery := ( bUnitId := 1, // The Modbus unit or slave address bFunctionCode := 4, // Function code for reading input registers uiReadAddress := 1829, // adress for the Power on off counter uiReadQuantity := 1 // Quantity of registers to read ); iStep: INT; oStatusModbus: WagoSysErrorBase.FbResult; utResponseModbus: typMbResponse; xConnect: BOOL := FALSE; delayTimer: TON; END_VAR Master( xConnect:= xConnect, I_Port:= _750_652_24_1, udiBaudrate:= 9600, usiDataBits:= 8, eParity:= WagoTypesCom.eTTYParity.Even, eStopBits:= WagoTypesCom.eTTYStopBits.One, eHandshake:= WagoTypesCom.eTTYHandshake.None, ePhysical:= WagoTypesCom.eTTYPhysicalLayer.RS485_HalfDuplex, xIsConnected=> xIsConnected, xError=> xError, oStatus=> oStatusModbus, eFrameType:= WagoAppPlcModbus.eMbFrameType.RTU, tTimeOut:= T#5S, utQuery:= utQuery, xTrigger:= xTrigger, utResponse:= utResponseModbus); delayTimer(IN := TRUE, PT := T#3S); // Use the Q output of the timer to set xConnect after the delay IF delayTimer.Q THEN xConnect := TRUE; END_IF CASE iStep OF 0: //Wacht totdat de master de poort geopend heeft IF xIsConnected THEN iStep := 1; END_IF 1: //Stuur request naar de slave xTrigger := TRUE; iStep := 2; 2: //Wacht totdat de master klaar is met het afhandelen van de request IF NOT xTrigger THEN iStep := 3; END_IF END_CASE The TON delay before opening the port is due to a an error I encountered when opening it straight away. This seems to be a bug, as described here. However, the TON solved that particular issue. I tried reading multiple registers, but like I said, I still always end up with the "Error time out". What else can I test or try at this point?
Last updated: 2024-02-24

Post by eschwellinger on Raspberry Pi 4 with Legacy Drivers and Codesys 3.5.19 Patch 4 ^{CODESYS Forge talk (Post)}
use attached projectarchive as workaround.. till this is fixed
Last updated: 2024-02-25

Post by eschwellinger on Codesys Control for Raspberry Pi 4.10.0.0 - Raspberry Pi OS > 2023-12-05 ^{CODESYS Forge talk (Post)}
now available in the CODESYS store..to Download. Deployment via CODESYS Installer will be added on Monday.
Last updated: 2024-02-25

Raspberry Pi 4 with Legacy Drivers and Codesys 3.5.19 Patch 4 ^{CODESYS Forge talk (Thread)}
Raspberry Pi 4 with Legacy Drivers and Codesys 3.5.19 Patch 4
Last updated: 2024-02-25

Post by aliazzz on Compile error ^{CODESYS Forge talk (Post)}
Try setting up your project environment. You can do this under Project -> Project Environment -> Press Button "Set all to newest". You have set your compiler, devices, etc in this project to the newest available versions.
Last updated: 2024-02-25

Post by cehermanstad on CODESYS V3.5 SP15 Patch 2 won't open ^{CODESYS Forge talk (Post)}
Hey, you probably already solved this, But I am posting to anyone coming over this thread with the same issue. Just hold your mouse cursor til black screen pops up. Right click and Left Click Maximize. There Something wrong with how the window minimizes in Codesys. Only happens once in a while. God luck to anyone with the same problem.
Last updated: 2024-02-25

Post by cehermanstad on CODESYS V3.5 SP15 Patch 2 won't open ^{CODESYS Forge talk (Post)}
Last updated: 2024-02-25

Post by reinier-geers on Compile error ^{CODESYS Forge talk (Post)}
i miss the font
Last updated: 2024-02-26

Post by reinier-geers on missing font ^{CODESYS Forge talk (Post)}
Hi I mis the font. Wenn i click i get an error
Last updated: 2024-02-26

Compile error ^{CODESYS Forge talk (Thread)}
Compile error
Last updated: 2024-02-26

Post by reinier-geers on Compile error ^{CODESYS Forge talk (Post)}
I know, But controller is Version 18.4. So i cant set to 19. I can try version 19. But will it run if i set the controller to 18.4
Last updated: 2024-02-26

Post by reinier-geers on Missing Font ^{CODESYS Forge talk (Post)}
Im trobles with version 18. Alraedy made a topic. But now i made it new. Some howe i miss the font
Last updated: 2024-02-26

missing font ^{CODESYS Forge talk (Thread)}
missing font
Last updated: 2024-02-26

Post by bruno-roth on Fehlender Menu-Eintrag RaspberryPI ^{CODESYS Forge talk (Post)}
Hallo, ich habe CODESYS 3.5 SP19P6 installiert und auch das Plugin für Raspberry PI aber im Tools menu taucht das Update Rapsberry pi nicht auf . Das Plugin wird irgendwie nicht richtig installiert ? auch das Edge -Gateway update Menu ist nicht vorhanden. Ich habe alles mit Admin installiert. was geht hier schief?
Last updated: 2024-02-26

Init Array input on a method ^{CODESYS Forge talk (Thread)}
Init Array input on a method
Last updated: 2024-02-26

Post by alexgooi on Init Array input on a method ^{CODESYS Forge talk (Post)}
Dear Forum, I would like to initialize an array input on a method. When I do this, I get the following error: "The type of ARRAY [1..2] OF BOOL cannot have a default value in this context." I attached a picture for more clarity. Is this simply not possible or is there a different way of tackling this problem? Thank you in advance
Last updated: 2024-02-26

Fehlender Menu-Eintrag RaspberryPI ^{CODESYS Forge talk (Thread)}
Fehlender Menu-Eintrag RaspberryPI
Last updated: 2024-02-26

Post by aved on Digital Clock ^{CODESYS Forge talk (Post)}
i need help creating a digital clock in CODESYS that should be displyed on a Raspberry Pi LCD Display trough the Visualization built in CODESYS. I have an idea how to display the time by making a 7 Segment Dysplay in the Visu. But I don't know how to get the actual time into the program. Can anyone help?
Last updated: 2024-02-26

ac_persistence not working when creating a Boot Application but works with a Direct Download to the PLC ^{CODESYS Forge talk (Thread)}
ac_persistence not working when creating a Boot Application but works with a Direct Download to the PLC
Last updated: 2024-02-27

Post by westcountryewe on ac_persistence not working when creating a Boot Application but works with a Direct Download to the PLC ^{CODESYS Forge talk (Post)}
I am using V3.5 SP18 Patch 5. I have noticed that when I Create a Boot Application from CODESYS, and upload this to my PLC via a USB stick the AC_Persistence does not work and none of my values that are in my PersistenceChannel are retained. However, if I connect direct to my PLC and I perform a direct download of my CODESYS program, my values that are in my PersistenceChannel are retained and work as they should. This makes me wonder if there are files that are missing when a Boot Application is created. I have tried taking a backup of my configuration files after performing a direct download, which gives me the plclog.zip folder, and appears to have the ac_persistence folder present within the file structure, however when I replace the plclogic.zip with the same folder that was created when I created a Boot Application, it still does not work but I wonder whether this is because the ac_persistence folder isn't stored in the correct location for reading. The .app and .crc files are embedded within the plclogic.zip folder, which obviously when uploading need to be standalone files in the root directory of the USB, so the intention there is clearly to extract the .app and .crc files and put them into the correct location within the USB. I wonder if it could be the same for the ac_persistence folder? I have tried moving it to different locations but none have worked. Has anybody else discovered a fix for this? I know the short-term solution is to do a direct download to the PLC but there are some logistical reasons why this isn't neccesarily the best solution for us.
Last updated: 2024-02-27

Sort by relevance or date