Building Automation Knowledge Base

Issue Importing a Menta application for a Xenta 301 controller cannot be saved. Environment Xenta 301 importing Save Saving Cause Importing a Menta application for a Xenta 301 controller, and then saving it, works correctly. If the application is modified in some way, requiring a second import, then this import cannot be saved. Resolution This issue has been assigned to defect 22178, which is due to be fixed in release 1.5. Work around. Delete the existing controller object, and then create a new controller object before importing the modified Menta application.

Issue If the 7716 is taken off the LAN what status light indicates LAN Reconfiguration? Environment I/NET Site Cause If the 7716 is taken off the LAN what status light indicates LAN Reconfiguration? Resolution Assuming the unit has not lost power, LED #7. It is Labeled "RECON"

Issue When a PDA is used to calibrate a MN-Sx sensor, the calibration offset value is stored in the controller. How can the value be preserved within the application drawing? Environment PDA MN-Sx sensor Cause The offset is not stored as a nci so a “Read NCI Values” command will not preserve it. Resolution The calibration offset is a plus or minus temperature and / or humidity value. These values must be entered in the hardware wizard - sensor config area. Once entered, the values remain with the application drawing (make sure to re-download the controller).

Issue The database has an invalid version. Note that LNS databases can be upgraded using the CompactDb method, but also note that LNS databases are not backwards compatible. Once updated to version N+1, the database will not be accessible for a version N client any more. Environment LonMaker NL220 Vista LNS Cause Invalid database version.  If you are running LonMaker 3.1 with a non-Turbo LNS Server and somebody who is running LonMaker 3.1 with a Turbo LNS Server has edited the database and sent you a backup, you will not be able to open the database until your PC has been upgraded. The global database is not open. (Subsystem: LNS, #64) and Invalid database version. (Subsystem: LNS, #81)[DB #-2038] errors occur if you try to open a database with an older version of LNS. Resolution Right click on the title bar of the design window and select About. This will tell you your LNS server version on the machine in question has. It must be the same or greater than the database you attempt to open.

  Issue Extending a User/Cardholder Expiry Date Product Line EcoStruxure Access Expert Environment Access Expert Hosted V3 Cause Steps needed to Extend an Expiry date for a cardholder Resolution In Access Expert, there needs to be a way to extend cards that are about to expire after the default time has been entered initially. This can be done for single users or badge types depending on the circumstances. The following steps describe how this can be accomplished:   Open and log on to the Users instance Once opened, select Access Control and click on the List Tab then select View Expiring Cards A list will appear that shows all the cards that are about to expire based on the parameters entered When this list comes up, Select the Extend All button to bring up the Editor that will extend the time Enter the New Expiry Date that allows the card to function accordingly Click OK and the cards listed will then have the New Expiry Date listed    

Issue Unable to add a new user in a G3 (Niagara) ENC station accessed via web browser. There is no "New" tab displayed under the Services / UserService / right-click, User Manager page. Environment I/A Series ENC-520, ENC-410 Embedded Workbench feature, part number ENC-WB Cause The ability to add a user to the ENC via web browser requires the Embedded Workbench feature be enabled. Resolution To determine if the ENC has the Embedded Workbench feature enabled, open the Platform, License Manager, view the license, and the feature name = "web" ... ui.wb.admin = true indicates that the feature is enabled.  See the high-lighted lines in the screen capture below. If the feature is not enabled, it can be ordered and added to the ENC license.  

Issue Which aux switch is the correct for the Forta actuators? Environment Forta Auxiliary switch S2 8800104000 Cause The correct aux switch for Forta Resolution The correct auxiliary switch to be used with the Forta series actuators is the S2. Part no 8800104000.

Issue Some MSTP Devices show up when learned but other are not coming in. They worked fine on the Continuum install with the same MSTP network. Environment Automation Server Cause The AS has a maximum of 50 MSTP nodes and the b3 controllers that are not coming in are above this NodeId. Resolution Change the b3's NodeId's to a value below 50. 1. Use the Continuum system to change the Id by deleting the device object from the database, recreating it with the new NodeId. 2. Clear the controller to factory default.

Issue ADAA problems: can not dial in or out of the site A PCU is set up as a 06 TAP. The RX and TX LEDs are flashing on the RS-232 card. A CBL048 cable is connected from the RS-232 card to the modem. The RD and SD lights are flashing. Environment ADAA Cause The wrong BIN file is in the PCU. Resolution You have the wrong BIN file in the PCU. If the PCU is at the “Boot State”, you may have the wrong EPROM too. Install the correct BIN file; and it is strongly recommend to put in a compatible Asynchronous EPROM.

Issue Where should I find the preprogrammed number for a key or card? Environment I/NET Site with Access Control Cause Where should I find the preprogrammed number for a key or card? Resolution Typically it is printed or stamped on the device. However you may have to convert the listed value into a number the can be entered into INET. Refer to TCON 237.

Issue I need to convert the hexadecimal value of a key/card for an older I/NET system. Is there a TCON or any documentation on how to do this? Environment I/NET Site Cause I need to convert the hexadecimal value of a key/card for an older I/NET system. Is there a TCON or any documentation on how to do this? Resolution Refer to TCON 237. Most calculators can convert decimal and hexadecimal. Windows also has this feature in the on-screen calculator.

Issue Send out the system date and time as a SNVT_Time_stamp Environment Time Stamp SNVT type Xenta 511 Cause Send out the system time properties to monitor externally and make sure the time is synchronized. Resolution You can do this by creating signals in the system window for the system variable year, month, day, hour, minute and second. Create an nvo SNVT_time_stamp in the Xenta 511. Create connection objects and connect the signals with the members of the SNVT. Note, you have to change the category and the unit for hour, minute and second to match the SNVT.

Issue Equalization not working on a File Master and Client Are you having an issue where you have a File Master and several Clients but cannot get Equalization to work? It looks like the snapshot gets delivered but the File Master’s Icon stays red and the client never gets the database.  Environment I/NET Cause SQL services may not be running properly. Resolution There are a few possibilities that could be the cause of this not working. Verify that MSSQLSERVER and SQLSERVERAGENT are set for Automatic and Local Machine in Services. Verify that the file C:\Program Files\Microsoft SQL Server\MSSQL\Data\InetDbSnapshot.mdf already exists but is not a registered database on the file master. See note below. Go to the FM; delete C:\Program Files\Microsoft SQL Server\MSSQL\Data\InetDbSnapshot.mdf and InetDbSnapshot_Log.ldf. Set all PCs to Stand Alone; re-promote the File Master and then the clients again. Note: This is an existing file that SQL uses, if you can rename it, it means that the existing one is not being used and therefore cannot be created by SQL again. If you cannot rename this file then this is not your issue.

Issue Lost or unknown access password for Micronet View.  Environment Global  Cause Lost user password for Micronet View Resolution Back up the MicroNet View project before carrying out the following: Take a copy of the default password file from MicroNet View default project1 Copy the password file from C:\MicroNet\Projects\Project1\View\password.bin Paste this file into Your project. C:\MicroNet\Projects\YourProjectName\View\password.bin

Issue Sigma - Short Text displaying correctly on local client but not displaying on the remote client Environment Sigma Version 4 releases Cause In version 4 Sigma the short text file is located in C:/Sigma/Data/Locality/English United_Kingdom (IF UK)/ This folder location is set by the regional settings of the PC. If there is a difference between the Sigma Client and Sigma Server then if new short text entries are added they can display on some clients but not on others. An example of this would be if the server is set to UK locale then any short text added via the local client would appear in the UK short text folder. If you then have a remote client with the locale set to US then it will read the short text from the US short text folder which will not have the correct entry. Result will be an incorrect object display. Resolution Check the Regional Settings for all Sigma PC's installed on the system. For Windows XP and Server 2003 go to Control Panel>Regional and Language Options. On the first tab make sure the Standards and Formats and Location are set to the correct location. On the third tab Advanced make sure the Language for non-Unicode programs is set to the correct location. For Windows 7 and Server 2008 go to Control Panel>Region and Language. On the first tab Formats make sure the Format is set to the correct location. On the second tab Location check the location is set to the correct location. On the last tab Administrative make sure the current language for non-Unicode programs is set to the correct location. In summary all Sigma machines connected to each other need to be set using the same regional settings

Issue Schedule Import will not update. Environment G3 Niagara Cause Schedule import defaults to Manual update this will prevent the schedule from automatically.. Resolution Schedule execution time can be set to daily, days of week, interval and manual.  Please consult Doc Drivers document.  

Issue Do I need a Handheld Console (HHC) to set up a 7798 (SLI) (ISITE)? Environment 7798 SLI ISITE Cause The 7798 does not have ports for a HHC. Resolution No. In fact, the 7798 does not have ports for a HHC. The 7798 is setup using its touch pad. Refer to 7798 TCONs for more details.

Issue How can BACnet objects be learned as "full" objects and not "lite" objects in Niagara R2? Environment Niagara R2 Cause "Use lite objects" is enabled and need to be disable (uncheck the box) "Use Lite Objects" setting using BACnet Utilities. Resolution From the BACnet Utilities window, when performing either a "network - learnNetwork" or "device - learnDevice" command, clicking the Execute button will generate a pop-up window. In this window, uncheck "Use lite objects", and click OK to proceed.

Issue In a Niagara R2 UNC station, running the LonWorks Service, there are duplicate node addresses. How can they be resolved? Environment Niagara R2 UNC Cause Duplicate subnet-node address conflicts abort the learn process. Follow the instruction in the resolution to apply unique addressing to learned devices. Resolution There are two ways: Change the subnet/node address(es) of the "duplicate" device(s) already in the station. Now, when a Learn function is performed, the newly learned node(s) addresses will not conflict with existing ones. Set the "duplicate" node(s) in the station to unconfigured. Then do a Learn function and ignore unconfigured devices. The unconfigured node(s) need their shadow object(s) copied manually into the station and then Matched / Commissioned using the Device Manager. For more details, see the Niagara LonWorks Integration Guide, page A-1 to A-3.

Issue When using the PSI software, the Current Status Screen, All Points History and the graphic data display screens do not properly display the text shown on that screen. Environment PSI software Computer Cause The video bios in the computer does not support the graphics mode used by the graphic displays of the PSI software products. Resolution This problem was first identified several years ago on some models of Gateway brand laptop computers. The problem has been observed from time to time, since then, on various computer makes and models. The problem affects both the "Current Status" screen, the "All Points History" screen and the graphic display screens for analog I/O points. There is no software workaround for the problem. The best solution for this problem is to evaluate the computer model before purchasing any quantity of them. Download test program vga_test on The Exchange Download Center, which allows testing of the computer without having to load the PSI software. The test program can be run from any removable media (diskette, CD, memory-stick, etc.) so the computer can be tested at the computer dealer's store or sales office. The text file included in the zip file explains how to run the test and how to interpret the results.