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

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

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

"The identifier 'min' is not a valid IEC identifier" error, Profinet Controller configuration ^{CODESYS Forge talk (Thread)}
"The identifier 'min' is not a valid IEC identifier" error, Profinet Controller configuration
Last updated: 2023-04-03

WAGO PLC GOES IN ERROR WHILE BOOTING BECAUSE OF PERSISTENT VARIABLE ^{CODESYS Forge talk (Thread)}
WAGO PLC GOES IN ERROR WHILE BOOTING BECAUSE OF PERSISTENT VARIABLE
Last updated: 2019-11-22

Sort by relevance or date