Building Automation Knowledge Base

Issue Changes to the Set Space Temperature do not work. Environment DC1100 DC1400 Controller Compensator Optimiser Setpoint Cause The pump overrun is timing down and will not allow the controller to act normally until it is complete. Resolution If the "Set Space Temperature" value is modified, then after the rotary switch is returned to "Auto", the user must wait until the Pump Overrun function has timed out. Where adjustments are generally being made, it is recommended that the Pump Overrun setting is set to 1 minute until  testing has been completed, after which it should be return to its required setting. To change the Pump Overrun setting carry out the following: Turn the rotary switch to "Setup". Select "System Menus" then "Alter Settings", and then enter the password of 0112. Select "Compensator", then "Set-up Menu", and then "Pump Overrun". Note the current value then change it to 1. On completion of the tests return the setting to its correct value. For the DC1100 data sheet, click here. For the DC1400 data sheet, click here.

Issue Proper handling and preparation of existing .vsd files help eliminate the crashing and lockup of the Visio application. Product Line EcoStruxure Building Operation, TAC IA Series Environment Workplace Tech Editor EcoStruxure 1.9.x - 3.2.3 Workplace Tech 5.9.1 - 5.9.4 Visio 2013, Visio 2016 Note: This does not apply to Workplace Tech Editor EBO 2022 (and newer) and Workplace Tech 5.10.x Cause The product is affected by the version of Visio in use as well as the file size and unused objects in the drawing. Resolution When using Workplace Tech 5.9.x with Visio 2013 or 2016, the file has to be opened in "Compatibility Mode." DO NOT CONVERT. Illustration 1 While the .vsd file is open in Visio, not in Workplace Tech, use the "Reduce File Size" option and select the boxes in Illustrations 1&2. Illustration 2 In Visio 2016, after opening the "Inspect Diagram," (Illustration 3), select the first 3 boxes in the "Reduce File Size" option (Illustration 4). Illustration 3 Illustration 4 Save the file for use in the Workplace Tech Project or to be imported into your AS-P as a .vsd. Add the "cleaned" file to your project or import it to Workplace Tech Editor. Make sure the Visio 2013 or 2016 is at the most recent version and build. You can find this under the file/account/About Visio. If Version 1802 is available in your Microsoft Office update Channel, use it. Version 1801 was used in testing. For Visio 2013 Build 15.0.4971.1000 MSO 15.0.5007.1000 was tested (Illustration 5) Illustration 5

Issue Since Generation 1 controllers do not have a controller webpage, how can I access the controller configuration to set up the controller or access controller information. Product Line Andover Continuum Environment Hyper Terminal CX9900 CX9940 CX9400 CX9410 CX9200 Cause 1st Generation Controllers do not have an embedded webpage. Resolution Find information about the pin configuration of the direct connection cable in PinOuts for the RS-232 Connection of the older 1st Generation CX controllers. The following document describes how to log into a generation 1 controller via a PC with a terminal emulation application: CX Operators Guide.pdf

Issue What is the contact information for Barber Colman Dyna group? What is the contact information for Barber Colman Aerospace division? What is the contact information for Barber Colman Industrial Instruments division? Environment Barber Colman Cause The old Barber Colman Dyna group is now a part of Woodward Governor. The old Barber Colman Aerospace division is now a part of the GE Aerospace. The old Barber Colman Industrial Instruments is now part of Eurotherm, an Invensys company. Resolution Barber Colman Dyna group is now Woodward Governor. They can be reached at 800-543-5811 Barber Colman Aerospace division is now GE Aerospace. They can be reached at 815-637-3500 Barber Colman Industrial Instruments is Eurotherm, an Invensys company. They can be reached at 815-637-3222 or 815-637-3404 for tech support.

Issue How to collect log files from the Project Configuration tool. Product Line EcoStruxure Building Operation Environment Project Configuration Tool Cause When contacting Product Support about issues with the Project Configuration tool, log files should be provided. Resolution Go to the PCT installation folder and run the program called LogCollector.exe located there. The default installation folder for versions 1.2 and higher is: "C:\Program Files (x86)\Schneider Electric EcoStruxure\Building Operation\Project Configuration Tool" and "C:\Program Files (x86)\Schneider Electric StruxureWare\Building Operation\Project Configuration Tool" for previous versions. Click Collect logs A program log of what LogCollector has done is displayed. A zip-file containing the collected PCT logs is created on the desktop.

Issue What is the proper way to replace AS hardware for an existing node. Cannot get the AS to come online in the Enterprise Server after replacing the AS hardware for an existing node. Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Automation Server - Classic (AS) Building Operation Automation Server - Premium (AS-P) Building Operation Automation Server - Bundled (AS-B) Cause To replace the AS hardware, a backup must have been made from the original AS while it was online.  Simply changing the controller name, IP information, and domain  information in the AS will not be sufficient for bringing the controller online in the ES. Before the new automation server can be brought online, the backup from the original controller must be restored to the new AS directly. Resolution This procedure assumes that a backup of the original AS is available. From Device Administrator and the USB interface, run the SetIP command to configure the following information in the new AS to match the original AS configuration. Note: You will have to use the version of Device Administrator that matches the replacement AS firmware. If necessary, use the appropriate version of Device Administrator to Upgrade or downgrade the firmware in the new AS so that it matches the Enterprise Server and/or the original AS hardware firmware. Install the AS then backplane. From StruxureWare workstation, log into the AS using the hardware's IP address for the Server field. Right click on the server name and select Restore. If the backup does not appear in the Available restore points window, click on Import Backup Set and browse to the backup file. Select Configuration only or All data in the window on the left. Select restore. Once the restore has completed the AS displays a solid green status light, log off the AS and log into the ES. The controller should now appear online in the ES.

Issue Steps on how to setup BACnet Time Synchronization to 3rd Party BACnet controllers. Product Line EcoStruxure Building Opertaion Environment SmartX Enterprise Server (ES) SmartX Automation Server (AS) BACnet Cause It is not always clear what is required to setup BACnet Time Synchronization and how to confirm that EcoStruxure Building Operation is actually performing it properly. Resolution To use the Time Synchronisation you will need to bring the 3rd Party BACnet device (Eg. Continuum bCX) under the EBO BACnet Interface -> IP Network: Go to the BACnet Interface Time Synchronization Recipients Tab. Add a new Local time synchronization recipient with the '+' button. Select recipient type as 'reference' In the Recipient device object reference field browse for your BACnet Device. Press OK and then save the changes. Right-click on the BACnet Interface and select send time sync now. This will send out an unconfirmed-req TimeSynchronization to that specific Device only.   Test Scenario with a bCX setup as a third-party BACnet controller You will see a unconfirmed-req TimeSynchronization packet being sent from the ES in WireShark but with no response from the bCX.  You may not see responses back from other 3rd party devices. The time in the bCX should be seen to change from within Continuum, (assuming it was incorrect in the first place) 

Issue Cannot find manual service pin location Environment Schneider Electric SE76xx, SE73xx and SE72xx Viconics VT76xx, VT73xx, VT72xx Ready7 Commissioning Neuron ID Lonworks ID Service Pin message Cause The Service PIN is used to identify the device at commissioning. There is not a visible service pin button located on the Viconics device. Resolution A Service Pin will transmit the program ID and the Neuron ID (LonWorks Unique ID) contained in the device to the commissioning or service tool. The Status LED will blink when the device accepts the Service PIN command. VT7600 device - Press simultaneously the “Yes” button and the “No” button located on the keypad interface VT7300 and 7200 device - Pressing simultaneously the “Up” button and the “Down” button located on the keypad interface.       Additional Information on Viconics VT7600 series can me found in this Viconics Lon Integration Manual. Additional Information on Viconics VT7300 and VT7200 series can me found in this Viconics Lon Integration Manual.

Issue Xenta Programmable Device is Offline in Vista, but Online in LonMaker. For LonWorks Devices refer to LonWorks Device is Offline in Vista but Online in LonMaker or NL220. Product Line TAC Vista Environment LonMaker, NL220 Vista Workstation Xenta programmable controllers Xenta 280, 281, 282, 283, 300, 301, 302, 401, 401:B Cause In an LNS system, Xenta programmable controllers have different methods of communication to the LNS server and the Vista server.  Communication with the LNS server indicates the wiring is connected, the neuron ID is set correctly, but does not guarantee communication with the Vista server.  An online condition for Vista is dependent on Xenta Group bindings and network description files in the device and the Xenta Group Master being online. Resolution Ensure that Vista Workstation is in Operating Mode vs. Engineering Mode. Refresh the Folders View - Highlight the root directory "TAC Vista" press "F5" or click the refresh icon. Ensure the device is physically Online in LonMaker even though the drawing displays as green. Check the status by right clicking on the device, select Properties. Commission Status should say "Current", and State should say "Online". Alternatively, right click on the device and select Manage / Test.  The state should read "configured online" if the device is online in LonMaker. Make sure that your Master Device in the corresponding Xenta Group in the System Plug-in is online. If the Master Device is online and displaying values, it is always necessary to download the application and parameters to the Xenta group after adding a new device. The entire Xenta Group must know there is a new device for proper communication to occur.  Download the applications and parameters to the entire group in the TAC System Plug-In. If all the above is true and there is still no data then use Verifying Xenta Group Bindings in an LNS system to verify that the Xenta Group Bindings are correct. If not, in the Vista system plug-in, click on the LNS Network tab choose Create Group Bindings and click Yes on the Resynchronize drawing to database (Fix-up Drawing). Ensure the Xenta Group name is less than 20 characters without any spaces. Note: Channel names can contain spaces (NL220) but still must stay under the 20 character limit. 

Issue Some jobsites require the use of conduit for all wiring between controllers. Is there a specific enclosure made for this purpose?  A general purpose enclosure such as the ENCL-100 can be used but must be punched or drilled to fit the damper shaft. Product Line TAC IA Series Environment MN-FLO / MN-FLO3T MNL-V1RVx / MNL-V2RVx MNB-Vx Cause Installation manual with reference to part number was misplaced. Resolution MNA-FLO-1 This enclosure is listed as an optional item in the installation manuals for all VAV controllers listed above. Click here to see F-26282-5, Installation Instructions for the MNL-V1RVx and MNL-V2RVx. Click here to see F-27346-4, Installation Instructions for the MNB-V1 and MNB-V2 Click here to see F-25718-6, Installation Instructions for the MN-FLO and MN-FLO3T

Issue General configuration for these controllers. Environment Drayton DC1100 Satchwell DC1400 Cause Access to the documentation unavailable and uncertain of the correct configuration. Resolution The available controller configurations are all shown in the controller data sheets, please select the required data sheet below. To review the Drayton DC1100 general data sheet, please click HERE. To review the Drayton DC1100 "A" data sheet, please click HERE. To review the Satchwell DC1400 general data sheet, please click HERE. To review the Satchwell DC1400 "A" data sheet, please click HERE. For a general overview of the DC1100/DC1400, please click HERE.

Issue What actuators are available? Environment VG210R VG310R Actuators Cause Choice of available actuators. Resolution Suitable Actuators for the VG210R and VG310R ball valves ranges are; Direct fit. MG600C, MG600C SR   With AV-823 Long Stem adaptor. M400 M800 M1500 MG900 SR To view the following data sheets, please select the data sheet required. VG210R,  VG310R, MG600C,  MG600C Installation,  MG600C SR,  MG600C SR Installation and Manual Override instructions

Issue The majority of the Satchwell MicroNet and Satchnet product ranges is now re-branded to Schneider Electric. Product Line Satchwell MicroNet Environment IAC-420-F IAC-420-P IAC-440-F IAC-440-P MN350-LON MN450-LON MN550-LON MN650-LON MN50-TS-LON MN50-TSP-LON MNN-COM MN550-NCP MN550-XCOM MN650-NCP MN650-XCOM MNN_RTC M50_RTC MN-TK MN-VWIO-NCP MN-VWIO-SNP MN-VW100-UK MN-VW500-UK MN-VWP500-UK MN-VWP2K-UK MN-VWP10K-UK MN-VWP60K-UK Monitor Tool MicroNet View Cause The branding exercise provided some insightful information regarding sales volume. As a result, a number of products that were low or zero sales have been discontinued. Resolution Updated June 2019   The MicroNet 50 series range MN350, 450, 550, 650 LCD and Touchscreen have been withdrawn from sale. The IAC 420, 600 and Touchscreen have now also been withdrawn from sale. No direct replacement is offered. Further information on these changes can be found in PA-00495 - Notice of Withdrawal - Satchwell Sigma and PA-00528 - End of Commercialization - Satchwell Sigma. ---------------------------------------------------------------------------------------------------------------------------------------------------------- For more information on the re-branding of the Satchwell MicroNet product range, see PA-00145A - Satchwell MicroNet Range Rationalisation and Schneider Electric Re-branding. Old Part Number New Part Number IAC420-F IAC420-P MN350-LON MN350-NCP + MNL-C (LON card) MN450-LON MN450-NCP + MNL-C (LON card) MN550-LON MN550-XCOM + MNL-C (LON card) MN650-LON MN650-XCOM + MNL-C (LON card) MN50-TS-LON MN50-TSP-LON (Panel Mounted Only) MNN-COM MN550-XCOM or MN650-XCOM MN550-NCP MN550-XCOM MN650-NCP MN650-XCOM  

Issue How to connect a 4 wire PT100 or PT1000 sensor to a 3-wire RTD input. Product Line EcoStruxure Building Operation Environment Building Operation I/O Module 16 Ch RTD Cause Some PT100/PT1000 sensors have only 3 terminals to connect to. Resolution The wires to the sensor are often color marked in pair, like two red cables and two white cables. As we only have 3 terminals to connect to, the solution is to only connect 3 of the cables, and not connect the 4th cable.   As the RTD device also measure the resistance of the cables, to make a correct temperature reading, it is important that all three wires used do have the same length and resistance. Therefore, the fourth wire should NOT be connected in parallel, it has to be un-connected.

Issue Using BQL query to extract data from a G3 station How to display data from the BMS system on their custom / third party application. Environment I/A Series G3 Cause A requirement to display data from the BMS system on their custom application. Resolution You can query for data using a BQL (Baja Query Language) query. The Baja Query Language (BQL) is an SQL-like query language that provides a mechanism for identifying various sets of data. It provides an ad hoc way to search for data based on some criteria. 3rd party applications which is capable of running a web query can be used to query data from a G3 station. One such application is Microsoft Excel. The Niagara BQL Query Examples PDF provides several examples of BQL queries as well as an example of using Excel web query. Most data in a station can be queried including point values etc. For detailed description of BQL usage, refer to the Niagara Help in Workbench ( as shown below).

Issue How can System Alarms be disabled? Product Line EcoStruxure Building Operation Environment Building Operation Workstation Cause There are over 230 system alarms and at times they need to be turned off temporarily. There is no straight-forward method to gain access to the (intrinsic) system alarms, so an instruction on how to disable them is needed. Resolution You cannot stop system alarms from triggering. But if there are system alarms that trigger often, you might want to "turn these off". The way to do this is to disable the alarms, which would cause the alarms not to trigger again until they are enabled. An alarm has to trigger first in order for it to be disabled. To disable an alarm, right click on the alarm in the alarm list and choose Disable alarm. There is no menu or object to access the system alarms only. For a list of system alarms see What system alarms can occur in StruxureWare Building Operation?

Warning Potential for Data Loss: The steps detailed in the resolution of this article may result in a loss of critical data if not performed properly. Before beginning these steps, make sure all important data is backed up in the event of data loss. If you are unsure or unfamiliar with any complex steps detailed in this article, please contact Product Support Services for assistance. Issue Upgrading the MPMs firmware through the boot loader was unsuccessful. 10.50.80.2 is pingable, but not the default IP 10.50.80.3. The LED's keep blinking in tandem (alternating one after the other), even after having the MPM powered over 10 seconds. Product Line EcoStruxure Building Expert Environment SmartStruxure Lite Multi-Purpose Manager Cause This can be triggered by multiple events: - MPM was interrupted (powered off) while the firmware was still being upgraded. - Database does not exist; MPM was formatted and does not have firmware installed. - Database is corrupt (for any reason) Resolution It is strongly recommended that a firmware upgrade be done via the "File Manager" tab in Building Expert. However, if this is not possible, an upgrade can be performed through the bootloader using the following steps: 1 - At the top left part of the screen, make sure "Status" says "Connected". 2 - Format the SD card clicking on the "Submit" button next to "File System Format". "Format Done" will be displayed next to the button once the format has been completed 3 - Click on the "Browse" button and Navigate to the Firmware_update_V2.XX.bp" on your computer then click on "Submit Query". 4 - The previous step will upload the firmware file to the MPM's SD card. Once the file has been transferred, the following message will appear: or 5 - The MPM Must be kept powered-up for at least 15 minutes in order to allow the MPM some time to unpack the firmware file. The best way to determine whether the MPM is back online is to ping its IP address using a "Command Prompt" window. 6 - Once the MPM replies to the ping, Building Expert can be accessible though 10.50.80.3   If the above solution does not work; meaning that every time a new firmware is pushed to the MPM, the MPM keeps coming back to the bootloader, contact technical support

Issue How do I share data between standard Continuum controllers and Continuum BACnet controllers? What communication method is used (COV, Import/export, or point to point)? What problems can I encounter? Product Line Andover Continuum Environment Continuum Controllers (CX9200, CX9400, CX9900,CX9702, CX9680, bCX9640, ACX5720, ACX5740) Continuum BACnet Controllers (b4920, bCX4040) Cause All communication between Continuum controllers and Continuum BACnet controllers is done using point to point protocol. Since BACnet controllers do not support Import/export and Continuum controllers do not support COV, point to point is the only common method to communicate. Resolution The method of programming the data sharing can be the same as standard Continuum programming, however because of the point to point protocol a specific method should be used. Using typical Continuum programming techniques, you would create a mirrored point in the BACnet controller (a BCX for instance). You would then write a PE program in the BCX that mirrors the point, for instance: Line Mirror BCX DataPoint1 = CX/Infinet/DataPoint1 goto Mirror Line E: goto mirror This method would perform a point to point communication every BCX scan and retrieve the data whether it has changed or not. It will create a lot of unnecessary network traffic and slow the scans of both controllers. The line E is necessary because with a point to point communication, the program will disable if the target controller temporarily goes offline. Now consider if you were mirroring many points between the systems for instance you were using the BCX as a BACnet gateway for the Continuum system. That same program would have many points that are being transferred. You would also write multiple programs because of the number of points being polled. The net result of this programming method would be that the entire system would be brought to its knees! Extremely slow scan rates in both controllers because these point to point data requests have to be completed end to end during the scan. Congested Infinet communications because to get the Infinet points we go all the way down the 19.2K Baud Infinet to get the data. The system would just plain no longer function correctly. The only reasonable method to accomplish this type of data transfer would be for the owner of the data that you want to transfer to the other controller sends the data to that controller, and only on an as needed basis, such as a change in its value. Therefore in the scenario described above where you want to mirror points in a BACnet BCX from a Continuum system, you would write the transfer program(s) in the CX controller, and within that program use a local variable for each transferred point to allow you to know if its value has changed since the last transfer, and not retransmit if the value is the same, thereby significantly decreasing network traffic and burden on the system. This method has the added benefit of eliminating the need to clog up the Infinet network, because the program in the CX automatically creates an import/export relationship between the CX and the Infinet controller's points so the normal export broadcast will transfer the data to the CX. One example of the program in the CX to perform the data transfer is as follows: Numeric num1 Line Mirror If num1<>CX/Infinet/datapoint1 then set BCX dataPoint1 to CX/Infinet/datapoint1 num1 = CX/Infinet/datapoint1 endif goto Mirror Line E: if TS>5 then goto Mirror You could also streamline the programs using such methods as creating an InfinityFunction that would be called to minimize the redundant portions of the data comparison and transfer in the programs for multiple point transfers. The function could be named “Exporter” look like this: Arg 1 RemotePoint Arg 2 LocalPoint Arg 3 TestPoint If TestPoint<> LocalPoint then Set RemotePoint to LocalPoint TestPoint= LocalPoint endif Return And now any point that you want to be exported would call this function so the above program would be reduced to: Numeric num1, ..... numX Line Mirror Exporter (BCX dataPoint1, CX/Infinet/datapoint1, num1) . . Exporter (BCX dataPointX, CX/Infinet/datapointX, numX) goto Mirror Line E: if TS>5 then goto mirror After the initial scan when we send all the current data to the BCX, only changed data would be sent thereafter. This syntax would be repeated for each point that you wanted to mirror. This program is setup to be looping. You could create a similar program to be fallthru and trigger it from a minute or seconds system variable. If kept looping it would be recommended to go to a delay line between scans if there was a lot of data transfer going on. There should also be many programs like this if there is a lot of data to be transferred for a couple of reasons. First, if for some reason one of the points could not be transferred due to a temporary comm loss, the program would disable, go to line E and restart from the beginning, not executing any data transfer on the points below the one that failed. Second, if you were transferring many points, you would most likely exceed the maximum file size. Always be cautious as to how much data you try to transfer, and how often. There is no fixed limit per controller, but system performance will degrade proportionally to the speed and amount of data being transferred. As an additional note, it would also be extremely beneficial to put thresholds on the exported points to decrease un-necessary traffic.

Issue Procedure for installing PCC-10 or PCLTA20/21 network cards on a Windows 7 PC Product Line TAC Vista Environment Vista Menta LonMaker Windows 7 Cause Installation procedure differs from earlier versions of driver software. Resolution The PCC-10 and PCLTA-20/21 network cards work on Windows 7 (32 bit) PCs when the OpenLDV 4.0 driver is installed. This driver is installed automatically when Lonmaker Turbo SR4 is installed, but if this version of Lonmaker is not present the driver must be installed manually.  The latest drivers can be obtained from the Echelon download site: http://www.echelon.com/support/downloads Note: The PCLTA-20/21 card is only supported on 32bit windows operating systems. For 64bit systems use a NIC-USB as mentioned in this article: Computer will not recognize NIC709-USB. Install the drivers before fitting the card in the PC. Please note that OpenLDV4.0 requires .NET Framework 3.5 SP1.  This is not included as a subset of .NET Framework 4 or later, so must be installed separately.  You can have multiple versions of .NET framework installed on the same PC. The following description is for the PCLTA-21 but the PCC-10 is similar. To change the system image or perform diagnostics, you must go to Control Panel and open the Lonworks Interfaces application: Click Start on the taskbar, point to Settings, click Control Panel, and then open the LONWORKS Interfaces application. Click the PCLTA-21 interface in the list view on the left side of the user interface to display the interface's properties in the details pane in the right side. The details pane lists the PCLTA-21 card's system image and transceiver properties. To change the system image used by the PCLTA-21 card, click anywhere in the NI Application property, click the box to the right, and then browse to and select the desired system image from the LonWorks\Images\PCLTA21 folder. Note: For more information on configuring, testing, and diagnosing the PCLTA-21 network interface, see the LonWorks Interfaces online help.

Issue Is there support for the C-Bus protocol in StruxureWare Building Operation? How can we integrate C-Bus into StruxureWare Building Operation? Product Line EcoStruxure Building Operation Environment StruxureWare Building Operation 1.0, 1.1 and 1.2. Cause Requirement to integrate C-Bus protocol into StruxureWare Building Operation, Automation Server or Enterprise Server. Clipsal C-Bus integrated service provide two gateways (BACnet / OPC), that may provide a suitable integration option. Resolution StruxureWare Building Operation does not directly support the C-Bus protocol at this point. Currently Schneider Electric Buildings integration with the C-Bus protocol is typically through the Xenta 913 (See Tip and tricks for communication between Xenta 913 and C-Bus on how this is achieved). When Interfacing the Xenta 913 to the Building Operation offerings you must create connection objects to and from the C-Bus objects via SNVTs, which need to be separately created within the Xenta 913 XBuilder project. Once these SNVTs are exposed, then the Xenta 913 can be added on the LonWorks network allowing the unit to be discovered as a LonWorks device (i.e. only acting as a third party LonWorks device). There are also two offerings provide by the Clipsal Integrated Services division that can be integrated with Building Operation, these are:   1. C-Bus BACnet Gateway (5000BACnet) The C-Bus BACnet Gateway is an embedded device that provides a field bridge between Clipsal C-Bus lighting control systems and the BACnet open protocol. The C-Bus BACnet Gateway provides 255 group addresses from a single application address. The C-Bus BACnet gateway supports the reading and writing of BACnet objects between C-Bus and BACnet and is supplied pre-configured from the (Clipsal) factory. Below is the link to detail of the C-Bus BACnet Gateway (5000BACnet) https://www.clipsal.com/Trade/Support/Software   2. C-Bus OPC Server For larger C-Bus systems (i.e. >255 group addresses) then the C-Bus OPC Server provides a gateway for C-Bus and the OPC Data Access protocols. Current releases of Building Operation does not support OPC, so you will require either an OPC to BACnet or OPC to LonWorks application which can be purchased through third party vendors. SCADA Engine is the preferred Clipsal BACnet OPC Client solution used. http://www.scadaengine.com/ Even though this solution is focused on BACnet, it may also be possible for a similar solution using LonWorks. Below is the link to detail of the C-Bus OPC Server https://www.clipsal.com/Trade/Support/Software There are additional requirements for each of these options that may need to be considered, it is best to discuss these directly with your regional Clipsal representative.