Building Automation Knowledge Base

Issue Some customers may specify that the login screen to a Xenta Server be bypassed. Environment Xenta 511, 527, 555, 701, 711, 721, 731, 913 Cause When accessing a Xenta Server using a web browser a username and password are required by default. Resolution Configure the user you want to automatically log in to the Xenta Server Generate a certificate To avoid having the certificate error pop up every time you connect to the Xenta Server, go to XBuilder, and generate a certificate that has the same name as the IP address of the Xenta Server. Edit Slogin.html and loggedout.html Connect to the Xenta Server using FTP ftp:// XXX.XXX.XXX.XXX The Slogin.html and loggedout.html are located in the folder www/index Copy the files to your local hard drive Edit the files with, for instance, notepad and change the following Slogin.html Line 54 document.AuthForm.UserID.focus();" document.AuthForm.UserID.focus(); send(AuthForm);" Line 98 input type="text" name="UserID" value="" size="20" > input type="text" name="UserID" value="user" size="20" > Line 104 input type="password" name="PassWord" value="" size="20"> input type="password" name="PassWord" value="password" size="20"> loggedout.html Line 5 (extra line, add < symbol at beginning of line) meta http-equiv="refresh" content="2;url=/www/index/Slogin.html"> Carry out the changes Reconnect to the Xenta Server using FTP Change the names of the files that are already in the Xenta Server (Backup) Copy the files that from your hard drive to the Xenta Server  

Issue 527/913 Hostname in I/NET Environment I/NET site using Xenta Cause getting generic serial number station name using 527/913 Hostname in I/NET Resolution The Xenta 527/913 will show up in the Station Summary report in I/NET, but if you have not configured it correctly it will show up with a generic serial number station name. To define this name you need to specify the hostname of the Xenta controller. This can be done with the setip command with HyperTerminal or via the Web Page in the Configuration\Network\TCP/IP page. Once you have changed this setting you will need to reboot your Xenta controller for the change to take effect.  

Issue An error occurred while installing DSS:COM+ installation corrupt Product Line TAC Vista Environment Microsoft Windows OS Windows Event Log Cause COM+ Installation error Resolution Consult the Windows Event Viewer to confirm that this operating system problem is present. To correct it you will need to follow the steps outlined in Microsoft's Technical Bulletin: How to clean up a damaged COM+ catalog  

Issue Every time you access a Xenta 511/527/913 you are taken to the "Server Reboot" page Environment Xenta Servers Xenta 511, 527, 913 Cause This problem is caused by some Proxy Servers that will cache the first page they find with that address which is typically the "Server Reboot" page since it is the first page found when you power up the device. Resolution To correct this, you can either clear the cache in the Proxy Server or you can configure your web browser to not use the Proxy Server for the Xenta Server address. Open Internet Options Select the Connections tab Click the LAN Setting button Click the Advanced... button Add the address of the Xenta server to the Exceptions window  

Issue "Not able to log on TCP connect" Error downloading to TAC Xenta 28x/30x/40x from System Plug-in The devices are offline in TAC Vista Environment System Plug-In Xenta Programmable Controllers Xenta 280, 281, 282, 283, 300, 301, 302, 401, 401:B Cause  If the TAC Vista Communication Port is set to "Communication Port - Echelon LTA" this message will occur. Resolution Check the settings in the TAC network in the system plug-in. If you want to use LNS for communication (open scenario) the Communication Port has to be set to "Communication Port – LNS" Once you have made this change Update the Vista Database before attempting another download.  

Issue Can't find the "Value" attribute when configuring a Digital Presentation on an OGC Graphic Page Environment TAC Vista IV OGC Graphic Editor Cause Some signals in Vista do not have a numerical value and the "value" attribute is not available by default when configuring a digital presentation object in the Vista Graphic Editor. Some examples of these points are SCPTLocation and SNVT_String. Resolution To select the "value" attribute on these signals check the "Presentation format" box and the "value" attribute will now be available.

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 Running reports on a PC that is using Datacard ID Works and the report is not showing up on the PC screen as expected. Only half of the report is visible while the other half is scrambled and unreadable. Environment Datacard ID Works Cause The Datacard ID Works Printer can only print that format and not text which was why the display was wrong in the Reports. Resolution Select Printers from, Start or Control Panel. Uncheck the ID Works printer if it is your default. If you have a secondary or Network printer, just add it to your system and make it the default. Run the Reports again and it will come out the way it should.

Issue How can I control a dual duct VAV box with Xenta controllers? Environment Xenta 102-AX Dual Duct heating/cooling Cause The Xenta 102-AX is an application specific controller designed to vary the volume and outlet temperature of a single terminal unit. It does not, by default, control a dual duct, where a constant source of cold air and hot air and delivered in separate ducts. Resolution You could conceivably use a single Xenta 102-AX with the airflow pickup on the discharge of the box instead of the inlet. Then connect the hot deck damper as a 2-out PWM heat stage. A more elegant solution is to use a pair of Xenta 102-AX controllers. One 102-AX is connected to the cool deck and setup normally. Either its heating airflow setpoint is set to match the cooling low flow or heating airflow is set to 0 if you wish the cool deck to shut off in heat. The "Effective Setpoint Source" must be set to "Norm of Heating and Cooling Setpoints" so that the setpoint sent to the hot deck controller will not bounce from heating to cooling when room conditions change. For this reason, it might be preferable to use an STR-202 so that there is no digital display to confuse the occupant. The second 102-AX is connected to the hot deck, space temp is bound from the first and nvoeffectivesp is bound from the first to nvisetpoint of the second. Configure input 1 as a duct temp and connect a 4.7Kohm resistor from it to ground. This will simulate a duct temp of 110°F and keep it in warmup mode. As with the cool deck, you have a choice whether to set the warmup low flow to 0 or to some minimum position. Set your occupied setpoints to the same values as the cool deck controller. (It's actually using them in the setpoint calculation, but for simplicity's sake, set them the same. For a more complete description, consult the reference manual concerning nviSetpoint.) You should also bind nvoOccupancyStatus from the cool box to nviOccCmd on the hot deck box. That way if someone puts the box in to after hours override, they'll both operate. As mentioned before, the room sensor (STR-200/202/250) is connected to the cooldeck controller. You'll need to connect 3 conductors to a 1/8"TRS jack to the hotdeck controller in order to connect the MSTAT for calibration purposes. Otherwise you'll have to crawl into the ceiling to connect it. This arrangement is based on having airflow sensors on the inlets of both the cold and hot deck.

Issue When running Seven (Crystal) Reports on the same PC as ID Works Environment I/NET Site Cause Having issue when running Seven (Crystal) Reports on the same PC as ID Works Resolution Using "Smart Printer Driver" set as the windows DEFAULT printer Seven Reports fails while attempting to display the query. You may first see a small window with '1/4o and a square". Before opening Seven Reports change your windows DEFAULT printer to another printer. Restart Seven Reports and run a query. The problem is due to the default paper size ID Works uses versus what windows uses.

Issue "??12293" error message when trying to log into Vista Workstation Environment Vista Workstation Cause If a message window appears stating "Could not connect to TAC Vista Server." in the title and "??12293" in the main window then you are trying to log into Vista using the wrong authority style. Resolution Trying to log into Vista using a Windows account when Vista is in Low authority. Trying to log into Vista using a Vista account when Vista is in High authority.

Issue Opening a graphic will not cause TAC Vista to dial out to a Xenta 901 Network. The field units can connect to the TAC Vista Workstation and transmit alarms and trend logs. It is also possible to acknowledge alarms from the TAC Vista Workstation and fetch trend logs. Even when values of the remote network are added to the status view the dial-up connection is started. When site-graphics are displayed in the TAC Vista Workstation, values from a remote TAC Xenta are displayed from the database, but the connection to the remote network is not established. Only when you display the properties of the value within the graphic is a connection to the remote network started and the value then updated.   Environment Vista Workstation 4.4.1 Dialed up TAC Xenta 901 Network Cause The server not being in Operating mode could cause this. Resolution Locate the $System object in the root TAC Vista folder Right click and go to Properties Make sure that the "Operating" check box is checked

Issue When upgrading I/NET 2000 to I/NET Seven, if during the install process you answered Yes and specified the I/NET 2000 root directory, I/NET Seven defaults all of its default directories to I/NET 2000. Environment I/NET Site Cause Issue when upgrading I/NET 2000 to I/NET Seven, if during the install process you answered Yes and specified the I/NET 2000 root directory, I/NET Seven will make all the default directories to I/NET 2000 Resolution Either copy the new BIN files into the old I/NET 2000 data directory, or change the I/NET configuration after the upgrade to point to the I/NET Seven data directory. By leaving everything the way it is, it will result in problems with I/NET Seven security, and transactions not showing up correctly.

Issue Viewing SCPTs, UCPTs and UNVTs from LonWorks devices in Vista Workstation Environment Vista Workstation Cause Vista uses a devices .XIF file to define public points in the Workstation.  SCPTs, UCPTs, and UNVTs are not defined in an .XIF, only SNVTs. Resolution As a general rule UCPTs and UNVTs are not available in Vista. There are two exceptions to the rule:  Xenta 102-AX and Xenta 121.  Configuration parameters for these two controllers are available through the Vista Workstation. Most SCPTs can be viewed in Vista UCPTs as NV based on standard SNVT types can be viewed in Vista

Issue Setpoint adjustment using a physical input doesn't work on the Xenta 121. Effective Setpoint has a value of 95°F Environment ZBuilder 4.xx - 5.0.1 Xenta 121-HP Xenta 121-FC Cause A problem in ZBuilder improperly adjusted the Temperature Offset Wheel Scaling units. Resolution Upgrade to Zbuilder 5.0.2 or higher Manually change the SCPTmaxRemoteTempSetpoint and SCPTminRemoteTempSetpoint using the following formula Degrees offset * 1.8 + 32 All values should be entered as positive. Example: 2 degrees up and 5 down results in a maxRemoteTempSetpoint of 35.6 and minRemoteTempSetpoint of 42.8.

Issue Can not Add, Delete or copy Individuals. Environment I/NET Seven Cause When the display order is based on the hexadecimal card number, the Add, Delete, and Copy functions become disabled in the Individuals Summary. This is not an issue with the database or password rights   Resolution Choose some other display order to re-enable the Add, Delete and Copy functions. Go to Access > Individuals. If you have multiple Tenants SELECT the respective Tenant From the Individual Summary display select OPTIONS Change the Display order to Individual, Last Name, First Name or Group Name. Do not put it on Card Number (Hexadecimal). This is option disables the Add, Delete and Copy buttons. OK out of the Options editor The Add, Delete and Copy buttons should now be available.

Issue Deleting Last Tenant from a given door in the System Environment I/NET site with Access Control Cause After deleting last tenant from a given door in the System, issue with cause individuals to not gain access Resolution Are you having an issue with individuals not gaining Access to a given door after the last Tenant is deleted from a Mipped 7920 and the SCU? This may have come about after a door was modified and the last Tenant may have been mistakenly deleted by the user. To correct this, a DPU Restore needs to be done to get the Tables realigned again. Once this is done, then access will be granted to the individuals. This will only take place if you are using I/Net Seven rev 2.11 and below. It was addressed in I/Net Seven rev 2.12, so all you have to do is upgrade your system.

Issue How do I time sync my controllers to my workstations? Product Line Andover Continuum Environment Continuum site Cause The workstation will only synchronize its time to the controllers automatically when the controller is reloaded. It is common practice though to have the controller synchronize its time with the workstation on a periodic basis, commonly once a day. Resolution The only way to synchronize time between the Controller and the Workstation is through a Plain English program running the Workstation. This Program only needs to be created in one Workstation. Below is an example of the program as well as how to trigger the program to run. If Minute = 3 then Goto SetTime Else Stop SETTIME: Set NetworkName\LowestNodeCXName\Date to Date Stop E: Stop Note: This program needs to be triggered off the minute system variable. The program is a Fallthru program which resides in the CyberStation. You only need to do the lowest ACCNet Id controller in each Continuum network. Also ensure that the UTC offset has been correctly entered in every Workstation and BACnet device, and that each Network has the correct Time Zone setting.

Issue How do I set up a Continuum system to do automatic log truncation to save database space? Product Line Andover Continuum Environment Continuum Trend logs Cause Database maintenance. Resolution Setting up Automatic Log Truncation with SQL Server and MSDE Database  MSDE Engine For MSDE, you can download the Stand Alone MSDE Database Utilities from Buildings Download Center.  These utilities are capable of automatically truncating the logs, as well making automated backups, checking for low hard drive space, etc.  SQL Server For full SQL Server, you can easily create a scheduled Job. Details are described below.   To create a scheduled Job that will truncate the Continuum logs in the SQL Server: Open up SQL Enterprise Manager  (Note that the SQL Server Agent service must be running in order to create a Job) Highlight the Continuum database From the Menu, select Tools \ Job Scheduling A wizard opens: "Welcome to the Create Job Wizard." Click Next Select Transact-SQL Command,  Click Next For the Database Name, select ContinuumDB (or whatever the name of the DB is) In the large white space for the Transact-SQL Command, cut and paste the code from our web site: ****** Replace 90 with the number of days to maintain in each log ******** delete from accessevent where DATEDIFF(day, timestamp, getdate()) > 90 delete from activityevent where DATEDIFF(day, timestamp, getdate()) > 90 delete from alarmevent where DATEDIFF(day, timestamp, getdate()) > 90 delete from errorevent where DATEDIFF(day, timestamp, getdate()) > 90 Click Next On the next screen, you are asked when you do want to run this job Select "On a recurring basis" and hit the Schedule button On the Schedule page, set up whatever schedule you desire Click OK to close the Schedule Page • Click Next On the Job Notifications screen, you can choose (if you want) any email or net send alerts. This is optional • Click Next In the final page, you are given a summary of the Job you have just created and you can change the name of your Job to anything you want. It might be a good idea to give it a more descriptive name like "Weekly Log Truncation" Click Finish and you are done. You should get a message that the job was created successfully. To verify that the Job is running correctly, you can go to the Enterprise Manager of SQL Server and click on the Management Folder, then expand the SQL Server Agent folder and click on Jobs. On the right-hand pane, you will see a list of created jobs. Scroll down and find the job that you just created. You can get information about the history of the Job, whether it ran successfully or not.

Issue What should I set the Access Server System variable to on Continuum access controllers? Environment CX9200, CX99xx, ACX57xx or CX9702 controller with an ACX780 or ACX700 controller. Access Server, AccessServer Cause Below are the different configurations and what their different AccessServer system variable settings mean. Unlike Infinity when changing the setting in the controllers the controller does not reset. It is best if you set the AccessServer setting to the ACC Net ID of the Primary Access server workstation. This will keep the Access Control system operational should there be any distribution problems. Resolution CX9200, CX99xx,  or CX9702 controller with an ACX780 or ACX700 controller. The CX can stay at the default of it’s own ACC Net ID. In the above configuration the AccessServer variable in the CX is ignored. The AccessServer variable in the ACX controller can be one of the following: AccessServer value set to 0 in the ACX (Default setting).This means that access validation of personnel records will only be done locally in the ACX. If the person is not found in the ACX or the person is denied access locally in the ACX the person will not get in. AccessServer in the ACX controller set to the ACC Net ID of the Primary Access Server workstation (valid values are 191-253). This means that access validation of personnel records will be done locally in the ACX first. If the person is not found in the ACX or if the person is denied access the controller will double check at the workstation to verify whether or not the person is supposed to have access. If the person is also denied access at the workstation then the person will not get in. If the AccessServer value in the ACX controller is set to the ACC Net ID of the parent CX controller it has no effect and is ignored. CX99xxor CX9680 controller with AC1 modules  or ACX57xx. The CX can stay at the default of it’s own ACC Net ID.  AccessServer value set to the CX’s own ACC Net ID (Default). This means that access validation of personnel records will only be done locally in the CX. If the person is not found in the CX or the person is denied access locally in the CX the person will not get in. AccessServer value set to the ACC Net ID of the Primary Access Server workstation (valid values are 191-253). This means that access validation of personnel records will be done locally in the CX first. If the person is not found in the CX or if the person is denied access the controller will double check at the workstation to verify whether or not the person is supposed to have access. If the person is also denied access at the workstation then the person will not get in. AccessServer value set to 0. This is not a valid setting for a CX controller.