Alarm System Connected Via 5500SHAC (TCP/IP - Cleint)

Discussion in 'C-Bus Automation Controllers' started by Peri92, Aug 13, 2019.

  1. Peri92

    Peri92

    Joined:
    Aug 6, 2019
    Messages:
    1
    Likes Received:
    3
    Hi Guys,

    I have been trying for the past few days to get my Inception alarm system to control CBUS via 5500SHAC.

    I have seen anther post where someone has the "Inner Range Inception" alarm system working via RS232.

    Although the Inception panel also has the functionality to send TCP/IP messages.

    I have FINALLY got it working and thought i would share my finding.

    I have been able to connect the Inception system to the SHAC_CNI, with the below settings.

    Connection type: TCP (Client)
    Port: 10001
    IP Address: 192.168.178.199

    With these setting it is the only way i get the status as "Connected".

    (Not sure if required although i have also added the below to the "C:\Clipsal\C-Gate2\config\access.txt")

    interface 192.168.178.82 operate
    remote 192.168.178.82 operate
    user <username> <password> operate

    Of course I have the correct username and password i just haven't posted them on here.

    My current setup is:

    SHAC_IP:
    192.168.178.199
    Inception_IP:
    192.168.178.82
    5500PCU:
    USB Serial (Used for Diagnostic Utility).

    The Inception system requires "Data Framing" (Refer to the link above for the image).
    - Prefix for Sent Messages:
    - Suffix for Sent Messages:
    - Prefix for Received Messages:
    - Suffix for Received Messages:

    If i set all the above as (empty) the review logs show me a message being received every second.
    Message: \x11

    When i turn a light on from the Diagnostic Utility i get the following (received message) in the review log on the Inception alarm system: \052D380100010193\r\n

    Then I set the framing as;
    - Prefix for Sent Messages: \
    - Suffix for Sent Messages: \r\n
    - Prefix for Received Messages: \
    - Suffix for Received Messages: \r\n

    And I am now receiving and sending the correct commands.
     
    Peri92, Aug 13, 2019
    #1
    MarkB, Timbo and cbus-ed like this.
  2. Peri92

    Robbo_VIC

    Joined:
    Jan 24, 2011
    Messages:
    145
    Likes Received:
    0
    Location:
    Melbourne, VIC
    Resurrecting an old thread here, but I have tried on a couple of sites now and just can't get this integration to work consistently.

    This site I am on now has a dedicated CNI for the Inception, and I am able to send commands from the Inception to the Cbus network, but I just can't get the Inception to listen to all the other Cbus messages.

    Even with Nothing in the prefix and suffix for received messages, I'm not seeing anything in the log when I have enabled Detailed events.

    I'm thinking something to do with the CNI needing to be setup to broadcast all messages? I have had a ticket open with Clipsal for a while now and I haven't got any response.

    Previously I had it set to talk to a Wiser2 and I managed to get that working, but after a week or so it would drop out. I am assuming this is due to the network interface on the Wiser being taken over when someone opens the app, and it severs the connection to the Inception.
     
    Robbo_VIC, Jul 11, 2025 at 1:07 AM
    #2
  3. Peri92

    Timbo

    Joined:
    Aug 3, 2004
    Messages:
    24
    Likes Received:
    4
    Location:
    Perth, Australia
    I didn't think you'd be able to configure the Inception to receive commands from a CNI, you need to mangle the C-Bus messages and form appropriate HTTP(S) REST API commands to push to Inception... ie using a SHAC/NAC etc etc.
    How are you firstly initialising the CNI to broadcast the C-Bus messages to the Inception IP (across reboots)?
    How are you extracting appropriate parts of the C-Bus messages in the very basic 'Data Framing' custom connection settings?

     
    Timbo, Jul 11, 2025 at 2:16 AM
    #3
  4. Peri92

    Colin Moderator

    Joined:
    Aug 3, 2004
    Messages:
    142
    Likes Received:
    26
    Location:
    Australia
    The original thread discusses using NAC and SHAC devices, not as web servers or for framing, but for their CNI feature. This is similar to using a 5500 CNI, where the main difference is transmitting the same strings over a TCP packet to the CNI.

    To get a CNI to respond correctly with information or events from C-Bus, refer to the setup guide for CNI/PCI. You can configure the CNI/PCI to transmit events from C-Bus over an established connection and ensure configurations are retained on power up or restore.

    If referring to the PCI user guide, it is recommended to set up the PCI/CNI with the correct configuration initially and handle power-up notifications and other configurations as needed. The Inception panel may not support this, but you can configure the CNI/PCI to power up in a known state.

    Additionally, you can set application filtering to receive events only from specific applications, such as the lighting application (application 38).

    The Inception panel may not understand all events coming back from C-Bus, even if the application is filtered. It likely does not understand state corrections that occur on C-Bus frequently. The PCI/CNI can be configured to pass these events onwards or not, as needed (refer to the user guide for this configuration).

    It is also unknown if the Inception panel can handle concatenated messages. C-Bus can send events in one package, including multiple groups in the same communication stream. For example, a packet might turn on/off multiple groups or change the level of multiple groups in a single event. It is unclear whether the Inception panel can process these concatenated messages.
     
    Colin, Jul 11, 2025 at 2:48 AM
    #4
    Timbo likes this.
Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.
Similar Threads

  1. Alternative Ness alarm system?

  2. Switchs connected via patch panal.

  3. Help how to arm homesafe alarm panel via CBUS

  4. Comfort Alarm System with C-Touch

  5. Cbus intergration with Bosch Solution 64 Alarm System

  6. TCP/IP Commands via CNI

  7. Ness Dx16 Alarm System

  8. D8x alarm system and outputs

Loading...