Product: Fixture Applies to All versions of fixtures
Warning: Only trained and qualified personnel should be allowed to install, replace, or service this equipment based on local and national electrical codes.
- How to verify and what to check when sensors are not communicating. Are they configured correctly? This condition could be caused by:
- The fixture has no power
- The network connection to the gateway that communicates with the fixture is down
- Gateway (GW) has a problem
- The image file on the fixture sensor is corrupted
- The radio parameters used to communicate between the sensor and gateway are corrupted on the gateway or sensor
- There is a new source of interference on the radio channel used by the sensor
- There is a hardware fault with the fixture sensor
- There is a hardware fault with the fixture's Control Unit
- There is a damaged cable between the sensor and Control Unit (CU)
The first check is to determine the status of the gateway. This is done by either moving the cursor over or double-clicking the gateway on the floor plan. If the status shows no network connectivity, then you should follow troubleshooting A gateway has no communication before proceeding. Note that even if the GW indicates that it has connectivity, it may still have problems with its wireless interface. If there are several fixtures that have no connectivity, try double-clicking on the gateway to display the Gateway Details screen. On it, click the Update button. This resends the radio parameters to the gateway and causes the wireless interface to be reset.
Try turning the power off and on to the fixture. If this does not resolve the problem, try Step 3.
Check to see if a source of radio interference has been added near the fixture, or in the line of sight between the sensor and the GW. (Note that a source of radio interference will generally affect multiple fixtures and not just one. If multiple fixtures have lost communication, then contact your system installer or Enlighted.)
Check the LEDs on the sensors.
- LED Off: The sensor is not receiving power. This could be due to no power to the fixture, a damaged cable between the CU and SU, or a failed CU. (NOTE: check to make sure that the fixture is not controlled by a sweep timer that disables power to the fixture during set times, such as from 6 pm to 7 am.)
- Red blinking: The CU has failed or the cable between the CU and sensor is damaged.
- Red solid: Finally, if the red LED is on continuously, it indicates a hardware fault or a firmware image corruption on the sensor.
In all the above cases an electrician is required to troubleshoot further and resolve.
The remaining cause of the problem is that the image or configuration has been corrupted. To resolve, you must replace the SU following the RMA procedure. Refer to the RMA Warranty FAQs, and Replacing a Defective Sensor.
Sensor LED Status for Firmware versions later than 4.0
|Red solid||The sensor has detected a critical error at start-up and is not able to continue|
|Green solid||The sensor started up and detected no errors. The sensor is not commissioned.|
|Blue solid||When a sensor is not commissioned, the sensor is being asked by the commissioning application to identify itself. When the sensor is commissioned, the user has set the light level of the sensor to 100%.|
|Blue turns off||When a sensor is not commissioned, the sensor is being asked by the commissioning application to stop identifying itself. When the sensor is commissioned, the user has set the light level of the sensor to 0%.|
|Red blinking||Sensor start-up detected wiring errors. The sensor is not commissioned.|
|Green blinking||The sensor is commissioned and has detected motion.|