Building Automation Knowledge Base

Issue Customer service requires proof of purchase of the old version when an order is processed for a version upgrade (rev 4 to rev 5) license. Environment WorkPlace Tech Tool Software Cause Customer wants to purchase a major version upgrade for the WorkPlace Tech Tool software and needs to know what documentation is required so that they can get the upgrade price instead of paying full price. Resolution The recommended documentation is the sales order / license request form that includes the original product request and the unlock code.  Either the email or faxed copy, including the unlock code, from our Customer Service department is acceptable. In the event that proof of the original order is not available, please contact Product Support Services for information on acceptable alternative documentation.

Issue Customer requests the capability to reset the setpoint entered via the MN-Sx sensor from his application program. Environment MNL series controller with MN-Sx sensor MNB series controller with MN-Sx sensor Cause Jobsite specification calls for the capability to remotely reset the setpoint. Resolution The MN-Sx series of sensors were not designed for remote programmability of the setpoints.

Issue Upgrading a UNC and a more current version of the CCN jar file is required. Environment Niagara R2 all versions Cause Current site UNC is being replaced with new hardware and the version of Niagara R2 is changing from 431 to 532. Resolution The CCN jar file is proprietary since it is used for integrating Carrier Comfort Network (CCN) controllers.  Current versions of the jar file are not available from Schneider-Electric.

Issue Do we need to power cycle an I/A Series BACnet controller after changing its address using the DIP switches? Environment I/A Series Micronet BACnet (MNB) controllers Cause There is a need to change the DIP switch address on a MNB controller. This could be due to several reasons such as DIP switch address being wrongly set or if there are gaps in addressing which needs to be fixed. Resolution No, there isn't a need to power cycle the MNB controller after changing its DIP switch addressing. The MNB controller should reset itself approximately 10 seconds after changing the address.

Issue When the mouse curser is hovered over bang in Continuum Explorer, the tool tip is not indicating what is wrong. Environment ACX57xx Cause Windows 7 is inhibiting tool tips on Bang indicators. Resolution The following registry entry is used to inhibit or expose the Tool Tips on a Mouse Over Note:  Always backup the registry before making any changes. HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\Advanced Data Type: REG_DWORD [Dword Value] // Value Name: ShowInfoTip Modify/Create the Value Name [ShowInfoTip] according to the Value Data listed below. Value Data: [0 - ShowInfoTip Disabled / 1 - ShowInfoTip Enabled] Exit Registry and Reboot following changes to the registry.

Issue Need to change the value of the same property in multiple VAV controllers without having to go to each individually. Product Line TAC IA Series Environment I/A series (Niagara) R2 Cause The site or database has a reoccurring controller that requires the same change to be made for each device. There is a need to an efficient way to perform this task across the entire site. Resolution The servlet is named AdminTool and it can be found in the Tridium core runtime jar in the apps folder.  The AdminTool object allows you to perform an online global search and replace of a property value.  The object is detailed in the Niagara Standard Programming Reference starting on page 6-18.  Use of this can be somewhat tricky as it is sometimes difficult to get the settings correct (e.g. names, filters, etc.).  It is a good practice to setup a test station and test the "search and replace" statement before performing the search and replace on the actual station database.

Issue UNC 410 AI point no longer reads the input properly. Environment UNC-410 Cause Input is not reading the input value properly. Resolution Verify that the NDIO object for that physical point is still programmed correctly -- 10K Thermistor, Resistance, 0-10 VDC, 4-20 mA. Verify that the input sensor or device has not been damaged and has not been replaced with an incorrect replacement. Verify that the physical input port has not failed or become damaged by either programming an unused input in place of the failed port or temporarily swap the input device/sensor to another port.  You may need to swap the input with another currently used input if none are available.

Issue Pinpoint will not start. When attempting to start it, an error related to MFC42.DLL pops up.. Environment CyberStation v1.71 Cause There was likely a file registration issue, deleted file or corrupted file. Possibly see the Windows Event Log for a related entry. Resolution Uninstall CyberStation on that workstation. Delete \Continuum directory. Reinstall CyberStation. Start CyberStation and Pinpoint.

Issue How to determine which version of the CPU card (GCMA-112-x) of the GCM-84000 series supports the GCS, ASD, or other communication protocol. Environment GCMA-112-x, CPU printed circuit board for the GCM-84000 series Cause Cross reference purposes.  Resolution   CPU Part No. Bus Type GCMA-112-000 GCS (standard) GCMA-112-001 GCS (standard) GCMA-112-002 ASD GCMA-112-003 CCL GCMA-112-010 GIM-21000 GCMA-112-011 GIM-MTECH This table shows which version of the GCM CPU card supports the different firmware and bus types.

Issue Building a database to take to a site and the doors do not show up in Netcon, though they can be controlled. Environment I/NET versions 2.10 and up using SCU 1284s. Cause The controller has not recognized the doors in the SCU and has to be readded in Netcon to be saved again. Resolution To resolve this there are a few simple steps that needs to be followed to get this to work again. Connect to the controller and then go to Edit/Host Computer/Network Configuration. Penetrate the Link Summary, Controller and then SCU. In the cnf column there should be a -- sign indicating that there is no communication to the device. Click on the delete button to remove it from the SCU. Close all the Editors and then go back to the controller. Go to Resident I/O Points, if the door point exists, delete it and close out of the editor. Open up the Resident I/O Points and re-add the point again and repeat Step 2. Save the doors now as Step would have a + sign indicating that there is communication to the device.

Issue What is the advantage of having a Doubly Bus Terminated Topology segment VS Free Topology in a LON FTT 10A setup? Environment CX9900 CX9680 LON IOU Modules Cause Unknown Resolution The advantage is bus distance, with the doubly terminated bus you can have a bus length of up to 2700 meters (depending on type of cable used), with the free topology the maximum would be 500 meters. (see page 22 in the Continuum I/O Reference document). The disadvantage is the Doubly Bus Terminated method is that it does not allow free topology, nodes must wired in a bus topology (just like in the LON RS-485 485) to limit electrical reflections.

Issue A system had two BACnet Icons in the ContinuumExplorer - one fully populated with controllers and points and the other empty.  Environment CyberStation BCX MS/TP Cause When trying to save a simple PE program mirroring a third party BACnet point, an error "could not find the object" on the path which included the BACnet Devices folder came up. Resolution There should not be multiple BACnet Devices folders in the ContinuumExplorer. In this case the empty BACnet Devices folder was renamed. The InfinityProgram could then resolve the object name and save the program successfully. Further investigation as to what caused the duplication must be done.

Issue In an I/A Series R2 (Niagara) UNC station, not able to link to the output of a SIM block, receive error "java.lang.NullPointerException". The SIM block is from a SIM-CCN, TYPE = 44. Environment I/A Series R2  UNC with the GCM driver Network 8000 SIM-CCN, containing SIM blocks with TYPE = 44 Cause The SIM-CCN, containing SIM blocks with TYPE = 44, can be  highly  "customized", so the inputs and /or outputs of the block may be "data species" that the GCM driver in the UNC does not recognize. The GCM driver has not been tested with any of the SIMs (SIM-CCN, SIM-MTECH, SIM-TRANE, SIM-YORK, LNC-100). Resolution 1. Try using appropriate Shadow Objects of type GcmAvParam, GcmDateParam, GcmDvParam, GcmEnumParam, GcmIntParam, GcmStringParam, or GcmTimeParam. 2. Try adding APT or DPT blocks to the SIM-CCN database to correctly interpret the SIM block outputs for the GCM driver in the UNC.

Issue Does Niagara G3 provide a way to route alarms from multiple ENCs to the ENS, and then send emails alarms from the ENS? Environment Niagara G3,  all versions Cause NA Resolution The alarm generated in the ENC must to be forwarded to the ENS. The following are steps for accomplishing this. It is assumed that Email service is already configured in the ENS. Drag an AlarmClass object from the Alarm Palette to the AlarmService of both the ENC and ENS. These Alarm Classes are for alarms which will be emailed. Name both the ENC and ENS AlarmClass the same. Both names must be the same. Drag a StationRecipient from the Alarm Palette to the AlarmService of the ENC. Open the property sheet of the StationRecipient Select the ENS from the Remote Station dropdown list. (must have an established NiagaraNetwork connection) - Save In the ENC AlarmService, connect the Alarm output of the Alarm Class to the StationRecipient’s Route Alarm input. Open the NiagaraNetwork of the ENS and select the ENC NiagaraStation. Expand the ENC station and select Alarms Right-click on Alarms and select Property Sheet For Alarm Class, select “Use Existing” from the dropdown list - Save Setup is now configured to send alarm email via the ENS Note: StationRecipient class receives Alarms and formats them for another station. The StationRecipient is available in the Alarm Module. This object along with AlarmClass will be used in this setup. Alarms from a remote station are routed to any "matching" AlarmClass, that is, one with identical name as the "alarmClass" field in each alarm record. If no local "matching" AlarmClass is found, the station's default AlarmClass is used.

Issue New computer hardware was provided for SIGNAL.  The SIGNAL folder from the previous hard drive was copied and pasted to the new computer's hard drive.  When SIGNAL is started, a pop-up error message appears:  User Build error, Btrieve # 910  INI path error Environment SIGNAL all versions Cause New computer hardware provided and the original floppy diskettes are not available. Resolution The following two things cause this error: Windows User Account must have administrative privileges the \windows folder must have the bti.ini and signal.ini files

Issue I/A Series G3 ASD driver Microzone II controller object point values indicate active override conditions when no overrides have been applied. Environment I/A Series G3, Microzone II, ASD, tacAsd Cause tacAsd driver / Microzone II firmware compatibility issue Resolution Due to compatibility issues, use of the tacAsd driver with Microzone II firmware below Version 2.0 will cause the associated Microzone II point values to indicate false override conditions. For proper operation, the Microzone II device firmware must be upgraded to V2.0.  The V2.0 firmware kit can be ordered using part number MZ2A-119-200.

Issue When attempting to start InVue Developer, an error message appears preventing it from proceeding: The application cannot be edited.  Process "WindowMaker" on computer "PCNAME" is editing this application. The Invue jobsite graphics and tagname database were last modified on a different computer.  Invue creates a "lock" file which prevents the application files from being changed on any other engineering computer than the original. Environment Wonderware for Intelligent Buildings (WIBS) or InVue version 1.1 Cause The application (graphics generation) was done on a different computer than the current one. Resolution In the application directory, find and delete the appedit.lok file and re-start InVue Developer.

Issue Does the STR-250 work on Micro Regulators (MR)? Environment I/NET Seven STR-250, I/STAT, M/STAT I/SITE Controller and Micro Regulators (MR) Cause The STR-250 Wall Module is the replacement for the commonly referred to I/STAT sensor, still referenced in I/NET documentation.  The I/STAT is no longer available.  Resolution The STR-250 sensor is the replacement for the I/NET I/STAT, so installation and configuration for the STR-250 is as per this I/STAT. There are two documents that will provide assistance with this TCON126 and TCON299 (Chapter 21). The STR-250 full functionality must be installed on the I/STAT port of any I/NET device and configured as detailed in the above documents. Only one I/STAT port exists per MR. The M/STAT is still available and is used as the hardware tool for configuring the controller settings on all supported I/STAT devices, such as, all Micro Regulators (MR) variants, I/Site LAN Controller (Model 7728) and Xenta 102-AX. 

Issue Upgraded a system from v1.74 to 1.93. Credential 1 tab is now grayed out in the personnel editor for users who had access to all personnel editor tabs previously.   Environment CyberStation Access Control Personnel objects Cause After an upgrade from v1.74 to v1.93 the personnel editor Credential 1 tab is grayed out for users who previously had access to all personnel editor tabs. If using the PIM, however, all the attributes, including the ones shown on the Credential 1 tab, are accessible to the same users.  Resolution Continuum creates some new features in v1.93 locked by default. So, any user that did have administrator or Group 1 access (i.e everything unlocked) finds that they are now locked out of the Credential1 tab because it didn't appear in the previous version (in this case v1.74). The resolution is to unlock (change from "locks" to "keys") all the new features for User Security Group 1 as well as any other groups that require this access. If  'Security' is grayed out when right clicking on the Continuum icon then the security settings for the user will have to be reset via s SQL query. (Contact PSS for query) However, if using the new v1.93 PIM (Personnel Information Manager) you will not notice this, because you are allowed access. It is only when you use the personnel editor that this is observed.  

Issue I/A Series R2 Enterprise Server station fails to start.  Error indicates "fatal boot - file is used by another process station VM." Environment I/A Series R2 Enterprise Server Cause There may be multiple stations running on the server, or write protection settings on the PC may be preventing the desired operation. Resolution Verify that only one station is running on the server (e.g. autostart). Verify that the station is not open offline when attempting to start. The Enterprise Server database and software is attempting to open, create, or write into a file as part of normal operation (e.g. config.db.lock, a properties file, etc.) and the file or directory is write protected.  Verify that all files under the Niagara directory are not set to read only or blocked for writing by the software.