Modbus TCP link ET200 1510 SP

Good morning all,

I am setting up modbus tcp MB_CLIENT link blocks which I have already used.

But I encounter a problem, the MB_client block dialogues well with the device because I see the exchange packets but the REAL values do not correspond between the MB_DATA_PTR and the device where I come to get the information.


My MB_ client block has the following parameters:

-REQ clocked at 10Hz
-Disconnect FALSE
-MB_MODE to 0
-MB_DATA_ADRR 40130 (Photo mapping)
-MB_DATA_LEN 2

I have the 7006 in status and the busy done this rate.

I think it's a problem either of parameterization of the block in particular the addressing of the DATA pointer or of variable format.

Mapping:

Thank you for your help :)

Hi,

Have you tried with address 40131? To my knowledge start holding register address is 40001.

Hope it helps.

Br,

Cocolino

Yes I even tried 40001 and 40131 it changes the values I receive but it's still not the right ones.

Here is the beginning of the mapping:

This is a SCAN concube v3 device

Do you think it is necessary to use another type of register than the 40000?

On my other jumo logoscreen nt device it works with the MB_CLIENT and register 40000.

Thank you

Looking at the image, it seems  that address 130 is an Input Register and not a Holding Register.

In this case, you should try with address 30131 or 30130. Have a look at image attached.

Hope it helps.

Br,

Cocolino

If the problem is: You see always status 16#7006.

The solution is changing MB_UNIT_ID in client FB's Database. 

IF the device ID is 2 For example. You should also make MB_UNIT_ID value 2 except Connect ID.

Hi,

Generally, in the case of Modbus TCP communication, Modbus TCP server is addressed via its IP address so MB_UNIT_ID is not relevant.

However, as indicated in the post above and in the following section of the manual, sometimes the modbus server requires a specific MB_UNIT_ID so it may be your case.

https://support.industry.siemens.com/cs/ww/en/view/109798671/141152652171

Therefore i would check the documentation of your Modbus TCP server to check it.

Hope it helps.

Br,

Cocolino