5/31/2014 8:19 PM | |
Joined: 6/8/2013 Last visit: 9/30/2024 Posts: 158 Rating: (9) |
Dear kiran, in he configuration of sation just righat click on CPU and go in diagnostics in that you get information |
6/1/2014 3:10 PM | |
Joined: 7/2/2008 Last visit: 9/30/2024 Posts: 928 Rating: (308) |
DearKIRAN_DABHI, I've checked your program and I had to save it with "reorganize slow" in order to open it correctly. However, it seems someone has terribly messed with your program. Here's what you should do after saving with "reorganize slow", 1- Delete all instance data blocks. 2- Check block consistency (This will create instance data blocks with the right length and you will remove most of area length errors in block consistency). 3- You will find some invalid block calls. 4- Click on every invalid block call and the STL/LAD editor will open with the network including the invalid block call. 5- Update block call. 6- Try to save, you probably will have to update some other calls before you will be able to save. 7- Do this for every invalid block call. 8- Download all blocks. 9- Now you sill get INTF LED. 10- Open diagnostic buffer, you will find some missing data blocks (DB9,DB311,DB312 and DB411) 11- For DB9 I don't know how your program is missing this data block (that's why I said someone messed with this program). -A service engineer (with all respect to service engineers) will use cross-reference to know the usage of DB9 in this software. He will easily find that the highest address used is DB9.DBX14.4. Then he will create and download DB9 with an array of 14 bytes. -A project engineer will look after software revisions to know why this data block was created and why it was removed then he will take a decision whether to clean the software and remove every access to this DB or to restore it back with symbols. -At the end if you don't know and can't know what the DB9 is for then act as a service engineer and just solve the problem. 12- You will also find some missing DBs (311,312 and 411) as you deleted them in step 1. This is also strange because they are instance data block in your original software. However, they are not generated any FB. I mean they should have been shared data blocks. If I were you I would have tracked revisions and documents to know their history. EDIT: If you copied them from your old project, you would still get errors again in block consistency. I recommedn to create shared data blocks instead as you have done with DB9. This time you need to extend your array to 366 byte. 13- Your internal fault is gone. Best regards, H-H
AttachmentDGEN.pdf (658 Downloads) |
Last edited by: H-H at: 6/1/2014 3:33 PM |
|
This contribution was helpful to5 thankful Users |
6/1/2014 5:01 PM | |
Joined: 9/16/2011 Last visit: 6/20/2024 Posts: 291 Rating: (6) |
|
Reg, |
|
6/1/2014 5:22 PM | |
Joined: 1/28/2012 Last visit: 7/23/2024 Posts: 519 Rating: (83) |
[quote user="H-H"] DearKIRAN_DABHI, I've checked your program and I had to save it with "reorganize slow" in order to open it correctly. However, it seems someone has terribly messed with your program. Here's what you should do after saving with "reorganize slow", 1- Delete all instance data blocks. 2- Check block consistency (This will create instance data blocks with the right length and you will remove most of area length errors in block consistency). 3- You will find some invalid block calls. 4- Click on every invalid block call and the STL/LAD editor will open with the network including the invalid block call. 5- Update block call. 6- Try to save, you probably will have to update some other calls before you will be able to save. 7- Do this for every invalid block call. 8- Download all blocks. 9- Now you sill get INTF LED. 10- Open diagnostic buffer, you will find some missing data blocks (DB9,DB311,DB312 and DB411) 11- For DB9 I don't know how your program is missing this data block (that's why I said someone messed with this program). -A service engineer (with all respect to service engineers) will use cross-reference to know the usage of DB9 in this software. He will easily find that the highest address used is DB9.DBX14.4. Then he will create and download DB9 with an array of 14 bytes. -A project engineer will look after software revisions to know why this data block was created and why it was removed then he will take a decision whether to clean the software and remove every access to this DB or to restore it back with symbols. -At the end if you don't know and can't know what the DB9 is for then act as a service engineer and just solve the problem. 12- You will also find some missing DBs (311,312 and 411) as you deleted them in step 1. This is also strange because they are instance data block in your original software. However, they are not generated any FB. I mean they should have been shared data blocks. If I were you I would have tracked revisions and documents to know their history. EDIT: If you copied them from your old project, you would still get errors again in block consistency. I recommedn to create shared data blocks instead as you have done with DB9. This time you need to extend your array to 366 byte. 13- Your internal fault is gone. Best regards, H-H
Good observation. . Special mention for "Service & Project Engineer"
|
Regards, |
|
6/1/2014 7:58 PM | |
Posts: 60 Rating: (8) |
HELLO EXPERTS, I WILL FOLLOW YOUR STATEMENTS.AFTER CHECKING REVERT YOU BACK. REGARDS, KIRAN DABHI |
7/12/2014 12:55 PM | |
Posts: 60 Rating: (8) |
thanks for support.i have cleared INT_F led error. |
This contribution was helpful to1 thankful Users |
3/14/2017 11:55 AM | |
Joined: 9/3/2014 Last visit: 3/13/2019 Posts: 4766 Rating: (122) |
New question published by ahmed_abdelhady is split to a separate thread with the subject Internal fault in the 2 cpu. Best regards |
Follow us on