When doing maintenance type functions like ICCprint all block
parameters...etc...the pdef/olist file is used as the template to go retrieve
values from the existing database.
So whether a CP60. 270, 280 the attempt will be made and just fills in default
values if they don't apply.
CHAN parameter in ICC only appears when configuring a CP280
As to lbugs...FCP280 has 4 individual Ports.
Each Port can use the 0-3 baseplate ID in the lbug.....but all must be unique
throughout the whole CP
So if you do use the 0-3 baseplate designation...then the first 4 characters
must be unique...
As example:
Port1 could be JOHN01-38
Port2 could be PAUL01-38
Port3 could be HANK01-38
Port4 could be STAN01-38
Or
The FEM letterbug scheme also works on the FCP280 ports...
PORT1 could be JOHN01-38
PORT 2 could be JOHN41-78
PORT3 could be JOHN81-B8
PORT4 could be JOHNC1-F8
-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx] On
Behalf Of foxpat
Sent: Monday, November 16, 2015 11:58 AM
To: foxboro@xxxxxxxxxxxxx
Subject: Re: [foxboro] ECB CHAN parameter new but not in ICC ??
I'm confused!
1)
What I still do not understand is why CHAN appears in the icc get listing when
getting all ECB parameters for ECB blocks in CP60 or CP270 which do not seem to
have, nor will they ever need, the CHAN parameter.
I have not tried yet to 'DONE' an ECB on any of the ECB's but I would be very
surprised to find the CHAN parameter in the ICC.
How can it be? It is not part of the CP60 or CP270 image, is it?
ICC should (at least I would expect it) show only parameters relevant for the
CP's software version?!
2)
So the CHAN was added to SELECT(?) which of the 4 internal CP280 field buses to
use?
Does that mean we will be faced AGAIN with a new FBM letterbug convention?
CP60 with FCM:
Letterbug xxxFNS where F = 1 to 4 for FCM 1 to 4, each FCM having max. 4 nests
(N=nestnumber 0 to 3, S=slot 1 to 8)
Upgrade this to FCP270 with FEM:
Letterbug xxxxNS where the N=nest 0 to F, requiring to change letterbugs for
all FCM 2, 3 and 4 FBMs.
We did this by save_all of CP60, load_all into test system CP270, run ICC to
delete all ECBs for FCM 2, 3 and 4 and add new ECB's with new letterbug format
and change IOM_ID for all I/O blocks concerned and finally save_all of
testsystem CP270.
All this just a few days in advance of a major planned plant-stop. Load_all
after CP270's, FEM, new fieldbus cabling and not to forget, all new vertical
baseplates were installed.
Now what if we are upgrading CP60 to CP280?
I guess we would need a (test) system with CP280 first?
It will not be any time soon, but just curious to know!
Kind regards,
Patrick Martens
Zeeland Refinery
-----Oorspronkelijk bericht-----
Van: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx]
Namens gheyIl .
Verzonden: maandag 16 november 2015 20:02
Aan: foxboro@xxxxxxxxxxxxx
Onderwerp: Re: [foxboro] ECB CHAN parameter new but not in ICC ??
To get back to the original question, can CHAN be changed by script? I don't
think so because it is "fixed" at the time of ECB creation, like HWTYPE or
DEV_ID. Am I wrong?
_________________________________________________________________________
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
