Skip to Content

Register Login

Industry Online Support

Technical Forum

Navigation

S7-414H ProfiBus Diagnostics

Created by: Damon at: 5/4/2009 7:38 AM (3 Replies)

Rating (0)

Thanks 0

4 Entries

5/4/2009 7:38 AM	Rate (0)
Damon Member Joined: 5/4/2009 Last visit: 6/8/2022 Posts: 3 Rating: (0)	Hi all, I have recently upgraded a system to a 414-H PLC. In the old configuration we used FC125 to check for any ProfiBus noded in error. However, when I use the same function to do this process none of the errors appear when they should (ie. during testing). Can someone please help with the parameters when using this function with a redundant system. The network I am trying to check is through a Y-Link (as per attachment) and has id of 5980. Is this network deemed to be external ? Is this the correct function to use in this type of PLC ? I look forward to any help you can give on this matter. Damon Attachment S7-400H Hardware Config.JPG (118 Downloads)

Suggestion To thank Quote Answer

5/4/2009 8:22 AM	Rate (0)
Tomcat Posts: 433 Rating: (48)	Hi Damon, I can't help you with this FC, I don't know it. Perhaps another user can help you... But for Profibus Diagnostics you can use Systemdiagnostics DP/PA Slaves as well. In tab "Download" you can download a demo version for testing. This addonworks for redundant systems definitely. Tomcat
Tomcat Posts: 433 Rating: (48)
Suggestion To thank Quote Answer

5/5/2009 10:40 AM	Rate (0)
H-H Platinum Member Joined: 7/2/2008 Last visit: 11/27/2023 Posts: 928 Rating: (304)	Hello, Idon't think FC 125 or even FB125 would work with slaves after Y-Link on H-System. I'm curiousto know how you filled the parameter DP_MASTERSYSTEM. Which DP_MASTERSYSTEM did you use (1 or 2 or 5980)?! One more thing, FC 125 uses SFC 51. I don't know which SSL_ID is used inside but I've seensomeone hereon forum saying that SFC 51 failed to diagnose DP slaves behind Y-Link because the DP_MASTERSYSTEM_ID (5980) can't be accepted. I think it can't even work directly with the ET200M direct slaves. It's the same reason, which DP_Master are you going to diagnose in H-System (1 or 2). Try to useFC125and alter the DP_MASTERSYSTEM parameter according to which CPU is MASTER. I'm not even sure that it might work this way. I don't have enough hardware to test it now. For DP slaves behind Y-Link, the manual says you can use SFC58. I'm afraid that if FC125 doesn't work, you will have to write your own code anddesign your own screens. Best regards. H-H

Suggestion To thank Quote Answer

5/6/2009 10:12 PM	Rate (0)
Ssc_Mikro Posts: 196 Rating: (12)	Yep thing is changing, you can use sfc51 withSZLID: W#16#94 for cpu with profinet and DP W#16#42 for CPU with one DP port ,and just add the net number you want status from, and save the record ina struct, the you havethe status. CALL "RDSYSST" // Read out the actual network configuration REQ :=#Internal.StartJob SZL_ID :=#SlzId INDEX :=#Parameter.NetNumber RET_VAL :=#Internal.SfcStatus BUSY :=#Internal.Busy SZL_HEADER:=#Header DR :=#Station The avenged with SFC51 is that you also can read the current Profibus / Profinet configuration when the plc powering up.
Ssc_Mikro Posts: 196 Rating: (12)
Suggestion To thank Quote Answer

|

Share this page:

Share this page on...

Follow us on