ENI server: Object type registry not found in the database ^{CODESYS Forge talk (Thread)}
ENI server: Object type registry not found in the database
Last updated: 2010-02-19

changing the type of an existing POU from FB to PRG ^{CODESYS Forge talk (Thread)}
changing the type of an existing POU from FB to PRG
Last updated: 2012-12-14

CmpIecVarAccess to get name of a type, not of a variable (instance) ^{CODESYS Forge talk (Thread)}
CmpIecVarAccess to get name of a type, not of a variable (instance)
Last updated: 2016-06-08

How to use Jerk input and Velocity ramp type in MC_MoveAbsolute ^{CODESYS Forge talk (Thread)}
How to use Jerk input and Velocity ramp type in MC_MoveAbsolute
Last updated: 2018-07-09

Problem configuring the 750-638 Counter for Hall-type sensor ^{CODESYS Forge talk (Thread)}
Problem configuring the 750-638 Counter for Hall-type sensor
Last updated: 2012-10-29

Post by struccc on Release SP20 - Changes in behaviour? ^{CODESYS Forge talk (Post)}
Dear all, I've just started to migrate some of my ancient projects to SP20. There is one strange error (?) I have noticed so far. In a method call, depending on the circumstances I would like to return reference to an object, or an invalid reference: METHOD Add_EVT_OUT : REFERENCE TO FB_MSG VAR END_VAR IF __ISVALIDREF(refMSG_Entry) THEN Add_EVT_OUT REF= MANAGER.AddMsg_EVT_OUT( refMSG_Entry, _Get_EVT_Message(MSG_EVENT.OUT), _Get_EVT_AddCode(MSG_EVENT.OUT) )^; ELSE Add_EVT_OUT := 0; END_IF So far setting a reference variable to 0, did this. But now, the expression Add_EVT_OUT := 0; gives an error: [ERROR] DB_WTP_370: Add_EVT_ACK MSG_TRIGGER_EXT: C0032: Cannot convert type 'BIT' to type 'REFERENCE TO FB_MSG' Naturally... I can write: Add_EVT_OUT := DWORD#0; But is this the correct way? Is there any constant I could use instead, like "NULL"? Or this is totally wrong and to be avoided?
Last updated: 2024-03-24

Post by pethun on Upgrade from codesys 3.5.19 to 3.5.20 ^{CODESYS Forge talk (Post)}
Hi We upgraded our ptoject from 3.5.19 to 3.5.20 but we get an error message in the latest version. We made our own trend function and its related to this we get error message: Trend_Menu Device: PLC Logic: Application: C0032: Cannot convert type 'RTS_SYSTIMEDATE(systimertc, 3.5.20.0 (system))' to type 'RTS_SYSTIMEDATE(systimertc, 3.5.17.0 (system))' The variables are defined as follow: start : SysTimeRtc.SYSTIMEDATE; end : SysTimeRtc.SYSTIMEDATE; The code that creates the error is the variable start and end IF xAssign THEN xAssign := FALSE; xPanEnable := FALSE; xZoomEnable := FALSE; drs.liFrom := VisuTrendStorageAccess.TrendStorageConvertToTimestamp(start, 0 (us)); drs.liTo := VisuTrendStorageAccess.TrendStorageConvertToTimestamp(end, 0 (us)); drs.m_itfDateRangeSelectorClient.SetCurrentRange(drs.liFrom, drs.liTo); END_IF I cant understand really what the error message means and what can be the cause of the error? It compiles fine in dthe older codesys 3.5.19. If anyone has some experience of this please help us out? We must upgrade due to the new licenses. Thanks
Last updated: 2024-04-20

Post by pethun on Upgrade from codesys 3.5.19 to 3.5.20 ^{CODESYS Forge talk (Post)}
Hi We upgraded our ptoject from 3.5.19 to 3.5.20 but we get an error message in the latest version. We made our own trend function and its related to this we get error message: Trend_Menu Device: PLC Logic: Application: C0032: Cannot convert type 'RTS_SYSTIMEDATE(systimertc, 3.5.20.0 (system))' to type 'RTS_SYSTIMEDATE(systimertc, 3.5.17.0 (system))' The variables are defined as follow: start : SysTimeRtc.SYSTIMEDATE; end : SysTimeRtc.SYSTIMEDATE; The code that creates the error is the variable start and end IF xAssign THEN xAssign := FALSE; xPanEnable := FALSE; xZoomEnable := FALSE; drs.liFrom := VisuTrendStorageAccess.TrendStorageConvertToTimestamp(start, 0 (us)); drs.liTo := VisuTrendStorageAccess.TrendStorageConvertToTimestamp(end, 0 (us)); drs.m_itfDateRangeSelectorClient.SetCurrentRange(drs.liFrom, drs.liTo); END_IF I cant understand really what the error message means and what can be the cause of the error? It compiles fine in dthe older codesys 3.5.19. If anyone has some experience of this please help us out? We must upgrade due to the new licenses. Thanks
Last updated: 2024-04-20

Post by song on How to convert a standard robot program into an excutive list when a robot runs? ^{CODESYS Forge talk (Post)}
Dear Sir, I'd like to learn and try to make robot based on Codesys, is there a FB block or other ways to convert a standard robot program into an excutive list? how codesys explain the robot command instructions on HMI, just like the SMC_NCDecoder used to convert CNC program into a list of SMC_GEOINFO object. Thanks very much! Peter Yan
Last updated: 2023-11-25

Post by gatto on Read codesys version in the codesys application ^{CODESYS Forge talk (Post)}
hi, i used another way declaration: pApp : POINTER TO APPLICATION; pAppInfo : POINTER TO APPLICATION_INFO; ProjectName : STRING (24) ; CodesysVersion : STRING (15) ; code: //library : // CmpApp // IoDrvEthernet // // Get Pointer to current application pApp := CmpApp.AppGetCurrent( pResult:= 0 ); // Get Pointer to Application information pAppInfo := CmpApp.AppGetApplicationInfo(pApp:= pApp, pResult:= 0 ); ProjectName := pAppInfo^.pstProjectName^ ; //convert codesys version to string CodesysVersion := IoDrvEthernet.UDINT_TO_IPSTRING ( udiIPAddress := pApp^.udiPSVersion ) ; so i think you need to convert your dwVersion in a UDINT and after convert UDINT_TO_IPSTRING
Last updated: 2025-01-17

Post by rabaggett on CODESYS control for Raspberry Pi 64 SL errors ^{CODESYS Forge talk (Post)}
Hi, I am trying to create a project using a raspberry pi, I have added the modules for the Pi and MCP3008. I have encountered som errors that I don't know how to track down. 1. The GPIOs give preprocessor errors, but I read that this does not prevent compiling. This seems to be true. I can build the empty project with no errors. 2. After adding a SPI master and MCP3008, the preprocessor errors double, but seem similar and the project again builds with no errors. 3. I add a DUT and GVL, with a function, and I get the following errors. They remain even if I delete these things. ------ Build started: Application: Device.Application ------- Typify code... [ERROR] crr: C0032: Cannot convert type 'Unknown type: 'ADR(GVL_Io_17160064_c083_41f8_9e53_208be7537753_HPS_7.Io_17160064_c083_41f8_9e53_208be7537753_HPS_7)'' to type 'POINTER TO IoConfigParameter' [ERROR] crr: C0077: Unknown type: 'GVL_Io_17160064_c083_41f8_9e53_208be7537753_HPS_7.Io_17160064_c083_41f8_9e53_208be7537753_HPS_7' [ERROR] crr: C0046: Identifier 'GVL_Io_17160064_c083_41f8_9e53_208be7537753_HPS_7' not defined Compile complete -- 3 errors, 0 warnings I attach the project. What am I doing wrong? Thanks!
Last updated: 2024-05-02

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 abauza on Type mappings in Datasource ^{CODESYS Forge talk (Post)}
Hi I have the same problem, any solution for this? Thanks
Last updated: 2024-09-12

Post by eschwellinger on File Transfer Error 4 ^{CODESYS Forge talk (Post)}
Which plc type and which version?
Last updated: 2024-11-25

Post by installwhat on Unable to select VisuDialogs.Numpad in Open Dialog input configuration ^{CODESYS Forge talk (Post)}
data type?
Last updated: 2025-07-16

Post by imdatatas on The default ramp type selection in SoftMotion V4.18.0.0 is Quadratic ^{CODESYS Forge talk (Post)}
Dear @gseidel, @tk096, I noticed that with SoftMotion V4.18.0.0, if a new axis is added to the project, the ramp type selection defaults to "Quadratic". In all previous versions, the velocity ramp type selection was "Trapezoidal". This causes some unexpected issues in projects with SoftMotion version V4.18.0.0 for newly created or newly added axes to existing projects. Is it possible to reconsider this situation in the next update and set the velocity ramp type to "Trapezoid" by default again? Best Regards, Imdat
Last updated: 2025-07-22

Post by snhatton on Add device greyed out ^{CODESYS Forge talk (Post)}
What type of PLC are you using?
Last updated: 2023-12-19

Post by snhatton on Add device greyed out ^{CODESYS Forge talk (Post)}
What type of PLC are you using?
Last updated: 2023-12-19

Post by eschwellinger on Add licence ^{CODESYS Forge talk (Post)}
Which plc and in which version? Runtime Type? Runtime Version?
Last updated: 2024-01-05

Post by macros8 on Alarm Management - latched variable represented as Text list ^{CODESYS Forge talk (Post)}
Hi, I haven´t noticed you put the comment here. I thing it´s a bit different. What I want is to have detail errors of technology in data type e.g. INT. This variable I would latch to the corresponding error msg but I would like to get it convert to text from the text list and not keep it in INT form. Example. Main error Valve Error: SubErrors 1 - Both sensors 2 - Not retracted in time 3 - Not pulled out in time In HMI Main error + latch SubErrors => "Valve Error: Both sensors" The benefit is that text lists are part of translation and can be easily manipulated. I know I can create whole string msg in PLC but then, it lose advantage of Alarm management. Thanks. M.
Last updated: 2023-11-07

Post by alexgooi on Modbus writing on value change ^{CODESYS Forge talk (Post)}
The way I usally tackle this is by syncing only words (then you are able to use the FB above). If you then want to write a Boolean simply type it like this. Value[1].0 := Bool1; Value[1].1 := Bool2; Value[1].2 := Bool3; Uints have the same number of bits than a INT/WORD so these ones will work as well (they are only represented diffrently). A Real will work but you will loose some infomration in the conversion. If you want to keep the information you can convert 2 words to a float with a function (for example with the IEEE-754 standard) . In this way the syncing to the server is very simple and in the Codesys Program you decide what part of the word you want to use.
Last updated: 2024-04-03

Post by smartcoco on OPC server in "Communication manager" ^{CODESYS Forge talk (Post)}
I don't recommend using 'Communication Manager'. Under 'Communication Manager', the 'NodeId' type of OPC UA can only be of type 'OPAQUE'. This will bring compatibility issues to the development of the upper computer.
Last updated: 2025-01-24

Post by altus22 on Type SM3_Drive is not equal to type SM3_Drive ^{CODESYS Forge talk (Post)}
Another way to resolve this is to set Codesys to use a specific version of the offending library under Placeholders in the Library Manager.
Last updated: 2025-04-17

Post by imdatatas on The default ramp type selection in SoftMotion V4.18.0.0 is Quadratic ^{CODESYS Forge talk (Post)}
Unfortunately, The same behaviour still exist with SoftMotion V4.19.0.0 too. (default ramp type is quadratic instead trapezoid for new created axis object) For your information.
Last updated: 2025-09-04

[ERROR] The PLCopenXML import is not possible because Device not found. Type: 89, Id: 0000 0005, Version: 3.5.10.0 ^{CODESYS Forge talk (Thread)}
[ERROR] The PLCopenXML import is not possible because Device not found. Type: 89, Id: 0000 0005, Version: 3.5.10.0
Last updated: 2024-02-15

Sort by relevance or date