[foxboro] PLB ladder running in FBM? Plus, disappearing files

System: old-school nodebus at v7.1.1 running AW51G boxes and CP30s.

Situation: I have a 100-series FBM whose .p file disappeared from the
/opt/fox/ciocfg/<compound_name> directory.  I don't know how that happened.
I can't see the ladder from the PLB's detail display, and of course the
ladder appears blank when looking at it through the ICC.  I found a saveall
from about 3 weeks ago that turned out to have the .p file in it, and I
copied that file to /opt/fox/ciocfg/<compound_name>, so now I can see the
ladder properly in the ICC but not on the detail display.  The FBM looks
fine in Sys Management.  The PLB's detail display shows some IFLs and OFLs
lit up and other not, and there's no cyan/smurfing present on either the
detail display or process display elements linked to this PLB.  The PLB
detail display's faceplate says "Logic = On-Line".

The .i, .r and .s files for sequence blocks in the same directory are also
missing but  I will burn that bridge when I get to it.

Question #1: how do I know if the FBM is actually executing a "real" copy
of the ladder and not just an empty ladder?  I know I could compile and
re-insert my restored ladder via ICC but the process is online and I don't
want to disrupt the timing and one-shot functions of the ladder if it's
already running OK in the FBM.  Rebooting the Matrix usually causes
problems.

Question #2: how can PLB and sequence files just disappear from
/opt/fox/ciocfg/<compound_name> but the blocks be running OK per the
process and detail displays?

Thanks,
Mike Adams
Mitsubishi Polyester Film, LLC
Greer SC USA
864-879-5231

 
 
_______________________________________________________________________
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:             http://www.freelists.org/list/foxboro
to subscribe:         mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
to unsubscribe:      mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave

Other related posts: