RE: I/A Alarms and Messages to PC's

[Stear, Bo]

For Foxboro style printer replacement software see www.erus.com

Any old PC can be used to capture all messages or alarms sent to the printer port and 
with an added ethernet card can be easily sent to your business network or anywhere.


-Original Message-
From: Stephen T. Woodworth [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, September 19, 2001 12:08 PM
To: Foxboro DCS Mail List
Subject: RE: I/A Alarms and Messages to PC's


Replace the printer with an old pc (low cost) running a terminal software in
capture mode.  Archive the captured ascii data to disk, periodically archive
the alarm data files across your network.  From there you can parse the
ascii data however you like and analyze it for nuisance, frequency, or
reports.

Stephen T. Woodworth
FeedForward, Inc.
1341 Canton Road, Suite H1
Marietta, GA 30066
mailto:[EMAIL PROTECTED]

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Keith, Tommy
Sent: Wednesday, September 19, 2001 10:41 AM
To: Foxboro DCS Mail List
Subject: I/A Alarms and Messages to PC's


I know there were some posts some time back concerning sending alarms and
messages to
PC's for display and storage.   Could some one who is doing this send me
some instructions.

Thanks,
Tommy Keith
Process Control
Wellman Inc
Florence SC
[EMAIL PROTECTED]
PH. 843-395-3565
Fax 843-395-3885




---
This list is neither sponsored nor endorsed by the Foxboro Company. All
postings from this list are the work of list subscribers and no warranty
is made or implied as to the accuracy of any information disseminated
through this medium. By subscribing to this list you agree to hold the
list sponsor(s) blameless for any and all mishaps which might occur due to
your application of information received from this mailing list.

To be removed from this list, send mail to
[EMAIL PROTECTED]
with "unsubscribe foxboro" in the Subject. Or, send any mail to
[EMAIL PROTECTED]


---
This list is neither sponsored nor endorsed by the Foxboro Company. All 
postings from this list are the work of list subscribers and no warranty 
is made or implied as to the accuracy of any information disseminated 
through this medium. By subscribing to this list you agree to hold the 
list sponsor(s) blameless for any and all mishaps which might occur due to 
your application of information received from this mailing list.

To be removed from this list, send mail to 
[EMAIL PROTECTED] 
with "unsubscribe foxboro" in the Subject. Or, send any mail to
[EMAIL PROTECTED]

---
This list is neither sponsored nor endorsed by the Foxboro Company. All 
postings from this list are the work of list subscribers and no warranty 
is made or implied as to the accuracy of any information disseminated 
through this medium. By subscribing to this list you agree to hold the 
list sponsor(s) blameless for any and all mishaps which might occur due to 
your application of information received from this mailing list.

To be removed from this list, send mail to 
[EMAIL PROTECTED] 
with "unsubscribe foxboro" in the Subject. Or, send any mail to
[EMAIL PROTECTED]

RE: telnet_mail and a poke at contact information.

[Stear, Bo]

Actually, I think it is an excellent idea.  Not to say that David Johnson may agree.  
Now, if you would all just add your socual security number and perhaps a credit card 
number or two, I could get on with it and retire in style...

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, September 19, 2001 8:11 AM
To: Foxboro DCS Mail List
Subject: Re: telnet_mail and a poke at contact information.




David is right.  Anyone who's capable of _using_ the I/A info here for nefarious
purposes is certainly capable of bluffing their way onto the list.  As David
said, are you going to call those contact phone numbers each time you post to
the list, even the ones on the other side of the planet?   Didn't think so.

Mike Adams
Mitsubishi Polyester Film, LLC





From: David Johnson <[EMAIL PROTECTED]> on 09/19/2001 12:53 PM GMT

Please respond to "Foxboro DCS Mail List"
  <[EMAIL PROTECTED]>


To:   "Foxboro DCS Mail List" <[EMAIL PROTECTED]>
cc:(bcc: Mike USA9192 Adams/MFAP/USA)

Subject:  Re: telnet_mail and a poke at contact information.




Hi Duc,

I did the write up on the various methods of e-mailing.  I would be willing
to write it up more formally for the FAQ.  I'll have it to you by Friday.

As far as contact information goes:
This is kind of silly.  It is ridiculously easy to make an alternate e-mail
address and subscribe to the list server.  Are we really going to start
making phone calls before we answer questions on the list?  Most of the
information provided here is freely available to anyone willing to read the
Foxboro manual set (although the list is often helpful with the
interpretation, tricks, etc).  If this is a real security concern then we
should start sending PGP authenticated signatures with the messages, and do
we really want that?

I am also sending Mark Holts latitude and longitude to our spy satellites
to see if he is really there.


Regards,

David Johnson
"Of course I'm who I say I am, why would anyone want to be me."
Premier System Integrators
(256) 355-1732



---
This list is neither sponsored nor endorsed by the Foxboro Company. All
postings from this list are the work of list subscribers and no warranty
is made or implied as to the accuracy of any information disseminated
through this medium. By subscribing to this list you agree to hold the
list sponsor(s) blameless for any and all mishaps which might occur due to
your application of information received from this mailing list.

To be removed from this list, send mail to
[EMAIL PROTECTED]
with "unsubscribe foxboro" in the Subject. Or, send any mail to
[EMAIL PROTECTED]








---
This list is neither sponsored nor endorsed by the Foxboro Company. All 
postings from this list are the work of list subscribers and no warranty 
is made or implied as to the accuracy of any information disseminated 
through this medium. By subscribing to this list you agree to hold the 
list sponsor(s) blameless for any and all mishaps which might occur due to 
your application of information received from this mailing list.

To be removed from this list, send mail to 
[EMAIL PROTECTED] 
with "unsubscribe foxboro" in the Subject. Or, send any mail to
[EMAIL PROTECTED]

---
This list is neither sponsored nor endorsed by the Foxboro Company. All 
postings from this list are the work of list subscribers and no warranty 
is made or implied as to the accuracy of any information disseminated 
through this medium. By subscribing to this list you agree to hold the 
list sponsor(s) blameless for any and all mishaps which might occur due to 
your application of information received from this mailing list.

To be removed from this list, send mail to 
[EMAIL PROTECTED] 
with "unsubscribe foxboro" in the Subject. Or, send any mail to
[EMAIL PROTECTED]

RE: PLC Question

[Stear, Bo]

Hear Hear on the "70" bit...

-Original Message-
From: Glen Bounds [mailto:[EMAIL PROTECTED]]
Sent: Friday, September 14, 2001 9:15 AM
To: Foxboro DCS Mail List
Subject: Re: PLC Question


First, thanks for all the responses.

Second, I have issues with all of the listed methods of communication
from ControlLogix to I/A because of the following reasons:

> 1. AB Integrator 30 to AB 1770-KF2 or 1779-KFL DH+ module in single or
> redundant ControLogix configuration.

I have nine overloaded AB30's connected to one PLC-3 that I plan on updating
to a ControlLogix 5550.  This is absurd.  I would like to have something
LIKE
an AB30 (with no hard drives, moving parts, configure in ICC, ...) but with
a
much larger capacity - like a CP60 communicating over Ethernet to
ControlLogix.

> 2. AW51 or AW70 with Ethernet interface, FoxBlocks and AB Interchange or
> RSLinx software.

I actually purchased AB Interchange for Solaris and was considering
installing it
when I realized how much maintenance and configuration is required.  One of
our plants does us this method and is not happy with the results.

> 3. AW70 with DH+ interface, FoxBlocks and AB RSLinx software.

If it has a "70" anywhere in the model number, it will not reside in my
control
system.  (Sorry, Foxboro!)

> 4. Micro I/A with AB Ethernet interface.

This was actually something I was very interested in until I found out the
true
performance and it isn't much better than the AB30.  I would still end up
with
many stations.

> 5. AW70 with FoxBlocks and DDE I/O Gate through a serial or Ethernet
> interface which addresses data in the native ControLogic naming structure.

See answer for #3.

> 6. AW51 or AW70 through an Ethernet interface with a third party OPC
> software which addresses data in the native ControLogic naming structure.

This is what I will probably have to end up doing.  AW51 with a third party
OPC server.  I just wish I didn't have go this way.  It has a hard drive,
has
to be configured a couple of places instead of one, and I will have to deal
with finger pointing when something goes wrong.

So, in conclusion, I want a "CP60" like performance and form factor, with
the ability to configure C:B.P directly in ICC or FoxCAE communicating
over fast Ethernet.  We have many plants around the world that could use
this technology today.  Is that too much to ask?


Glen Bounds
[EMAIL PROTECTED]
Corn Products International



- Original Message -
From: "Jason Wright" <[EMAIL PROTECTED]>
Subject: RE: PLC Question


> Glen,
>
> I don't think there is a real good answer, but I've seen it done. I have
> copied some old information I found below for reference (from Foxboro
tech).
> There are several options depending on the amount of data and type of
> communications. From the Foxboro perspective, the easiest way would be to
> communicate to the ControlLogix as a PLC-5. This would require a little
bit
> of configuration on the Rockwell side. I hope this is helpful.
>
> Regards,
> Jason
> ___
> Jason Wright
> Regional Technical Specialist
> ControlSoft
> (216) 397-3900 x201
>
>
> A-B ControlLogix PLC's
>
> Many Foxboro customers are purchasing the new Allen Bradley ControLogix
PLC
> and asking how would we interface it to I/A Series. The ControLogix
product
> is designed around their new ControlNet data highway and uses an object
> oriented data naming structure. Fortunately, Allen Bradley also supports
> Ethernet and DH+ with PLC5 data table structure so that all of our
> traditional interfaces can be used. When a data object (up to 40
characters
> in length) is created, a pull-down menu is available to assign the data
> object to a PLC5 data table. In addition, Allen Bradley will be
introducing
> a fault-tolerant ControLogix configuration with two processors and shared
> I/O. As a result, we can interface via the following methods:
>
> 1. AB Integrator 30 to AB 1770-KF2 or 1779-KFL DH+ module in single or
> redundant ControLogix configuration.
> 2. AW51 or AW70 with Ethernet interface, FoxBlocks and AB Interchange or
> RSLinx software.
> 3. AW70 with DH+ interface, FoxBlocks and AB RSLinx software.
> 4. Micro I/A with AB Ethernet interface.
> 5. AW70 with FoxBlocks and DDE I/O Gate through a serial or Ethernet
> interface which addresses data in the native ControLogic naming structure.
> 6. AW51 or AW70 through an Ethernet interface with a third party OPC
> software which addresses data in the native ControLogic naming structure.
>
> -Original Message-
> Subject: Re: PLC Question
>
>
> I for one would be interested in some more detailed information.
>
> I have asked Foxboro about this for a couple of years now with
> no results.
>
> Glen Bounds
> [EMAIL PROTECTED]
> Corn Products International
>
>
>
> - Original Message -
> > Foxboro does not yet endorse connectivity to ControlLogix.
> >
> > We (FeedForward, a Foxboro Systems Integrator) have, however,
successfully
> > integrated the two for one of our customers.
> > I was n

RE: System Alarms & XWindow

[Stear, Bo]

Read a manual. hmmm read a manual hmmm.  Once again Alex comes up with an 
entirely new concept!!!

-Original Message-
From: Johnson, Alex (Foxboro) [mailto:[EMAIL PROTECTED]]
Sent: Friday, September 07, 2001 8:39 AM
To: Foxboro DCS Mail List
Subject: RE: System Alarms & XWindow


I recommend that you read the following three manuals:

*   Display Engineering for 50 Series Workstations (B0193MQ)
*   X Client/Server Support for 50 Series (B0193NV)
*   FoxRemote and TCP/IP Network Integration Installation and
Configuration Guide (B0193VR)

I believe that after reading them, you will have the information that you
need.


Regards,


Alex Johnson
10707 Haddington
Houston, TX 77043
713.722.2859 (office)
713.722.2700 (switchboard)
713.932.0222 (fax)
[EMAIL PROTECTED]  


-Original Message-
From:   Allen Hansie [SMTP:[EMAIL PROTECTED]]
Sent:   Thursday, September 06, 2001 8:06 PM
To: [EMAIL PROTECTED]
Subject:System Alarms & XWindow

Hi Friends,

 (1)   Will u pl. help to know the location path of

system Alarms in VT100 &

XWindow file  path

   (2)How to create XWindow?What is required to change in Master AW
and what 
is to be change in Slave(Xwindow) AW/WP?IP Address is to be
given?File name 
is to be given?etc.and in which location path it is to be given?
After that 
reboot is required?


Thanx,

Allen Hansie





_
Get your FREE download of MSN Explorer at
http://explorer.msn.com/intl.asp



---
This list is neither sponsored nor endorsed by the Foxboro Company.
All 
postings from this list are the work of list subscribers and no
warranty 
is made or implied as to the accuracy of any information
disseminated 
through this medium. By subscribing to this list you agree to hold
the 
list sponsor(s) blameless for any and all mishaps which might occur
due to 
your application of information received from this mailing list.

To be removed from this list, send mail to 
[EMAIL PROTECTED] 
with "unsubscribe foxboro" in the Subject. Or, send any mail to
[EMAIL PROTECTED]

---
This list is neither sponsored nor endorsed by the Foxboro Company. All 
postings from this list are the work of list subscribers and no warranty 
is made or implied as to the accuracy of any information disseminated 
through this medium. By subscribing to this list you agree to hold the 
list sponsor(s) blameless for any and all mishaps which might occur due to 
your application of information received from this mailing list.

To be removed from this list, send mail to 
[EMAIL PROTECTED] 
with "unsubscribe foxboro" in the Subject. Or, send any mail to
[EMAIL PROTECTED]

---
This list is neither sponsored nor endorsed by the Foxboro Company. All 
postings from this list are the work of list subscribers and no warranty 
is made or implied as to the accuracy of any information disseminated 
through this medium. By subscribing to this list you agree to hold the 
list sponsor(s) blameless for any and all mishaps which might occur due to 
your application of information received from this mailing list.

To be removed from this list, send mail to 
[EMAIL PROTECTED] 
with "unsubscribe foxboro" in the Subject. Or, send any mail to
[EMAIL PROTECTED]

RE: Putting ECBs on/off line without using System Monitor

[Stear, Bo]

The reason you can not set the ACTION bit with omset is because it is NOT SETTABLE.  
However, one can still set it with the ever hazardous tool 'setpars'.

-Original Message-
From: Michael J Wing [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, July 31, 2001 8:43 AM
To: [EMAIL PROTECTED]
Subject: RE: Putting ECBs on/off line without using System Monitor


 
When I try to set the ACTION parameter with omset (only testing!) I get an errror code 
of 15.  This corresponds to "omopenlist already open".  Is this perhaps because I'm 
talking about an ECB that is used to communicate with an AB PLC on an AW51 integrator 
rather than a more common FBM ECB? omget for this parameter returns a 0. 

-Original Message-
From: [EMAIL PROTECTED] 
[mailto:[EMAIL PROTECTED]]On Behalf Of Holger Dahl
Sent: Tuesday, July 31, 2001 2:37 AM
To: [EMAIL PROTECTED]
Subject: Putting ECBs on/off line without using System Monitor



David,
 
You can set the ACTION Parameter of the ECBs.
Setting this Parameter to "1" turns the ECB on, setting
it to "2" turns the ECB off.
 
Regards,
Holger Dahl 

 
erpicon software development GmbH
Neusser Str. 724-726
50737 Koeln
 
Tel: 0221-97460-70
Fax: 0221-97460-99
Email: [EMAIL PROTECTED]  


---
This list is neither sponsored nor endorsed by the Foxboro Company. All 
postings from this list are the work of list subscribers and no warranty 
is made or implied as to the accuracy of any information disseminated 
through this medium. By subscribing to this list you agree to hold the 
list sponsor(s) blameless for any and all mishaps which might occur due to 
your application of information received from this mailing list.

To be removed from this list, send mail to 
[EMAIL PROTECTED] 
with "unsubscribe foxboro" in the Subject. Or, send any mail to
[EMAIL PROTECTED]

V6.3 and Exceed

[Stear, Bo]

Help!
Since we have upgraded our workstations to version 6.3 the displays served via the 2nd 
Ethernet port (Hummingbird Exceed) no longer work at any other desktop setting than 
1024 X 768 and 256 colors.  Otherwise they simply get a window filled with black.  
Prior to the upgrade, MOST of the 100 or so users could get it to work at 800 X 600 
and SOME of those with High Color.  Any suggestions?

---
This list is neither sponsored nor endorsed by the Foxboro Company. All 
postings from this list are the work of list subscribers and no warranty 
is made or implied as to the accuracy of any information disseminated 
through this medium. By subscribing to this list you agree to hold the 
list sponsor(s) blameless for any and all mishaps which might occur due to 
your application of information received from this mailing list.

To be removed from this list, send mail to 
[EMAIL PROTECTED] 
with "unsubscribe foxboro" in the Subject. Or, send any mail to
[EMAIL PROTECTED]

RE:

[Stear, Bo]

I think Foxboro's inclination for that support is Micro I/A which also talks ethernet 
and, I believe, is much less expensive.

-Original Message-
From: Schouten, Frits JF [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, July 18, 2001 11:13 PM
To: Foxboro DCS Mail List (E-mail)
Subject: 


Hello all,

we are faced with the fact that Foxboro is throwing out the MB+ gateways and we are in 
the middle of setting up more MODBUS+ connections to our Foxboro systems. This is a 
problem.

Now here is a thought. 
A CP60 talks ethernet, right? Modicon PLC's talk ethernet, right? How about tying the 
two together and have the CP60 programmed to talk to the Modocon PLC. Wouldn't that be 
wonderful.
Imagine the throughput we could achieve.

Can Foxboro come to the party please


Frits Schouten
Process Computing Department

B New Zealand Steel
Phone:   +64 +9 375 8111 ext 5261
Email:   [EMAIL PROTECTED]



EOM 

NOTICE - This message and any attached files may contain information that is 
confidential and/or subject of legal privilege intended only for use by the intended 
recipient. If you are not the intended recipient or the person responsible for 
delivering the message to the intended recipient, be advised that you have received 
this message in error and that any dissemination, copying or use of this message or 
attachment is strictly forbidden, as is the disclosure of the information therein.  If 
you have received this message in error please notify the sender immediately and 
delete the message.

---
This list is neither sponsored nor endorsed by the Foxboro Company. All 
postings from this list are the work of list subscribers and no warranty 
is made or implied as to the accuracy of any information disseminated 
through this medium. By subscribing to this list you agree to hold the 
list sponsor(s) blameless for any and all mishaps which might occur due to 
your application of information received from this mailing list.

To be removed from this list, send mail to 
[EMAIL PROTECTED] 
with "unsubscribe foxboro" in the Subject. Or, send any mail to
[EMAIL PROTECTED]

---
This list is neither sponsored nor endorsed by the Foxboro Company. All 
postings from this list are the work of list subscribers and no warranty 
is made or implied as to the accuracy of any information disseminated 
through this medium. By subscribing to this list you agree to hold the 
list sponsor(s) blameless for any and all mishaps which might occur due to 
your application of information received from this mailing list.

To be removed from this list, send mail to 
[EMAIL PROTECTED] 
with "unsubscribe foxboro" in the Subject. Or, send any mail to
[EMAIL PROTECTED]

RE: Synchronization (was RE: HLBL REF.)

[Stear, Bo]

Other tools to check synchronization of all the pertinent data files can be obtained 
and aren't mentioned here.  When installed, check_db_sync and ck_multi_cps in the 
directory check_sync located in /opt/fox/bin/tools will give you a warm and fuzzy 
feeling when it successfully reports databases are synchronized.  These tools are a 
part of the (now partially defunct) 'bootless upgrade' feature.  I run these once a 
week and have discovered problems long before they cause real trouble.

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]
Sent: Monday, July 09, 2001 7:29 PM
To: Foxboro DCS Mail List
Subject: Synchronization (was RE: HLBL REF.)



Corey,

It is critical that the CSA database, the station volume workfile and the
checkpoint file stay synchronized.  Because parameters are constantly
changing on the CP, it is normal that the setable parameters in the CP will
not match the other files, although the non-settable parameters must match.

There are several things that can cause a problem between CP, CSA, station
workfile and checkpoint file.  Some of these include:
1) Power failure or system reboot during ICC session
2) Improper exit from ICC
3) Tape restore
4) setpars
5) CSA tools
6) ICC use with severe station overloading
Other causes probably exist.  Corruption of CSA, work file or checkpoint
file is possible too.  Of the list above, #1 is the one I have seen most
often.  Typically, an ICC session is left open and is still open when the
computer or xterminal it is running on is rebooted (before checkpoint).
Tape restore of an AP or AW is a tricky one.  If changes have been made in
ICC since the tape you are restoring from was made, and if no current
SaveAlls exist, you will probably need to restore from tape, reboot the CP
(to checkpoint file from tape) and re-create the changes in ICC made after
the tape.

A couple of items that may not be obvious:
1) Upload only updates settable parameters from CP to workfile.  Assumption
probably is that non-settable parameters shouldn't need to be updated from
CP.
2) A SaveAll is not made from the CP but from the workfile.  If setpars is
used to change a non-settable parameter on the CP, a SaveAll won't reflect
that change even after an upload.

Tools are available for troubleshooting mismatches:
Select views parameters in CP.
iccprt views parameters in workfile.
dbvu views parameters in checkpoint file (-t option, needs checkpoint file,
map file and image file).
CSA_save exports an ascii copy of the CSA database.

Regards,

Kevin FitzGerrell
Systems Engineer
Foxboro New Zealand

Tel:  +64 (9) 573 7690
Fax:  +64 (9) 573 7691


   
  
Corey R Clingo 
  
<[EMAIL PROTECTED]>  To: Foxboro DCS Mail List 
<[EMAIL PROTECTED]>   
Sent by: cc:   
  
<[EMAIL PROTECTED]Subject: RE: HLBL REF.
  
oject.org> 
  
   
  
   
  
07/10/01 11:17 AM  
  
Please respond to "Foxboro 
  
DCS Mail List" 
  
   
  
   
  




OK, you've gone and confused me now (don't get the big head; it's not that
hard
to do ;-).

I am kind of new to I/A, and this whole checkpoint/workfile/CP's memory
thing
has me asking a lot of questions, to say the least.  I had thought that the
checkpoint at least was a direct copy of the CP's memory, but from what you
say
below this is not the case.  (Emotional state on discovering this
deleted...)

Sois there anything else supplied by Foxvensys that can make changes to
the
C

RE: HLBL REF.

[Stear, Bo]

What Alex did NOT mention although I feel he should have, is that using setpars should 
be avoided period.  There are other more graceful (omset class) methods that are not 
nearly as dangerous.

-Original Message-
From: Johnson, Alex (Foxboro) [mailto:[EMAIL PROTECTED]]
Sent: Monday, July 09, 2001 12:22 PM
To: Foxboro DCS Mail List
Subject: RE: HLBL REF.


Re: Sequence Block Resources

HLBL is slow. Each line of HLBL code is roughly equivalent to the CPU
requirements of an AIN block.

External references to CBPs in the same CP take even longer.



Re: Setting External OM Variables from within HLBL

HLBL allows OM variables (C:B.Ps and SVs) to be set directly using the
following syntax:

: := ;

where 

 is a C:B.P name or a Shared Variable Name
 is the new value for the variable.

The leading colon is required. Two examples are:


:TOWER:OVRHD_LEVEL.SPT := 50.0;


:WP0001DMCMD := "dmcmd applic /opt/prog/myScript $DMNAME &";


NAME := SN0001, "DMCMD";
:'NAME' := "dmcmd applic /opt/prog/myScript $DMNAME &";



This is documented in the appropriate manuals.


There are a couple of "gotcha"s though:

1) If the variable being set is secured or missing, you will get an
operational error that will either cause an SBX to be fired or suspend the
block.
2) Each external reference suspends the execution of the HLBL code for one
block period if the target is outside the CP. If the target is inside the
CP, the call does not suspend the code, but it can take quite a long time.


The former issue is difficult to handle properly if one has several external
references in the code since they will all fire the same SBX and you will
probably want different handling for each case. Personally, I do not use
this approach. I prefer to use a program like cpShell and send it messages
from SENDCONF (see below).


The second issue causes subtle problems in the code. I had one customer call
because his emergency shutdown logic took 10s to execute and it was only 20
lines of code. The problem was that he did not know about the suspension of
execution on an external reference. Since his block ran every 0.5 seconds
though, 10s to execute the code was as good as he could expect.

There is no workaround for this delay other than to not use external
references, i.e., connect the targets to the output of the block. Of course,
that can lead to conflicts with the operator if the operator needs to set
the same targets.



Re: Executing Scripts and Programs from a Sequence Block

There was a long discussion on how to run scripts on demand. The options
boil down to:


*   Using the external reference capability of HLBL to set the DMCMD
global of a DM/FV instance
*   Using SENDMSG or SENDCONF to send a message to a program that will
execute the command.


There are issues with the first approach related to error handling, i.e.,
what happens and how do you handle it if the DMCMD variable does not exist
or someone overrides your command before it can be executed. These are
actually quite difficult to handle.


The latter approach is much more controllable. The SENDCONF command has a
timer. It suspends execution of the sequence block and sets the SUSPND
parameter. When the SUSPND parameter is reset or the timer expires, the
sequence block awakes. If it awakes because of a timeout, the flow of
control goes to a particular part of your logic associated with exactly that
failure. If it awakes because the SUSPND parameter is reset, the flow of
control moves to the next line.


Sadly, we do not ship such an application with the standard system. However,
you can get a copy of one by ordering cpShell. This is a VAS-IT item which
means that it is sold as reusable application engineering. It is licensed on
a per unit basis where we trust you to have a reasonable "process unit".


To order, tell your account rep that you want:


Part No: VAS-IT
Description: cpShell for Solaris
Order Type: ZZPB or ZZPR 
Item Tag: cpShell for Solaris
Special Shipping Instructions: Contact Ruby Chapman in Houston to fill the
cpShell order.
Delivery: 4 to 8 weeks ARO.
List Price (US): 2,200 USD


I'll send you the manual separately.


I'm sure that there are others with similar products.



Regards,


Alex Johnson
10707 Haddington
Houston, TX 77043
713.722.2859 (office)
713.722.2700 (switchboard)
713.932.0222 (fax)
[EMAIL PROTECTED]  


-Original Message-
From:   Jones, Charles R. (Chuck) [SMTP:[EMAIL PROTECTED]]
Sent:   Monday, July 09, 2001 8:59 AM
To: 'Foxboro DCS Mail List'
Subject:RE: HLBL REF.

If the operators can interact with the process, I recommend putting
GDEV
blocks to AUTO (then WAIT 2 seconds for the block to see it) right
before
you use each one.  It is the only way to be sure that the GDEV will
be in
the correct auto/manual state when you need it to be.  If you are
going to
change state on several GDEVs, then you can put t

RE: Speaking of Save_All

[Stear, Bo]

I took a saveall that spanned three disks and tried the loadall from the ICC.
It appears to work just fine, loading all the compounds from the disk even though 
there was only ONE compound listed in the .Compound_Dir file.  We need to find the 
mechanism that makes this work before we can properly create saveall disks from the 
files we are making with our scripts using the ICC API.

-Original Message-
From: Deen, Ron [mailto:[EMAIL PROTECTED]]
Sent: Monday, May 07, 2001 10:25 AM
To: Foxboro DCS Mail List
Subject: RE: Speaking of Save_All


I asked around.
The .Compound_Dir file contains the names of all compounds to be loaded.
As a result only compounds in this file will be loaded regardless of the
compounds available on the diskette. However, if .Compound_Dir it NOT on the
diskette the compounds are loaded in what seems "random order".
So if you state that .Compound_Dir contains only one compound name, this
would be the only one loaded during load_all's.

H, I would be interested in the save_all diskettes and how you have made
these. This is somewhat strange. We would have heard if load_all's would not
load "all" I guess...

Regards

Ron Deen

-----Original Message-
From: Stear, Bo [mailto:[EMAIL PROTECTED]]
Sent: maandag 7 mei 2001 16:53
To: 'Foxboro DCS Mail List'
Subject: RE: Speaking of Save_All


In looking more closely at the contents of the save all diskettes I find
something peculiar (at least to me).
For savealls that can fit on a single disk, the file .Compound_Dir contains
the list of compounds as you suggest.

For savealls that span multiple disks, the content of the .Compound_Dir on
disk #1 contains only the name of the LAST compound as seen from 'ls' on the
mounted saveall and the content of the .Compound_Dir on disk #2 also
contains the name of the LAST compound on that disk.  I don't know if anyone
here has actually tried to restore from these savealls but so far from what
I gather, if Foxboro uses the content of this file to restore, it wont work.
Anyone else know more about how this works?


-Original Message-
From: Deen, Ron [mailto:[EMAIL PROTECTED]]
Sent: Monday, May 07, 2001 5:35 AM
To: Foxboro DCS Mail List
Subject: RE: Speaking of Save_All


I'm sure about the name now:
It is a hidden file: ".Compound_Dir" located in the save_all directory of
your choice.

Regards

Ron Deen

-Original Message-
From: Ron Deen [mailto:[EMAIL PROTECTED]]
Sent: vrijdag 4 mei 2001 19:40
To: Foxboro DCS Mail List
Subject: Re: Speaking of Save_All


I'm not sure about the name, but I think on the harddrive in the save_all
directory, there's a file named "compound.dir" which contains the names (in
order) of the
compounds to be loaded. This is the same sequence as they appear in in ICC.
Follow that list to create the diskette and you will be assured that the
compounds will
be loaded in the same sequence.
I believe ECB's still go first, put these on the first diskette.

Load_all's can be performed from the commandline too.
Go to /opt/fox/ciocfg/api and run load_all for some usage info.
The command take two arguments: "station" and "location/station" or the
other way around, I can never remember.
I could have them mixed up but I think:

load_all  /

comes close.

You should not need it too often I hope...

Regards

Ron Deen@home

"Stear, Bo" wrote:

> I suspected as much.  Is there anything special about savealls that span
more than one disk?  just copy the directories to multiple disks however
they may fit?
>
> -Original Message-
> From: David Johnson [mailto:[EMAIL PROTECTED]]
> Sent: Friday, May 04, 2001 7:45 AM
> To: Foxboro DCS Mail List
> Subject: Re: Speaking of Save_All
>
> Bo,
>
> You should be able to do a cp -r on the directory that you put the
save-all in.
>
> If the save_all command for CP3001 was:
> save_all CP3001 /tmp/CP3001
>
> Insert a BLANK FORMATTED Solaris diskette
> Mount it on /f0
> cp -r /tmp/CP3001/* /f0
>
> and that should do it.
>
> David
>
> ---
> This list is neither sponsored nor endorsed by the Foxboro Company. All
> postings from this list are the work of list subscribers and no warranty
> is made or implied as to the accuracy of any information disseminated
> through this medium. By subscribing to this list you agree to hold the
> list sponsor(s) blameless for any and all mishaps which might occur due to
> your application of information received from this mailing list.
>
> To be removed from this list, send mail to
> [EMAIL PROTECTED]
> with "unsubscribe foxboro" in the Subject. Or, send any mail to
> [EMAIL PROTECTED]
>
> ---
> This list is neithe

RE: Speaking of Save_All

[Stear, Bo]

In looking more closely at the contents of the save all diskettes I find something 
peculiar (at least to me).
For savealls that can fit on a single disk, the file .Compound_Dir contains the list 
of compounds as you suggest.

For savealls that span multiple disks, the content of the .Compound_Dir on disk #1 
contains only the name of the LAST compound as seen from 'ls' on the mounted saveall 
and the content of the .Compound_Dir on disk #2 also contains the name of the LAST 
compound on that disk.  I don't know if anyone here has actually tried to restore from 
these savealls but so far from what I gather, if Foxboro uses the content of this file 
to restore, it wont work.  Anyone else know more about how this works?


-Original Message-
From: Deen, Ron [mailto:[EMAIL PROTECTED]]
Sent: Monday, May 07, 2001 5:35 AM
To: Foxboro DCS Mail List
Subject: RE: Speaking of Save_All


I'm sure about the name now:
It is a hidden file: ".Compound_Dir" located in the save_all directory of
your choice.

Regards

Ron Deen

-Original Message-
From: Ron Deen [mailto:[EMAIL PROTECTED]]
Sent: vrijdag 4 mei 2001 19:40
To: Foxboro DCS Mail List
Subject: Re: Speaking of Save_All


I'm not sure about the name, but I think on the harddrive in the save_all
directory, there's a file named "compound.dir" which contains the names (in
order) of the
compounds to be loaded. This is the same sequence as they appear in in ICC.
Follow that list to create the diskette and you will be assured that the
compounds will
be loaded in the same sequence.
I believe ECB's still go first, put these on the first diskette.

Load_all's can be performed from the commandline too.
Go to /opt/fox/ciocfg/api and run load_all for some usage info.
The command take two arguments: "station" and "location/station" or the
other way around, I can never remember.
I could have them mixed up but I think:

load_all  /

comes close.

You should not need it too often I hope...

Regards

Ron Deen@home

"Stear, Bo" wrote:

> I suspected as much.  Is there anything special about savealls that span
more than one disk?  just copy the directories to multiple disks however
they may fit?
>
> -Original Message-
> From: David Johnson [mailto:[EMAIL PROTECTED]]
> Sent: Friday, May 04, 2001 7:45 AM
> To: Foxboro DCS Mail List
> Subject: Re: Speaking of Save_All
>
> Bo,
>
> You should be able to do a cp -r on the directory that you put the
save-all in.
>
> If the save_all command for CP3001 was:
> save_all CP3001 /tmp/CP3001
>
> Insert a BLANK FORMATTED Solaris diskette
> Mount it on /f0
> cp -r /tmp/CP3001/* /f0
>
> and that should do it.
>
> David
>
> ---
> This list is neither sponsored nor endorsed by the Foxboro Company. All
> postings from this list are the work of list subscribers and no warranty
> is made or implied as to the accuracy of any information disseminated
> through this medium. By subscribing to this list you agree to hold the
> list sponsor(s) blameless for any and all mishaps which might occur due to
> your application of information received from this mailing list.
>
> To be removed from this list, send mail to
> [EMAIL PROTECTED]
> with "unsubscribe foxboro" in the Subject. Or, send any mail to
> [EMAIL PROTECTED]
>
> ---
> This list is neither sponsored nor endorsed by the Foxboro Company. All
> postings from this list are the work of list subscribers and no warranty
> is made or implied as to the accuracy of any information disseminated
> through this medium. By subscribing to this list you agree to hold the
> list sponsor(s) blameless for any and all mishaps which might occur due to
> your application of information received from this mailing list.
>
> To be removed from this list, send mail to
> [EMAIL PROTECTED]
> with "unsubscribe foxboro" in the Subject. Or, send any mail to
> [EMAIL PROTECTED]


---
This list is neither sponsored nor endorsed by the Foxboro Company. All 
postings from this list are the work of list subscribers and no warranty 
is made or implied as to the accuracy of any information disseminated 
through this medium. By subscribing to this list you agree to hold the 
list sponsor(s) blameless for any and all mishaps which might occur due to 
your application of information received from this mailing list.

To be removed from this list, send mail to 
[EMAIL PROTECTED] 
with "unsubscribe foxboro" in the Subject. Or, send any mail to
[EMAIL PROTECTED]

---
This list is neither sponsored

Speaking of Save_All

[Stear, Bo]

I can't seem to locate the helpful hint that describes how to put these ICC API 
created save alls that are in a file on the hard disk onto a loadable diskette.  
Anyone know where that is?

---
This list is neither sponsored nor endorsed by the Foxboro Company. All 
postings from this list are the work of list subscribers and no warranty 
is made or implied as to the accuracy of any information disseminated 
through this medium. By subscribing to this list you agree to hold the 
list sponsor(s) blameless for any and all mishaps which might occur due to 
your application of information received from this mailing list.

To be removed from this list, send mail to 
[EMAIL PROTECTED] 
with "unsubscribe foxboro" in the Subject. Or, send any mail to
[EMAIL PROTECTED]

RE: Speaking of Save_All

[Stear, Bo]

I suspected as much.  Is there anything special about savealls that span more than one 
disk?  just copy the directories to multiple disks however they may fit?

-Original Message-
From: David Johnson [mailto:[EMAIL PROTECTED]]
Sent: Friday, May 04, 2001 7:45 AM
To: Foxboro DCS Mail List
Subject: Re: Speaking of Save_All


Bo,

You should be able to do a cp -r on the directory that you put the save-all in.

If the save_all command for CP3001 was:
save_all CP3001 /tmp/CP3001

Insert a BLANK FORMATTED Solaris diskette
Mount it on /f0
cp -r /tmp/CP3001/* /f0

and that should do it.

David





---
This list is neither sponsored nor endorsed by the Foxboro Company. All 
postings from this list are the work of list subscribers and no warranty 
is made or implied as to the accuracy of any information disseminated 
through this medium. By subscribing to this list you agree to hold the 
list sponsor(s) blameless for any and all mishaps which might occur due to 
your application of information received from this mailing list.

To be removed from this list, send mail to 
[EMAIL PROTECTED] 
with "unsubscribe foxboro" in the Subject. Or, send any mail to
[EMAIL PROTECTED]

---
This list is neither sponsored nor endorsed by the Foxboro Company. All 
postings from this list are the work of list subscribers and no warranty 
is made or implied as to the accuracy of any information disseminated 
through this medium. By subscribing to this list you agree to hold the 
list sponsor(s) blameless for any and all mishaps which might occur due to 
your application of information received from this mailing list.

To be removed from this list, send mail to 
[EMAIL PROTECTED] 
with "unsubscribe foxboro" in the Subject. Or, send any mail to
[EMAIL PROTECTED]

RE: /etc/wplns and /etc/aplns or Sigh... I fired off without thin king

[Stear, Bo]

Yeah, just put it in the User Notes.

-Original Message-
From: Johnson, Alex (Foxboro) [mailto:[EMAIL PROTECTED]]
Sent: Thursday, May 03, 2001 12:50 PM
To: Foxboro DCS Mail List
Subject: RE: /etc/wplns and /etc/aplns or Sigh... I fired off without
thin king


I forgot about AWs. Sigh...

I'm in the UK, think I can blame jet lag?


Regards,


Alex Johnson
10707 Haddington
Houston, TX 77043
713.722.2859 (office)
713.722.2700 (switchboard)
713.932.0222 (fax)
[EMAIL PROTECTED]  


-Original Message-
From:   Ron Deen [SMTP:[EMAIL PROTECTED]]
Sent:   Thursday, May 03, 2001 6:41 PM
To: Foxboro DCS Mail List
Subject:Re: /etc/wplns and /etc/aplns

The /etc/wplns file contains the logical names of the WP's on your
system. The
/etc/aplns contains (you might have guessed) the logical names of
the AP in you
system.
If you have only AP's and WP's you would normally use the letterbug
as the
logical name.
If you have AW's you have a problem: the AW containss a logical AP
AND a logical
WP and only one can be be letterbug name. This is why you may see
"strange "
names on you system. Some time you can have a letterbug AW0101 which
will have
aplns: AW0101 and wplns: AWWP01 for instance.

Solved problem??

Ron Deen

Stan Brown wrote:

> I have some utilites thta check varios system stauses on a given
Foxboro
> node.
>
> I am trying to deploy these on a newly installed node, here. These
utilites
> use the files /etc/wplns and /etc/aplns to determine what
computers are
> supposed to exist on the node.
>
> On this node there seem to be 2 entries for non existent machines
in
> /etc/wplns. Should this not be a reliable way to determine this?
>
> --
> Stan Brown [EMAIL PROTECTED]
843-745-3154
> Charleston SC.
> --
> Windows 98: n.
> useless extension to a minor patch release for 32-bit
extensions and
> a graphical shell for a 16-bit patch to an 8-bit operating
system
> originally coded for a 4-bit microprocessor, written by a
2-bit
> company that can't stand for 1 bit of competition.
> -
> (c) 2000 Stan Brown.  Redistribution via the Microsoft Network is
prohibited.
>
>
---
> This list is neither sponsored nor endorsed by the Foxboro
Company. All
> postings from this list are the work of list subscribers and no
warranty
> is made or implied as to the accuracy of any information
disseminated
> through this medium. By subscribing to this list you agree to hold
the
> list sponsor(s) blameless for any and all mishaps which might
occur due to
> your application of information received from this mailing list.
>
> To be removed from this list, send mail to
> [EMAIL PROTECTED]
> with "unsubscribe foxboro" in the Subject. Or, send any mail to
> [EMAIL PROTECTED]



---
This list is neither sponsored nor endorsed by the Foxboro Company.
All 
postings from this list are the work of list subscribers and no
warranty 
is made or implied as to the accuracy of any information
disseminated 
through this medium. By subscribing to this list you agree to hold
the 
list sponsor(s) blameless for any and all mishaps which might occur
due to 
your application of information received from this mailing list.

To be removed from this list, send mail to 
[EMAIL PROTECTED] 
with "unsubscribe foxboro" in the Subject. Or, send any mail to
[EMAIL PROTECTED]

---
This list is neither sponsored nor endorsed by the Foxboro Company. All 
postings from this list are the work of list subscribers and no warranty 
is made or implied as to the accuracy of any information disseminated 
through this medium. By subscribing to this list you agree to hold the 
list sponsor(s) blameless for any and all mishaps which might occur due to 
your application of information received from this mailing list.

To be removed from this list, send mail to 
[EMAIL PROTECTED] 
with "unsubscribe foxboro" in the Subject. Or, send any mail to
[EMAIL PROTECTED]

---
This list is neither sponsored nor endorsed by the Foxboro Company. All 
postings from this list are the work of list subscribers and no warranty 
is made or implied as to the accuracy of any information disseminated 
through this medium. By subscribing to this list you agree to hold the 
list

RE: Remote Displays using Exceed

[Stear, Bo]

We're not running Windows 2000 but here are some hints
use RLOGIN method
we remove the .profile dm startup from /opt/ia and use it in a command instead so the 
command in Xstart for exceed should say:
exec /opt/ia/whateveryounamedthe.profile
The other important setting is in the 'Other' settings where you need to put -1 for 
the Close (sed.) timeout.
Hope this helps.

-Original Message-
From: Joe Gale (MP) [mailto:[EMAIL PROTECTED]]
Sent: Thursday, May 03, 2001 7:27 AM
To: Foxboro DCS Mail List (E-mail)
Subject: Remote Displays using Exceed


We have been using exceed for years to open remote display managers using
the telnet start method without much for problems.  The IT people have been
upgrading the PC's in the plant with new PC's that are running Windows2000
and have been having problems opening a DM after installing exceed.  Several
have worked by installing exceed while logged in as Power User, while some
didn't work that way either.  The error they get is a "connection closed(3)"
when trying to open a DM.  They are able to open a x-window into another
application (a unit optimization program) running on a non Foxboro sun box
without a problem.  The new installs are using the same xstart and xconfig
setups as the older installs are using.  Does anyone have any ideas on what
may be the conflict here?

Thank You,

Joe Gale

DCS Administrator
Minnesota Power
Boswell Energy Center

---
This list is neither sponsored nor endorsed by the Foxboro Company. All 
postings from this list are the work of list subscribers and no warranty 
is made or implied as to the accuracy of any information disseminated 
through this medium. By subscribing to this list you agree to hold the 
list sponsor(s) blameless for any and all mishaps which might occur due to 
your application of information received from this mailing list.

To be removed from this list, send mail to 
[EMAIL PROTECTED] 
with "unsubscribe foxboro" in the Subject. Or, send any mail to
[EMAIL PROTECTED]

---
This list is neither sponsored nor endorsed by the Foxboro Company. All 
postings from this list are the work of list subscribers and no warranty 
is made or implied as to the accuracy of any information disseminated 
through this medium. By subscribing to this list you agree to hold the 
list sponsor(s) blameless for any and all mishaps which might occur due to 
your application of information received from this mailing list.

To be removed from this list, send mail to 
[EMAIL PROTECTED] 
with "unsubscribe foxboro" in the Subject. Or, send any mail to
[EMAIL PROTECTED]

Asynchronous Memory Errors

[Stear, Bo]

Good day all.

I am trying to gather as much information as I can to help analyze persistent 
Asynchronous Memory Error reboots on some, if not all, of our AP51B and WP51B boxes.  
These are fairly rare reboots and usually are not hard failures.  The symptom is 
simple, an AP, AW, or WP reboots without warning.  the /var/adm/messages file contains 
a message that states a Panic dump was made, the Asynchronous Memory Error was the 
reason and also lists the offending memory address.  As far as I can remember, this 
problem has existed since the very first 'B' box was installed in our plant.  Now, 
with nearly 100 of them in service, we see altogether too many of them over a years 
time.  Since we have such a large number of 'B' boxes,  it appears to Foxboro that we 
here at PPG are seeing more of these faults than the rest of the customer base (thats 
YOU).  But I wonder???

If you would be so kind, please answer the following questions:

1.  Have you ever experienced this failure?

If so, please continue:

2.  On average, how many times per year?
3.  How many 'B' boxes do you have in service?
4.  What method have you been using to repair (reboot, replace cimms, replace 'B' box, 
etc.)

Thanks to all who participate...
Bo


---
This list is neither sponsored nor endorsed by the Foxboro Company. All 
postings from this list are the work of list subscribers and no warranty 
is made or implied as to the accuracy of any information disseminated 
through this medium. By subscribing to this list you agree to hold the 
list sponsor(s) blameless for any and all mishaps which might occur due to 
your application of information received from this mailing list.

To be removed from this list, send mail to 
[EMAIL PROTECTED] 
with "unsubscribe foxboro" in the Subject. Or, send any mail to
[EMAIL PROTECTED]

Daylight Savings

[Stear, Bo]

How many, if any, of you users either do NOT change to daylight savings time or know 
some other company what does not.  We are considering not following time changes for 
DST since there are still so many persistent problems with I/A when moving the clock 
backwards.


---
This list is neither sponsored nor endorsed by the Foxboro Company. All 
postings from this list are the work of list subscribers and no warranty 
is made or implied as to the accuracy of any information disseminated 
through this medium. By subscribing to this list you agree to hold the 
list sponsor(s) blameless for any and all mishaps which might occur due to 
your application of information received from this mailing list.

To be removed from this list, send mail to 
[EMAIL PROTECTED] 
with "unsubscribe foxboro" in the Subject. Or, send any mail to
[EMAIL PROTECTED]

RE: Failed SaveAll -- the rest of the story

[Stear, Bo]

This is the exact procedure we have used and it does work most of the time.  Get into 
check_db_sync.  It will tell you exactly where you are out of sync.  I run them 
periodically just to be sure all is well.

For the rest of you who have been faithfully pounding me into the ground, it's never 
too late to teach an old dog something new.  I'm reconsidering SOME of my feelings 
about Automatic Save-Alls and am experimenting with triggering save-alls whenever 
FoxCTS (Change Tracking Software) detects a checkpoint containing valid changes.  
Apologies to Duc, I'm pirating some of his script.

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: Friday, April 06, 2001 1:46 PM
To: [EMAIL PROTECTED]
Subject: RE: Failed SaveAll -- the rest of the story


Thanks to all for all of your helpful suggestions.

Thanks to Alex for offering to examine my control database. Unfortunately,
his prognosis ("It's fried!") was not what I wanted to hear.

Thanks to Bo for his suggestion of using check_db_sync. I didn't get around
to using it, but I'll have to make a note of checking into it before the
next disaster drill. (And despite Bo's misgiving about automating the
SaveAll job, I'll continue running this weekly job. I just have to do a
better job of raising awareness among our group as to all the things I'm
doing behind the scene. And to just say no!)

Here's how we fix our problem:

I'm fortunate to have the old hard drive for the host AW still sitting
around since the last upgrade. Even though it was at v6.1, it's good enough
for our purpose. I booted it up in an off-line node along with the CP in
question (20CP02). I then did a LoadAll using a good SaveAll from two weeks
back. Then it's just grunt work of comparing the list of blocks in the
compounds between the off-line CP versus the real-life CP. We had to delete
a compound and add a block to another compound to make the off-line CP match
the on-line one.

At that point, I copied all of the files in /opt/fox/ciocfg/20CP02 (workfile
and all the .O files) from the off-line AW to the real-life system, did an
upload and shrink. Then I  verified that we now could do a SaveAll. I
further verified that that SaveAll is good by loading it back to the
off-line CP. Everything is hunky-dory without having to initialize and
reboot the CP.

Hope this may be of help to somebody who may end up in the same dire strait
some day.

Regards,

Duc

-- 
Duc M. Do
Process Control Systems
Dow Corning, Carrollton Plant
Carrollton, KY, US

_
This message has been checked for all known viruses by the 
MessageLabs Virus Control Centre. For further information visit
http://www.messagelabs.com/stats.asp


---
This list is neither sponsored nor endorsed by the Foxboro Company. All 
postings from this list are the work of list subscribers and no warranty 
is made or implied as to the accuracy of any information disseminated 
through this medium. By subscribing to this list you agree to hold the 
list sponsor(s) blameless for any and all mishaps which might occur due to 
your application of information received from this mailing list.

To be removed from this list, send mail to 
[EMAIL PROTECTED] 
with "unsubscribe foxboro" in the Subject. Or, send any mail to
[EMAIL PROTECTED]

---
This list is neither sponsored nor endorsed by the Foxboro Company. All 
postings from this list are the work of list subscribers and no warranty 
is made or implied as to the accuracy of any information disseminated 
through this medium. By subscribing to this list you agree to hold the 
list sponsor(s) blameless for any and all mishaps which might occur due to 
your application of information received from this mailing list.

To be removed from this list, send mail to 
[EMAIL PROTECTED] 
with "unsubscribe foxboro" in the Subject. Or, send any mail to
[EMAIL PROTECTED]

RE: Failed SaveAll

[Stear, Bo]

Having gone from bad to worse myself, I offer consolation...

Some answers that may help:

1.  See if you have a 'check_sync' directory in /opt/fox/bin/tools.  If so, this 
directory contains some CP database utilities.  I suggest running 'check_db_sync 
' on the offending CP.  This will tell you whether you have any possibility of 
recovering your database.  The odds are actually pretty slim, but if you're lucky, 
there are friendly folks at Foxboro that may be able to recover your database.

2.  Given no option to recover, a clean Initialize, reboot, load-all will must 
certainly get things back on track if you can afford to do so.

3.  I have long been an anti-proponent for automated save-alls and even checkpoints.  
Your quandry is one of the best examples I can give to avoid automating something so 
important as your control database backups.

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: Thursday, April 05, 2001 12:29 PM
To: [EMAIL PROTECTED]
Subject: Failed SaveAll


warning: long message
-

Hi folks,

I have a CP (CP-40) that has its control database corrupted when a person
answered Yes when presented with the "Database locked. Override?" dialogue
box.

A little background: I schedule a weekly cron job to perform SaveAll on all
of our CPs using the ICCAPI save_all command. As luck would have it, this
person was called in on a Sunday to fix a sequence problem, and he tried to
open a CIOCFG session on this CP while the ICCAPI save_all was running. When
presented with the "Database locked. Override?" question, he didn't hesitate
long, reasoning that it was Sunday and nobody would be working on that CP,
must be a mistake. Once in the control session, he still couldn't connect to
the CP so he rebooted it.

Since then, I have not been able to perform a good SaveAll for this CP.
Using the CIOCFG interface the SaveAll appears to run successfully, but I
can't perform a LoadAll with the resulting disk (to an off-line CP), I keep
getting "Invalid block type" error for each of the compounds in this CP.
Using the ICCAPI save_all command always resulted in a failure message with
the following text in the /tmp/output* files (at different times after
trying different things to mitigate the problem):

04AW01# more /tmp/output*
FAIL 3 save 20CP02!: Wed Mar 28 16:27:01 2001 -8 Save cmd: no path name
arg

04AW01# more /tmp/output*
FAIL 2 getorder 20CP02!: Thu Mar 29 15:52:50 2001 -15 Get compound order
cmd
: ICCget error: class= 20 error= 4 text= load_wrk: fread error

04AW01# more /tmp/output*
FAIL 4 save 20CP02!20CP02_STA: Fri Mar 30 09:08:34 2001 -8 Save cmd: no
path
 name arg

BTW, I can do an upload for this CP and the workfile appears to be in good
condition (at least good enough so that I can see all the compounds, blocks,
and parameters while in a CIOCFG session). And the CP is still running okay
as we speak.

Questions:

1. What are my options in getting a good SaveAll for this CP?

2. If I have no option, would initializing/rebooting/reloading it with a
good SaveAll (from 2 weeks back) get me out of this jam?

3. Has anybody encountered problem similar to this, and what's your remedy?

Thanks for any thought and help.

Duc

-- 
Duc M. Do
Process Control Systems
Dow Corning, Carrollton Plant
Carrollton, KY, US

_
This message has been checked for all known viruses by the 
MessageLabs Virus Control Centre. For further information visit
http://www.messagelabs.com/stats.asp


---
This list is neither sponsored nor endorsed by the Foxboro Company. All 
postings from this list are the work of list subscribers and no warranty 
is made or implied as to the accuracy of any information disseminated 
through this medium. By subscribing to this list you agree to hold the 
list sponsor(s) blameless for any and all mishaps which might occur due to 
your application of information received from this mailing list.

To be removed from this list, send mail to 
[EMAIL PROTECTED] 
with "unsubscribe foxboro" in the Subject. Or, send any mail to
[EMAIL PROTECTED]

---
This list is neither sponsored nor endorsed by the Foxboro Company. All 
postings from this list are the work of list subscribers and no warranty 
is made or implied as to the accuracy of any information disseminated 
through this medium. By subscribing to this list you agree to hold the 
list sponsor(s) blameless for any and all mishaps which might occur due to 
your application of information received from this mailing list.

To be removed from this list, send mail to 
[EMAIL PROTECTED] 
with "unsubscribe foxboro" in the Subject. Or, send any mail to
[EMAIL PROTECTED]

RE: Version 4.3 to 6.2.1 upgrade question

[Stear, Bo]

That is, Foxboro Unconditionally Backs All Releases..

-Original Message-
From: Julie Monsour [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, March 21, 2001 1:13 PM
To: Foxboro DCS Mail List
Subject: Re: Version 4.3 to 6.2.1 upgrade question


hmmm...Well, maybe "adventure" was a poor choice for a word, then.

- Original Message -----
From: "Stear, Bo" <[EMAIL PROTECTED]>
To: "'Foxboro DCS Mail List'" <[EMAIL PROTECTED]>
Sent: Wednesday, March 21, 2001 10:29 AM
Subject: RE: Version 4.3 to 6.2.1 upgrade question


> According to Websters:
>
> Adventure (ad-ven'tur), n. an event the issue of which is determined by
chance: v.t. to hazard or risk.
>
> Hmmm, risk, hazard, chance... gimme a break!
>
>
> -Original Message-
> From: Julie Monsour [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, March 21, 2001 8:29 AM
> To: Foxboro DCS Mail List
> Subject: Re: Version 4.3 to 6.2.1 upgrade question
>
>
> Where's your sense of adventure, Bo?  Foxview is GREAT!
>
> Julie Monsour
>
> - Original Message -
> From: "Stear, Bo" <[EMAIL PROTECTED]>
> To: "'Foxboro DCS Mail List'" <[EMAIL PROTECTED]>
> Sent: Wednesday, March 21, 2001 7:46 AM
> Subject: RE: Version 4.3 to 6.2.1 upgrade question
>
>
> > It will be a dead heat as to whether you or we are the last to migrate
to
> FoxView
> >
> > -Original Message-
> > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
> > Sent: Wednesday, March 21, 2001 7:36 AM
> > To: [EMAIL PROTECTED]
> > Subject: RE: Version 4.3 to 6.2.1 upgrade question
> >
> >
> > Jim,
> >
> > We did an upgrade like yours last year (with a slight difference, we
went
> > from 6.1 to 6.2.1 -- for all practical purposes, 4.3 and 6.1 are the
> same).
> > Here are our take on your questions:
> >
> > 1. No, the nodes can be converted individually. Foxboro recommends that
> you
> > upgrade the node where CSA resides first. Luckily it works out for us
> > without having to move the CSA server to the first node to be converted.
> >
> > 2. Yes, most definitely. We'll be the last system to be forced to
migrate
> to
> > FoxView.
> >
> > 3. Again, yes. Legacy historians work fine.
> >
> > 4. We did this as a Day 0 install, so we reboot the CPs anyway. It
didn't
> > make any difference to us if the CP images were new or not.
> >
> > Duc
> >
> > --
> > Duc M. Do
> > Process Control Systems
> > Dow Corning, Carrollton Plant
> > Carrollton, KY, US
> >
> >
> > -Original Message-
> > From: James Kahlden [mailto:[EMAIL PROTECTED]]
> > Sent: Wednesday, March 21, 2001 8:14 AM
> > To: [EMAIL PROTECTED]
> > Subject: Version 4.3 to 6.2.1 upgrade question
> >
> >
> > Hello List,
> >
> > We are looking at updating our version 4.3 system to version 6.2.1 in
> order
> > to expand our system to include the new CP60.  We currently use
AW/WP51B's
> > with Display Manager and the Legacy Historian.  Our CP's are fault
> tolerant
> > CP40A's.  We have 5 nodes connected via Carrier Band LAN.  We can not
shut
> > down all nodes at once, since this system controls two 600 megawatt coal
> > fired power generators.
> >
> > Questions?
> >
> > 1. Do all of the nodes need to be converted at one time to 6.2.1 or can
> some
> > nodes exist at 4.3  while part of the node is at 6.2.1?
> >
> > 2. Can we continue to use our Display Manager displays, or do we have to
> > change to the Fox View displays?
> >
> > 3. Can we continue to use the Legacy Historian at version 6.2.1, or do
we
> > have to convert to the AIM historian?
> >
> > 4. Is there a different CP image at version 6.2.1 that requires a reboot
> of
> > the CP for this upgrade?
> >
> > Thanks for any guidance that you can give, as we are looking to see what
> > windows of opportunity we have for doing this type of upgrade.
> >
> > Jim Kahlden
> > [EMAIL PROTECTED]
> >
> > ---
> > This list is neither sponsored nor endorsed by the Foxboro Company. All
> > postings from this list are the work of list subscribers and no warranty
> > is made or implied as to the accuracy of any information disseminated
> > through this medium. By subscribing to this list you agree to hold the
> > list sponsor(s) blameless for any and all mishaps which might occur due
to
> > your application of information rece

RE: Version 4.3 to 6.2.1 upgrade question

[Stear, Bo]

Perhaps FUBAR?

-Original Message-
From: Julie Monsour [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, March 21, 2001 1:13 PM
To: Foxboro DCS Mail List
Subject: Re: Version 4.3 to 6.2.1 upgrade question


hmmm...Well, maybe "adventure" was a poor choice for a word, then.

- Original Message -----
From: "Stear, Bo" <[EMAIL PROTECTED]>
To: "'Foxboro DCS Mail List'" <[EMAIL PROTECTED]>
Sent: Wednesday, March 21, 2001 10:29 AM
Subject: RE: Version 4.3 to 6.2.1 upgrade question


> According to Websters:
>
> Adventure (ad-ven'tur), n. an event the issue of which is determined by
chance: v.t. to hazard or risk.
>
> Hmmm, risk, hazard, chance... gimme a break!
>
>
> -Original Message-
> From: Julie Monsour [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, March 21, 2001 8:29 AM
> To: Foxboro DCS Mail List
> Subject: Re: Version 4.3 to 6.2.1 upgrade question
>
>
> Where's your sense of adventure, Bo?  Foxview is GREAT!
>
> Julie Monsour
>
> - Original Message -
> From: "Stear, Bo" <[EMAIL PROTECTED]>
> To: "'Foxboro DCS Mail List'" <[EMAIL PROTECTED]>
> Sent: Wednesday, March 21, 2001 7:46 AM
> Subject: RE: Version 4.3 to 6.2.1 upgrade question
>
>
> > It will be a dead heat as to whether you or we are the last to migrate
to
> FoxView
> >
> > -Original Message-
> > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
> > Sent: Wednesday, March 21, 2001 7:36 AM
> > To: [EMAIL PROTECTED]
> > Subject: RE: Version 4.3 to 6.2.1 upgrade question
> >
> >
> > Jim,
> >
> > We did an upgrade like yours last year (with a slight difference, we
went
> > from 6.1 to 6.2.1 -- for all practical purposes, 4.3 and 6.1 are the
> same).
> > Here are our take on your questions:
> >
> > 1. No, the nodes can be converted individually. Foxboro recommends that
> you
> > upgrade the node where CSA resides first. Luckily it works out for us
> > without having to move the CSA server to the first node to be converted.
> >
> > 2. Yes, most definitely. We'll be the last system to be forced to
migrate
> to
> > FoxView.
> >
> > 3. Again, yes. Legacy historians work fine.
> >
> > 4. We did this as a Day 0 install, so we reboot the CPs anyway. It
didn't
> > make any difference to us if the CP images were new or not.
> >
> > Duc
> >
> > --
> > Duc M. Do
> > Process Control Systems
> > Dow Corning, Carrollton Plant
> > Carrollton, KY, US
> >
> >
> > -Original Message-
> > From: James Kahlden [mailto:[EMAIL PROTECTED]]
> > Sent: Wednesday, March 21, 2001 8:14 AM
> > To: [EMAIL PROTECTED]
> > Subject: Version 4.3 to 6.2.1 upgrade question
> >
> >
> > Hello List,
> >
> > We are looking at updating our version 4.3 system to version 6.2.1 in
> order
> > to expand our system to include the new CP60.  We currently use
AW/WP51B's
> > with Display Manager and the Legacy Historian.  Our CP's are fault
> tolerant
> > CP40A's.  We have 5 nodes connected via Carrier Band LAN.  We can not
shut
> > down all nodes at once, since this system controls two 600 megawatt coal
> > fired power generators.
> >
> > Questions?
> >
> > 1. Do all of the nodes need to be converted at one time to 6.2.1 or can
> some
> > nodes exist at 4.3  while part of the node is at 6.2.1?
> >
> > 2. Can we continue to use our Display Manager displays, or do we have to
> > change to the Fox View displays?
> >
> > 3. Can we continue to use the Legacy Historian at version 6.2.1, or do
we
> > have to convert to the AIM historian?
> >
> > 4. Is there a different CP image at version 6.2.1 that requires a reboot
> of
> > the CP for this upgrade?
> >
> > Thanks for any guidance that you can give, as we are looking to see what
> > windows of opportunity we have for doing this type of upgrade.
> >
> > Jim Kahlden
> > [EMAIL PROTECTED]
> >
> > ---
> > This list is neither sponsored nor endorsed by the Foxboro Company. All
> > postings from this list are the work of list subscribers and no warranty
> > is made or implied as to the accuracy of any information disseminated
> > through this medium. By subscribing to this list you agree to hold the
> > list sponsor(s) blameless for any and all mishaps which might occur due
to
> > your application of information received from this mailing list.
> >
> &g

RE: Version 4.3 to 6.2.1 upgrade question - Why not FoxView?

[Stear, Bo]

Since you asked seriously, I'll respond properly.

We that have had Foxboro I/A on our sites for many years had to deal with an 
especially slow call up time for displays in the early days, something on the order of 
15 seconds or more.  As time went by, the DM was improved and the hardware was updated 
to faster processors and now the DM is a real zinger as far as speed is concerned.  
Early releases of Foxview were an instant reminder of the slow speed of the DM in its 
early stages because the call up time for it was something on the order of 15 seconds 
or more on the, then prevalent, WP51 Style 'B' workstations.  Even now, the current 
Foxview is 3 to 5 times slower in call up time than the DM on the 'B' style 
workstations.  Since we have some 80 style 'B' workstations in house now, even the 
very best advantage upgrade to a faster processor would be too expensive and so is not 
possible.  If we were to switch to Foxview today, I expect that our operators would 
soon hang me from some pipe rack by my thumbs because they are used !
to the
speed.

SO, I do not dislike Foxview for any particularly detrimental reason and others that 
agree with me probably do so for the same reasons (but they should speak for 
themselves).

-Original Message-
From: Anderson, Gary T(Z02256) [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, March 21, 2001 9:33 AM
To: 'Foxboro DCS Mail List'
Subject: RE: Version 4.3 to 6.2.1 upgrade question - Why not FoxView?



I have to jump in here and ask why the reluctance to use FoxView? What don't
I know?  What should I know?

We are a relatively new IA site and have never used the old Display Manager.
Other than potential processor loading of older hardware and converting the
displays, I can't see any reason not to use FoxView.  The old style look of
the Display Manager was enough incentive to cause us to start with FoxView.


Gary Anderson
Arizona Public Service

-Original Message-
From: Julie Monsour [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, March 21, 2001 7:29 AM
To: Foxboro DCS Mail List
Subject: Re: Version 4.3 to 6.2.1 upgrade question


Where's your sense of adventure, Bo?  Foxview is GREAT!

Julie Monsour

- Original Message -
From: "Stear, Bo" <[EMAIL PROTECTED]>
To: "'Foxboro DCS Mail List'" <[EMAIL PROTECTED]>
Sent: Wednesday, March 21, 2001 7:46 AM
Subject: RE: Version 4.3 to 6.2.1 upgrade question


> It will be a dead heat as to whether you or we are the last to migrate to
FoxView
>
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, March 21, 2001 7:36 AM
> To: [EMAIL PROTECTED]
> Subject: RE: Version 4.3 to 6.2.1 upgrade question
>
>
> Jim,
>
> We did an upgrade like yours last year (with a slight difference, we went
> from 6.1 to 6.2.1 -- for all practical purposes, 4.3 and 6.1 are the
same).
> Here are our take on your questions:
>
> 1. No, the nodes can be converted individually. Foxboro recommends that
you
> upgrade the node where CSA resides first. Luckily it works out for us
> without having to move the CSA server to the first node to be converted.
>
> 2. Yes, most definitely. We'll be the last system to be forced to migrate
to
> FoxView.
>
> 3. Again, yes. Legacy historians work fine.
>
> 4. We did this as a Day 0 install, so we reboot the CPs anyway. It didn't
> make any difference to us if the CP images were new or not.
>
> Duc
>
> --
> Duc M. Do
> Process Control Systems
> Dow Corning, Carrollton Plant
> Carrollton, KY, US
>
>
> -Original Message-
> From: James Kahlden [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, March 21, 2001 8:14 AM
> To: [EMAIL PROTECTED]
> Subject: Version 4.3 to 6.2.1 upgrade question
>
>
> Hello List,
>
> We are looking at updating our version 4.3 system to version 6.2.1 in
order
> to expand our system to include the new CP60.  We currently use AW/WP51B's
> with Display Manager and the Legacy Historian.  Our CP's are fault
tolerant
> CP40A's.  We have 5 nodes connected via Carrier Band LAN.  We can not shut
> down all nodes at once, since this system controls two 600 megawatt coal
> fired power generators.
>
> Questions?
>
> 1. Do all of the nodes need to be converted at one time to 6.2.1 or can
some
> nodes exist at 4.3  while part of the node is at 6.2.1?
>
> 2. Can we continue to use our Display Manager displays, or do we have to
> change to the Fox View displays?
>
> 3. Can we continue to use the Legacy Historian at version 6.2.1, or do we
> have to convert to the AIM historian?
>
> 4. Is there a different CP image at version 6.2.1 that requires a reboot
of
> the CP for this upgrade?
>
> Thanks for any guidance that you can 

RE: Version 4.3 to 6.2.1 upgrade question

[Stear, Bo]

According to Websters:

Adventure (ad-ven'tur), n. an event the issue of which is determined by chance: v.t. 
to hazard or risk.

Hmmm, risk, hazard, chance... gimme a break!


-Original Message-
From: Julie Monsour [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, March 21, 2001 8:29 AM
To: Foxboro DCS Mail List
Subject: Re: Version 4.3 to 6.2.1 upgrade question


Where's your sense of adventure, Bo?  Foxview is GREAT!

Julie Monsour

- Original Message -----
From: "Stear, Bo" <[EMAIL PROTECTED]>
To: "'Foxboro DCS Mail List'" <[EMAIL PROTECTED]>
Sent: Wednesday, March 21, 2001 7:46 AM
Subject: RE: Version 4.3 to 6.2.1 upgrade question


> It will be a dead heat as to whether you or we are the last to migrate to
FoxView
>
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, March 21, 2001 7:36 AM
> To: [EMAIL PROTECTED]
> Subject: RE: Version 4.3 to 6.2.1 upgrade question
>
>
> Jim,
>
> We did an upgrade like yours last year (with a slight difference, we went
> from 6.1 to 6.2.1 -- for all practical purposes, 4.3 and 6.1 are the
same).
> Here are our take on your questions:
>
> 1. No, the nodes can be converted individually. Foxboro recommends that
you
> upgrade the node where CSA resides first. Luckily it works out for us
> without having to move the CSA server to the first node to be converted.
>
> 2. Yes, most definitely. We'll be the last system to be forced to migrate
to
> FoxView.
>
> 3. Again, yes. Legacy historians work fine.
>
> 4. We did this as a Day 0 install, so we reboot the CPs anyway. It didn't
> make any difference to us if the CP images were new or not.
>
> Duc
>
> --
> Duc M. Do
> Process Control Systems
> Dow Corning, Carrollton Plant
> Carrollton, KY, US
>
>
> -Original Message-
> From: James Kahlden [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, March 21, 2001 8:14 AM
> To: [EMAIL PROTECTED]
> Subject: Version 4.3 to 6.2.1 upgrade question
>
>
> Hello List,
>
> We are looking at updating our version 4.3 system to version 6.2.1 in
order
> to expand our system to include the new CP60.  We currently use AW/WP51B's
> with Display Manager and the Legacy Historian.  Our CP's are fault
tolerant
> CP40A's.  We have 5 nodes connected via Carrier Band LAN.  We can not shut
> down all nodes at once, since this system controls two 600 megawatt coal
> fired power generators.
>
> Questions?
>
> 1. Do all of the nodes need to be converted at one time to 6.2.1 or can
some
> nodes exist at 4.3  while part of the node is at 6.2.1?
>
> 2. Can we continue to use our Display Manager displays, or do we have to
> change to the Fox View displays?
>
> 3. Can we continue to use the Legacy Historian at version 6.2.1, or do we
> have to convert to the AIM historian?
>
> 4. Is there a different CP image at version 6.2.1 that requires a reboot
of
> the CP for this upgrade?
>
> Thanks for any guidance that you can give, as we are looking to see what
> windows of opportunity we have for doing this type of upgrade.
>
> Jim Kahlden
> [EMAIL PROTECTED]
>
> ---
> This list is neither sponsored nor endorsed by the Foxboro Company. All
> postings from this list are the work of list subscribers and no warranty
> is made or implied as to the accuracy of any information disseminated
> through this medium. By subscribing to this list you agree to hold the
> list sponsor(s) blameless for any and all mishaps which might occur due to
> your application of information received from this mailing list.
>
> To be removed from this list, send mail to
> [EMAIL PROTECTED]
> with "unsubscribe foxboro" in the Subject. Or, send any mail to
> [EMAIL PROTECTED]
>
> ---
> This list is neither sponsored nor endorsed by the Foxboro Company. All
> postings from this list are the work of list subscribers and no warranty
> is made or implied as to the accuracy of any information disseminated
> through this medium. By subscribing to this list you agree to hold the
> list sponsor(s) blameless for any and all mishaps which might occur due to
> your application of information received from this mailing list.
>
> To be removed from this list, send mail to
> [EMAIL PROTECTED]
> with "unsubscribe foxboro" in the Subject. Or, send any mail to
> [EMAIL PROTECTED]
>
>


---
This list is neither sponsored nor endorsed by the Foxboro Company. All 
postings from this list are the work of list subscribers 

RE: Version 4.3 to 6.2.1 upgrade question

[Stear, Bo]

It will be a dead heat as to whether you or we are the last to migrate to FoxView

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, March 21, 2001 7:36 AM
To: [EMAIL PROTECTED]
Subject: RE: Version 4.3 to 6.2.1 upgrade question


Jim,

We did an upgrade like yours last year (with a slight difference, we went
from 6.1 to 6.2.1 -- for all practical purposes, 4.3 and 6.1 are the same).
Here are our take on your questions:

1. No, the nodes can be converted individually. Foxboro recommends that you
upgrade the node where CSA resides first. Luckily it works out for us
without having to move the CSA server to the first node to be converted.

2. Yes, most definitely. We'll be the last system to be forced to migrate to
FoxView.

3. Again, yes. Legacy historians work fine.

4. We did this as a Day 0 install, so we reboot the CPs anyway. It didn't
make any difference to us if the CP images were new or not.

Duc

-- 
Duc M. Do
Process Control Systems
Dow Corning, Carrollton Plant
Carrollton, KY, US


-Original Message-
From: James Kahlden [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, March 21, 2001 8:14 AM
To: [EMAIL PROTECTED]
Subject: Version 4.3 to 6.2.1 upgrade question


Hello List,

We are looking at updating our version 4.3 system to version 6.2.1 in order
to expand our system to include the new CP60.  We currently use AW/WP51B's
with Display Manager and the Legacy Historian.  Our CP's are fault tolerant
CP40A's.  We have 5 nodes connected via Carrier Band LAN.  We can not shut
down all nodes at once, since this system controls two 600 megawatt coal
fired power generators.

Questions?

1. Do all of the nodes need to be converted at one time to 6.2.1 or can some
nodes exist at 4.3  while part of the node is at 6.2.1?

2. Can we continue to use our Display Manager displays, or do we have to
change to the Fox View displays?

3. Can we continue to use the Legacy Historian at version 6.2.1, or do we
have to convert to the AIM historian?

4. Is there a different CP image at version 6.2.1 that requires a reboot of
the CP for this upgrade?

Thanks for any guidance that you can give, as we are looking to see what
windows of opportunity we have for doing this type of upgrade.

Jim Kahlden
[EMAIL PROTECTED]

---
This list is neither sponsored nor endorsed by the Foxboro Company. All 
postings from this list are the work of list subscribers and no warranty 
is made or implied as to the accuracy of any information disseminated 
through this medium. By subscribing to this list you agree to hold the 
list sponsor(s) blameless for any and all mishaps which might occur due to 
your application of information received from this mailing list.

To be removed from this list, send mail to 
[EMAIL PROTECTED] 
with "unsubscribe foxboro" in the Subject. Or, send any mail to
[EMAIL PROTECTED]

---
This list is neither sponsored nor endorsed by the Foxboro Company. All 
postings from this list are the work of list subscribers and no warranty 
is made or implied as to the accuracy of any information disseminated 
through this medium. By subscribing to this list you agree to hold the 
list sponsor(s) blameless for any and all mishaps which might occur due to 
your application of information received from this mailing list.

To be removed from this list, send mail to 
[EMAIL PROTECTED] 
with "unsubscribe foxboro" in the Subject. Or, send any mail to
[EMAIL PROTECTED]

RE: Version 4.3 to 6.2.1 upgrade question

[Stear, Bo]

-Original Message-
From: James Kahlden [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, March 21, 2001 7:14 AM
To: [EMAIL PROTECTED]
Subject: Version 4.3 to 6.2.1 upgrade question


Hello List,

We are looking at updating our version 4.3 system to version 6.2.1 in order to expand 
our system to include the new CP60.  We currently use AW/WP51B's with Display Manager 
and the Legacy Historian.  Our CP's are fault tolerant CP40A's.  We have 5 nodes 
connected via Carrier Band LAN.  We can not shut down all nodes at once, since this 
system controls two 600 megawatt coal fired power generators.

Questions?
These are the answers as I know them, someone from Foxboro will probably give a more 
detailed answer:

1. Do all of the nodes need to be converted at one time to 6.2.1 or can some nodes 
exist at 4.3  while part of the node is at 6.2.1?
No, but you will have to do some special tricky stuff with the Device Manager.

2. Can we continue to use our Display Manager displays, or do we have to change to the 
Fox View displays?
Yes, you can still use the DM

3. Can we continue to use the Legacy Historian at version 6.2.1, or do we have to 
convert to the AIM historian?
Yes, you can still use the Legacy Historian

4. Is there a different CP image at version 6.2.1 that requires a reboot of the CP for 
this upgrade?
Yes, this is a Day 0 upgrade and requires a CP reboot.

Thanks for any guidance that you can give, as we are looking to see what windows of 
opportunity we have for doing this type of upgrade.

Jim Kahlden
[EMAIL PROTECTED]


---
This list is neither sponsored nor endorsed by the Foxboro Company. All postings from 
this list are the work of list subscribers and no warranty is made or implied as to 
the accuracy of any information disseminated through this medium. By subscribing to 
this list you agree to hold the list sponsor(s) blameless for any and all mishaps 
which might occur due to your application of information received from this mailing 
list.

To be removed from this list, send mail to [EMAIL PROTECTED] 
with "unsubscribe foxboro" in the Subject. Or, send any mail to
[EMAIL PROTECTED]

---
This list is neither sponsored nor endorsed by the Foxboro Company. All 
postings from this list are the work of list subscribers and no warranty 
is made or implied as to the accuracy of any information disseminated 
through this medium. By subscribing to this list you agree to hold the 
list sponsor(s) blameless for any and all mishaps which might occur due to 
your application of information received from this mailing list.

To be removed from this list, send mail to 
[EMAIL PROTECTED] 
with "unsubscribe foxboro" in the Subject. Or, send any mail to
[EMAIL PROTECTED]

RE: Block Scan Time

[Stear, Bo]

A blocks period is not a dependable timekeeper especially if a CP can or ever will go 
into overrun conditions.  Consider the TIMER block instead.

-Original Message-
From: Burnham, Rob C. [mailto:[EMAIL PROTECTED]]
Sent: Thursday, February 01, 2001 2:32 PM
To: 'Foxboro List'
Subject: Block Scan Time


Can a blocks scan time be used
to accurately count? I am trying to
to count elapsed seconds of overflow
on a tank, the scan time for the block
is 1 second and I increment a memory
register by one on each scan.
Is this accurate?

Rob Burnham
P. H. Glatfelter Co.
920 727-2426


---
This list is neither sponsored nor endorsed by the Foxboro Company. All 
postings from this list are the work of list subscribers and no warranty 
is made or implied as to the accuracy of any information disseminated 
through this medium. By subscribing to this list you agree to hold the 
list sponsor(s) blameless for any and all mishaps which might occur due to 
your application of information received from this mailing list.

To be removed from this list, send mail to 
[EMAIL PROTECTED] 
with "unsubscribe foxboro" in the Subject. Or, send any mail to
[EMAIL PROTECTED]

---
This list is neither sponsored nor endorsed by the Foxboro Company. All 
postings from this list are the work of list subscribers and no warranty 
is made or implied as to the accuracy of any information disseminated 
through this medium. By subscribing to this list you agree to hold the 
list sponsor(s) blameless for any and all mishaps which might occur due to 
your application of information received from this mailing list.

To be removed from this list, send mail to 
[EMAIL PROTECTED] 
with "unsubscribe foxboro" in the Subject. Or, send any mail to
[EMAIL PROTECTED]

RE: A request for questions

[Stear, Bo]

Sorry I won't be able to be there to harass you Alex so let me get one in here:

I am always interested in new and deceptive ways to get the display manager to 
do things.  I would probably concentrate on the dmcmd commands, especially the 
differences in syntax between what is used in the AApan file and what can be 
done in a script (via pref) and how to use substitution lists with these two 
methods.

Hope ya'll have fun without me.

-Original Message-
From: Johnson, Alex P (Foxboro) [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, January 09, 2001 11:56 AM
To: Foxboro DCS Mail List
Subject: A request for questions


I've been asked to speak at the 'Gulf Coast User's Group' meeting on Jan
24th. The topic requested is I/A Series Calls.

Since this is a topic that is a little hard to cover in a couple of hours, I
was wondering if you folks had questions in this area. 

My thought was that you folks could summit questions to me and I will (try
to) answer them and present the results at the GCUG meeting and on this
forum.

The calls that most people seem interested in include:

IPC - Inter-process communication. These calls can be used to communicate
between programs and to send/receive standard I/A Series messages, e.g.,
alarms.
OM - Object Manager calls. These are the calls that provide access to I/A
Series process data at the lowest level.
FoxAPI - A suite of APIs that provide access to process data (legacy AIS
calls and new CDX calls), CSA data, and historical data (legacy API and new
API).
Display Manager commands - These are the commands used in Display Manager
scripts.

Any comments? or questions?

Regards,


Alex Johnson
10707 Haddington
Houston, TX 77043
713.722.2859 (office)
713.722.2700 (switchboard)
713.932.0222 (fax)
[EMAIL PROTECTED]  


-Original Message-
From:   Jorge Monsalvo [SMTP:[EMAIL PROTECTED]]
Sent:   Monday, January 08, 2001 9:07 PM
To: Foxboro DCS Mail List
Subject:RE: PI displays

Really it's what i'm looking for. Get object to connect to the PI
database.
but 

- Original Message -
From: Thornton, Dennis (Sudbury) <[EMAIL PROTECTED]>
To: 'Foxboro DCS Mail List' <[EMAIL PROTECTED]>
Sent: Monday, January 08, 2001 12:16 PM
Subject: RE: PI displays


> This method works if you are happy with a bitmap background for
Pi.
> It doesn't give you all of the objects that I want for connection
to the
Pi
> database.
>
> > --
> > From: Murray, Steve[SMTP:[EMAIL PROTECTED]]
> > Reply To: Foxboro DCS Mail List
> > Sent: Monday, January 08, 2001 9:18 AM
> > To: 'Foxboro DCS Mail List'
> > Subject: RE: PI displays
> >
> > Hi Jorge,
> >
> >   If you use Exceed (or something else) and can bring up a
display on a
> > regular personal computer you can copy the display to the
Window's
> > clipboard
> > and then paste it into many different applications.  You can
then
convert
> > the image to something else if you like.
> >
> >   We copy displays into PowerPoint and Word documents all the
time.  You
> > may
> > be able to paste it directly into your PI application as well.
> >
> >   (Alt - Print Screen will copy the current window to the
clipboard in
> > Windows)
> >
> >
> >   Another option may be to use snapshot &/or imagetool on the
Solaris
> > machine to convert a dsiplay - see the man pages on them.  They
are
> > located
> > in the /usr/openwin/bin directories.
> >
> > Stephen Murray
> > Asarco
> >
> > -Original Message-
> > From: Jorge Monsalvo [mailto:[EMAIL PROTECTED]]
> > Sent: Saturday, January 06, 2001 4:08 PM
> > To: 'Foxboro DCS Mail List'
> > Subject: PI displays
> >
> >
> > I'm looking for an utility to convert DM/FV graphics into PI
displays. I
> > mean DM/FV into any "common" format (dxf for example).
> > I think that this thing doesn't exits but any help will be
appreciate
> >
> > Thank you
> >
> > Jorge Monsalvo
> > IVControl S.R.L.
> > Argentina


---
This list is neither sponsored nor endorsed by the Foxboro Company. All 
postings from this list are the work of list subscribers and no warranty 
is made or implied as to the accuracy of any information disseminated 
through this medium. By subscribing to this list you agree to hold the 
list sponsor(s) blameless for any and all mishaps which might occur due to 
your application of information received from this mailing list.

To be removed from this list, send mail to 
[EMAIL PROTECTED

RE: OAJ startup at boot

[Stear, Bo]

FYI

The OAJ startup can be done by editing /usr/fox/wp/data/wp51_gbls.all.  This
is the file used to overwrite the other wp51_glbl files.  If you just
include your modification there you will have one less file to keep uup
with.

-Original Message-
From: Murray, Steve [mailto:[EMAIL PROTECTED]]
Sent: Friday, November 17, 2000 2:35 PM
To: 'Foxboro DCS Mail List'
Subject: RE: OAJ startup at boot



Hi Duc,

  Tanks, I'm editing the init.user files right now.

Stephen

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: Friday, November 17, 2000 1:44 PM
To: [EMAIL PROTECTED]
Subject: RE: OAJ startup at boot


Steve,

I guess it doesn't matter that they appear in both wp51_glbls and init.user.
At least not that I know of. From what I understand, each time the station
is rebooted, a new _glbls file is created in
/usr/fox/wp/data/, and this glbls in corporates setting in
both wp51_glbls and init.user. I guess those settings in init.user have
precedents.

With our latest upgrade from v4.3/6.1 to v6.2.1, I've left the wp51_glbls
file alone and just make my customized settings in init.user and everything
still works, so that's my experience.

Duc

This transmission is for the intended addressee only and is confidential
information. If you have received this transmission in error, please delete
it and notify the sender. The contents of this E-mail are the opinion of the
writer only and are not endorsed by ASARCO Inc. unless expressly stated
otherwise.

---
This list is neither sponsored nor endorsed by the Foxboro Company. All 
postings from this list are the work of list subscribers and no warranty 
is made or implied as to the accuracy of any information disseminated 
through this medium. By subscribing to this list you agree to hold the 
list sponsor(s) blameless for any and all mishaps which might occur due to 
your application of information received from this mailing list.

To be removed from this list, send mail to 
[EMAIL PROTECTED] 
with "unsubscribe foxboro" in the Subject. Or, send any mail to
[EMAIL PROTECTED]

---
This list is neither sponsored nor endorsed by the Foxboro Company. All 
postings from this list are the work of list subscribers and no warranty 
is made or implied as to the accuracy of any information disseminated 
through this medium. By subscribing to this list you agree to hold the 
list sponsor(s) blameless for any and all mishaps which might occur due to 
your application of information received from this mailing list.

To be removed from this list, send mail to 
[EMAIL PROTECTED] 
with "unsubscribe foxboro" in the Subject. Or, send any mail to
[EMAIL PROTECTED]

RE: Variable selection in a sequence

[Stear, Bo]

Can anyone actually believe that Alex Johnson lost his COLON?

-Original Message-
From: Johnson,Alex [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, October 17, 2000 2:07 PM
To: Foxboro DCS Mail List
Cc: Wilfred Kram (E-mail)
Subject: RE: Variable selection in a sequence


Let me try that again. A colon was lost! or MS Outlook messed with my
incoming message. I can't tell:

Here's some sample code for you.

 APP_NAME : SN0001;{ Name of DMC application }
 CNTDWN   : SN0009;{ AOA reference for CNTDWN }

...
 { This stores the destination tag as a string into CNTDWN}

 CNTDWN := APP_NAME,":DMCOP.CNTDWN";

 { This clears the count down timer. Note the use of : and ' }
 { In case you can't see it, the line reads 'colon''single quote''variable
name''colon''equal''zero' }

 :'CNTDWN' := 0;

You can use string variables rather than parameters. I like to use the
parameters as a debugging aid.

Hope this helps.

Regards,

Alex Johnson
10707 Haddington
Houston, TX 77063
713.722.2859(v)
713.722.2700(sb)
713.932.0222(f)
[EMAIL PROTECTED]  


-Original Message-
From:   Johnson,Alex [SMTP:[EMAIL PROTECTED]]
Sent:   Tuesday, October 17, 2000 1:37 PM
To: Foxboro DCS Mail List
Cc: Wilfred Kram (E-mail)
Subject:RE: Variable selection in a sequence

Here's some sample code for you.

APP_NAME : SN0001;{ Name of DMC application }
CNTDWN   : SN0009;{ AOA reference for CNTDWN }

...
{ This stores the destination tag as a string into CNTDWN}
CNTDWN := APP_NAME,":DMCOP.CNTDWN";

{ This clears the count down timer. Note the use of : and ' }
:'CNTDWN' := 0;

You can use string variables rather than parameters. I like to use
the
parameters as a debugging aid.

Hope this helps.

Regards,

Alex Johnson
10707 Haddington
Houston, TX 77063
713.722.2859(v)
713.722.2700(sb)
713.932.0222(f)
[EMAIL PROTECTED]  


-Original Message-
From:   Baltus, C.J.M. [SMTP:[EMAIL PROTECTED]]
Sent:   Tuesday, October 17, 2000 1:27 PM
To: Foxboro DCS mailing list (E-mail)
Cc: Wilfred Kram (E-mail)
Subject:Variable selection in a sequence

Hi All, (I think this is the standard opening)

I will introduce myself first, I am a DCS engineer working
for 2
years with
Foxboro IA, in a small wet country.

I am following this list since I started with Foxboro IA and
I saw
many
problems solved. Now here is my problem (perhaps its a
stupid one,
but I'm
breaking my wooden shoe on it).

I want to make a variable selection in a sequence, its
written in
SFC.

First I made a macro called:
PUMP1 :TEST:GDEV1.AUTDSR
PUMP2 :TEST:GDEV2.AUTDSR

Then I made a variable called:
PUMP and attached to BOOL

In the first selection I want
PUMP := PUMP1;
the following step:
PUMP := TRUE; 


and when I return to the beginning I perhaps want PUMP
select to:
PUMP := PUMP2;
the following step:
PUMP := TRUE;

But what I tried, it didn't work, has someone got a solution
?? This
will be
written for a selection of 32 posibilties 


With Kind Regards,
Cor-Jan Baltus
DCS Engineer

KH-AMEC Engineering
Bergen op Zoom
the Netherlands
* [EMAIL PROTECTED]

---:-)** **---



---
This list is neither sponsored nor endorsed by the Foxboro
Company.
All 
postings from this list are the work of list subscribers and
no
warranty 
is made or implied as to the accuracy of any information
disseminated 
through this medium. By subscribing to this list you agree
to hold
the 
list sponsor(s) blameless for any and all mishaps which
might occur
due to 
your application of information received from this mailing
list.

To be removed from this list, send mail to 
[EMAIL PROTECTED] 
with "unsubscribe foxboro" in the Subject. Or, send any mail
to
[EMAIL PROTECTED]


---
This list is neither sponsored nor endorsed by the Foxboro Com

RE: Rolling average

[Stear, Bo]

Here's a way to do it using a TIMER and an IND block.  You could do without
the timer and just use the WAIT for the period but then you might run into
problems if your CP goes into overrun.

This is set for a flow but will work on anything..

INDEPENDENT_SEQUENCE{***
  **  **
  **   INDEPENDENT SEQUENCE   **
  ** CONTROL BLOCK**
  **  **
  *}

CONSTANTS {*
  * specify any Constants  *
  * in the following format:   *
  **
  * 12_char_name = value ; *
  *}

VARIABLES {*
  * specify any Block Local Variables  *
  * in the following format:   *
  **
  * 12_char_name [ , 12_char_name ] : type;*
  **
  *where type is one of B, I, R, S, S12, S6*
  *}

AVG:R[360];
ICT:I;

USER_LABELS{
  * specify any user labeled parameters*
  *   in one of the following formats: *
  **
  *   10_char_name : BI00nn; n = 01 -- 24  *
  *   10_char_name : BO00nn; n = 01 -- 16  *
  *   10_char_name : BA000n; n =  1 --  4  *
  *   10_char_name : RI00nn; n = 01 -- 15  *
  *   10_char_name : RO00nn; n = 01 -- 15  *
  *   10_char_name : RA000n; n =  1 --  2  *
  *   10_char_name : II000n; n =  1 --  8  *
  *   10_char_name : IO000n; n =  1 --  5  *
  *   10_char_name : IA0001;   *
  *   10_char_name : SN00nn; n = 01 -- 10  *
  *}

FI3050: RI0001; {MEASURED FLOW}
FA3050: RO0001; {AVERAGE FLOW}
CNTIDX: IO0001; {AVERAGER INDEX}
SUM:RO0002; {TEMPORARY SUM}
TIM:RI0002; {10 SECOND TIMER INPUT}
REMOVE: RO0003; {VALUE TO REMOVE FROM SUM}
BTU:RI0003; {ENTERED VALUE FOR BTU}
BTU_VAL: RO0015; {CALCULATED BTU VALUE FOR CURRENT FLOW}

  {*
  * Specify any Subroutines*
  **
  **
  * SUBROUTINE name ( formal arguments ) ; *
  *  VARIABLES  subr. local variables ;*
  *  STATEMENTS*
  *  ; *
  * ENDSUBROUTINE  *
  *}


  {*
  * Specify any*
  *Standard Block Exception Handlers   *
  **
  **
  * BLOCK_EXCEPTION exc_name [ DISABLE ]   *
  *  STATEMENTS*
  *  ; *
  * ENDEXCEPTION   *
  *}


STATEMENTS{*
  *  Specify the statements here   *
  *}

CNTIDX := 1;
AVG := SET_ARRAY(FI3050);
SUM := FI3050 * 360.0;
START_TIMER(::10SECONDS.TIMR1,0.0);
<>
REMOVE := AVG[CNTIDX];
AVG[CNTIDX] := FI3050;
SUM := SUM - REMOVE;{REMOVE THE OLD VALUE}
SUM := SUM + AVG[CNTIDX];   {ADD IN THE NEW VALUE}
CNTIDX := CNTIDX + 1;
IF CNTIDX > 360 THEN
  CNTIDX := 1;
ENDIF;
FA3050 := SUM / 360.0;
{CALCULATE BTU VALUE}
BTU_VAL := FA3050 * BTU;
::10SECONDS.TIMR1V := 0.0;
WAIT 1;
WAIT UNTIL TIM >= 10.0;
GOTO START;

ENDSEQUENCE

-Original Message-
From: Steve Rigby [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, September 06, 2000 8:01 AM
To: 'Foxboro DCS Mail List' (E-mail)
Subject: Rolling average


Hi all,

What I would like is a way to calculate the average position of a valve over
the last hour, updated say every minute.
and then available as an input for a block. Any ideas?

Thanks in advance.

Steve Rigby
Air Liquide Industrie BV
Merseyweg 10
3197 KG Botlek-Rotterdam
The Netherlands
Tel: +31(0)181-271131
Fax:+31(0)181-271100
Email:
[EMAIL PROTECTED]
[EMAIL PROTECTED]





-

RE: rexecing without password

[Stear, Bo]

The invisible .rhosts file in the root directory must be created or modified
to allow remote access without passwords.
This file sets up a 'trusted' station that does not require passwords.
Create or modify the .rhosts file to contain the LETTERBUG name of all of
the stations that you want to be 'trusted'.

-Original Message-
From: Sascha Wildner [mailto:[EMAIL PROTECTED]]
Sent: Thursday, August 31, 2000 7:17 AM
To: Foxboro Mailing List
Subject: rexecing without password


Hello,
 
does anyone know if it is possible to remotely execute commands on other
hosts (either AW70 or AW51) without having to enter a password?  My
application must be able to do this from either architecture, all four
combinations (AW70->AW70, AW70->AW51, AW51->AW51 and AW51->AW70).
 
 
Regards,
 
Sascha Wildner
erpicon Software Development GmbH



---
This list is neither sponsored nor endorsed by the Foxboro Company. All 
postings from this list are the work of list subscribers and no warranty 
is made or implied as to the accuracy of any information disseminated 
through this medium. By subscribing to this list you agree to hold the 
list sponsor(s) blameless for any and all mishaps which might occur due to 
your application of information received from this mailing list.

To be removed from this list, send mail to 
[EMAIL PROTECTED] 
with "unsubscribe foxboro" in the Subject. Or, send any mail to
[EMAIL PROTECTED]

RE: Sysdef

[Stear, Bo]

An update to Sysdef (version 2.0.1, part # K0175SR) is available on the
Foxboro CSC website.  This update will allow you to change the invalid IP
addresses as well as correct some other problems with Sysdef.

-Original Message-
From: Harshad Viradia [mailto:[EMAIL PROTECTED]]
Sent: Monday, August 28, 2000 10:14 PM
To: Foxboro DCS Mail List
Subject: Sysdef




Hi list

I have five systems with plenty of nodes.

The sysdef of one of the system having 24 nodes showing incorrect IP address
in
hardware definition. I am using sysdef, revision 2.0.

The first two filed of most of the IP address in hardware definition shows
127.000 and 158.128 instead of 151.128 (Class assigned to Foxboro).

After day 0 and commit,  /etc/hosts shows correct IP addresses of all the
hosts
i.e. 151.128. ... . 

I have checked the uniqueness of MAC address, NSAP and IP, and are ok.

The sysdef for other systems shows correct IP address in hardware
definition.

Can anyone advise, whether its a problem of sysdef software for large
configuration or I am committing some errors.

Thanks in advance.

Harshad Viradia
Reliance Petroleum Ltd.
Jamnagar.



---
This list is neither sponsored nor endorsed by the Foxboro Company. All 
postings from this list are the work of list subscribers and no warranty 
is made or implied as to the accuracy of any information disseminated 
through this medium. By subscribing to this list you agree to hold the 
list sponsor(s) blameless for any and all mishaps which might occur due to 
your application of information received from this mailing list.

To be removed from this list, send mail to 
[EMAIL PROTECTED] 
with "unsubscribe foxboro" in the Subject. Or, send any mail to
[EMAIL PROTECTED]

---
This list is neither sponsored nor endorsed by the Foxboro Company. All 
postings from this list are the work of list subscribers and no warranty 
is made or implied as to the accuracy of any information disseminated 
through this medium. By subscribing to this list you agree to hold the 
list sponsor(s) blameless for any and all mishaps which might occur due to 
your application of information received from this mailing list.

To be removed from this list, send mail to 
[EMAIL PROTECTED] 
with "unsubscribe foxboro" in the Subject. Or, send any mail to
[EMAIL PROTECTED]

RE: Alarm Printers

[Stear, Bo]

ERUS software (www.erus.com) created a simple printer replacement for us and
now markets it under the name "Visual Alert".  You can download a demo on
their web site.  It uses any PC (Pentium preferred) and is a direct
replacement for the printer.  It allows scrolling through the last 1000
alarms and maintains dated log files for later review.  At about $300/copy
it's hard to beat.

-Original Message-
From: SWAPP ROBERT L [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, August 23, 2000 4:56 PM
To: 'Foxboro DCS Mail List'
Subject: Alarm Printers


Greetings from Arizona,
 I have a question about replacing alarm message printers with PC's.  I
heard about someone doing this at a user group and would like to get more
information.  Is anyone doing this??  I've contacted Foxboro (US west coast)
but they didn't have any details yet.  I was lead to believe this was a
Foxboro product but I might be wrong about that. 
 Any information would be appreciated...
   Thanks
Bob Swapp
Navajo Generating Station
Page, Arizona
520-645-8811 ext. 7480  

---
This list is neither sponsored nor endorsed by the Foxboro Company. All 
postings from this list are the work of list subscribers and no warranty 
is made or implied as to the accuracy of any information disseminated 
through this medium. By subscribing to this list you agree to hold the 
list sponsor(s) blameless for any and all mishaps which might occur due to 
your application of information received from this mailing list.

To be removed from this list, send mail to 
[EMAIL PROTECTED] 
with "unsubscribe foxboro" in the Subject. Or, send any mail to
[EMAIL PROTECTED]

---
This list is neither sponsored nor endorsed by the Foxboro Company. All 
postings from this list are the work of list subscribers and no warranty 
is made or implied as to the accuracy of any information disseminated 
through this medium. By subscribing to this list you agree to hold the 
list sponsor(s) blameless for any and all mishaps which might occur due to 
your application of information received from this mailing list.

To be removed from this list, send mail to 
[EMAIL PROTECTED] 
with "unsubscribe foxboro" in the Subject. Or, send any mail to
[EMAIL PROTECTED]

RE: Back on the Soap Box

[Stear, Bo]

If I did say that I did a 'bootless' upgrade to version 6.2, I was mistaken
and apologize.  I did 'bootless' upgrades to version 6.1.1 which do not
require EEPROM updates.  Can't be done with EEPROM updates.

-Original Message-
From: John Miller [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, July 26, 2000 11:29 AM
To: 'Foxboro DCS Mail List'
Subject: RE: Back on the Soap Box


There are a few of things I need to bring up:

First, besides Bo, has anyone had success with doing an upgrade to 6.2 and
not having to reboot the CP's.  Bo says that he has seen it work, yet I have
had sources in Foxboro recommend against doing it.  Does anyone know why we
would be told this?

Second, in addition Bo's desire to see bootless CP upgrades (with economics
dictating longer intervals between shutdowns, we could use that feature,
too), I'd like to see FoxView/FoxDraw brought beyond what I still feel is
beta test reliability and features.  Two years ago, we were promised that
the next version of the package would have dynamic trending - where is it?
I'd also like to know if FoxView is still being developed or is it being
abandoned in favor of a Wonderware based product?  I know this isn't as
critical as Bo's issue, but it's important for planning and upgrades.

Finally, there are two and half working days left until the User's
Conference.  Has anyone given any thought to how those of us who feel that
bootless CP upgrades are a critical issue can organize and vote to see that
it gets the attention it deserves?  Are there any other specific items that
we can bring up - additional function blocks, time delayed alarming, better
documentation of existing control blocks, integerated expert system
functions, fuzzy ?  Granted, not everyone will have the same issues, but I
think the group should be able to form a consensus to support each other's
issues.   

John

---
This list is neither sponsored nor endorsed by the Foxboro Company. All 
postings from this list are the work of list subscribers and no warranty 
is made or implied as to the accuracy of any information disseminated 
through this medium. By subscribing to this list you agree to hold the 
list sponsor(s) blameless for any and all mishaps which might occur due to 
your application of information received from this mailing list.

To be removed from this list, send mail to 
[EMAIL PROTECTED] 
with "unsubscribe foxboro" in the Subject. Or, send any mail to
[EMAIL PROTECTED]

---
This list is neither sponsored nor endorsed by the Foxboro Company. All 
postings from this list are the work of list subscribers and no warranty 
is made or implied as to the accuracy of any information disseminated 
through this medium. By subscribing to this list you agree to hold the 
list sponsor(s) blameless for any and all mishaps which might occur due to 
your application of information received from this mailing list.

To be removed from this list, send mail to 
[EMAIL PROTECTED] 
with "unsubscribe foxboro" in the Subject. Or, send any mail to
[EMAIL PROTECTED]

RE: Back on the Soap Box

[Stear, Bo]

Folks,
Somewhere I've been slightly misunderstood.  Here's exactly what I know:

1.  Foxboro has been working diligently to upgrade the software quality
process both within their development staff and the testing crew.  I've
personally been involved in this and see much promise for the future
although this has not shown itself in any release as yet.  That is the
primary reason you don't hear me grumbling about software quality these
days.  I'm in a hold position right now waiting for the first new release
coming out of the new process.  Otherwise, this would REALLY be my 'top
pole' issue.

2.  I never intended that we should let up on Foxboro to complete and debug
the products we already own, Foxview et al.  We do need to let Foxboro know
that that is a given and should proceed right along with developing the
online upgrade capability and take priority over any 'new' offerings.

3.  That being said, I want to get on with this new mission and get online
upgrades for myself and you.



-Original Message-
From: John Miller [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, July 26, 2000 11:29 AM
To: 'Foxboro DCS Mail List'
Subject: RE: Back on the Soap Box


There are a few of things I need to bring up:

First, besides Bo, has anyone had success with doing an upgrade to 6.2 and
not having to reboot the CP's.  Bo says that he has seen it work, yet I have
had sources in Foxboro recommend against doing it.  Does anyone know why we
would be told this?

Second, in addition Bo's desire to see bootless CP upgrades (with economics
dictating longer intervals between shutdowns, we could use that feature,
too), I'd like to see FoxView/FoxDraw brought beyond what I still feel is
beta test reliability and features.  Two years ago, we were promised that
the next version of the package would have dynamic trending - where is it?
I'd also like to know if FoxView is still being developed or is it being
abandoned in favor of a Wonderware based product?  I know this isn't as
critical as Bo's issue, but it's important for planning and upgrades.

Finally, there are two and half working days left until the User's
Conference.  Has anyone given any thought to how those of us who feel that
bootless CP upgrades are a critical issue can organize and vote to see that
it gets the attention it deserves?  Are there any other specific items that
we can bring up - additional function blocks, time delayed alarming, better
documentation of existing control blocks, integerated expert system
functions, fuzzy ?  Granted, not everyone will have the same issues, but I
think the group should be able to form a consensus to support each other's
issues.   

John

---
This list is neither sponsored nor endorsed by the Foxboro Company. All 
postings from this list are the work of list subscribers and no warranty 
is made or implied as to the accuracy of any information disseminated 
through this medium. By subscribing to this list you agree to hold the 
list sponsor(s) blameless for any and all mishaps which might occur due to 
your application of information received from this mailing list.

To be removed from this list, send mail to 
[EMAIL PROTECTED] 
with "unsubscribe foxboro" in the Subject. Or, send any mail to
[EMAIL PROTECTED]

---
This list is neither sponsored nor endorsed by the Foxboro Company. All 
postings from this list are the work of list subscribers and no warranty 
is made or implied as to the accuracy of any information disseminated 
through this medium. By subscribing to this list you agree to hold the 
list sponsor(s) blameless for any and all mishaps which might occur due to 
your application of information received from this mailing list.

To be removed from this list, send mail to 
[EMAIL PROTECTED] 
with "unsubscribe foxboro" in the Subject. Or, send any mail to
[EMAIL PROTECTED]

RE: Back on the Soap Box

[Stear, Bo]

I would think that the most likely target for online upgrade would be those
CP's that are fault tolerant and that have dual field busses.  I can't
visualize any possible way to provide online upgrade capability otherwise
and I wouldn't want to start off by asking for the impossible.

-Original Message-
From: David Johnson [mailto:[EMAIL PROTECTED]]
Sent: Thursday, July 20, 2000 1:48 PM
To: Foxboro DCS Mail List
Subject: Re: Back on the Soap Box


To add to what Neil just said, what about having to EPROM the FBMs, do we 
have to have redundant I/O too?

David


---
This list is neither sponsored nor endorsed by the Foxboro Company. All 
postings from this list are the work of list subscribers and no warranty 
is made or implied as to the accuracy of any information disseminated 
through this medium. By subscribing to this list you agree to hold the 
list sponsor(s) blameless for any and all mishaps which might occur due to 
your application of information received from this mailing list.

To be removed from this list, send mail to 
[EMAIL PROTECTED] 
with "unsubscribe foxboro" in the Subject. Or, send any mail to
[EMAIL PROTECTED]

---
This list is neither sponsored nor endorsed by the Foxboro Company. All 
postings from this list are the work of list subscribers and no warranty 
is made or implied as to the accuracy of any information disseminated 
through this medium. By subscribing to this list you agree to hold the 
list sponsor(s) blameless for any and all mishaps which might occur due to 
your application of information received from this mailing list.

To be removed from this list, send mail to 
[EMAIL PROTECTED] 
with "unsubscribe foxboro" in the Subject. Or, send any mail to
[EMAIL PROTECTED]

RE: Physical RAM

[Stear, Bo]

prtconf |grep Mem

-Original Message-
From: Mercer,Craig [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, May 10, 2000 7:36 AM
To: 'Foxboro DCS Mail List'
Subject: RE: Physical RAM


Is it a Solaris Machine or NT.  For Solaris - dmesg | more - Look through
the file and you will see the memory reported.
 
Craig

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, May 10, 2000 6:55 AM
To: [EMAIL PROTECTED]
Subject: Physical RAM



I need to know the physical RAM in my AW without reboot them... but I don't
know how to. 
Could you help me? 

Thank you in advance 

Pedro J. Hernandez 
Advanced Process Control 
Repsol Quimica Puertollano 
[EMAIL PROTECTED] 



---
This list is neither sponsored nor endorsed by the Foxboro Company. All 
postings from this list are the work of list subscribers and no warranty 
is made or implied as to the accuracy of any information disseminated 
through this medium. By subscribing to this list you agree to hold the 
list sponsor(s) blameless for any and all mishaps which might occur due to 
your application of information received from this mailing list.

To be removed from this list, send mail to 
[EMAIL PROTECTED] 
with "unsubscribe foxboro" in the Subject. Or, send any mail to
[EMAIL PROTECTED]

RE: upload/shrink/checkpoint problems

[Stear, Bo]

That seems to be more than enough disk space.
Look on your system in /opt/fox/bin/tools for a directory called
'check_sync'.
If you have it there, cd to /opt/fox/bin/tools/check_sync and run
'check_db_sync  where LETTERBUG is the letterbug name of your CP.
If this fails, you're in trouble.
If you don't have the 'check_sync' directory, get it from field service
it's an invaluable tool.


-Original Message-
From: Stan Brown [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, May 02, 2000 8:15 AM
To: [EMAIL PROTECTED]
Subject: Re: upload/shrink/checkpoint problems


On Tue May  2 08:43:27 2000 Stear, Bo wrote...
>
>Check the drive space on the host AP for this CP.  Shrink uses extra space
>and you may be running out.
>I'm not certain but since the ICC session failed during the 'shrink' it may
>have left the database locked causing the remaining sessions to fail.
>
>

Plenty of space:

Filesystemkbytesused   avail capacity  Mounted on
/dev/md/dsk/d0 35071   17251   1432055%/
/dev/md/dsk/d4578455  308615  21200060%/usr
/dev/md/dsk/d2 266798951   1506838%/var
/dev/md/dsk/d5   1094414  338073  64690135%/opt

At least, I think that's plenty. Am I wrong?

-- 
Stan Brown [EMAIL PROTECTED]
843-745-3154
Charleston SC.
-- 
Windows 98: n.
useless extension to a minor patch release for 32-bit extensions and
a graphical shell for a 16-bit patch to an 8-bit operating system
originally coded for a 4-bit microprocessor, written by a 2-bit 
company that can't stand for 1 bit of competition.
-
(c) 2000 Stan Brown.  Redistribution via the Microsoft Network is
prohibited.


---
This list is neither sponsored nor endorsed by the Foxboro Company. All 
postings from this list are the work of list subscribers and no warranty 
is made or implied as to the accuracy of any information disseminated 
through this medium. By subscribing to this list you agree to hold the 
list sponsor(s) blameless for any and all mishaps which might occur due to 
your application of information received from this mailing list.

To be removed from this list, send mail to 
[EMAIL PROTECTED] 
with "unsubscribe foxboro" in the Subject. Or, send any mail to
[EMAIL PROTECTED]

RE: upload/shrink/checkpoint problems

[Stear, Bo]

Check the drive space on the host AP for this CP.  Shrink uses extra space
and you may be running out.
I'm not certain but since the ICC session failed during the 'shrink' it may
have left the database locked causing the remaining sessions to fail.

I hate to be a killjoy but it's just these types of problems that cause me
to avoid 'automatic' scripts to handle my CP's.  These are fragile databases
that can sometimes be easily corrupted.  Everything has to go just right or
the synchronization between the running CP, its workfile, it's locks, and
CSA can be fowled.

-Original Message-
From: Stan Brown [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, May 02, 2000 7:29 AM
To: [EMAIL PROTECTED]
Subject: upload/shrink/checkpoint problems


I jsut deployed my new upload/shrink/checkpoint script on a new node,
and it failed during the run last night.

Can anyone give me some insight into what this failure means? Here is
the ouput of one station:

Starting upload/checkpoint...
Mon May  1 23:00:05 GMT 2000 --- upload and checkpoint CP0401
DONE 1 OPEN CP0401!: Mon May  1 23:00:06 2000
DONE 2 UPLOAD CP0401!: Mon May  1 23:04:53 2000
FAIL 3 SHRINK CP0401!: Mon May  1 23:06:53 2000 -15 ICCshrink
error: class= 
-30 error= 0 text= ICCinit: CCshrink problem
FAIL 4 CHECKPOINT CP0401!: Mon May  1 23:06:53 2000 -15 ICCchkpt
error: clas
s= 20 error= 1 text= Session not in progress
FAIL 5 CLOSE CP0401!: Mon May  1 23:06:53 2000 -16 ICCclose error:
class= 20
error= 1 text= Session not in progress
DONE 6 EXIT CP0401!: Mon May  1 23:06:53 2000

I _think_ all the later errors are trigered by the shrink problem,
but I am not certain of this.

Any insight would be greatly appreciated.


-- 
Stan Brown [EMAIL PROTECTED]
843-745-3154
Charleston SC.
-- 
Windows 98: n.
useless extension to a minor patch release for 32-bit extensions and
a graphical shell for a 16-bit patch to an 8-bit operating system
originally coded for a 4-bit microprocessor, written by a 2-bit 
company that can't stand for 1 bit of competition.
-
(c) 2000 Stan Brown.  Redistribution via the Microsoft Network is
prohibited.


---
This list is neither sponsored nor endorsed by the Foxboro Company. All 
postings from this list are the work of list subscribers and no warranty 
is made or implied as to the accuracy of any information disseminated 
through this medium. By subscribing to this list you agree to hold the 
list sponsor(s) blameless for any and all mishaps which might occur due to 
your application of information received from this mailing list.

To be removed from this list, send mail to 
[EMAIL PROTECTED] 
with "unsubscribe foxboro" in the Subject. Or, send any mail to
[EMAIL PROTECTED]

RE: Question about /etc/aplns and /etc/wplns

[Stear, Bo]

The AW, unlike the WP, gets two 'names' assigned.  One is its letterbug
(AW0400) and is the host name for the AP section of the AW code.  The other
(AWP400) is the WP logical name for the WP section of the AW code.  AW0400
should show up in your /etc/aplns file and AWP400 in the /etc/wplns file.

-Original Message-
From: Stan Brown [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, May 02, 2000 7:22 AM
To: [EMAIL PROTECTED]
Subject: Question about /etc/aplns and /etc/wplns


I have ben working on some scripts lately that do various things on
our
Foxboor nodes. All of the nodes, exceept for 1 consits of one or
more
AP51B's, and WP51B's. On these machines ehre are the files
/etc/wplns
and /etc/aplns. Thes files descibe what WP's and AP's exist ont ehis
node.

I have just deplyed these cripts on a node thta consosits of a
AW51B,
and a WP51B. Mich to my suprise, I found thta /etc/wplns contaied
the
folowing entry:

AWP400

This is the WP, I think it's real name is AW0400. Can anyone tell me
why this entry is there?

Thanks.

-- 
Stan Brown [EMAIL PROTECTED]
843-745-3154
Charleston SC.
-- 
Windows 98: n.
useless extension to a minor patch release for 32-bit extensions and
a graphical shell for a 16-bit patch to an 8-bit operating system
originally coded for a 4-bit microprocessor, written by a 2-bit 
company that can't stand for 1 bit of competition.
-
(c) 2000 Stan Brown.  Redistribution via the Microsoft Network is
prohibited.


---
This list is neither sponsored nor endorsed by the Foxboro Company. All 
postings from this list are the work of list subscribers and no warranty 
is made or implied as to the accuracy of any information disseminated 
through this medium. By subscribing to this list you agree to hold the 
list sponsor(s) blameless for any and all mishaps which might occur due to 
your application of information received from this mailing list.

To be removed from this list, send mail to 
[EMAIL PROTECTED] 
with "unsubscribe foxboro" in the Subject. Or, send any mail to
[EMAIL PROTECTED]

RE: Re: Scripts to backup CP database and CSA to an alternate sta tion

[Stear, Bo]

OFHA has some problems that won't be resolved.  See CAR 100053 and you'll
find that OFHA will skip filenames when they are more than 14 characters in
length.  The CAR response recommends I rename these files so they are
shorter kinda strange since they're either SYSTEM or FOXBORO created
files.  The CAR also states that Foxboro has NO intentions of fixing this
problem and have turned it into a PRODUCT ENHANCEMENT...

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: Saturday, April 29, 2000 3:57 PM
To: Foxboro DCS Mail List
Subject: Re: Re: Scripts to backup CP database and CSA to an alternate
station


If you are using model 51 stations, you should consider using the OFHA 
product that is included in the baseline software supplied with AW51s and 
AP51s

Best Regards,
Fred

>
>Yes I'd be happy to donate them. And I don't consider it an intrusion. 
Thanks for doing such a good thing with the
>Cassandra Project. I wonder how long it will be before we see Foxboro 
using the Project as a selling point.
>
>
>
>
>
>
>
>Duc M Do <[EMAIL PROTECTED]>@lists.TheCassandraProject.org> on 04/18/2000 
03:15:46 PM
>
>Please respond to "Foxboro DCS Mail List" 
<[EMAIL PROTECTED]>
>
>Sent by:  <[EMAIL PROTECTED]>
>
>
>To:   "Foxboro DCS Mail List" <[EMAIL PROTECTED]>
>cc:
>Subject:  Re: Scripts to backup CP database and CSA to an alternate 
station
>
>
>Hi Ed,
>
>Sorry for one more intrusion: I forgot to ask you if you are "donating"
>your ez_archive scripts to the Cassandra Project? If affirmative,
>please let me know so I can add the proper GNU Open Source text block
>to the files. Thanks!
>
>Duc M. Do
>
>
>At 02:46 PM 4/18/00 -0500, you wrote:
>>
>>Duc M. Do was kind enough to upload the scripts I use to back-up the
>control database and CSA information to an
>>alternate station to the cassandra server
>>
>>The scripts are located at
>>
>>http://thecassandraproject.org/archive/ez_archive.zip
>>
>>Duc also created a compressed tar-format file:
>>
>>http://thecassandraproject.org/archive/ez_archive.tar.Z
>>
>>
>>I think this is an important utility. I believe if a few of you hacker
>types could take a look at the scripts it could be improved greatly.


---
This list is neither sponsored nor endorsed by the Foxboro Company. All 
postings from this list are the work of list subscribers and no warranty 
is made or implied as to the accuracy of any information disseminated 
through this medium. By subscribing to this list you agree to hold the 
list sponsor(s) blameless for any and all mishaps which might occur due to 
your application of information received from this mailing list.

To be removed from this list, send mail to 
[EMAIL PROTECTED] 
with "unsubscribe foxboro" in the Subject. Or, send any mail to
[EMAIL PROTECTED]