Skip to content
  • There are no suggestions because the search field is empty.

Connect/Gateway panel guide: Honeywell XLS3000

Overview

Nimbus supports connection to either an Isolated RS232 Interface or the Mainboard RS232 Port.

Equipment required

From Nimbus

  • A Nimbus Connect or Fixed Gateway device

  • A Male 'D' Type panel connector (part no 201-304-01) - if connecting to the mainboard RS232 port

From the panel manufacturer/3rd party

  • 3 core screened data cable

  • Notifier ID3000 Isolated RS232 Interface PCB (PN:020-478) - if not connecting via the mainboard

 

    Panel configuration

    1. Navigate the menu according to the required connection method

      1. User Menu

      2. Option 6 (enter level 3 password)

      3. User Menu

      4. Configuration

      5. Option 6: Panel Settings

      6. Option 17: Isolated RS232 Interface

        ...or...

        Option 18: Mainboard RS232 Port

    2. Configure as below

      1. Type: 3rd Party RS232

      2. Baud rate: 9600

      3. Protocol Version: 011A Protocol

      4. Port Setup: Full Duplex

      5. Controls: Disabled

      6. Fault Monitoring: Disabled

      7. Suspend Time Limit: 0 & Not Logged

      8. Incoming Data Timeout: 1 Second

      9. Allow Time Sync from 3rd Party: No

    It may be necessary to power cycle the control panel following a port configuration. Upon initial connection the event log may download.

     

    Wiring

    Isolated RS232 Interface

    Using 3 core screened data cable wire to the Nimbus RS232 as follows.

    Isolated RS232 Interface Nimbus RS232
    0V Ground
    Tx Rx
    Rx Tx

     


    Mainboard RS232 Port

    Connect the Nimbus Male 'D' connector to then RS232 port on the mainboard.

    Using 3 core screened data cable wire to the Nimbus RS232 as follows.

    Male 'D' connector Nimbus RS232
    0V Ground
    Rx Tx
    Tx Rx

     

     

     


    Troubleshooting

    If Nimbus appears to be recording each event 10 times, check the connection between Nimbus Connect and Panel, specifically the Nimbus Connect TX to Panel RX. A poor connection will result in the acknowledgement from the Nimbus Connect to Panel not being received and 10 copies of each event being reported.