Plc's gets disconnected from OPC server when any one plc shutsdown ^{CODESYS Forge talk (Thread)}
Plc's gets disconnected from OPC server when any one plc shutsdown
Last updated: 2018-02-22

Retreive Port Number of UDP Client connected to my UDP Server ^{CODESYS Forge talk (Thread)}
Retreive Port Number of UDP Client connected to my UDP Server
Last updated: 2020-11-24

Raspi SL MC: Which core is used by OPC-UA server ^{CODESYS Forge talk (Thread)}
Raspi SL MC: Which core is used by OPC-UA server
Last updated: 2020-12-16

Codesys OPC DA server requires more then 2 GB of ram ^{CODESYS Forge talk (Thread)}
Codesys OPC DA server requires more then 2 GB of ram
Last updated: 2024-01-25

OPC UA Server Stops after 5 consecutive disconnections of ethernet port ^{CODESYS Forge talk (Thread)}
OPC UA Server Stops after 5 consecutive disconnections of ethernet port
Last updated: 2024-02-13

OPC UA Server with on Codesys + OPC UA Client on Labview ^{CODESYS Forge talk (Thread)}
OPC UA Server with on Codesys + OPC UA Client on Labview
Last updated: 2024-04-12

Post by jacobwago on v3.5 SP19 - Modbus TCP Devices - Channel Limit? ^{CODESYS Forge talk (Post)}
Hello, I have experienced the same issue as described above but for the Modbus Serial configurator. Looking for a solution. In v3.5 SP19 Patch 7 the Modbus Serial Master Slave configurator has a "virtual" limit of 10 channels. In v3.5 SP18 Patch 5 this virtual limit does not exist. I can successfully copy back and forth from 18 to 19 with out any build error. However, this is not a good solution for our customers. What is even more confusing is that the IoDrvModbus library is the same version (4.3.0.0) for both SP18 and SP19. Please help in providing a fix to the virtual channel limit of 10 in SP19. Thanks,
Last updated: 2024-09-29

Post by struccc on Problem Reading Registers via Modbus from non Codesys device ^{CODESYS Forge talk (Post)}
Hi, Might be a good idea first to try out the connection and the device with some handy software, like Modbus Poll. There you can see better, what's really going on... - Is it really connected? - What error code does it return? - Can it read from the register address? - Maybe try Input registers and Holding Registers - can make a difference - Sometimes register addresses are messed up: shifted +-1 (mixing of 2 standards) - Sometimes register addresses start with offset 30000, 40000 ... - Are you using the right protocol? - Is it RTU or TCP? Maybe ASCII? - Can even have a look at the data packets, etc... All this is easier to figure out first with some modbus utility... and then to set it up in CODESYS should not be an issue. P.
Last updated: 2025-03-09

Post by em1681 on Modbus RTU over 750-652 ^{CODESYS Forge talk (Post)}
Hi, It's my first time operating in Codesys 2.3, but I have done a good amount of Codesys programming, so I'm a little familiar. I haven't done a lot of RTU, but a lot of Modbus TCP. I don't have the PLC in my reach at the moment, but I'm trying to be a little ahead. We're adding the 750-652 module to read energy from a flowmeter over RTU. There will only be 1 slave. I attached pictures of my current hardware, PLC code, the register datasheet from the slave and the only modbus serial library I seem to have available. I'm uncertain if this will work. Any help or clarification on how things work will be greatly appreciated. Thanks in advance.
Last updated: 2025-09-01

Post by timl on Application has invalid license metrics ^{CODESYS Forge talk (Post)}
Hallo, ich habe eine Control for Linux SL auf der ich einen TCP Modbus Master anlege, mit dem ich einen Slave auslesen möchte. Das Anlegen funktioniert soweit alles, sobald ich beim ModbusTCPSlaveE/A-Abbild in den Channel eine Variable einfüge, damit ich den Channel auslesen kann, kommt es beim übertragen auf die SPS zu einem Ausnahmefehler. Im Anhang noch eine Bilder der Fehlermeldung und der installierten Lizenzen. CODESYS Version ist V3.5 SP19 Patch 4 Meinem Verständnis nach ist die Modbus Lizenz mit in der Control Standard L inbegriffen und auch in der Lizensierten Softwaremetrik sehe ich keine überschreitung meiner Lizenzbegrenzungen. Daher verstehe ich nicht wieso ich diesen Fehler bekomme und eine auslesung via Modbus nicht möglich ist. Gruß Tim
Last updated: 2024-05-08

Post by dkugler on Modbus RTU Slave ^{CODESYS Forge talk (Post)}
Variablen aktualisieren aktiviert?
Last updated: 2023-12-06

Post by schorge on Modbus RTU Slave ^{CODESYS Forge talk (Post)}
ja
Last updated: 2023-12-10

Post by eschwellinger on VPN ^{CODESYS Forge talk (Post)}
Give CODESYS Automation Server a try!
Last updated: 2023-09-06

Post by mattplc on Opaque NodeId in the OPC UA server ^{CODESYS Forge talk (Post)}
Last updated: 2025-01-09

Post by trebbia92 on Exception when OPCUA datasource disconnects from Server ^{CODESYS Forge talk (Post)}
Last updated: 2025-03-20

Post by k4zz on Continuous Build Server ^{CODESYS Forge talk (Post)}
Last updated: 2024-03-15

Post by k4zz on Continuous Build Server ^{CODESYS Forge talk (Post)}
Last updated: 2024-03-15

Post by k4zz on Continuous Build Server ^{CODESYS Forge talk (Post)}
Last updated: 2024-03-15

Post by k4zz on Continuous Build Server ^{CODESYS Forge talk (Post)}
Last updated: 2024-03-15

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 elsmart on Sequential read and triggering of Modbs RTU channels in application ^{CODESYS Forge talk (Post)}
Hello I need some help understanding how to use Modbus RTU (COM port) in Codesys enviroment. I defined a Modbus Server device (slave) in device tree and added some channels to read from (function 3). Also I set trigering mode to Application. I have a POU in which I want to trigger each channel one after the other something like this (C code for better visualisation): for (int i = 0; i < channelsCount; i++) { triggerChannel(channelsArray[i]); // Start transmission while(channel.xBusy); // Wait for transmission to complete } I have found ModbusChannel function block documentation but examples are scarce. I don't understand how rising edge triggering works. What would be the best solution for achieving sequntial channel triggering? What is the common way to read multiple Modbus channels once every time a specified POU is executed?
Last updated: 2025-05-16

Post by mbmik on IoDrvModbusTCP_Diag not defined when using MODBUS ^{CODESYS Forge talk (Post)}
Hi Im trying to setup a Weidmüller WL2000 to run with MODBUS, to get some data from a server. Codesys V3.5 SP20. The issue is, that whenever i attach an ethernet port and add MODBUS Master und also a Slave, codesys will compile the project, but there always seem to be some remaining errors, which or only visible, when setting the messages window to "Pre-Compiled". I tried a lot of stuff to get rid of these errors, but cant find to seem the reason. New installation of codesys, cleaned project, setup completely empty new project, manually adding libs. Nothing helps. Any help is apreciated. Maybe we are doing something wrong.. Example Project is available, if somebodey wants to take a look. Greetings and thanks alot
Last updated: 2024-04-15

Post by ben1 on How to write multiple coils (Modbus FC15) ^{CODESYS Forge talk (Post)}
If I am understanding what you are saying, then yes that would be your problem. I would create an array of bools on the client side for the transfer and try that. Or if client can't be changed then use words on server and unpack. But I am not sure if you or I are mis interpreting but it sounds a bit jumbled. I don't know what you have control of, but, if you are turning on BITS in the server, you should write to BITS in the client with a Function 15. If you are writing to WORDS in the server, you should write to WORDS in the client with a Function 16.
Last updated: 2024-11-17

Post by wbj0t on What the right way to update TCP/COM slave device holding registers ^{CODESYS Forge talk (Post)}
Hi all :) I have an plc. This plc has option to be as slave device. There are TCP -> Serial Slave Device and COM -> Serial Slave Device. There are 4096 ModBus holding registers with mark "internal modify" for the both devices above. So, COM Slave has 4096 registers and TCP Slave has 4096 registers. And, finally, I have an ARRAY[0..4095] OF WORD. This array glued with COM Slave and TCP slave. Yes, I need plc's opportunity to be communication both TCP and COM ways for the same registers. For example, the next task structure: * TASK_0: 1. pou_READ_Registers 2. pou_0 3. pou_1 4. ... 5. pou_N 6. pou_WRITE_Registers At the first pou I read registers for the other pous, after job we have sort of state of the plc. At the last pou (6) we write modified registers. It is a good scenario: some one wrote registers for the job, after job we save these (modified) registers. But, what if registers wrote between 1 and 6 pou by operator, for example, at the 3 pou -> the last pou 'pou_WRITE' will rewrite this request from operator. What the right way to work with this logic? Thanks you.
Last updated: 2024-07-01

Post by timvh on Unable to Connect to Modbus RTU Device ^{CODESYS Forge talk (Post)}
If your Control Win is the Modbus "Master" then your configuration should be something like: Modbus_COM (Serial port) - Modbus Master (this is the Control Win SoftPLC actively setting up the communication) - Modbus Slave (this is then your WAGO 750-315) You need to add channels to the Modbus Slave configuration to inform the master which variables to read/write from the Wago module. The way you configured it now, the Control Win is also a slave. PS, don't forget to put the PLC (Control Win) in Run.
Last updated: 2024-09-03

Sort by relevance or date