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 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 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 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 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 Performing an action that normally starts WorkPlace Tech Editor or Monitor does not start the tool. A warning message is displayed. Schneider Electric StruxureWare has stopped working A problem caused the program to stop working correctly. Please close the program. Product Line EcoStruxure Building Operation, TAC IA Series Environment SmartStruxure WorkStation SmartStruxure WorkPlace Tech Editor and Monitor program Cause .NET support not enabled in Visio Resolution Enable the .NET programmability support in Visio. as documented in Section 4.6 of  the SmartStruxure WorkPlace Tech Editor and Monitor manual. Open Windows Control Panel Click Programs and Features In the list of programs, select Microsoft Office Visio and then on the File menu, click Change In the Change your Installation dialog box, select Add or Remove Features and then click Continue On the Installation Options tab, expand Microsoft Office and then Microsoft Office Visio Click .NET Programmability Support, select Run from My Computer, and then click Continue Windows reconfigures Microsoft Visio. When finished, click Close

Issue A space temperature sensor is not reading correctly on a MicroSmart controller (Model # MSC-P-1504).  The type of sensor is not known due to its remote location.  What are the possible values for the SCALE, OFSET, and CVTYP elements? Environment MicroSmart MSC-P-1500 line of controllers Cause Trying to determine the type of sensor installed so a spare sensor can be brought for the service call. Resolution The different combinations of SCALE, OFSET, and CVTYP can narrow down the type of sensor installed (i.e. RTD, voltage, or current).  The exact model cannot be identified remotely.  See page Table 6 on page 17 of the Installation Guide for this controller family.

Issue Is there a SmartStruxure specification that includes a piece for Network 8000 migrations? Environment Network 8000 Cause sales request Resolution The document is available on the Buildings Business Extranet, under Products > SmartStruxure solution > Sales > Guide Specification. It's a Word doc so it can be modified to suite the desired needs. The current version is 1.4 and is available here for convenience.

Issue The customer is replacing a defective actuator on a hot water reheat valve downstream of a VAV box.  The VAV and associated hot water valve are controlled by a DMS MicroSmart MSC-V-511 controller. Can the MF41-6043 actuator be wired into the MSC-V-511 and control the valve? Environment DMS MSC-V-511 MF41-6043 Cause Defective actuator is discontinued and cannot be swapped with an identical, working one. Resolution The triac outputs on the MSC-V-511 can properly control the MF41-6043 actuator. Terminals D1 to D4 provide 24 Vac which is the voltage required for the actuator. Look at the MSC-V-511 installation guide (F-25710) on page 18 for details on how to wire and program the actuator. Remember that the MSC-V-511 provides 24 Vac power so there's no need for an external power source.   If needed, the MF41-6043 installation guide has wiring diagrams on page 6. The actuator requires 2.3 VA. The digital outputs on the MSC-V-511 can provide up to 12 VA.

Issue Can the SE7605B5045 be converted to work on an Echelon trunk? Environment Viconics SmartStruxure Lite Cause Wrong controller ordered for application Resolution VCM7600V5045E Echelon Retrofit Communication Card is available for purchase and can be installed in the field. Click here for a list of all communication cards available.

Issue Proxy objects were successfully created in a G3 obix integration of a R2 station.  The writable proxy objects (ie: setpoint overrides) in the G3 station do not propagate the new value to the native object in the R2 station. Environment Niagara G3 Niagara R2 Cause This is a known issue with the G3 obix driver. Resolution Right-click the proxy object in the G3 station and do a 'forceUpdate'. If there are several dozen proxy objects affected, download this program object.  Paste it anywhere in the Obix Network and execute it.  A 'forceUpdate' will be done to all proxy objects. As of June 2013, these are the most up to date jar files for an obix integration:  2.301.535i.beta.jar, 2.301.535i.beta.jar.pc, and niagaraDriver.zip. Extraction password:  niagara (all lowercase)

Issue A network of GCMs are configured with the NIM card in each GCM to allow intercommunications over the ethernet network. Some (or all) of the devices are no longer communicating.  No known changes have been made to the ethernet network. Environment GCM-86xxx series GCMs with GCM-ETH-1 ethernet network cards The GCM-ETH-1 network card contains firmware version 11.1F. Cause Known issue with the older version of the firmware (rev 11.1F)  where network traffic issues can cause communications failures. Resolution If a firmware upgrade kit (GCMA-149-113) is available you should update the firmware in the NIM card to version 11.2T, using the procedure in document F-26229. In the event that you cannot obtain a firmware upgrade kit or a replacement GCM-ETH-1 NIM card, the procedure documented in Technical Bulletin 99-56, can be used to clear the memory of the NIM card, allowing it to re-establish communications.

Issue What was the repeater used on MicroSmart communication trunks? Environment DMS MicroSmart (all revisions) Cause Information on a discontinued product line Resolution The typical repeater installed was Model # RPTR-DMS-WW.  There are other model numbers for trunks installed with fiber. Click here to view the Repeater Installation Instructions (F-25846).

Issue Need a currently available sensor that is compatible with the MicroFlo II controller. Environment MicroFlo II VAV controller Cause Need a sensor for the obsolete MicroFlo II. Resolution See the Spec Data sheet (F-24314-5, page 3) for a list of compatible sensors that are currently available. NOTE: The MicroFlo II controller is OBSOLETE.