Post by gatto on library ModbusTCP Slave 4.1.0.0 - function block ModbusServer ^{CODESYS Forge talk (Post)}
I've always liked codesys, but sometimes it drives me crazy
Last updated: 2024-11-28

Post by struccc on library ModbusTCP Slave 4.1.0.0 - function block ModbusServer ^{CODESYS Forge talk (Post)}
:) Yeah... Definitely not a "boring" platform, they are nice to give us work for the upcoming years... :)
Last updated: 2024-12-02

Post by felipemsgarcia on Generic EtherCAT slave ^{CODESYS Forge talk (Post)}
Hello Edwin, Thank you foryour answer but, I believe I was not very clear in my question, sorry. What I wanted to know is if there is a generic EtherCAT slave object already in CODESYS that I can use for anything, remote IO, Drives, VFD's and so on, as long as I match PDO's. Is there such an object? Thank you again!
Last updated: 2024-05-16

Post by felipemsgarcia on Generic EtherCAT slave ^{CODESYS Forge talk (Post)}
Hello all, I still couldn't find the answer. I wanted to know is if there is a generic EtherCAT slave object already in CODESYS that I can use for anything, remote IO, Drives, VFD's and so on, as long as I match PDO's. Is there such an object? Thank you!
Last updated: 2024-06-20

Post by yannickasselin on codesys VLAN tagging ^{CODESYS Forge talk (Post)}
I ordered a cheap managed switch and tested it as soon as I received the switch. It works great! I even went a bit further. As you can see in the screenshot, I created 2 Codesys containers. Each one having 2 fieldbuses. The first one has EtherCAT and EtherNet/IP and the second one has EtherCAT and Modbus/TCP. All going through the same ethernet port from the PC to the switch. The switch splits it up into 4 different networks. The hardest part was to figure out how to configure the switch. @eschwellinger, thank you very much.
Last updated: 2024-09-17

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 shrikantp007 on help to get codesys understand ^{CODESYS Forge talk (Post)}
Hello , I need some help on how to start with , 1) how to get test license to test codesys , 2) how to take a configuration backup or running process back and post file on fourm so people can understand and deploy same file and get idea what is missing or configure wrong 3) where i can get pdf for codesys admin or programmer 4) what is hardware recommand ,i am running on windows guest on kvm server .is it ok ? 5) i am trying to get ardunio porject working ,using ardunio board as a modbus slave but its not working some how https://forge.codesys.com/forge/talk/Engineering/thread/bf832569b8/ Thanks in advance . shrikant pune -india
Last updated: 2024-07-22

Post by egau on Enable and Disable Project IO programmatically ^{CODESYS Forge talk (Post)}
Hi @eschwellinger, I tried this with Modbus COM slaves. I was able to disable them (slave becomes greyed out in the device tree), but the DED.Reconfigure "eError" output shows "NOT_SUPPORTED". After this, when I tried to re-enable the slave, it did not work (device stayed greyed out in the device tree), and the DED.Reconfigure "eError" output also showed "NOT_SUPPORTED". Is there something to do about this, or the device just doesn't support reconfiguration? P.S: I tried this running locally on my computer (not in simulation mode). So of course I was not physically connected to the devices. I have two similar projects, but one of them doesn't have the Modbus_COM devices. I know I can "Exclude from build" the devices for that project, but I would really prefer not to do this if possible. I would prefer to dynamically toggle a configuration variable that would enable or disable the slaves.
Last updated: 2025-03-14

Post by solidlogicguy on Little endian to Float from Modbus RTU ^{CODESYS Forge talk (Post)}
Just tried and returns the same value but in scientific notation.
Last updated: 2024-01-08

Post by tomast on Siemens V20 Frequenzumrichter über Modbus RTU ^{CODESYS Forge talk (Post)}
Hi Tim, Have you sorted out your problem because i have also problems with i?
Last updated: 2024-03-21

Post by dawidr on Timeout Error in Modbus Communication with WAGO PFC200 and iEM2050 Meter using 750-652 Module ^{CODESYS Forge talk (Post)}
Last updated: 2024-04-07

Post by csanderson on IoDrvModbusTCP_Diag not defined when using MODBUS ^{CODESYS Forge talk (Post)}
I am also having this same issue after upgrading to 3.5.20.0. Any help Codesys?
Last updated: 2024-04-17

Post by santana on IoDrvModbusTCP_Diag not defined when using MODBUS ^{CODESYS Forge talk (Post)}
I'm having this same issue. I upgraded to 3.5.20.0 from 3.5.19.20. Now I have the precompile errors shown above.
Last updated: 2024-04-17

Post by eschwellinger on IoDrvModbusTCP_Diag not defined when using MODBUS ^{CODESYS Forge talk (Post)}
error need to be solved by CODESYS. hopefully next release
Last updated: 2024-05-01

Post by zer0g on Modbus Client Request Not Processed ^{CODESYS Forge talk (Post)}
Hi, Thank you for your suggestion but the problem is fixed after I disabled and enabled the network adapter from Windows settings.
Last updated: 2024-05-30

Post by mystx on Timeout Error in Modbus Communication with WAGO PFC200 and iEM2050 Meter using 750-652 Module ^{CODESYS Forge talk (Post)}
Hello I have the same problem, anyone have some idea?? Regards
Last updated: 2024-07-30

Post by mystx on Timeout Error in Modbus Communication with WAGO PFC200 and iEM2050 Meter using 750-652 Module ^{CODESYS Forge talk (Post)}
Hello I have the same problem, anyone have some idea?? Regards
Last updated: 2024-07-30

Post by mystx on Timeout Error in Modbus Communication with WAGO PFC200 and iEM2050 Meter using 750-652 Module ^{CODESYS Forge talk (Post)}
Hello I have the same problem, anyone have some idea?? Regards
Last updated: 2024-07-30

Post by thysonfury on OPTO22 Groov Epic PR2 Modbus Comms Dropping out every 2 hours and 4 Mins ^{CODESYS Forge talk (Post)}
OPTO22 Codesys Activation license not active.
Last updated: 2024-09-11

Post by nltheves on Raspberry PI4 Serial Port ^{CODESYS Forge talk (Post)}
Hi Ricardo. I was having the same problem with Codesys and a Raspberry Pi 2W while using the GPIO uart. Your post helped me a lot. Thanks! But could not understand why MODBUS parity bit makes Codesys MODBUS COM driver stopping to work after first request transmission. Did you see this @eschwellinger ? Regards, Nelson
Last updated: 2024-07-18

Post by greenwood on CODESYS Control Raspberry Pi mit Servotreiber T6 von StepperOnline ^{CODESYS Forge talk (Post)}
Hallo, ich versuche, eine Modbus-RTU-Kommunikation zwischen meinem Raspberry Pi mit CODESYS Control für Raspberry Pi 64 SL und einem Servotreiber von StepperOnline, Typ T6, herzustellen. Die Verbindung ist wie folgt: RJ45-Stecker am Servotreiber -> Kabel mit RJ45 an einem Ende und USB-A-Stecker am anderen Ende -> Seriell-zu-USB-Konverter -> Raspberry Pi. Der Seriell-zu-USB-Konverter und die Kabel habe ich zusammen mit dem Motor und Treiber von StepperOnline gekauft und sie sind dafür gedacht, den Servotreiber mit einem Computer zu verbinden, auf dem deren Setup-Software läuft. dmesg | grep tty auf dem Pi sagt mir, dass der USB-zu-Seriell-Konverter auf ttyusb0 ist. Ich weiß nicht, wie man das in einen COM-Port übersetzt, ich habe COM 1 genommen. Ich habe ein Projekt in Codesys erstellt und ein Modbus_COM-Gerät hinzugefügt, einen Modbus_Master_COM_Port und einen Modbus_Slave_COM_Port angehängt. Auf der Registerkarte "Allgemein" des Modbus_COM habe ich die folgenden Werte eingestellt: Slave address 1 Baud rate 9600 Parity None Data bits 8 Stop bits 2 Ich habe den Servotreiber auf die gleichen Werte eingestellt. (Ich habe auch andere Werte getestet, aber mit dem gleichen Ergebnis). Auf der Registerkarte "Modbus Slave Channel" des Modbus_Slave_COM_Port habe ich einen Kanal hinzugefügt und die folgenden Werte eingetragen: Access type Read Holding Registers (Function Code 3) Read Register offset 0x0000 Length 1 Ich habe noch keinen Code geschrieben, weil ich noch nicht herausgefunden habe, wie man die Kommunikation programmiert. Wenn ich das Projekt zum Raspberry Pi herunterlade scheint der Modbus_Master_COM_Port zu laufen (grünes Symbol), aber der Modbus_Slave_COM_Port nicht (rotes Dreiecksymbol). Wenn ich einen anderen COM-Port eintrage, haben sowohl der Master als auch der Slave das rote Dreiecksymbol. Ich habe dies auch mit meinem Windows-PC unter Verwendung von Codesys Control Win 64 versucht und die gleichen Ergebnisse bekommen. Ich wäre dankbar für jede Hilfe oder Tipps, wie ich den Grund dafür herausfinden kann, warum der Servotreiberreiber nicht reagiert.
Last updated: 2024-05-31

Post by dantheman on Connecting to SoftPLC Only Works By Turning Off Modbus Ethernet Port ^{CODESYS Forge talk (Post)}
I have an IPC with 2 ethernet ports and 1 Wi-Fi. I'm using ModbusTCP with the ethernet port named "enp2s0" connected to my remote I/O. This works fine when testing with Python and also works with CODESYS, but CODESYS is only able to scan for the Linux SoftPLC when I turn off the "enp2s0" interface. In other words, I can't get online with the IDE if I want my ModbusTCP comms to run with CODESYS. I'm using a Linux SoftPLC that has the following entry in CODESYSControl.cfg, hoping that this will allow me to connect with "enp1s0" or "wlp3s0", and leave "enp2s0" for field comms, but this seems to only make the source IP of the ModbusTCP comms to be bound to "enp2s0". That last point is the case only if I don't restart the service, but if I do restart the service after changing the config file, the source IP for the ModbusTCP comms then becomes the one for "enp1s0", which is very confusing to me: [SysSocket] Adapter.0.Name="enp2s0" Adapter.0.EnableSetIpAndMask=1 On the device list, I only have "enp2s0" given as the ethernet device that has the ModbusTCP master & slave beneath it, shown in Screenshot 1. On the IPC, I can ping the ModbusTCP client (remote I/O) from "enp2s0", and I've attached a Wireshark capture of running ModbusTCP from the CODESYS runtime as Screenshot 2, 3 & 4 (again, I can't get online when this is running, I have to turn off "enp2s0" to connect even when it's idle and I don't have an active TCP session with my Python tests). Like I explained above, the source IP is "enp1s0", even though the ethernet device on the project is "enp2s0". I was lucky to catch the red message that showed the source IP that makes sense to me (the one for "enp2s0"), but for some reason that connection was reset and I never saw that packet again. I've also tried this with Auto-reconnect both enabled & disabled, for the ModbusTCP Master device. I also have to turn off "enp1s0" and then turn it on, just so that I can have the ModbusTCP comms running from "enp2s0" (which is not intuitive in any way to me, I'd love some help understanding that phenomenon as well) in the weird manner that I've described above. I would be very appreciative if someone can help me figure out this pickle. I'd love to just connect to CODESYS through my Wi-Fi interface and leave my ethernet ports for field comms.
Last updated: 2024-08-01

Post by yang123 on EtherCAT Can't reconnect to servo drive ^{CODESYS Forge talk (Post)}
I am using Ethercat Master 4.6.0.0 and have use the automatic restart slaves feature. But we found of after the Ethercat communication normal and slave drive power-off and power-on the slave can't reconnect sucess. The PLC Log show the drive was al status "6#34 : Invalid DC Timeout Error" and its was reconnection sucess first but seconced later the drive will show the "16#2C : Fatal Sync error" and then drive will can't reconnection. Other slave are reconnect sucess which was link after the can't reconnect's drive the drive was OMRON R88D-1SN
Last updated: 2024-01-23

Post by pazderai on CanOpen write issue ^{CODESYS Forge talk (Post)}
Thank you for an answer. Unfortunatelly, it doesn't work. The slave needs command byte as follows 0x22. It means expedited transfer where s-bit is not set, therefore data length is not specified. If I use segmented mode by CiA405.SDO_WRITE_DATA it produce command byte as follows 0x21 which is unfortunately supported by the slave and it returns with error 0x05040001 - SDO Abort Code -Client/server command specifier not valid or unknown. I can use CAN API low level to overcome this problem where it is possible to set 0x22 as a command byte, but than I can use user interface to set the communication probably, because I thing that machine expert uses library CiA405.SDO_WRITE for setting the slave. Or am I wrong?
Last updated: 2024-07-16

Post by fredruel on ModbusServer became unreachable if reach maximum of 16 byClientConnections ^{CODESYS Forge talk (Post)}
Hello Fraziersedge, the solution of Codesys might be to update your codesys to the lastest version but it was not possible for us. In our Codesys V3.5 SP9 patch 8 I was able to fix this bug. I change my ModbusTCP slave component version or one of the sub component version (ex: SysSocket). Look at the picture in attachement that's the receipe that have work for us. When I got the bug my version of ModbusTCP slave was 3.5.5.0 with SysSocket at 3.5.6.0 and I change to ModbusTCP slave 3.5.14.0 with same version 3.5.14.0 of SysSocket event if I still use codesys V3.5 SP9 patch 8.
Last updated: 2024-08-27

Sort by relevance or date