Hello,

very sry but it looks like you ask for something what is simply impossible to share.

1. know how about projects, internal Company rules.

2. no one here is expected to help with this very specific problem, no one here have time to teach you about things you requested, very sry. Every one here have own free time at his life and I can't imagine then to spend with you so long time as you ask to be familiar with all things.

You have more choices, ask maybe other Company to solve your problem or maybe other steps. pls imagine again for what you're asking now. If you want share something different with forum members, pls go ahead, maybe then some one will help you in your situation.

Hello,

thank you for better description. As I said, maybe if you did already some code, some users here can help you. Yes, maybe I've not understood your description but you ask for complete prj example what is very specific. I don't know what is better, to wait for some user that have your project exactly same (I don't expect) or maybe check some Forum Knowledge areas about S7-300/400 Modbus TCP examples or FAQs. In this case is expected to do some code and tests at your HW and then some one can help better in my opinion. I can also recommend check SIMATIC Modbus TCP Conference with many Topics where similar things are consulted, I also think that many basic things about correct cfg are explained. Don't hesitate to say your next requests or opinions.

Hello Ad_181;

2 poins you have to take into consideration for this project:

1. Modbus TCP is not a native protocol for s7 PLCs, Ethernet cmmunications is mostly done using Profinet (via the integrated profinet port of the CPU or a Ethernet CP 441-1, for example). Modbus TCP exchanges can be progranmmed over the Profinet port, either through Modbus TCP inctructions for the S7-1200 or s7-1500 PLCs or using Modbus TCP libraries that you must purchase for the S7-300 and S7-400 CPUs.

Look at this FAQ, it describes the different libraries you can choose from for your project, and also shows the demo siftware you can download to try out the libraries in yoru program (the SF LED will be continuously OON as long as you do not purchase and install the license):

https://support.industry.siemens.com/cs/ca/en/view/22660304

2. The Bently Nevada 3500 requires a 3500/92 communication gateway to establish Modbus TCP/IP communications, as described in this document:

https://dam.bakerhughes.com/m/3ef267db216875e3/original/3500-92-Communication-Gateway-Datasheet-141542-pdf.pdf

Once you have the correct software and hardware to establish the Modbus TCP connections in this project, some issues can still make the exchanges difficult to program. Here is a discussion that can give you some hints:

https://support.industry.siemens.com/forum/ca/en/posts/s7-1513-1-pn-communication-with-bently-nevada-3500-via-modbus-tcp-getting-error-with-status-value-809b/179741

Hope this helps,

Daniel Chartier