Re: [foxboro] FoxView Hang-up

If the .Compound_Dir file is present, as Patrick alluded to, the
compounds are loaded in that order. So the <CPlbug>_ECB is always the
second one to be loaded, after the <CPlbug>_STA compound.

I've seen the problem with the IOM_ID being blanked out, but that's not
the case here.

Duc

-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx]
On Behalf Of Boulay, Russ
Sent: Monday, June 30, 2008 11:17 AM
To: foxboro@xxxxxxxxxxxxx
Subject: Re: [foxboro] FoxView Hang-up

What was deemed years ago as a safety precaution, if a Block is loaded
into a CP that references a certain IOM_ID and that ecb does not exist,
than the IOM_ID parameter of that PLB block is blanked out as a
precaution.
So, FBM ecb's should always first be present before a PLB block is
loaded into a CP.


-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx]
On Behalf Of duc.do@xxxxxxxxxxxxxx
Sent: Monday, June 30, 2008 11:10
To: foxboro@xxxxxxxxxxxxx
Subject: Re: [foxboro] FoxView Hang-up

Patrick,

I've also seen problems with PLB ladders not functioning correctly after
a LoadAll. But in our case, I am certain that the .Compound_Dir file was
transferred -- I made sure of that. And all the xxxxxx.p files in the
ECB compound were maintained as well.

Still, the problem persists, so it's standard procedure for us to
inspect every PLB ladder after a LoadAll. Most of the time (98%) the
problem can be fixed by entering the PLB Editor, compiling the ladder
and selecting Done. Only rarely that we have to resort to
delete/undelete the block.

Duc


-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx]
On Behalf Of patrick Den Haese
Sent: Friday, June 27, 2008 3:13 PM
To: foxboro@xxxxxxxxxxxxx
Subject: Re: [foxboro] FoxView Hang-up

Jack,



I know what could be your problem with your PLB blocks. At least I had
the same error after an on-line upgrade.

PLB's kept functional until they where changed.

When the saveall was transferred with FTP from your "old" system to the
new, you loose your .compound_dir file.

If you then do a load all your don't load your <LBUG>_STA and <LBUG>_ECB
compounds first, but load them in order of appearance.

Then you loose your xxxxx.p files (located in the ECB compound)
containing the references to your PLB blocks in the compounds, if these
are loaded before the 2 mentioned compounds.

That's what happened. A DEL/UNDEL fix the xxx.p reference in the
<LBUG>_ECB compound.



If they didn't transfer them with FTP then I don't know what went wrong.

But perhaps the original savealls are still on the system, so you
could check these.




Regards,

Patrick Den Haese
Invensys systems Belgium.



 
 
_______________________________________________________________________
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: