Building Automation Knowledge Base

Issue In Niagara R2, how can manual commands be issued to Network 8000 GCM/LCM analog and binary points? The LcmAnalogCmd, LcmBinaryCmd, GcmAnalogCmd, and GcmBinaryCmd objects have a manualCmd field.  However, this option does not appear in a web browser. Environment Niagara R2 Cause To use binary and analog commands to control points, connect the objects to an Analog output or Binary object. Resolution Due to an anomaly in these objects, connect to an Analog output or Binary Object and issue a change with it before the option to allow issuing a command to the AnalogCmd or BinaryCmd will be available.

Issue What is the Thermowell part number for the sensor TT-I-4-1? Environment TT-I-4-1 Cause Replacing the Thermowell for sensor TT-I-4-1 Resolution The thermowell for sensor TT-I-4-1 is either the W-S-4-1/2-1 for 1/2" MPT 4" long well or W-S-3/4-4-1 for 3/4" MPT and 4" long well

Issue What is the part number for the thermowell for the sensor TT-I-6-1? Environment TT-I-6-1 Cause Replacing the thermowell for sensor TT-I-6-1. Resolution The thermowell for sensor TT-I-6-1 is either W-S-6-1/2-1 for 1/2" mpt and 6" long well OR W-S-6-3/4-1 which is for 3/4" mpt and 6" long well.

Issue In Niagara G3, can the station's web login page be customized to display a custom logo? Environment Niagara G3 Cause Instruction on displaying a custom logo on the station web login page. Resolution If the WebService of a Niagara G3 station is configured for cookie authentication (the default), the station's login page can be customized to add a custom logo, centered over the login entry field.  Adding a custom logo can be done by performing the following steps: Go to the slot sheet of WebServices under Services in the station and add a new slot. Name the slot "logo", and select Type of "baja" and "Ord". In the property sheet of the WebServices, the new slot logo now can be used to point to an image for display on the login screen. The custom logo will also appear above the "Powered by NiagaraAX" when loading the Web Workbench applet.

Issue Vista events from a standalone Xenta 5xx must be adjusted. Product Line TAC Vista Environment Vista Event Logging Xenta 5xx Cause Situations where the Xenta controller must handle more events while in a "standalone" installation. Resolution In Xenta firmware versions >5.1.3 it is possible to change the event storage capacity of the Xenta with a console command "eventcap". The variable of eventcap allows the user to define how many event storage files Xenta may have. The valid number range of events is from 10 to 2000. Each file stores ~150 events, depending on event size. Example: 700 files are recommended to store ~100,000 events. Note: This only works for Vista events, not I/NET. I/NET uses another memory module of the Xenta device and will not be affected with this change.

Issue In a Niagara R2 UNC or Niagara G3 ENC station running the ASD service, the block output override feature does not get range-checked if the override is initiated from a linked gxText. Environment Niagara R2 Cause Graphic feature defect Resolution Attempting an override using the Block Output object with a time that is greater than 255, generates an error informing the user that the range must be between 0 and 255. If the same override is performed from an attached gxText or graphic, the range is not checked. A value greater than 255 is truncated to a one byte value equal to four minutes. Add descriptive text on the graphic near the override explaining (and warning) that the valid range for an override is 0 to 255.

Issue The ProView for LON Display shows the enumeration definitions for SNVT_tod_event even though the wizard is set up to use SNVT types with different enumerations. Environment Niagara R2 & G3 Proview Cause Display conflict Resolution Although the schedule does not display the desired enumerations, the schedule's "value" is successfully sent to the bound controller. This issue has been observed on both Niagara R2 and G3 platforms. It applies to version 2.62 of the ProView display. Distech Controls, the makers of the display, have been informed of this "display-only" issue. For now, OCCUPIED and UNOCCUPIED are the enumerations that will work.

Issue In a Niagara R2 station, the ProView for LON Display wizard initializes with "Nv Type Lookup Error". Environment Niagara R2 Cause The ProView wizard for R2 displays a dialog box with error  "Nv Type Lookup Error" after the display is commissioned for the first time. The Workplace Pro DOS window will show a java exception as well: OnInit_WeekSchedStep called. Disposal was interrupted: java.lang.InterruptedException Resolution This is a nuisance error that occurs only with the initial commissioning of the display. Clear the program from the display and exit out of the wizard. Re-enter the wizard and begin programming. Subsequent commissioning completes successfully.

Issue How do I use the Corporate 1000 card format on sites with a mixture of CX9900 and CX9680 controllers? Environment CX9900 CX9680 Corporate 1000 card format Cause You cannot use the card type of Corporate 1000 directly in a system that has access controllers other that Netcontroller II and ACX II's on it Resolution The problem here is that the CX9900 does not directly support the Corporate 1000 card type. The only way to do it on the CX9900 is to use a custom format which means the card type on the personnel record is also set to Custom Format. Setting up the AccessFormat on the CX9900 is standard but when trying to use this format on the CX9680 you will get an error. The reason for this is because in order to implement the Corporate 1000 card type on the CX9680 we had to create a custom format for it behind the scenes since the AC-1's could not directly support this new card type. In order to create this as a Custom Format on the CX9680 use the special numeric AccessFormat2 and set it up the same as you did in the CX9900.

Issue CyberStation stops sending Alarm Emails Environment Continuum CyberStation Cause There are spaces or special character in EventNotification names, which cause the emailing of alarms to stop. Resolution In order to send emails from Alarms you must make sure your EventNotification names do not have any spaces or special characters in them.

Issue How to install hotfixes that replace executable files. Environment Continuum Cyberstation Cause No longer need the existing executable file and want to replace with the hotfix file. Resolution The correct way to install a hotfix that replaces an executable file is to either delete the original file before installing the hotfix or to do the below. In Windows Explorer drag and drop copy the original file so you end up with a file called Copy of xxxxx.exe Delete the original file through Windows Explorer. Then extract the hotfix file into the Continuum directory through Windows Explorer.

Issue Two different new batteries were installed into a DMS-350A. Neither of them has charged to the point of indicating GOOD. The voltage on the battery clips with the battery installed reads 4.5 Vdc. Why doesn't the battery charge? Environment DMS-350A Cause Poor connection between the battery and battery holder. Resolution Clean the battery holder contacts and bend them for a better connection.

Issue In a Niagara R2 station, a particular folder has a very high number of links. The completed links in this folder show tags with "??" instead of the usual letters. Environment Niagara R2 Cause The "??" tag names indicate that the available letter tags have all been used up. Resolution They start at "a" and go to "z" then re-start with "aa" and finish at "zz". If there are additional links, the tags display "??".  This is a display only limitation and will not cause any performance issues.

Issue The help menu in Niagara G3 fails to load.  After pressing the "Load Help" button, the "Building Help Database" pop-up "blinks" and nothing happens. Environment Niagara G3 Cause This issue is typically caused by some non-standard jar files being placed in the c:\Niagara\ \modules directory. Resolution Ensure there are no sub-directories, or files other than valid .jar files, in the modules directory of the Niagara installation. Custom jar files or other files in the modules directory must be moved somewhere else.

Issue Erie controllers SR-201, 301,601, 201-AT, 301-AT, and 601-AT. Voltage apparent on unpowered Relay Terminals. Environment SR-201 SR-301 SR-601 SR201AT SR301AT SR601AT Cause The large foil surfaces used to carry the high currents of the switched loads of these control boards act as antennas causing the DMM to read a voltage signal. Resolution The voltage as read L2 to X1 approximately 12 VAC and L2 to X2 approximately 25 VAC is not harmful to humans or equipment and will not affect the operation of the unit. When determining if these induced voltages are present, all wiring except power wiring to L1 and L2 should be disconnected.

Issue On a Niagara R2 / LON integration, this error appears in the Standard Output Window: {lon} Wrong Nv direction for nvUpdate from {lon}MNV2_16(1/17) for Selector 132. How can this issue be resolved? Environment Niagara R2 LON Cause The error is related to a mismatch between the Lon network management tables within the Niagara R2 UNC station and what is actually in the controllers on the bus. Resolution To view the errors: Run the Lon Utilities Manager (right click on the LonWorks service) Select the local Lon device Select command reports, and sub-command verify. This will compare the UNC’s network management tables to the values within the controllers and show any discrepancies. This issue can occur for many reasons (i.e. controllers that are offline when making changes to the network bindings, a rogue controller out on the bus that has or was not commissioned and had the same domain, subnet, and node as another controller, etc.) To correct the error: Re-commission the local Lon device The re-commission all controllers Perform a bind. This will clear the appropriate tables, recalculate the selectors, and re-write the bindings. This should clear the issues. Run another reports verify to confirm that there are no further errors listed.

Issue In a Niagara G3 ENC, is there a way to view its diagnostic data without Workbench (i.e. CPU usage)? Assume the ENC is not licensed for web access. Environment Niagara G3 ENC Cause Alternative way to view the diagnostic data without Workbench. Resolution In a web browser, type in the following: http://x.x.x.x/ord?spy:/ (where x = IP address of the ENC) After logging in, all the diagnostic and statistical data will be available via a set of links. It's the same information that's also accessible via Workbench.

Issue After performing a backup in WorkPlace Commissioning Tool, where are the backup files located? Environment WorkPlace Commissioning Tool Windows XP Windows Vista Cause Locate the backup files to do a restoration or transfer to another workstation. Resolution In Windows XP, the backup files are located in the C:\Documents and Settings\All Users\Application Data\Workplace Tech\Backups directory. In Windows Vista, the backup files are located in the C:\ProgramData\WorkPlace Tech\Backups directory.

Issue Is there a way to allow users station access, through a browser or JDE, in Niagara R2, without having to first sign-on without a user name and password? Environment Niagara R2 Cause Enable "Public Access" feature to bypass sign on.  Resolution Yes. Starting with Niagara release 2.3, a “public access” feature was added. The public access feature allows for configuration of a station to permit GxPage access without being prompted to enter a user name and password. When this feature is used, the “Sign On” dialog box is skipped and the GxPage is displayed as if user was already signed on. See “Niagara Web Solutions Guide” for detailed setup information.

Issue In Niagara R2, some GxPages and control objects are going to be duplicated many times. Each page and object will have many links. Is there a quick way of linking objects instead of the time intensive way of manually linking each individually? Environment Niagara  R2 Cause Graphics programming tip Resolution The Bundle container along with composites are used to expose control logic properties to a GxPage.  The properties, to be linked, would be composited for both the control objects and Gxpages.  Composite involves assigning the same name to both the GxPage object property and the control object property that are being linked.  Once composited objects properties have been named, it is simply a matter of clicking on the “Match” button in the Link Properties screen to complete the link. Objects with the same name are then automatically linked. The procedure for linking objects using Bundles and Composites can be located in Niagara Standard Programming Reference document. Note that only native Niagara objects should be placed in bundles.  Shadow objects should not be in bundles.