C-Bus PC Interface Housed, 4M, DIN Rail Enclosure

C-Bus PC Interface Housed, 4M, DIN Rail Enclosure

C-Bus PC Interface Housed, 4M, DIN Rail Enclosure

Item Number: 5500PC

Datasheet

Specifications

Design

Range of product

C-Bus

Range

C-Bus

Product brand

Clipsal

Product or component type

interface module

Device application

connection

Sustainable offer status

Green Premium product

Physical

Mounting support

DIN rail

Local signalling

LED

IP degree of protection

IP20

REACh Regulation

Free of Substances of Very High Concern above the threshold

REACh free of SVHC

Yes

EU RoHS Directive

Compliant

Toxic heavy metal free

Yes

Mercury free

Yes

RoHS exemption information

Yes

China RoHS Regulation

 Pro-active China RoHS declaration (out of China RoHS legal scope)

Environmental Disclosure

ENVPEP111268EN

Circularity Profile

ENVEOLI111254EN

Others

Number of modules

4

Communication port support

RS232

Transmission rate

9600 bauds

Unit Type of Package 1

PCE

Number of Units in Package 1

1

Package 1 Weight

351 g

Package 1 Height

9 cm

Package 1 width

12.5 cm

Package 1 Length

16 cm

WEEE

The product must be disposed on European Union markets following specific waste collection and never end up in rubbish bins
Show all specifications

Documents & downloads

hide show
Filter items
  • All

  • Product Brochures

  • CAD Files and Packs

  • Installation Instruction

  • Specifications

  • Application Solutions

  • Software - Release

  • Software - Archive

Frequently Asked Questions

hide show

Feedback for PUSH Controls slow from C-Bus?

PUSH Contols is not getting feedback from C-Bus property, is slow or not at all?

Note: These recommendations or suggestions below are assuming you are familiar with programming PUSH Controls, have the Project Editor Software & have the original project file (.bwe).

I. RS232 preferable

Symptom: slow feedback or control
During our testing when developing the C-Bus module, the performance of the C-Bus module is much better when using C-Bus 5500PC (RS232) compared to C-Bus 5500CN (TCP).
IMPORTANT: when changing communication method between RS232 and TCP, make sure to re-upload the project programming both to the Push controller and Push app (iOS or Android). Otherwise your site (or part of it) will still be using the old communication method.

II. Double Check your RS232 Cabling

Symptom: from Push app you can control C-Bus lighting but no feedback update (ie. when you physically press a C-Bus switch, the Push app doesn’t update) or vice versa
Check the RS232 cabling, a one-way communication could indicate that there is issue with either the RX or TX side of the cabling.

III. Local Network & Lighting Application Only

Symptom: unable to control or receive feedback, except for C-Bus groups on local network and lighting application
The C-Bus module only support a single network, which is the local network. In regard to feedback, only feedback for C-Bus group with application address of 56 (lighting) will be displayed.

IV. Check Feedback State Id

Symptom: no feedback on sliders however toggle buttons receives feedback (showing latest state); or vice versa
The Feedback State Id is different between a slider and a toggle button. The reason is because a slider displays a value between 0 – 255 but toggle button displays either 0 or 1 (on or off).

Slider

Format: PUSH_CBus_LevelApplicationAddress_GroupAddress. See sample below for a slider which is programmed for C-Bus group 0/56/32.
cid:image002.png@01D47B52.DE2E7BB0

Toggle Button

The Feedback State Id for a toggle button is available as a selection from the combobox. See below for a toggle button which is programmed for C-Bus group 0/56/32.

 

V. No Feedback on non-native C-Bus groups

Symptom: no feedback on C-Bus groups which control non-native C-Bus devices. For example: DALI.
This is due to the behaviour of MMI’s within C-Bus, a non-native C-Bus devices (such as DALI gateway) is not considered an output unit, therefore does not partake in in the MMI process when a switch supporting the application initiates it. Because of this, this means that the feedback of a DALI group address has to be monitored by an output unit which has the particular group addresses programmed into it from that application.
If there are any relays or dimmers on the same application as the DALI gateway, then it is best to load the channels and logic channels with these group addresses, the problem resolves itself at this stage as the group address is programmed into an output unit which partakes in the MMI process.
It is also important that there is a switch on the network which is set up for this application, as with this, no MMI process will begin.
Cheapest option is to use the ELV relay, which will allow us to store 8 group addresses on the channels, plus an additional 4 group addresses into the logic channels.

VI. Remove legacy C-Bus script from your GUI project

Symptom: no feedback on the Push app (ie. when you physically press a C-Bus switch, the Push app doesn’t update)
Legacy C-Bus module (version 3.1 or older) uses a separate script which is located in your GUI project, make sure you delete this when using C-Bus module version 3.2 or above.
 

Which USB-RS232 adaptor do I need for C-Bus?

Issue:
User is trying to connect PC Computer to Clipsal C-Bus system through RS232 PC Interface PCI device.  The user cannot establish a connection or open the network.

Product Line:
Clipsal C-bus 5500PC Serial Interface

Environment:
C-Bus Toolkit

Cause:
Most PC's today do not have built in RS-232 ports.  The PC must use a USB to RS-232 adaptor device or cable.    It has been our experience that some of these USB to RS232 adaptors work better than others.  The reasons for these differences is typically driver related.  

Also, it has been our experience that although a USB to serial adaptor may be known to work on one piece of equipment, it may not work on the C-Bus PCI.   For example, we have seen some adaptors successfully connect to a Powerlink G3 controller and then fail to connect to a C-Bus RS-232 PCI.   

Resolution:
It is suggested to try a USB-to-serial adaptor that is known to work with C-Bus these will need to contain the FTDI Chip set.
Cheaper brands on the market do not use this chip and will not work correctly with the Serial Library used by C-Bus Software.

Google Search: USB-RS232 FTDI

This will show results from suppliers such as Element14, RS Components etc, we've had success with these adaptors in the past.  


An alternative resolution would be to use a different device to access the C-Bus Network such as any of the following:  
USB PC Interface 5500PCU
Pascal Automation Controller 5500PACA
Ethernet Network Interface 5500CN2
Mark II Black and White Touch Screens

Where do I find the C-Bus Protocol document?

I can't connect to the NAC/SHAC via USB but I can from Ethernet RJ45 connection?

This is probably due to an old version of CBus Toolkit being installed on your computer.

CBus Toolkit older than 1.15 will not have the newer USB drivers required for the NAC/SHAC.

Your 5500PACA (PAC) or your 5500PCU (USB PC Interface) with their USB
connections will still be working, as they both use different "older" USB drivers.

Download the current Version Here: https://www.clipsal.com/learn-and-discover/trade-talk/trade-software-tools/c-bus-software
NAC SHAC Image with Details.jpg
 

What is the code for Cbus PC USB Interface?

The code is 5500PCU

Clipsal Cbus RS232 PC Interface (PCI) will not connect to PC (USA model)

Issue:
User is trying to connect PC Computer to Clipsal C-Bus system through RS232 PC Interface PCI device.  The user cannot establish a connection or open the network.

Product Line:
Clipsal C-bus (SLC series US model)

Environment:
C-Bus Toolkit

Cause:
Most PC's today do not have built in RS-232 ports.  The PC must use a USB to RS-232 adaptor device or cable.    It has been our experience that some of these USB to RS232 adaptors work better than others.  The reasons for these differences is typically driver related.  

Also, it has been our experience that although a USB to serial adaptor may be known to work on one piece of equipment, it may not work on the C-Bus PCI.   For example, we have seen some adaptors successfully connect to a Powerlink G3 controller and then fail to connect to a C-Bus RS-232 PCI.   

Resolution:
It is suggested to try a USB-to-serial adaptor that is known to work with C-Bus.  Below is a list of adaptors that we had successful experiences with C-Bus RS-232 PCI device.  

Date of Functional Verification:  16May2014
Manufacturer:  Gigaware
Product Name:  6ft USB-A to Serial Cable
Product Model Number:  2603487
Purchase Date:  15May2014 from RadioShack, $25
Computer used with:   HP Laptop running Windows 7 64-bit


An alternative resolution would be to use a different device to access the C-Bus Network such as any of the following:  
USB PC Interface SLC5500PCU
Pascal Automation Controller SLC5500PACA
Ethernet Network Interface SLC5500CN2
Mark II Black and White Touch Screens