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=20
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,=20
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=20
the references to your PLB blocks in the compounds, if these are loaded=20
before the 2 mentioned compounds.

That's what happened. A DEL/UNDEL fix the xxx.p reference in the
<LBUG>_ECB=20
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=20
check these.




Regards,

Patrick Den Haese
Invensys systems Belgium.





----- Original Message -----=20
From: <Jack.Easley@xxxxxxxxxxxx>
To: <foxboro@xxxxxxxxxxxxx>
Sent: Friday, June 27, 2008 8:32 PM
Subject: Re: [foxboro] FoxView Hang-up


> Yes,
>
> We have had multiple problems at Ver8.2 and Ver8.3 with Ladder Logic
> being non-functional or cyan after an upgrade to the MESH from Nodebus
> 6.12. The worse scenario is a non-functional PLB, as you have no
warning
> of a problem. Most of these issues were found at this site shortly
after
> the MESH upgrades and were fixed by delete/undelete of FBMs. I have
> submitted CAR #1010385 for this issue, but have heard of no resolution
> as yet.
>
> A word of advice to all users (and Fox Engineers) upgrading to MESH
> 8.2/8.3 who use PLB blocks. Check all PLB blocks very carefully after
> your upgrade to ensure outputs track inputs and/or they are not cyan.
>
> Jack Easley
>
> -----Original Message-----
> From: foxboro-bounce@xxxxxxxxxxxxx
[mailto:foxboro-bounce@xxxxxxxxxxxxx]
> On Behalf Of Scott, Joe
> Sent: Thursday, June 26, 2008 3:34 PM
> To: foxboro@xxxxxxxxxxxxx
> Subject: [foxboro] FoxView Hang-up
>
> Hello Everyone,
>
>
> I had a strange thing happen today with Foxview 10.1 I/A Version 8.3.
> The Dynamic updated on valve limit color wouldn't change, but if you
> went to the ladder you could see the OFL change. I checked the CP for
> over runs and it looked fine with no over runs. This affected only one
> FBM10. Everything on this FBM that was tie to a Display wouldn't
changes
> states. I had to delete / undelete the FBM before it started acting
> right. Does anyone have an idea what would have cause this?
>
> Thanks,
>
> Joe Scott
>
> ATI Alldyne
>
> Huntsville, AL
>
>
 
 
_______________________________________________________________________
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: