HMI communication problem with S7-300 (when scan time is high)

supporter

Member
Join Date
Mar 2006
Location
Malmö
Posts
167
Hi Experts,

Here is the problem, a HMI is communicating with a S7-300 system over an ethernet connection (using ISO TCP/IP Protocol). The scan time in the PLC is rather high (50 - 70 ms). The HMI updates slow when the scan time is high but if we download a simple PLC-application (with a low scan time) then the communication/update is OK.

I assume that the problem is caused due to that the PLC only answers to HMI's requests in the end of the scan cycle. I'm more familiar with Mitsubishi PLC-systems, and Mitsubishi Q has a function called COM_M that you can add in the ladder, this function will make the PLC answer requests directly (and not in the end of the scan cycle).

So, the question is, are there any settings/functions in the S7-300 that will improve how the PLC handle requests from the HMI? All ideas and suggestions are most appreciated.

Thanks,

//Supporter
 
I am not sure, that will help ...

In WinCC (if you use WinCC): System Parameter of connection -> Cycle Management -> Uncheck "by PLC"
 
HI


Some thing you can do :
In the PLC under hardware - CPU properties - Cycle/clock memory ... Scan cycle load from communications you can adjust the percentage spend on comms BUT read the help file !!! because it can have strange results if the values are changed to much.

You don't say what HMI youre using but keep your tags or variables grouped in one block , where possible scan the status only when required.

Maybe you should try and find out what is causing the 'huge' cycle time .Are you using profibus DP .Cause we found out that if you got a lot of ET200 IQ it increases the cycle time.You could at a profibus comms module and connect the ET200 to this module and unload you CPU.

Greetings
Eric
 
A 317 and scan times of 50 - 70 ms - that's some big program! As aikona says you can adjust the percentage of scan time allotted to communications, but if I remember correctly the default is 20% and that ought to be enough normally. Which HMI are you using, and are you doing a lot of logging?

keep your tags or variables grouped in one block

This is really the killer, if your I/O is scattered all over the place, especially digital I/O (Bits) you can waste a heck of a lot of transmission time. Data from the PLC to the HMI is usually transferred WORD- or DWORD-wise. If your data is scattered it may be worth mapping all the HMI data to a contiguous area of memory or keeping it all in an HMI-DB so as to optimise data-transfer.
 

Similar Topics

Hello I hope someone could help. I have installed Intouch 2014 R2 on a new HMI, Loaded the Intouch Project, Load DB, Configure the DAServer...
Replies
0
Views
1,469
I have wincc flex 2008 project made with wincc flexible 2088 sp1 project hmi device is simatic pc panel 19" I want to change hmi device to run the...
Replies
17
Views
5,280
I have a Omron CP1L PLC that I'm having problems communicating with a NS5-SQ11B-V2 Omron HMI through ethernet . I have the exact same set up on...
Replies
3
Views
2,084
I have an M241 connected in Ethernet to a HMIS5T panel and I can't get them to communicate I'm using Machine Expert 1.2 On the controller the...
Replies
0
Views
1,797
Dear all, I have TSX 3721 PLC and it has two 8Pin mini din port, one is ter port and other is Auxilary port. can i upload logic from this port...
Replies
1
Views
2,014
Back
Top Bottom