Post by winki on Modbus TCP & RTU with Control for Linux SL ^{CODESYS Forge talk (Post)}
No, my vpn is 10.0.0.12. The docker interface is 172.17.0.1.
Last updated: 2024-10-24

Post by eschwellinger on Only single ehternet ip drive is communicating ^{CODESYS Forge talk (Post)}
which versions EIP & Runtime and which plc is this? Does it work if they are connected to one network interface?
Last updated: 2024-03-09

Post by ara32 on CODESYS 4 Linux: ^{CODESYS Forge talk (Post)}
Hello! I managed to correctly launch CODESYS Developer Studio 3.5.17, almost all functionality works. The only issue remaining is that when connecting to a device and obtaining its public key, the NCryptEncrypt function is called, which is not fully implemented in the DLL source code, resulting in the connection not being established. Currently, the code of this function in the Wine repository looks like this: SECURITY_STATUS WINAPI NCryptEncrypt(NCRYPT_KEY_HANDLE key, BYTE *input, DWORD insize, void *padding, BYTE *output, DWORD outsize, DWORD *result, DWORD flags) { struct object *key_object = (struct object *)key; TRACE("(%#Ix, %p, %lu, %p, %p, %lu, %p, %#lx)\n", key, input, insize, padding, output, outsize, result, flags); if (flags & ~(NCRYPT_NO_PADDING_FLAG | NCRYPT_PAD_OAEP_FLAG | NCRYPT_PAD_PKCS1_FLAG | NCRYPT_SILENT_FLAG)) { FIXME("Flags %lx not supported\n", flags); return NTE_BAD_FLAGS; } if (flags & NCRYPT_NO_PADDING_FLAG || flags & NCRYPT_PAD_OAEP_FLAG) { FIXME("No padding and oaep padding not supported\n"); return NTE_NOT_SUPPORTED; } if (key_object->type != KEY) return NTE_INVALID_HANDLE; return map_ntstatus(BCryptEncrypt(key_object->key.bcrypt_key, input, insize, padding, NULL, 0, output, outsize, result, flags)); } The program crashes due to the NCRYPT_PAD_OAEP_FLAG flag. I'm not proficient in C++, but I attempted to add handling myself, and here's the result: SECURITY_STATUS WINAPI NCryptEncrypt(NCRYPT_KEY_HANDLE key, BYTE *input, DWORD insize, void *padding, BYTE *output, DWORD outsize, DWORD *result, DWORD flags) { struct object *key_object = (struct object *)key; TRACE("(%#Ix, %p, %lu, %p, %p, %lu, %p, %#lx)\n", key, input, insize, padding, output, outsize, result, flags); if (flags & ~(NCRYPT_NO_PADDING_FLAG | NCRYPT_PAD_OAEP_FLAG | NCRYPT_PAD_PKCS1_FLAG | NCRYPT_SILENT_FLAG)) { FIXME("Flags %lx not supported\n", flags); return NTE_BAD_FLAGS; } if (flags & NCRYPT_NO_PADDING_FLAG) { FIXME("No padding not supported\n"); return NTE_NOT_SUPPORTED; } BCRYPT_OAEP_PADDING_INFO oaepInfo = { 0 }; oaepInfo.pszAlgId = BCRYPT_SHA1_ALGORITHM; NTSTATUS status = BCryptEncrypt(key_object->key.bcrypt_key, input, insize, &oaepInfo, NULL, 0, output, outsize, result, flags); if (key_object->type != KEY) return NTE_INVALID_HANDLE; return map_ntstatus(BCryptEncrypt(key_object->key.bcrypt_key, input, insize, padding, NULL, 0, output, outsize, result, flags)); } Now, when calling the connection, it crashes with the error "bcrypt:BCryptEncrypt flags 0x4 not implemented." Can anyone help with enhancing this functionality or at least point me in the right direction?
Last updated: 2024-03-22

Post by imdatatas on The default ramp type selection in SoftMotion V4.18.0.0 is Quadratic ^{CODESYS Forge talk (Post)}
Dear @gseidel, Thank you for your clarification. I fully agree that the quadratic ramp type may have certain technical advantages. However, the main problem is backward compatibility and consistency across projects. In many automation projects, application developers rely on the fact that creating a new axis object will behave exactly the same way as in previous versions. With SoftMotion V4.18.0.0 and later, if an application developer adds an axis and overlooks the changed default, the motion function blocks behave differently than expected. In particular, since the Jerk value in SM3_Basic function blocks is ineffective in trapezoid ramp type, users are accustomed to leaving this parameter empty in their projects. In many existing projects, this variable has not even been assigned. When the default is changed to quadratic, the Jerk parameter suddenly becomes relevant, which can cause errors or unexpected behaviour in the field. From a user perspective, a default setting should always be the “safe” and “expected” option, while alternative options (like quadratic) can be selected manually if desired. Keeping the default as trapezoid ensures compatibility with existing projects and prevents unexpected issues, while still allowing users to benefit from quadratic ramps if they explicitly choose so. For these reasons, I kindly ask you to reconsider making trapezoid the default again. This would significantly reduce the risk of unexpected behaviour in future projects while still preserving the advantages of the quadratic ramp type for those who actively select it. Of course, the final decision is entirely at your discretion. Best Regards, imdatatas
Last updated: 2025-09-26

Post by ewi04 on Recipe Manager - RecipeManCommands, load & write wrong values, Bug? ^{CODESYS Forge talk (Post)}
Hallo, I have a strange problem with the recipe manager. ISSUE: When using RecipeManCommands not all values are loaded correctly. Saving a recipe with CreateRecipe(), ReadAndSaveRecipe() or ReadAndSaveRecipeAs() works without any problems. BUT: LoadRecipe(), WriteRecipe() or LoadFromAndWriteRecipe() do not load the data correctly. It is Interesting that we have a different error pattern with LoadRecipe() than with WriteRecipe() or LoadFromAndWriteRecipe(). LoadRecipe() does not load all data and WriteRecipe() or LoadFromAndWriteRecipe() overwrites some data or assigns it incorrectly. And it is also strange that LoadRecipe() writes the values to the PLC. Normally it doesn’t do it. It makes no difference whether the memory type is textual or binary. I have an object consisting of STRUCTs which is inserted in the recipe definition. Environment: Codesys V3.5 SP19 Patch 4 (64Bit), Recipe Management 4.2.0.0 *Add a project (reduced to the problem)
Last updated: 2023-11-15

Post by gseidel on Beckhoff AS1060 and EL7041 configuration ^{CODESYS Forge talk (Post)}
Hi pmanuele, while I don't have firsthand experience with the EL7041 and the step motor AS1060, there are two things you can check: If you use an external encoder, please make sure you use the alternative device description calles "EL7041 1Ch. Stepper motor output stage (50V, 5A) Rev24 with external Encoder". The SoftMotion driver will set the feedback type automatically, and use the correct object for the actual position (16#6010:21 instead of 16#6010:20) If you have problems with changing the controller mode, I assume to velocity, please make sure you change the PDO mapping so that the actual velocity (16#6020:33) and set velocity (16#7010:33) are mapped by PDO. Hope this helps, Georg
Last updated: 2024-12-23

Post by pernockham on Inheritence of struct, ^{CODESYS Forge talk (Post)}
Im looking for a way to define predefined version of the same structures through "extends"/inheritance. What I want to do is best shown with an example: TYPE log_item_val_type : ( BOOL_ := 0, INT_, REAL_, STRING_ ); END_TYPE TYPE LOG_DATA_BASE STRUCT val_type : log_item_val_type; (* value, name etc *) ENDSTRUCT ENDTYPE (* this/below is not possible as I understand from the compiler?? *) TYPE LOG_DATA_BOOL extends LOG_DATA_BASE : STRUCT val_type : log_item_val_type := log_item_val_type.BOOL_; END_STRUCT END_TYPE TYPE LOG_DATA_INT extends LOG_DATA_BASE : STRUCT val_type : log_item_val_type := log_item_val_type.INT_; END_STRUCT END_TYPE etc. for LOG_DATA_REAL and ..STRING. The system will not allow me to "re-define" "val_type" however. Instead I must do the work-around of defining four different types with all fields individually defined. The benefit if I could extend the base item would be that Im (more) sure the structures are identical. In usage I can call in a specific type rather use the base type and assign which type. Usage by pointer/ref to log_data_base would also be easier.. (* Usage: *) log_data : log_data_int := (name, value etc.) (* Instead of: *) log_data : log_data_base := (name, value, val_type).. Is this possible to achieve in some way that I have missed?
Last updated: 2025-03-05

Post by ihatemaryfisher on Sorting array of any-sized structure ^{CODESYS Forge talk (Post)}
With that I could make an array of varying size, but would still have to define the array type in the function's declaration VAR_IN_OUT stArray: array [*..*] of <pre-defined data type> END_VAR I wanted a function that could take an array of any type (e.g., a structured VAR) as an input. That way I could call it in multiple POUs to handle different arrays structures.
Last updated: 2023-08-18

Post by simotion on Inheritance of axis ^{CODESYS Forge talk (Post)}
I have developped a function block 'Axis' the inherits from 'AXIS_REF_SM3' -> FUNCTION_BLOCK Axis EXTENDS AXIS_REF_SM3 In my global variable list I define a variable MasterDrive of type Axis and assign Axis1. Axis1 is a virtual drive (AXIS_REF_VIRTUAL_SM3). This type should inherit from AXIS_REF_VIRTUAL. VAR_GLOBAL MasterDrive : Axis := Axis1; However I get the error 'Cannot convert type'. What is the way to obtain what I want : function block inheriting AXIS_REF_SM3 and initialising this function block with a Softmotion virtual or real axis?
Last updated: 2023-12-07

Post by timvh on Device logon problem following fresh install ^{CODESYS Forge talk (Post)}
In your project you selected the "CODESYS Control Win V3" as device, but the device you want to connect to is a "CODESYS Control Win V3 x64". Those are not the same. If you double click on the device during the network scan, you will get information that these are not the same, but that you can change the type in your project to the x64 bit type. Another option is to "right-click" on the device in the device tree of your project and select "update device" then select the x64 type.
Last updated: 2024-03-19

Post by xcqt on Oop best practice ^{CODESYS Forge talk (Post)}
Hi all, I’m currently trying to improve my OOP structure in CODESYS and I’m looking for some input on how others approach this. I understand the basics like inheritance, interfaces, abstract FBs, methods, and properties, but I still struggle a bit with the overall architecture and what’s considered clean or scalable in bigger projects. As an example, I’m working on two different energy meter function blocks: FB_EnergyMeter_MQTT reads data from MQTT (strings) FB_EnergyMeter_Modbus reads data from Modbus (words) Both have their own Update() method and implement the same interface (something like IF_EnergyMeter). Later on, I’ll probably add more meter types, but they should all behave the same from the controller’s point of view. Now, there’s a FB_GridControl block that needs power data from these meters. I see two options here: Define the meter blocks inside FB_GridControl and call them directly (for example fbModbusMeter.UpdateModbus()). Keep the meter blocks outside and pass them into FB_GridControl as interface references, so the control block doesn’t know which specific type of meter it’s dealing with. Option 2 feels cleaner and more flexible to me, but I’m not entirely sure how to handle the data flow in that case. Should I pass the meter instance through an interface reference (REFERENCE TO IF_EnergyMeter)? Or is there a better way to link the external FBs to the control block? I’d like to hear how you structure this kind of setup or see an example from someone who has done something similar. EDIT: I think i need to do something like this fbModbusUpdateInput(wInput:= wWordValue); fbMqttUpdateInput(strInput:= strStringValue); IF bUseMqtt THEN Meter REF = fbMqttUpdateInput; ELSE Meter REF = fbModbusUpdateInput; END_IF fbControl.SetMeter(UsedMeter := Meter); Or am i thinking wrong? Thanks, Thomas
Last updated: 2025-10-16

Post by jeroenaero on Problem with CodeSys Control SL Deploy Tool 4.15.0.0 ^{CODESYS Forge talk (Post)}
Hello, We just installed the new version of CodeSys Control SL Deploy Tool 4.15.0.0 but we get the following error when we try to add a VPLC. Can someone of the CodeSys team fix this issue? the object reference is not set to an instance of the object Zie het einde van dit bericht voor meer informatie over het aanroepen van JIT-foutopsporing (Just In Time) in plaats van dit dialoogvenster. ** Tekst van uitzondering ** System.NullReferenceException: De objectverwijzing is niet op een exemplaar van een object ingesteld. bij _3S.CoDeSys.RuntimeDeployTool.Views.AddNewInstanceForm.ShowAllImages() bij _3S.CoDeSys.RuntimeDeployTool.Views.AddNewInstanceForm..ctor(List1 virtualControls, List1 existingNames) bij _3S.CoDeSys.RuntimeDeployTool.Views.MainEditorTab_Operation.OnAddInstanceClick() bij _3S.CoDeSys.RuntimeDeployTool.Views.MainEditorTab_Operation.bt_add_Click(Object sender, EventArgs e) bij System.Windows.Forms.ToolStripItem.RaiseEvent(Object key, EventArgs e) bij System.Windows.Forms.ToolStripButton.OnClick(EventArgs e) bij System.Windows.Forms.ToolStripItem.HandleClick(EventArgs e) bij System.Windows.Forms.ToolStripItem.HandleMouseUp(MouseEventArgs e) bij System.Windows.Forms.ToolStripItem.FireEventInteractive(EventArgs e, ToolStripItemEventType met) bij System.Windows.Forms.ToolStripItem.FireEvent(EventArgs e, ToolStripItemEventType met) bij System.Windows.Forms.ToolStrip.OnMouseUp(MouseEventArgs mea) bij System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks) bij System.Windows.Forms.Control.WndProc(Message& m) bij System.Windows.Forms.ScrollableControl.WndProc(Message& m) bij System.Windows.Forms.ToolStrip.WndProc(Message& m) bij System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m) bij System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m) bij System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam) ** Geladen assembly's ** mscorlib Assembly-versie: 4.0.0.0 Win32-versie: 4.8.9300.0 built by: NET481REL1LAST_C
Last updated: 2025-04-24

Post by ph0010421 on How to manage variable types larger than 64 bits - Ethernet/IP ^{CODESYS Forge talk (Post)}
My guess is that's a STRING, not an INT type. And it's 128 bytes, not bits
Last updated: 2024-09-23

Post by athuum on Error 'Library not found' and 'Unkown type' ^{CODESYS Forge talk (Post)}
I have found the solution, the CmpEventMgr version has to correspond with the 3sLicense version.
Last updated: 2024-10-10

Post by eschwellinger on Server not adding PLC ^{CODESYS Forge talk (Post)}
which plc type do you try to add? Unique serial numbers of the plc are mandatory too.
Last updated: 2025-02-17

Post by timvh on Inheritence of struct, ^{CODESYS Forge talk (Post)}
Maybe the ANY type can help? https://content.helpme-codesys.com/en/CODESYS%20Development%20System/_cds_datatype_any.html
Last updated: 2025-03-08

Post by jampid on How do I fix ";Internal Error (x86-64): Invalid type size" error? ^{CODESYS Forge talk (Post)}
Bonjour Mucleus, peut-être mettre à jour le Device et recompiler?
Last updated: 2025-04-16

Post by dkugler on Reading a negative number ^{CODESYS Forge talk (Post)}
why not simply converting data type UINT to INT? Then avoid negative values with ... := MAX(0 , intTest); Good luck!
Last updated: 2025-05-28

Post by simotion on Property ^{CODESYS Forge talk (Post)}
Why can't a property be of type REFERENCE TO? Plc goes to stop if I try that.
Last updated: 2023-12-14

Post by askic on Name Validation of Visualization objects ^{CODESYS Forge talk (Post)}
Hello, In my projects, I'm following this recommendation about the rule names in Codesys https://content.helpme-codesys.com/en/CODESYS%20Development%20System/_cds_rules.html, so I always use backtick identifiers, not only for variables, but also for the object names. However, I have noticed that in the current version of Codesys, when adding Visu object, it is not allowed to used these identifiers in the name. This is very different from all other objects like, folder names, POU names, Variable list names etc. I wonder if there is some hidden settings I can use to enable backtick identifiers in the Visu object names? Attached is a screenshot with the details. Thank you!
Last updated: 2025-01-10

Post by george32 on Learning ST in an object-oriented way. ^{CODESYS Forge talk (Post)}
Dear all, I am currently creating a program in the ST language. Because the program is starting to grow nicely I would like to switch to a more object-oriented way of programming. (Like for example in Python). By surfing the internet I found out that Function Blocks is the best method for this. Now I would like to delve further into this, with all the possibilities that Function Blocks have only I cannot find a clear course, explanation of what everything is around the function block thing and how to approach everything. I find the standard documentation around Function Blocks rather abstract and the examples are minimal. Therefore I am looking for a page/course/document explaining object oriented programming in Codesys (or other PLC programming environment). Do you have any recommendations on this?
Last updated: 2025-06-10

Post by garrian on How to sort JSON object in codesys ^{CODESYS Forge talk (Post)}
Hi there, I'm testing out MQTT from my Wago PLC using JSON object. I have managed to publish this {"Temperature":15.6,"Setpoint":38.0} to my broker. Now I', trying to subscribe to the same message. The result is this: '{"Temperature":15.6,"Setpoint":38.0}95}ê$10šå$04$Nå$08²Ÿå$0B` á$08@šå' First, why do I see 95}ê$10šå$04$Nå$08²Ÿå$0B` á$08@šå' at the end of the message? Second, how Can i sort out this data to use it in my program? I followed a youtube tutorial which gave me the attached result, which works. But I need some other smart way of doing this when the object gets even more data in it. Any help is very appreciated :)
Last updated: 2024-05-04

Post by jonasz on Discontinuity of A/B/C axis movement. ^{CODESYS Forge talk (Post)}
Hi, My problem was related to the behavior of the modulo axis, but maybe you will find something useful from what I write. The solution lies in path processing. Codesys offers a G-code analysis tool. Insert a CNC object into the project. The CNC settings object will be added automatically. By inserting appropriate processing modules into the CNC settings object and parameterizing them, you can test the behavior of the axis. When the effect is satisfactory, remember to add the module from CNC settings in the correct order in the processing path. Each CNC machine case is different. You need to spend some time to get your design tailored like an Armani suit. Good luck.
Last updated: 2024-05-09

Post by eschwellinger on Scan Network on gateway created with Control Sl ^{CODESYS Forge talk (Post)}
it seems that the device you scan, is not the same type which you have added to the project in CODESYS. Virtual Control is Arm 64 SL so please select this type in CODESYS when you generate a new Application..or right click to the device- update device - virtual Control Arm 64 SL
Last updated: 2024-10-16

Post by rafaelbrito on The element of type 'VisuFbElemImage' could not be updated. Reason: Index was outside the bounds of the array. ^{CODESYS Forge talk (Post)}
When trying to use the Visualization ToolBox, no objects appear and the following error appears. Could you tell me what this error could be? The element of type 'VisuFbElemImage' could not be updated. Reason: Index was outside the bounds of the array. Can anyone tell me what this error is?
Last updated: 2024-12-03

Sort by relevance or date