Building Automation Knowledge Base

Issue How does Continuum calculate the average value when a point is configured with an Average LogType. Environment Log TrendI Infinity Controller NetController CX i2 TCX SCX Cause It is often important for the end user to know how log values are calculated in cases where trend log data may be audited. Resolution Point values are sampled stored and calculated at the controllers level, not at the Cyberstation level.  The point logging process is not dependent on the scan time of the controller and is therefore unaffected by a controllers scan time. The controller stores the most recent data polled as its data sample. The smallest interval that we can log data is 1 second.  Even when an average log type is selected, a log with a 1 second interval is essentially a non averaged log since each calculation would take one sample/second and divide it by interval in seconds (1). With points logged with an average log type at intervals that are > 1 second, each second the most recent data sample added to the summed value. The sample values are added together, (each new sample is added to the stored sample value) and the sum is divided by the number of samples taken (which would also equal the number of seconds in the log interval).  A controller calculates average point values using a weighted average algorithm at the end of the log interval period. A controller does not retain data samples when the log period ends, but rather it begins to assemble a completely new collection of sample data at the start of each interval period.

Issue What is the difference between SQL Server 2005 and SQL Express Edition. Environment SQL 2005 Cause Why would I need SQL Server instead of SQL Express. Resolution Limitations for SQL Express Edition are: CPU:  1   CPU RAM:   Maximum 1 Gig. Database Size:  Maximum  4 Gig.

Issue ENC is licensed for GCM but gets error "Unlicensed: javax.baja.license.FeatureNotLicensedException: tac_llc:tacgcm" when attempting to access the GCM Network property sheet. Environment I/A Series G3, ENC-520 with TAC-LLC license installed. Cause When displaying the I/A Series G3 Platform details via the Platform Administration screen in the Workbench, the display shows the following for licensing: Licenses   Tridium.license (Tridium 3.5 - never expires)   TAC_LLC.license (TAC_LLC 3.5 - never expires) Certificates   Tridium.certificate (Tridium - never expires) This information shows that the Tridium and TAC_LLC licenses have been installed but only the Tridium certificate. The TAC_LLC license will not be recognized unless the TAC_LLC.certificate is also installed (as shown in the following platform details display. Licenses   TAC_LLC.license (TAC_LLC 3.6 - never expires)  TAC.license (Tridium 3.6 - never expires)Certificates Tridium.certificate (Tridium - never expires)  TAC_LLC.certificate (TAC_LLC - never expires) Resolution There are two ways to resolve this issue depending on network connectivity of the G3 Workbench computer. If public ethernet connectivity is available, the licenses and certificates can be downloaded from the I/A Series G3 (Tridium) license server, using the Workbench "License Manager". Open Workbench and connect to the subject ENC. Open the Platform then select License Manager. In the License Manager, select [Import] then check "Import licenses from license server".  This process will download any available licenses for the selected device, along with any available certificates.  After the download is complete, the licenses and certificates downloaded will automatically be installed.  If public ethernet connectivity is not available or the certificate is not found, download the TAC_LLC certificate from The Exchange Download Center website.  Navigate to the I/A Series G3 (ENS, ENC, etc.) Conference > SE Proprietary Drivers.  Use Workbench to import the downloaded file.

Issue Workstation has had a number of its system variables renamed to names such as FanStatus and HHWV. These objects have also changed their Object Class to BACnet objects such as AnalogueValue.   Environment Continuum BACnet Cyberstation Cause This can occur when the Device Node ID of your Device object (Workstation) is the same as a BACnet devices BACnet ID. Resolution The best way to resolve this is to "cut out the bad bits" by deleting the BACnet device from the BACnet tree, the Workstation Device object, and Workstation Folder.   Perform the following: Backup the ContinuumDB. Backup any WS programs or other objects in the WS that you will require later. Export these to dump files. Export any graphics that reference your BACnet Devices.  Shut down all other Cyberstations. Delete the BACnet Device that is conflicting from the BACnet side of Continuum.  Delete the Workstation Device object and Workstation Folder. Shut down Continuum and then re-initialize the Workstation object into the database using a unique number for its BACnet ID (this is the Device Node ID). This number can be between 1 and 4194302, but must be unique in your entire BACnet network. Log-on and re-find the BACnet controller and import anything that you previously backed up in steps 2 and 3.

Issue Is IPv6 supported with I/Net and SE Vista Controllers? Environment NPR2000 Xenta 527-NPR, 527, 731, 913 Cause IPv6 with I/NET and Vista Controllers Resolution  I/NET and Vista Controllers DO NOT support IPv6

Issue Using Access Initiated Control to trigger an event sequence Environment I/NET Seven 7798 Cause Custom door applications sometimes require several steps to be initiated on a reader entry Resolution Create in Internal DO point (Point1) where 0 = off and 1 = ON, The scan interval should be shorted than the expected time between 2 card reads at the door. Add a Calculation to point1 that sets it equal to 0. [C0 where C0=0] Add an event extension to the point that triggers your desired event sequence on the specified state of ON Create an AIC that starts point1 on a reader Entry Create your event sequence with the desired programming. The effect should be that a reader entry causes Point1 to turn on triggering the event sequence

Issue Any objects created get placed in the folder Environment Continuum Windows XP Windows Vista Windows 7 Windows Server 2003 Windows Server 2008 Cause Selecting the checkbox for put object in folder and specifying a folder causing all objects to default to this folder.  Resolution By default, this checkbox isn't selected. To go back to normal functionality, uncheck the checkbox to 'put object in folder' and remove the specified folder. When this mistake is made, not one single point can be named the same in similar controllers that are under that NetController or BCX.  This can affect drag and drop also.

Issue Weather information provided through the weather module in I/A Series G3 is no longer updating. Product Line TAC IA Series Environment I/A Series G3 Enterprise Network Server ENC-410 ENC-520 Cause The National Weather Service hosts the data service used by the Niagara weather module's default provider, the "NWS Weather Provider". At some point during the week of September 26th, the National Weather Service moved the location of their forecasted weather conditions service.  No advanced warning of the change was provided. The error message encountered may include: WARNING [10:04:20 30-Sep-11 EDT][weather] Updating forecast failed for WeatherReport javax.baja.sys.BajaException: 404 Not Found at com.tridium.weather.nws.NwsForecastReader.getFeed(NwsForecastReader.java) at com.tridium.weather.nws.NwsForecastReader.getFeed(NwsForecastReader.java) at com.tridium.weather.nws.NwsForecastReader.getFeed(NwsForecastReader.java) at com.tridium.weather.nws.NwsForecastReader.getForecast(NwsForecastReader.java) at com.tridium.weather.nws.BNwsWeatherProvider.updateReport(BNwsWeatherProvider.java) at javax.baja.weather.BWeatherReport.doUpdateWeatherReport(BWeatherReport.java) at auto.javax_baja_weather_BWeatherReport.invoke(AutoGenerated) at com.tridium.sys.schema.ComponentSlotMap.invoke(ComponentSlotMap.java) at com.tridium.sys.engine.EngineUtil.doInvoke(EngineUtil.java) at javax.baja.sys.BComponent.doInvoke(BComponent.java) at javax.baja.util.Invocation.run(Invocation.java) at javax.baja.util.Worker.process(Worker.java) at javax.baja.util.Worker$Processor.run(Worker.java) at java.lang.Thread.run(Thread.java:823) Resolution The weather service has been updated in patched weather modules to use the new data service location.  A number of other enhancements have also been made to better detect this situation and attempt to automatically resolve the issue by better following the 'HTTP Moved Permanently' error response messages. This may help reduce the impact of future unannounced National Weather Service data service changes. Although some users may wish to work around this problem by making changes to hidden fields on the weather provider, this is not recommended because it leaves stations exposed problems resulting from future data feed changes. forecast server: graphical.weather.gov forecast path: /xml/sample_products/browser_interface/ndfdBrowserClientByDay.php The NWS has also deprecated the current condition feeds previous retrieved from the www.nws.noaa.gov servers. These are now being replaced by feeds made available at www.weather.gov.  The new patched weather module will automatically use the feeds at the new location. As a temporary workaround, the Nws Weather Provider's hidden slot "conditions server" can be modified with the new value "www.weather.gov". It is recommended that weather service users upgrade to the most recent weather module for their release.  The modules can be downloaded from The Exchange Download Center. weather-3.4.67.3 or higher weather-3.5.39.5 or higher weather-3.6.37.4 or higher

Issue ENC is licensed for Microsmart but gets error "Unlicensed: javax.baja.license.FeatureNotLicensedException: tac_llc:tacms" when attempting to access the Microsmart Network property sheet. Environment I/A Series G3, ENC-520 with TAC-LLC license installed. Cause When displaying the I/A Series G3 Platform details via the Platform Administration screen in the Workbench, the display shows the following for licensing: Licenses   Tridium.license (Tridium 3.5 - never expires)   TAC_LLC.license (TAC_LLC 3.5 - never expires) Certificates   Tridium.certificate (Tridium - never expires) This information shows that the Tridium and TAC_LLC licenses have been installed but only the Tridium certificate. The TAC_LLC license will not be recognized unless the TAC_LLC.certificate is also installed (as shown in the following platform details display. Licenses   TAC_LLC.license (TAC_LLC 3.6 - never expires)  TAC.license (Tridium 3.6 - never expires) Certificates   Tridium.certificate (Tridium - never expires)  TAC_LLC.certificate (TAC_LLC - never expires) Resolution There are two ways to resolve this issue depending on network connectivity of the G3 Workbench computer. If public ethernet connectivity is available, the licenses and certificates can be downloaded from the I/A Series G3 (Tridium) license server, using the Workbench "License Manager". Open Workbench and connect to the subject ENC. Open the Platform then select License Manager. In the License Manager, select [Import] then check "Import licenses from license server".  This process will download any available licenses for the selected device, along with any available certificates.  After the download is complete, the licenses and certificates downloaded will automatically be installed.  If public ethernet connectivity is not available or the certificate is not found, download the TAC_LLC certificate from The Exchange Download Center.  Use Workbench to import the downloaded file.

Issue When cold starting a controller, if the controller has a valid back store it will always receive the files from there and not request the files from the server. Environment Cold Start Backup Archive Cause When cold starting a controller, if the controller has a valid back store it will always receive the files from there and not request the files from the server. Resolution There are two options for this. Option 1 Using SDCU clear the controllers archive. The clear archive option can be accessed by selecting the advanced button on the SDCU's main screen. Option 2 Using Sigma System Diagnostics download the files from the server to the controller. Re-triggering the archive time schedule will add the new information to the controllers archive.

Issue  Temporary groups can't get a PM time, only AM Environment I/NET Cause The time are using US settings AM/PM on for example a European PC Windows don't use AM/PM Resolution Enter Control Panel and choose Regional and Language Settings On first tab click Customize Choose tab "Time"  Set AM and PM symbol to AM and PM Click OK Restart I/NET IO server and try again.

Issue How can the Niagara R2 UNC be setup to monitor DI1 and DI2 contacts status of the Viconics VT7600 Series Lon thermostat? Environment Niagara R2 UNC-410, UNC-520   Cause How can the Niagara R2 UNC be setup to monitor DI1 and DI2 contacts status of the Viconics VT7600 Series Lon thermostat? Resolution The DI status of the Viconics VT7600 Series thermostat can be accessed through its nvoSccStatus SNVT. The DynamicDemux (Demux) object will be used to expose the status of the DI inputs, as well as other thermostat status points, in the UNC. The Demux object allows for the various status points of the nvoSccStatus SNVT to be brought into the UNC individually as bits. The DI1 status is on bit18 and DI2 status is on bit17 of the VT7600 Series nvoSccStatus SNVT. The following steps need to be taken to expose the DI inputs in the UNC. It is assumed that the VT6000 shadow object is been commissioned in the UNC. Open the page containing the VT700 thermostat shadow object in Workspace Editor view. Open the /tridiumx/lonworks/conversion folder; copy and paste the DynamicDemux object to the Workspace. Right-click the VT7600 shadow object and select link, then select the DynamicDemux object. Select nvoSccStatus under the VT7600 column and then select link under DynamicDemux column. Click OK to save. You can now link the bits to objects you selected to monitor their status. DI1 is bit18 and DI2 is bit17 of the Demux object.  

Issue AMT message "Time-sync failed" Environment I/NET Seven AMT Cause The Time-sync failed message indicates that an attempt to sync time with a DCU has failed. Resolution Time synchronization is a function of DCU Synchronization. This is only intended for use with direct-connect, TCP/IP or AD/AA communication. If your site is using Integrated Dial or NPR Dial connection, this explains the alarm and must be deactivated. To View the systems DCU synchronization settings. Log into I/NET and select Edit>Host Computer>Network functions. From there you can select a link via a dropdown menu view the "Sync" setting for each controller. If Sync is enable on any controller that are offline or no longer exist, disable synchronization (and any other Host function)  If time sync is not desired, it can be disable which will also remove the alarm. If time DCU synchronization is desired, This is likely an indication of a communication failure. Determine if this has occurred on an entire Controller LAN or just a single controller. Use this as a starting point and work towards the PC looking for communication errors.  

Issue Average space temperature on TAC Xenta 120 devices. Product Line EcoStruxure Building Operation, TAC Vista Environment TAC Xenta 121-FC TAC Xenta 121-HP Cause TAC Xenta 121 is able to average space temperatures from multiple sensors. For example, it could average two room units, or one room unit and one Lon sensor. It is possible to average up to three different Lon sensors. Resolution Bind a valid temperature SNVT value to the input nviSpaceTemp. The TAC Xenta 120 device will calculate the average between the bound input and the physical sensor.

Issue When accessing the Webstation/Screenmate website a 404 Page not found error message is returned. Environment Windows Server 2003 Vista 5.x.x Cause The ASP.NET technology is currently prohibited on the Web Server. Resolution Open the Windows Control Panel Click the Administrative Tools Click Internet Information Services (IIS) Manager Expand the local computer Click Web Service Extensions Ensure that ASP.NET v 1.1.4322, ASP.NET v 2.0.50727, and ASP.NET v 4.0.30319 are allowed (Possible that only version 2.0.50727 is listed) Version 4.0.30319 is required for Vista versions 5.1.5 or higher.

Issue Are the batteries for the UNC-410 and UNC-520 interchangeable? Product Line TAC IA Series Environment I/A Series R2, UNC-410, UNC-510, UNC-520 Cause Replacement batteries are needed and compatibility between devices must be known. Resolution The batteries used in the UNC-410, UNC-510, and UNC-520 are the exact same and are interchangeable. The replacement part numbers UNC-400-BAT and UNC-500-BAT include the same battery.

Issue Provides additional setup information for the R2 ASD (IbsASD) driver. Environment R2 ASD (IbsASD) driver (all revisions) Cause The driver may not communicate correctly with the ASD devices if the driver has not been configured properly. Resolution IbsASD driver basic settings ... General / Engineering retryCount = 3 responseTimeout (sec) = 2 Poll / Config cycleTime (ms) = 333 times number of devices on the ASD bus, i.e., 3 devices per second. Comm / Config commPort = COM4, COM5, COM6 or COM7 depending on which port you are using maxBaudRate = 19200 ( or 9600 if PEM1 controllers exist on the ASD bus) DeviceStatus / Config deviceStatusPingDelay (ms) = 60000

Issue Meter Points, Pulse Points Frequency, Pulse Point Width. UNC496, UNC596, UNC696, UNC796 Pulse Point Location. Environment BAS, Sigma, 532, 632, x96 Cause What is the maximum pulse repetition rate and minimum pulse width of a pulse/meter point configured on a digital input. On a x96 controller, where can pulse points be configured. Resolution UNC532 - channels 1-2 object no's 81 - 82  repetition rate = 10 Hz , minimum pulse width of 50 milliseconds. Note if channels 3-10 object no's 83 - 90 are configured as pulse objects then the repetition rate = 0.5 Hz UNC632 - channels 1-10 object no's 81 - 90  repetition rate = 10 Hz , minimum pulse width of 50 milliseconds. UNCx96 (fitted with S-UNC-DI) - channels 1-16 object no's 81 - 96  repetition rate = 10 Hz , minimum pulse width of 50 milliseconds. Note: For x96 controllers, pulse objects can only be configured in slot 6 of the controller.

Issue The inputs and outputs from the remote I/O modules either show as NA or do not function properly. Environment MNB-1000 installations with MNB-1000-15 remote I/O modules Cause In this case the dip switches on the remote I/O modules were set to 2 and 3 incorrectly because it was assumed the MNB-1000 was address 1.  The MNB-1000's address relative to the remote I/0 modules is 0 and cannot be changed.  The remote I/O modules must be addressed 1 through 8.  Resolution Adjust the dip switch settings on each remote I/O module to address them from 1 up to 8.

Issue Can additional resources be added to an ENC-SW (Soft JACE) to increase the resources over the 30,000 KRu (30 Million) limit? Environment I/A Series G3, ENC-SW Cause Can additional resources be added to an ENC-SW (Soft JACE) to increase the resources over the 30,000 KRu (30 Million) limit? Resolution The I/A Series G3 Soft JACE can be initially purchased to support 10,000 KRu (10 Million) resources.  Additional resources can be added to the 10,000 KRu (10 Million) version to increase the total to 30,000 KRu (30 Million).  The maximum number of licensed resources per ENC-SW (Soft JACE) is 30,000 KRu (30 Million). ENC-SW-1M  >> Support for 10,000 KRu (10 Million) resources ENC-SW-2MU >> Upgrade ENC-SW-1M to increase total to 30,000 KRu (30 Million) resources