Building Automation Knowledge Base

Issue Requirement to powering DPU’s / SCU's with DC Power Environment DPU 7900 Series; 7910, 7920, 7930 and 7940 SCU 1200 Series; 1284, 1280 and 1200 Cause The majority of times that a user powers up a DPU / SCU is usually with 24V AC. However, DC power can also be used as an alternate. Resolution Series 7900 DPU's: The wiring to this can be two fold, it can be done just like the AC with pins 1 and 2 to power from the XFMR. However by doing it this way, the full 24V will be not be delivered to the unit. The recommended way to do this would be to hook either wire 1 to Power and wire 2 to ground or wire 2 to power and wire 1 to ground. This way you will get the full 24V delivered to the unit. SCU 1200 Series: For these units you would connect the +24V positive lead to TB1-1 and the negative lead to TB1-3 (which also must be connected to earth ground). Assuming you have sufficient 24Vdc current supplied, all the reader supply current output ratings would apply. The same local 24VDC source could be connected to more than one SCU in the same enclosure.

Issue Windows User's Account for logging into I/NET Environment I/NET Seven 2.11 and above Cause With the release of I/NET Seven 2.11, there is a new feature where the user can utilize the Windows User’s Account to log into I/NET. Resolution Select Edit Host Computer Passwords from I/NET's main menu to open the Host Password editor. Select Add to open the Host Passwords Assignments editor. In the Name field, use up to 30 characters to define the user's Windows account name. Use the following syntax for this field: machine_name\user_name or domain_name\user_name The entry in the Name field must exactly match the user's Windows account name. The following characters cannot be used within the name: " / []: | =, + *? < >. The Password and Confirmation fields become inactive and are not used for this type of account. Skip these fields. Continue filling in the other fields and assigning functions to the account. If necessary, refer to the Host Passwords Assignments editor for instructions. Once this is set up, select Log Off, then Log On again and check the box for Current Windows User and the current user will be logged on automatically.

Issue An error occurred while installing DSS: Cannot Start Service Product Line TAC Vista Environment DSS Vista Installation Cause This error can be found when installing Vista 4.3.x or higher after selecting Vista Administration of the SQL database. In the Application Event Log you will have an error stating the following: Cannot start service DSSWriterService on Computer '.'. --Stacktrace- at System.ServiceProcess.ServiceController.Start(String[[,args) at System.ServiceProcess.ServiceController.Start() at TAC.DSS.Install.ServiceInstallTask.Install() --End of stacktrace-- The reason this is happening is because when you selected to have Vista Administrate your SQL database it created local PC accounts (TACA_PCNAME and TACM_PCNAME). The TACA_PCNAME account is used to start the TAC DSS Writer Service and that account does not have access to the file to launch it. The access problems are typically caused by installing Vista on Windows Server 2003 and the "Authenticated Users" group has been removed from the User group on the PC. Resolution Click "Yes" at the install prompt and let the installation complete. Right Click on My Computer, and select "Manage". Navigate to Groups found in System Tools\Local Users and Groups. Double Click the "Users" group. Click the "Add" button. Click the "Locations" button and select your PC at the top of the list and then "OK". Type in TACA_PCNAME and click "OK". Note: This error should only occur if you have a non default security scheme on the network or PC. You should consult the IT department to make sure the TACA_PCNAME account will not be removed from the User group which will cause this problem to return.

Issue There is no explicit documentation which explains methods of wiring an STR sensor to an Xenta 100, 280 or 300 other than which wires connect to which terminals. If OP power wires are in the same bundled cable being used for the sensor and override button and potentiometer, it can cause temperature swings in the readings. Environment Xenta Operator's Panel (OP) Xenta Programmable controllers Xenta 281, 282, 283, 301, 302, 401 Cause The problem is that when you connect either one of those wires for OP power to the controller, you have created a capacitor between the signal wire and the OP power. This can cause temperature swings of typically 0.5°F and up to 2.5 or 3°F. Resolution Ideally you'll separate that pair of wires from the others by at least a few inches from the bundle. Even if they are in the same conduit, the reading will still be better with OP power on a separate pair from the bundled cable. Twisted temp sensor wire is also preferable for minimizing this effect. What about the sensors that are already connected this way? You can eliminate most of the variation by installing a 33 microFarad capacitor on the thermistor input terminals of the Xenta in parallel with the sensor. This should be a 10V or higher, low leakage cap (e.g. tantalum) and you should be careful to observe the polarity.

Issue Calculate proportional band from Control > PI > gain values Environment Xenta 121 ZBuilder Cause The gain value in ZBuilder is a unitless value representing the inverse of the proportional band in °C. The maximum value for gain is 32.7675. Resolution 100/gain = proportional band °C If the gain is set to 25, then the proportional band is 4°C (7.2°F, diff). Because the maximum gain value is 32.7675, the smallest possible proportional band is 3.05°C (5.49°F, diff).

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.