Re: [foxboro] hlbl msglin

  • From: dirk.pauwels@xxxxxxxxxx
  • To: foxboro@xxxxxxxxxxxxx
  • Date: Tue, 23 Oct 2007 16:20:35 +0200

sounds like the OMI (Operator Message Interface) application we use quite
intensively. It works quite well, allthough you have to make sure your
sequence message looks like this :
SENCONF("This is a msge to be acknowledged by the CRO") TO MSSGR1 AFTER 30
GOTO next step;
next step being a label somewhere in the code. If you do not do this and
the host running the OMI is rebooted or backed up etc...every sequence
sending a message through the OMI will lock up.....We purchased a redundant
OMI version to solve this but this didn't run like it was supposed to so
we're waiting for a new version. Other than that it works perfectly. The
message is still there in the background when not confirmed and a new
message pops up, when the new msge is confirmed, the older one is still
there to be confirmed.

Rgds,

Dirk Pauwels - DCS/MOC coordinator
Engineering dept.
Hexion Specialty Chemicals
E mail: dirk.pauwels@xxxxxxxxxx
T.  +32.(0)3.570.95.97
F.  +32.(0)3.570.16.09
Mob. +32.(0)497.428.300


                                                                           
             "Grumelart,                                                   
             Alain"                                                        
             <alain.grumelart@                                          To 
             ips.invensys.com>         <foxboro@xxxxxxxxxxxxx>             
             Sent by:                                                   cc 
             foxboro-bounce@fr                                             
             eelists.org                                           Subject 
                                       Re: [foxboro] hlbl msglin           
                                                                           
             23-10-2007 16:07                                              
                                                                           
                                                                           
             Please respond to                                             
             foxboro@freelists                                             
                   .org                                                    
                                                                           
                                                                           




RE: "Is there a way to kick off a script from a sequence block so that
no message gets recorded to the OAJ?"

Alex Johnson has this "cpShell" utility which allows just that.
It runs on an AW and waits for commands from sequence blocks.
You send it a shell command via either SENDCONF or SENDMSG. =

This mechanism does not depend on any DM or Foxview instance. =


Alain Grumelart Ing.
Systems Integration & IT
Invensys Systems Canada Inc.
-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx]
On Behalf Of Lowell, Timothy
Sent: Friday, October 19, 2007 10:40 PM
To: foxboro@xxxxxxxxxxxxx
Subject: Re: [foxboro] hlbl msglin

I have a follow-up question on this.  We have a sequence block that
kicks off a script file every 30 seconds which records the value of some
important totalizers into a text file.  The idea is, if the CP should
fail and set the totalizers to zero, this sequence block will run upon
the initialization of the CP and read the text file it has been writing
to every 30 seconds and omset the totalizer values back to what they
should be.

This works well, but the problem is, the sequence code uses the
:AW0101DMCMD call to kick off the script, and every time it does, this
gets recorded to the OAJ.  This means there are 2880 useless messages
per day in the OAJ.

Is there a way to kick off a script from a sequence block so that no
message gets recorded to the OAJ?  This script uses wp_applic to invoke
the script, and I was wondering if using just applic would work better.
Does anyone know?

Tim

----- Original Message -----
From: foxboro-bounce@xxxxxxxxxxxxx <foxboro-bounce@xxxxxxxxxxxxx>
To: foxboro@xxxxxxxxxxxxx <foxboro@xxxxxxxxxxxxx>
Sent: Fri Oct 19 21:29:42 2007
Subject: Re: [foxboro] hlbl msglin

If memory serves, the object is to have the Sequence block
set the DM/FV variable "DMCMD" with the text of a display
manager command.

That variable can be accessed from outside the DM/FV by using
a name which is the DM/FV name followed by the variable name
"DMCMD".  So, for FoxView name 05WP01, the variable is named
05WP01DMCMD.  =


In Sequence code an OM name is preceded by ":", so the statement
to set it is:

     : 05WP01DMCMD :=3D "dmcmd msglin Hola"

Be careful to remember that if the DM/FV instance isn't running,
the Sequence block gets a -1 error (because the variable doesn't
exist), also that it will fail the same way if the DM/FV station
is dead or is rebooting, etc.  There are also some nodebus conditions =

which can also make the command fail, at least temporarily, so it
is a good idea to have an error handler.

William C Ricker
FeedForward, Inc.



-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx]
On
Behalf Of Ron Schafer
Sent: Friday, October 19, 2007 12:17 PM
To: foxboro@xxxxxxxxxxxxx
Subject: [foxboro] hlbl msglin

 =

 =


 =


Does anyone know the command for hlbl (ind block) to send text to the
message line?

 =


Ronald G. Schafer

Distrubuted Controls System Administrator

White Birch Paper

Bear Island L.L.C. Division
10026 Old Ridge Rd.
Ashland Va. 23005
804-227-4034
Email: rschafer@xxxxxxxxxxxxxxxxxxxxxx

 =


 =


 =



 =

 =

_______________________________________________________________________
This mailing list is neither sponsored nor endorsed by Invensys Process
Systems (formerly The Foxboro Company). Use the info you obtain here at
your own risks. Read http://www.thecassandraproject.org/disclaimer.html
 =

foxboro mailing list:             //www.freelists.org/list/foxboro
to subscribe:         mailto:foxboro-request@xxxxxxxxxxxxx?subject=3Djoin
to unsubscribe:      mailto:foxboro-request@xxxxxxxxxxxxx?subject=3Dleave
 =



 =

 =

_______________________________________________________________________
This mailing list is neither sponsored nor endorsed by Invensys Process
Systems (formerly The Foxboro Company). Use the info you obtain here at
your own risks. Read http://www.thecassandraproject.org/disclaimer.html
 =

foxboro mailing list:             //www.freelists.org/list/foxboro
to subscribe:         mailto:foxboro-request@xxxxxxxxxxxxx?subject=3Djoin
to unsubscribe:      mailto:foxboro-request@xxxxxxxxxxxxx?subject=3Dleave
 =

 =

 =

_______________________________________________________________________
This mailing list is neither sponsored nor endorsed by Invensys Process
Systems (formerly The Foxboro Company). Use the info you obtain here at
your own risks. Read http://www.thecassandraproject.org/disclaimer.html
 =

foxboro mailing list:             //www.freelists.org/list/foxboro
to subscribe:         mailto:foxboro-request@xxxxxxxxxxxxx?subject=3Djoin
to unsubscribe:      mailto:foxboro-request@xxxxxxxxxxxxx?subject=3Dleave
 =



Confidentiality Notice:
This e-mail and any associated files are intended solely for the
individual=
 or entity to whom they are addressed. Please do not copy it or use it for
=
any purposes, or disclose its contents to any other person. Further, this
e=
-mail and any associated files may be confidential and further may be
legal=
ly privileged. This email is from the Invensys Process Systems business
uni=
t of Invensys plc which is a company registered in England and Wales with
i=
ts registered office at Portland House, Bressenden Place, London, SW1E 5BF
=
(Registered number 166023).  For a list of European legal entities within
t=
he Invensys Process Systems business group, please click here
http://www.in=
vensys.com/legal/default.asp?top_nav_id=3D77&nav_id=3D80&prev_id=3D77.

If you have received this e-mail in error, you are on notice of its
status.=
 Please notify us immediately by reply e-mail and then delete this message
=
from your system. Thank you for your co-operation. You may contact our
Help=
desk on +44 (0)20 7821 3859 / 2105 or email inet.hqhelpdesk@xxxxxxxxxxxxx
T=
his e-mail and any attachments thereto may be subject to the terms of any
a=
greements between Invensys (and/or its subsidiaries and affiliates) and
the=
 recipient (and/or its subsidiaries and affiliates).




_______________________________________________________________________
This mailing list is neither sponsored nor endorsed by Invensys Process
Systems (formerly The Foxboro Company). Use the info you obtain here at
your own risks. Read http://www.thecassandraproject.org/disclaimer.html

foxboro mailing list:             //www.freelists.org/list/foxboro
to subscribe:         mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
to unsubscribe:      mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave



 
 
_______________________________________________________________________
This mailing list is neither sponsored nor endorsed by Invensys Process
Systems (formerly The Foxboro Company). Use the info you obtain here at
your own risks. Read http://www.thecassandraproject.org/disclaimer.html
 
foxboro mailing list:             //www.freelists.org/list/foxboro
to subscribe:         mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
to unsubscribe:      mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave
 

Other related posts: