wiki Discussion
wudaxi
wiki
(Discussion)
Forum for wiki comments
Last updated: 2025-02-26
blog Discussion
wudaxi
blog
(Discussion)
Forum for blog comments
Last updated: 2025-02-26
(no subject)
wudaxi
wiki
(Thread)
Last updated: 2025-02-26
Home
wudaxi
wiki
(WikiPage)
Project Members: wudaxi (admin)
Last updated: 2025-02-26
wiki Discussion
soumitra87
wiki
(Discussion)
Forum for wiki comments
Last updated: 2025-02-26
blog Discussion
soumitra87
blog
(Discussion)
Forum for blog comments
Last updated: 2025-02-26
Home
soumitra87
wiki
(WikiPage)
Project Members: soumitra87 (admin)
Last updated: 2025-02-26
(no subject)
soumitra87
wiki
(Thread)
Last updated: 2025-02-26
Post by atcprojectteam on Modbus Function Code 15, writing multiple coils
CODESYS Forge
talk
(Post)
Hi all, I am using an RSTI-EP I/O card along with the EPXMBE101 Modbus/TCP network adapter. I have a Control Standard L license. I successfully connected to the I/O card via Modbus and can read inputs without any issues. However, when I try to write to the digital output modules using function code 15, I am unable to make any changes. Here’s what I have done so far: I created a small project using Structured Text. I set up Modbus channels (as shown in the attached image) and mapped the pins. When I use cyclic mode, the connection results in an error. However, when I use the rising edge, the connection works, but I don’t see any changes on the I/O card. For the output module, I assigned one bit to high. After that, I ran CODESYS Control Win V3. (Should I be running the PLC as well?) I built the program, but I am not receiving any response from the I/O card. Could you please advise on what might be causing this issue?
Last updated: 2025-02-26
Modbus Function Code 15, writing multiple coils
CODESYS Forge
talk
(Thread)
Modbus Function Code 15, writing multiple coils
Last updated: 2025-02-26
Post by atcprojectteam on Modbus Function Code 15, writing multiple coils
CODESYS Forge
talk
(Post)
Hi all, I am using an RSTI-EP I/O card along with the EPXMBE101 Modbus/TCP network adapter. I have a Control Standard L license. I successfully connected to the I/O card via Modbus and can read inputs without any issues. However, when I try to write to the digital output modules using function code 15, I am unable to make any changes. Here’s what I have done so far: I created a small project using Structured Text. I set up Modbus channels (as shown in the attached image) and mapped the pins. When I use cyclic mode, the connection results in an error. However, when I use the rising edge, the connection works, but I don’t see any changes on the I/O card. For the output module, I assigned one bit to high. After that, I ran CODESYS Control Win V3. (Should I be running the PLC as well?) I built the program, but I am not receiving any response from the I/O card. Could you please advise on what might be causing this issue?
Last updated: 2025-02-26
problem OPC UA array
CODESYS Forge
talk
(Thread)
problem OPC UA array
Last updated: 2025-02-26
wiki Discussion
pilouuu
wiki
(Discussion)
Forum for wiki comments
Last updated: 2025-02-26
blog Discussion
pilouuu
blog
(Discussion)
Forum for blog comments
Last updated: 2025-02-26
(no subject)
pilouuu
wiki
(Thread)
Last updated: 2025-02-26
Home
pilouuu
wiki
(WikiPage)
Project Members: pilouuu (admin)
Last updated: 2025-02-26
Post by pilouuu on problem OPC UA array
CODESYS Forge
talk
(Post)
Hello, why can't I read the arrays on my PLC's UA OPC server with codesys, even though they are accessible from UA Expert?
Last updated: 2025-02-26
Modbus Function Code 15, writing multiple coils
CODESYS Forge
talk
(Thread)
Modbus Function Code 15, writing multiple coils
Last updated: 2025-02-26
problem OPC UA array
CODESYS Forge
talk
(Thread)
problem OPC UA array
Last updated: 2025-02-26
Post by pilouuu on problem OPC UA array
CODESYS Forge
talk
(Post)
Hello, why can't I read the arrays on my PLC's UA OPC server with codesys, even though they are accessible from UA Expert?
Last updated: 2025-02-26
wiki Discussion
peterkcontrols
wiki
(Discussion)
Forum for wiki comments
Last updated: 2025-02-26
blog Discussion
peterkcontrols
blog
(Discussion)
Forum for blog comments
Last updated: 2025-02-26
Home
peterkcontrols
wiki
(WikiPage)
Project Members: peterkcontrols (admin)
Last updated: 2025-02-26
(no subject)
peterkcontrols
wiki
(Thread)
Last updated: 2025-02-26
Post by itsthefabs on (no subject)
CODESYS Forge
talk
(Post)
Hallo zusammen, ich nutze eine Wago 8212 als Modbus Client (in früheren Codesys Versionen hieß der Modbus Master) und habe einen weitere Wago 8212 als Modbus Server (früher Modbus Slave). Bisher habe ich für den Client den Funktionsblock FbMbMasterTcp aus der WagoAppPlcModbus-Library genutzt. Zukünftig würde ich das allerdings gerne über das Anhängen eines Modbus-Geräts am Ethernet-Knoten im Projektbaum realisieren. Zum besseren Verständnis habe ich ein Bild beigefügt. Der Modbus mit dem Server läuft auch. Kommt es allerdings zum Fehler des Modbus, z.B. kurzzeitig keine Verbindung oder timeout, wird der Fehler nicht automatisch quittiert. Ich muss dann manuell über den Status des Server-Knotens einen Button mit "Bestätigen" drücken. Im Betrieb kann ich mich aber nicht jedes Mal einloggen um einen Fehler zu quittieren. Gibt es hier irgend einen Trick, wie ich das aus dem Programm-Code quittieren kann? Vielen Dank schon einmal.
Last updated: 2025-02-26