Paul,
I appreciate your attempt to clarify. I agree that most users are
confused, myself included. There have been so many System names, application
names, platform names, etc. floating around since the Foxboro / Wonderware
merger that I don't even think Foxboro sales and application folks know what is
what. It would be great if someone could compose a little table that showed
the current names of all the Foxboro related products with a short description
of their basic function. Ideally the table would also show the older product
name that used to serve that same function. Something like:
"Control Software" - Provides a GUI based interface used to configure Foxboro
process control strategies via function blocks or control templates comprised
of many function blocks. This application supersedes functionality previously
provided by:
Integrated Control Configurator, (ICC)
I/A Series Configuration Component, (IACC)
Control Editor ........ etc.
Regards,
Tom VandeWater
Control Conversions, Inc.
-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx] On ;
Behalf Of Paul McQuaid
Sent: Monday, February 06, 2017 11:13 PM
To: foxboro@xxxxxxxxxxxxx
Subject: Re: [foxboro] EVO - ECB Name v. ECB DEV_ID
I hope you don't mind me piggy backing on your thread but in order to avoid
confusion.... "Foxboro Evo" is a software bundle with two major component
parts, it does not really have a release version of its own.... it, broadly
speaking, consists of.....
- "Control Software" Currently at V6.3 which consists of software based on
Wonder Ware "System platform", including "InTouch" and "Application Server",
but, importantly, built on with additional component features to provide
support for the Foxboro Evo DCS System. E.g ArchestrA objects suitable for
compounds , Strategies, et al, and over 2000 pre designed InTouch screens to
work, out of the box so to speak, e.g. Block detail screens.
- "Control Core Services" currently at V9.3, which is the DCS software evolved
from the former I/A software.
I have experience quite some confusion amongst my customers with regard to
this, hence my attempt at some clarification....
Best Regards
Paul McQuaid
Senior Technical Training Instructor
-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx] On ;
Behalf Of William C Ricker
Sent: 06 February 2017 18:42
To: foxboro@xxxxxxxxxxxxx
Subject: Re: [foxboro] EVO - ECB Name v. ECB DEV_ID
Rereading this, I should be more specific.
In an EVO 6 system, when importing a SaveAll into BulkData and generating
blocks, it seems the block name for an ECB must always be the same as DEV_ID.
Does anyone know of a way to divorce these two? So that the DEV_ID and ECB NAME
can be different values, or, described differently, so the ECB Block name is
not overwritten by the value of DEV_ID.
Thanks
William C Ricker
-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx] On ;
Behalf Of William C Ricker
Sent: Monday, February 06, 2017 12:28 PM
To: foxboro@xxxxxxxxxxxxx
Subject: [foxboro] EVO - ECB Name v. ECB DEV_ID
Friends and neighbors,
In an EVO 6 system, it seems the block name for an ECB must always be the
DEV_ID.
Does anyone know of a way to divorce these two? So that the DEV_IS and ECB NAME
Can be different valus.
Thanks
William C Ricker
_________________________________________________________________________
This mailing list is neither sponsored nor endorsed by Schneider Electric
(formerly The Foxboro Company). Use the info you obtain here at your own
risks. See the disclaimer at 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 Schneider Electric
(formerly The Foxboro Company). Use the info you obtain here at your own
risks. See the disclaimer at 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 email has been scanned by the Symantec Email Security.cloud service.
______________________________________________________________________
*** Confidentiality Notice: This e-mail, including any associated or attached
files, is intended solely for the individual or entity to which it is
addressed. This e-mail is confidential and may well also be legally privileged.
If you have received it in error, you are on notice of its status. Please
notify the sender immediately by reply e-mail and then delete this message from
your system. Please do not copy it or use it for any purposes, or disclose its
contents to any other person.
_________________________________________________________________________
This mailing list is neither sponsored nor endorsed by Schneider Electric
(formerly The Foxboro Company). Use the info you obtain here at your own
risks. See the disclaimer at 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 Schneider Electric
(formerly The Foxboro Company). Use the info you obtain here at your own
risks. See the disclaimer at 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