Re: [foxboro] V8 clarifications (was Upcoming device integrators)
- From: "Johnson, Alex P (IPS)" <alex.johnson@xxxxxxxxxxxxxxxx>
- To: foxboro@xxxxxxxxxxxxx
- Date: Wed, 21 Sep 2005 12:14:41 -0400
Re: We have dark fiber between nodes and were expecting to use it to migrate
a few nodes off of the CLAN and onto the new mesh network. This will require
the ATS, correct?
This will require:
1) 1 pair of ATSs
2) 1 pair of Ethernet switches
3) 1 AW70 to boot the ATS and run NFD
4) CP270 plus FDSI FBM
5) A variety of cables, baseplates, and such.
Re: We will need a I/A v8 AW/AP to host the CP270 (wintel only at this
time), and even when Sun is available, it will be FV only.
Yes.
Re: If we convert all of our displays from DM to FV, and keep out 51B or 51D
boxes, they will still lock up when we change back to standard time, because
they cannot run IA v8.
Switching from DM to FV does not eliminate V6/7 DST issues. Some will tell
you it makes it worse. This is the current situation.
51Bs and 51Ds cannot be migrated to the Mesh and I/A Series V8 now or in the
future.
Re: So either we upgrade all of the AW/WP's on a node, or we stay with DM,
and put the new CP270 host AW in the rackroom, where it will only be used
for calling up "Select" displays.
Pretty much. The Nodebus based WPs will be able to control the CP270
(setpoint changes, data on display, alarm messages, etc. are all supported).
Re: Display conversion
The DM to FV conversion works pretty well, but there is a font replacement
issue that causes problems for some displays. We hope to have that fixed
before Solaris on the Mesh is released.
Hope this helps.
Regards,
Alex Johnson
Invensys Systems, Inc.
10707 Haddington
Houston, TX 77063
+1 713 722 2859 (voice)
+1 713 932 0222 (fax)
+1 713 722 2700 (switchboard)
alex.johnson@xxxxxxxxxxxxxxxx
I hope to see you at the Invensys Process System User Group meeting October
3-6 in Houston, TX -
www.invensys.com/usergroup2005
-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx] On
Behalf Of Brian Bates
Sent: Wednesday, September 21, 2005 10:53 AM
To: foxboro@xxxxxxxxxxxxx
Subject: Re: [foxboro] V8 clarifications (was Upcoming device integrators)
Thanks for the quick reply Alex.
I think that understand now.
All of our AW/AP/AP's are Unix IA v6.x, and all of the nodes communicate
via CLAN.
We want to use FDSI FBMs hosted by CP270s on a few of our existing nodes.
We have dark fiber between nodes and were expecting to use it to migrate a
few nodes off of the CLAN and onto the new mesh network.
This will require the ATS, correct?
We will need a I/A v8 AW/AP to host the CP270 (wintel only at this time),
and even when Sun is available, it will be FV only.
If we convert all of our displays from DM to FV, and keep out 51B or 51D
boxes, they will still lock up when we change back to standard time,
because they cannot run IA v8.
So either we upgrade all of the AW/WP's on a node, or we stay with DM, and
put the new CP270 host AW in the rackroom, where it will only be used for
calling up "Select" displays.
BTW If we do upgrade all of the AW/WP's on a node to workstations that can
run V8, and do finally convert from DM to FV, a converter works as well as
the convdisp2_50 would be much appreciated.
-Regards, Brian Bates.
Bowater Canadian Forest Products Inc.
Thunder Bay ON
"Johnson, Alex P
(IPS)" To:
foxboro@xxxxxxxxxxxxx
<alex.johnson@xxxxxx cc:
vensys.com> Subject: [foxboro] V8
clarifications (was Upcoming device integrators)
Sent by:
foxboro-bounce@freel
ists.org
09/21/2005 10:21 AM
Please respond to
foxboro
Re: ATS
Hi, Brian.
Re: ATS
The ATS is the device that allows Nodebus based stations to talk to Mesh
network based stations. It has nothing to do with the host OS on either
network.
Re: Solaris on the Mesh
We currently run Solaris 8 on V7.x boxes. Relatively speaking V8 is
reaching
the end of its lifetime. We have a choice then of Solaris 9 or Solaris 10.
Solaris 10 is the newest release - a year or two in commercial release -
and
is the clear target for development.
Sun like many vendors has trimmed its legacy code and OpenWindows is one of
the pieces that have been trimmed. That impacts much of our software.
Beyond
that, there are other differences that require adjustments.
Of course, the testing burden is the largest single piece of work since
every single application needs to be redone and retested under the new OS.
And don't forget the documentation changes that will be required.
Re: Is this true that we are we waiting for BOTH the ATS and IA v8 for
Solaris?
I'm not sure how to answer this so I'll enumerate all of the answers that I
think you might be interested in:
1) If you want to add to an existing V6/7 system, we have equipment
available to do that.
2) If you want to add a new standalone unit, we have equipment to do that
(V8).
3) If you want to connect a new unit to the existing facility, you need an
ATS. The ATS should be released before year end.
4) If you want Solaris on the Mesh network, it is not yet available and we
do not yet have a release date for it though we have a considerable number
of people working on it.
Re: Can you verify that I/A v8 will (or will not support) DM?
There are no plans to support the DM on V8 workstations (Solaris or
Windows). We are working to improve the display conversion support from DM
to FV by adding the older fonts which were the single biggest problem in
display conversion.
Re: V8 workstations do not have DST issues. Nothing has changed on Solaris
workstations under V6/7 with regard to DST. Are you saying that I/A SUN
boxes and I/A WinTel boxes no longer have DST issues when running I/A v8?
That is correct. DST is handle properly on V8 workstations.
Re: Will I/A v8 support 51B and 51D workstations?
No. We've previously announced that only the 51F and 51G SPARC machines
will
be supported by I/A Series V8.
Re: Is this information available on the IA website?
For the public? Not to my knowledge.
For our account representatives? Yes.
Regards,
Alex Johnson
Invensys Systems, Inc.
10707 Haddington
Houston, TX 77063
+1 713 722 2859 (voice)
+1 713 932 0222 (fax)
+1 713 722 2700 (switchboard)
alex.johnson@xxxxxxxxxxxxxxxx
I hope to see you at the Invensys Process System User Group meeting October
3-6 in Houston, TX -
www.invensys.com/usergroup2005
_______________________________________________________________________
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
_______________________________________________________________________
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:
