TP 1500 Modbus Master

Hello everyone,

I have one TP1500 6AV2124-0QC13-0AX0 connected via modbus at Prosafe (Yokogawa PLC) modbus Card (Ale111), this hybrid configuration was choose, not be me, for high temperature range of the Prosafe CPU. Anyway my problem this modbus connections is so slowly take like 12 / 17 second to update a RT value, i tried all the combo, like change the Acquisition Cycle and Acquisition Mode.

I have 500 tags pass through this modbus, 100 analogs and 400 digitals.

I tried to check this connection via Wireshark and the HMI request and the PLC answer are fast but still slow in runtime.

I attached a .Png file of wireshark scan, the PLC (ALE111) have IP address 192.168.0.1 and HMI 192.168.0.5

Someone have suggestion?

Thank so much for every reply

I don't know how to speed up the reply from the HMI 192.168.0.05/server, but apparently you are not getting any Input Register values, every Request for Input Registers generates an exception response.   Wrong registers? 

Hello,

eeeehm I don't know really, one thing is to collect data with PLC from Server's side and other thing is to present these data on HMI. So much registers collected from Server takes some time of course so what I see as most important is refresh time of TAGs on HMI and how you collect data from Server's side. I expect you have HMI connected via PN to PLC, correct? I expect Modbus TCP only to Server PLC.

Hi Duris,

Thank you for the reply

This plant is a small Skid and all the RT pass throw the modbus, i don't have other way to get tag from PLC

Hello,

aaaaah ok, understand. Ok, your HMI is Client in this cfg for sure and I expect this behaviour probably. In case you set more quick request time of HMI, question is how answer Server PLC. Simply, in case you set very quick request time and PLC isn't capable answer quickly as you need (cfg on PLC side???? who knows) then your HMI is in situation with error and cycle of requests will be prolonged probbaly. But problem lies somewhere else, also as danw already sugested, maybe you're requesting with wrong defined data. I recommend 2 possibilities:

1. do some tests with PC and Client MB TCP app to be sure that your expected data from Server PLC are available.

2. set maybe better PLC (S7-1200) or any MB TCP capable to request the Server PLC and to do diagnostic then there. Here are more possibilities to speed up requests and better check/test some situations. Also this PLC as Client (now not added HW only expected as test) can be better solution instead of actual HMI. You can better handle MB TCP communication with that Server PLC and present data on this HMI via PN network connection with this expected S7-1200 PLC (as example). Simply, now you 're fighting with HMI's MB TCP functionality what can be no easy but putting this PLC as Client between, it can be best solution in my opinion. You can then more efefctively and easy exchange data (also MB TCP dat) between this S7 PLC and your HMI

Hi Duris,

in my configuration HMI TP1500 is the master of modbus TCP/IP communication, today i connect again my HMI Panel at the Prosafe interface and did test again. Same result of the first one. in the attachment i add a new wireshark scan without exception response, how i set the HMI tags and a little video of my online PLC (Prosafe) that i force a value on it and the HMI waiting time before update the value.

i don't have much options on Prosafe PLC because i need to follow the default columns of datas,

all the signals work, both side, but that a lot of time to animate the graphics.

in the video in attachment, i force at 25.0% the value of AI-55001, before i see this value on HMI it's visible the H, means that PLC send High threshold before see the value (High threshold  set is 20.0%)

Thank for every reply

Hi,

really not sure if I can help you here exactly, I can imagine my steps in this case what I'll do, as I've described already. Ok.

Hi Duris,

in my configuration HMI TP1500 is the master of modbus TCP/IP communication, today i connect again my HMI Panel at the Prosafe interface and did test again. Same result of the first one. in the attachment i add a new wireshark scan without exception response, how i set the HMI tags and a little video of my online PLC (Prosafe) that i force a value on it and the HMI waiting time before update the value.

A: ok, I see this attachment but really not helpful to discover something strange.

i don't have much options on Prosafe PLC because i need to follow the default columns of datas,

A: therefore I've recommended to you set some PC app or S7 PLC instead of HMI now. If there will be same data exchange times then you can do nothing. Now is simply not clear what device does exactly problem, it can be also Server PLC, who knows...

all the signals work, both side, but that a lot of time to animate the graphics.

A; again, somehow I see your times ok due that big number of expected data, therefore my previous recommended test must be prepared to be sure +/-

in the video in attachment, i force at 25.0% the value of AI-55001, before i see this value on HMI it's visible the H, means that PLC send High threshold before see the value (High threshold  set is 20.0%)

Hello,

Simatic PC? Isn't enough to do tests with your NTB/PC running some MB TCP Client SW? Yes, it depends also what app you have available but this you'll need also with Simatic PC, or?