Access Expert unable to bring downstream devices online

[Product_Support]

Issue

Downstream interfaces/controllers appear as Unknown or remain Offline in Access Expert and cannot be brought online.

Product Line

EcoStruxure Access Expert

Environment

Downstream controllers/interfaces

Cause

Offline downstream interfaces can occur for several reasons:

• The downstream controller has not been set to Active after being added to the system.
• Interfaces were added after the controller was already activated, and the controller has not been rebooted to receive the new configuration.
• DIP switch settings or device addressing are incorrect.
• RS-485 wiring is incorrect.
• End-of-line (EOL) termination is not configured correctly.
• Duplicate addresses or baud rate mismatches exist on the RS-485 network.
• Power supply issues prevent downstream devices from communicating reliably.

Resolution

1. Verify Device Activation

• Navigate to the controller configuration page.
• Confirm that the downstream interface/controller is set to Active.
• If the interface was recently added, perform a Full Download or reboot the main controller to force the updated configuration to download.

2. Reboot the Controller

• Reboot the controller associated with the offline interface.
• This allows the controller to download and apply the correct configuration.

3. Verify DIP Switch Settings and Addressing

Check that the DIP switch configuration matches the settings configured in Access Expert.

• Switches 1–5 define the device address in binary (addresses 0–31).
• The address configured in Access Expert must match the physical DIP switch address.
• Switches 6 and 7 define the baud rate. The default setting is 38400 baud with both switches ON.
• Switch 8 should be OFF to disable AES key encryption. Communication is encrypted through TLS 1.2.

Note: DIP switch orientation may appear inverted compared to labels on other connectors. For example, on an MR52 board, the ON label is located below the switch bank.

4. Verify RS-485 Wiring

• Ensure all panels are wired correctly according to the hardware installation guide.
• Verify RS-485 communication wiring polarity and continuity.
• Use a true daisy-chain topology.
• Avoid star configurations and wiring stubs.

5. Verify End-of-Line (EOL) Termination

• Confirm that EOL termination jumpers are configured according to the hardware installation guide.
• Enable termination only on the last physical controller in the RS-485 chain.

6. Verify Address and Baud Rate Consistency

• Inspect the physical DIP switches on all downstream controllers.
• Ensure each downstream controller has a unique address.
• Verify that software-configured addresses match the physical settings.
• Confirm that all devices on the same RS-485 segment use the same baud rate.

7. Isolate the Affected Controller

1. Disconnect the second downstream controller from the RS-485 network.
2. Verify whether the first controller remains online.
3. Connect only the second controller to the main board.
4. If the controller still fails to communicate, investigate:
   • Duplicate addressing
   • RS-485 communication hardware faults
   • Local power supply issues

8. Verify Power Supply Health

• Measure voltage at the downstream controller power input.
• Confirm voltage remains stable between 12 VDC and 13.8 VDC under load.
• Low or unstable voltage can cause controllers to go offline, especially when readers, door strikes, or other peripherals draw power.