Building Automation Knowledge Base

Issue Is the power supply in the ProView LON Display a half wave or full wave rectified? Environment ProView LON display Cause This information will help power ProView with other 24 Vac devices or if a dedicated 24 Vac transformer is required. Resolution ProView is a half-wave rectified device.  Since ProView has no physical inputs or outputs, there are no precautions to take with power supplies.

Issue Vista Workstation is crashing/shutting down when graphics begin to load. Environment Vista Workstation (observed on a HP blade server) Cause This can be caused by the Video Hardware Acceleration being set to the default value of "High". Resolution Open Control Panel Go to Display Properties > Settings Tab > Advanced Choose the Hardware tab Back the Hardware Acceleration level towards "none" by one notch.

Issue What are the current versions of PSI and related programs? Environment Network 8000 Cause Software tools for Network 8000 devices Resolution The latest version of the PSI software is PSI v4.10. It can be downloaded from here. This release contains a software bundle consisting of 8 different PSI tools including: MicroZoneII (MZII) MicroFlow II (MFII) MicroFlow II Air Balance (MFII-Air Balance) LIM PEM XPSI MicroNet-CI (MNet-CI) MicroNet-CI Air Balance (MNet-Air Balance)

Issue What products are required for a Signal XP installation? Environment Signal XP Cause Part number to order for a Signal XP installation. Resolution There are two options: SIG-80301-XP (20 graphic screen limit) SIG-80302-XP (9000 graphic screen limit) Both options include DMS & Network8000 drivers.

Issue What options are NOT supported by Signal XP? Product Line TAC IA Series Environment SIGNAL software installed in PC Windows XP Professional. Cause Knowing the product features helps sum-up what SIGNAL can manage day-to-day operations. Resolution Below are features not supported with Signal XP: Networking BAS third party support (Andover, Metasys, Trane, …) DataTalk for Windows CTI port expansion card Foreign language capability

Issue For a high temperature application, how can a TS-8204 be programmed to read accurately when connected to a MNL controller? Environment TS-8204 Cause Require instruction on configuring the TS-8204 temperature sensor for accurate reading. Resolution Connect the TS-8204 sensor and install a 2.49 kohm resistor in parallel (1% resistor or better). Set the Analog Input object to Balco and link the output to a Curve Fit object. Curve Fit objects are supported only on controllers with Rev.3. They are not supported on VAV controllers. Configure the Curve Fit X and Y data points as follows: Data Point X1 10.8 Data Point X2 34.5 Data Point X3 57.0 Data Point X4 78.0 Data Point X5 97.8 Data Point X6 116.4 Data Point Y1 200 Data Point Y2 240 Data Point Y3 280 Data Point Y4 320 Data Point Y5 360 Data Point Y6 400

Issue The MicroNet VAV Flow Balance program version 2.0 cannot connect to any MNL VAV controllers on the trunk.  An Echelon USB adapter is being used. Environment MicroNet VAV Flow Balance program version 2.0 MNL VAV controllers Echelon USB adapter Cause MicroNet VAV Flow Balance program doesn't support Echelon's USB driver. Resolution The MicroNet VAV Flow Balance program version 2.0 is not compatible with Echelon's USB adapter.  It does not interface to the new ldv32.dll driver file. The compiled code of this program is the issue. It was written before Echelon released its USB adapter. The only adapters that can be used are the PCLTA-10 / PCLTA-20 / PCLTA-21 / PCC-10 cards using the LonWorks Plug & Play interface.

Issue What's the difference in enabling / disabling the receive-heartbeat for a nvi programmed in any of the MNL controllers? Environment MNL controllers (all models and revisions) Cause Preventing a nvi from dropping to its fallback value. Resolution With the receive-heartbeat enabled, the nvi can be set to fallback to a local sensor or value when communications fails. With the receive-heartbeat disabled, the nvi will hold its last value until the controller either is reset or a new value is received at the nvi. Being a nvi, the value is volatile (held in RAM).

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 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 This video details some of the troubleshooting and diagnostics tools available in the Macrovision/Flexnet License Server LMTools. Product Line TAC Vista Environment LMTools Cause See below for a video tutorial of LMtools diagnostic utility overview.   Resolution

Issue In Workplace Tech 5.x, the properties of any object on the drawing do not appear. The properties option is selectable, but nothing appears. Environment Workplace Tech 5.x Cause Possible cause: COM add-ins is enable cache issue Resolution Try the following two changes: 1. Uncheck the com add-ins checkbox within the Visio security settings. Open Workplace Tech and uncheck the Com Add-ins box in the Visio options area. For Visio 2003, the Com Add-ins is located in the Visio - Tools - Security tab area. Under Macro Security, uncheck the "Enable COM add-ins" checkbox. 2. Close Workplace Tech and search for the content.dat file (typically located under the C:\Documents and Settings\ \Local Settings\Application Data\Microsoft\Visio directory). This is a hidden file, so make sure the search is setup to include hidden files. Move this file out of the directory and run Visio 2003 (not Workplace Tech). This will cause Visio to force a rebuild of the Visio cache. Then close Visio 2003 and open Workplace Tech. The cache may update again.

Issue In LonMaker drawing, the TAC device stencils have disappeared. Environment LonMaker Visio Cause Either the TAC ToolPack was not installed, or the stencil view has been closed. Resolution To open the TAC stencils, click on File menu, go to Shapes and select desired stencil group. If the stencil is not available from this menu, then the TAC ToolPack was not successfully installed.

Issue What is the process required to upgrade application drawings done with Workplace Tech 3.1? Environment Workplace Tech 3.1 Cause Use the application drawings done with Workplace Tech 3.1 on newer Workplace Tech. Resolution The first step is to convert the drawings using Workplace Tech 3.2 Service Pack 1 (and Visio 2000). Then the drawings can be converted using Workplace Tech 5.x and Visio 2002 or Visio 2003.

Issue Vista Webstation 4/5 is installed but only displays HTTP error 500 Environment Vista Webstation IIS Cause If the local host page cannot be displayed then the problem lies within IIS more so than Vista Webstation. Resolution The first thing to do is check if the IIS will display any webpages (http://localhost/ for example). If it will not then follow these steps to correct the matter: From Administrative Tools, Open Component Services MMC and delete IIS related packages (IIS In-Process Applications, IIS Out-of-Process Applications, and IIS Utilities) if the Files cannot be deleted, Right click on the object, select properties, select Advanced Tab, uncheck "Disable deletion". Open a command prompt and navigate to the %windir%\system32\inetsrv folder and enter the following commands: rundll32 wamreg.dll,CreateIISPackage regsvr32 asptxn.dll Restart IIS via IISRESET entered at a command prompt.

Issue Local security policy may prevent Niagara R2 Workplace Pro from running properly. Environment Niagara R2 Workplace Pro Cause The Local Security Policy settings and blocking port 3011 might prevent the WorkPlace Pro from accessing the local computer (Localhost). Resolution Workplace Pro's "Admin Tool" software requires network access to the local computer (Localhost) to allow it to connect to a station. The typical cause is Firewall software or other security software on the computer blocking access to port 3011. If the port in the internal firewall has been opened and "Admin Tool" still cannot run, local security policy may be preventing access to the computer. To verify the local security policy settings, open the "Local Security Policy" function, found under "Administrative Tools" in the Windows Control Panel. Within the "User Rights Assignment" under the "Local Policies", there are two rights that must be configured properly. The first of these two policies is "Access this computer from the network". In the "Security Setting" for this policy, the "Administrators" group must be present. The second of these two policies is "Deny access to this computer from the network". The exclusions in this policy are a bit more complex to configure and requires an understanding of the group membership of the user attempting to run Workplace Pro. To configure this setting, the user's name must not be listed and any security group to which the user belongs must not be listed in the "Security Setting" list. With typical user security settings, the user's name and the "Administrators" group must not appear in the "Security Setting" list. After making changes to the Local Security Policy, the user must log off and log back into the computer to force these policies to be activated.

Issue Error "Initialization Failure" when starting I/NET on a PC that has just been upgraded Environment I/NET Seven I/NET Host Tool Cause Upgrading the version of I/NET on a PC requires that the database also be upgraded. Resolution Verify that the log in name that is used has Admin rights to I/NET Close I/NET and I/O Server, then start DB Create - log in Select the Upgrade Database radio button Force an upgrade on the database to reassign the passwords again Restart I/NET again and it should come up and give you the log in box, put your user name and password and it should start.

Issue Using a Xenta 527-NPR to connect to an I/NET system and cannot see it in Network Configuration, although it can be reached over the web. Environment Xenta 527-NPR Cause There could be several things that are causing this to occur. It may be a setting on the device, or the device may just need to be rebooted. Resolution  Please check the following settings on the device: Verify that the port setting 50069 is opened If it is connected to other controllers, verify that it has its own address, otherwise it will cause LAN Reconfigurations In the I/O Configuration, verify that the device shows up in the Online Devices If these settings are all correct and you are unable to see the device, the following steps will send the device back to boot and then set it up again: Download the most recent bin file for that device from the Web, Type dsh/format when the prompt comes up, Re-enter the IP address when asked Download the bin file to the device again Once completed, put back the reference hosts IP etc so that it can talk to I/NET again. If this fails then return the device and get a replacement.

Issue MNL-800 LON SNVT Programming Standards Environment Workplace Tech Tool software (any version) MNL-800 controller application Cause Problems occasionally arise as a result of improper LON SNVT programming and configuration in the MN-800 device application.  These issues include problems with the re-commissioning of the updated controller and potential network variable mismatch situations. Resolution  The following standards will prevent these problems from occurring. Network variables MUST be manually indexed. This prevents issues with the network variables becoming renumbered when application programming changes are made. (See NOTE 1) Change the application "Program ID" any time network variables are added or removed from an application.  To change the "Program ID" use the WPT Hardware Wizard,  (See NOTE 2) Select Hardware Wizard from Application Menu Click [Next] in MicroNet Setup Wizard screen Change the displayed program ID by entering a different program ID or adding a suffix letter/number. Maximum length is 8 characters. Click [Finish] to save the changed program ID and exit the MicroNet Setup Wizard.  In addition, one method of minimizing the need to repeatedly change the "Program ID" as the application is developed and debugged is to add a few extra common SNVT input and output definitions when first creating the application, leaving them unconnected to the application program.  If one of these SVNTs is needed, it is available in the LON network image (XIF file) and it is not necessary to change the "Program ID". If the MNL-800 controller has firmware version 2.0 (or later) installed, the standard nci network variables do not have to be indexed as the highest numbered SNVTs in the application.  It is perfectly acceptable to number them as the first 17 indexed SNVTs. Note that there are 17 standard network variables (12 nci, 2 nvo & 1 nvi), not just ten nci SNVTs. SNVT variable names should be limited to 16 characters or less.  Longer names are accepted by the WorkPlace Tech programming tool but the names will automatically be truncated by the LON Network Management tool when commissioning the controller. In addition, when programming the MNL-800 applications with the WorkPlace Tech Tool version 5.0, or later, it is not necessary to put each MNL-800 application in a separate project. NOTE 1: If using the WorkPlace Tech Tool version 5.8 or above, you can use the "Object Indexer" to automatically number all the network variables for you.  This tool also includes functions for detecting duplicate SNVT index numbers and for detecting gaps in the assigned index numbers. NOTE 2: If using the WorkPlace Tech Tool version 5.8 or above, you can set an option in the Hardware Wizard to automatically generate a new ProgramID and reindex the network variables when compiling the application.  Please be aware that this automatic generation of the ProgramID will require the Echelon network image for this device to be updated in any Echelon compatible network management tool.  Please refer to the documentation for the network management tool to determine what actions will be required. For example, if Niagara was used to manage the LON network, then the old shadow will need to be deleted, a new one added, and the device points rediscovered and the device re-commissioned.  

Issue Echelon LON interface card installed in computer is not recognized by the LonWorks Plug and Play utility nor by the I/A Series software installed on the computer. Environment LON interface card PC Cause This problem is caused by not installing the Echelon driver for the PCLTA-10 / PCLTA-20 / PCLTA-21 / PCC-10 card before installing the card into the computer. Resolution Steps 14-20 of this procedure can be used to test the PCC-10 lon card and driver if the proper driver is believed to be installed.     Before attempting to reinstall the driver, verify that this Echelon file is available:  "OpenLDV340.exe", "153-0117-01C.zip" or "PCLTA21 Win2k XP.exe". If the .zip version is available, extract the .exe file from that .zip file, to the desktop.   To correct the problem and install the proper driver, use the following procedure. Open the Windows Control Panel and select SYSTEM then select the hardware tab. Select the Device Manager button. Check to see if the Echelon card is already installed -- look for the entry "Lonworks Network Interface" and click on that entry to open it then select the "Lonworks xxxx Network Interface" choice that was just displayed. (then continue with step 5 below.) If the Lonworks Network Interface was not shown, look for an entry with a yellow question mark -- a Lonworks entry so marked should be found. Select that entry. Right click on the Lonworks entry just selected and select "Uninstall…". Follow the prompts to uninstall the driver. Shut down Windows and power down the computer then remove the Echelon card from the computer. Power up the computer. Log into the computer using an account with full administrative rights. Run the Lonworks driver application file ("OpenLDV340.exe", "153-0117-01C.zip" or "PCLTA21 Win2k XP.exe") that was downloaded and extracted. This installs the driver into Windows. After the installation completes, close the prompt indicating that a reboot is required then shut down Windows and power down the computer. Reinstall the LON interface card. Power up the computer and log into Windows. The system will indicate that new hardware has been installed and will attempt to locate a driver for the new hardware. Allow the system to install the card driver. When the hardware installation wizard finishes, it may indicate that the computer must be restarted before attempting to use the new hardware. If so prompted, shut down windows and restart the computer, logging in again as an administrative user. Open the Windows Control Panel and select (double click) the "Lonworks Plug 'n Play" entry. Verify that the device selected is LON1. If not already selected, specify the NSIxxx application in the NI Application selection box. Click the "Diagnostics" button. Click the "Reset" button then click the "Restart" button. Click "Yes" to reset the card to its boot state. Click the "Test" button and verify that no errors are indicated. Click the "OK" button to leave the Diagnostics screen then click "OK" on the Lonworks Plug 'n Play screen to save the configuration information and exit the utility. The Echelon LON Interface Card is now ready to use.