Building Automation Knowledge Base

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 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 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 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 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 In Niagara G3, how many stations can connect to one Enterprise Network Server? Environment Niagara G3 Cause Planning a large installation Resolution An Enterprise Network Server running on a 32-bit server can handle up to 150 stations. An Enterprise Network Server running on a 64-bit server can handle up to 500 stations.

Issue Customer has a Niagara R2 JACE-NXS (part # TRD-JACE-NXS-R2).  Can it be re-imaged with Niagara G3? Environment Niagara R2 Niagara G3 Cause Site was converted to Niagara G3 and the JACE-NXS is an expensive model that the customer would like to re-use on his G3 network. Resolution Since the JACE-NXS is a Tridium product, this request must be done through them. They must be contacted with each request since this service is no longer 'advertised' as being available. Send an email to orders@tridium.com and quote part number JACE-REIMAGE.

Issue Does Niagara G3 support or use the Service Location Protocol (SLP)? Environment Niagara G3 Cause Query made by an end customer Resolution No.  Niagara G3 is not aware of or uses the Service Location Protocol (SLP).

Issue Getting LON messages TException E_QUEUE_FULL {LonAsyncRequest} in the standard output window. Environment R2, Niagara, Lon Service Cause If also in the message there is a line that includes: "lonextras.control.PollSnvtTempSetptCmd.execute" these messages are being caused by the use of the special object from the LonExtras jar called PollSnvtTempSetptCmd.  Resolution When the station is booting up the PollSnvtTempSetptCmd object  will begin its polling function before the station has finished rebooting causing the queue to fill up before the station starts.  There is an object in the LonWorks jar - Conversion container called SnvtTempSetptCmd that will perform the same function as the PollSnvtTempSetptCmd except it does not poll which is not necessary in most cases.  Replace all PollSnvtTempSetptCmd objects in the station with the SnvtTempSetptCmd object.

Issue I/A Series MNL version 3 controller profiles are not shown in the list when adding a new LON device to a SmartStruxure Automation Server.  How do I add the template for one of those controllers to the Automation Server? Environment SmartStruxure 1.3 or newer Automation Server I/A Series MNL version 3 or earlier controllers. Cause Templates are not provided in SmartStruxure 1.3 for the older families of I/A Series MNL controllers Resolution Import a device template per StruxureWare Building Operation release 1.3 Technical Reference Guide section 40.14. This procedure is used any time the device template was not pre-defined or has not been imported into the AS. The templates for the older MNL family of controllers can be downloaded from the Download Center. You should also download the associated readme file so that you understand the arrangement of the files in the folders of the zip file. We suggest that you download and unzip the entire file to your computer using the folder structure contained in the zip file. The readme file lists the xif files contained in each of the xif folders. The xif files contained in the xif_40 folder are already contained in the SmartStruxure 1.3 system. When importing these templates into StruxureWare 1.3, you may get some warnings about SelfDoc strings and possibly errors about missing DRF types. Both issues can be ignored. If errors are reported regarding missing DRF types, click the [No] button to continue the import process.   After importing the template, you can then create the device under the LonWorks network as defined in the StruxureWare Building Operation Technical Reference Guide section 40.2. The template that you imported will be listed based on the name and profile of the device. You can assign a name of your choice (or use the default) for the created device. After device NeuronID or using the service pin process to send it from the controller, you then commission the added device. You should select the option "Keep current configuration in the device". Do not check the "Device application file" because the I/A Series MNL controllers do not use loadable executable files.

Issue Can the Alarm Console in Niagara R2 be configured with different sound files when annunciating an alarm? Environment Niagara R2 Cause End customer query Resolution The alarm console cannot be configured with sound files.  It comes with a very basic alarm tone which can be set to 'continuous' or 'once every so often'.

Issue The UNC and Enterprise server, as well as many other Schneider-Electric Buildings products, use a TIME protocol server to provide clock synchronization. The address of that Time Protocol Server no longer works. NOTE: The nist.gov sites will no longer be providing TIME protocol services over TCP port 37 as of March 1, 2013. Product Line Andover Continuum, Satchwell MicroNet, Satchwell Sigma, TAC IA Series, TAC INET, TAC Vista Environment Schneider Electric Buildings products that rely on the use of TCP TIME protocol servers for time synchronization. This includes the I/A Series R2 UNC & ES and the I/A Series G3 ENC & ENS as well as other IP ethernet based products. Cause Many server sites are discontinuing support for the TCP TIME protocol because it is so bandwidth intensive. NOTE: The nist.gov sites will no longer be providing TIME protocol services over TCP port 37 as of March 1, 2013. The site http://tf.nist.gov/tf-cgi/servers.cgi lists most of the currently available TIME protocol servers as well as the status of the entire TIME protocol system. Resolution If the product supports the use of the NTP time sync protocol, switch to the use of that protocol. If the device only supports the TIME protocol, consult the web site http://tf.nist.gov/tf-cgi/servers.cgi for currently available sites.

Issue Error "Job Failed  java.lang.NoSuchMethodError: com/tridium/install/BDaemonPlatform.getNiagaraR2Enabled()Z" when attempting to perform an I/A Series G3 Station Backup in version 3.6.31 after having installed the August 2012 security updates. Environment I/A Series G3 JACE or ENC with release 3.6.31 and security patches 3.6.47 installed. Cause Internal software error in the backup.jar file, version 3.6.47.2 Resolution Remove the backup.jar file, version 3.6.47.2 from the modules folder on the I/A Series G3 WorkBench computer. Remove the file backup.jar from the \niagara\niagara-3.6.31\sw\3.6.47.2 folder. Verify that the original 3.6.31 backup.jar file is in the  \niagara\niagara-3.6.31\modules folder.  Note that when replacing the backup.jar file, the 3.6.47.2 file should be renamed so that it can be restored later. Open the 3.6.31 Workbench and open the platform of the ENC / JACE. Run the Software Manager and note that a newer version of the is shown as installed as compared to the avail. version. Select the "backup" module by clicking on it then click the [Downgrade] button then click the [Commit] button. Acknowledge the warning that a reboot will be required by clicking the [Yes] button. Wait for the module commit process to complete, the station to reboot and restart. After the station has restarted you can log into the Station through Workbench and perform the backup to a .dist file using the standard station backup procedure (by right-clicking on the station name and selecting "Backup Station").

Issue The descriptions of the MN-S and MN-S1 sensors both state that they are temperature sensor only, what is the difference? Environment MN-S MN-S1 MN-Sx Micronet 2000 I/A Series Micronet Cause The part number descriptions of the MN-S and MN-S1 sensors both state that they are sensor only, what is the difference? Part # MN-S Description: MicroNet 2000 Wall Temperature Sensor with Temperature Sensor Only          Part # MN-S1 Description: I/A Series Micronet S-Link Sensor Assembly Providing Temperature Only.   Resolution While physically and functionally similar the two sensor belong to different product families and are not interchangeable since they utilize different communications protocols. The MN-S communicating sensor is compatible with the Micronet 2000 product family and is used with MN-FLO, MN-FLO3T, MN-HPFC controllers that use U bus communication protocol for sensor data. The MN-S1  communicating sensor is compatible with the I/A Series Micronet  product families and is used with MNL and MNB range of controllers that use S-Link communication protocol for sensor data.

Issue A sensor connected to a DMS system displays the letters INH to the right of the real-time display.  What does this mean and how can it be removed? Environment DMS Cause It is unknown how the INH appeared on the point.  There are at least three ways to do it with programming but none were found in the database. The INH is short for 'inhibit'.  It prevents a point from generating alarms or changing conditions even though an alarm or change of condition exists.  It is useful during times when maintenance is being done on the associated HVAC system or if the HVAC system is scheduled off.  It prevents nuisance alarms. Sometimes it gets applied after a database glitch during a loss of power or communications.  This situation is rare but it can occur. Resolution To remove the INH and allow the sensor to alarm and change condition, it must receive the ENINH command.  There are several ways to apply the ENINH command.  The quickest way is to use command mode. In OPRIF, - use the up and down arrow keys to highlight the sensor with the INH applied to it. - press F8 to enter command mode - type ENINH then enter - press F8 to exit command mode - allow OPRIF a few seconds to update and refresh the sensor on the screen

Issue Upgrading an end customer copy of WorkPlace Tech from version 5.8.1 to 5.8.2. Is there a charge for it? Environment WorkPlace Tech Cause Cost estimating for end customer's system upgrade Resolution There is no charge when upgrading WorkPlace Tech from 5.8.x to 5.8.y. Charges apply when upgrading WorkPlace Tech 5.7.x to 5.8.x.