5/4/2018 3:43 PM | |
Joined: 9/27/2006 Last visit: 9/22/2024 Posts: 12282 Rating: (2685)
|
Hello gentlemen; I would like to offer an alternative: First, as suggested by ChristophD, missing or incorrect network configurations are not generally well accepted by the system. I strongly suggest you configure the data exchanges between the 2 CPUs correctly, even if they will be modified at a later date, so the slave becomes acceptable to the master. You can follow the following example program, even if the master nd slave shown are not the same as in your project The important thing is that the data exchange areas should be adequately structured and downloaded to each CPU: DP Link between a S7-315-2DP (slave) and a S7-400 (master): https://support.industry.siemens.com/cs/ww/en/view/6518822 Once the basic configuration is correct for Profibus-DP networking, you can use SFC12 "D_ACT_DP" to remove this slave from the polling loop of the master, so that it will not be interrogated over Profibus, until you decide to reactivate it (using another call of SFC12). Enabling a disabled DP slave with SFC12 ”D_ACT_DP” https://support.industry.siemens.com/cs/ww/en/view/19730984 Notes on the use of system function SFC12 “D_ACT_DP” https://support.industry.siemens.com/cs/ww/en/view/17624225 Hope this helps, Daniel Chartier |
Follow us on