6/9/2010 6:58 AM | |
Joined: 10/7/2005 Last visit: 3/18/2025 Posts: 3042 Rating:
|
Hello mr83 apart from the HWconfig changes thatAyman Elotaifyalready outlined, there is one more additional change that you will have tomake. Put simple, your program will currently communicate with the CP 342-5 via pre-programmed Siemens FC'scalled DP_SEND and DR_RECV (default numbers are FC 1 and FC 2, but these can be changed). DP_RECV will take all (Profibus) Inputs from the CP342-5 and (typically) put these into a DB from which your program accesses them. Conversely, your program will write all CP342-5 related (Profibus) Outputs (typically) into a DB from which DP_SENDwill take them and write them to the CP342-5. Your program may also additionally use the (optional) FC's DP_DIAG and DP_CTRL (default numbers are FC3 and FC4). You can NOT use any of the four above mentioned FC's 1 to 4 anymore if youuse the onboard DP port of the CPU and will have to rewrite this part of the logic. Good news is that it is in general simpler to use the onboard DP port of the CPU as you now have direct access to the Profibus I/O's, bad news is that you will have to change your program. Have a look too at SFC 14 and 15 which may come in handy to replace DP_SEND and DP_RECV (note though that you'll need one SFC14/15 call per I/O module per DP Slave). Below are a few links which have more on this subject and I hope they help with the "reverse Engineering" of your logic from CP342-5 to the onboard DP port: What should you watch out for when configuring a CP342-5 as DP master? What are the differences between an integrated DP interface of my CPU (e.g. CPU 315-2 DP) and the DP interface of the CP 342-5? Which entries deal with consistent data in conjunction with distributed I/O? |
Cheers |
|
Follow us on