Specifications
RN: 2-26
RS3: Software Release Notes for P1 R4.2
Software and Hardware Requirements
Table 2.28. CPII ControlFile with MPCII and Standard Controllers
CP NV Memory Controller Image and Hardware to Support Image
Image Hardware
Boot
ROM
Size/Type
Controller Image
File Name
Controller
Image
Hardware
Boot
ROM
Max Config
$
$
C
P
M
A
X
1
8
CPII 2.70 2MBNV
R
A
M
CC 5.15
$
$
C
PM
A
X
18 R
A
M
(Requires
1
1
5
N
V
CC
MPC(I)
(2)
5.15
1.15
N
V
Boot) or
MPCII
(3)
6.05
1MBNV
R
A
M
$
$
C
P
M
A
X
1
8
(
1
)
MLC MLC 5.15
R
A
M
(Requires
1
1
5
N
V
$$CPM
A
X
18
(
1
)
MUX/PLC 5.15
1
.
1
5
N
V
Boot) or
MUX
MPC(I)
(4)
5.15
1 MB Bubble
o
r
MPCII
(5)
6.05
o
r
0.5 MB
B
u
b
b
l
e
SSC SSC 5.15
B
u
b
b
l
e
$
$
M
P
C
A
1
8
M
P
C
MPC(I) 5.17
$$MPC
A
18 MPC
MPCII
(6)
6.05
$
$
M
P
C
A
S
1
8
M
P
C
A
S
MPC(I) 5.21
$$MPC
A
S18 MPC
A
S
MPCII
(6)
6.05
(1)
These controller images are part of the $$CPMAX18 image. No additional controller images are needed.
(2)
An MPC(I) controller jumpered to run the Contact Controller image
(3)
An MPCII controller jumpered to run the Contact Controller image
(4)
An MPC(I) controller jumpered to run the MUX image
(5)
An MPCII controller jumpered to run the MUX image
(6)
An MPCII controller jumpered to run an MPC(I) image
NOTES:
For an explanation of the various MPC(I) images, see Table 5.2 of the ”Software Loading and Upgrade Procedure,
Including Batch” which accompanies these Release Notes.
D
Boot ROM level X.YY is the minimum required; a higher .YY number will also work.
D
CPII ControlFile nodes use V18 images contained in the P1 R4.x software release. Only the combination of hardware
and software listed in the above table is supported.
D
The size of NV memory or bubble card required depends on the combination of images needed in the ControlFile.
See the section Memory Allocations and Plant Program Space on page 2-34 and Table 2.32 to Table 2.36 to
determine the size of NV memory card required.
D
The NV boot level is listed as the BRAM field on the ControlFile Status (CFS) screen.
General Hardware Upgrade Information
D
$$CPMAX18 is the only CPII image supplied with the P1 R4.x software release.
D
A CPII ControlFile running batch, if it needs to continue to run batch after the upgrade to P1 R4.x, must have its
hardware upgraded to Table 2.23 or Table 2.25.
D
Rosemount Basic Language Controller (RBLC) image is only supported with MPCII or MPC5 controllers in the P1
R4.x software release. Any MPC(I) running RBLC image must be upgraded to an MPCII.
D
With a CPII, the CPMAX CP image stores part of the controller configuration in the CP memory. A CPIV, CPIV+, or
CP5 does not provide this functionality. The portion of the controller configuration that was stored in the CPII memory
will now have to be placed back into the controller. Therefore, all controllers in a CPII ControlFile running CPMAX
need at least 20% free space if the CPII is upgraded to a CPIV, CPIV+ or CP5. There should be a trial load of the
Config on a test system before the plant upgrade to make sure the Config will fit.
(continued on next page)