Post by gvdb on Raspberry Pi 4 mod B icm codesys linking USB serial device (arduino) to com port ^{CODESYS Forge talk (Post)}
Raspberry Pi 4 Codesys 3.5.20 sp3 Codesyscontrol 4.15.0.0 based on sdk 3.5.21.0 Hi all, I have found a lot of topics but none of them get me on the right path, therfore i started a new post. Usually i work with plc based systems and codesys but now im trying to create an project where i read out a serial data stream from an arduino connected by an USB port. in the future this need to be more arduino's but first trying to make it work with one I had my program working but i needed to update my raspberry pu to the letest version to get the mimo screen working. Now i tried several rules in the CODESYSControl.cfg and/or CODESYSControl_User.cfg files but i never get the com port opened. At this moment i have an file CODESYSControl_User.cfg with entry: [SysCom] Linux.Devicefile.1=/dev/ttyUSB0 I tested the connection with minicom and the data runs fluently. Can somebody help me with what could be wrong? the com port states ERROR_UNKNOWN 5004 when i tried to open.
Last updated: 2025-07-17

Post by yannickasselin on MQTT QoS 1 & 2 ^{CODESYS Forge talk (Post)}
Hello, I am using Codesys sp20p3 and IIoT library 1.11. I am trying to test QoS 1 & 2 and I have some issues. I am using mosquitto as the broker. I am also using some other MQTT clients like Node-Red and TwinCAT. They all work as expected for every QoS levels. I only have issues with Codesys MQTT client. In the Codesys client, if I subscribe to a topic as QoS 1 or 2, and a client publishes to this topic, I receive the message. But if I disconnect the Codesys client from the network and a client publishes to the subscribed topic, when I reconnect Codesys client to the network, I don't receive the messages as expected. Also there does not seem to be an auto-reconnect feature. So I have to manually set the mqttClient.xEnable bit to FALSE then back to TRUE in order to reconnect to the broker, then I also have to set the subscribe.xEnable to FALSE and back to TRUE in order to re-subscribe to the topic, but even then, I don't receive the messages that were published while I was disconnected. What am I doing wrong? I set the cleanSession bit to FALSE and I give my client a clientID. With the TwinCAT MQTT Client, I do the same thing and everything works as expected. It even auto-reconnects to the broker. I would expect Codesys MQTT Client to be as reliable as TwinCAT. Maybe I am doing something wrong? I also noticed that when trying to publish a QoS 1 or 2 message while disconnected from the broker, it does not work. In TwinCAT, I am still able to publish. The messages are stored in the client and published once reconnected to the broker. I would expect to be able to do the same thing in Codesys. Is this all possible? Am I doing something wrong? Thank you
Last updated: 2024-10-26

Post by cer-wa on Not able to connect multiple profinet encoder in codesys Linux ARM64 ^{CODESYS Forge talk (Post)}
Hello, currently im working with a RevPi connect 5 on a codesys project. Up until now I was having a blast because things were going really smooth but for like almost a day im kind of stuck on the integration of multiple profinet sensors into my project. This is kind of a bummer because that should be an easy thing to do. What I tried so far was to create and additional ethernet adapter where I then tried to connect my devices. in the beginning I tried to connect the devices directly which was not working because I could assign the IP-adress only to the ethernet adapter and not to the devices but the device was found in the device repository (this gets important in the second part) So what I tried next was to setup a PN-Controller and connect my devices subsequently to the Controller. Sadly now the devices wont show up in the device repository anymore. To me its not clear why this is happening. And the worst thing is: I went ahead and setup a device completely like I would want to have it in the project and when I then click on scan devices I can even find the device. But it can not be added to project for whatever reason eventhough im 100% certain that the gsdml file is the correct one. Can anyone help me with this. Like I said this seems like an easy thing to do and its taking me way longer than expected already. The only thing that came to my mind why this might not work is because I have codesys license which only allows one profinet instance. Could that be the case? The error message seems then pretty unfit but ok. I will be grateful for every advice. Thanks in advance! Best regards!
Last updated: 2025-09-25

Post by trusty-squire on Strange problem with the ‘MC_SetPosition’ function ^{CODESYS Forge talk (Post)}
Here, it seems to me that we are getting completely off track with the observed problem. If questions clarifying the details of the installation are problematic, it's best to include those details in the original question then... I had already written this elsewhere. The program before being brought into machines was exhaustively tested in SW emulation and the problem did not occur. Testing the full program in emulation is entirely different from creating a simplified program to isolate the function causing problems in the real world. I would recommend trying it to isolate the issue. The drive and motor have been working fine for about 10 years. In replacing the machine control system, I opted for CoDeSys where before there was something else. But this is not the subject of the problem A simple "yes" is the correct answer to my question here... Anyways, you seem to be a very knowledgeable expert, good luck on your problem!
Last updated: 2025-01-18

Post by caprez95 on Deleting the trend recording history ^{CODESYS Forge talk (Post)}
Hallo Ich möchte eine laufende Trendaufzeichnung stoppen, den Inhalt löschen und Trend-Diagramm auf 0 zurücksetzen. Laut Codesys soll das mit dem folgenden Code möglich sein: You can insert an input element in the visualization which the operator can use to delete the previous value recording in the trend visualization at runtime. The curve displayed until then is removed and the display starts over. In the application (example: in the program PLC_PRG), implement the following code: itfTrendRecording : ITrendRecording; itfTrendStorageWriter : ITrendStorageWriter; itfTrendStorageWriter3 : ITrendStorageWriter3; sTrendRecordingName : STRING := 'TrendRecording'; itfTrendRecording := GlobalInstances.g_TrendRecordingManager.FindTrendRecording(ADR(sTrendRecordingName)); xClearHistoryTrend: BOOL; IF xClearHistoryTrend THEN itfTrendRecording := GlobalInstances.g_TrendRecordingManager.FindTrendRecording(ADR(sTrendRecordingName)); IF itfTrendRecording <> 0 THEN itfTrendStorageWriter := itfTrendRecording.GetTrendStorageWriter(); IF __QUERYINTERFACE(itfTrendStorageWriter, itfTrendStorageWriter3) THEN itfTrendStorageWriter3.ClearHistory(); END_IF END_IF In the visualization of the trend recording, add a button for deleting the previous curve. Configure its Toggle property with the variable PLC_PRG.xClearHistoryTrend. ⇒ When xClearHistoryTrend is set to TRUE, the previously recorded curve is deleted. The recording immediately starts again. Dies löscht auch die Daten vom Trend, aber das Diagramm wird nicht auf 0 zurückgesetzt, sondern läuft einfach da weiter wo man gestoppt hat. Braucht es für den Diagramm-Reset noch einen zusätzlichen Befehl? Gruss
Last updated: 2024-06-11

Post by timvh on Visuutils FbOpenDialog(Extended) not open Dialog from POUs ^{CODESYS Forge talk (Post)}
I had a similar situation recently where this didn't work, but read to the end to see the solution. The reason is that CODESYS only downloads visualisations (dialogs) if they are part of the project or linked to the project. In your case the dialog is not loaded onto the controller. But the solution is pretty simple: Double click on the Visualization Manager in your application. Select the Tab "Visualizations". Here you can see that your dialog is not "checked". Do this manually and load your project on the controller. Then your code should be able to open the dialog, because now it exists on the controller.
Last updated: 2024-09-28

Post by r-niedermayer on OPC UA subscriber not operational ^{CODESYS Forge talk (Post)}
Hi. As far as projects in "old version"s are concerned, these can be upgraded to newer versions at any time. To do this, the device must be updated accordingly and the copilers and library versions must be adapted. You can find instructions on how to proceed in the online help/FAQ: https://content.helpme-codesys.com/en/CODESYS%20Development%20System/_cds_changing_compiler_version.html https://content.helpme-codesys.com/en/CODESYS%20Development%20System/_cds_cmd_update_device.html See also 4.3.22.4 "How to open an Example Project" within the following pdf for more details on the single steps: https://forge.codesys.com/lib/counit/tickets/_discuss/thread/3e991befbc/ca97/attachment/Public%20FAQ-v13-20240610_075228.pdf Regaring your OPCUA connection state always showing just "DISABLED", without knowing both sides of the assembly in detail, one can only approach the problem theoretically. We can give a chekclist on how to proceed: Fist, please recheck the communication settings in the OPC UA connection function block to ensure that the server URL, endpoint URL, and other settings are correct and match the configuration of the OPC UA server. Verify that the OPC UA server is running and accessible. -You can try to connect to the OPC UA server using a separate client, such as UAExpert, to ensure that the issue is not related to the OPC UA server itself. Test the security settings in the OPC UA connection function block to ensure that the correct security policy and certificate are selected. If you are using a dynamic connection to the OPC UA server, probe that the connection settings are correctly configured and that the OPC UA client is able to establish a connection to the OPC UA server. Also, please loock into the log files for any errors related to the OPC UA connection function block, these should be listet there. The log files may also provide additional information about the issue and help you to further troubleshoot the problem. FYI - Please see https://content.helpme-codesys.com/en/CODESYS%20Communication/_cds_obj_data_source_communication_opc_ua_server.html: Her you can finde the Communication settings via OPC UA Server -> layout Browse Live Server: The client connects to the server and detects the existing variables and types. From Information Model The client reads the data structure (layout) of the OPC UA Server from the information model set here and as a result receives the information about available variables and types. A connection to the server is not required. The list contains the information models installed in the OPC UA Information Model Repository. "Read Connection" Settings from IEC Variable (option set): - The connection settings used by the device are not read here from the dialog, but at runtime from the IEC variable specified here. - For this possibility, please see the Using a Dynamic Connection to an OPC UA Server (https://content.helpme-codesys.com/en/CODESYS%20Communication/_comm_use_dynamic_opc_ua_server_comm_settings.html) The settings for the communication of a Client-data source to an OPC UA Server can also be dynamically configured from the IEC code and can also be changed at runtime. For such a purpose, a structure is available in the DatasourceOpcUAServer library (For a description of the OPC UA Server, there is one included in the standard installation of CODESYS, https://content.helpme-codesys.com/en/CODESYS%20Communication/_cds_encrypt_communication_data_sources_opc_ua_client.html)
Last updated: 2024-11-04

Post by snhatton on OpC UA server on Raspberry Pi 64 SL runtime ^{CODESYS Forge talk (Post)}
Good afternoon, After changing the security settings to: CommunicationPolicy: POLICY_BASICSHA256SHA256 CommunicationMode: ALL Activation: Activated UserAuthentication: ENABLED Then generate a new certificate on the device for the OPC-UA server from Security Agent->Device->OPC UA Server. Restart the runtime using tools->Update Raspberry Pi->Stop->Start for the changes to take effect. It may take a minute for the runtime to start. Initiate the connection from the UA server side. You should see a pop-up asking you to trust the certificate. Click on the button 'Trust Server Certificate'. Next, you should see a certificate in the quarantined folder of the security agent in CODESYS. Click and drag this from quarantined to trusted and then try connecting from UA expert to the device. These steps worked for me and my setup and I hope they can help you!
Last updated: 2023-12-11

Post by ppix on Establishing TLS Connection with MQTT Broker using MQTT Client SL Package ^{CODESYS Forge talk (Post)}
I’m currently working on establishing a TLS connection with an MQTT broker using the MQTT Client SL package in CODESYS. While I’ve successfully established communication with the broker without TLS, I'm encountering issues when trying to enable TLS. In the 'MQTT Explorer' application, I can easily upload the server certificate (.crt), client certificate (.crt), and client key (.key). However, in CODESYS, I can’t find a way to upload my client key (.key file). Here's a summary of my current setup: Certificates: I have uploaded both the client and server certificates to the certificate store under the 'Trusted Certificates' folder in the security screen. TLS Context Initialization: Despite setting the _sCommonName as the name of my client certificate, a new self-signed certificate is created and placed within the device’s certificates. I then need to manually move this certificate to the trusted certificates folder. This results in three certificates in my trusted certs folder: client cert, server cert, and the newly created cert. _ciDefaultCertInfo : MQTT.NBS.CERT_INFO := (psInfo := ADR(_sCommonName), udiSize := TO_UDINT(LEN(_sCommonName))); // CN of the certificate (common name) _sCipherList : MQTT.NBS.CIPHER_LIST := STRUCT(psList := ADR('HIGH'), udiSize := 4); // Cipher string see https://www.openssl.org/docs/man1.1.1/man1/ciphers.html _tlsContext : MQTT.NBS.TLSContext := ( sUseCaseName := _sCommonName, // A certificate is stored in the certificate store with the use case name. You can choose any name. Here we use the common name. ePurpose := MQTT.NBS.PURPOSE.CLIENT_SIDE, // For client certificates set this to NBS.PURPOSE.CLIENT_SIDE sTLSVersion := '1.3', // The TLS version sCipherList := _sCipherList, // Set the cipher list sHostname := sHostname, // The hostname of the broker udiVerificationMode := 2, // 2 => Active Peer verification ciCertInfo := _ciDefaultCertInfo, // Set the cert info itfCertVerifer := 0); // 0 => No Verifier mqttClient : MQTT.MQTTClient := (xUseTLS:=TRUE, itfTLSContext := _tlsContext, itfAsyncProperty := _asyncProperty); Additional Details: In the client FB, I’ve set uiPort:= 8883, xUseTLS:= TRUE, and configured itfTLSContext as mentioned above. The certificates are encrypted with SHA256RSA. sHostname is the IP address of my broker. I’ve attached a copy of the client FB, which shows straight lines where variables are assigned and boxes where they are not. I am currently trying this on the only 2 compatible versions of COSDESYS with my controller (V3.5.15.20 and V3.5.18.40) My Question: How do I correctly set up this mTLS connection? What might I be missing? Any guidance or suggestions would be greatly appreciated, especially considering I’ve already successfully established a non-TLS connection with the same broker. Thank you in advance for your help!
Last updated: 2024-06-19

Post by jonasz on Device diagnosis ( EtherCAT IO card ) ^{CODESYS Forge talk (Post)}
Hi, I'll link to the topic not wanting to start a new one. In the application I am building, I wanted to use the diagnostics described in the CAA Device Diagnosis library. In principle, everything is ok, except for the elements related to ModbusTCP. Despite the fact that ModbusTCP is taken into account in the documentation, it is not recognised via the interfaces. FUNCTION_BLOCK NET_HW_DIAG VAR_INPUT END_VAR VAR_OUTPUT END_VAR VAR (* Referencja do struktury z danymi dla HMI ASTRAADA.*) Visu: REFERENCE TO VISU; (* Wskaźnik na mastera EtherCAT.*) pEtherCATMaster : POINTER TO IoDrvEtherCAT; (* Wskaźnik na slave EtherCAT.*) pEtherCATSlave : POINTER TO EtcSlave; (* Interfejs dla węzła w drzewie urządzeń.*) _itfNode: DED.INode; (* Ogólny interfejs magistrali. Zapewnia podstawowe informacje o magistrali polowej.*) _itfBus: DED.IBus; (* Interfejs urządzenia. Zapewnia rozszerzone informacje o urządzeniu (magistralowym).*) _itfDevice2: DED.IDevice2; (* Ogólny interfejs magistrali. Zapewnia podstawowe informacje o magistrali polowej.*) _itfStack: DED.IStack; (* Numer węzła w drzewie urządzeń.*) uiNodes: UINT; (* Operator jest rozszerzeniem normy IEC 61131-3. W czasie wykonywania operator wykonuje konwersję typu odwołania do interfejsu na inny typ. Operator zwraca wynik BOOL. Wartość TRUE oznacza, że CODESYS pomyślnie wykonał konwersję. *) xQueryResultBus: BOOL; xQueryResultDevice2: BOOL; xQueryResultStack: BOOL; (* Struktura danych dotyczących węzłów w drzewie urządzeń.*) NetHwDiag: NW_HW_STAT; ModbusTcpClientDeviceInfo: IoDrvModbusTCP.DED.DEVICE_INFO; ModbusTcpClientDeviceState: IoDrvModbusTCP.DED.DEVICE_STATE; ModbusTcpDeviceInfo: IoDrvModbusTCP.DED.DEVICE_INFO; ModbusTcpDeviceState: IoDrvModbusTCP.DED.DEVICE_STATE; END_VAR (* Pobranie wskaźników dla pierwszego mastera i pierwszego slave w sieci EtherCAT.*) pEtherCATMaster := g_pFirstMaster; pEtherCATSlave := pEtherCATMaster^.FirstSlave; (* Diagnostyka sieci EtherCAT.*) pEtherCATMaster := g_pFirstMaster; pEtherCATSlave := pEtherCATMaster^.FirstSlave; NetHwDiag.xConfigFinished := pEtherCATMaster^.xConfigFinished; NetHwDiag.xDistributedClockInSync := pEtherCATMaster^.xDistributedClockInSync; NetHwDiag.xError := pEtherCATMaster^.xError; NetHwDiag.xSyncInWindow := pEtherCATMaster^.xSyncInWindow; NetHwDiag.sLastMessage := pEtherCATMaster^.LastMessage; NetHwDiag.LastError := pEtherCATMaster^.LastError; (* Diagnostyka drzewa urządzeń.*) uiNodes := 0; _itfNode := DED.GetRoot(); REPEAT NetHwDiag.asDeviceName[uiNodes] := DED.GetDeviceNameString(itfNode := _itfNode); xQueryResultBus := __QUERYINTERFACE(_itfNode,_itfBus); IF xQueryResultBus THEN _itfBus.GetBusInfo(buiInfo := NetHwDiag.aBusInfo[uiNodes]); NetHwDiag.aBusState[uiNodes] := _itfBus.GetBusState(); END_IF xQueryResultDevice2 := __QUERYINTERFACE(_itfNode,_itfDevice2); IF xQueryResultDevice2 THEN _itfDevice2.GetDeviceInfo(deiInfo := NetHwDiag.aDeviceInfo[uiNodes]); NetHwDiag.aDeviceState[uiNodes] := _itfDevice2.GetDeviceState(); IF pEtherCATSlave <>0 THEN pEtherCATSlave^(); IF pEtherCATSlave^.SlaveAddr = NetHwDiag.aDeviceInfo[uiNodes].idSystem THEN NetHwDiag.aAlStatus[uiNodes] := pEtherCATSlave^.ALStatus; pEtherCATSlave := pEtherCATSlave^.NextInstance; END_IF END_IF ELSE xQueryResultStack := __QUERYINTERFACE(_itfNode,_itfStack); IF xQueryResultStack THEN _itfStack.GetDeviceInfo(deiInfo := NetHwDiag.aDeviceInfo[uiNodes]); NetHwDiag.aDeviceState[uiNodes] := _itfStack.GetDeviceState(); END_IF END_IF uiNodes := uiNodes + 1; _itfNode := DED.GetNextNode(_itfNode); UNTIL _itfNode = 0 END_REPEAT (* Diagnostyka Modbus.*) Modbus_TCP_Client.GetDeviceInfo(deiInfo := ModbusTcpClientDeviceInfo); ModbusTcpClientDeviceState := Modbus_TCP_Client.GetDeviceState(); PAC_3200T.GetDeviceInfo(deiInfo := ModbusTcpDeviceInfo); ModbusTcpDeviceState := PAC_3200T.GetDeviceState(); Of course, you can take the easy way out and refer directly to the devices, but I wanted a reusable component. Any constructive help is very welcome Best regards Jonasz
Last updated: 2025-07-15

Post by eschwellinger on Visu Plugin 4.5.0.0, "Visu, Webvisu: Improve diagnosis" ^{CODESYS Forge talk (Post)}
that way: http://deviiceIP:8080/webvisu.htm?CFG_DebugOnlyDiagnosisDisplay=true or http://deviiceIP:8080/webvisu.htm?CFG_DebugOnlyDiagnosisDisplay=true&CFG_DebugOnlyInputReactionOnUp=true or http://deviiceIP:8080/webvisu.htm?CFG_DebugOnlyDiagnosisDisplay=true&CFG_DebugOnlyInputReactionOnUp=true&CFG_DebugOnlyInputReactionExplCoord=true
Last updated: 2024-01-09

Post by malie on Visuutils FbOpenDialog(Extended) not open Dialog from POUs ^{CODESYS Forge talk (Post)}
Hello, how can i open a dialog from POUs and not from Devices via FbOpenDialog. In an project would it work when i place it in the application, but in a library? Example attached. Thanks in advance Max Update: - append a screenshot
Last updated: 2024-08-20

Post by ahmedbadawi10 on Codesys Trend Problem ^{CODESYS Forge talk (Post)}
I have control win v3 with simulation and a small program with function to convert analog values to percentages, I need to show these percentages in a trend chart, but nothing is shown in the trend as you see in snips attached! thanks in advance
Last updated: 2025-09-16

Post by timvh on Fix compiler version in SP18+ ^{CODESYS Forge talk (Post)}
Their is quite a detailed explanation in the help: https://content.helpme-codesys.com/en/CODESYS%20Development%20System/_cds_codesys_modularization.html
Last updated: 2024-07-22

Post by pierre on difference between stub file and source file in scriptengine ^{CODESYS Forge talk (Post)}
same situation for DeviceID. In the stubfile this is Deviceid
Last updated: 2024-09-23

Post by jeffersonhui on SFC Reset Codesys 2.3? ^{CODESYS Forge talk (Post)}
Hi, Is there a way to reset an SFC in Codesys 2.3, similar to using the "SFCReset" flag in Codesys 3.5? Thanks
Last updated: 2024-11-20

Post by ph0010421 on OSCAT Scale_r function not working in LD 4.60 works in LAD2 on 3.5.21sp3 ^{CODESYS Forge talk (Post)}
Is that rung definitely being executed? Is the POU called?
Last updated: 2025-10-23

Post by eschwellinger on search runtime 4.9.0.0 for pi 3 ^{CODESYS Forge talk (Post)}
runtime could always be in latest version. just keep everything in CODESYS stable and deploy the latest runtime. This will work.
Last updated: 2025-10-25

Post by paro on Client Independent Visualization Switching ^{CODESYS Forge talk (Post)}
Hi, can you please provide a new example for the topic at CODESYS "Client Independent Visualization Switching" https://forge.codesys.com/prj/codesys-example/client-independ/home/Home/ Since a few versions, the functions used cause warning messages. Examples for the use of all function blocks from the Visu Utils would generally be very helpful! Several people have put together an example here: https://forum-de.codesys.com//download/file.php?id=2240 BR Patrick
Last updated: 2023-12-20

Post by thomasrohnerch on Color Change for Symbols not working ^{CODESYS Forge talk (Post)}
I have some Symbols from the Visualization Toolbox on my Target Visu on the Computer. I tried many Symbols, mainly Arrows. I'm able to control the visibility with condition e.g. "GVL.actual_testvalues.speed <= 0" But I can't do "Toggle color" with boolean GVL.b_toggle_color. Neither "TRUE" nor "FALSE" does change anything. Is this a known issue? I'm using CODESYS V3.5 SP19 Patch 5 + (64-bit). See attached file with more Version-Info. I'm currently using Style 6, Gradient axial 2, 3.5.12.0. I had the same issue with Default 3.5.16.0.
Last updated: 2024-02-08

Post by pradeepradha on Update Raspberry Pi option is missing under Tools menu ^{CODESYS Forge talk (Post)}
Hello, the option to update Rasberry Pi from under the Tools menu is missing in my installation. Currently I have the build 3.15.19.50, along with the Pi package 4.11.0.0. But the same problem is observed even with the latest build and Pi packages. I have tried clean install with both the versions but cannot solve the issue. I never faced this on Windows 10, but now the new PCs are with Windows 11 - this is the only difference. How can I solve this problem?
Last updated: 2024-09-02

Post by rmaas on Webvisu cliënt responsiveness ^{CODESYS Forge talk (Post)}
hi, Does anyone know how to optimise the responisiveness of the web visualisation? When i open the webvisu on my laptop it is very responsive, no noticable lag. But when i open it on the HMI (web client) at the customer site there is a lag of +-500 when opening popups etc. The hmi used is: Phoenix Contact WP 6156-WHPS full hd Arm® Cortex®-A53, 1.6 GHz qt web browser The clients performance seems to be the problem, what can i do in my project to decrease the load for the client?
Last updated: 2024-09-28

Post by martincapd on EWON ^{CODESYS Forge talk (Post)}
I have the same problem in that I can connect to the eWon and ping the controller IP Address, however I cant connect through CodeSys. I'm using Gateway-1 which is configured to use "IP-Address: localhost" and "Port: 1217". Rather than scanning the network for devices, I enter the IP Address of the device, codesys returns a "No Device is repsonding..." message. See attached. I'm wondering if the IP-Address used Gateway-1 should be "localhost" or the WAN/LAN IP of the eWon? Thanks for the help MC
Last updated: 2024-02-21

Post by timvh on Modbus TCP & RTU with Control for Linux SL ^{CODESYS Forge talk (Post)}
RS485 doesn't seem very logical to use in VPLC's in my opinion. I also don't know if this is supported.... But for TCP/IP, I think you still need to configure the Nic settings. See the attached png. In my case enp6s0. When changing this setting, restart the VPLC. What is really nice, is that you don't have to configure the IP address setting in Linux. By setting the Nic to a certain IP address in the CODESYS instance configuration, this is automatically done for you. I only tested this with EtherCAT, but I guess this works the same for Modbus TCP/IP.
Last updated: 2024-10-23

Post by rickmotion on Opening and saving files with fileOpenSave dialog ^{CODESYS Forge talk (Post)}
I have a customer that types in machine programs in a text file for machines and lets the machine execute it. In the old situation they can open and edit these files in a winform application. Now I want to move this to codesys. What I need is a simple way to open, close, save, edit the machine file in codesys visualisation. I want to use the fileOpenSave dialog. But don't understand how it works. I have the file transfer example and some other examples. But it is hard to figure out how the part with the file dialog works so that you can select a folder or file. Does someone know how that works?
Last updated: 2025-03-26

Sort by relevance or date