Re: [foxboro] Maintaining Foxview displays on mixed Windows and Unix consoles
- From: "Joseph M. Riccardi" <joe@xxxxxxxxxxxxx>
- To: <foxboro@xxxxxxxxxxxxx>
- Date: Thu, 17 Jan 2008 19:44:38 -0500
I hate to dig up old issues, but did Patrick ever get any response to the
question about retrieving historical data across an ATS? We will be facing
this dilemma soon...
We also intend to start replacing WP51D's to windows boxes and will do this
in groups of 4 because (as Invensys told us already a long time ago) of the
common alarm group issue which does not work through the ATS. I did not know
yet that alarm history retrieval also does not work through the Mesh (it
seems that they don't tell you everything or maybe I was not listening or I
mist it because the meeting was held partly in french). Are there plans to
make this work in the future or are we forced to have a historian on a Mesh
station?
Thanks
Joseph M. Riccardi, Inc.
DCS Services - Industrial Process Control
Joe@xxxxxxxxxxxxx
"To give real service you must add something that cannot be bought or
measured with money; and that is sincerity and integrity." - Donald A. Adams
> -----Original Message-----
> From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx]
> On Behalf Of FoxPat
> Sent: Wednesday, November 07, 2007 6:24 PM
> To: foxboro@xxxxxxxxxxxxx
> Subject: Re: [foxboro] Maintaining Foxview displays on mixed Windows and
> Unix consoles
>
>
> We do not have any problems maintaining Foxview displays on mixed
> stations.
> (initially copied hundreds of graphics from unix to windows and still do
> so on a regular base when displays need to be modified).
>
>
> Our operator workstations are currently all unix WP51D's I/A 6.3, Foxview
> 99.01 (or something).
>
> We recently (June this year) introduced Mesh, replaced all the CLAN's with
> ATS and installed a terminal server2003, I/A 8.2 and 1 AW70 I/A 8.2 (OPC
> server).
>
> We (as probably most of us) have a script for distributing graphics (or
> any other file) to one, all or a selection of stations through second
> ethernet (also on the Mesh stations, which would be 'third ethernet'), not
> by means of FTP but by means of rcp.
>
> We have successfully installed an rsh service on the windows boxes (thanks
> again Marco, still works like a charm!) which allows us to use our
> existing distribute script without (nearly) any modification. In the
> script is listed which stations are Windows based. If any of the
> destination stations is a windows station, the .fdf file is automatically
> converted to .g, distributed and automatically (rsh) converted back to
> .fdf on the windows boxes.
> We do not have any problems with the resulting displays, no font issues,
> color issues or anything else. This might be because initially our
> graphics were drawn on a stand-alone AW70 integrator (NT), converted to
> .g, copied to the unix boxes and converted back to .fdf. However the unix
> boxes have since
> (1999) been the master of all graphics although, whenever we need text we
> simply copy an existing object and change the text.
>
> I would consider sharing our distribute script if there is real interest
> although it is quite site specific.
> I would need to spend some time to make it a little more generic and
> easier to read (there's a lot more code then comments!).
> It has some nice features, like creating a backup of the display(s)
> whenever displays are distributed to all stations (just suppose you made a
> giant f..k up, and distribute a corrupted display or something). This
> back-up is incremental so you can check the status of a display any number
> of revisions back in time (as long as HD space allows)!
>
>
> As also mentioned, the first call-up of the graphic will be relatively
> slow (but not extremely) due to the fact that the display is not yet
> optimised.
> You could probably automate this as well but the windows boxes are pretty
> fast these days and we do not think it is worth the effort.
>
> We also intend to start replacing WP51D's to windows boxes and will do
> this in groups of 4 because (as Invensys told us already a long time ago)
> of the common alarm group issue which does not work through the ATS.
>
> I did not know yet that alarm history retrieval also does not work through
> the Mesh (it seems that they don't tell you everything or maybe I was not
> listening or I mist it because the meeting was held partly in french).
>
> Are there plans to make this work in the future or are we forced to have a
> historian on a Mesh station?
>
> Kind regards,
>
> Patrick Martens
> Total Raff. Ned. N.V.
-- No attachments (even text) are allowed --
-- Type: application/ms-tnef
-- File: winmail.dat
_______________________________________________________________________
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:
