Post by simotion on Multiple Ethercat masters on one IPC ^{CODESYS Forge talk (Post)}
Our IPC has multiple seperate ethernet ports. Is it possible to have two ethercat masters on the IPC (on two different ehternet ports off course)? If so, is there documentation available on this, or are there watchouts? Thanks
Last updated: 2024-01-12

Post by rafael on Wbm/runtime and visualization login ^{CODESYS Forge talk (Post)}
Solved, there is a configuration inside the WBM where I can disable this login option (config>ports config)
Last updated: 2024-06-25

Post by timvh on Modbus TCP & RTU with Control for Linux SL ^{CODESYS Forge talk (Post)}
It seems you have 2 network interfaces. Did you try eth1? Did you already configure the IP address for this interface in Linux? If yes, then maybe undo this. - or only set eth0 in the Nic configuration without anything else (so no IP address, because this is already set in Linux). For more information about the Nic settings, see (probably already read it?): https://content.helpme-codesys.com/en/CODESYS%20Control/_rtsl_obj_deploy_control_sl_configuration.html PS, if you only want to run CODESYS Control SL, you don't necessarily need the Virtual PLC variant. You could also install and run the CODESYS Control SL Runtime in the Host operating system. This way you should also be able to access the serial port and directly access all ethernet ports. Maybe this is easier?
Last updated: 2024-10-23

Post by eschwellinger on Raspberry PI4 Serial Port ^{CODESYS Forge talk (Post)}
no parameter seems ok but RS485 does only work with CODESYS if the send/receive is determined by hardware as I remember correct
Last updated: 2024-03-18

Post by eschwellinger on Raspberry PI4 Serial Port ^{CODESYS Forge talk (Post)}
no config file is ok, the feedback is: your hardware must support this send/receive switching
Last updated: 2024-03-19

Post by corriibme on Read Serial Number of PLC ^{CODESYS Forge talk (Post)}
I have recently used this example from @Brine, and it worked. Thanks
Last updated: 2024-05-21

Post by lsislsis on RPI Serial port connects with no errors but not data being transmitted or received ^{CODESYS Forge talk (Post)}
Is there any solution because we have the same problem with other hardware?
Last updated: 2024-09-30

Post by lsislsis on SIGABRT Error ^{CODESYS Forge talk (Post)}
After many tests i see that problem comes when serial communication established for modbus rtu. If the slave device not connected we don't see the exception. If the slave device connected at serial port then we have exception about 1 hour after startup and every 10 or 15 minutes. Any suggestion?
Last updated: 2024-11-08

Post by macieksz on PCIE isolated DIO card on Linux amd64 ^{CODESYS Forge talk (Post)}
Where I can find hardware compatibility list? I have Advantech PCIE-1758 card with 128 DIO isolted ports. Will it works with Codesys? Do You know any PCIe isolated DIO cards?
Last updated: 2024-01-23

Post by dhumphries on IO link on IFM AL133x only single digital input on a channel ^{CODESYS Forge talk (Post)}
Try changing the port mode to digital input for each port you want to have 2 inputs in the connection settings for the device. I've successfully used ports for inputs on an AL1920 this way, I think the procedure should be the same for an AL1332.
Last updated: 2023-12-30

Post by i-campbell on Not able to see input data coming from eip adapter on codesys ^{CODESYS Forge talk (Post)}
Hello, I think you can try to change the Connection from Multicast to Point to Point. Please also make sure your windows firewall is allowing the correct UDP ports inbound for ethernet IP. You might also need to increase the RPI, so it times out slower.
Last updated: 2024-03-07

Post by nano on Cant login to Rpi4 but can see it in codesys communications settings. ^{CODESYS Forge talk (Post)}
which ports in detail are configured. the search of the rts works via broadcast-messages, programming with tcp-port on p2p-connection woth port-hopping, handled by runtime after siccesfully handshake. look at this entry on forge https://forge.codesys.com/forge/talk/Runtime/thread/4078a2ed28/
Last updated: 2024-06-23

Post by paulg on RasPi CAA Serial example - unexpected behavior during debug ^{CODESYS Forge talk (Post)}
I've trimmed down the CAA Serial Codesys example to only listen on one port but, when stepping through the Case structure in debug mode, it jumps out of the structure during a specific point in every scan (I'll point it out below after describing the setup and listing the code). I'm using a Pi 4 Model B, and I have an Arduino Nano Every plugged in via USB which is streaming the following serial message at 1 Hz: Time since opening connection: 1 s Time since opening connection: 2 s ...and so on. The Pi shows the Nano at /dev/ttyACM0 so I edited CODESYSControl_User.cfg to read: Linux.Devicefile=/dev/ttyACM The code in my PLC_PRG is (ignore some of the comments, I hadn't deleted them out from the original example): PROGRAM PLC_PRG VAR xStartTest : BOOL:= TRUE; iState : INT; xTestDone : BOOL;(* True, when the test was done succesfully *) (* Settings to communicate with the COM Port *) aCom1Params : ARRAY [1..7] OF COM.PARAMETER; como1 : COM.Open; comc1 : COM.Close; comw1 : COM.Write; comr1 : COM.Read; //sWrite : STRING := 'Test String!'; sRead : STRING(25); szRead : CAA.SIZE; xCom1OpenError : BOOL; xCom1CloseError : BOOL; xCom1WriteError : BOOL; xCom1ReadError : BOOL; END_VAR //This example shows the communication of two COM Ports with each other. //The first one writes a string of characters, which is read by the second one. //After successful execution, the two COM Ports are closed and the test is done. IF xStartTest THEN CASE iState OF 0: //The parameters are set for the COM Port aCom1Params[1].udiParameterId := COM.CAA_Parameter_Constants.udiPort; aCom1Params[1].udiValue := 1; // the correct Port should be adapted aCom1Params[2].udiParameterId := COM.CAA_Parameter_Constants.udiBaudrate; aCom1Params[2].udiValue := 115200; aCom1Params[3].udiParameterId := COM.CAA_Parameter_Constants.udiParity; aCom1Params[3].udiValue := INT_TO_UDINT(COM.PARITY.NONE); aCom1Params[4].udiParameterId := COM.CAA_Parameter_Constants.udiStopBits; aCom1Params[4].udiValue := INT_TO_UDINT(COM.STOPBIT.ONESTOPBIT); aCom1Params[5].udiParameterId := COM.CAA_Parameter_Constants.udiTimeout; aCom1Params[5].udiValue := 0; aCom1Params[6].udiParameterId := COM.CAA_Parameter_Constants.udiByteSize; aCom1Params[6].udiValue := 8; aCom1Params[7].udiParameterId := COM.CAA_Parameter_Constants.udiBinary; aCom1Params[7].udiValue := 0; //The first Port is opened with the given parameters como1(xExecute := TRUE, usiListLength:=SIZEOF(aCom1Params)/SIZEOF(COM.PARAMETER),pParameterList:= ADR(aCom1Params)); IF como1.xError THEN xCom1OpenError := TRUE; iState := 1000; END_IF //After a successful opening, the next state is reached IF como1.xDone THEN iState := 15; END_IF 15: // the reading process is started comr1(xExecute := TRUE,hCom:= como1.hCom, pBuffer:= ADR(sRead), szBuffer:= SIZEOF(sRead)); IF comr1.xError THEN xCom1ReadError := TRUE; END_IF //After completion the size of the written bytes are saved IF comr1.xDone OR comr1.xError THEN szRead := comr1.szSize; iState := 20; END_IF 20: // If everything was successful the ports are closed and the handles are released comc1(xExecute := TRUE,hCom:= como1.hCom); IF comc1.xError THEN xCom1CloseError := TRUE; END_IF IF comc1.xDone OR comc1.xError THEN iState := 25; END_IF 25: // The first port is closed and the used handle released xTestDone := TRUE; xStartTest := FALSE; iState := 0; como1(xExecute := FALSE); comw1(xExecute := FALSE); comc1(xExecute := FALSE); ELSE iState := 0; END_CASE END_IF I realize as I write this that the .udiPort should be 0 and not 1, but that shouldn't be causing the issue I'm seeing. I'm forcing xStartTest:=TRUE every scan so that I can step into each line and observe what's happening. What I see is that the port parameters are set and the port is opened with no errors, but the code jumps out of the case structure to the last line every time it reaches (and I step into) the iState:=15 line (at the end of the iState:=0 block). So every scan cycle it goes through the block for iState=0 and jumps out at the same spot. I'm a little new to PLC programming so I may be misunderstanding the flow, but shouldn't this case structure keep moving down in the same scan? If it only handles one case per scan, why doesn't the value of iState persist? Thanks! Update: I restarted the Codesys control today and I was then able to see an error for como1.eError of "WRONG_PARAMETER". I tried doing some digging and another post made me think I should add another line to CODESYSControl_User.cfg, so I now have: [SysCom] Linux.Devicefile=/dev/ttyACM portnum := COM.SysCom.SYS_COMPORT1 So now when I set .udiPort to 1, I get "NO_ERROR" but I also don't read anything from the port (i.e. szRead = 0 always). If I try setting the port to 0 (which I'm confused about, because I added a COMPORT1 line but the device shows on the Pi as ACM0), I get the "WRONG_PARAMETER" error again. Is there an easier way to troubleshoot the Pi and view what ports the Codesys runtime is actually able to see while the Pi is running?
Last updated: 2024-06-06

Post by eschwellinger on PCAN serial "No CAN driver found" ^{CODESYS Forge talk (Post)}
which system are you using on the target system? If this is Linux this is different - in compare to use it on Control Win
Last updated: 2023-09-20

Post by thewizard8 on Raspberry PI4 Serial Port ^{CODESYS Forge talk (Post)}
Hi eschwellinger, Thanks for replying, but I'm not shure if I got it right. Do you mean that I have bad configuration on my CODESYS config file? Or in my project? Thanks in advance!
Last updated: 2024-03-19

Post by thewizard8 on Raspberry PI4 Serial Port ^{CODESYS Forge talk (Post)}
Hi thanks once again, Yes it supports because using python scripting I'm able to send data from the rasberry raspberry and receive it on my pc and vice versa (Image attached). But when using the CoDeSyS I just got red flags. Any light on this problem?
Last updated: 2024-03-19

Post by eschwellinger on CODESYS Control Raspberry Pi mit Servotreiber T6 von StepperOnline ^{CODESYS Forge talk (Post)}
Ist das RS232 oder RS485? Bei RS485 muss der Adaper also dein USB/Serial die Senderichtung in Hardware machen und das unterstützen. Abschlusswiederstände?
Last updated: 2024-06-01

Post by maldus512 on How to adapt Codesys Control SL to custom board ^{CODESYS Forge talk (Post)}
Hello everyone, I have been given the task to develop I/O drivers for a custom made, Linux based board to allow for Codesys applications to run and control the hardware. I have successfully installed Codesys Control SL for ARM/Linux and tested it with a simple demo application. Now I should start interfacing the runtime to the actual hardware; I should be able to interact with 2 RS485 serial ports, a few GPIOs and an I2C port, all of which already have the corresponding /dev/ interface in the Linux system. I am having trouble understanding how it should be approached. I have found sporadic references that fail to lead to a really comprehensive documentation. For example: The store page (https://store.codesys.com/en/codesys-control-for-linux-arm-sl-1.html#options) mentions a "runtime package" that should allow "Integration of existing C code" and "Usage of local I/Os", which seems exactly what I need to interact with custom peripherals. I have found no further reference to Codesys-C interpop. The Codesys Help page for the runtime package has a page on the "Development of Drivers" (https://content.helpme-codesys.com/en/CODESYS%20Control/rtsllinuxrbpdriverdevelopment.html) that suggests to either "Implement a function block" or "Implement I/O drivers". Those in turn lead to this page (https://forge.codesys.com/drv/io-drivers/doc/Generic/) which describes briefly an XML schema to describe new devices; unfortunately, it doesn't mention what to do with such a description (i.e. how does the runtime know about it) or how it is in any way connected to the actual hardware. Could anyone give me some pointers? I should also mention I have no prior experience with Codesys, so maybe I'm missing an obvious answer.
Last updated: 2024-08-09

Post by warrumungi on Beckhoff EL6652-0010 with Codesys ^{CODESYS Forge talk (Post)}
Hi Has anyone successfully used a Beckhoff EL6652-0010 Ethernet/IP slave terminal through an EK1101 EtherCAT coupler, or similar, and been able to set it up through Codesys? It seems there is no driver for it, and it can't be done? The only option would be to use the Ethernet/IP capability of the controller directly with one of its ethernet ports and a Codesys Ethernet/IP adapter + module and routing it through EtherCAT by tunnelling it through via an EL6614 switchport? Any advice would be appreciated. Billy.
Last updated: 2024-01-15

Post by nano on Issues with Modbus Slave with Raspberry Pi ^{CODESYS Forge talk (Post)}
in the codesyscontrol.cfg or codesyscontrol_user.cfg you have to declare whoch comport-ports from runtime are used. please tell us how the comport is called in linux an post the codesyscontrol.cfg files also write down here, which parameters are used in the python-script and what is parameteized in the modbus-master-comport of your codesys-application. mostly the errors occurs in ine of these areas
Last updated: 2024-07-11

Post by nicopolux on Profinet RPC-call error ^{CODESYS Forge talk (Post)}
Hello everyone Since I have installed Codesys 3.5.20sp2 I cannot get the profinet features working again. Now I get RPC Blocked during device scan (see attached file) and when online I get RPC-call error (see attached file). I run Codesys on the last version of Windows 11, Profinet ports have been added to Firewall rules, and even with disabled Firewall I get same result I really never seen that before Same result using another PC I already spent 2 days to find the issu without any success, I would appreciate some help, thank you! Nico
Last updated: 2024-08-22

Post by kevinl on RevPi Connect RS485 ^{CODESYS Forge talk (Post)}
I figured this out on my own with this logic: usually the Serial port on a Raspberry pi is on /dev/ttyUSB0 then you need to set linux.DeviceFile=/dev/ttyUSB in codesys you then must set com port to 1 so i assumed codesys subtracts 1 from the number and adds this to the filename... (in code it would look like this: var comPort : byte := '1'; linuxDevice : string := '/dev/ttyUSB'; filename : string; end_var filename := concat(linuxDevice, (to_string(comPort-1)); filaname then is /dev/ttyUSB0 RevPi uses ttyRS485 as Serial port so you must remove the last number from the name and set the com port to this number +1 i hope this is understandable ;-)
Last updated: 2023-12-11

Post by gatto on Modbus tcp - channel ^{CODESYS Forge talk (Post)}
Hi can you give more details? Are you talking about a danfoss? wich model? Can post the configuration of channel' I used, on the past, serial modbus with danfoss fc280 I remember ((id x 10)-1) I remember that you couldn't use continuous reading/writing of the directors but you had to use them one at a time. it seemed that reading empty registers (caused by x10) was not accepted by danfoss. So I had created a scan that used just one register, then the next etc etc with a timed interval. But this was for the serial, I don't know if it's the same thing with ethernet. I currently use Ethernet TCP/IP interface with FC280.
Last updated: 2024-06-13

Post by wbj0t on Global variable access by Programms and Modbus Devices (attach device to bus) ^{CODESYS Forge talk (Post)}
Hi everyone. I use Raspberry Pi 4, one core codesys SL. I have a question about global variable access via programm when I glued the same variable to MODBUS SERIAL/TCP DEVICE holding register. So, the question: what behavior of this modifying? When I set "Always update variables (in bus cycle)" and set some task as bus for the Device, then in another task I cant change this varible (can, but immediatly the old value setted again). But the same things works with MODBUS SLAVE: again "Always update..." and master attached to some task, then I change variable in another task and all works. I cant set up my variables from retains file at PrepareStart event because of this behavior with MODBUS SERIAL/TCP DEVICE. Thanks, wbj0t.
Last updated: 2024-07-18

Post by jp23 on Unable to Connect to Modbus RTU Device ^{CODESYS Forge talk (Post)}
Hi all, I am attempting to use the Control Win V3 soft PLC to control a WAGO 750-315 remote I/O system via modbus RTU communication. I am struggling to connect to the device. I have been following this tutorial: https://www.youtube.com/watch?v=YlRfkESaNds I have setup my devices as shown in the images below. I have verified that my com port settings are correct as I am able to connect/control using modbus simulator software with these settings. I have also connected to a modbus master simulator program as instructed in the video, but the orange triangles will not go away. Additionally, I have updated my settings to 485 using the PLC shell. I have also set "always update variables" to enabled (1). Serial port, PCI-Bus, and modbus serial device status all show as "Not Running."
Last updated: 2024-08-26

Sort by relevance or date