Mapping of Array Element to a EtherCAt Slave variable ^{CODESYS Forge talk (Thread)}
Mapping of Array Element to a EtherCAt Slave variable
Last updated: 2018-07-25

How can I get the status of an ethercat slave ^{CODESYS Forge talk (Thread)}
How can I get the status of an ethercat slave
Last updated: 2018-05-30

Virtual Master and virtual slave - MC_CamIN and MC_Halt ^{CODESYS Forge talk (Thread)}
Virtual Master and virtual slave - MC_CamIN and MC_Halt
Last updated: 2019-03-20

Using Codesys Soft PLC as EtherCAT slave ^{CODESYS Forge talk (Thread)}
Using Codesys Soft PLC as EtherCAT slave
Last updated: 2018-06-04

CANopen slave device: Boolean PDO objects not working ^{CODESYS Forge talk (Thread)}
CANopen slave device: Boolean PDO objects not working
Last updated: 2022-03-11

EtherCAT : enable/disable slave by IEC code ^{CODESYS Forge talk (Thread)}
EtherCAT : enable/disable slave by IEC code
Last updated: 2023-01-06

modbusTCP raspberry as master arduino mega as slave ^{CODESYS Forge talk (Thread)}
modbusTCP raspberry as master arduino mega as slave
Last updated: 2021-02-28

Adding PDO mapping variables in EL6751-0010 (CAN slave) ^{CODESYS Forge talk (Thread)}
Adding PDO mapping variables in EL6751-0010 (CAN slave)
Last updated: 2019-08-16

MC_Home of a master axis while a slave is geared? ^{CODESYS Forge talk (Thread)}
MC_Home of a master axis while a slave is geared?
Last updated: 2021-05-31

Change IP for profinet slave without topology losing ^{CODESYS Forge talk (Thread)}
Change IP for profinet slave without topology losing
Last updated: 2020-12-14

Pilz Drive als ModbusTCP Slave - Adressenbereich verändern ^{CODESYS Forge talk (Thread)}
Pilz Drive als ModbusTCP Slave - Adressenbereich verändern
Last updated: 2019-08-13

CODESYS Control RTE SL as a profinet Slave ^{CODESYS Forge talk (Thread)}
CODESYS Control RTE SL as a profinet Slave
Last updated: 2020-06-20

Coupling Devicenet Slave EL6752 in CODESYS 3 ^{CODESYS Forge talk (Thread)}
Coupling Devicenet Slave EL6752 in CODESYS 3
Last updated: 2016-10-28

WAGO 750-8212 SUPPORT PROFINET (MASTER/SLAVE) ? ^{CODESYS Forge talk (Thread)}
WAGO 750-8212 SUPPORT PROFINET (MASTER/SLAVE) ?
Last updated: 2019-05-20

Eigenen Slave entwickeln - ESI und lib schreiben ^{CODESYS Forge talk (Thread)}
Eigenen Slave entwickeln - ESI und lib schreiben
Last updated: 2018-09-27

WAGO 750-838CanBus Slave - Informationen an Master übergeben ^{CODESYS Forge talk (Thread)}
WAGO 750-838CanBus Slave - Informationen an Master übergeben
Last updated: 2008-05-14

How to add startup parameters to an EtherCAT slave ^{CODESYS Forge talk (Thread)}
How to add startup parameters to an EtherCAT slave
Last updated: 2015-09-15

Interface to Parallax Propeller using I2C slave ^{CODESYS Forge talk (Thread)}
Interface to Parallax Propeller using I2C slave
Last updated: 2015-01-20

Driving the slave axis across master's zero point - caming ^{CODESYS Forge talk (Thread)}
Driving the slave axis across master's zero point - caming
Last updated: 2024-01-18

Post by eschwellinger on Generic EtherCAT slave ^{CODESYS Forge talk (Post)}
Sure, import the ESI file, scan the slave access the PDOs.
Last updated: 2024-05-14

Post by yannickasselin on Question about Demo License limitations for Modbus TCP communication and Fieldbus Instances ^{CODESYS Forge talk (Post)}
As far as I know, there is no other limitations than the 2 hours limit. The demo mode should be plenty enough for testing purposes. Regarding instances. In the device tree, 1 master = 1 instance, no matter how many slaves the master is communicating with. But it is also possible that your Codesys runtime act as a slave. In this case, each slave in the device tree is one instance. You can also use the license metric tool in the IDE. This will tell you exactly how many instances you have in your project. https://content.helpme-codesys.com/en/CODESYS%20Development%20System/_cds_edt_device_licensed_software_metrics.html
Last updated: 2026-02-28

Post by garrian on How to write multiple coils (Modbus FC15) ^{CODESYS Forge talk (Post)}
Hi there! I'm testing out modbus TCP/IP for my home brewery, using Wago PFC200 as both slave and master. I'm using Wago library WagoAppPlcModbus. Holding registers, input registers' and discrete inputs works fine, but when trying to write multiple coils, it doesn't work. Any idea what I'm doing wrong here? Attached is a screenshot of my code. I tried both using bit mapping and without. If I change to FC05, and write only 1 coil at the time, it works fine. But I want to write all at the same time.. Any help is very appreciated :)
Last updated: 2024-11-16

Post by chris--o on ModbusTCP RaspberryPi zu Fronius Wechselrichter ^{CODESYS Forge talk (Post)}
Hallo zusammen, ich hab ein kleines Problem bei einer Modbus TCP-Verbindung von meinem RaspberryPi (ML) zu einem Fronius Wechselrichter. Ich habe mir die CodeSys Version 3.5SP20 heruntergeladen und die Runtime auf dem RaspberryPi mit aktualisiert. Gerät ist ein Fronius Symo 6.0-3-M Folgende Konfiguration habe ich im Wechselrichter (Siehe Bilder). Laut Registertabelle fangen die Daten bei Adresse 40001 an und gehen im Modus int+SF bis 40120 Ich habe mir also im Ethernet-Adapter einen Modubus Master und darunter einen ModbusSlave angelegt. Der Slave (Fronius) hat bei mir die IP 192.168.2.46 dazu UnitID und Port. Ich habe dann einen Kanal mit den 120 WORDS und dem OFFSET angelegt. Wenn ich nun die Konfiguration übertrage , scheint erst mal alles zu passen.. aber es flackert immer wieder ein Fehler beim Slave auf (kann nicht erkennen welcher und finde auch keine Diagnose). Es werden auch keine Daten übertragen. Alles bleibt auf 0. Ich muss dazu sagen, dass ich noch eine weiter Modbus TCP Verbindung zu einer anderen SPS habe. Die funktioniert wunderbar. Normalerweise sollten ja auch mehrere Verbindungen gleichzeitig möglich sein oder? Wäre top, wenn ihr mir helfen könntet, den Fehler zu finden. LG Chris
Last updated: 2025-06-30

Post by testlogic on Sending Sequential Modbus TCP Packets ^{CODESYS Forge talk (Post)}
I have a Modbus TCP slave device where I need to do sequential writes to the same register. The register I'm writing to is kind of like a command line, each packet is a command word encoded in Hexadecimal. I am having difficulty implementing this system in CoDeSys 3.5 SP19. I feel like the structure of the program should be something along the lines of (Pseudocode): ModbusTCPSend(Command Register, Command1) ModbusTCPSend(Command Register, Command2) ModbusTCPSend(Command Register, Command3) I have tried to implement this with a rising edge trigger wMot1OPCode := 16#E1; //Stop Motor & Kill Program xMot1SendOP := TRUE; //Send OP on rising edge xMot1SendOP := FALSE; //Reset wMot1OPCode := 16#9E; //Disable Motor xMot1SendOP :=TRUE; //Send OP on rising edge xMot1SendOP := FALSE; //Reset Where "wMot1OPCode" is the IO map for writing to the command register, and "xMot1SendOP" is the rising edge trigger for that modbus channel. However, this doesn't work. The device never responds to the modbus commands. It seems like the trigger variable is switched too quickly for modbus to send the packet. I know the modbus register is working, because I can set the channel to cyclic and the device will respond. However, I can't use this reliably because I need each command to be sent once, in order. Cyclic keeps re-sending the commands and seems like it could miss a command as well if one was sent in-between cycle time. I have also trying using the Application trigger as described by https://faq.codesys.com/pages/viewpage.action?pageId=24510480, but this is also not working for me. See attached picture for my FBD code. This seems like a simple function, I can't tell what I'm doing wrong here. Thanks for the help.
Last updated: 2024-03-06

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

Sort by relevance or date