7/13/2013 12:15 PM | |
Posts: 30 Rating:
|
Sir you mean to edit GSD file and configure the parameter it self and reload it again, So if i have 3 stations i will edit/create GSD file for each? thanks |
7/13/2013 12:44 PM | |
Posts: 30 Rating:
|
OK Sir, I have seen the diagnostic address, so each diagnostic address should be desame for profibus address number. |
7/14/2013 9:40 AM | |
Posts: 30 Rating:
|
Ty Sir for helping me and clearing out the details, Best Regards Jeff |
This contribution was helpful to
1 thankful Users |
7/14/2013 2:33 PM | |
Posts: 30 Rating:
|
Hi Expert, Sir hdhosseini, playerslight, ste39, Here is my another query, after configuring the master slave profibus communication, what is the best way to start with, should i used the diagnostics first? 1. Start Daignostics to verify the list of slave stations? how do i go about programming it? ________________________________________________ step 7 online manual wrote: Diagnostic Address STEP7 specifies a default address for diagnostics here. You can change this address. The failure or return of a DP slave is reported to the master via this diagnostic address. The CPU then starts the OB86 "Rack/DP Slave Failure." You can also use this address with SFC 13 DPNRM_DG to obtain the complete diagnostic information from the DP slave and include it in the CPU program. For DPV1 slaves this address is assigned to the virtual slot 0. 2. Below is my previous thread /tf/WW/en/Posts/92533#top 3. Attached also here the sample program im trying to work on base on Mr. Slave126 suggestion. AttachmentmyTest.zip (214 Downloads) |
7/14/2013 3:17 PM | |
Joined: 1/28/2009 Last visit: 8/5/2024 Posts: 6844 Rating:
|
Hello again, First , you should read data from the slave.For that you can use the addresses in HW.Config plus using load/transfer or check and assign instructions. For diagnostics, there are several ways,Using OB86.But note there are some points to consider: I wanna know when DP Slave has a failure - OB86 Issue related to OB86 call after CPU startup in case of DP Slave [code] CALL SFC51 "RDSYSST" REQ :=#IN0 SZL_ID :=W#16#292 INDEX :=W#16#1 RET_VAL :=#TEMP3 BUSY :=#TEMP31 SZL_HEADER:=#TEMP4 DR :=#TEMP32 JBI M004 //failure of SFC51 processing BEU M004: NOP 0 //READ CONTENT OF DATA RECORD AN #TEMP32.TEMP34 //ZERO SHOWS FAULT = DB16.DBX 4.7 //1ST SLAVE FAILING AN #TEMP32.TEMP35 = DB16.DBX 5.0 //2ND SLAVE FAILING AN #TEMP32.TEMP36 = DB16.DBX 5.1 //3RD SLAVE FAILING AN #TEMP32.TEMP37 = DB16.DBX 5.2 //4TH SLAVE FAILING[/code] also see what "FB126" can provide as diagnostics information: Diagnostic package PNIODiag for diagnostic evaluation for PROFIBUS DP and PROFINET IO Best regards Hamid Hosseini |
Last edited by: hdhosseini at: 7/14/2013 3:36 PM// FB126 Last edited by: hdhosseini at: 7/14/2013 3:18 PM |
|
This contribution was helpful to
2 thankful Users |
Follow us on