Building Automation Knowledge Base

Issue Feature overview and tested platforms, operating systems, databases, and web browsers for AX/G3 version 3.8. Product Line TAC IA Series Environment Niagara AX / G3 3.8 Cause Field inquiries Resolution View the PDF files below.  They were obtained from Niagara-Central.com.  Feature Overview Test Summary Windows 8.1 is also supported (not listed in the Test Summary).

Issue WorkPlace Tech revision 5.7.7 installed on a Windows Server 2003, 64-bit machine, receives the following error: Environment WorkPlace Tech Tool version 5.7.7 Windows 2003 Server, 32 bit or 64-bit Windows 2008 Server, 32 bit or 64 bit (multiple processors) Cause WorkPlace Tech Tool (WPT) is not supported on computers with Windows Server operating systems, nor on computers with 64-bit operating systems. Resolution Install on an approved hardware platform, per the Installation Instructions.

Issue Allowing write access from BACnet Product Line TAC IA Series Environment I/A Series G3 BACnet Integration Cause By default, the BACnet driver provides external BACnet (client) devices "read access" to all exposed (exported to BACnet) objects in the station. Access depends on a station user named "BACnet." If this user does not already exist in the station, the Bacnet driver automatically creates it, upon startup. The BACnet user is initially created without any permissions. Resolution See below which is extracted from the Niagara Ax BACnet Guide: To allow any external writes (from BACnet) to properties of exported components, including invoking commands (actions), you must assign the BACnet user the necessary permissions to those components. For example, to allow an invoked "Active" action from BACnet to an exported BooleanWritable, in addition to making it "BACnet Writable" at priority level 8 when exporting, you must configure the station’s BACnet user to have operator write permissions on that BooleanWritable, at a minimum. Or, if an exported NumericWritable has an alarm extension, and you want to permit external BACnet writes to its "alarm limit" values, configure the BACnet user to have admin write permissions on the exported NumericWritable. In either example, to allow an external BACnet write to a property like "Out Of Service" or "Notify Type," you must give the BACnet user admin write permissions on the BACnet export descriptors. For details about station user security, see "About Security" in the User Guide. Note: BACnet user permissions also apply to writes of any exported files and histories. Also, note that while a password for the BACnet user is technically not needed (for external BACnet access), you should assign one anyway, because of the write permissions typically assigned. Make it a "non-blank" password, and guard this password carefully.

Issue What NEMA or IP rating is a specific product? Environment All devices Cause Is a product protected against water and access by foreign objects? Resolution The Degrees Of Protection document details both the IP rating and NEMA Enclosure charts. The IP rating is made up of 2 digits, the first is the level of protection to foreign objects, the second is the level of protection to water. If a product does not specify any rating for water ingress in it's datasheet then the the second digit will be 0. The first digit relates to the size of a foreign object that can be inserted into the product. Typically many Buildings products will not allow the insertion of a finger (12.5mm approx' 1/2") and offer no water protection, so they would be rated as IP20, however it would be IP10 should they have holes of up to 50mm (approx' 2").

Issue Can the old Robertshaw T99 temperature sensors be integrated to SBO? Product Line EcoStruxure Building Operation, TAC IA Series Environment SBO all versions Cause Retrofit job installation Resolution According to the RTD-DI-16 specification sheet, the T99 sensor can be integrated to SBO as follows with some limitations. Configuration Use an RTD-DI-16 module with a 2 or 3 wire RTD resistive input. Select 1000 ohm for the Sensor class property of the RTD input object. Configure the Conversion Settings properties of the RTD input object near the endpoints of the temperature range to be measured using values from the T99 temperature/resistance table. Configure the remaining properties of the RTD input as needed. Limitations Input Range. An RTD-DI-16 input configured for 1000 ohm operation is limited to an input resistance range of 500 to 2200 ohms. This will limit the temperature range that can be measured with a T99 sensor to ~115 deg. F maximum. Linearity Error. Depending on the range of temperatures to be measured and the needs of the application, linearity error may be significant. This can be corrected by using a script or function block program to linearize the signal based on the T99 temperature/resistance table values.

Issue After upgrading to Niagara G3 3.8 (from 3.7), nested PxIncludes now only partially load and very slowly.  They are not all entirely missing.  After a screen refresh, most will load except for a random few.  Also, they may load all at one moment but not the next.  The same Px file in version 3.7 loads faster with nothing missing. Environment Niagara G3 / AX version 3.8 Cause PxInclude caching is disabled by default in 3.8. Resolution This issue was addressed with the release of an updated bajaui module - version 3.8.38.3.  This version re-enables PxInclude caching.  Download it here.

Issue Information on the MicroSmart Laptop Interface Module (MSC-LIM) Environment DMS MicroSmart Cause Information Resolution Installation / Connection sheet

Issue Robertshaw T99-112 RTD Immersion Temperature Sensor - Specification Sheet & Temperature / Resistance Table Environment DMS MicroSmart Cause Create a custom temperature / resistance object in Niagara, SBO, etc... Resolution Spec & T/R table available here.

Issue Existing sensor has failed (TS-5751-850).  The application involves below freezing temperatures (not outside air but a storage freezer).  Since the sensor is obsolete, what's a suggested replacement? Environment Network 8000 MicroZone II Cause Sensor failure Resolution Try the TO series sensor from Veris Industries.

Issue Installation flowchart for a network SIGNAL software installation Environment SIGNAL network version Cause Installation documentation Resolution Installation flowchart available in the Network Supplement of SIGNAL (F-25952), page 9 (pdf) or page 7 (paper)

Issue Trying to use OPRIF to make a few programming changes to a MicroSmart controller. OPRIF is installed on a SIGNAL computer (Windows 98). With SIGNAL disabled, OPRIF is able to start and handshake with the COM port. However the Auto Answer feature is enabled by default and begins an endless loop of trying to synchronize with the modem. The looping effect prevents a proper connection to the DMS to do programming changes. How can the Auto Answer be disabled on startup of OPRIF? Product Line TAC IA Series Environment OPRIF or Operator Interface version 11.4 and higher Cause Initialization file was modified by default Resolution The readme.txt file in the DMS folder explains how to prevent Auto Answer from being enabled on startup of OPRIF. Click here to view the entire readme file. Below is the excerpt on how to disable Auto Answer: Changes to the command strings used for modem-initialization and control The default modem init-string "AT C1 E1 V1 S0=1 S7=51" has been changed. It is now "AT&C1&D2E1V1". If you or your modem don't like this string, you can now override the default. Using NOTEPAD or EDIT, create a file called MODEM.INI in the DMS directory. This file should contain a single line of ASCII, which will be your customized initialization string. The line must begin with the letters "AT", and must not contain the letters "DT". Other than this one restriction, your modem-init string can contain whatever commands your modem requires. Two separate default strings have been defined for turning auto-answer ON and OFF. These may be overridden by creating files with the appropriate names in the DMS directory. To specify a customized string to force your modem to STOP auto-answering, use NOTEPAD or EDIT to create file a called ANSWEROF.INI in the DMS directory. By default, this file would contain the single ASCII line "ATS0=0". If your modem requires a disconnect command, you could instead write a line that reads "ATH ATS0=0". The default autoanswer ON string "ATS0=1", instructs the modem to answer on the first ring. To answer on the third ring, use NOTEPAD or EDIT to create a file called ANSWERON.INI in the DMS directory. It should contain the single ASCII line "ATS0=3". SUMMARY: Description Default String Filename Comment Modem Initialize AT&C1&D2E1V1 \DMS\MODEM.INI Modified in 11.4 Auto-answer On ATS0=1 \DMS\ANSWERON.INI New in 11.4 Auto-answer Off ATS0=0 \DMS\ANSWEROF.INI New in 11.4

Issue TRD-IO-16 and TRD-IO-34 Installation (Wiring) & Configuration Guides Environment Niagara G3 Cause Quick access Resolution These guides are also available at http://www.niagara-central.com. TRD-T-IO-16 TRD-T-IO-34

Issue The AX Serial Tunnel service does not initialize on a station startup: ---------- Station Starting: FRI JUL 11 14:02:45 2014 ---------- Tridium Niagara Station, r2.301.529.v1 [WFU_UNC06] MESSAGE: ErrorLogService installed [/WFU_UNC06/services/ErrorLogService] ************************************************************ ERROR: Could not init node [/WFU_UNC06/services/IbsAsdService/AxSerialTunnel] java.lang.NullPointerException at tridiumx.tunnelAx.Tunnel.doInit (bytecode 48) at tridiumx.ibsAsd.AxSerialTunnel.doInit (bytecode 84) at tridium.foundation.node.Node.init (bytecode 1) at tridium.foundation.prism.LoaderModule.initNodes (bytecode 26) at tridium.foundation.prism.Prism.initNodes (bytecode 4) at tridium.foundation.Station.startStation (bytecode 60) at tridium.foundation.Sys.boot (bytecode 27) at tridium.foundation.Sys.bootLocalSns (bytecode 17) at tridium.tools.StationMain.bootSns (bytecode 0) at tridium.tools.StationMain.doIt (bytecode 352) at tridium.tools.StationMain.main (bytecode 10) at java.lang.reflect.Method.invoke (Native Method) at tridium.nre.Nre.mainTmpl (bytecode 271) at tridium.nreNre.main (bytecode 1) Product Line TAC IA Series Environment Niagara R2 (revision 522 or above) Cause The tunnelAx jar is not installed in the host UNC. The release notes for AX Tunneling in R2 do not clearly state to install the jar file in section 2.4 and 2.5 which provide install instructions; however, section 1.2 indicates the requirement of this jar file. Resolution Install the tunnelAx jar file prior to starting the install instructions in 2.4 and 2.5.

Issue XIF files for Version 1 and Version 2 of MNL controllers Product Line EcoStruxure Building Operation, TAC IA Series Environment SmartStruxure with MNL Cause Not available on other online resources Resolution Download the zip file available here for the following profiles:

Issue Vulnerability affecting certain versions of OpenSSL. Product Line Andover Continuum, EcoStruxure Building Expert, EcoStruxure Building Operation, Satchwell MicroNet, Satchwell Sigma, TAC IA Series, TAC INET, TAC Vista Environment OpenSSL Cause Software vulnerability Resolution Information and Customer Statement located at the following link on the community: Schneider Electric Security Statement Regarding the Heartbleed Vulnerability. A corporate statement on this can also be found here: Schneider_Electric_Heartbleed_Customer_Statement_APR_15_2014.pdf.

Issue MicroSmart MSC-P1500 Series controller quick reference for interfacing voltage and current sensors. Environment MicroSmart MSC-P1500 Cause The configuration for this controller is non-standard meaning the wiring and software configuration are not 'typical' with the rest of the MicroSmart controller line. Resolution The images available here are excerpts from the MSC-P1500 Installation Instructions (F-25504)

Issue Includes PSI Error Messages and Device Error Messages Environment PSI Microzone II Network 8000 Cause Quick reference Resolution The error codes are listed in the PSI MicroZone II Operator's Manual.  The full document is available here:  F-23058. Just the error codes are available here:  Pages 59-61.

Issue Using the SIM-MTECH manual (F-26133-2) for reference, the Read/Write range of "Space Static Pressure Setpoint' on page A-45 displays as 0 to 5.0 "WC.  But the displayed setpoint does not match the value in the McQuay controller.  And, in general terms, any space static is never as high as 5.0 "WC. Environment SIM-MTECH Cause The manual contains a typo. Resolution The above-mentioned space static pressure setpoint range is actually -0.25 to +0.25 "WC. Keep this in mind as calculations are done to convert the unitless range of 0-250 to a value in "WC.

Issue A new computer has been configured as an InVue Client computer.  In Viewer, when displaying a typical graphic screen, the dynamic values for each OCX is replaced with the words "Access is Denied". What causes this message and how can it be corrected? Environment InVue Wonderware for Intelligent Buildings (WIB) Cause Primarily a Windows permissions issue or incomplete communications setup. Resolution Try each of the following to correct the problem: Make sure DCOM is enabled (Start -> Run -> dcomcnfg) and running on both the client and server computers. Use "telnet" command to see if port 135 is open and available for DCOM. Use dcomcnfg.exe to modify its settings: On Default Properties tab, verify that "Enable Distributed COM" is checked, default authentication level is "Connect" and Default impersonation level is "Identify" On Default Security tab, Default Launch Permissions - click Edit ... button, verify that the Administrators group is shown and has "Allow Launch" permission" On Default Security tab, Default Configuration Permissions - click Edit ... button, verify that the Administrators group is shown and has "Full Control" permission" Windows login account for the client pc must exist on the server as well -- same username and password -- administrative privileges mandatory Ensure wwuser.exe (factorysuite/common folder) reflects the local computer name and administrative user account Re-do the DDE Shares as outlined in Tech Bulletin 02-26 on the client computer. Turn off any firewall and disable/remove anti-virus / anti-spam program or service.

Issue Replacement for discontinued I/A Series hardware UNC-410, UNC-520, ENC-410 & ENC-520 Product Line TAC IA Series Environment I/A Series R2 Universal Network Controllers UNC-410 and UNC-520 I/A Series G3 Enterprise Network Controllers ENC-410 and ENC-520 Cause Due to component availability, the following UNC/ENC parts have been discontinued as of 1st December 2013.  Resolution Discontinued UNC/ENC controllers can be replaced with the JACE 603, JACE 645 controllers series. The JACE 603 and JACE 645 are the first network controllers that can run either R2 or G3 Niagara applications when a corresponding license is installed.  New sites and expansions – these Network Controller parts come with the same metal box enclosure as the products they replace: Retrofit applications – these Network Controller parts are a replacement board that fits into an existing UNC/ENC enclosure: Refer to PA-00251 for details.  *Note - The parts for new sites and expansions are not available for all regions. Contact your local Schneider Electric sales representative if you have any questions.  * Updated May 2015 The parts TRD-RB-603-R2 and TRD-RB-645-R2 are not longer available. See below for the equivalent parts. TRD-RB-603-R2 > TRD-RB-603 + TRD-R2-RB-6XX TRD-RB-645-R2 > TRD-RB-645 + TRD-R2-RB-6XX _______________________________________________________________________________________________________ * Updated March 2019 The JACE-603 and JACE-645 has been discontinued as of June 2018.  The recommended replacements are the EcoStruxure Building Operation AS-P or the I/A Series JACE-8000. Refer to PA-00592 I/A Series JACE 600 End of Commercialization.