Building Automation Knowledge Base

Issue The PowerUptime value is later than the current time. This issue may cause some program cannot run if the PowerUptime value is checked in that program. Environment TAC Continuum BCX-1 BACnet Controllers, for example B3851 B3867 B3887 and so on. Infinity Controllers, for example I2851 I2867 I2887 and so on. Cause Maybe there are two reasons. The first reason may be that the computer installed Continuum Workstation don’t synchronize time with the Domain server. The second reason may be that the controller has been learned in another Continuum Workstation, and that Workstation time is error. Resolution Firstly, interrupt the controller’s power. After approximately half a minute, reconnect the controller’s power.

Issue Modbus XDriver value may have to be converted to obtain correct value. Example: Temperature point read from slave device as 7985.00 must be divided by 100 to obtain its correct value of 79.85 Environment CyberStation All CX master controllers Modbus XDriver Cause For various reasons slave devices may store values in a different format such as storing the floating point value 79.85 as an integer 7985, in such cases the read value has to be converted on the Continuum side. Typically these conversions involve dividing or multiplying the read value by a multiple of 10 Resolution Consult the documentation of the slave Modbus device, typically the listing specifies the required conversion EXAMPLE: Here is an example from the C-TRAC3 HVAC controller Modbus documentation. Ambient Temperature Sensor - Description: Outdoor ambient sensor generally located in the outside air inlet. - Read only - Modbus® register: 30709 - Return value: The floating point variable inside the C-TRAC3 has been multiplied by 10 then converted into a Signed Integer which is sent out on the Modbus® port. To reconstruct a single precision number, divide the returned integer value by 10. - Sensor range: -46 to 160 °F In the example above the read value must be converted by dividing it by 10, this can be done directly upon referencing the value or a second numeric point can be created to hold the converted value, a PE program reads the raw value, makes the conversion and stores the results in the secondary numeric point. 

Issue Continuum Reports Suite runs under Administrator level user, but will not run under a user group to which the Administrator privileges have been copied. Environment Continuum Reports Suite Cause User group properties were incorrectly copied from the administrator user group to the user group used in this case. Resolution Enable all permissions for the user group attached to the user name that cannot run the reports.  Once reports have run successfully start locking down the necessary privileges in groups testing Continuum Reports between each phase.

Issue Forward and Log should not be selected under Recipient Configuration when Enhanced Alarm Logging and Enhanced Alarm Delivery is in effect. Environment Event Notification Duplicate alarms Cause When Enhanced Alarm Logging and Enhanced Alarm Delivery is in effect, the Forward and Log checkboxes should not be selected under Recipient Configuration . Resolution When Enhanced Alarm Logging and Enhanced Alarm Delivery is in place, the Log and Forward checkboxes under the event notifications Recipient Configuration should be unchecked.

Issue Unable to update VAS client configuration after initial setup using the Configuration Wizard.  The Configuration Wizard and Client Email Configuration selections remain unselected or grayed out. Environment I/A Series R2 Enterprise Server Vykon Alarm Service Client 2.4x Vykon Alarm Service Client  3.xx Cause For security reasons the Configuration Wizard and Client Email Configuration selections are only enabled (not grayed out) if the user is associated with the computer's Administrators group. Resolution Review the user accounts for the computer and make sure that the user name being used to login and operate the VAS client is associated with the computer's Administrators group. You may find that a local user needs to be added and used if the computer is part of a domain and IT does not allow that user to be a member of the Administrators group.

Issue I/A Series G3 Enterprise Network Server (ENS-1) oBix licensing Environment I/A Series G3 Enterprise Network Server oBix driver Cause Clarification on oBix licensing for the Enterprise Network Server and the use of the part numbers ENS-OBIX and ENS-OBIX-500.  Resolution When you purchase the Enterprise Network Server (ENS-1), the license includes the oBixDriver as standard*. This oBixDriver provides oBix client / server functions for connecting to Niagara based controllers or stations. Typically, these would be I/A Series R2 UNCs or Enterprise Servers.  The ENS-OBIX is used when you need to add Obix point support connecting devices that are NOT powered by Niagara. The ENS-OBIX includes support for 500 oBix points. Additional points are purchased in blocks of 500 using the part number ENS-OBIX-500.  * Standard features in ENS-1 are email, niagaraDriver (peer to peer communications), obixDriver (oBix client / server), provisioning, web, and workbench.

Issue Intermittent master / slave calendar and schedule operation between I/A Series R2 Enterprise Server and UNC.  Schedules do not appear follow or recalculate during holiday override conditions. Environment I/A Series R2, Enterprise Server, UNC Cause Master/slave schedule objects were used however the calendar object only links to the local schedule. Resolution Proper implementation of Enterprise Server to UNC master/slave calendar and schedule objects. Schedule: Master schedule objects reside in the Enterprise Server and slave schedule objects reside in UNC controller. Link the masterOut from a Enterprise Server Schedule object to the masterIn input of one or more UNC Schedule objects.  In case of a communications failure between devices, each UNC retains schedule configurations, as this data is persistently stored in all Schedule objects. Calendar: Master calendar objects reside in the Enterprise Server and slave calendar objects reside in UNC controller. Link the masterOut from a Enterprise Server calendar object to the masterIn input of one or more UNC calendar objects.  In case of a communications failure between devices, each UNC retains calendar configurations, as this data is persistently stored in all calendar objects. Linking: Linking of calendar to schedule ... link the local calendar's output to the local schedule's holiday override input (e.g. master calendar to master schedule or slave calendar to slave schedule).  The holiday override should not externally link across the network. In addition, a holiday schedule must not be left blank (no events), “assuming” inactive.  Otherwise, an output that is active upon transition to the holiday day will remain active.

Issue Fault Finding on an IC-SNP / IC3-SNP and associated IAC controllers. Product Line Satchwell MicroNet, Satchwell Sigma Environment IC-SNP IC3-SNP IAC Communications Cause How should testing be carried out where communications between an IC-SNP / IC3-SNP and IAC controllers is not possible. Resolution Overview  The purpose of this article is to advise of the methods and techniques available when fault finding on an IC-SNP SubLAN.  Using the Alarm Manager on the Sigma default/backup Server. The Alarm Manager is a valuable source of information when investigating a problem SubLAN. All system messages generated by the controller will be displayed here. Check system messages (priorities 22 – 30) from the appropriate controller. Unable to open gateway.txt file. This generally indicates that an error has been made in an entry in the gateway.txt file. When initially setting up the gateway.txt file add just one or two entries, as this cuts down the chances of making a mistake. Make sure the basic gateway.txt file is known to be good, or download it from Exchange-On-Line. If an error is reported, check the file for obvious mistakes, if none can be seen, then make a copy of the file. Working on the gateway.txt file, remove all entries, except for one. Download the file and then warm-start the controller. If the file is now processed correctly, then from the backup of gateway.txt, copy a small section of the entries back into the gateway.txt, download and warm-start again. Repeat this process until the problem is located.  Controller??? Is not responding  A specific controller is not communicating. Investigate the controller locally. Will the controller communicate with Visisat via a LIB-4-485 converter, are the LAN connections correctly connected, does the controller have power?  Multiple controllers reported as not responding  Dependent on the number of controllers involved, this may indicate a partial or total failure of the SubLAN. Investigation starting at the IC-SNP will be required.   Investigation at the IC-SNP  The SNP SubLAN, channel 2 should have its BIAS jumper position set to D, for full biasing. The 120-ohm, end of line termination resistors should be fitted. If the controller is warm-started, then shortly afterwards the channel 2 TX LED should be seen to start flashing. This proves that the gateway.txt file is being processed. If the channel 2 RX LED flashes, then the IC is receiving replies to its requests. If the channel 2 RX LED remains permanently on, then this suggests that an IAC controller communications driver is faulty, and is stopping the LAN communications – see below.  IC-SNP Retry Mechanism  Having completed a warm or cold-start, the IC-SNP will process the gateway.txt file. Assuming the file format is correct, then the IC-SNP will start to process the text entries. The IC-SNP will read each line of text in sequence and try to communicate with the appropriate IAC controller. If the IAC controller does not respond, then the IC-SNP will repeat the message three times before marking the IAC controller as off-line. It will also send an “Unable to Communicate with Controller ???” message to the default server. The IC-SNP will then try the next controller. Communications with the off-line controller is retried every 30 minutes, on the hour and half hour. Testing – IC-SNP channel 2 RX LED is permanently on. Try to assess the mid point of the LAN, and instigate a binary chop by separating the twisted pair comm’s at the nearest controller. Check the IC-SNP, RX LED. If the LED has gone off warm-start the IC-SNP: If communications restarts to the remaining controllers, it suggests that the fault must be in the section of the LAN beyond the mid point, and further investigation must be pursued from there. If the LED remains on, it indicates that a fault is still present between the IC-SNP and the mid point of the LAN. In both of the above cases, the next action is to split a section of the LAN into two again, to be working on either 25% of the twisted pair, or by adding the first half of the remaining LAN to be working on 75% of the whole LAN. Using a voltmeter set to DC volts, measure the voltage on each LAN cable. Communications cable +ve and the controller 0volt terminal Communications cable -ve and the controller 0volt terminal Communications +ve and the Communications -ve  Below are some example voltages, these are only as a guide, they will vary dependent on LAN conditions.  Communications cable +ve and the controller 0volt terminal             2.5 volts Communications cable -ve and the controller 0volt terminal               0.15 volts Communications +ve and Communications –ve                                                                     2.31 volts  When checking voltages, a minus value is a good indication that something is wrong. For example if testing at the 75% position, the fault could be in either direction. If when measuring the voltages, cable 1 gives a reading between +ve and –ve of 1.6 volts and cable 2 gives a reading of –2.4 volts, then cable 2 would be the cable to investigate further. The above process is continued until the faulty controller or controllers are located. Once it is believed that all problems have been resolved. The full gateway.txt file should be downloaded, and the IC-SNP should be warm started. Allow a few minutes and then check the Alarm manager for any new error messages. Testing – IC-SNP channel 2 RX LED gives no indication at all  Having warm-started the controller, channel 2 TX LED should be seen to start flashing. If at this stage channel 2 RX LED does not flash, then this suggests that there could be a problem with the IC-SNP, SNP SubLAN, or the controllers connected to it. At this stage there should be fair confidence that the IC itself is working correctly and therefore the controllers or the SubLAN would be suspect. The method for determining the problem will be the same in both cases. Identify the first controller on the SubLAN, and disconnect the twisted pair LAN going to the next controller at this point. Warm-start the IC and observe channel 2 RX LED to see if any flashing occurs. If communications with the controller is possible, then it will be necessary to proceed as in the previous examples, using the binary chop method to locate the problem. If the controller will does not communicate with the IC, then this could be a cable fault or the controller could be faulty. To test the cable, ensure that both cable ends are disconnected and that the cores are separated. Check the resistance between cores and each core to earth. All values should be infinity. And one cable end, short the cores together. At the other cable end, check the resistance between cores, should be almost zero, and each core to earth, should be infinity. To check the controller, connect to it using an LIB-4-485 converter and Visisat Engineering software.

Issue What can cause RAW alarms seen in alarm log? Environment Continuum error alarm log List View Cause The two most common reasons for seeing Raw Alarm Errors are... Alarms have been updated or deleted offline Continuum DB server is being overloaded. When this occurs, the alarm event coming off the wire gets dropped in the Raw alarm table to get its name and all other information rendered out into a readable format.  If the server is too backlogged the alarm could fall off the raw alarm table before the rendering is complete which in turn would generate the Raw Alarm error. Resolution If the alarm has been updated or deleted offline, reloading the controllers should remove these RAW alarm errors.  This will ensure the database is fully synchronized with the controllers. If there are indications that SQL is overburdened steps should be taken to address this issue.

Issue On a jobsite doing a backup of a GCM and its ASD controllers.  After an upload of the GCM is complete, the ASD controllers appear in the tree (the upload of the GCM created them).  Do they also need to be uploaded individually? Environment TreeTech (any version) Cause Understanding all the steps in a proper / complete upload of a GCM and its controllers. Resolution The first step is to upload the GCM. The second step is to upload each individual ASD controller (Microzone II, Microflo II, etc...).  Each upload will take less than a minute.

Issue A computer running UltiVist locked up and was rebooted.  Each reboot brings it right back to its locked up state.  How can this be prevented? Environment OS/2 UltiVist Cause A task or program does not execute properly and causes OS/2 to lock up with no response from keyboard or mouse. Resolution Boot up from the installation diskettes to gain access to a command prompt.  On the hard drive, modify the config.sys file to include the following lines: set restartobjects=startupfoldersonly set autostart=programs,tasklist,folders,warpcenter These lines will prevent the computer from running programs or tasks that lead to its locked up state.

Issue How to retrieve the XBuilder project (XPB) from the Vista Database. Environment XBuilder Xenta Server 913 Xenta Server 511 Xenta Server 7xx Cause  XBuilder file was not saved and backup was not set to target. Except Vista database backup do not have any other backups. Resolution To manually extract the XBuilder project from the Vista Database follow these steps: Using Windows Explorer navigate to the Vista database folder which has the XBuilder project you wish to extract. Open the $thisfil folder. You can see a zip folder named something like DE03xxxx.ZIP or similar.  Copy the zip file and paste it in the desired location. Unzip this file. The Zip contains the complete XBuilder project inside it.

Issue Cyberstation Online Help for Workstation editor Time Tab contains incorrect information. Environment Cyberstation online help Cause The highlighted text in the Workstation Time Tab online help is inaccurate.    Note: When entering this number, use the opposite sign (negative or positive) from what you actually want the system to write. For example, if you are 300 minutes (5 hours) ahead of GMT, enter: -300 For example, if you are -240 minutes (4 hours) behind GMT, enter: 240 Resolution Under UTC Offset, the Note should read as follows: Note: When entering this number, use an negative integer to specify time zones to the West (earlier than) Greenwich Mean time and a positive integer to specify time zones that are to the east of GMT. For example, if you are 300 minutes (5 hours) ahead of GMT, enter: -300 For example, if you are 240 minutes behind (later than) GMT, enter: 240 

Issue The R2 Enterprise server is running in a virtual environment. The station stops when the user logs off. Environment Niagara R2 Enterprise Server Cause The station’s App folder is over the recommended 500MB size. Resolution 1. Stop the station database 2. Locate the app folder under the station folder, and delete the app folder or rename it with ".old" suffix 3. Restart the station. The Cloudscape (app folder with file structure) will be automatically re-created. Note: All of the station's archives and logs are lost when deleting the App folder.  If the database’s archive needs to be save, then the app folder should be cut and save to the hard drive.  The saved station archives can then be viewed by placing the app folder in a new blank station    

Issue Where can I find the UL and CE certificates for our valves? Environment Valves Cause In some applications/installations, the UL or CE (depending on geographical region) is requested for the components used. Resolution The UL and CE certificates are only valid when electrical components are involved, such as actuators.

Issue Does the JACE-6E or JACE-7 support multiple FTT-10A LON cards? Environment JACE-6E, JACE-7, LON FTT-10A Cause Application requires multiple FTT-10A LON trunks. Resolution Yes ... the JACE-6E / JACE-7can support two individual FTT-10A cards.  Purchase (2) TRD-NPB-LON (FT-10A Lon Adapter cards) and (1) ENC-DRV-LON driver.  Add one LonNetwork for each physical port.  Under each LonNetwork within the Lon Comm Config, specify the port's Device Name (e.g. LON1 and LON2).  Reference the Niagara AX Lonworks Guide for more details.

Issue If the Automation Server (AS) starts up with its clock set to 1970, it is possible to create duplicate object Id's. Product Line EcoStruxure Building Operation Environment Automation Server, version 1.3.0.938 Cause If the clock in the AS is set before engineering the unit, the issue does not occur. However, if the clock is not set this problem occurs and the only was out is to re-engineer the AS. In addition, the BACnet interface will cease to function. Resolution This issue has been identified as a defect, and will be resolved in a future release.  In the meantime, be sure to configure the AS to the correct date and time prior to engineering the unit.

Issue Is Niagara G3 version 3.7 compatible with all the legacy drivers? Environment Niagara G3 Cause Sales request Resolution The ENC-520-2 can be installed with version 3.7 as well as any of the legacy drivers (ASD, GCM, DMS, MicroSmart).

Issue Doing a R2 to G3 oBIX integration.  The alarms in the R2 station have been successfully imported into the G3 station.  However, they are as 'normal' in the G3 Alarm Console when they are actually in alarm.  How can they be configured to change color? Environment Niagara G3 oBIX integrations (any version) Cause R2 native alarms are NOT oBIX 'Stateful Alarms', meaning there is no defined 'lifecycle' of an alarm event (unlike native G3 alarms). As a result, R2 imported alarms appear as "normal" (green alarm bell) source state events when routed to the G3 Alarm Console. Resolution Add native G3 alarming proxies to provide the red color of an alarm.

Issue What is an acceptable induced voltage on to I/Net signal terminals Environment I/net SCU Cause If you have 10V which is induced on to an input cable. And The installer ran 24Vac alongside signal wires in a multicore cable with a common screen. And  have a plan to eliminate the induced voltage by reducing the number of pairs carrying voltage and using other cables Resolution Of the input signal types, the Thermistor type is considered the most vulnerable to the pickup of stray voltage from sources in the local area. This is because the AI input is a high input impedance (as it is with all voltage measurement modes of operation), AND the signal source is also very high impedance (the 10K thermistor itself). With one side of the circuit grounded, this presents the 10K ohm impedance of the signal wire as a prime candidate for inducing AC voltage noise from and local adjacent AC voltage sources AND especially any such run in the same cable. There is no “acceptable limit” definition on such AC pickup. Acceptability is directly related to the system application and/or customer tolerance for fluctuations of temperature readings. In the room temperature range, a thermistor signal changes by only ~ 54mv for each degree C. Without filtering, this 54mv/C sensitivity would produce constant variation form small induced noise levels. We provide both hardware and software filtering on the analog signals that allows rejection of AC noise seen on the input terminal, BUT you still want to minimize the level of the noise pickup as seen on the analog inputs. In the I/NET controllers the hardware filter provides a 94/95 % reduction of the 50/60 hz AC noise level presented to the controller. The controller firmware follows with implementation of  deglitching and averaging filters that further reduce the effect of noise on the AI point value.  We also have a input filter technique specifically targeted at reducing the impact from AC line induced noise. That filter works on the principle of making the AI readings at a scan rate of 1.5 times the AC line frequency. This is the purpose of making the AC line frequency a configuration item (50 or 60 hz) in the CLAN controllers. On the SubLAN, this is scan rate is fixed at 25ms (1.5 times 60hz) which make the line frequency filter not as effective for 50hz, but still very helpful.   As the analog inputs are scanned, we capture a reading on the negative or positive cycle of the induced noise and then we average that with a reading taken from the opposing cycle of the induced AC noise as seen 25ms (or 20ms) away from the previous sample. The average of the positive and negative cycle of the induced noise creates a near complete cancelation of the induced error – for a sinusoidal wave noise signal. This technique does a great job of producing a notch filter centered on the AC line frequency and reducing/filtering the impact from such line frequency noise.   This combination of several filters allows you to see AC line induced noise on the analog input terminal, and still maintain a stable temperature reading in many cases.  Note -- If the AC noise is non-sinusoidal, due to anomalies in the noise transfer or originating from an AC source other than the sine wave AC power line, then the affectivity of the noise reduction will be reduced and signal reading impact will be larger. The 10V of induced voltage you describe is very large (huge) and far beyond anything I have seen, but then I have never seen 24VAC wired in the same cable with thermistor signals.  Separation of the 24VAC as you describe below is needed. Your described past tolerance for  5V is also above what I would expect to accept.   However, it is possible that the AC line frequency filter has been making such high noise level appear acceptable on the temperature reading display.   For possible work-around use, the high impedance of the thermistor source makes the addition of a capacitor on the AI terminal to ground very effective in reducing the applied voltage from AC noise pickup. Here a capacitor value in the range from 2 to possibly 100 micro-farads can sometimes be useful to reduce or work-around an installation wiring problem. The capacitor should be of the “Low Leakage” type.  Leakage in the capacitor would be exhibited as a small reduction in the DC voltage and associated increase in the temperature reading.  The higher the micro-farad capacitance value, the more reduction in noise you will achieve, but it is easier to obtain low leakage capacitors in the smaller capacitance values.  If polarized electrolytic capacitors are used, be sure to position the negative terminal toward ground.