124 Network Guide
Table 40: Error code Interpretation for Allure EC-Smart-Vue Sensor Symptoms
Device is not communicat-
ing with controller
Is the address correctly set
to a unique address?
Each Allure EC-Smart-Vue sensor must be set to a unique address for
each controller. See Commissioning a Controller with an Allure EC-
Smart-Vue Sensor on page 98.
Is the device too far from
controller?
Verify the distance between the device and the controller. See Subnet-
work Data Bus Length on 75.
Is there a configuration
problem?
With EC-gfxProgram, check the configuration of the sensor, for exam-
ple, is it enabled? Refer to the EC-gfxProgram User Guide for more
information.
Have the subnetwork EOL
settings been correctly set?
Only the last module on the subnetwork data bus must have its EOL
termination set to ON. See Figure 51, Figure 53, and Figure 54. When
one or more ECx-400 Series IO Extension modules are connected to
the controller, only the last ECx-400 must have its EOL termination set
to ON. See Figure 61.
Controller cannot communi-
cate on the LONWORKS
network (ECL controllers
only)
Too many Allure EC-Smart-
Vue sensors are providing
network access
Disable the Net to Subnet Port Settings jumpers on all controllers (for
jumper location, see LAN through an Allure EC-Smart-Vue Sensor for a
LonWorks Network on page 104). If communications are re-estab-
lished, re-enable only a few Allure EC-Smart-Vue sensors to have net-
work access.
Allure EC-Smart Vue sen-
sor motion detector window
indicator is always ON
Does the connected con-
troller have Allure EC-
Smart-Vue sensor firmware
that supports the motion
and CO
2
sensor?
When the Allure EC-Smart-Vue sensor is connected to a controller, its
firmware is loaded from the controller. In this case, the controller has an
earlier version of Allure EC-Smart-Vue sensor firmware that does not
support the motion or CO
2
sensor. To upgrade to the latest Allure EC-
Smart-Vue sensor firmware, download the firmware from SmartInstaller
and refer to the firmware upgrade procedure in the EC-
gfxProgram
User Guide.
The Motion or CO
2
output
of the associated ComSen-
sor block always reads
NULL in EC-gfxProgram
The CO
2
sensor readings
are too high, too low, or
inconsistent between sen-
sors
Immediately after installing
the Allure EC-Smart-Vue
sensor with CO
2
sensors,
are the CO
2
sensor read-
ings incoherent?
If the CO
2
sensor readings seem unusual or show inconsistencies
between sensors in the same building right after installation, the follow-
ing reasons should be taken into consideration:
- Concentration levels in each space may be different
- The installer may have unintentionally blown into the sensor while
installing it.
- The sensor may have been dropped or mishandled during shipment
causing a minor shift in the original factory calibration.
Allow up to 14 days of operation (without power interruptions) for the
sensor to calibrate itself according to its new environment.
Symptom Possible Cause Solution
Symptom Possible Cause Corrective Action
Clock icon flashing for 15
seconds
Cannot communicate with
controller.
Wait for the communication link to the controller to be established.
Verify wiring.
Verify that all Allure EC-Smart-Vue sensor's Subnet IDs are unique for
this controller. See Setting the Allure EC-Smart-Vue Sensor's Subnet
ID Address on page 98.
After 15 seconds: Error
code 1 with Bell icon
Error code 2 with Bell icon Invalid configuration. In EC-gfxProgram, resynchronize the code with the controller.
Contact Distech Controls customer support.
To Next Page
Loading...
Need help?
General
