Re: [foxboro] foxboro Digest V7 #356
- From: <Jack.Easley@xxxxxxxxxxxx>
- To: <foxboro@xxxxxxxxxxxxx>
- Date: Mon, 27 Aug 2007 08:45:20 -0500
Concerning your last two issues mentioned:
The history conversion is best accomplished using the leg2hist utility
provided when AIM historian is installed on the old UNIX AP/AW. If you
are not using the legacy historian on your old system, perhaps your
Foxboro field service will work with you for a temporary AIM install
long enough to migrate your historian.=20
Crontab is replaced by Windows scheduler. The main point to remember is
to not use "fox" as the user when setting up the utility you want to
schedule. Use administrator, or some other user, otherwise you will get
DOS boxes popping up on your P91/P92's screen every time a
utility/application runs. Of course, any scripts you schedule must be
tweaked to run in the new Windows environment. Most of Foxboro's old
utilities are available. The only one I've found completely missing is
the dos2unix utility, although I'm not very far along in converting my
scripts.
Jack Easley
-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx]
On Behalf Of rguercio@xxxxxxx
Sent: Friday, August 24, 2007 8:16 PM
To: foxboro@xxxxxxxxxxxxx
Subject: Re: [foxboro] foxboro Digest V7 #356
Comments on transitioning from legacy (Solaris/Unix) to Windoze/MESH.
I am helping with a transition to Windoze/Mesh on a fairly large and=20
well-established refinery-wide control system.? Drawing/screen=20
conversions?have not been?consistently straightforward, especially when=20
using older templates, which we wanted to do to provide continuity of=20
look and feel at this location.? Be warned that there is no backward=20
compatibility between drawings created on the new system and the old=20
system, so in some cases you have to maintain two "identical" drawings=20
or do it on the old and migrate to the new.
With Foxdraw, mouse clicking and dragging are different between the old=20
and new, and requires some getting used to.? Screens done in Windows=20
are not as likely to appear exactly on the actual displays as they do=20
in FoxDraw, and the best solution I have found is to do the screens in=20
FoxDraw at 85, 90 or 90% sizing, depending on the object being drawn,=20
and frequently checking between what you are designing and how it=20
actually looks on a "live" screen.? This is inefficient at best.
There is some irritation with how Windows manages the various windows -=20
such as ICC popping up partly on each of two screens, then the=20
mandatory dragging to one screen or the other.? I also personally like=20
the old "front" button rather than constantly referring to the task bar=20
to retreive other applications.? Also, FoxSelect seems to pop up block=20
details in unexpected places on two-headed stations, and to get back to=20
FoxView, you have to remember which task bar icon goes to which head -=20
it's not clearly delineated.
The main irritation is only being able to use ICC on one Windows=20
station, even when trying to edit different CP's.? The flexibility to=20
use just about any station on the old system for ICC AND the ability to=20
edit more than one CP at a time is a feature that should not have been
lost.
That being said, it is nice to be able to transfer savealls easily in=20
the Windows world via regular PC's, etc.
On a large system that is slowly migrating from Unix to Windoze, it=20
seems as though there is a "Berlin Wall" right in the middle of things=20
- that wall being the MESH with Windoze on one side and all the legacy=20
hardware and apps on the other side.? There are a lot of adjustment=20
pains and will continue to be as the system slowly climbs over the=20
wall.? I'm just not sure at this point, along with accommodating the=20
new FCP's and ZCP's, etc., where we will be once finally over the wall=20
- East or West Berlin!
Issues for the future:? historian migration; propagating crontab=20
applications; etc.? Good luck everyone, on this forced march.
Rick Guercio
RG Consulting
=20
=20
_______________________________________________________________________
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
=20
foxboro mailing list: //www.freelists.org/list/foxboro
to subscribe: =
mailto:foxboro-request@xxxxxxxxxxxxx?subject=3Djoin
to unsubscribe: =
mailto:foxboro-request@xxxxxxxxxxxxx?subject=3Dleave
=20
_______________________________________________________________________
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:
