The short answer is that you cannot recover the entirety of the "source code" of the CP from the CP's RAM. There are things that can be done however to come and, maybe, close enough. The tool dbvu in /opt/fox/bin/tools can be used to document the parameters and blocks from the contents of a checkpoint file. With this information, you can begin to reconstruct the "source code" of the running CP in an off-line machine by manually re-entering the data in the ICC or by using it to create a tag list to feed FoxCAE or IACC. The end result will be a valid workfile (using ICC) or SAVE ALL (using FoxCAE and/or IACC) that contains the compounds and blocks from the CP. The next step is to use whatever backups that remain to find the source code for the Sequence Blocks and PLB blocks: 1) Sequence code Look in /opt/fox/ciocfg/<compoundName> for files that end in .s. If you can recover the text from the files you can use your configuration tool in the off-line system to "cut and paste" it into the correct block. 2) Ladder logic Recovering the source for a PLB block is a little harder. The files are in the same place, but they are not readable by a human. You will need to get the plc2asc tool (or equivalent) from the Cassandra web site to turn the file into text. You can then use the text to reconstruct the ladder logic using your control configurator tool. Of course, if the PLB Monitor still works on the running system, you can try it first to recover the rungs. At this point, you will need to check the configuration. To do that, you will need a CP in your off-line system. You would use your configuration tool to load that CP. Once it is loaded, use dbvu to compare it to the running CP's checkpoint file. Next, you will need to test the sequence and ladder logic and block processing as if you were in a FAT. Eventually, you will be able to create a SAVE ALL that you can load into your new system. Obviously this is a lot of work and experienced hands are going to be useful. I hope this helps. Regards, Alex Johnson Invensys Systems, Inc. 10900 Equity Drive Houston, TX 77041 713.329.8472 (voice) 713.329.1700 (fax) 713.329.1600 (switchboard) alex.johnson@xxxxxxxxxxxxxxxx -----Original Message----- From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx] On Behalf Of Imran Butt Sent: Friday, March 10, 2006 9:48 AM To: foxboro@xxxxxxxxxxxxx Subject: [foxboro] How to make SaveAll when AW changed and no block backup is available. Dear All, Our Customer is running their system at version 3.3 which is not supported by IPS. Now they are upgrading it to version 7 and CP60. The problem is their AW was damaged and not working so they commit one WP as AW and they still cannot access ICC database from new committed AW. The block backup database on the floppy is corrupt and now backup is only in the CP30 which is running. Should we do HH845 (Change the AW's MAC address in the CP), I believe that will not work. Can any one Please guide us how to make the block backup of CP30 for load in CP60. Thanks and Best Regards, Imran Butt System Engineer Manstock Engineering Company (Pvt.) Ltd. 39-42 Farid Chambers, Abdullah Haroon Road Karachi - 74400, Pakistan TEL: +92-21-5678952, 5678953, 5673145 FAX: +92-21-5682576 Cell: +92-321-2102686 E-mail: imran.butt@xxxxxxxxxxxxxxxxx URL: http://www.manstock-engg.com _______________________________________________________________________ This mailing list is neither sponsored nor endorsed by Invensys Process Systems (formerly The Foxboro Company). Use the info you obtain here at your own risks. Read http://www.thecassandraproject.org/disclaimer.html foxboro mailing list: //www.freelists.org/list/foxboro to subscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=join to unsubscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave _______________________________________________________________________ This mailing list is neither sponsored nor endorsed by Invensys Process Systems (formerly The Foxboro Company). Use the info you obtain here at your own risks. Read http://www.thecassandraproject.org/disclaimer.html foxboro mailing list: //www.freelists.org/list/foxboro to subscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=join to unsubscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave