6. Redundancy with NX3030 CPU
323
ATTENTION:
At the physical construction of these remotes (electric panels), it’s strongly recommended to insert
compatible bases with the future I/O modules in the respective positions. This way, when the I/O
module insertion is necessary in this remote, there’s no need for switching off the remote to insert
the base. In case this detail isn’t observed, it will be necessary to switch off the specific remote, as
it’s not possible a base hot insertion in the remote. It can be observed that the remote stopping in
some cases can be tolerable, but not always.
ATTENTION:
The original I/O module bases must be inserted in the first remote rack positions and the future I/O
modules, in the last remote rack positions.
ATTENTION:
It must be considered the limitations of the Ponto Series redundant remotes at constructing this list,
as the PO5063V1 PROFIBUS Head Utilization Manual and PO5063V5 PROFIBUS Redundant
Head, and PO5064 PROFIBUS Head Utilization Manual and PO5065 PROFIBUS Redundant Head.
There are limits regarding the number of modules per remote, number of bytes per remote, current
consuming per power supply, etc. These limits are verified automatically by the ProPonto. For
further information, see the MT6000 MasterTool ProPonto Utilization Manual - MU299040.
Step 2 – Insert the Redundant PROFIBUS Network Initial Version in the Project
To insert the redundant PROFIBUS network initial version in the project, initially the two redundant
NX5001 modules must be inserted in the rack, or use those already inserted by the redundancy
wizard.
Next, each remote must be inserted in the device tree below these two NX5001, as well as the I/O
modules under each remote.
Regarding the inserted I/O modules, there are two categories that must be treated differently:
ï‚· Those that are part of the PROFIBUS network initial version and will be installed immediately
ï‚· Those that will be used for future expansion
In the case of those that are part of the PROFIBUS network initial version, the module itself must be
inserted in the device tree, in the planned remote correspondent position.
In the case of those that will be used for future expansion, a virtual module must be inserted in the
planned correspondent position. A virtual module correspondent to a real module needs to allocate
the same amount of I/O bytes than this real module. The virtual module insertion in the place of a
real module avoids the real module absence diagnostics to be produced.
The following Table 6-4 shows real modules and its correspondent virtual modules:
Correspondent Virtual Module
PO9999 – 2 bytes output
PO9999 – 2 bytes output
Table 6-4. Virtual Modules correspondent to the real modules
To Next Page
Loading...
General