RE: HLBL REF.

2001-07-09 Thread Jones, Charles R. (Chuck)
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

RE: OPC client for I/A?

2001-07-09 Thread Lemieux, Tom
Corey, I believe Matrikon makes an OPC server that will talk to an AW51. Phone 780-448-1010 www.matrikon.com Thanks Tom Lemieux Process Systems Specialist Alabama Pine Pulp Phone334-743-8576 Fax 334-743-8295 Email [EMAIL PROTECTED] -Original Message- From: Corey R

Re: OPC client for I/A?

2001-07-09 Thread Bakke, Richard A
Corey, We are have been using the Matrikon OPC server for almost a year to make I/A points (740 points so far) available to our mill info system, and to send a few values back to I/A. The Matrikon OPC server is running on an NT box and communicates via ethernet to an AW51B to open FoxAPI

RE: HLBL REF.

2001-07-09 Thread 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,

RE: HLBL REF.

2001-07-09 Thread Johnson, Alex (Foxboro)
Okay, I'll say it. My advice is do not use setpars on a running system. It is intended as an application engineering support tool, e.g., to put CP's in simulation mode. There are some places where its use can be considered to be appropriate, e.g., setting some parameters like Computer Control

RE: HLBL REF

2001-07-09 Thread Fitzgerrell Kevin
Ken, To efficiently set the appropriate state of a number of blocks at the same time I use a calc or logic block. I trigger the calc block with a boolean input that can be pulsed from a display (momentary contact) or from sequence logic. The calc block uses an appropriate OSP to toggle on and

RE: HLBL REF.

2001-07-09 Thread Ken . E . Moore
After speaking with our former application engineer, I agree that the setpars is not what we want to do. We currently only use the setpars tool after an unusual event, it is not used on a routine basis, the display with the call button is not nomally accessible. Do you recommend running a

RE: HLBL REF.

2001-07-09 Thread Johnson, Alex (Foxboro)
Depends on what you are trying to do. If you want to the change to survive a reboot, it must be reflected in the checkpoint file. What are you doing that requires the use of setpars? Regards, Alex Johnson 10707 Haddington Houston, TX 77043 713.722.2859 (office) 713.722.2700 (switchboard)

Synchronization (was RE: HLBL REF.)

2001-07-09 Thread kevin . fitzgerrell
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

GC Analyzer Control

2001-07-09 Thread Loupe, Rory (RJ)
I am converting some old Foxboro SMS control schemes to run on I/A. There is some code that does validity, rate of change and time-out checking on some GC data. If the GC data is good the code does PID control with this data (in the code itself, not through a PID block). The analyzer has a