Building Automation Knowledge Base

Issue The lib-2.301.532.v1.jar file is missing objects that were present in previous builds.  Here is list of those objects: lib\programObjects\hvac\RemainingOverrideTime.sns lib\programObjects\hvac\StartupInhibitor.sns lib\programObjects\hvac\TriStateOutput.sns lib\programObjects\lon\BooleansToMfgNvTypeBits.sns lib\programObjects\lon\BooleansToSnvtStateTypeBits.sns lib\programObjects\lon\FloatToSnvtHvacModeEnum.sns lib\programObjects\lon\MfgNvTypeBitsToBooleans.sns lib\programObjects\lon\SnvtLevDiscEnumTransposition.sns lib\programObjects\lon\SnvtStateTypeBitsToBooleans.sns lib\programObjects\lonHoneywell\XL15AnvoFTStatusDemux.sns lib\programObjects\lonHoneywell\XL15AnvoLogicOutputDemux.sns lib\programObjects\lonHoneywell\XL15AnvoStStpStatusDemux.sns lib\programObjects\miscellaneous\MinMaxAvg.sns lib\programObjects\miscellaneous\NumberRamp.sns lib\programObjects\miscellaneous\PulseGenerator.sns lib\programObjects\miscellaneous\WatchdogTimer.sns lib\programObjects\muxDemux\DateTimeDiscreteComponents.sns lib\programObjects\muxDemux\ExtractTextSegment.sns lib\programObjects\muxDemux\ParseString.sns Environment Niagara R2 version 532 Cause A compiling error with the jar file. Resolution This error has been corrected in a new 'lib' jar file: lib-2.301.533.v1.zip.

Issue Getting the error message “Can not access controller” when downloading to an MNB-300 controller with WorkPlace Tech 5.7.7. Environment WorkPlace Tech 5.7.7 Cause Corrupt database Resolution   Use backup copy of application or create a new application.

Issue Unable to successfully use Gmail SMTP server to send out alarms via email from I/A Series G3.  Various errors can be seen in the console output. Some of the errors are indicated below but they may not be limited to these. Error: BOutgoingAccount could not dequeue persistent email: 550 The address is not valid java.lang.Exception: Valid CryptoService not found Environment Enterprise Network Server / Enterprise Network Controller I/A Series G3 version 3.5 and above I/A Series G3 maintenance builds version 3.4.55 and above Cause Improper configuration of the EmailService's OutgoingAccount and missing CryptoService in the station. Resolution Procedure and properties settings required when using the Gmail SMTP Server: Add the EmailService and CryptoService to the station's Services folder. If emails are to be sent from an ENC, ensure that the email and crypto modules (and their dependencies) are installed into the ENC. Add the OutgoingAccount to the EmailService. In the OutgoingAccount properties, configure the properties indicated below. Leave other properties as their default settings. Hostname: smtp.gmail.com Port: 465 (this is the TCP port SMTP over SSL uses) Account: example@gmail.com Password: Your Gmail account password Enabled: true Use Ssl: true (Gmail requires SSL) Transport: SMTP Use Authentication: true (Gmail requires authentication when sending out emails) You can test the functionality by right-clicking on the EmailService and selecting 'Actions' > 'Send' to send out an email. If you are still having an issue with authentication, it may need to allow less secure apps to access your Gmail account. Refer to https://support.google.com/accounts/answer/6010255?hl=en for details.  Notes: CryptoService enables the SSL feature in the G3 station. The crypto module is included in the installation of I/A Series G3 version 3.6 but it was not included in earlier versions. You can download the crypto modules for earlier versions of G3 (crypto 3.4.64 / crypto 3.5.34) from The Exchange Download Center. Ensure that the station is licensed for crypto. You can look into your license file to check. Below is an example taken from a demo license. feature expiration="2012-03-31" name="crypto" parts="ENS-DEMO" ssl="true"

Issue Getting “Lost Sync with system clock - resetting control engine” warnings messages in R2 Enterprise Server? Environment Niagara R2, Enterprise Server, UNC-520, UNC-410 Cause The cause could be any one or a combination of several things listed in the resolution. Resolution The following settings should be verified in both the UNC and Enterprise Server. The following settings are for the Enterprise Server (ES): serverEnabled = true if syncing with UNC. clientEnabled = true if the ES is getting its time from an internet time sync server or site’s server. If not, clientEnabled= false. clientResetTolerance: the default is 30 sec with is too tight. Set it for a minute or more. (Remember to enter value as seconds, not minutes.) timeProtocolServer*: If clientEnabled = True, then all three slots should contain an address of a time sync server. If only one server is being used, then all three slots should be filled in with the one time sync server (same server). No slot should be left blank.   UNCs TimeSyncService settings: serverEnabled = false clientEnabled = true clientResetTolerance: the same would apply as the server timeProtocolServer*: the same would apply as the server reboot the UNC after any changes.

Issue I/A Series R2 (Niagara) Enterprise Server displays "ERROR: Cannot subscribe: Invalid node : (specifies node)". Environment I/A Series R2 (Niagara) Enterprise Server, all versions. Cause These errors are related to invalid subscriptions (swids) typically caused by changing the parent container or object name on the UNC without deleting and recreating the associated external link. The swid name changed but the external link is still referencing the invalid swid.   Resolution Review the links specified in the error message(s) and correct them.

Issue If a database is downloaded to the controller after the box has been balance will it lose the balance data? Product Line TAC IA Series Environment All versions of MNB VAV controllers MNB-V1 MNB-V2 Cause In MNB VAV controllers the flow balance data is preserved in a different area of EEPROM than the application data. Resolution Balance data in an MNB VAV controller is not affected by the downloading of its database.

Issue Cannot ping the MNB-1000 to test network connectivity.  Looking for an alternative method of network diagnostics, possibly by use of the second Ethernet port on the MNB-1000. Environment MNB-1000 (firmware 1.510 and later) Also can be used, but not required, with earlier firmware versions. Cause All Ethernet functions except for BACnet UDP messaging and router management functions has been disabled in the MNB-1000 firmware versions 1.510 and newer.  This prevents the use of Ethernet ICMP messaging (PING command, etc.) for diagnosing the Ethernet connection to the MNB-1000 controller. Resolution A computer can be plugged into the second (lower) Ethernet port on the MNB-1000 to allow network troubleshooting, device configuration and programming.  Plugging in a computer into the second port and assigning it an address on the same subnet as the MNB-1000, you can then ping other devices on the network to verify outgoing network connectivity.  Since the ICMP messaging has been disabled in the MNB-1000 itself, you can also ping the computer on port 2 from other computers on the Ethernet network to verify incoming connectivity.  NOTE: When performing troubleshooting in this manner, you need to remember that the MNB-1000 itself still will not respond to PING commands but will pass the ping commands and all other Ethernet or IP messages through to the second ethernet port. 

Issue Does Niagara G3 provide a way of importing existing ENC PxViews into an ENS?  Environment Niagara G3 version 3.5 or later Cause Importing existing ENC PxViews into an ENS is a time saving process. Resolution Niagara G3 does provide a way of importing existing ENC PxViews into the ENS with the use of exportTags, specifically PxViewTags. Open the exportTags in the Palette Drag and drop the SupervisorExportTagNetworkExt to the NiagaraNetwork of the ENS (server). Drag and drop the SubordinateExportTagNetworkExt to the NiagaraNetwork of the ENC. Enable the joinProfile in ENC: Expand the NiagaraNetwork of the ENC  Expand the ENS’ station. Double-click on the Join Profile and select Enable - Save. Setup the ENC’s PxViex File Structure: Expand Files Folder in the ENC and then expand joinProfile Expand ENS_profile.bog file and then expand niagaraStation Double-click the Points folder (The ENC’s PxViews will be setup here) Right-click in the ViewPane and select New Folder You may want to give the folder the same name as the PxView being exported The Folder structure should be the same PxViex folder structure as in the ENC’s PxView structure. Add folder for each PxView to be exported to the ENS Right-click on ENS_profile.bog and Save. Placing PxViewTags in PxViews PxViewTags are placed in each PxView being exported to the ENS. From the Palette, open exportTags and expand the Extensions folder Drag and drop a PxViewTag into the ENC’s PxView folder to be exported Configure each PxView’s Property sheet to point to the folders you created under Points in the ENS_profile.bog file. Double-click on the PxViewTag to set its properties For Supervisor Station, select ENS from the drop-down menu. - Save For Station Slot Path, click on the folder to display the “Select Parent Target” window. Expand NiagaraStation and then expand Points.  Select the corresponding PxView Folder and click OK For Px View, select the PxView to be displayed Click Save to save changes. Repeat steps for each PxView being exported to the ENS Do a Join to export PxView to ENS Once the above is setup a join can be performed.  A join can be accomplished in two ways. Join #1 Expand the NiagaraNetwork of the ENC Right-click on SubordinateExportTagNetworkExt, select Actions and then Join Join #2 Expand the NiagaraNetwork of the ENC and expand the ENS station Right-click on Join Profile, select Actions and then Join If everything was configured correctly, messages stating that both the Supervisor and Subordinate joins were successful will be displayed. If all goes well, then the ENC’s PxViews should appear in the Point folder of ENC under the ENS’ NiagaraNetwork. Notes: There were no provisions for importing the nav file during development of the exportTags. The file structure will also change once the ENC station.bog file is loaded on the Supervisor. For more detailed information on PxViewTags reference the NiagaraAX Export Tags Technical Document. This document is located in docs folder of the Niagara build root directory.

Issue SMS messages for alarms stop being sent after functioning for a period of time. The messages are stuck in the queue which can be seen in the SmsService's 'Queue Size' property. Messages in the queue are sent when the GSM modem is reset (power cycle). Problem will reoccur again after a period of operation. Environment I/A Series G3 Enterprise Network Server Cause The GSM modem appears not to be able to handle the messages being sent from the I/A Series G3 SmsService. Resolution In the SmsService properties, increase the 'Inter Message Delay' time. In this particular case, the delay has been increased to 1 second. The 'Inter Message Delay' is defined as: The delay between each command send to the GSM modem. By default this is set to zero. However, some older GSM modems may require this to be increased if there are problems with communication.

Issue ENC is licensed for ASD but gets error "Unlicensed: javax.baja.license.FeatureNotLicensedException: tac_llc:tacasd" when attempting to access the ASD 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.6 - never expires) TAC_LLC.license (TAC_LLC 3.6 - 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   Tridium.license (Tridium 3.6 - never expires)   TAC_LLC.license (TAC_LLC 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. If you have previously installed the TAC_LLC.certificate in any other version of the G3 software, you can import that certificate into the version you are currently running. Open Workbench and connect to the subject ENC. Open the Platform then select License Manager. In the License Manager, select [Import] under the certificate section of the window. Browse to the "certificates" folder under any other G3 installation folder and locate the TAC_LLC.certificate file.  If the file is not found, check the "certificates" folder of another G3 folder.  Click on the TAC_LLC.certificate file name then click [OK]. The certificate will automatically be copied and installed.   If public ethernet connectivity is 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 The message "Could not invoke the command "New"" is displayed when attempting to right-click in the Drivers View Pane and add a BACnetNetwork. Also, the message "Cannot perform the drop" is displayed when attempting to drag and drop a BACnetNetwork driver from the Palette into the Drivers folder. Environment Niagara G3, Enterprise Network Sever, ENC-520, ENC-410 Cause NA Resolution Uninstall WorkBench Delete remaining folders and files from Niagara build directory Reinstall WorkBench

Issue The following error messages are displayed in the Application Director output windows when attempting to add additional histories to a existing SQL database. javax.baja.sys.BajaRuntimeException at javax.baja.rdb.history.BRdbmsHistoryExport.insertMetaRecord(BRdbmsHistoryExport.java:679) at javax.baja.rdb.history.BRdbmsHistoryExport.exportRecords(BRdbmsHistoryExport.java:279) at javax.baja.rdb.history.BRdbmsHistoryExport.doExecute(BRdbmsHistoryExport.java:202) at auto.com_tridium_rdb_sqlserver_history_BSqlServerHistoryExport.invoke(AutoGenerated) at com.tridium.sys.schema.ComponentSlotMap.invoke(ComponentSlotMap.java:1232) at com.tridium.sys.engine.EngineUtil.doInvoke(EngineUtil.java:49) at javax.baja.sys.BComponent.doInvoke(BComponent.java:1050) at javax.baja.util.Invocation.run(Invocation.java:46) at javax.baja.util.ThreadPoolWorker$WorkerThread.run(ThreadPoolWorker.java:266) Caused by: java.sql.BatchUpdateException: Invalid column name 'INTERVAL_'. at net.sourceforge.jtds.jdbc.JtdsStatement.executeBatch(JtdsStatement.java:944) at org.apache.commons.dbcp.DelegatingStatement.executeBatch(DelegatingStatement.java:297) at javax.baja.rdb.history.BRdbmsHistoryExport.insertMetaRecord(BRdbmsHistoryExport.java:673) ... 8 more Environment G3 Niagara, 3.4 and later, SQL Cause The term INTERVAL was a keyword in some SQL dialects, so the column name was changed from INTERVAL to INTERVAL_ in the database schema. The database schema changed between 3.3 and 3.4. Resolution The following changes needed to be made to the SQL database. Altered the existing HISTORY_CONFIG table in the SQL database to change the column to INTERVAL_. Altered the HISTORY_CONFIG table, added a column called SYSTEMTAGS, set up as VARCHAR(500). Changed SOURCE column length to VARCHAR(500) in the HISTORY_CONFIG table  

Issue Need to replace the GCMA-136-2 repeater circuit board. Environment Network 8000 devices on an RS-485 bus (ASD, LCM, or GCS) with fiber-optic repeater(s). Cause Failure of the repeater. Resolution The GCMA-136-2 printed circuit board is the major component of the fiber optic repeater RPTR-FIBER. It is not available separately. Order the RPTR-FIBER to replace the complete repeater.

Issue When installing UltiVist on a new OS/2 computer, it fails to begin stating there's not enough space on c: drive.  However, c: drive has plenty of free space. Pop-up error message reads as follows: Setup is unable to copy the installation support file a:\~ins0762.lib to a temporary location.  Error 420 Environment UltiVist Cause The primary partition size is an issue for UltiVist. OS/2 can support partition sizes greater than 2 gigabytes if HPFS is selected over FAT.  UltiVist will NOT support a primary partition size of 2 gigabytes or greater and, as a result, it will think that there's insufficient capacity for writing data to the partition. To confirm, open a Win-OS/2 window, go to file manager, and check the drive space.  If a partition of greater than 2 gigabytes has been created, the available drive space will display as zero. Resolution Create a primary partition size of 1.99 gigabytes.  It can be HPFS or FAT. Best practice:  Install only OS/2 on the primary partition.  Install UltiVist on an extended partition (typically d: drive).

Issue A Network 8000 LCM-84x10 or LCM-88x10 will be integrated with a Niagara R2 UNC.  What firmware revision level must the LCM have for proper operation? Environment Network 8000 LCM Niagara R2 UNC-520 Cause The integration requires the LCM to have at least Year 2000 firmware installed.  The shadow objects in the Niagara station will not update or function properly. Resolution Upgrade the LCM using EPROM kit # LCMA-138-54. This kit is to be used with the LCM-84x10 or LCM-88x10 and it will upgrade the firmware level to 5.4, Year 2000 compliancy. It is available for purchase via iPortal.

Issue Getting the message “Cannot display page” and “Access Denied: Remote host does not accept brand “Webs”” while trying to access the Platform of an ENC-520 with Niagara G3 WorkBench. Environment G3 Niagara all version, ENC-410, ENC-520 Cause Honeywell WEBs (Honeywell’s version of Ax) on the same PC as Niagara G3. WEBS was installed and licensed first. G3 was installed after WEBs, but never licensed. Since a license for G3 was never obtained, G3 was attempting to use the Honeywell license to connect to the ENC-520. This results in a license brand incompatibility. Resolution The Niagara G3 WorkBench has to be licensed to connect to an ENC.   All TIP and end customer Niagara G3 / R2 license requests are emailed to:IASeries.License@buildings.schneider-electric.com  

Issue How can the entire I/A Series R2 Error Log or Audit Log (or any other log) be saved to a text file? Environment I/A Series R2 system, any release 2.15 or later Cause Many times, the issue being researched by use of the log extends over several screens of log entries. It is usually easier to review the data by looking at text format output instead of several screen captures. Resolution Access the UNC or Enterprise Server via web browser using the address "http: < ipaddress > /log/index" where < ipaddress > is the IP address of the UNC or Enterprise Server.  After logging in with the station user name and password, the following is displayed: Log Index ErrorLogService text/comma-separated-values text/tab-separated-values text/plain text/xml application/x-tridium-datax text/html AuditLogService text/comma-separated-values text/tab-separated-values text/plain text/xml application/x-tridium-datax text/html This table shows two logs, the "ErrorLogService" and the "AuditLogService".  Any additional logs created in the device will also be listed in the table.  By clicking the desired display format, the entire contents of the selected log will be displayed in the web browser screen.  The log output can then be saved to a file using the File / Save As function of the web browser, specifying a text file.  For example, selecting "text/plain" for the "ErrorLogService" will generate a file similar to the following: 2011-04-15T09:22:19.59-5,MESSAGE,/LON_BACnet_522services/ErrorLogService,ErrorLogService installed, 2011-04-15T09:22:38.89-5,MESSAGE,/LON_BACnet_522,Station started successfully. (HTTP port=80), 2011-04-15T09:42:32.09-5,WARNING,/LON_BACnet_522/services/ControlEngineService,Lost sync with system clock - resetting control engine., 2011-04-15T09:26:45.19-5,WARNING,/LON_BACnet_522/services/ControlEngineService,Lost sync with system clock - resetting control engine., 2011-04-16T21:35:33.28-5,WARNING,/LON_BACnet_522,Lost power shutdown, 2011-04-18T08:04:15.29-5,MESSAGE,/LON_BACnet_522services/ErrorLogService,ErrorLogService installed, 2011-04-18T08:04:34.48-5,MESSAGE,/LON_BACnet_522,Station started successfully. (HTTP port=80),

Issue Can the 30 day demo period of an expired I/A WorkPlace Tech demo license be extended? Environment WorkPlace Tech 5.x Cause The 30 day demo period has expired. Resolution The utility called WIBDemoExtender.exe allows the WIB suite demo period to be reset. The WIBExtender is used for WorkPlace Tech 5.6 or older. The utility can not be used with version of WorkPlace Tech 5.7 and newer. Currently there is no provision for extending the demo period of WorkPlace Tech version 5.7 or newer.  To prevent abuse of the demo mode extension, the program will extend the demo period for a duration of half the previous demo period from the current date.

Issue Do the universal inputs (UI) of the MNB-1000 support pulse inputs? Product Line TAC IA Series Environment MNB-1000 Cause Attempting to wire a pulse input to a UI on the MNB-1000 can cause issues. Resolution The UI inputs of the MNB-1000 do not support pulse inputs and can not be used for this purpose.  The digital inputs (DI) of a MNB-1000 do support pulse inputs. Pulse Input Rate Minimum rate of 1 pulse per 4 minutes Maximum rate of 10 pulses per second  

Issue The Remote stations name in the tree does not match the Remote stations name in the Admin Tool. How can the Remote station name in the tree be changed to match that of the Remote station name in the Admin Tool? Environment R2 Niagara, all versions Cause The station name was changed after it was initially created. Resolution The stations name will have to be changed in its XML file. An XML editor will be required for this. The most recent copy of the station’s XML file should be used. Open the XML file in an XML editor. Use the editor’s Replace function to ensure that all station names are found and replaced. For Find What: Type in the station name to be replaced For Replace with: Type in the replacement station name Save the XML file once the replacement is complete. Install the XML file to the Remote station. The station name in the tree and Admin Tool should now match.