Table of Contents
Advertisement
7.
Cases for which Undefined Blocks are Generated
Cases for which undefined blocks are generated and measures to be taken when you do not want the
undefined blocks to be generated, are described below.
(1)
When there is an R/C group which belongs to a contract, but is not allocated to a block, its power
consumption is apportioned to an undefined block.
To prevent generation of an undefined block
●
Allocate all R/C groups to blocks.
●
When that is not possible, either allocate it to a common block, or power off the indoor unit and
perform re-scan so that it is removed from the electricity charge apportionment object.
(2)
When the electricity charges of a common block are to be freely distributed to tenant blocks and
the total is not 100%, the power consumption under 100% is apportioned to an undefined block.
●
To prevent generation of an undefined block, make sure that the total distributed power consump-
tion is 100%. In addition, when the period of the allocated blocks do not match, an undefined
block is generated for periods that do not match.
(3)
On the day with no block defined, with just common blocks or with blocks but when some units
remain unallocated, those energy consumption are apportioned to undefined blocks.
●
To prevent generation of an undefined block, disable the electricity charge apportionment function
during that period.
8.
Electricity charge apportionment error
Errors and their main causes related to electricity charge apportionment detected by the System Con-
troller Lite are described.
(1)
Generation conditions
●
Generated when a unit that does not send the information necessary for electricity charge appor-
tionment (non-communicating unit) is detected during the period electricity charge apportionment
data collection is performed.
Judgment, performed for the outdoor unit and the indoor unit, is based on whether there is no
communication for more than 30 minutes or not.
(2)
Processing of errors by the
●
Electricity charge apportionment error with the unit address are displayed for the non-communi-
cating unit.
The generation time and recovery time are recorded in the error history as with the other errors.
●
In the electricity charge apportionment calculation, non-communicating unit is handled as follows:
· Non-communicating indoor unit: Handled the same as an indoor unit whose operation is stopped
by a remote controller
· Non-communicating outdoor unit: When the non-communicating unit is a master unit, since the
minimum data necessary for electricity charge apportionment is not collected, apportionment
calculation of the relevant refrigerant system is not performed. (Charge becomes "0".) When a
slave unit is the non-communicating unit, calculation is performed as if the slave unit does not
exist.
●
Whether or not the outdoor unit standby power is apportioned to non-communicating indoor units
can be set from the basic setting screen.
(3)
Recovery conditions
●
When the data necessary for electricity charge apportionment can be acquired from the relevant
unit, the electricity charge apportionment error is reset.
Copyright© 2013-2015 Fujitsu General Limited. All rights reserved.
System Controller Lite
247
Advertisement
Table of Contents
