12/14/2014 2:59 PM | |
Joined: 1/28/2009 Last visit: 5/2/2024 Posts: 6838 Rating: (1359)
|
Dear friends,
I-Slave (S7-300/400) can trigger Hardware Interrupt on the DP Master with SFC 7 "DP_PRAL".You can read more in online manual of STEP 7 or search the online support website for some sample.As it has been mentioned by friends, first process the interrupt in slave and then generate a Hardware interrupt on the DP Master with SFC7.
I also prefer the solution propose by Juergen, but this issue discuss in more details in the following link(How to do an easy task with difficult ways): FAQ:Recognizing a Failure of DP Master at the I Slave
I hope this helps, Hamid Hosseini |
Last edited by: hdhosseini at: 12/14/2014 3:07 PM |
|
This contribution was helpful to1 thankful Users |
12/15/2014 9:29 AM | |
Joined: 1/28/2009 Last visit: 5/2/2024 Posts: 6838 Rating: (1359)
|
Hello Jürgen, Thank you for the interest, Handling process interrupt over PROFIBUS DP subnet has the constraints of DP network.If a large DP network exists with badly designed parameters such as long cables, slow baud-rate, Multi-Master and too many slaves, reaction time to all process changes are longer.This appplies for an interrupt from an analog input due to limit violation on a modular DP Slave (ET200M) to an interrupt from I-Slave(in the same subnet).
SFC 7, generates telegrams for process interrupts to master with high priority function(over DP network) and for sure you have the chance to react to cause of interrupt in I-Slave much faster. I suggest the section 6.3 of Josef Weigmann's "Dezentralisieren mit PROFIBUS-DP/DPV1" for more related information plus a sample. Best regards, Hamid Hosseini |
Last edited by: hdhosseini at: 12/15/2014 9:36 AM |
|
This contribution was helpful to1 thankful Users |
Follow us on