Post by ahuckphin on Issues with Modbus Slave with Raspberry Pi ^{CODESYS Forge talk (Post)}
duplicate
Last updated: 2024-07-11

Post by dohy on Modbus RTU Response CRC fail ^{CODESYS Forge talk (Post)}
Did you resolve it?
Last updated: 2024-09-19

Post by ph0010421 on MODBUS TCP REGISTERS CODESYS V3.5 ^{CODESYS Forge talk (Post)}
hello Use FC3 instead of FC4
Last updated: 2024-10-11

Post by bartspako on Connection between Beijer PLC and Schneider Tesys-Island using Modbus TCP ^{CODESYS Forge talk (Post)}
Last updated: 2024-10-16

Post by durallymax on Access Variable Visu Dialog ^{CODESYS Forge talk (Post)}
Is there a way to access the variable in the called dialog? Example: Text Field element with PLC_PRG.myVar as Text variable. OnMouseClick configured to write variable with keypad pop-up. OnValueChanged configured to Execute ST RND(PLC_PRG.myVar,2); Rather than change myVar with each copy of this Text Field, is there a way to access whatever the configured text variable is? Generally try to stay away from ST in visu, but was curious regardless.
Last updated: 3 days ago

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 laazik2 on v3.5 SP19 - Modbus TCP Devices - Channel Limit? ^{CODESYS Forge talk (Post)}
I am actually wondering as well if there are plans to fix it or not? As adding two modbus devices creates it's own problems with connection limits and other issues, which some slave devices have.
Last updated: 2023-09-05

How to use more 4 instances of CANopen/Profibus/Modbus with The application-based license CODESYS Control ^{CODESYS Forge talk (Thread)}
How to use more 4 instances of CANopen/Profibus/Modbus with The application-based license CODESYS Control
Last updated: 2023-11-02

Controlling PM564-eth PLC using Weintek HMI with MODBUS TCP/I. I keep getting communication errors. ^{CODESYS Forge talk (Thread)}
Controlling PM564-eth PLC using Weintek HMI with MODBUS TCP/I. I keep getting communication errors.
Last updated: 2021-02-15

Post by squiggleypuff on Can't Add New Version of Modbus TCP Master ^{CODESYS Forge talk (Post)}
Turns out Modbus was working despite the pre-compiler errors; I was reading the wrong addresses of the slave device, which was why I was seeing all 0s. Thanks for ignoring me.
Last updated: 2024-04-09

Post by brzozka100 on Change modbus server parameters from program ^{CODESYS Forge talk (Post)}
Hello, is there a possibility to change modbus server parameters (baud rate, parity, etc.) configured in devices tree from PRG? I need to be able to change them, for example, from HMI.
Last updated: 2024-07-16

Post by brzozka100 on Change modbus server parameters from program ^{CODESYS Forge talk (Post)}
Hello, is there a possibility to change modbus server parameters (baud rate, parity, etc.) configured in devices tree from PRG? I need to be able to change them, for example, from HMI.
Last updated: 2024-07-16

Post by wagomikep on Number of Connections to Modbus TCP Slave ^{CODESYS Forge talk (Post)}
Hello, Is there a maximum number of Masters that can connect to a Modbus Slave that is configured in the device tree? Is this limited by the CODESYS IDE, or the manufactures hardware and CPU load? Thank you,
Last updated: 2024-08-01

Post by wagomikep on Number of Connections to Modbus TCP Slave ^{CODESYS Forge talk (Post)}
Hello, Is there a maximum number of Masters that can connect to a Modbus Slave that is configured in the device tree? Is this limited by the CODESYS IDE, or the manufactures hardware and CPU load? Thank you,
Last updated: 2024-08-01

Post by wagomikep on Number of Connections to Modbus TCP Slave ^{CODESYS Forge talk (Post)}
Hello, Is there a maximum number of Masters that can connect to a Modbus Slave that is configured in the device tree? Is this limited by the CODESYS IDE, or the manufactures hardware and CPU load? Thank you,
Last updated: 2024-08-01

Post by wagomikep on Number of Connections to Modbus TCP Slave ^{CODESYS Forge talk (Post)}
Hello, Is there a maximum number of Masters that can connect to a Modbus TCP Slave that is configured in the device tree? Is this limited by the CODESYS IDE, or the manufactures hardware and CPU load? Thank you,
Last updated: 2024-08-01

Post by jacobwago on v3.5 SP19 - Modbus TCP Devices - Channel Limit? ^{CODESYS Forge talk (Post)}
Hello All, The solution is updating SP19 Modbus version from 4.3.0.0 to 4.4.0.0 (see attached image for bug fix). Thank you,
Last updated: 2024-09-30

Post by banialuk on Modbus TCP Server ^{CODESYS Forge talk (Post)}
I created Modbus Server TCP, but when I try started i have a error "TCP socet error" "Error on open/close/read/write TCP socket."
Last updated: 2024-10-21

Post by timvh on Modbus TCP & RTU with Control for Linux SL ^{CODESYS Forge talk (Post)}
Most likely your IP address is set to 172.... because you use a VPN connection to your device. Probably best to use the other Ethernet interface for your modbus communication.
Last updated: 2024-10-24

Post by dawidr on Best practices for querying multiple MODBUS devices ^{CODESYS Forge talk (Post)}
Hi! What are the best practices for querying multiple Modbus devices? Single PRG or maybe multiple PRG (so basically multiple thread) per each Modbus device. In my current implementation I'm using single PRG and I'm utilizing FbMbMasterMultiQuerySerial and WagoAppPlcModbus.FbDigitalTwinMbSlaveDevice in eCockpit with PFC200. I've the timer with 2 seconds delay there and it was working fine for single device. But now I have three Modbus devices and for two of them I need to run 2/3 queries to get data from all registers. I noticed that the delays for getting the data from the Modbus devices is much bigger right now.
Last updated: 2024-07-31

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

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

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

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

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