9/19/2012 8:36 AM | |
Posts: 50 Rating:
|
sorry I forget to attach program attaching herewith
Attachmentwinder_j.zip (130 Downloads) |
9/19/2012 8:50 AM | |
Posts: 50 Rating:
|
as per referance data they are used Manish |
9/19/2012 11:44 AM | |
Joined: 10/7/2005 Last visit: 6/18/2024 Posts: 3008 Rating:
|
Hello Manishkools you have two problems: 1.) DB4 is based on UDT 1. A UDT though existst only in the offline program (it is never downloaded), so you "miss" it now with your online upload. The only fix for this to get hold ofUDT1 from an offline backup and recreate DB4 with it OR or manually recreate UDT1 and then base DB4 on it ORmanually fix up DB4. 2.) FC14 has 13Parameters declared in its interface (7 IN and6 OUT) The call of FC14 from FC13 has though 14 Parameters assigned to it. This "mismatch" now creates the odd looking (corrupted) STL code that you get in your online backup (see also attached pic). Stuff like this can happen when someone does for example the following: Starting point: FC14 had 14 Parameters and was correctly called from FC13 and both were up to date in the PLC. Now someone decides to remove a Parameter from FC14 in the offline backup. He also downloads FC14 to the S7 BUT "forgets" to update FC14's call from FC13 (or updates the call correctly offline but "forgets" to download FC13). When you now do your online upload, you get hit with this garbage call of FC14 in FC13. Note that the S7 and programmay indeed still function correctly in this case even though there is obviously also an online mismatch between calling Block and called Block (it can also crash though or lead to error OB calls,it all depends on what parameter was deleted and/or added). If you are curious enough you can reproduce getting these kind of "corrupt" STL block calls via PLCSIM. The fix in this case isto either get hold of the offline program or manually fix thisone up. I hope this helps |
Cheers |
|
This contribution was helpful to
2 thankful Users |
Follow us on