Building Automation Knowledge Base

Issue Remote Alarm Manager does not work on Sigma 4.06. Environment Sigma 4.06 RAM Remote Alarm Manager Version 1.2 Version 2.0 Cause Site has been upgraded to Sigma 4.06 and Remote Alarm Manager 1.2 does not work. Resolution Sigma release 4.06 only supports the use of Remote Alarm Manager version 2.1. Download Remote Alarm Manager release 2.1 software

Issue When backing up the Continuum Database using SQL Server Management Studio the backup fails.  SQL indicates Status = 112  Environment Continuum SQL SQL Server Management Studio DB Backup Cause Insufficient disk space to hold backup file. Resolution Remove files from hard drive to free up a sufficient amount of storage space.

Issue Xenta Server installation on a LON network Environment LNS Network Cause Installing a Xenta Server on a LON network Resolution The Xenta Server can be installed anywhere along the LON channel as long as the terminators are located at each physical end of the wire. The server will function the same as any other LON node.

Issue The stop watch object operates erratically when set to days. If you set the stop watch to issue a pulse once a day it can issue a pulse 2 or 3 times during the day. Environment VisiSat Bubbleland Stopwatch   Cause Software/firmware error. No fix planned. Resolution When programming a stop watch do not use days. Instead of 7 days  use 168 hours  Instead of 14 days  Use 336 hours  If there is a requirement to convert the value back to a day for MicroNet View graphical representation, A suggested method follows: -   In VisiSat find the stopwatch object.  Add the Stopwatch Rollover to the VisiSat points list. Under the menu topic Tools Export your points list to MicroNet View.   In the MicroNet View project manager and load the new points. To view the hour value received from the controller as weeks on the graphical interface. Open MicroNet View in Development mode (Window Maker) Open the window that the value will be added too. Add some text to the Windows you want to display the value. For example “###” To view the rollover value, add the tag for the stop watch rollover value. To show the value as weeks add /24 after the tagname. Below is an example of both showing the results. This can be achieved using a data change script. In MicroNet Window Maker (Development mode) add a tag and data change script. The tag could look something like this. The minimum and maximum values of the tag can be changed to provide limits. The data change script could look something like this.  To display and allow the user to change the value in weeks. Add some text to the Windows you want to display the value. For example “###” Inside the "###" should be set for "user inputs Analog" (Analogue)  Click on "user inputs Analog and select the data change tag created earlier.  Using the example from above, the window will now look like this  To set the rollover in days click the days set area.  Change to the required amount of days. Hit the return key to enter the value.  The Rollover is now set to 14 days. It is important to remember the rollover value in the controller its not 14 it is the hour value 336. It is just at the MicroNet View front end/user interface window where it is displayed as days.

Issue How many digits can the PIN number be when using card + PIN entry? Also how can it be viewed as it is displayed as stars in the Personnel Manager? Environment Access Controllers Card + PIN entry or exit Display PIN number Cause Leading zeros on a PIN number are not saved and how long can the number be? Also as the number is shown as * characters how can the number be seen? Resolution The PIN number for a personnel object can be in the range: 0 to 4,294,967,295 inclusive for the NC2 (9680) and ACX2 (ACX5720/40). For all other older controllers the PIN range is 0-65535 You are not allowed leading 0’s in a PIN number, they will be removed. i.e. 0010 will save as 10 0000 will save as 0 To view a persons PIN number, use the "Command Line" application and from the folder where the personnel are stored enter: P PersonName PIN This will print the value of the PIN attribute for the person named "PersonName".

Issue The Analogue output card only produces 9.9 volts dc. Environment Sigma Analogue Output Voltage Cause The Analogue output card only produces 9.9 volts dc, can it produce 10 volts? Resolution No, although the card is said to produce 0 - 10 volts, it will produce slightly less. For the data sheet please click here.

Issue Can SIGNAL send alarms to a pager? Environment SIGNAL all versions Cause End customer has requested pager numbers be added to alarm notification.  Currently just visual display on the SIGNAL computer via Alarm Manager and printouts to the connected printer are available. Resolution SIGNAL does not have the ability to dial out alarms to a pager.  Years ago, a 3rd-party product called Alarm Flash was used to provide this capability.  If a similar product is available today, it may work with SIGNAL's Alarm Manager. Another alternative is to use a modem connected to the field panel (GCM or DMS) that can dial a pager number via a modem when an alarm occurs.  There are also several 3rd party products which can interface serially to the field panels and be programmed with several phone numbers and customized text messages.

Issue File Equalization, what passes between the Filemaster and Equalized Client Environment I/NET with Filemaster and Equalized Client snapshot, equalize, tables Cause What transpires between the Filemaster and Equalized Client Resolution File equalization is essential in TAC I/NET Seven systems where multiple host workstations will be used to manage access control or TAC I/NET Seven’s network configuration. It allows host workstations connected to an Ethernet LAN to share certain database information while still maintaining their own TAC I/NET Seven database. File equalization is a function of the SQL server that is installed on TAC I/NET Seven workstations. The SQL server ensures that each individual workstation has up-to-date copies of equalized information. The equalized information includes: Network configuration (links, sites, stations, etc.) Host passwords Controller passwords Tenant data User-defined tenant field labels Individual records Group door assignments Elevator floor assignments Trend plot data The following tables are equalized: Tenants Individuals IndivCustomData IndivImages IamUser DoorsGroups Groups SecondaryGroups XRefTenantDoor XRefGroupDoor XRefIndivGroupDoor Cards CardTrans Floors FloorPoints Visitors Operators OpWindowPosition XRefOperatorDoor PwdHistory AmtFilters MultiPlot MultiPlotPnt PwDCU DpuRestore DoorScheduleTypes DoorSchedules PerSchedNames PerScheds GlobalOptions DispatchStrings Tools UserButtons NetConLink NetConSite NetConDCU NetConMCU NetConDoor

Issue Logging off one user, logs another user on. Environment Sigma Users Logon Logoff Cause When a specific user logs off  the Sigma system, another user is logged onto the system. Resolution This issue is caused by corruption of the GenCNF.rec and user files, there are two options available. Locate a backup of the system files that was taken before the corruption occurred. Shutdown the Sigma server and all clients. Copy the GenCNF.rec file and the User folder from the system backup. Paste the copied files into the Data folder. Restart the Sigma server and clients. Test the user access operation. Rename the corrupted user. System users cannot be deleted, they can only be re-named. In the Sigma SSM / Users, highlight the User name and select to rename it Rename the user to an appropriate name. Create a new user to replace the old user, allocate the correct access levels. Test the user access operation.

Issue Choosing the correct range of sensor is important in order to provide the most accurate value. Environment SPD310 SPD360 Cause Only the max value is specified for each range. How low is the lowest accurate value? Resolution The reasonable minimum pressure in the 100Pa range should be equal or greater than 40Pa (typically), otherwise the max. error becomes bigger.

Issue Need to know if Continuum account passwords are encrypted Environment Cyberstation and webClient (all versions) Cause No cause - information only. Resolution Continuum passwords are encrypted with an algorithm. Being salted and hashed before being saved in the Continuum Database.

Issue National Weather Service Data Showing Stale Product Line TAC IA Series Environment I/A Series N4 Enterprise Server I/A Series N4 Jace 8000 / 9000 Cause Due to recent changes with the National Weather Service, the current weather information displayed through Niagara is showing as “Stale” when using the NWS Weather Provider in the Niagara Weather Service. Resolution The Current Conditions “Last Update” time may be null or a current date, and the “Observed” time may be null or a date in the past. Current Weather View: Property Sheet:   This issue is being addressed in future releases. In the meantime to manually correct this behavior, make the below manual updates to the BNwsWeatherProvider components in the station: 1. Go to the Property Sheet view on the BNwsWeatherProvider component, click the ‘Slot Details’ button, then click the ‘Hidden Slots’ button to display the hidden slots. 2. Click the Flags for the “Conditions Server” slot which opens the “Configure slot flags” dialog.  Clear the checkbox for the Hidden slot flag, then click the OK button to clear the Hidden slot flag.  3. The “Conditions Server” slot should now display “(none)” in the Flags column.  4. Click the “Slot Details" button to toggle back to the default Property Sheet View.  The “Conditions Server” property is configured with the default value of “www.weather.gov”. 5. Update the “Conditions Server” property to “forecast.weather.gov” and save the change. 6. Invoke the “Update Weather Report” action on the Weather Report component and verify the Current data updates and no longer indicates a Stale status.              

Issue Lookup table downloads. Environment Lookup tables AI Objects Downloading Cause Analogue valve is not correctly displayed, due to a missing lookup table in the controller. Resolution When a lookup table is assigned to a Sigma object, it is not automatically downloaded with the object. The lookup table must be downloaded via "System Diagnostics" and "Download Files" where Lookup.rec is selected from the options.  

  Issue Is it possible to host the same third party BACnet device on the AS-P private networks on multiple automation servers, which are all connected on the same network? Product Line EcoStruxure Building Operation. Environment Building Operation Automation Server Premium Cause The design in question is a 3-storey accommodation building which includes 1 x BMS panel/AS-P per level. However, only 1 x Mitsubishi EW-50E BACnet gateway is being provided for the building. Resolution It is possible to host the same 3rd party BACnet device in multiple AS-Ps. Some caution is required, however, because if the user makes changes to an object in that device through one AS-P, that change may not be reflected in other AS-Ps. When viewing runtime variables, such as 'Value' and 'Status Flags', this is not a problem because the EBO server will always get new values from the wire. Where the problem can present itself, is when changes are made to configuration values because these are only updated in an EBO server during an upload operation. For example, if you set the hi-limit and low-limit values in an analog-value object from one AS-P, those values will not be updated in other AS-Ps until you do an upload of that object.   The other place where this problem may present itself is in schedules. An EBO schedule only writes values to a device when that value changes. For example, if you have a schedule configured to change the setpoint to 65 degrees at 5pm, EBO will only write a value of 65 if the current 'local' value is not 65. If this schedule only writes 1 time per day and someone has set the value to 70 from another AS-P, the first AS-P does not realize the value has changed so that schedule will not generate a write request to set the value to 65 (it will stay at 70). However, if you have a program or trend-log monitoring the value, the AS-P will be tracking that value and realize it is not 65 so you will see a write request at the scheduled time.   The system works this way because reading all values of all devices and all objects all the time is simply not practical. As long as the user is aware of how the system is designed, they can avoid these potential issues.   Make sure to use Static IP, so IP do not change, or you get multiple DHCP servers on the same network.   Another alternative is to host the BACnet device in one AS-P only, then using internal bindings to share the data with other AS-Ps.

Issue The process of merging two Index files. Environment BAS 2800+ BasFiles Merging Indexes Cause BasFiles in it's basic form cannot be used to merge Index files. A switch is required. Resolution When starting BasFiles normally the options presented are as follows; To merge two BAS site Index files together, BasFiles needs to be used in a different mode, this mode is not normally available, and a switch is required. To start BasFiles in the mode that enables merging, carry out the following.. From the Windows "Start" button select the "Run" option. Browse to where BasFiles is located and select it. To BasFiles.exe add the extension "space"scs as follows  - BasFiles.exe scs When run a new menu option is now available. Having selected the "Merge" option, you will be presented with the window below. Note - The directory structure used must be present before merging takes place..

Issue An initial calculation of KWH produced a artificially high value that was captured by a trend log and is now stored in Report Server. This anomaly is artificially skewing the auto scale feature. Environment Web Report Server Trend Log Extended Trend Log Extended Log Cause The trend data anomaly is artificially skewing the auto scale feature of the trend graph in Report Server. Resolution Open the associated extended trend log. Right click on the entry that is to be corrected and select edit record.  Change the value of the entry to some more acceptable value. Enter  a reason for the change in the comment field. Select save. The new value will appear in place of the original entry with an icon to show that the value was altered. Allow up to 24 hours for the data to be migrated into Web Reports Server.

  Issue Understanding the size of individual tables within the Security Expert databases is essential for effective database management. This insight helps optimize system performance and supports archiving strategies. Product Line EcoStruxure Security Expert Environment EcoStruxure Security Expert Microsoft SQL Server Cause Managing SQL database size is critical to maintaining system performance. Identifying which tables consume the most space provides actionable data for optimization and archiving. Resolution To determine table sizes in the Security Expert and Security Expert Events databases, follow these steps using SQL Server Management Studio (SSMS): Open SSMS Right-click on the relevant database (e.g., Security Expert or Security Expert Events). Navigate to: Reports > Standard Reports > Disk Usage by Table Review the report to identify tables with the largest data footprint. Examples: Security Expert DB Security Expert Events DB Exporting the Report You can print or export the report for documentation or analysis: Print Export to Excel, PDF or Word Right-click on the data results and select Export Note: The “Disk Usage by Table” report is available in SQL Server 2008 and later.

Issue Communications with the controllers is very slow. Environment Slow communications Displaying objects seem to lock up Globals V53 hardware Cause Communications with the controllers is very slow. Objects will display correctly once, but if the display is carried out several times, or if an object is overridden, the server appears to lockup. Resolution The issue was caused by two Sigma objects being globally transmitted at the rate of 12 per second. The two objects were Programmable and the programme had been incorrectly written as follows; 10 IF POINT 0|108 = 0.000000 THEN RETURN "Ch1  Off" 20 IF POINT 0|108 = 1.00000 THEN RETURN "Ch1 Start" 30 IF POINT 0|108 = 2.00000 THEN RETURN "Ch1 Running" 40 IF POINT 0|108 = 3.00000 THEN RETURN "Ch1 Shutdown" 50 IF POINT 0|108 = 4.00000 THEN RETURN "Ch1 Service" The above object is incorrect because it does not specify True or False. Because globals are transmitted on "change of state" the global was being transmitted with every scan of the object file. It is recommended that the object is changed as follows. 10 IF POINT 0|108 = 0.000000 THEN RETURN FALSE "Ch1  Off" 20 IF POINT 0|108 = 1.00000 THEN RETURN TRUE "Ch1 Start" 30 IF POINT 0|108 = 2.00000 THEN RETURN TRUE "Ch1 Running" 40 IF POINT 0|108 = 3.00000 THEN RETURN TRUE "Ch1 Shutdown" 50 IF POINT 0|108 = 4.00000 THEN RETURN TRUE "Ch1 Service"

Issue A displayed on main display. Environment CMC CSMC A Alarm Cause Showing A for alarm on the display Resolution Set code B61 to 1 Click here to download the data sheets.

Issue EBO acts as a BACnet server and a BACnet client send SubscribeCOVProperty to get value updates of specific property of a BACnet object, ex. present value, but EBO respond with "NOT_COV_PROPERTY".   Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Automation Server Building Operation Automation Server Premium Building Operation Automation Server Bundled Building Operation Edge Server - Standard Cause Specified property does not support COV notifications. Resolution EBO only supports SubscribeCOVProperty (DS-COVP-B) for the following properties and object types: Status_Flags: AI, AO, AV, BI, BO, BV, MI, MO, MV, Loop, Trend Log Event_State, Reliability, Out_Of_Service: AI, AO, AV, BI, BO, BV, MI, MO, MV, Loop When a client attempts to use SubscribeCOVProperty for another property not listed above, the appropriate response is 'Not COV Property', as specified in BACnet standard. When getting this response from EBO, the client is expected to automatically use another method to acquire the property value (either via COV subscription or polling). If the client is attempting to read Present_Value, then using SubscribeCOV would be the preferred mechanism.