C-Bus™ Networking C-Bus™ Products Training Course Training Guide 1250SM0905R10/09 Retain for future use.
C-Bus™ Networking C-Bus Products Training Course 1250SM0905R10/09 10/2009 HAZARD CATEGORIES AND SPECIAL SYMBOLS Read these instructions carefully and look at the equipment to become familiar with the device before trying to install, operate, service, or maintain it. The following special messages may appear throughout this bulletin or on the equipment to warn of potential hazards or to call attention to information that clarifies or simplifies a procedure.
1250SM0905R10/09 10/2009 C-Bus™ Networking C-Bus Products Training Course PLEASE NOTE Electrical equipment should be installed, operated, serviced, and maintained only by qualified personnel. This document is not intended as an instruction manual for untrained persons. No responsibility is assumed by Square D for any consequences arising out of the use of this manual.
C-Bus™ Networking C-Bus Products Training Course 1250SM0905R10/09 10/2009 SAFETY PRECAUTIONS Carefully read and follow the safety precautions below before attempting to install or maintain electrical equipment. HAZARD OF ELECTRIC SHOCK, EXPLOSION, OR ARC FLASH Apply appropriate personal protective equipment (PPE) and follow safe electrical work practices. See NFPA 70E. This equipment must be installed and serviced by qualified electrical personnel.
© Copyri ght Cli psal Inte grated S ystems Pty Ltd 2 006. All ri ghts Reserve d. Thi s materi al i s copyri ght under Au stralian a nd in ternational la ws. Exc ept a s p ermitted un der t he re levant la w, n o p art o f t his work may be reproduced by any process wi thout prior written permission of and acknowledgement t o Clipsal Integrated Systems Pty Ltd. Clipsal and C-Bus are registered trademarks of Clipsal Australia Pty Ltd. The information in this manual is provided in good faith.
Contents Scope Learning Outcomes 1.0 2.0 3.0 C-Bus Network Interface 1.1 Wiring 1.2 LED Indicators 1.3 Ethernet Basics 1.4 Ethernet Card Setup 1.5 CNI Configuration 1.6 Bandwidth Usage 1.7 Command Routing 1.8 Network Extending 1.9 C-Bus Network Interface Location Network Bridge 2.1 Network Bridge Applications 2.2 Configuration 2.3 Network Bridge Topology 2.4 Programming 2.5 Command Routing 2.6 Group Addressing 2.7 Traffic Considerations 2.8 Network Bridge Location C-Bus Network Topologies 3.
C-Bus By Demand 3 Scope This manual aims to provide the trainee with the basic skills needed to design and commission a commercial C‐Bus installation. A fundamental technical background is required.
C-Bus By Demand 3 1.0 C-Bus Network Interface This chapter will explain the programming and operation of a C‐Bus Network Interface (CNI), focusing on: • Wiring • LED Indicators • Ethernet Basics • Ethernet Card Setup • CNI Programming • Bandwidth Usage • Command Routing • Network Extending • C‐Bus Network Interface Location. It must be stressed that CIS does not support diagnostics and analysis of Ethernet networks.
C-Bus By Demand 3 1.1 Wiring There are three fundamental wiring connections shown in Figure 1, which must be made to ensure the correct operation of the C‐Bus Network Interface: 1) C‐Bus Connection 2) 12 Volt Plug Adaptor 3) Ethernet Connection. Figure 1: Three wiring connections to a CNI. 1.1.1 C‐Bus Connection The C‐Bus power connection is used so the C‐Bus Network Interface can transmit and receive C‐Bus messages onto the network.
C-Bus By Demand 3 1.2 LED Indicators There are two LED Indicators on the CNI: 1) the Ethernet LED. 2) the C‐Bus LED. These indicators identify what the state of the Ethernet or C‐Bus is, by using various colours and flashing sequences. 1.2.1 Ethernet LED The Ethernet LED has multiple states indicating different conditions for the Ethernet part of the network, they are: Ethernet LED Condition Meaning Red Bad Ethernet Link. Red Flash (5 times) No DHCP Server found and a bad Ethernet Link.
C-Bus By Demand 3 1.3 Ethernet Basics There are two parameters that need to set to program a C‐Bus Network Interface (CNI), and they are: • IP Address • Subnet Mask 1.3.1 IP Address An IP Address is the logical address of a network adapter. The IP Address uniquely identifies computers, printers and other Ethernet Devices on a network. Internet Protocol supports the idea of individual addressing for Ethernet Devices on a network.
C-Bus By Demand 3 1.4 Ether net Card Setup Before configuring the Ethernet card on a PC, contact your network administrator to identify what address the CNI needs to be set to. This will determine what addresses will be assigned to the Ethernet card in the PC. This example assumes that the IP Address you want to assign to the CNI is 10.120.120.121 with a Subnet Mask of 255.255.0.0.
C-Bus By Demand 3 1.5 CNI Configuration ARP stands for Address Resolution Protocol. ARP functions are used to determine the hardware address of Ethernet devices on a network. ARP functions may be used to program the C‐Bus Network Interface. To begin to program a CNI using ARP functions, follow the steps listed below: 1) Ensure both the CNI LED indicators are orange. This indicates that the CNI is correctly wired.
C-Bus By Demand 3 9) Press enter again within 5 seconds to continue, otherwise connection to the telnet session will be lost. If a successful connection has been made, you will see a screen similar to the one below. Figure 3: Successful connection to a telnet session. 10) You will see a menu. Type in 0 (Server Configuration) and press enter. 11) You will be prompted to enter in the IP Address parameter.
C-Bus By Demand 3 So for this example you will type in 16 (for Subnet Mask 255.255.0.0) and press enter. 13) Keep pressing enter until you get to the main menu. 14) Once at the main menu, select 1 (Channel 1 Configuration) and press enter. 15) Keep pressing enter until you reach the Port Number parameter. 16) Type in the Port Number 10001 and press enter. 17) Keep pressing enter until you return to the main menu. 18) Press 9 to save and exit. 19) Whilst in the command prompt, type in ping 10.120.120.
C-Bus By Demand 3 1.7 Command Routing When using an Ethernet backbone in a multiple network C‐Bus installation, it is important to understand that CNI’s do not support tunnelling. Tunnelling is when a command is sent from one CNI to another, through the Ethernet network. This means that if an installation used 5 CNI’s (one on each floor), there would be no direct way to route messages between networks.
C-Bus By Demand 3 2.0 Network Bridge This chapter will cover the use of a Network Bridge (5500NB) in commercial installations, focusing on: • Network Bridge Applications • Programming • Network Bridge Topology • Command Routing • Traffic Considerations • Network Bridge Locations The Network Bridge is primarily used in C‐Bus commercial installations to provide connectivity between different C‐Bus Networks. 2.
C-Bus By Demand 3 2.1.2 C‐Bus Network Extender There may be instances in a commercial C‐Bus installation, where one of the fundamental C‐Bus operating parameters is exceeded. These parameters may be: • more than 100 C‐Bus units • more than 2 Amps of C‐Bus Current • more than 1 km of C‐Bus CAT 5 cable • more then 255 Group Addresses. It is when one of these parameters is exceeded, that you will still need to extend the network.
C-Bus By Demand 3 2.2 Configuration To configure the Network Bridge, the C‐Bus Toolkit must be used to create new networks and edit unit addresses. When configuring the Network Bridge you must ensure that: • The Unit Address on the Near Side of the bridge, is the Network Address on the Far Side of the Bridge. • The Unit Address on the Far Side of the bridge, is the Network Address on the Near Side of the Bridge. Figure 5: Network Bridge Addressing.
C-Bus By Demand 3 2.2.1 Connect Applications The Connect Applications parameters can be found on the Connection tab of the Network Bridge Graphical User Interface (GUI). The Application 1 and Application 2 parameters filter the commands that are routed through the Network Bridge. By default all applications are set to pass through the Network Bridge. If you wish to filter messages by application, then you will be limited to a maximum of 2 applications.
C-Bus By Demand 3 2.3 Network Bridge Topology The network bridge topology, describes the way that network bridges are connected. There are three types of network topologies that may be used with network bridges. These topologies are: • Daisy Chain Topology • Backbone Topology • Fully Connected Topology. A combination of these three topologies may also be used. 2.3.
C-Bus By Demand 3 2.3.2 Backbone Topology A backbone topology refers to when all C‐Bus networks are connected to a single central C‐Bus network. Figure 13 shows how network 253, network 252, network 251 and network 250, are all connected to a centralised network 254. In this example network 254 is referred to as the backbone network, as all other networks connect to it.
C-Bus By Demand 3 2.3.3 Fully Connected Topology A fully connected network topology is the most rarely used of all network topologies. The concept of a fully connected network is that each C‐Bus network will have a network bridge that is connected to every other C‐Bus network (see Figure 14). With this particular configuration it may also be feasible to remove one of the bridges, and utilise the dual routing capability of the network bridges. Figure 10: A fully connected network topology.
C-Bus By Demand 3 2.4 Program ming The following sections will focus on: • Creating a Network Online • Editing Existing Networks Online 2.4.1 Creating A Network Online The most simple way to program a network bridge is to use the ‘Make Networks’ button while you are connected to the network using Toolkit. Follow the steps below to program the network bridge. 1) Scan the C‐Bus Local Network. You will see that a new Network Bridge will show up at Unit Address 255 (like all other new C‐Bus units).
C-Bus By Demand 3 5) Click on the ‘Make Network’ button as show. Figure 13: Click the Make Network button. 6) Once you have clicked the Make Network button, you will then be prompted to confirm your actions. Figure 14: Confirmation of creating a new network.
C-Bus By Demand 3 7) Toolkit will that automatically create a new network and scan in the remote network. You will then see that Toolkit has also updated the Project Manager to show the new network in your selected project. Figure 15: Project Manager showing the Local and Remote networks. 8) Change the Unit Address on the Remote side of the Network Bridge to the Network Address of the Local Network (254 by default). Figure 16: Change Unit Address of the Remote side of the Network Bridge.
C-Bus By Demand 3 2.4.2 Editing Existing Networks Online To identify the true setting of how a Network Bridge is programmed it is best to look at its true addressing. This can be done by simply selecting the project in the Project Manager. Figure 17: True Network Addressing. You will see the highlighted section that states 254/p/253. This means that network 253 (the selected network) is physically linked through network 254.
C-Bus By Demand 3 3) Once you have clicked the Readdress button you will then be prompted to select a new Network Address for the selected network. Figure 19: Selecting a new Network Address. 4) Once you have clicked ok, you will then be prompted to readdress the corresponding Unit Address to match the new Network Address. Click Yes. Figure 20: Automatic Readdressing of Unit Addresses.
C-Bus By Demand 3 2.4.3 Creating Networks Offline To create a network offline, which contains multiple bridges, please follow the steps below. 1) Create a new C‐Bus project and add a network (using a Serial PCI at COM1 if possible). 2) Once you have done this, select the project in the Project Manager and click on the Add Networks button on the toolbar. Figure 22: The Add Network button. 3) Specify the Network Name. 4) Specify the Network Type (in this case Bridge – Wired).
C-Bus By Demand 3 8) Enter any Serial Numbers if applicable otherwise press the OK button. Figure 24: Adding Serial Numbers. Your network has now been created with a bridge. The databases of both networks now will have a network bridges in the databases and the unit addresses will be configured in accordance with default network addressing. If you click on the Topology branch of your project (in the Project Manager), you will see the a visual display of the network topology.
C-Bus By Demand 3 2.5 Command Routing Command routing is a very important consideration to contemplate when designing a multiple network C‐Bus installation. Every single C‐Bus command has information in it, that specifies which network to communicate with. When routing C‐Bus commands, it is important to understand two things: 1) If a C‐Bus command is generated specifically for a dedicated network, then the dedicated network is the only C‐Bus network that will see and react to the command sent. Eg.
C-Bus By Demand 3 2.5.2 Other Routing Enabled Devices C‐Bus has a range of products and software packages that are capable of routing commands directly to other C‐Bus networks. The routing enabled devices are products such as: • Schedule Plus & HomeGate • Touch Screens (Monochrome and Colour) • Pascal Automation Controller (PAC). When programming with any of these other routing enabled devices, the commissioning software allows the specification of what network to send the command directly to.
C-Bus By Demand 3 2.6 Group Addressing When creating new networks, it is very important to manage the group addresses that are being used on all other networks. This will ensure that you do not use two identical group addresses to control different outputs. An example of this is that you may have a relay on the local network, and a dimmer on the remote network. Both of these units are using the Lighting Application (56 or 38h), and Group Address 01.
C-Bus By Demand 3 2) On the toolbar, select the Copy Tags button. Figure 29: The Copy Tags button. 3) You will then be prompted with a dialogue box that asks you which network would you like to copy the tags from. Select the relevant network and press ok. Figure 30: Selecting a network to copy tags from. 4) Now all of your tags will show up on the new network.
C-Bus By Demand 3 2.7 Traffic Considerations When designing a multiple network project using network bridges, it is extremely important to consider the amount of C‐Bus traffic being sent around the networks. 2.7.1 Daisy Chain Considerations When using a daisy chain configuration, network traffic is not usually much of a problem. This is due to the network bridged only being able to send commands to two networks. What must be considered it the speed of the networks.
C-Bus By Demand 3 3.0 C-Bus Network Topologies This chapter will explain some of the more commonly used C‐Bus Network Topologies, focusing on: • Typical C‐Bus Backbone Topologies • Typical Ethernet Backbone Topologies • Typical Vertical Network Topologies • Typical Horizontal Network Topologies A C‐Bus Network Topology is a way of explaining the physical layout of multiple C‐Bus Networks.
C-Bus By Demand 3 3.1 Typical C-Bus Backbone Topology A C‐Bus backbone topology is a commonly used network topology in C‐Bus projects. Utilising the C‐Bus Network Bridge (5500NB), the connectivity between C‐Bus networks is provided by a dedicated C‐Bus network operating as backbone. Using network bridges will allow this topology to transmit locally generated C‐Bus commands between adjacent and remote C‐Bus networks.
C-Bus By Demand 3 3.2 Typical Ethernet Backbone Topology An Ethernet backbone is another of the more commonly used C‐Bus network topologies. Utilising C‐Bus Ethernet Interfaces (5500CN), the connectivity between C‐Bus networks is provided by an Ethernet Switch or Hub. Figure 32: Ethernet Backbone Topology The C‐Bus Network Interfaces do not support network tunnelling. This means that you cannot communicate directly between networks.
C-Bus By Demand 3 3.3 Typical Vertical Network Topology The fundamental principle of a Vertical C‐Bus Network Topology, is that the C‐Bus network will run vertically. So on a commercial installation with multiple levels, a single C‐Bus network will control a certain area of each level. Each network may be programmed using multiple Applications within the lighting range, to identify each level. This configuration is commonly used in the design of stadiums and arenas.
C-Bus By Demand 3 3.4 Typical Horizontal Network Topology The fundamental principle of a Horizontal Network Topology is when you want to connect C‐Bus between buildings. C‐Bus cable may be used to connect buildings together, however you must ensure that the cables connecting the buildings are: • Suitable for being run underground • Enclosed in suitable conduit. Please refer to your local wiring rules for further information. Fibre Optics can also be used to connect C‐Bus networks in different buildings.
C-Bus By Demand 3 3.5 Network Topology Comparisons The following sections will identify the: • Advantages Of A C‐Bus Backbone • Disadvantages Of A C‐Bus Backbone • Advantages Of A Ethernet Backbone • Disadvantages Of A Ethernet Backbone 3.5.1 Advantages Of A C‐Bus Backbone Some of the advantages of using a C‐Bus Backbone are: • The C‐Bus Backbone allows communications between networks, via Network Bridges.
C-Bus By Demand 3 3.5.3 Advantages Of A Ethernet Backbone Some of the advantages of using a C‐Bus Backbone are: • An Ethernet Backbone can utilise existing Ethernet Backbone infrastructure. • An Ethernet Backbone has a faster synchronisation time when scanning C‐Bus networks (via Toolkit, Schedule Plus or HomeGate). • An Ethernet Backbone allows HomeGate or Schedule Plus to control and monitor all networks.
C-Bus™ Networking Training Guide SUPPORT AND TRAINING Contact the Customer Information Center for technical support by phone at 1-888-778-2733 or e-mail at lightingcontrol.support@us.schneider-electric.com. You may also find helpful information on our web site at www.Schneider-Electric.us. Schneider Electric, USA 320 Tech Park Drive, Suite 100 La Vergne, TN, 37086 1-888-778-2733 www.schneider-electric.
