Post by fdmartello on Unable to compare projects containing alarm manager 4.5.0.0 ^{CODESYS Forge talk (Post)}
Hello. In Codesys version 3.5.19.50 when comparing two projects that have an "Alarm Configuration" obj from the Alarm Manager library vers. 4.5.0.0 the attached error pops up. This originally happened with two projects that I converted from vers. 3.5.17.30 so, thinking it was some conversion issue, I created two clean projects directly in 3.5.19.50 using the Standard Project template and only added the Alarm Configuration objects in them. The result is the same and the only way I found that allowed me to compare them is by deleting the incriminated object in one of the two projects. Has anyone else encountered this issue? Best regards
Last updated: 2024-01-19

Post by matthew on New Ladder Diagram conversion does not work due to missing features ^{CODESYS Forge talk (Post)}
Hi It looks like in the new ladder there is no way to remove unused FB call parameters or update the function block? It's quite often where you have a function block with multiple uses and not all the parameters are required. Need the ability to leave an input/output blank without getting an compile error Expression expected instead of '' Also double clicking on the FB no longer opens the underlying FB code and view what it was doing online. Dragging and dropping a variable does not work, only using the selection works. Will these be available in the V1.0 release or just best to stick to the old ladder until it's available? Thanks
Last updated: 2024-01-28

Post by dhumphries on No source code available ^{CODESYS Forge talk (Post)}
Try using an Ethernet/IP scanner instead of an adapter, I'm guessing the 2 devices you're trying to communicate with are adapters, you have to have a scanner somewhere and Codesys should be a scanner. I don't know why you're getting the error, you should be able to use your Ethernet port as an EthernetIP adapter (although I've never had a reason to try,) but it's probably not what you wanted to do, unless you're connecting to another PLC that is a scanner. Good luck configuring the devices you're trying to connect to, it will be a lot easier if you have an .EDS file instead of starting with a generic module, even with an .EDS it can be tricky getting the communication working.
Last updated: 2024-02-03

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 timvh on Profinet fault with codesys control V3 - Receive packet error ^{CODESYS Forge talk (Post)}
Are you using the Control Win SL (installed together with the development environment of CODESYS)? If yes, you might want to consider using the CODESYS RTE instead. This has real-time capabilities (running on separate core(s)). But to be able to use this, you have to install the CODESYS Ethernet driver for your network interface to be able to let the RTE access the network port also in realtime. See: https://store.codesys.com/en/codesys-control-rte-sl-bundle.html https://content.helpme-codesys.com/en/CODESYS%20Control/_rtsl_windows_rts_v3.html PS, I haven't tested this myself yet, but you could try to use the SetCommunicationState method of the Profinet controller to see if you can reset and start the bus communication: result := PN_Controller.SetCommunicationState(eRequestedState := DED.DEVICE_TRANSITION_STATE.START); PS, if you are located in the Netherlands or Belgium, we could also provide the license(s) for you.
Last updated: 2024-02-28

Post by timvh on Profinet fault with codesys control V3 - Receive packet error ^{CODESYS Forge talk (Post)}
Are you using the Control Win SL (installed together with the development environment of CODESYS)? If yes, you might want to consider using the CODESYS RTE instead. This has real-time capabilities (running on separate core(s)). But to be able to use this, you have to install the CODESYS Ethernet driver for your network interface to be able to let the RTE access the network port also in realtime. See: https://store.codesys.com/en/codesys-control-rte-sl-bundle.html https://content.helpme-codesys.com/en/CODESYS%20Control/_rtsl_windows_rts_v3.html PS, I haven't tested this myself yet, but you could try to use the SetCommunicationState method of the Profinet controller to see if you can reset and start the bus communication: result := PN_Controller.SetCommunicationState(eRequestedState := DED.DEVICE_TRANSITION_STATE.START); PS, if you are located in the Netherlands or Belgium, we could also provide the license(s) for you.
Last updated: 2024-02-28

Post by valenting on Runtime not working on raspberry pi Bullseye ^{CODESYS Forge talk (Post)}
Hello I have a problem with Codesys on Raspberry pi with Bullseye The device is not recognized as a Raspberry pi, as I get this error : ooops... this runtime was built for RASPBERRYPI. Hardware version or firmware version not supported! (-18, 0x00000BB8, 0xFFFFFFFB) I'm running Codesys on a compute module 4S with Raspbian GNU/Linux 11 (bullseye), my kernel version is Linux 5.10.90-v7l+ Codesys version is the latest, released last week (4.11.0.0, CODESYS Control V3.5.19.61 for ARM-32Bit - build Feb 22 2024) I know it works on the same device if I use Raspbian 10 (Buster) with Linux 5.4.81-v7l+ kernel, but for some other reasons I have to use Bullseye. What can I do ?
Last updated: 2024-03-01

Post by comingback4u on Memory Address Overlap ^{CODESYS Forge talk (Post)}
Hello, We use a controller that comes with a bunch of predefined faults. These faults are considered active and historic. They are a 32 byte array but only take up 26 bytes of data. Because of this the historic faults start at address 26 instead of 31. Active faults variable take up address location 0 to 31. Historic faults variable take up address location 26 to 57. Because of this overlap I get an error that these overlap and it wont allow me to download to my controller. This isn't an issue in 3.5.5.4 but becomes an issue in newer version. Is there a way to turn this off? If I change the address location, the historic faults then become broken without doing some manipulation in the code. The software will build just fine. Thank you for your time.
Last updated: 2024-03-07

Post by superjojo2002 on Licensing info not available. ^{CODESYS Forge talk (Post)}
I recognized that I have to start the two services "/etc/init.d/codemeter" and "/etc/init.d/codemeter-webadmin" in the docker container as well. If I do so, then the command "cmu -x" returns root@sensoredge-field-netfield-produktmanagment:/# cmu -x cmu - CodeMeter Universal Support Tool. Version 7.60c of 2023-Aug-09 (Build 5625) for Linux/ARMHF 64-Bit Copyright (C) 2007-2023 by WIBU-SYSTEMS AG. All rights reserved. So this time there is no indication any more that "Codemeter is not running". But still we are getting the error when using the license manager in CODESYS development system.
Last updated: 2024-03-21

Post by peterned on CNC - system goes to X=0 Y=0 before CNC file execution starts, how to avoid that? ^{CODESYS Forge talk (Post)}
Hi, I have a XY system and use a CNC file to move it. Everything works OK, except for the following: when CNC execution starts, the system rushes at high speed to (X=0, Y=0) point, and only then goes to the first line of the CNC file. If one of the axes is near 0, the system jumps and immediately stops with an error. In the CNC file settings (screenshot attached) I specified low default values for speed/acceleration and a start position different from 0,0 - but all that is ignored. Any idea how to avoid that move to 0,0 ? Thanks.
Last updated: 2024-04-26

Post by esave on Softmotion Light Problem: The license is missing or invalid ^{CODESYS Forge talk (Post)}
Hello everybody I want to controll a stepper driver from Leadshine (EM3E-556E). The EtherCat slave is CiA 402 compatible. Because of this I bought the Softmotion Light Package from Codesys and implemented it in my project. I rightclicked the EtherCat slave and added the Softmotion Light axis. But now the error message shows: "The license is missing or invalid. The PLC runs in demo mode." What have i done wrong? I use Codesys 3.5.17. Is it possible that the stepper driver is not compatible with the Softmotion license? Thanks for all your help
Last updated: 2024-05-02

Post by fugtwad on Automation Builder V2.5 EtherCAT CM579 Master Scan for devices - >No gateway selected ^{CODESYS Forge talk (Post)}
ABB Automation Builder v2.5.0.22 Premium CodeSys 2.3.9.62 Running on Win 10 VM x64 Goal: I have an EtherCAT topology issue which normally a "Scan for devices.." on the EtherCAT master would shed some light on. Issue: Upon trying such I get a "No gateway selected" error. Question: How might I point the the "scanner" at a gateway? What is working: Gateway is running in system tray. I can go online to PLC. A scan from the "Diagnostics live" tab of the EtherCAT master gives slave status. What I have tried: Restarting gateway in system tray. Exiting system tray gateway and reloading it. Turning off firewall. Contacting ABB support multiple times. Any help appreciated.
Last updated: 2024-05-20

Post by kronlundo on Licensing info not available (WAGO PFC200 + Codesys V3) ^{CODESYS Forge talk (Post)}
Hi! We're using a WAGO PFC200 for several projects towards the energy sector, and recently upgraded to CODESYS V3. We have the "IEC 60870-5-104 Server" package in a test program, and it works well with the package in DEMO mode. However, when we acquired a license for the "IEC 60870-5-104 Server" package and tried to add the license on the PFC200 through the license manager, we get an error (see attached file). It seems like there is no CmContainer on the device, does anyone have an idea on how to fix this? We've also contacted WAGO on this issue a while back with no feedback yet.
Last updated: 2024-06-10

Post by salvadegianluca on SysPlcCtrl23 and C0338: The library 'cmperrors interfaces, 3.5.5.0 (system)' is supported just in 32 bit applications ^{CODESYS Forge talk (Post)}
Good afternoon to everyone; I'm stuck with this error and I don't know how to get out from it... I tried several time googling for alternative systems to control the PLC applications and resets but without success. I would like to realize the possibility to reset the CPU and to start/stop the applications as it was possible with the SysPlcCtrl23, but this library is no longer supported in 64 bit systems and it seems due to the cmperrors interfaces sub library that was included in the above said one. Someone found a work around for this issue?
Last updated: 2024-06-14

Post by salvadegianluca on SysPlcCtrl23 and C0338: The library 'cmperrors interfaces, 3.5.5.0 (system)' is supported just in 32 bit applications ^{CODESYS Forge talk (Post)}
Good afternoon to everyone; I'm stuck with this error and I don't know how to get out from it... I tried several time googling for alternative systems to control the PLC applications and resets but without success. I would like to realize the possibility to reset the CPU and to start/stop the applications as it was possible with the SysPlcCtrl23, but this library is no longer supported in 64 bit systems and it seems due to the cmperrors interfaces sub library that was included in the above said one. Someone found a work around for this issue?
Last updated: 2024-06-14

Post by salvadegianluca on SysPlcCtrl23 and C0338: The library 'cmperrors interfaces, 3.5.5.0 (system)' is supported just in 32 bit applications ^{CODESYS Forge talk (Post)}
Good afternoon to everyone; I'm stuck with this error and I don't know how to get out from it... I tried several time googling for alternative systems to control the PLC applications and resets but without success. I would like to realize the possibility to reset the CPU and to start/stop the applications as it was possible with the SysPlcCtrl23, but this library is no longer supported in 64 bit systems and it seems due to the cmperrors interfaces sub library that was included in the above said one. Someone found a work around for this issue?
Last updated: 2024-06-14

Post by salvadegianluca on SysPlcCtrl23 and C0338: The library 'cmperrors interfaces, 3.5.5.0 (system)' is supported just in 32 bit applications ^{CODESYS Forge talk (Post)}
Good afternoon to everyone; I'm stuck with this error and I don't know how to get out from it... I tried several time googling for alternative systems to control the PLC applications and resets but without success. I would like to realize the possibility to reset the CPU and to start/stop the applications as it was possible with the SysPlcCtrl23, but this library is no longer supported in 64 bit systems and it seems due to the cmperrors interfaces sub library that was included in the above said one. Someone found a work around for this issue?
Last updated: 2024-06-14

Post by salvadegianluca on SysPlcCtrl23 and C0338: The library 'cmperrors interfaces, 3.5.5.0 (system)' is supported just in 32 bit applications ^{CODESYS Forge talk (Post)}
Good afternoon to everyone; I'm stuck with this error and I don't know how to get out from it... I tried several time googling for alternative systems to control the PLC applications and resets but without success. I would like to realize the possibility to reset the CPU and to start/stop the applications as it was possible with the SysPlcCtrl23, but this library is no longer supported in 64 bit systems and it seems due to the cmperrors interfaces sub library that was included in the above said one. Someone found a work around for this issue?
Last updated: 2024-06-14

Post by salvadegianluca on SysPlcCtrl23 and C0338: The library 'cmperrors interfaces, 3.5.5.0 (system)' is supported just in 32 bit applications ^{CODESYS Forge talk (Post)}
Good afternoon to everyone; I'm stuck with this error and I don't know how to get out from it... I tried several time googling for alternative systems to control the PLC applications and resets but without success. I would like to realize the possibility to reset the CPU and to start/stop the applications as it was possible with the SysPlcCtrl23, but this library is no longer supported in 64 bit systems and it seems due to the cmperrors interfaces sub library that was included in the above said one. Someone found a work around for this issue?
Last updated: 2024-06-14

Post by mborchert on PFC100 Error "Bus not running" ^{CODESYS Forge talk (Post)}
Hello, i currently want to use a wago 750-8102 with the "codesys control for pfc100" runtime. I want to add the devices connected to the internal pfc100 bus via the "search devices" tab. This was reccommended in the following thread: https://forge.codesys.com/forge/talk/Deutsch/thread/7701332199/ But whenever i try to search for devices codesys just doesnt find anything and i cant close the "search devices" window. Has anyone got an idea what the problem might be? I already tried adding the devices connected to the pfc100 manually but the bus just doesn´t start. best regards Moritz
Last updated: 2024-06-17

Post by kazuhiro on Problems using MySql Library and SysProcessExecuteCommand2 together ^{CODESYS Forge talk (Post)}
I use fbMsSQL_compact(FUN) of the MySQL Library to write data to the database. There is no problem when writing data using only fbMsSQL_compact(FUN). However, when I try to write data obtained using SysProcessExecuteCommand2 to the database using fbMsSQL_compact(FUN), an error message "Dest server on ip address:xxx.xxx.xxx.xxx and port:1433 is unreachable" appears and writing is not possible. From what I have researched, it seems that writing is not completed in one cycle of fbMsSQL_compact(FUN), and when SysProcessExecuteCommand2 is executed first in the second cycle, the work done in one cycle of fbMsSQL_compact(FUN) is reset. Could you please give me some advice?
Last updated: 2024-06-18

Post by kazuhiro on Problems using MySql Library and SysProcessExecuteCommand2 together ^{CODESYS Forge talk (Post)}
I use fbMsSQL_compact(FUN) of the MySQL Library to write data to the database. There is no problem when writing data using only fbMsSQL_compact(FUN). However, when I try to write data obtained using SysProcessExecuteCommand2 to the database using fbMsSQL_compact(FUN), an error message "Dest server on ip address:xxx.xxx.xxx.xxx and port:1433 is unreachable" appears and writing is not possible. From what I have researched, it seems that writing is not completed in one cycle of fbMsSQL_compact(FUN), and when SysProcessExecuteCommand2 is executed first in the second cycle, the work done in one cycle of fbMsSQL_compact(FUN) is reset. Could you please give me some advice?
Last updated: 2024-06-18

Post by ron-rp on Errors with VisuUserManagement library ^{CODESYS Forge talk (Post)}
Hi all, I've played a bit with the VisuUserManagement library, and some other security option in my project, and I started getting this error when logging in - see attached pic. something to do with a specific screen in the library - VUM_Login. Also, Codesys started to ask me to log in to the library when logging in, asking to log in as user of the groups Maintainer or Owner, which I dont know either users (attached pic). when I close the login screen and try to log in to the PLC again, everything works again until I close and open Codesys. I do use user and password to login to the PLC, and this login screen is fine I know the user and pass I setup. anyone know what did I do wrong here and how to fix it?
Last updated: 2024-06-25

Post by yannickasselin on MQTT QoS 1 & 2 ^{CODESYS Forge talk (Post)}
Hello, After some more tests, here is what I found out. It seems we have to increase the uiKeepAlive and tPingInterval parameters. If I increase the uiKeepAlive value to 60s and the tPingInterval to 30s, then if I disconnect the ethernet cable from Codesys and publish some messages to which Codesys subscribes to and then reconnect within 30s, I will get the messages. If I don't reconnect the cable within 30s (ping interval), the client goes in error with "ACKNOWLEDGE_TIMEOUT". When this happens, it will not automatically reconnect after reconnecting the cable. I have to disable and re-enable the client but I will not get the published messages. I need to do more tests because there are a lot of weird things happening when playing with the ping interval and the keep alive. It is not clear to me what does what. I even ended up not receiving messages anymore, even if I disabled and re-enabled the mqtt client. The client did not give any error. The only way I was able to get messages again was by modifying my client ID. After that, if I try to re-use one of the old client IDs, nothing works (publish, subscribe) and I get a TCP_INIT_ERROR and sometimes a TCP_READ_ERROR. I need more explanation/documentation about these weird behaviors. Maybe it is the way I use it, maybe it is related to the broker (I am using Mosquitto with default parameters). When using a Node-Red client, everything works perfectly. I am trying to achieve the same behavior with Codesys but it seems impossible so far.
Last updated: 2024-10-30

Post by s1ack on Wago PFC200 Ethernet / IoDrvEthernet Issue? ^{CODESYS Forge talk (Post)}
CODESYS Control for PFC200 4.13.00 CODESYS IIoT Libraries SL 1.11.0.0 Application Based License: CODESYS Control Standard M I have (2) projects with similar code base and both using Wago PFC200. On the second project I am seeing 2 things that I have not been able to resolve: 1) Errors in the log under the Ethernet Item: IoDrvEthernet: [PCI\E1Q51CE62] Could not be found on target! Please check the Ethernet settings. 2) Exception for CPU Load. "Processorload watchdog: plcload=100, maxplcload=95" I have slowed down cyclic tasks on this project, even though on the first project there is actually more code - and it does not exhibit this behavior. In looking at the CPU loading via Linux 'TOP' command there appears to be 20% idle. So plenty of headroom (my opinion). In an effort to troubleshoot I have duplicated the target hardware on my bench. It ran overnight without a CPU load exception. On the test system, I have tried (3) version of the ethernet device. 3.5.16.0 3.5.17.0 and 4.2.0.0 Presently the log does not show the error, but status says the module reports an error. I really do not know if this issue is related to the CPU load exception. The issue does not appear to effect ethernet communications (ModbusTCP or SNMP or Webvisu or PuTTy into Linux Shell). On my test bench I have ModbusTCP slave simulators for all ModbusTCP slaves, but only (1) of the (5) SNMP devices present.
Last updated: 2025-01-21

Sort by relevance or date