C-Bus OPC installation C-Bus programming guide
C-Bus OPC installation User Guide Conventions in this guide Before you start using this guide, it is important to understand the terms and typographical conventions used in the documentation. For more information on specialised terms used in the documentation, consult the Glossary. The following kinds of formatting in the text identify special information. Formatting convention Type of Information MENU OPTIONS Items you must select, such as menu options, command buttons, or items in a list.
Contents 1.0 Overview 1.1 1.2 1.3 1.4 1.5 1.6 1.7 1.8 1.9 2.0 Why have a C-Bus OPC Server? ......................................................................................................................3 For more information.........................................................................................................................................4 Software layers ..........................................................................................................................
1.0 Overview The C-Bus OPC Server is a stand-alone software package made available by Clipsal to allow OPC communication between C-Bus networks and building management systems. The OPC Server acts as a gateway for transmitting Lighting Compatible and Error Reporting application information to entities such as building management systems, which are capable of handling OPC messages.
C-Bus OPC installation User Guide How C-Bus messaging translates to OPC Server objects The C-Bus OPC Server utilises the OPC Data Access and OPC Alarms and Events interfaces, which define how OPC clients and servers can transmit data to each other. The specification is based around a component object model and takes advantage of Microsoft DCOM (distributed component object model) technology.
Overview 1.1 Why have a C-Bus OPC Server? An obvious reason for installing and operating a C-Bus OPC Server is because you want to incorporate lighting application data from C-Bus networks as part of a building management solution. The C-Bus OPC Server makes it possible to transmit Lighting Type application messaging between a C-Bus network and a OPC Client.
C-Bus OPC installation User Guide 1.2 For more information OPC Foundation website The OPC Foundation http://www.opcfoundation.org/ is tasked to provide information and support for the development of OPC solutions. Their website contains links to high level documentation about OPC technology. OPC Programmers Connection website The OPC Programmers Connection http://www.opcconnect.com/ website provides support for programmers who are developing OPC solutions.
Overview C-Bus OPC Commissioning Application The C-Bus OPC Commissioning Application is the programming interface for C-Bus OPC Server. It establishes OPC Data Access and OPC Alarms and Events interfaces for linking project network Lighting Compatible and Error Reporting groups and their levels to OPC groups and items. C-Bus OPC Monitoring Application The C-Bus OPC Monitoring Application monitors the health of the C-Bus OPC Server.
C-Bus OPC installation User Guide 1.4 Host computer system requirements The C-Bus OPC Server has the following host computer system requirements: Memory 1024 MB Error correction (ECC) RAM or greater CPU Pentium 4 processor, 2.4 GHz or better with 512k on-chip cache. A Core 2 Duo processor E6300 or better is recommended.
Overview 1.5 C-Bus OPC Server system configurations The C-Bus OPC Server can either be installed on its own computer host or in combination with the C-Gate server (local). In the combined (local) system configuration, the C-Bus OPC Server and CGate communicate via TCP/IP locally. Communication between the OPC Client and the C-Bus OPC Server is through the OPC network (TCP/IP).
C-Bus OPC installation User Guide 1.7 Licensing Licensing of the C-Bus OPC Server is divided into three categories: demonstration, Clipsal C-Bus OPC Server, and CITECT licenses. Demonstration licensing If no physical licensing dongle is connected to the USB port of the host computer, then the C-Bus OPC Server operates in Demo mode. This means that the C-Bus OPC Server will only run for approximately one hour and cannot operate in Production mode.
Overview Licensing for the C-Bus OPC Server, when activated by a CITECT License, is based on the number of configured OPC Items. This is referred to as the point count, and matches the point count of the CITECT license you are using. Example: If you have CITECT SCADA with a 500 point count license installed you can use the C-Bus OPC Server with up to 500 configured Lighting groups and/or channels of units with at least one alarm or event configured across any number of C-Bus networks.
C-Bus OPC installation User Guide 1.8 The OPC Data Access interface The OPC Data Access interface supports both Lighting Compatible and Lighting Type applications, which are used to carry lighting control messages.
Overview The DALI application has been specified for use with the DALI mostly for the benefit of keeping DALI control separate from other lighting control operations. How OPC Data Access handles Lighting Type data The Lighting Type group transmits integer values within the range of 0255 values. The OPC Data Access handles discrete and ramping operations differently.
C-Bus OPC installation User Guide 1.8.1 How the OPC Data Access interface works A simple example of a C-Bus OPC Server implementation is to send lighting information to and receive lighting control messages from the OPC Client. Within the C-Bus, there is one network which contains a Lighting application which controls four dimmer output units, each being named FLR1_DIM1, FLR1_DIM2, FLR1_DIM3, and FLR1_DIM4. In the graphic below, the C-Bus network consists of a dimmer and a 4 key input unit.
Overview Messaging sequence The messaging sequences listed below are part of the process for translating C-Bus messaging to OPC messaging. Sequence 1: A building occupant turns Key 1 on which is linked to DIM1 lighting group. Sequence 2: A C-Bus FLR1_DIM1 Group ON message is sent across the C-Bus network. C-Gate is one of the recipients of the ON message and stores the DIM1 element to 255. At the physical network level, this turns the dimmer on to full power.
C-Bus OPC installation User Guide 14 © Schneider Electric 2011 Sequence 2: The C-Bus OPC Server receives the OPC message, translates this to C-Bus 0 lighting level. Sequence 3: C-Gate server passes the 0 lighting level value to DIM1 lighting group. Sequence 4. The OFF message is stored in the dimmer unit where it turns the lighting connected to it OFF.
Overview 1.9 OPC Alarms and Events interface The OPC Alarms and Events interface provides information about the status of output unit channels and DALI ballasts. A C-Bus network may contain Error Reporting compatible units, all of which are reporting the status of channels or DALI ballasts across the C-Bus. Error Reporting applications supported The Error Reporting application is used to report error information detected or generated by certain C-Bus units over the C-Bus network.
C-Bus OPC installation User Guide The graphic below shows a C-Bus system containing output units such as the C-Bus Universal dimmer, the DALI gateway, and the 6 channel architectural dimmer. All of these output units can generate Error Reporting messages. The C-Bus OPC Server translates these messages into OPC alarm or error events. This information is then transmitted across the OPC network.
Overview 1.9.1 Transmitting Error Reporting into OPC Alarms and Events error data The conversion of Error Reporting messages to OPC Alarms and Events error conditions involves the C-Bus network, C-Gate, OPC Server, and the OPC Client as shown in the graphic below. The C-Bus OPC Server passes Error Reporting messages retrieved from the C-Bus network to the C-Bus OPC Server.
C-Bus OPC installation User Guide OPC mapping to either the Architectural dimmer or Professional dimmer units OPC error condition Professional dimmer or Architectural dimmer error conditions Ballast controller failure The Ballast Card Error message indicates that the ballast card fitted on this channel has an error. Channel not powered The No Power message indicates that there is no power in the channel. For example, the breaker has tripped or that phase has gone down.
Overview Control communication failure The Communication Error error condition indicates that an internal communications error has occurred in the dimmer. No hardware The No Hardware error condition indicates that there is no card for this channel. Over current The Over current error condition indicates that the channel is over current. This can be caused by: Over temperature Status communication error a short circuit on the channel tripping the in-built over current protection.
C-Bus OPC installation User Guide Event and alarm conditions The OPC Server receives Error Reporting messages from C-Bus, then processes them as OPC events that may change alarm condition states. The OPC Server also processes OPC acknowledgment messages from the OPC Client. The OPC events and alarm conditions are defined below: Events An event condition represents a change of state for an error condition of an output unit channel.
Overview Figure 11: State diagram showing processing of alarm conditions Inactive, Acknowledged [Send "Condition Active' notification] [Send "Condition Inactive" notification] [Send "Active Acknowledged" notification] [Send "Acknowledged" notification] Active, Unacknowledged Active, Acknowledged [Send "Acknowledged" notification] [Send "Condition Inactive" notification] [Send "Condition Active" notification] Inactive, Unacknowledged Quality changed © Schneider Electric 2011 21
C-Bus OPC installation User Guide Typical error condition names and their active and inactive states The table below lists the inactive and active state messages for each of the error conditions.
Overview 1.9.2 Quality of OPC Alarms and Events data and logged data The C-Bus OPC Server provides information on the quality of the information coming from the OPC Alarms and Events as well as logging data to track the behaviour of the interface over time. Quality of OPC Alarms and Events data The OPC Alarms and Events interface evaluates the quality of information coming from C-Gate and provides a quality rating.
C-Bus OPC installation User Guide The sequence illustrates the messaging sequences that occur to convert a error condition into an OPC error condition event. The 12 channel architectural dimmer must be programmed before it is possible to send error conditions and accept acknowledgements. Sequence 1: Each channel of the 12 channel architectural dimmer generates an error condition report at regular intervals or as error conditions change. The reports are sent as Error Reporting messages over C-Bus.
Overview where FLOOR2 refers to the specific C-Bus network, DIMMER refers to the unit tag name, CHANNEL1 refers to the first of twelve (12) channels, and OVER_TEMP_ACKED refers to the alarm condition acknowledgement state (assuming that this alarm condition has been configured to require acknowledgement). Sequence 2: C-Bus OPC Server sends a message to C-Gate to acknowledge the alarm condition for this channel.
2.0 Installation The installation of the C-Bus OPC Server includes the software components described in the software layers in the Overview chapter. It also installs software related to the dongle driver and SmartInspect log viewer. Before you start Review the Overview chapter especially the section discussing licensing You will need access to the Internet to download the C-Bus OPC Server software.
C-Bus OPC installation User Guide 2.1.1 Installed software The installed components reside in the C:\Clipsal\CbusOPCServer directory. Installed software components The main components are listed below: C-Bus OPC Server software components C-Bus OPC Commissioning Application C-Bus OPC Monitoring Application OPC core components SmartInspect components . The SmartInspect components including the SmartInspect Console application and and Help file.
Installation 2.3 Downloading and installing C-Bus Toolkit You can obtain the most recent copy of C-Bus Toolkit at the Clipsal software download http://www2.clipsal.com/cis/technical/downloads page. 1 Download the installation package to a temporary directory. 2 Double click the installation package to run the installation wizard.
3.
