6/19/2009 6:00 PM | |
Joined: 7/2/2008 Last visit: 9/30/2024 Posts: 928 Rating: (308) |
Hello, It depends on how the ET200S is configured (either DPV0 or DPV1) behind the Y-Link. The Y-Link manual says, The diagnostic data of the underlying diagnostics-capable slaves buffered in the IM 153-2 can be read via the SFC 59 "RD_REC". Each module in ET200S occupiessingle slot from the max. 256 slots. 12.2.3.3 Module status (Page 157) Definition The module status is part of the device-related diagnostics and reports the status of the configure modules. Structure of the module status The modules status comprises 63 bytes. The start address x is the equal to 37 for the S7 standard mode and redundant mode, in DP standard master mode it depends on the diagnostic blocks that are present. The status of each slot is coded by 2 bits in the module status. The following applies to the entry in the module status: ● If an underlying slave delivers its own module status in its diagnostics, this status is copied to the appropriate location. ● If an underlying slave delivers an identifier-related diagnosis but no module status, the status 01B "Module error" is entered for an incorrect identification.● If an underlying slave delivers neither its own module status nor an identifier-related diagnosis, the status is entered as follows: –In case of faultless operation: 00B "Module OK" –In case of configuration errors: 10B "Wrong module"–If a slave is missing 11B "No module"–In case of other errors (for example "Prm_Fault"): 01B "Module fault"
If a DPV0 slave or a non-interrupt-capable DPV1 slave on the underlying master system reports a diagnosis, the IM 153-2 initiates a diagnostic interrupt on the higher level DP master system ("proxy diagnostic interrupt"). The diagnostic frame of the slave is stored in the additional interrupt information. If this frame is longer than 59 bytes, the information exceeding the 60th byte is discarded. In addition to this, bit 7 (Ext_Diag_Overflow) is set in the third forwarded byte (byte x+6). The diagnosis of an interrupt-capable DPV1 slave operated in DPV1 mode does not cause a diagnostic interrupt. Interrupt routing When an interrupt-capable DPV1 slave on the underlying master system initiates an interrupt, the IM 153-2 forwards it to the higher level DP master system. The interrupt header and additional interrupt information of the slave are stored in the interrupt section of the IM 153-2. With the exception of slot numbers and sequence numbers, this information remains unchanged. |
Last edited by: H-H at: 6/19/2009 6:03 PM |
|
This contribution was helpful to1 thankful Users |
6/19/2009 10:08 PM | |
Joined: 10/3/2008 Last visit: 8/28/2024 Posts: 961 Rating: (124)
|
Hi, this information is new for me. The Technical Support said me, that it's not possible to diagnose the modules behind an y-link. But this was some time ago... I will test it. You can download a demo version of Systemdiagnostics for testinghere, Tab "Download": http://www.industry.siemens.com/industrial-services/it/en/PRODUCTS/DIAGNOSTICS/PROFIBUS_DPPA_SLAVE_DIAGNOSTICS.HTM. Wüstenräuber |
6/20/2009 7:11 PM | |
Joined: 7/2/2008 Last visit: 9/30/2024 Posts: 928 Rating: (308) |
DearWuestenraeuber, Thank you very muchfor the link. I'm going to try this demo quite soon. Apparently there might be some confusion and I should have written my words in another way. I meant that diagnostic data of DP slaves behind Y-Link can be reached but I don't know if System Diagnostics software can reach it or not. I'm quite sorry for this mess. However, it's stated in the picture I'm attaching that System Diagnostic V5. can display DP slaves behind Y-Link. I hope your test will give us more details and tell if it just displays slaves behind Y-Link or even fetch their diagnostics. Navang, I'm quite sorry as Idon't havesuch code but it seems that our friend Dariusmight havethe right experience according to this thread. Darius is very helpful and I think he won't mind helping you. Best regards. H-H |
6/20/2009 7:46 PM | |
Posts: 557 Rating: (64) |
hi find the link......... /tf/WW/en/Posts/30955#top http://support.automation.siemens.com/WW/view/en/22727527 regards |
Follow us on