Banxico

The modbus RTU to TCP converter is the one that does the work of moving from one medium to another, so you can use the blocks spoken in the Siemens PLC and configure them as if they were RTU (IP and ID).

What PLC will you use?

What you should see is how to configure the modbus RTU to TCP (ID, baud) converter.

 Hi everyone!

I need to do this configuration in my application. I am using a 1512 (TIA V16) controller, a Modbus-RTU/TCP-IP converter (not gateway, only medium converter) and I have a Modbus-RTU Slave at the serial side. The converter I am using does not have any GSD file to install, then I created a TCP connection between the controller and the converter. The block Modbus_Comm_Load need a hardware identifier at the pin PORT. There's any way so I can configure the block to read slaves data?

BR from Brazil

------------------------------------------------------------------------------------------
Split from Modbus RTU OVER TCP protocol in TIA.

Duris_I

 Hello,

DanPereira

 

Banxico

The modbus RTU to TCP converter is the one that does the work of moving from one medium to another, so you can use the blocks spoken in the Siemens PLC and configure them as if they were RTU (IP and ID).

What PLC will you use?

What you should see is how to configure the modbus RTU to TCP (ID, baud) converter.

 Hi everyone!

I need to do this configuration in my application. I am using a 1512 (TIA V16) controller, a Modbus-RTU/TCP-IP converter (not gateway, only medium converter) and I have a Modbus-RTU Slave at the serial side. The converter I am using does not have any GSD file to install, then I created a TCP connection between the controller and the converter. The block Modbus_Comm_Load need a hardware identifier at the pin PORT. There's any way so I can configure the block to read slaves data?

BR from Brazil

 very sry, from your description I see some not correct informations or maybe some missunderstanding about use of Converter with your existing HWs.

1. On S7-1500 side you mention TCP connection but MB RTU blocks used.

2. Your serial side of Converter has Slave device, ok. Is your Converter working as this is required? Can you pls only for sure give us link ENG about that converter?

3. This isn't Profibus and Profinet module so no GSD/GSDML file not required to your HW, it's pure converter of protocols. You need maybe cfg it for proper functionality as I recommend in point 2. Some similar devices can be configured differently at both sides, I mean as MAster and Slave generally.

 HI, Duris_I! Thanks for answering.

I never used a converter like this before, so I'm trying to learn it. 

I probably wasn't very clear about the scenario. I'll answer you point by point:

1. I created a TCP connection to the converter trying to estabilish communication between the controller and the converter. I thought that, once I need to communicate with a Modbus-RTU slave at serial side, at the controller side I needed to use MB RTU blocks. I dont know if this is the right way to do it. (Probably not XD)

2. The converter is working fine. I translated and attached the converter manual (Available only in Brazilian Portuguese)

3. Thats what I dont know how to do correctly. How to configure hardware correctly at TIA application and which blocks should I use at my program to set this communication right?

Thanks, again.

The converter has a feature that allows the conversion from Modbus-TCP to Modbus-RTU protocol. When enabling this function, the converter assumes an MB server role and wait for the controller to connect to port (502). In the controler, you need to configure a TCP based connection to the converter IP and configure it to actively establish a connection in the same port opened in the converter (502).