Post by mattkaree on Mapping values with etherCAT mailbox communication ^{CODESYS Forge talk (Post)}
I am using a WAGO PFC200 PLC as an etherCAT master and a Keyence IV3-G120 with DL-EC1A attached as an etherCAT slave. I am using CODESYS V3.5 SP21 Patch 3. I was able to set up mailbox communication and can see values changing accordingly, but I want to know how I can map these values and reference them in my program. I am able to map the process data objects in the 'EtherCAT I/O Mapping' tab, but there is no where to map the mailbox values in the 'CoE Online' tab. Is there a way I can reference one of these values in my code?
Last updated: 2026-01-27

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 gseidel on AXIS_REF_SM3 Error Codes? ^{CODESYS Forge talk (Post)}
Hi SLUCodesys, dwErrorId is a drive specific error number. The drive documentation should be consulted to interpret it. (Note that you should use MC_ReadAxisError to read this error, see https://content.helpme-codesys.com/en/libs/SM3_Basic/Current/SM3_Basic/POUs/Diagnostics/MC_ReadAxisError.html. Accessing the internal variable will result in outdated values if the acis error is not mapped by PDO and is not recommended in general.) uiDriveInterfaceError holds errors of the SoftMotion driver for the drive. It is also an internal variable, not intended for direct access. It is intended for logging, the PLC log will contain the drive interface error, consisting of this number and an error text. My recommendation for handling axis errors in the CODESYS application: 1) Use MC_ReadStatus on the axis to find out whether it is in state Errorstop 2) If in Errorstop, there are two possibilities: an error reported by the drive (MC_ReadAxisError) or an error of the SoftMotion function blocks (output MC_ReadStatus.FBErrorOccured). 3) If there is no drive error, you can use SMC_ReadFBError https://content.helpme-codesys.com/en/libs/SM3_Basic/Current/SM3_Basic/POUs/Diagnostics/FBError/SMC_ReadFBError.html Best regards, Georg
Last updated: 2025-09-24

Post by marek71 on Ambiguous use of name - CO136 ^{CODESYS Forge talk (Post)}
My PLC is WAGO PFC200 Firmware Revision 26. target After updating WAGO_Devices_and_Libraries with newer Firmware 27, CODESYS wants to update all libraries to new versions. I will only add that I did not update the Firmware in the PLC. After compiling the program, I received the following errors: ------ Build started: Application: Device.Application ------- Typify code... [ERROR] wagosyscom_internal_pfc, 1.0.2.5 (wago): FbSerialInterface_internal: C0136: Ambiguous use of name 'RTS_IEC_HANDLE' [ERROR] wagosyscom_internal_pfc, 1.0.2.5 (wago): FbSerialInterface_internal: C0136: Ambiguous use of name 'RTS_IEC_RESULT' [ERROR] wagosyscom_internal_pfc, 1.0.2.5 (wago): Initialize [FbSerialInterface_internal]: C0032: Cannot convert type 'Unknown type: 'RTS_INVALID_HANDLE'' to type 'POINTER TO BYTE' [ERROR] wagosyscom_internal_pfc, 1.0.2.5 (wago): Initialize [FbSerialInterface_internal]: C0136: Ambiguous use of name 'RTS_INVALID_HANDLE' [ERROR] wagosyscom_internal_pfc, 1.0.2.5 (wago): Initialize [FbSerialInterface_internal]: C0046: Identifier 'RTS_INVALID_HANDLE' not defined [ERROR] wagosyscom_internal_pfc, 1.0.2.5 (wago): comextra_is_tx_empty: C0136: Ambiguous use of name 'RTS_IEC_HANDLE' [ERROR] wagosyscom_internal_pfc, 1.0.2.5 (wago): comextra_get_line_state: C0136: Ambiguous use of name 'RTS_IEC_HANDLE' [ERROR] wagosyscom_internal_pfc, 1.0.2.5 (wago): comextra_is_line_available: C0136: Ambiguous use of name 'RTS_IEC_HANDLE' [ERROR] wagosyscom_internal_pfc, 1.0.2.5 (wago): COMSW_SET_MODE: C0136: Ambiguous use of name 'RTS_IEC_HANDLE' [ERROR] wagosyscom_internal_pfc, 1.0.2.5 (wago): comextra_set_line_state: C0136: Ambiguous use of name 'RTS_IEC_HANDLE' Compile complete -- 10 errors, 0 warnings Build complete -- 10 errors, 0 warnings : No download possible The problem was caused by the WagoSysPlainMem(WAGO) library in the original version 1.5.3.0 after updating to 1.5.3.1. After returning to version 1.5.3.0, the problems disappeared. Probably the version number of this library is responsible for supporting the appropriate Firmware Revision. Can anyone confirm or deny my suspicions?
Last updated: 2024-07-06

Post by tim-roelant on Profinet fault with codesys control V3 - Receive packet error ^{CODESYS Forge talk (Post)}
I have set up a brandnew Beckhoff panel pc with a codesys control runtime V3. I configured it together with 2 profinet field devices: a 16in/16out IO module from Turck and an MTS linear encoder. The machine works fine untill all of a sudden the communication breaks and the profinet participants become unreachable. At that point I can still ping the device, but the profinet master does not find them anymore: When i do a scan they are not found. When i do a cold restart, the profinet master becomes active again and the devices are found again. In the log i get Ethercat packet receive error: sysethernet. I am a little confused, there is no ethercat device in the device tree. I already set the send clock and the reduction ratio to higher values, but without result. Can codesys be configured, so that the communication re-establishes without doing the cold reset? This is very annoying and is causing a lot of prodution losses. regards Tim
Last updated: 2024-02-27

Post by tim-roelant on Profinet fault with codesys control V3 - Receive packet error ^{CODESYS Forge talk (Post)}
I have set up a brandnew Beckhoff panel pc with a codesys control runtime V3. I configured it together with 2 profinet field devices: a 16in/16out IO module from Turck and an MTS linear encoder. The machine works fine untill all of a sudden the communication breaks and the profinet participants become unreachable. At that point I can still ping the device, but the profinet master does not find them anymore: When i do a scan they are not found. When i do a cold restart, the profinet master becomes active again and the devices are found again. In the log i get Ethercat packet receive error: sysethernet. I am a little confused, there is no ethercat device in the device tree. I already set the send clock and the reduction ratio to higher values, but without result. Can codesys be configured, so that the communication re-establishes without doing the cold reset? This is very annoying and is causing a lot of prodution losses. regards Tim
Last updated: 2024-02-27

Post by tim-roelant on Profinet fault with codesys control V3 - Receive packet error ^{CODESYS Forge talk (Post)}
I have set up a brandnew Beckhoff panel pc with a codesys control runtime V3. I configured it together with 2 profinet field devices: a 16in/16out IO module from Turck and an MTS linear encoder. The machine works fine untill all of a sudden the communication breaks and the profinet participants become unreachable. At that point I can still ping the device, but the profinet master does not find them anymore: When i do a scan they are not found. When i do a cold restart, the profinet master becomes active again and the devices are found again. In the log i get Ethercat packet receive error: sysethernet. I am a little confused, there is no ethercat device in the device tree. I already set the send clock and the reduction ratio to higher values, but without result. Can codesys be configured, so that the communication re-establishes without doing the cold reset? This is very annoying and is causing a lot of prodution losses. regards Tim
Last updated: 2024-02-27

Post by tim-roelant on Profinet fault with codesys control V3 - Receive packet error ^{CODESYS Forge talk (Post)}
I have set up a brandnew Beckhoff panel pc with a codesys control runtime V3. I configured it together with 2 profinet field devices: a 16in/16out IO module from Turck and an MTS linear encoder. The machine works fine untill all of a sudden the communication breaks and the profinet participants become unreachable. At that point I can still ping the device, but the profinet master does not find them anymore: When i do a scan they are not found. When i do a cold restart, the profinet master becomes active again and the devices are found again. In the log i get Ethercat packet receive error: sysethernet. I am a little confused, there is no ethercat device in the device tree. I already set the send clock and the reduction ratio to higher values, but without result. Can codesys be configured, so that the communication re-establishes without doing the cold reset? This is very annoying and is causing a lot of prodution losses. regards Tim
Last updated: 2024-02-27

Post by konstantin on Lenze i950 Servo and WAGO PFC200 ^{CODESYS Forge talk (Post)}
Hello, In our workshop we have a Lenze i950 servo drive that has an EtherCAT bus and CiA402 compatibility. The WAGO is PFC200 750-8212 and as per documentation it has built-in license for SoftMotion Light functionality. It is not capable of supporting the full SoftMotion functionality like gearing and synchronizing. I added the EtherCAT esi files from Lenze and the EtherCAT master does see the drive, then I added a SoftMotion Light Axis object. The problem is that I can only energize the axis, I cannot execute any other commands. I set the positive and negative torque limits from the PDOs to 200% and when I try to move the axis by force it does not move back to its original position. I use the SML function blocks from the PLCOpen library and the error from the function blocks is that the op mode cannot be changed. Then I tried using a standard SoftMotion axis object and everything works fine, except the MC_Home function block. The axis moves back to its position when forced out of it. I follow this guide from Lenze - Lenze i950 CODESYS V3 What could cause this issue with the SoftMotion Light axis object? Best Regards Konstantin Kolev
Last updated: 5 days ago

Communication error (#0), logout performed,please check if plc is connected ^{CODESYS Forge talk (Thread)}
Communication error (#0), logout performed,please check if plc is connected
Last updated: 2023-09-11

Uninstall Codesys2.3 got RUNDLL There was a Problem Starting error ^{CODESYS Forge talk (Thread)}
Uninstall Codesys2.3 got RUNDLL There was a Problem Starting error
Last updated: 2024-07-15

Timeout Error in Modbus Communication with WAGO PFC200 and iEM2050 Meter using 750-652 Module ^{CODESYS Forge talk (Thread)}
Timeout Error in Modbus Communication with WAGO PFC200 and iEM2050 Meter using 750-652 Module
Last updated: 2024-07-30

Error while processing the visualization: Client id not present or no longer valid ^{CODESYS Forge talk (Thread)}
Error while processing the visualization: Client id not present or no longer valid
Last updated: 2024-08-21

Codesys V18 SP18 Patch 4 with G 1.2.1.0 - Error Checkout or Compare ^{CODESYS Forge talk (Thread)}
Codesys V18 SP18 Patch 4 with G 1.2.1.0 - Error Checkout or Compare
Last updated: 2024-08-21

ERROR: GetNetLinkSockAndInfoByMac(): could not open netlink socket: Too many open files ^{CODESYS Forge talk (Thread)}
ERROR: GetNetLinkSockAndInfoByMac(): could not open netlink socket: Too many open files
Last updated: 2024-09-19

Codesys v3.5 SP4 Patch 1 pbF: Internal error while opening archive with projects.open_archive() ^{CODESYS Forge talk (Thread)}
Codesys v3.5 SP4 Patch 1 pbF: Internal error while opening archive with projects.open_archive()
Last updated: 2025-08-25

MC_MoveAbsolute: C0138: No matching 'FB_Init' method found for instantiation of SMC_MoveAbsRelPerformerImpl [ERROR] ^{CODESYS Forge talk (Thread)}
MC_MoveAbsolute: C0138: No matching 'FB_Init' method found for instantiation of SMC_MoveAbsRelPerformerImpl [ERROR]
Last updated: 2025-10-02

ERROR C0138: No matching 'FB_Init' method found for instantiation of VisuClientObjectMgr ^{CODESYS Forge talk (Thread)}
ERROR C0138: No matching 'FB_Init' method found for instantiation of VisuClientObjectMgr
Last updated: 2025-10-07

enabling OPC UA connectivity while using motion control SM3_basic library gives build error ^{CODESYS Forge talk (Thread)}
enabling OPC UA connectivity while using motion control SM3_basic library gives build error
Last updated: 2018-08-22

[Error] HMI with CODESYS Control RTE SL does not show Pool images ^{CODESYS Forge talk (Thread)}
[Error] HMI with CODESYS Control RTE SL does not show Pool images
Last updated: 2022-06-21

Error 4709....Trends are not supported by the current target ^{CODESYS Forge talk (Thread)}
Error 4709....Trends are not supported by the current target
Last updated: 2012-04-02

CODESYS Control Win SL: Error Preparation was not successful: could not open network adapter ^{CODESYS Forge talk (Thread)}
CODESYS Control Win SL: Error Preparation was not successful: could not open network adapter
Last updated: 2023-05-19

Yellow triangle and bus not running error in Modbsu TCP master and Slave. ^{CODESYS Forge talk (Thread)}
Yellow triangle and bus not running error in Modbsu TCP master and Slave.
Last updated: 2021-12-07

what to do in case of a writing error to eeprom ^{CODESYS Forge talk (Thread)}
what to do in case of a writing error to eeprom
Last updated: 2020-11-26

OPC-UA errors in log, how do I interpret the error codes? ^{CODESYS Forge talk (Thread)}
OPC-UA errors in log, how do I interpret the error codes?
Last updated: 2021-02-05

Sort by relevance or date