Building Automation Knowledge Base

Issue Deleting a Group from the System Plug-in Environment TAC Vista System Plugin Cause After adding a controller to the Vista database, the System Plug-in automatically creates a new Group Resolution If you move the new controller to a different Group, make sure the controller you added is not still selected when you try to delete the old group. By default, both the controller you moved and the group you moved it from will be selected. Hitting the delete key will delete both.

Issue Xenta 511/527/911: Recovering from a bad download Environment Xenta 511, 527, 911 Cause If the 511/527/911 has suffered an error during the download process and the system starts behaving abnormally, then the device needs to be taken back to a boot state. Resolution Connect to the 511/527/911 using the serial connection on port B Use HyperTerminal to log in. Type "format" command to format the device. Once the process has completed, log in as super user (root/root by default) and set the IP address as detailed in the device manual. Verify that you can ping the device from a computer and then run the appropriate system program for the device you are working with. Select option B Install Full System. This will verify the current program is in the device as well as let you change the color scheme. Once this is completed you should be able to download the existing or new XBuilder project to the device.

Issue Adding Custom Buttons in Vista 4.2 Environment Vista 4.2 Cause In Vista 4.2 you can add custom buttons to the Tools menu or the Toolbar. This can be useful to make shortcuts to the desktop, your Vista database directory, or WordPad. Resolution Right click on any tool bar and choose Customize. On the Tools tab, insert a new shortcut. Enter a name for the button and the Path for the EXE you wish to execute in the Command box. Click Close and your button should be visible from the Tools menu. You can also drag and drop this button on any tool bar.

Issue How can I get SNVT values from one LonWorks network to another without relying on Vista to do object transfer? Environment Two LNS Networks LonMaker/NL220 Cause Data cannot be transferred between two separate LON networks unless they share an L-Proxy in the network management tool. Resolution Each port of a Loytec L-Proxy may be commissioned in a different LonWorks network. Any SNVT bound to one port can be transferred by the L-Proxy to its other port(s).

Issue Corrupted/Hidden Time Schedule Events Environment Time Schedule Objects Vista Workstation Cause Sometimes an event will not show up in the Time Schedule window in Vista, but may still be in the object. Resolution To check all Time Schedules in Vista press Ctrl+Shift+D and a table will show up with all events in that Time Schedule. From here you can edit, add, and delete events.

Issue It is possible to browse and bind the public signals while working on MTA files on your hard drive, however this has repeatedly led to problems when downloaded due to differences in controller names between the MTA file and the controller name in the Vista database. Environment TAC Menta TAC Network Variables Xenta programmable controllers Cause Waiting until the application is imported into the network will allow the Vista database to automatically provide you with the correct controller name to the public signal you are wanting to use. You will have a database browse window rather then a file select window which is your indication that you are doing this the correct way. This method to reduces the chance of operator error. Resolution While generating your Menta application, do not set the Network Address while binding Inputs to the Network Variable option Complete the other parts of the application and import the .mta to the Vista Database using the System Plug In. Once the application has been incorporated in the Vista database you can then edit the application and browse the Network Address of the Input.

Issue "Field Unit Not Configured" error during download Environment Vista System Plug-In Xenta programmable controllers  Xenta 280, 281, 282, 283, 300, 301, 302, 401, 401:B Cause If trying to download the application and parameters in a Xenta controller and the error "Field Unit Not Configured" is received, one cause that has been found is when an Xenta base unit is placed in a LonWorks group (even if it appears to be a part of a Xenta group). Resolution The group in question should be deleted from the Vista database pane in the Vista System Plug-In. Update the Vista database and the controllers imported into the Vista Database should be created in proper groups. Verify that the group is tagged correctly and then update the Vista database once more. Verify for the final time in Vista Workstation that the group is a Xenta group before downloading to the controller in the Vista System Plug-In. You may also drag that Xenta unit into an existing Xenta group after it has been re-imported.

Issue "Error: Device does not refer to a COM port" when downloading an application to a Xenta 400/300/2xx controller Environment Xenta 281, 282, 283, 301, 302, 401 Cause This message means that the LonWorks network in the Vista database doesn’t have any COM port (LNS port) defined. The problem is usually caused when you start a different LonMaker network but forget to change the Vista database directory. When a "update Vista db" is done from the system plug-in instead of adding or updating the correct database, a second network has been added to the Vista db. You now have 2 LonWorks networks in your Vista db but only one communication port. Resolution Delete the incorrect LonWorks network Open the correct LonMaker drawing Update the Vista Db once more to make sure everything is in sync. For the second LonMaker drawing, specify the correct Vista db directory in Vista Server Setup and update the Vista db.

Issue Space temperature sensor calibration using the Xenta 102-AX plug-in Environment Xenta 102-AX Plug-In Cause The space temperature of a 102-AX can be calibrated in three locations:   M/STAT, service menu OP > CSS, resolution 0.1° Vista Workstation, VAV_Controller.UCPTvavSelection.CSS, resolution as entered Xenta 102-AX Plug-in, Browser tab > UCPTvavSelection, resolution 1° The first two allow resolution at least as fine as 0.1° step sizes on the offset.  The LNS plug-in, however, by default only allows whole integer 1° step sizes. Resolution Read to the end before you try this.  NOTE:  It is recommended to make this fix prior to opening the plug-in on a VAV box that has already had the space temperature calibrated via the M/STAT.  Failure to do so may result in the desired calibration being rounded to the nearest whole degree. From the Xenta 102-AX plug-in, select the browser tab (or open the LonMaker browser if you wish). Navigate to and expand the VAV controller object and select "UCPTvavSelection.CSS". Past all of the "CALIBR_NOT_ACTIVE" statements, you'll find a couple of numbers - the second one being 32. Raising or lowering this value will raise or lower the space temp by the same amount. But, until now, if you try to enter 33 or 31 you'll find that only even numbered integers are accepted. What to do? Open c:\Lonworks\types\user\TAC\Xenta100.fmt in notepad. Locate line 172 which should appear as UCPTvavSelection#US: text("%m,%m,%m,%d,%d,%d,%m,%m,%m,%m,%m", Change the second "%d" to "%f" and save the file and restart the Xenta 102-AX plug-in. Now you can change that value in finer increments than is necessary.

Issue Xenta Time Charts changes when clicking Edit in Vista 4.2.3 Environment TAC Vista 4.2.3 Time Schedules Cause In some cases Xenta Time Charts will change when clicking the Edit button. For example, if you have a time chart running Monday through Saturday and you click Edit the days will change to Tuesday through Sunday. Resolution Upgrade to the latest version of Vista to fix this issue. To work around this without upgrading: Change the First Day of week setting in your registry HKEY_CURRENT_USER\Control Panel\International\iFirstDayOfWeek If you change this to 0, the first day of the week will be considered Monday and editing Time Charts will work.

Issue HASP Error when installing Privilege Licenser 2.01 on Windows XP Machine Service Pack 2 Environment Aladdin Privilege Administrator 2.01 Windows XP SP2 Vista IV Licensing Cause On the most recent versions of Windows XP with Service Pack 2 installed, there has been a problem installing Privilege Licenser 2.01. Upon installing the software a "HASP" error occurs. This is caused by the version of HASP on the computer not being compatible with one Privilege Licenser is trying to use. Resolution Aladdin does not officially support Windows XP SP2, but there is a fix that usually fixes the problem. Go to the following url and download the "HASP Device Driver Commandline Installation" https://supportportal.gemalto.com/csm/?id=kb_article&sys_id=f7055f20db6207c8fe0aff3dbf9619cc Download the file to your hard drive and use the following steps to install the fix: Unzip file to root of your C: drive. Go to Start/Run and type in ‘cmd’. In the DOS window type in ‘cd\’ This will take you to the root of the ‘C:\’ drive Type in ‘cd hinstall’ This will take you to the program folder Type in ‘hinstall.exe –i’ A window will pop up and let you know when the file has finished installing. Close out of DOS by typing in ‘exit’ Run setup for Privilege Licenser 2.01 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 If there is a " in any of the Xenta OP screens, the application will not compile/download correctly. Error message states "ERROR c":\program files\tac\tac menta 4.2.3\temp\opdoc.gop Error in line: xx " Environment Xenta programmable controllers Menta Xenta OP Tree (.dop) Cause The character " is not allowed in the Xenta OP. Resolution Do not use the character " in the Xenta OP tree.

Issue Xenta 102-AX Heat cycling off even with rev. 1.11 Environment TAC Xenta 102-AX v1.11 Cause If nvi_applicmode is bound to another device, it will revert to hvac_cool for a split second every time it receives a packet. If the controller is in heat mode, this is long enough for the heat to turn off and the terminal load to go to 0 for about 3-5 seconds. If it is time to change modes anyway, this is not a problem but if the mode is re-enforced periodically, your heat output will turn off upon that period. Resolution There is no need to re-enforce this command, so make sure that the output is set to send ONLY on a change. Make sure period is set to 0.

Issue Stroke time (throttling range) on Xenta 102-AX VAV controller Environment Xenta 102-AX Cause The stroke time of the actuator differs when the input power is 50Hz versus 60Hz. Since this is not an Imperial vs. Metric issue, LonMaker or Vista does not automatically change this for you according to your regional settings. Resolution The stroke time for the Xenta 102-AX is as follows: 2.4 seconds / degree rotation (50 Hz) 2.0 seconds / degree rotation (60 Hz)   Assuming the damper stroke is 90º: The default setting for damper stroke time is 230 seconds. This is the approximate stroke time when that AC motor is driven with a 50Hz supply. 185 seconds is the approximate time when using a 60Hz supply. The unit will control space temperature regardless but the damper position which is estimated in software will be off when it is anywhere other than 0% or 100%. This will make the damper more aggressive than the program thinks it is. This could make the calibration efforts take longer since the damper might take longer to stabilize the airflow reading. It is recommend to change the damper stroke time to 185 on any site fed by a 60Hz supply. (Unless the damper travel is other than 90°. In that case, set the physical screws accordingly and calculate a new appropriate stroke time based on the seconds per degree values above.)

Warning Potential for Data Loss: The steps detailed in the resolution of this article may result in a loss of critical data if not performed properly. Before beginning these steps, make sure all important data is backed up in the event of data loss. If you are unsure or unfamiliar with any complex steps detailed in this article, please contact Product Support Services for assistance. Issue Dependencies for Vista Server running as a service Product Line TAC Vista Environment Vista Server Cause The Vista server can run into issues if it starts up before other services. Resolution Ensure that Vista Server does not start up before Aladdin Privilege Server by making some changes to the registry. Select the start menu, select run, and type “regedt32”. Once the program opens you should browse to the following path: HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\TACOS\ The key named DependOnService should by default contain the value RPCSS. To add a dependency to this service just modify the value of the key and add the name of the service you wish to start before this one. In the case of Aladdin Privilege Server just add the text “Privilege Win32 Server” to the registry key. Close the registry editor and the dependency will be visible in the services properties window for TACOS. Note: If you need Vista to start late in the boot cycle but you do not have a specific service dependency, as explained above, then choose one of the services which startup last as the data value for the value "Depends on Service". Services commonly selected are Spooler and Messenger.

Issue Cannot register LonMaker plugins Product Line TAC Vista Environment LNS, LonMaker, NL220 Cause If you are having difficulty registering plug ins in LonMaker then you may have corrupted LNS credits. Resolution To check your LNS credit status, run the LNS Server License Wizard which is found at C:\LonWorks\bin\LnsLic.exe If you run the wizard and it displays the Max Credits at zero and Credits Available as zero as well, then your LNS credits have become corrupted. To correct this, select Next in the Wizard so that it displays the PC Key. The wizard provides a button titled "Copy to Clipboard" which when selected will allow you to paste a form letter into an email or text editor. After filling your specific contact information you will want to check the "No Charge" box and the "Replacement Use" box. Before you send the form via fax or email, you also need to provide evidence that your LNS credits have been corrupted. Select Start > Run > and type "cmd" to reach a command prompt. This command will check the status of the LNS credits: checklic nsseng.exe The output of this command should either be printed and sent with the fax or included in the email to the address or phone number shown at the top of the form letter. You should then receive instructions or an application key to correct the problem.

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 Using reference shapes to clean up a LonMaker drawing Environment LonMaker Visio Cause A Xenta 401 controller can have as many as 125 SNVT inputs and 125 SNVT outputs visible on a LonMaker drawing. If every one of these signals is connected with a SNVT binding with graphical lines connecting the source and destination signals it can be rather difficult to differentiate between the connections. Resolution One way to clean up your drawing is to select the "Use References" option when you are in the process of creating your SNVT bindings. This will graphically display a line to a numbered balloon at the source and a numbered balloon with a line drawn to the destination. Since the balloons will contain the same number you can easily identify these as bound together. If for some reason you need to revert a referenced binding to a graphical line, right click on the reference object and select the "Don't Use Reference" option and a normal graphical line will be added. If you have a large network, the destination of the binding is on another page, or the destination is not easily visible, right click on the reference object and select "Go To Reference" to have LonMaker take you directly to the destination.

Issue Displaying SNVT Switch on a Graphic in Vista Environment TAC Vista IV Workstation OGC Graphics Cause When displaying a point of type SNVT Switch on a graphic page in Vista Workstation it's common for the user to see the value of zero when they are expecting the analog value of the SNVT . The reason that this is seen; is due to the fact that when a digital presentation is created on the graphic page and the SNVT Switch signal is browsed in, the attribute field is by default set as "Authenticated." Resolution Proper selection of the attribute field will allow the correct values to be see in the graphic page. To display the analog portion of the SNVT Switch the attribute field should be selected as "Value_(%)" To display the binary portion of the SNVT Switch the attribute field should be selected as "State"  

Issue Which Xenta 101 stencil should be use in LonMaker? Environment Xenta 101-1VF, 101-1VFC, 101-2VF, 101-2VFC, 101-VF Cause Adding a Xenta 101 to a LonMaker drawing. Resolution Please use the following chart when deciding which Xenta 101 stencil to use in LonMaker:   Xenta Unit Stencil 101-1VF 101 101-1VFC 101 101-2VF 101 101-2VFC 101 101-VF 101-VF