Building Automation Knowledge Base

Issue Which Continuum controllers support RAS via modem connection? Environment CyberStation CX9900 CX9940 CX9680 CX9640 CX9200 CX9924 Cause Not all Continuum controllers support modem connection. Resolution The access point for a remote site is the controller that is configured with a modem that is used to establish a communication link with the remote CyberStation. Only the following Continuum controllers can act as access points for remote sites. CX9900, CX9940, CX9680, CX9640, CX9200, CX9924. Note that other controllers communicating with the access point controller via ethernet can fully participate in RAS communications as the access point controller will route messages to/from its peers.

Issue Does Sigma 4.04 support a Windows 7 operating system? Environment Sigma release Windows 7 Cause Sigma release 4.04 does not support a Windows 7 operating system. Resolution Sigma 4.04 cannot be used on a Windows 7 operating system. It is recommended that the earliest release of Sigma to be used is 4.05 SEB, To review the release note, please click here.

Issue Are examples available to show how to write Plain English programs and create points for a Modbus RTU X Driver linked to Schneider Electric Power meters? Environment Modbus RTU X Driver Schneider Electric PM700, PM750 Power meters. Cause Requirement for some examples to see how Modbus RTU programs can be written to poll for the data in a 3rd party Modbus device. Resolution The attached example was written by an application engineer in the UK to extract data from the Schneider Electric PM700 and PM750 meters. This example provides the mapping of data for these 2 specific meters, but the polling principle utilized in the Plain English programming can be applied to any Modbus RTU interface Download file here. 

Issue Boiler plant is not operating. Environment DC1100 DC1400 Compensator Plant Off Day Economy Cause Controller is in a Day Economy mode. Resolution The DC1100 / DC1400 has a mode known as "Day Economy, this will prevent the plant from working. The controller display will show "Day Economy", its operation is as follows. Day Economy Day economy will allow the system to turn the heating off during an occupation period if the space temperature is at or above the Space Setpoint and the outside temperature is within 4 degrees of the Space Setpoint. When the heating is switched off by day economy, pump run-on will commence. If during a day economy period the space temperature drops more than 1 degree below setpoint or the outside temperature is no longer within 4 degrees of the Space Setpoint then the heating will switch back on. The Day Economy function can be disabled though the controller menu system. For further details please select the data sheet HERE.

Issue XBuilder project will not download to the controller and there are no errors indicating other known issues with a download. It simply fails. Environment Xenta Server Xenta 511, 527, 701, 711, 721, 731, 913 Cause The Xenta controller may need to be recovered due to various software and hardware issues. XBuilder/Xenta firmware versions do not match Hardware or firmware failure requires hard reset Corrupted XBuilder project Fail-safe Resolution Check all software versions to ensure Vista, XBuilder, and Xenta Firmware all match. Correct any discrepancy by upgrading to the latest version. Try to download the XBuilder project, if that does not work...   Run in failsafe mode by jumpering pins 9 and 10 before power up. Try to download the XBuilder project, if that does not work...   From Hyperterminal DSH prompt do a FORMAT command. Correct the IP Address Download a new System Program to the controller. Try to download the XBuilder project, if that does not work...   Download a "blank" XBuilder project to ensure the project is not the root of the problem. Try to download the XBuilder project, if that does not work...   The controller may be bad. Replace the controller.

Issue The Forta range actuator does not fit onto the V321 Valve. Environment V321 M800 M1500 MV15B M3000 Cause The actuator has a 10mm fitting, the valve (DN65 to DN100 only) spindle has a 8mm stem. Resolution On V321 valves size DN65 to DN100 an adaptor piece is supplied with the valve part no. 880-0133-000 to adapt the valve spindle to the actuator drive. The part no. 880-0133-000 can be ordered separately.

Issue What is the maximum binding count per graphic when polling OPC tags? Product Line TAC Vista   Environment Vista Server Vista OPC Server Cause There is no limit to the number of OPC tags, but performance may be affected when a large number of binding are used. Resolution The load on the Vista server should be considered. E.g. datatypes and the update period: Does an outside air temperature tag need to be updated every 10 seconds or is 10 minutes maybe more appropriate? Can binary signals be combined into a single register?

Issue 7718 and Expansion Modules Environment I/NET Site Cause What Expansion Modules come with the 7718 controller? Can those be bought separately? Can the ribbon cable or stand-offs be purchased separately from the P16UI expansion module also referred to as the P16UISO Resolution P16UISO 16 Point Universal Input Module 7718 PCU module, 8.6” x 3.4” (21.8 cm x 8.6 cm). Standoff mount. The Sixteen Point Universal Input (P16UI) expansion module provides sixteen universal (analog or contact) inputs. The expansion module card is 3.25"L x 8.60" W (8.25 x21.8 cm). It attaches on top of the 7718 with standoffs supplied with the module. Signals are passed from the P16UI through a ribbon cable type connection between the terminals of the two boards. The input points on the Sixteen Point E16UI Expansion Board occupy point addresses 0100 through 0107 and 0200 through 0207. Please find the 7718 Expansion board Input testing procedure below. Also here is the Datasheet Below is the part number from iPortal: This is the Model numbers and brief description:  Expansion Board Testing Procedure: 7718 Expansion board Input testing All 8 AIs (TBX1-1,4,7,10 and TBX2-1,4,7,10) come in thru the same analog multiplexer IC U3. The only components in front of the Mux is a .47uF capacitor on each input and a 100K resistor on each, and then the user plug-in resistors. I assume reference to TBX1 is associated with 1st input channel on pin 1 and 249 ohm is being plugged in to SIP socket RS3 position A1. Assuming no other resistors are plugged in to any of the Bx, Cx or Dx positions, there isn't much left that can be wrong. Get the specifics of what input signal level is causing what count to be seen. Use M & B of 1 & 0 to report straight counts. Make voltage measurements on the TBX1-1 and TBX2-1 terminals with signal being injected, and record the counts seen on the HHC, or PC, for a low medium and high level signal. An external power supply can be used in place of the sensor to easily set a 0V, 2.5V and 4.90V signal input. We want something less than 5V so we don't get the high end max count of 4095 which can mask a high end + error. If they don't have a supply, differing values of resistance can be plugged in to positions A1 (pull down) and B1 (pull up) with J10 set to B-C position so the B positions are pulling up to 5V. 1K in A1 position and B1 open produces 0V input. Measure and confirm volts and counts 1K in both A1 and B1 positions produces mid scale of approx 2.500. Measure and confirm volts and counts 10K in A1 and 1K in B1 positions produces high end of approx 4.545V Measure and confirm volts and counts This can be repeated on TBX2 using resistor positions A5 and B5 The A/D Counts should equal (measured volts / 5 * 4095) 2.500V = 2047 counts 4.545V = 3722 counts See what the above shows as a possible indication of where something is going awry. An A/D count that is correct on one input and wrong on another with only the specified resistances plugged in, or no resistances plugged and an external voltage source being used, would suggest a faulty multiplexer chip (on only specific selected channels) or a faulty capacitor. Return for repair.  

Issue Drayton DC1000 Energy Controller requires replacement. Environment Drayton Stand alone DC1000  DC 1000 Discreet  Energy Controller Optimiser Compensator Optimiser/Compensator Optimiser / Compensator Cause Obsolescence of Drayton DC1000 Energy Controller. Resolution There is no direct replacement of the DC1000, the DC1100 and the DC1400 are also obsolete now.

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 Is there a way to globally change the path of active animation controls so that each control does not have to be edited manually? Pinpoint graphics will be very slow to open if the image file is on a network drive that is no longer available. Product Line Andover Continuum Environment CyberStation Cause A method to make the change globally in one operation is required system the design does not provide a way to do it. Resolution As of version 1.94 Continuum does not provide a mechanism to globally change the path of image files in active animation controls in Pinpoint. This can be a problem when a large number of active animation controls have been created using a given path and the image files then need to be moved. If the image files must be moved, every effort should be made to retain the path that was used in the controls, otherwise the path to the files will have to be manually changed in each active control that references the path in the graphic panel. With the above said there is a way to go in the Graphic PIN file and change the path, it requires a hex editor such as HxD. Using a hex editor the path for a control like this Can be found and changed in the PIN file itself, like this... *** Warning *** Please note that the length of the new path string must be the same length (i.e. take up the same number of characters) as the original path string, otherwise the file may become corrupted. As an example the following cannot be used replacing C:\Program Files\Continuum\NewGraphicsFiles with E:\Graphics, but the following could replace C:\Program Files\Continuum\NewGraphicsFiles with E:\Program Files\Continuum\NewGraphicsFiles   Notes: If a system is upgraded (new PCs) or a network drive that contains the image files is no longer available, then the graphics can be very slow to open.

  Issue The WebStation menu used to create new calendar dates and values is not visible. Product Line EcoStruxure Building Operation Environment Building Operation Workstation Building Operation Webstation Building Operation Enterprise Server Cause The panel used to display the calendar schedule is incorrectly configured Resolution In Workstation, right-click on Panel and go to Properties, go to Show Toolbars, and choose Yes.    Now when you log in to Webstation, you will see the toolbar including the menu on the top of the calendar in the panel.     

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 How to setup automatic table truncation on Single-User SQL Express systems. Product Line Andover Continuum Environment Continuum Cyberstation Single-User SQL Express SQL Server 2005 Cause Only the ExtendedLog table is automatically truncated on an Single-User SQL Express Continuum system. The other tables that can fill up quickly and need to be truncated regularly are not catered for (accessevent, activityevent, alarmevent, and errorevent). Resolution IMPORTANT: Make sure to perform a full SQL Database backup before attempting to make any changes to the database. (See Move / Backup / Restore a database on a Single User SQL2005 Express system for details on how to backup your database and, if not already installed, where to get Management Studio from) Use the attached file SQLExpress to add table truncations.zip, to configure your Single-User SQL Express system to automatically truncate these tables when it does the ExtendedLog truncation. After downloading the file, follow the steps below. There are three files in the archive, these need to be copied to your Continuum folder on your Single-User system running SQLExpress as the database engine. LogTruncate.SQL This file is the SQL script that performs the truncation of the four tables (accessevent, activityevent, alarmevent, and errorevent) to the number of days you specify - I have selected 90 days as my default but you can change this to whatever you require for each table. CS_LogTruncate_OneOff.bat This batch file will run the LogTruncate.sql script once when manually executed. You will need to change the server name "PC3" to whatever your PC's name actually is on your system. CS_Hrly - with LogTruncat.bat This is the batch file that will be renamed and replace the existing "CS_Hrly.bat" file currently located in your Continuum folder. This is the same as your current file except it has added the LogTruncate.sql script so that this will now be executed every hour along with the rest. Backup "CS_Hrly.bat" file in Continuum folder by renaming the file to something like "CS_Hrly ORIGINAL.bat". Rename "CS_Hrly - with LogTruncat.bat" to "CS_Hrly.bat", copy into (overtop the existing file if you haven't renamed it) the Continuum folder, and change the server name "PC3" to your PC's name. This should now execute this table truncation script along with the other database maintenance scripts every hour.

Issue Replacement for Satchwell DDT0001 Duct Temperature Sensor.  Environment Satchwell Sensor DDT DDT0001 Cause Obsolescence of Satchwell DDT0001 Duct Temperature Sensor. Resolution Replace Satchwell DDT0001 Duct Temperature Sensor with Schneider Electric STD660 Duct Temperature Sensor. The Schneider Electric STD660 provides the same functionality as the Satchwell DDT0001, differing only in its appearance, dimensions and terminal identification. The Schneider Electric STD660 Terminals are not polarised.    

Issue Where should door connection be made on a SCU1284 Termination, Terminal number, PIN, SCU1284 Environment I/Net SCU1284 Cause What output to use for door contact Resolution This information is taken from TCON 312.  

Issue How to Logon / Logoff Continuum using a button on a Graphic or Menu page. Environment Continuum Cyberstation Cause Want to be able to Logon Continuum with the click of a button from Graphics or Menu page and also bring up the Logon prompt the same way. Resolution ** DISCLAIMER ** This application is not a supported part of Continuum and is provided as-is. 1. Copy the "Logoff.tx_" file in this archive, here, to the Continuum folder (c:\Program Files\Continuum). 2. Rename the .tx_ file extension to .exe. 3. Create hotspots / buttons as below to call the program with the two available command line arguments; 1 will logon, 2 will logoff. Suggested usage: On the Main Continuum Menu page create two buttons, one for logon, one for logoff. (Pinpoint could also be used for Logoff but would not work for Logging back on - Pinpoint closes when the user is logged off.) For the Logon Button:                 Set control to:        Execute                 Open:                     C:\ProgramFiles\Continuum\Logoff.exe                 Arguments:             1                   Button Text:           Logon   For Logoff Button:                 Set control to:        Execute                 Open:                     C:\ProgramFiles\Continuum\Logoff.exe                 Arguments:             2                   Button Text:           Logoff

Issue Values in EBO from a PM5000 series energy meter do not update Product Line EcoStruxure Building Operation, Field Devices Environment Building Operation Server BACnet PM5000 series energy meter Cause The EBO trace log shows a lot of BACnet related error messages, such as:   nsp.pin.BACnet.VariableProperty Subscription to ~/BACnet Interface/IP Network/PM 5340/Application/THD Current - Ph G attempted COV, but will POLL due to BACnet error: 0x00030013 (resources,no_space_to_add_list_element)   This error indicates that a Change of Value (COV) subscription is being attempted but has failed. This is due to a resource issue with the device, i.e., error class 0x0003 from error code 0x00030013. The error is no space to write property (0013 part) which suggests the subscription limit of the device has been reached. Refer to the Decoding BACnet Errors Knowledge Base article for further information on decoding the error code.   Reviewing the PM5300 series user manual reveals that the device only supports 20 COV subscriptions.     Resolution Remove BACnet objects that are not required in EBO, it is unlikely that fewer than 20 values will be practical. Disable COV for the device in EBO. This can be done via the service_blacklist as noted in the BACnet RULES implementation to disable features such as readPropertyMultiple, COVs etc How to disable RPM (readPropertyMultiple), COVs etc services in AS/ES BACnet interface. Knowledge Base article. The following is an example service_blacklist for the PM3450 <blacklist> <rule> <vendor>10</vendor> <model>PM5340</model> <no-cov/> <no-rpm/> </rule> </blacklist> Polling can put an unintended load on the polling device and the polled device. The polling intervals should be adjusted using the settings on the BACnet Interface. This is available from BACnet Interface -> Properties -> Advanced and scroll all the way to the bottom as shown below for an ES. If looking at the option for an Automation Server it will also have additional options for the RS485 communication ports. Minimum polling intervals in the range of 5,000 to 10,000ms are a good starting point.  

  Issue For an AS-P running on EBO 4.0.3.176, in Device Administrator, it is showing the State-Ready (Device crash logs available). When trying to download the debug info, it populates the below error and does not get rid of the logs.   ERROR: Failed to run devadmin3 command cmd with arguments -u -m devadmin3 --sa -v cmd 172.20.214.78 -b *** "rm -f /var/sbo/log/crash/coredump_SM222432005_nsp_servers_2022-09-03_110836.tgz" :rm: can't remove '/var/sbo/log/crash/coredump_SM222432005_nsp_servers_2022-09-03_110836.tgz': Permission denied   Product Line EcoStruxure Building Operation Environment • Building Operation Workstation • Building Operation Automation Server Cause Not running Device Administrator correctly Resolution When opening Device Administrator, ensure to run as administrator as below. This will clear device logs.  

Issue What diagnostic information is available within Niagara that can be sent to Product Support or acted on locally? Product Line TAC IA Series Environment I/A Series Enterprise Server I/A Series Jace Cause Jace or Enterprise Server operating slow or specific problems are causing the need for debugging a station or platform Resolution There are several diagnostic tools available: Check the station Resource Manager Right-click on the station and select "Views - Station Summary" This will open up a resource monitor page where you can check CPU and memory usage.  The CPU should not be consistently above 80%.  Spiking is common as the process is executing and completing tasks.  There are other things easily referenced here also. Heap memory will vary as well.  It can slowly increase until a garbage collection cycle releases unused heap back to the pool.  You should never use more than 75% of the total available heap memory. Heap Memory is primarily used by station modules and java program objects, so if the memory usage is high, these 2 might be the main reasons Engine Hogs   Right-click on the station, and select "Spy". From the main view, click on "sysManagers". Click "engineManager" and then scroll down to find "Engine Hogs". Clicking Engine Hogs will open a list of the main components of the station and a column on the right-hand side will display the average execution time of the component. Review the top 10 or so and see if any are taking an extraordinary amount of time.  This can help to locate improperly executing objects. Driver Poll Rates Drivers that are based on polling data, like BACnet when COV is not enabled, or Modbus constantly run commands to read data based on the fast, normal, and slow configured rates.  Open the Poll Service under the network the points are being polled on. Looking at the property sheet of the driver, it is important to verify that the cycle time (1) for each rate (fast/normal/slow) is always equal to, or below the actual time configured (2) for that rate. The defaults are 1 second for Fast Cycle Time, 5 seconds for the Normal Cycle Time and 30 seconds for the Slow Cycle Time. Seeing a longer cycle time is usually an indication that the network is saturated with commands and may cause the Jace/Niagara controller to be slow with heavy use of controller resources.  There are several ways to correct this: changing the polling rate spreading the number of objects being polled at each rate, etc. In this example, all points (3) are in the "normal" bucket. Application Director console The "Application Director" (under "Platform") shows a live console output.  Open it by clicking the option under the platform Copy the content of the Application Director, or "stream to file" to send the content to support. It will be essential to help the support engineer to understand the problems in the station.  Add more debug information to the Application Director console You can add more granularity to the messages in the Application Director for a deeper look into possible issues. This can be accomplished in 2 different ways: Right-click on the station, and select "Spy". Then, select "logSetup" on the main view From the list that appears, you can scroll and find appropriate topics to log and you can select at what level you want the information to appear.  This will add traffic to the application Director window so be careful how "fine" and how many logs you enable.  It might be good to consult with support before enabling these logs. example; bacnet.debug/finest if you select this box. Debug Service   Select the "DebugService" from the station "Services" In the Log Category, type a few letters of the topic and scroll to find what you are interested in logging From the pulldown menu, determine the granularity of the log Click the plus Click "Save" Setting this logging and streaming the output to a file will allow information to be sent to support for better diagnostics if required.  Remember to set this logging back to "Default" when done so the Application Director is not overwhelmed with information when you are only trying to view normal station activity.

Issue Can SLPSXC2 CO2 sensor calibration be used with both methods (ABC standard and Fresh Air process) at the same time? Product Line Field Devices. Environment Building Operation SmartX Living Space Sensor. Cause SLPSXC2 CO2 can be calibrated using two different methods. Automatic Baseline Calibration(ABC) The ABC algorithm constantly keeps track of the sensor’s lowest reading over a pre-configured time interval and slowly corrects for any long-term drift detected when compared to the expected fresh air value of 400 ppm. ABC calibration is enabled/disabled through coil 4 (invoke = enable ABC). Manual Calibration Coil 11 triggers the manual calibration (FRC 400ppm) => this will tell the sensor that the current level of CO2 should be interpreted as 400ppm. When setting this register to 1, it automatically goes back to 0 a couple of seconds later. Setting Coil 11 to value 1 is the same as pressing the calibration button. Resolution The both methods of calibration can be used simultaneously since one method is for correcting drift over time (1 week intervals), the other is a manually executed reset.   The only error would come if the unit was exposed to high CO2 concentrations at night, inducing abnormal averages. If ABC is disabled, manual calibration would need to be performed more frequently.

Issue Need to export Access Events automatically to a file format that a third party system can then import. This needs to be triggered at a set interval such as once a day. Product Line Andover Continuum Environment Continuum Access Control Cause Events can be exported from Continuum using a Listview of AccessEvents and then exporting to .CSV format file but this needs to be set up and manually run by the user. There does not appear to be an automatic method to get the same results from a listview into a file format. Resolution There is a method that can be used to export AccessEvent data to an external file without user intervention. The file format will be in HTML or XML format. A file format of XML is the obvious choice as it is usually easier for third party systems to import from an XML format. To do this, you will need to: Create a Report object with a Datasource set to "AccessEvents" or "Listview". These would then be configured with the AccessEvent attributes that you want to export. Once the desired Report is created, configure it so that it is run automatically using Windows Scheduled Events and the ReportCmdLine.exe application that is available for this purpose. See the article here for detailed steps on how to set this up.