Contents:
- Fault Indication
- LEDs1 and 2
- Modbus Registers
- Fault Codes
- NON-Toshiba Fault Codes (Special Fault codes)
Fault Indication
FDP3-Modbus interfaces indicate a fault state in two ways:
- LEDs 1 and 2
- Input Registers 0021, 0022, and in case of group control: **21 and **22 (*..is the remote controller's TCC-NET address of a unit in the group and is only in the range: 01 < ** < 08).
LEDs 1 and 2
The LED statuses which indicate a fault situation are explained in the FDP3-Modbus installation instructions. Note that the LED status is not enough to tell which indoor unit fault has occurred. The exact fault can only be identified through the Modbus fault code register(s) or the wired remote controller's display.
Modbus registers
If there is an active fault in the system the value of Input register 21 is changed. This register returns 0 if there is no fault and 1 if there is at least one unit in fault. More details can be found in the FDP3-Modbus inbstallation instructions.
Input register 0022 returns the indoor unit's fault code. This is the same error code displayed on the wired remote controller's display (see Special Fault codes below).
If several indoor units are grouped on the remote controller's TCC-NET network follow the instructions detailed in this article.
Please note that fault code registers are Modbus Input registers.
Fault Codes
For the list of Toshiba fault codes, please see the attached file.
Please note that the Fault codes are 16 bit values. For details on encoding of the Fault Codes please see the attached FDP3-Modbus installation instructions (page 3).
NON-Toshiba Fault codes (Special Fault codes)
The FDP3 interface has two fault codes that are generated by the interface itself and not by the indoor unit. These are:
- 14384: (80) Group Fault, timeout on no units found
- 14388: (84) Unit Missing, reported if unit data previously observed (on the TCC-NET network). If there are more than one unit on the network and some units are powered down or there are some changes in network connection this fault may be signalled (because FDP3 is powered from unit).
In any of both cases above try powering down the FDP3 interface and then powering up again.