Building Automation Knowledge Base

Issue When using the old part no for ordering, it's no longer valid. Environment SHD100 006902320 006902321 Cause Revised version of sensor Resolution Due to a revised and improved version of the sensor, the part number was revised from 006902320 to 006902321.

Issue   Webreport editor - Trendlog comparison dataset is not set. Environment Report editor Cause We haven't mapped any dataset to display the available trend logs in Ext.Trend Logs selection box. In the web reports application we are generating the trend logs data and displaying it. So you can not see the data through report builder. Resolution Since the dataset is not mapped we cant display the report in the editor.

Issue A Niagara R2 UNC-520 time clock cannot maintain proper system time.  It is losing approximately 1 hour daily. Environment Niagara R2 UNC-520 Cause Inadvertently calibrated with an incorrect time clock. Resolution This issue can be corrected in the field.  For details, read TPA-RKFD-08-0003.00 "Slow Time Clock on UNC-520-2 and UNC-520-2-N" on The Exchange Download Center.

Issue The requested service cannot be provided in the current management mode.  Environment NL220 ZBuilder Xenta 121 Cause Attempts to download a ZBuilder configuration to a Xenta 121 on a network that is not "attached."  This is the incorrect management mode to perform a download. Resolution Make sure the network status is onnet and attached.

Issue Provides additional setup information for the R2 ASD (IbsASD) driver. Environment R2 ASD (IbsASD) driver (all revisions) Cause The driver may not communicate correctly with the ASD devices if the driver has not been configured properly. Resolution IbsASD driver basic settings ... General / Engineering retryCount = 3 responseTimeout (sec) = 2 Poll / Config cycleTime (ms) = 333 times number of devices on the ASD bus, i.e., 3 devices per second. Comm / Config commPort = COM4, COM5, COM6 or COM7 depending on which port you are using maxBaudRate = 19200 ( or 9600 if PEM1 controllers exist on the ASD bus) DeviceStatus / Config deviceStatusPingDelay (ms) = 60000

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 The dates shown in the ODBC database are in the incorrect format for the region set. Environment Sigma ODBC Date format Windows 2008 Server Cause The engineer reports that although the correct date structure is shown in the Sigma logging, the format in the ODBC database is incorrect. Resolution This issue was reported on a Windows 2008 Server. Although all of the obvious entries had been changed to the correct regional and language format, one had not. Locate the entry in Regional settings "Copy all settings to all new users" which should be set to the required regional and language format.

Issue Link Summary Indicator in Netcon during Equalization Environment Netcon Cause During equalization, when a Client is connected to the File master, who is either directly or over Ethernet connected to the system, a – sign is displayed in the cnf column in Network Configuration, Link Summary. Normally, this indicates that there is no communications from the Client PC to the controllers. However, if you penetrate the link you are able to see all the controllers and their sub-lan devices. Resolution In order to get rid of the – sign in the cnf column, the following steps needs to be followed: Shut I/NET and I/O Server down on the Client Open Windows Explorer and browse to C:/Program Files/INET Seven/Data folder and delete all files with .dat extensions Restart I/NET and I/O Server again Go to Edit/Host Computer/Network Configuration and in the Link Summary, the – sign in the cnf column would be gone Note: The dat files will get rebuilt when I/NET is restarted.

Issue A Continuum database setup for IE. version 1.81 will only support Continuum software version 1.81. Environment Continuum all versions Cause Attempting to use different versions of the Continuum software on a Continuum database Resolution Using Continuum software version IE. 1.9 would not be able to access a database setup for ie... older Continuum version 1.81. This is true for all versions of Continuum. The Continuum software and database must be of the same version.

Issue An attempt was made to modify the protocol service type attribute, and that attribute was not specified as configurable. Environment Vista LonMaker SNVT binding types Cause For network variables, the service type can be specified in the connection information in the Neuron C variable declaration. The options are unackd, nackd_rpt and ackd. The keyword config is the default. This allows a network management tool to change the service specification at installation time. The keyword nonconfig indicates that the service type cannot be changed by a network management tool. Resolution Echelon requests to please refer to the Neuron C Reference Guide for more information. To see which binding type is necessary, open the .XIF in a text editor and look for the following definition: XIF Definition of Line 2, Field 5: Default service type to use for connections containing this variable. Set to 0 for acknowledged, 1 for repeated, or 2 for unacknowledged. Created bindings needs to match the type defined in the XIF file.  Right click on the SNVT and go to properties.  Go to binding type.  Ensure binding type is the same, i.e. you cannot bind a Repeated SNVT type to a point that was flagged for only Acknowledged bindings. 

Issue Auxiliary I/O or inputs and outputs, allow a system to be expanded to include additional devices outside of standard door hardware such as sirens, panics buttons, or warning lights. Product Line Access Expert Environment Access Expert v3 Cause Lack of documentation on Auxiliary I/O Resolution Input Devices Inputs are also added to  Downstream (interfaces). Inputs are typically added automatically when used to support door contacts and REX but can be implemented to connect motion detectors, glass break detectors, and even panic buttons. Inputs in this section would be separate from those associated with the reader-controlled doors. Inputs can have cameras associated with them to associate alarm points.   Though you can assign multiple cameras to a single point the Assign Camera section will only present one camera at a time. The Assign View allows multiple cameras to be brought together in a single view. To add an Input: Open a downstream interface configuration Select the “Add Input” Enter a Display Name. Define the Address for the input. Set the Behaviour. Click “Save” or “Save & Close”. **Note: Take special care when setting the address as the value does not match the number labeled on the physical hardware. The first address is always 0 (not 1). Input Attributes: Display Name: This is the name of the input that is used throughout the system. Address: The address that the hardware is connected to on the downstream. Behavior: The Normally Open or Normally Closed setting of the input. This is also where any custom EOL Tables are applied. Debounce: The amount of time required before registering the signal. Bouncing is the tendency of any two metal contacts in an electronic device to generate multiple signals as the contacts close or open. “Debouncing” is any kind of hardware or software that ensures that only a single signal will be acted upon for a single opening or closing of a contact. Latching Mode: This sets the type of latching used by the input. Normal Mode (No Entry or Exit Delay): This will cause the input to report an alarm immediately upon activation and deactivation. Non-latched Entry: If set, the alarm will not be reported from an input activation until the entry delay expires. If the input is still activated when the entry delay expires the alarm will be reported. If the input is not active when the Entry Delay expires, no alarm will be reported. Latched Entry: If set, the alarm will not be reported from an input activation until the entry delay expires. If the input is still activated when the entry delay expires AND the input has not been masked, the alarm will be reported. Entry Delay: The time before the input alarm will report. Exit Delay: This function is useful to secure a door when an individual is leaving.  When the ‘exit delay’ mode is set, the following shall occur.  The alarm will not be reported from an input activation until the exit delay expires.  If the input is still active upon exit delay expiry, the alarm will be reported.  If the input is not active upon exit delay expiry, the alarm will not be reported. Hold Time: This can be thought of as a Motion Detector Delay. This is the number of seconds that the change of state must be held before the input will be changed to a deactivated state. Attached: Sets the Attached status of the input. Input Addressing The address programmed in Keep will not match the address shown on the physical board. The programming address is 1 less than the space used on the physical board. Input Address on Board Programmed Address in Keep by Feenics 1 0 2 1 3 2 4 3 Outputs Outputs are also added downstream. Outputs are not only used to support strikes but can be implemented to connect sirens, strobes, and other signaling type devices. Outputs in this section would be separate from those associated with the reader-controlled doors. Outputs can also have cameras associated with them to associate alarm points.   To Add an Output: Open a downstream interface configuration Select the “Add Output” Enter a Display Name. Define the Address for the input. Set the Behaviour. Click “Save” or “Save & Close”. Output Attributes: Display Name: This is the name of the output that is used throughout the system. Address: The address that the hardware is connected to on the downstream. Activation Time: This is the amount of time the output will be active when pulsed. Mode: This sets the output to be in a normal operating mode (normally un-energized) or inverted operating mode. Schedule: This sets the time during which an output will activate. Assign Camera/View: The associated cameras or views for the output. These will display in the Live Monitor/Event History for events associated with the output. Output Addressing The address programmed in Keep will not match the address shown on the physical board. The programming address is 1 less than the space used on the physical board. Output Address on Board Programmed Address in Keep by Feenics 1 0 2 1 3 2 4 3 Scheduling Outputs Outputs can be scheduled by clicking the schedule drop-down menu and selecting the desired schedule. The output will then Activate when the schedule activates, and deactivate when the schedule deactivates.

Issue Upgrading a standalone workstation from 1.74 to 1.9x. The installation fails and returns "Event Log is Full" error. Environment Standalone Workstation Cause The error is displayed when the Windows Application Event Log is full. Resolution Open the Windows Control Panel. Select Administrative Tools. Select Event Viewer. Select Application Open the Action menu. Select Clear all Events. You will be asked if you want to save "Application" before clearing it? Answer "Yes." Enter an appropriate file name. Click on Save. Cold start the workstation and reinstall Continuum.

Issue There is a confusion regarding the output signal options since the data sheet states 0-10V, 0-5V and 2-10V in different places  Environment SCD100 SCD100-D Cause Incorrect output signal range Resolution The output signals available are 0-10V and 0-5V.

Issue Program settings and User profile lost after upgrade. Environment Vista Cause When you upgrade Vista to a new version, a new folder structure is created in the Windows registry. All saved user profiles are stored in the previous version folder structure and need to be exported and imported to the new folder. Resolution First make sure you save the user profile File - Save my program settings Go to Start - Run enter regedit Locate HKEY_CURRENT_USER\Software\TAC\TAC Vista Workstation All Vista version that has been installed can be viewed here. Enter the folder which version you saved the userprofile. Go to TAC Vista Workstation - Settings Right click on the user you want to export and export. Right click on the .REG file created and choose Edit. Change all navigation paths to the version you want to import to. When its done save and right click and choose merge. PS: You can change the folder name in the registry to the correct version and export. Remember to change the name back again afterward.

Issue Object information cannot be seen in the SSM display window. Environment Sigma Display window Display area Items are shown off the screen Cause When the SSM display area is full and you request more data, the new data is not displayed in the display area.  Because the area cannot "scroll down" you cannot see this data. Resolution The issue is related to the Font type / Size selected for text in the "Display" window. The problem can be resolved by; Maximising or resizing the window. Choosing a different font / size.  

Issue Serially connected to a GCM-84000 with a pc running OS/2 and UltiVist.  There is no existing database in UltiVist.  The GCM database will be uploaded to create a new one.  The COM port in the GCM was configured correctly.  The serial cable is also correct and tested with Hyperterminal.  The E: EQUIPMENT SEGMENT in UltiVist is configured correctly and a serial COM port has been added to the W: WORKSTATION & USERS segment.  The UltiVist Background Apps are all running and configured. When trying to access the GCM's Time and Date, an error appears in place of the time and date and reads:  PTP no running. Environment UltiVist GCM-84000 Cause The default settings of the COM port must be modified to suite connectivity to a GCM-84000 which are different than the settings required for a GCM-86000. Resolution Right-click the COM port in the W: WORKSTATION & USERS segment and go to Settings. On the Port Setup tab, ensure the following settings are changed as indicated: IDSR = OFF ODSR = OFF OCTS = OFF DTR = OFF RTS = ON Shut down UltiVist including the UltiVist Background Apps and re-start.  This will re-initialize the serial COM port with the new settings listed above.

Issue What does a Card-View Plus device look like? Product Line TAC INET Environment Card-View plus Cause Ordering and identifying this equipment. Resolution See picture below:

Issue SMTP Copy to Blind copy to Reply to Environment Vista Xenta Cause In order to CC, BCC and the option to let a user reply to a sent alarm you need to configure the Xenta's SMTP settings Resolution There are 3 options under SMTP settings in Xbuilder   Copy to - The same as CC in outlook Blind copy to - The same as BCC in outlook (A copy of the email sent discrete to chosen email) Reply to - When a user gets an email about an alarm and clicks on reply, the address will become the same as the one specified here.  

Issue The Xbuilder device editor by default only allows 200 lines, and some integration efforts require more than 200 points to be programmed. Environment Xbuilder Device Editor Cause The device editor only has 200 rows by default. Resolution The device editor is designed with excel functionality meaning, new rows can be added to allow for more points to be programmed. To add rows to the device editor follow these steps: Open the device editor. Right click on the row number. Choose insert row. Type in the desired number of rows (up to 100) If more than 100 are needed repeat steps 2-4.

Issue Remote Alarm Manager running with TAC Vista loses the connection to the license file. Environment RAM pre 2.1 Remote Alarm Manager License file Cause Remote Alarm Manager fails to recover after its license management briefly loses a valid license from the TAC license server Resolution This issue is now corrected by installing the RAM Software Release 2.1 Then follow the upgrade options in the RAM Release 2.1 Release Notes documentation.