Post by siscu on Raspberry i2c master device ^{CODESYS Forge talk (Post)}
I want to implement an extended I2C master for Raspberry Pi Control. I was hoping for it to be as easy as creating a library with a FB that extends i2cMaster and associating it with a device following the forge drivers documentation, but I haven't managed to make it work as the driver behaves only as an i2c slave. I'm thinking this is because the forge forum only talks about extending i2c, and the master portion is omitted since most users won't want to add a custom one. I'd like to know if I'm doing something wrong. Is it really possible to make an I2C master extension device? If so, are there public examples we can check out? Any info on this topic will be appreciated.
Last updated: 2024-10-16

Post by milan-svarny on ModbusFB.ClientSerial Problem with Reply Timeout ^{CODESYS Forge talk (Post)}
Hi All, I have problem with ModbusFB.ClientSerial. I'm using 4 different port for Modbus communication. After some time of running program ClientSerial stops to receive data to reply buffer and all request finish with Reply Timeout. The Device sent reply correctly,that it is visible on oscilloscope and it is possible to see that data( reply )are in the device. If the usbtty device is read over external app. then it is possible to see all data which were not taken by ModbusFB.ClientSerial. The stack does not overflow or something , program runs correctly forward and no exceptions or something. The main problem it is that when the error occur than it is not possible to reset port or something or maybe i'm doing it wrong way. please help me with this issue. Thank you for any help in advice Milan
Last updated: 2025-05-23

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 cdutz on Problems connecting to Codesys 4.9.0.0 runtime on my Wago PFC200 ^{CODESYS Forge talk (Post)}
Hi all. I am currently struggling to get my Wago PFC200 running the Codesys Runtime in version 4.9.0.0 working. I am using Codesys V3.5SP19. I updated the PFC200 to the firmware version 04.01.10(23) after having tried the latest version (04.03.03(25) from Wago and not being able to start the runtime. After reading version 23 was needed, I changed to that and at least was able to have it start the codesys runtime. I also installed the "Codesys Control for PFC200 SL 4.9.0.0" plugin for Codesys to install the Codesys runtime in version 4.9.0.0 as well as update the Gateway on the device. While I seem to be able to connect to the gateway on the PLC (the dot is green) and when doing a scan, I do now find my PFC200, which is a huge improvement to before, where with firmware version 25 it just failed to start the runtime and I never found any device when doing a scan. Unfortunately I don't seem to be able to connect to the PLC in codesys. I logged in via SSH and changed the password and I can see that this password is correct as the stuff in the Codesys PFC200 tools tab only works if I use my changed password. And I used those credentials to update the installed Runtime version, which the log claimed to have worked fine. Now whenever I try to connect to the device found in the scan, I get a authentication pop-up with empy device name, device address: 000A. As User I use "root" and as password the password that I changed it to. As a response I just get "Ungültige Benutzerauthentifizierung auf dem Gerät" (Eng. probably something like "Invalid user authentication on the device". What could I be doing wrong? Admittedly I'm a bit lost here :-/ Chris
Last updated: 2023-08-26

Post by ernesto881124 on ernesto881124 ^{CODESYS Forge talk (Post)}
Hello good morning everyone I would like to ask a question, is it possible to directly connect a device that only contains modbus RTU communication through an R-45 connector, directly to the PC? Or would you need an intermediate device to achieve communication? It would be of great help to me because I cannot achieve communication between the Codesys simulator plc and a Fuji Frenic mini VFD, please help me if anyone has had the same experience. Thank you so much
Last updated: 2023-09-13

Post by timvh on ernesto881124 ^{CODESYS Forge talk (Post)}
You will need a USB to RS485 converter to connect the PC to the Modbus RTU Slave Device. In Windows this converter will be recognized as Serial COM poort (e.g. COM2, or COM3, see the windows device manager to find this out). Select this port in your CODESYS application. On the PC you need to use the CODESYS Control Win (SoftPLC) to run your application. It will not work in simulation mode, because then the Modbus Communication will not be activated.
Last updated: 2023-09-14

Post by janderson on Ethercat scan for devices not picking up EL7041 as a softmotion axis ^{CODESYS Forge talk (Post)}
it appears that the different revisions have different PDOs. I am currently trying to use the rev25. I have tried to use the rev24 (the device repository entry not from 'scan for devices') and i keep getting 'invalid output mapping' or 'invalid input mapping' in the ethercat log. I cant even get the bus to run from the device description that comes from 'scan for devices'...
Last updated: 2023-09-18

Post by janderson on Ethercat scan for devices not picking up EL7041 as a softmotion axis ^{CODESYS Forge talk (Post)}
it appears that the different revisions have different PDOs. I am currently trying to use the rev25. I have tried to use the rev24 (the device repository entry not from 'scan for devices') and i keep getting 'invalid output mapping' or 'invalid input mapping' in the ethercat log. I cant even get the bus to run from the device description that comes from 'scan for devices'...
Last updated: 2023-09-18

Post by naps on Welchen I-Port benötige ich? ^{CODESYS Forge talk (Post)}
Hallo, ich versuche eine 750-653(konfiguriert per iocheck) über die Wago Modbus Lib einzusetzen. Ich scheitere im moment an dem Korrekten I-Port. Ich habe es mit 75x_653 und IoConfig_Globals.75x653 versucht, jedoch bekomme ich folgenden fehler: ------ Übersetzungslauf gestartet: Applikation: Device.Application ------- Code typisieren... Code erzeugen... [FEHLER] Unbenannt7: POU_1 Device: SPS-Logik: Application: C0032: Typ 'DED.CAADiagDeviceDefault(caa device diagnosis, 3.5.20.0 (caa technical workgroup))' kann nicht in Typ 'WagoTypesCom.I_WagoSysComBase(wagotypescom, 1.6.2.3 (wago))' konvertiert werden Übersetzung abgeschlossen -- 1 Fehler, 0 Warnungen : Kein Download möglich Wie kann ich den die Karte benutzen?
Last updated: 2024-10-01

Post by imdatatas on Remote to PLC device in City-B from City-A ^{CODESYS Forge talk (Post)}
Hello, In an example scenario like below figure, can the developer in City-A connect to the device in City-B remotely using only "Codesys Automation Server" and "Edge Gateway" with the following structure? If no, what should be done with Automation Server for this remote connection requirement? If yes, how should it be configured for this remote connection requirement? Thank you in advance for your answers. Regards, Imdat
Last updated: 2025-02-04

Post by atone on Change IO-Link Device Interface connected to a Profinet-Slave at Runtime ^{CODESYS Forge talk (Post)}
I need to be able to update (change) the interface of an IO-Link device at runtime. The reason is the connected sensor can be selected at runtime, and some sensors we use have a 2 byte IN interface, others have a 4 byte IN interface, others 16 byte IN, others 16 byte IN/OUT (see attached screenshot). Is it possible at all? When yes, which function should I use? Thank you!
Last updated: 2025-03-18

Post by kuegerls on OpC UA server on Raspberry Pi MC SL - Certificate Issue ^{CODESYS Forge talk (Post)}
Hello, I have set up an OPC UA server following several guides, including this one: https://revolutionpi.com/documentation/tutorials/opc-ua-codesys-nodered/. The license for the runtime is installed on the device. However, I am unable to create a certificate for the OPC UA server in the security screen. I always get the error message: "The certificate has not been created by the device." Does anyone have an idea what might be causing this issue? Any help would be greatly appreciated! Thanks in advance! Best regards, Stefan
Last updated: 2025-04-02

Post by glutenaron on Safety drive EL6900 and mitsubishi ^{CODESYS Forge talk (Post)}
Hi, Im wokring to get my servo mitsubishi mr-j5-g40-rnj1 working with my safety drive. I have as you can se in the picture Ek1100 koppler and EL6900 as safety plc. My questien is how do i connect the safety_drive to the SM3_Drive_ETC_Mitsubishi_MelServo_J5_Axis1 down below? I get the error ((Logical I/Os]: The logical device 'Safety_Drive' is not mapped to any physical device.)) but how do i map this? regard
Last updated: 2025-05-13

Post by yannickasselin on Dynamically enabling/disabling Modbus slave devices in runtime (performance issue with timeouts) ^{CODESYS Forge talk (Post)}
I would definitely try using the "Reconfigure" function block from "CAA Device Diagnosis@ library. https://content.helpme-codesys.com/en/libs/CAA%20Device%20Diagnosis/3.5.17.0/CAA-Device-Diagnosis/Function-Blocks/Reconfigure/Reconfigure.html#:~:text=This%20function%20block%20reads%20and,take%20effect. Although I have not tried it with Modbus, I had great success with EtherNet/IP, Profinet and EtherCAT. You can also have a look at the other functions in this library. There are useful functions to help iterate through all the nodes under a master node.
Last updated: 2025-08-12

Post by timvh on How to correctly create a device descriptor (.devdesc.xml) for a custom Linux ARM64 PLC in CODESYS 3.5.21.20? ^{CODESYS Forge talk (Post)}
If you are a vendor of controllers and want to have your own CODESYS Runtime on your device, then you need to contact the CODESYS Sales team and ask for the runtime Toolkit. For resellers of CODESYS devices, this can be interesting. If it is only for a few devices, then why not just take the standard runtime?
Last updated: 2025-10-07

Post by hermsen on Control Runtime Toolkit ^{CODESYS Forge talk (Post)}
Hi, there is a plethora of hardware available for it to be succesful on. In theory every ARM32/64 or x86/64 device is a potential target. Next to this there are embedded device platforms for which specific toolchains are available. A good starting for manufactureres of CODESYS capable devices is available here: https://www.codesys.com/the-system/codesys-inside.html. That should give you a good reference point.
Last updated: 2023-12-31

Post by takashi on CODESYSControlWinCE Crash ^{CODESYS Forge talk (Post)}
Hey all CODESYS-experts. I'm at a customer site, and we hade a power-failure and one of the devices apparently runs codesys and has crashed. It's an old device (out of warranty) that is bought many years ago. Now this device doesn't seem to boot. Any idea what to do in this case? We have access to the drive so we have access to the files. See screenshots.
Last updated: 2024-01-23

Post by marlutec on [ERROR] The PLCopenXML import is not possible because Device not found. Type: 89, Id: 0000 0005, Version: 3.5.10.0 ^{CODESYS Forge talk (Post)}
Hello every one. Now i'm instaling a Weintek cMT2108x2(v2) with IR-ETN40R. When I start to import the archive content the code of I/O remote IR-ETN40R, ocurred this error. [ERROR] The PLCopenXML import is not possible because Device not found. Type: 89, Id: 0000 0005, Version: 3.5.10.0 Can someone help me? Marcos Gentil, from Brazil.
Last updated: 2024-02-15

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 john-martin on Control SL Extension Package doubts ^{CODESYS Forge talk (Post)}
Hello everybody, I'm trying to understand the SL control extension package, more specifically, the external IODriver example, because C integration is very easy and I just made my first C component successfully. Ther External IODriver has no documentation and it's not clear how to proceed. Furthermore, there is no information on how to modify the device descriptor, which is necessary to import the device into the Codesys repository. Any advice ? Thank you in advance and best regards.
Last updated: 2024-02-28

Post by nano on Is there any support for I2C on Raspberry Pi? ^{CODESYS Forge talk (Post)}
hello jdj this question can be answered well with a pretty good forge documentation: https://forge.codesys.com/drv/io-drivers/doc/Generic/ u r also able to create in codesys directly an iec-code by using the i2c-interface as driver using the codesys ide and st depending on the stepperdriver, used in yöur hat, its possible that an driver is already available in the device-repository. which mcp-device is used on the hat?
Last updated: 2024-03-01

Post by timvh on IFM CR711S Version Mismatch ^{CODESYS Forge talk (Post)}
You should ask IFM to provide you with the correct version of their controller packages. Then after you have installed this, you can select the correct version of the controller by right clicking on it in the device tree, update device, enable the option "Display all versions" and then select the version which matches your controller. Alternatively you can ask IFM to provide an update package which can update the runtime version on your controller to 3.2.0.0.
Last updated: 2024-03-05

Post by mp9876 on Device User Logon ^{CODESYS Forge talk (Post)}
Hi everyone, Had that problem before where I could not create another user but used the method just above and it worked great. My problem now is that I get this message when attempting to logon to the device: invalid user authentication on the target dev5, the new user created is pretty much a copy of the user 'Owner' except for the password. Any idea as to why I am always getting this "invalid user authetication on the target" message ? Using Codesys V3.5 SP19 Patch 6 + (64 bit) Regards
Last updated: 2024-03-16

Post by eschwellinger on License problem gateway ^{CODESYS Forge talk (Post)}
I just try to help. Anyway it is a big difference if a Store SL runtime or an oem plc and licence is used. These licenses need to be activated on plc side - so you have dependencies to the version (CODESYS and Runtime Version) Did you ever ask Epis out for this situation? They should know which license fit to their device. Even they should know if the device is capable for Softmotion and see the requiremnts in the CODESYS store: Runtime 4.9.0.0 - how should this work with Epis 3.5.16.x? Anyway refund is not a problem.
Last updated: 2024-04-26

Post by alez on CANOpen SDO to write VISIBLE STRING ^{CODESYS Forge talk (Post)}
Hello, I am experiencing difficulties in configuring a CANopen device by sending SDOs. In particular I am attempting to write an Object Dictionary that has VISIBLE STRING as the Data Type. When I try to configure the sending of an SDO from Codesys to configure this parameter I am not allowed to enter a string value. In my particular case I am trying to change the Manufacturer Device Name ( Index 0x1008 ). Could it be that Codesys doesn't manage these types of variables?
Last updated: 2024-04-29

Sort by relevance or date