Building Automation Knowledge Base

Issue Using "Module" display with a controller in Vista 4.4.0 Environment TAC Vista Workstation IV LON Devices Cause There are two options for how to display SCPTs and SNVTs in Workstation for a LON device. Resolution To change the way points are displayed for specific controller in Vista 4.4.0 or higher you can change the "Use Modules" option on that controller. Right click on the Controller and while holding down the "Shift" and "Ctrl" keys select the properties option. You will now see the "Use Modules" option in the list. With this option set to "on", the controller will display the SNVTs and SCPTs using functional blocks to separate them. With the option off the SNVTs and SCPTs will be displayed in a single group as a list. To get the setting to take effect, right click on the controller and select properties. On the XIF file tab browse to the XIF file of the controller. (The path must change for this to take effect.)  

Issue Modifying the Vista database to put all the points of a 102-AX into one folder to accommodate graphic pages that were built in Vista with versions of 4.4.0 or earlier. Environment Vista 4.4.0 Vista IV Cause When you upgrade to Vista 4.4.0, your database structure remains unchanged. Although 4.4.0 now displays SCPTs, you cannot see them on any LonWorks controllers yet. The process to access these is simple, but if you are not careful it will break any graphic pages, shortcuts, and other similar database access functions. Resolution To avoid the work of rebuilding your database follow these steps: Right click on the Vista Server object and select "Properties" while holding down "Shift" and "Ctrl". Change the LWUOPTION from a 0 to a 3. This will turn off Module display as a default and will avoid the change in database structure that will break graphics. For each controller that has SCPTs that you want to see right click on the controller and select properties. On the XIF file tab browse to the XIF file of the controller( typically found in C:\LonWorks\Import\TAC\X100\ for Xenta 100 controllers). Log out and back into Vista Workstation to see the changes. You will now have access to the SCPTs for each of the controllers you changed without breaking any graphic pages and shortcuts.  

Issue ZBuilder launches, displays the splash screen, and immediately minimizes. Environment ZBuilder Cause ZBuilder always launches minimized Resolution Do not wait for it to minimize to restore it. Click on the splash screen and that will prevent it from minimizing.

Issue Turning off automatic plug-in registration when LonMaker is opened Environment Echelon LonMaker Plug-Ins Cause By default, LonMaker automatically registers any unregistered plug-ins when a drawing is opened. It can cause a major delay in starting up a drawing if it is restored onto another PC where the plug-ins don't need to be registered and is better to leave that as an option to the individual users. Resolution The option in LonMaker is enabled by default as are the other startup options (network interface, onnet/offnet). Uncheck "Register all unregistered plug-ins when re-opening this drawing" Check "Skip this prompt when re-opening this drawing" There won't be any unwanted plug-ins registered to the LM drawing and LonMaker will launch a little faster, as well.

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 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 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 "??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 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 What does "Commence Communication" do? Environment LonMaker TAC Vista System Plug-In Cause The menu option in the System Plug-in to commence communication is a common troubleshooting step. Understanding exactly what occurs when this option is selected is beneficial to know when it will be helpful. Resolution The function of "Commence Communication" is to upload the Vista group and configuration parameters to the Vista database. When creating a new network, it is necessary to execute the "Commence Communication" command as the final step of the process.

Issue TAC Vista and Peripheral Software Installation Outline Product Line TAC Vista Environment Microsoft Windows 2000/XP (Microsoft) LonMaker (Echelon) Microsoft Visio PCLTA-10/PCC-10/PCLTA-20/SLTA-10/PCNSI Adobe Acrobat  LNS  lmw31.exe lmw313U1.exe LNS3SP8.EXE LNSSP8U1.EXE HASP device driver h4_hinstall hdd32.exe Privilege Licenser 2.01 Aladdin Privilege Administrator 2.01 taclicense201.exe taclicense202.exe .NET Framework 1.1 TACVistaConfig1.2.0 .NET Framework 1.1 SP1 Microsoft SQL Server (MSDE)2000 SP4 MSXML 4.0 MDAC 2.8 Vista Server IV WorkStation TAC ToolPack 4.X   Cause The correct installation procedure for Vista IV and necessary peripheral software. Resolution Below is an outline that can be followed to install Vista in the proper order. Each "*" denotes a software package followed by the associated files/programs that are included. Depending on your specific application, some of the software may not be needed. For example, a Vista Classic network will not need LonMaker. Call Tech Support if you have any questions concerning the software needed for your application. *Microsoft Windows 2000/XP (Microsoft) *LonMaker (Echelon CD) LNS Utilities: Microsoft Visio, PCLTA-10/PCC-10/PCLTA-20/SLTA-10/PCNSI (only if using an Echelon LNS interface), Adobe Acrobat (if you don't already have it) *Update LonMaker to 3.13 and LNS to 3.08.05 (TAC Extranet) lmw31.exe, lmw313U1.exe, LNS3SP8.EXE, LNSSP8U1.EXE *HASP device driver utility (TAC Extranet) h4_hinstall - MUST Execute from a Command Prompt! or... hdd32.exe if using Windows Server 2003 *Privilege Licenser 2.01 - "taclicense201.exe" or 2.02 - "Privilege Windows XP crash hotfix" (TAC Extranet) *.NET Framework 1.1 (Microsoft) *TACVistaConfig1.2.0 (TAC Extranet) .NET Framework 1.1 SP1, Microsoft SQL Server (MSDE)2000 SP4, MSXML 4.0, MDAC 2.8 (Reboot) At this point you could be prompted to choose which type of Licensing to be used. Select which option is best for you, the Site License (Order Entry Department), 30 Day Demo (TAC Extranet), or Engineering dongle. This will write the appropriate license files to the Privilege License Server. *Vista Server 4.X with WorkStation (TAC Extranet) (Reboot) *TAC ToolPack 4.X (TAC Extranet) If you encounter any errors during the installation process, be sure to make a note of specific errors received so Technical Support can better troubleshoot your issue. A simple way to record errors are to capture a "screenshot" (Ctrl+PrintScnr). The screenshot can then be pasted (Ctrl+V) into Paint a text editor like wordpad for later reference. Note: Beginning 2012, PSS will no longer support the Privilege License System. The Tamfs26 Server will be retired along with TAC License Server software. It would be wise to inform the customer of this important information to plan for future upgrade in the event that their site license has issues.

Issue The actuators or devices terminated off of the V outputs are not working properly. Environment ZBuilder 121 FC/HP controllers Cause The triac outputs on the TAC Xenta 100-series controllers are sinking (switching the ground connection) rather then voltage sourcing (switching the hot connection) except for the Xenta 104-A. Resolution Since most equipment requires voltage sourcing then there are two possible solutions:   For the TAC Xenta 121, use the Zbuilder to reassign the I/O to use a relay output (max 4). This is sufficient for basic applications such as cooling, heating, and fan on a Fan Coil Unit or reversing valve, compressor, fan, and strip heat on a Heat Pump. Install interposing relays on the triac outputs.