Building Automation Knowledge Base

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 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 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 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 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.

Issue When using the PSI software, the Current Status Screen, All Points History and the graphic data display screens do not properly display the text shown on that screen. Environment PSI software Computer Cause The video bios in the computer does not support the graphics mode used by the graphic displays of the PSI software products. Resolution This problem was first identified several years ago on some models of Gateway brand laptop computers. The problem has been observed from time to time, since then, on various computer makes and models. The problem affects both the "Current Status" screen, the "All Points History" screen and the graphic display screens for analog I/O points. There is no software workaround for the problem. The best solution for this problem is to evaluate the computer model before purchasing any quantity of them. Download test program vga_test on The Exchange Download Center, which allows testing of the computer without having to load the PSI software. The test program can be run from any removable media (diskette, CD, memory-stick, etc.) so the computer can be tested at the computer dealer's store or sales office. The text file included in the zip file explains how to run the test and how to interpret the results.

Issue Input scaling issues with the use of 0 to 5 Vdc and 0 (or 4) to 20 Milliamp transducers on a MNB controller. Environment MNB Series Controller application program using Analog Input voltage or current inputs. Cause The resolution of the Analog Input object value is determined by the maximum value that can be processed. If the scaled input range is less than 163.84, the output resolution is 0.01 If the scaled input range is greater than 163.84, the output is an integer value. Resolution When programming the Analog Input object in the WorkPlace Tech Tool, it is important to properly configure the input range and scaled value range for this object. If configured for a 0 to 5 VDC input, the sensor properties must be configured as follows: Input Sensor Type (Type): 5 - Volts Input Low Value (LInput): 0 Scaled Low Value (LScale): 0 Input High Value (HInput): 5 Scaled High Value (HScale): (value, up to 16383, corresponding to 5 volt input) See note below. If configured for a 0 to 20 milliamp or 4 to 20 milliamp input, the sensor properties must be configured as follows: Input Sensor Type (Type): 4 - Milliamp Input Low Value (LInput): 0 or 4 (depending on transducer) Scaled Low Value (LScale): 0 (value corresponding to LInput sensed value) Input High Value (HInput): 20 Scaled High Value (HScale): (value, up to 16383, corresponding to 20 milliamp input) See note below. NOTE: The HScale value should be set to give an output value for the Analog Input object that corresponds to the maximum temperature, flow, cfm, etc. that the sensor is measuring. The resolution of the value processed by this object must be taken into account when setting the HScale value because the input to output scaling and precision depends on this scaling constant. If the HScale value is less than 163.83, the input resolution is two decimal places and if greater than 163.83, integer resolution. An example of where this scale range is critical would be the use of a 0 to 5 volt air pressure transducer measuring an air pressure of 0 to 2 InWC. If the HScale is set to 2, the output would only resolve to 0.01. If the HScale value were set to 2000, the output would be in thousandths of an InWC, giving you an effective resolution of 0.001. Since this value is one thousand times the actual measured pressure, this 1000x scale factor would also have to be taken into account in any use of that value within the application.

Issue Cannot get the serial communications in the Pocket IA software to work on an HP IPAQ H1945 (or other similar Pocket PC devices). Environment Pocket IA software HP IPAQ H1945 Cause Some Pocket-PC devices do not support a serial interface regardless of the availability of a serial cable that is plug compatible with the Pocket-PC device. Resolution The following procedure can be used to determine if the Pocket-PC device supports a serial interface. On the PDA, from the Start menu, select ActiveSync From the Tools menu (in ActiveSync), select Options On the displayed "PC Synchronization" screen, select the "Options" button. On the "PC Synchronization Options" screen displayed, you should see a checkbox with the description "Enable PC Sync using this connection:" with a pull-down selection box immediately below it. Click on the down-arrow at the right end of that box. If the list in the box shows only "`BlueToothActiveSync" and "`USB", the device does not support serial communications and therefore is not usable with the Pocket IA software.

Issue How can the factory default settings for the level 3 password and the two serial ports be restored on a DMS-3500? Environment DMS-3500 Cause Factory passwords are changed and need access to they system. Resolution With power on, remove the DMS-3500 cover to expose the circuit board. Locate the "CONFIG" 2-pin connector on the circuit board (near the green LED labeled SYS). There should be a jumper over one of the pins. Remove the jumper and place it over the two pins. Cycle power to the DMS-3500. When the DMS-3500 is powered up with the jumper shorting the "CONFIG" pins, NOVRAM is cleared and the default settings for the password and port assignment elements are restored. This does not affect the remaining configuration or database for the DMS-3500. Remove the jumper and place it back over one of the pins. The default settings listed below are in effect until set to different values: Level 3 Password: 170 Serial Port 1: 9600 1 7 E P N Serial Port 2: 2400 1 7 E P M CAUTION: Return the jumper to its original position. If this is not done, the new password and port settings will be lost the next time power is cycled to the DMS-3500.

Issue With the MNL VAV controllers, does the integral damper motor perform a self calibration during which it cycles fully closed or fully open? Environment MNL VAV controllers Cause When main power is applied to the MNL VAV controller, the damper motor will cycle to a full closed position. Resolution Automatic Calibration: An internal calibration feature automatically synchronizes the actuator position whenever the actuator is commanded to the full closed (0.0%) or full open (100.0%) position by continuing to drive the actuator in the requested direction for a time period of at least one additional complete full stroke drive time. If during this “end of stroke” drive period the Input value changes to a value within the control range, the output drive to locate the true end of stroke operation is terminated. Drift Compensation Enable: Setting the Drift Compensation Enable configuration property to On (1) compensates for floating actuator mechanical drift whenever the actuator remains at the full open or full closed position for extended periods of time. Drift compensation is done by periodically driving the actuator in the commanded direction for a time period derived from the Drive Time assigned. Drift compensation does not occur whenever the actuator is within the actual control range between full open and full closed. Refer to the Floating Actuator Object in F-27254 for additional information.

Issue Trends no longer collect Alarms have stopped annunciating Programming changes to any segment do not work A reboot of the UltiVist software and/or of the server does not clear up the issues Environment UltiVist server Cause When this behavior appears unexpectedly on a system that has operated solidly for several years, it is likely that the UltiVist buffer files have grown to an unmanageable size. When this occurs, features and functions of the UltiVist software stop working. Resolution As a good housekeeping step, delete all the existing buffer files. UltiVist will re-create new ones when it is re-started. Here's how to delete the buffer files: Exit UltiVist and shutdown all background programs using "Arnold" Using OS/2, delete any & all buffer files on the partition which the UltiVist software is installed. There will be many located in different directories and sub-directories. The buffer files have many different filenames but all have the same filename extension of ".d$$".   CAUTION: On the root directory of the root drive, there exists a file named "WS_ID.D$$". Do NOT delete this file. Restart the UltiVist software.

Issue A SIGNAL computer is missing the security plug or the original installation diskettes. How can they be replaced? Environment SIGNAL computer Cause Purchase replacement part for SIGNAL computer. Resolution Here are the part numbers: SIG-KEY-CHG -> (obsolete) replacement security plug SIG-UPDAT-ENG -> replacement installation diskettes When ordering, provide the existing serial number so that the replacement part can be coded properly. Note: Both items above cannot be ordered for the same job. If both items are lost, a new SIGNAL software package must be ordered.

Issue The computer hardware for a SIGNAL installation has changed and there are no parallel ports for the security plug. Is there a USB key for SIGNAL? Environment Computer without parallel ports SIGNAL Cause Computer hardware limitation prevent the use of security plug. Resolution As noted in Product Announcement PA-00280, Signal support ended on June 30, 2014.  Replacement parallel port and USB keys are no longer available. Yes. Here are the part numbers: SIG-USB-CHG -> (OBSOLETE) Replaces the parallel security plug with a USB version for an existing SIGNAL installation. Contact Customer Service to order this part.  It is not available via iPortal. SIG-USB-KEY -> (OBSOLETE) Replaces the parallel security plug with a USB version for a new SIGNAL order

Issue The SIGNAL serial numbers on the security plug and the first installation diskette are different. Will they work together? Environment SIGNAL computer Security plug installation diskette Cause Information about the date code found on SIGNAL system. Resolution Every SIGNAL serial number is 8 digits long. The first 4 digits are a datecode and the second 4 digits are the actual serial number: Serial# xxxx-yyyy where x = datecode  and y = serial number The first 4 digits will differ if either the original security plug or original installation diskettes were lost and replaced. As long as the last 4 digits are identical, they will work together.

Issue A new battery is required for a DMS-3500. It looks like an AA battery. What is the replacement part for it? Environment DMS-3500 Cause Replace failed battery on a DMS-3500. Resolution Order part number DMS-BATT-001 for any of the following products: DMS-3500 DMS-350A DCM-1000 MSC-MPC-001 MSC-MPC

Issue In a Niagara R2 / Microsmart integration with revision 9 controllers, what's the best way to implement the MsL9Value object? Environment Unknown Environment Cause Unknown Cause Resolution The only way to effectively implement this object is to do the following: Create a virtual AI point in the revision 9 MicroSmart controller. This is a standard AI point with no input address assigned to the INPUT field. Learn it into the UNC station. Create a MsL9Value object in the workspace of the virtual AI point's shadow object. The only property that needs to be assigned is the "logpt". This must be a numeric value 1 to 250. If more than one MsL9Value object is used under a L9 controller, it should be a different number in each. Refer to ibsMS-2.302.514a Release Notes.pdf for additional details of this object. The UNC can now send a value down to the virtual AI which, in turn, can be used as a manual setpoint input to a Loop point or Mode Control point. The MsL9Value object can be linked to a GxText object providing the building operator the ability to change the value from a web graphic.

Issue What's the best way to uninstall SIGNAL software? Environment SIGNAL software Cause Remove SIGNAL software from a computer that no longer need the software. Resolution Steps: Perform two backups - one with executables and one without executables. The backup with executables can be used to restore the entire SIGNAL installation if that is required. The backup without executables is good to have if SIGNAL is already installed on a computer and only job-specific files are restored In Windows Explorer, delete the SIGNAL folder and two files in the C:\WINDOWS directory: signal.ini & bit.ini Remove any shortcuts created on the desktop and in the Windows startup folder. Reboot the computer.