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.





----- Original Message ----- 
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
>
> Confidentiality Notice: This email message, including any attachments, 
> =0A=
> contains or may contain confidential information intended only for the 
> =0A=
> addressee. If you are not an intended recipient of this message, be =0A=
> advised that any reading, dissemination, forwarding, printing, copying=0A=
> or other use of this message or its attachments is strictly prohibited. 
> If=
> =0A=
> you have received this message in error, please notify the sender =0A=
> immediately by reply message and delete this email message and any=0A=
> attachments from your system.
>
>
> _______________________________________________________________________
> 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
>
> 

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