Specifications

168 GX Configurator-PN
(c) 2013 MITSUBISHI ELECTRIC CORPORATION
refresh area size needed for data exchange between PN controller and controlling CPU.
2. there is no input corresponding to the 'CPU Specific Send Range' in the 'Multiple CPU Setting' tab
of the GXW2 'Q Parameter Setting' dialog. This value is always calculated from the value of the
'Additional user area size' and the auto refresh area size (added sizes of the configured refresh
blocks).
3. the number of refresh blocks is fixed to 3 for both the PN controller and the controlling QnU CPU.
Only on the controlling QnU-CPU additional auto refresh blocks can be configured for example to
exchange data with a motion CPU.
4. the CPU type property of both the PN controller and the controlling CPU is read only. The position
of either CPU in the rack can be changed by manually selecting a different scenario or by scan-
ning the rack online via the ‘Check PLC’ button. If the actual rack position differs from the configu-
ration in the dialog, the user can have the dialog automatically updated.
When the 'Multiple CPU Settings' dialog must be used
The ‘Multiple CPU Settings’ dialog is needed,
if additional CPUs beside the PN controller and the controlling QnU-CPU are mounted or if empty
slots between CPUs are required
if PLC program projects and/or parameter files should be updated in order to assign the file paths
If additional CPUs such as a Q17nNC or a motion CPU are mounted, the following configuration opti-
ons are supported:
1. specifying the additional user area size for Q17nNC and motion CPUs. The CPU specific send
range is calculated based on this value and the auto refresh area size.
2. configuring refresh blocks for motion CPUs only. For Q17nNC CPU this property cannot be chan-
ged and is always 0.
Comparison of GXW2 'Multiple CPU Setting' tab and GXPN 'Multiple CPU Set-
tings' dialog
In GXW2 the user starts by entering the 'CPU Specific Send Range', here e.g. 3k. In GX Configura-
tor-PN this value is calculated by adding the 'Additional user area size' of 2048 words and the total
size of all refresh blocks, here 100 words and then rounding up this sum to the next multiple of 1k
words. The memory section to the next multiple of 1k words, in this example 924 words (= 3k -
2148), is technically part of the user area, which explains the difference between the 'Additional user
area size' of 2048 words entered by the user and the actual user area size of 2972 words (= 2048 +
924) set in the CPU, which is displayed in GXW2 as 'User Setting Area - Points'.
Configuring Send CPU Devices
The refresh blocks differ from the user area in high speed memory in the fact, that they can be asso-
ciated to device addresses in the respective CPU. The CPU, on which the refresh block is located,
contains the so-called 'Send device', from which data is copied to the refresh block on the same
CPU. Any of the other CPUs, which support device addresses, can read the data from the 'sending'
CPU by specifying a 'Receive device'. The contents of the refresh block on the 'sending' CPU are
then automatically copied to the 'receive device', where they can be processed by the receiving CPU.
Note: it is important to remember that refresh blocks are not necessarily for a one-to-one, but a one-
to-many communication, i.e. the data provided by one CPU can be simultaneously read by any of