Building Automation Knowledge Base

Issue The following error message appears when adding a LON application to a project in WorkPlace Tech 5.x from the pre-engineered "WPT Applications" zip file: AppXMLAddon Error Code: -2032465751 Code meaning: Unknown error 0x86DB08A9s. Environment WorkPlace Tech 5.x WPT Applications.zip Cause Workplace Tech encountered one or more values in the application that contain invalid characters. Generally, the most common value that causes this issue is the nciLocation SNVT. The value that should be in this SNVT is "/0", but through a previous Microsoft Visio conversion, it was replaced with a "vertical bar" character. Resolution Locate the invalid characters Replace them with valid ones or delete them. Once this is done, select "Application - Rebuild Application" from the drop-down menu.

Issue Trying to connect to a Xenta 527 over the web and cannot see it in I/NET, but can access it over the Ethernet Environment Xenta 527 Cause This occurs mainly because the reference host of the Xenta 527 and the Host PC are not seeing each other. Resolution Verify that all applicable ports are open, especially #50069, all C-Lan terminations are correct, # 19 and 20 on the Xenta 527. Start I/NET on the Host PC, open I/O Server, verify that TCP/IP is enabled. In the reference host, put in the IP address of the Xenta 527then save the settings. Connect to the Xenta 527 over the Ethernet, select Configuration Profile and put the IP address of the Host in reference #1 then save the settings. Restart both the Host and Xenta 527. Open I/O Server again then click on NP Routers and verify that the Xenta 527 appears in the table. Close this, then go to Edit Host Computer, Network Configuration, penetrate the link, it should be the Xenta 527’s name, save it. Penetrate the controller and its sub-lan devices should be seen as well, save all at this point. Close out of these editors and then connect to the controller, go to Summary and verify that you can control the points.

Issue Using the same power supply (transformer) for a Xenta 527 and a 7798 I/Site LAN comes down and there is no communication to any other devices. Environment Xenta 527 7798 I/Site 7798C 7798B Cause This is because it has blown the RS-232 expansion board on the 7798 I/Site due to a voltage overload The Xenta 527 must be powered with either half wave AC Power or DC power.  (Half wave power connects earth ground 1 leg of the AC power to the controller.) The 7798B and the 7798C can use either full way power or DC power. It is recommended to use a separate power supply for each device Resolution If required you can power the 7798C and the Xenta 527 on the same DC power supply, provided all devices are properly grounded.  This is not recommended as each devices specifies a separate power supply. To correctly wire these devices follow these instructions. You will need to send your damaged 7798 in for repair Add a second transformer or power supply to power the 7798 controller Ensure that the Xenta 527 is properly grounded. Please reference TCON190 (page 15)  for the 7798B or TCON311 (page 9)  for the 7798C wiring diagrams.  Reference this cut sheet for the Xenta 527 which shows that G0 must be grounded.

Issue Lon Tunneling does not function with Workplace Tech 5.7. Environment Workplace Tech 5.7 Cause In order for Lon Tunneling to work, the Echelon OpenLDV Network Driver, version 3.4 is a requirement. Resolution To determine what driver version is currently installed, follow the steps outlined on page 7 of the WPT 5.7 Installation Instructions (F-27367-4). If "Echelon OpenLDV 3.4" is not listed, install the Echelon OpenLDV Network Driver software. The installer file for this driver is provided on the WPT 5.7 CD or it can be downloaded from The Exchange Download Center: 153-0212-01A_OpenLDV340.exe. Alternatively, it can be downloaded from the Echelon website (www.echelon.com). In order to download from Echelon’s website, a (free) user account is required. Once it is created, proceed to “Recommended Downloads” and the LDV driver will be listed (towards the bottom):"OpenLDV 3.4 Network Drivers for Windows Vista/XP/2000/Server 2003 (includes drivers for i.LON 10/100/600 RNI, PCLTA-20/21, PCC-10, and U10/20".

Issue How many BACnet objects can a Niagara R2 UNC / Niagara G3 ENC station support? Product Line TAC IA Series Environment Niagara R2 UNC Niagara G3 ENC BACnet Cause Performance degradation will occur if exceed the BACnet objects quantity limits. Resolution A limit of 1500 applies to UNC BACnet point shadow objects and to ENC proxy points. This limit refers to all BACnet point shadow objects and proxy points, regardless of type (BACnet/MSTP, BACnet/IP, or BACnet/Ethernet). Exceeding this limit will result in degraded performance. For more information, review Appendix A of the MicroNet BACnet Wiring, Networking, and Best Practices Guide (F-27360).

Issue After installing SigmaX version 5.0 or later, when running the software an error message reports a missing DLL. Product Line Satchwell Sigma Environment SigmaX version 5.0x, 6.0x and 7.0x Cause System Path variable is missing C:\Sigma\Bin in Environment Variables Resolution Make the following modification to the PC's System Properties. Note: This addition is only required on machines running SigmaX.   For Windows XP and Windows 7 Right click the My Computer icon on the desktop and select Properties Choose the Advanced tab and select the Environment Variables button From the System Variables section, highlight Path and select Edit The statement ‘;C:\Sigma\Bin’ must be added to the end of the Variable value line For Windows 10 In the search bar type and type 'environment' and go to 'edit the System Enviroment Variables' Bottom right go to Enviroment Variables In the bottom window 'System variables', find 'Path' and double click In the 'Edit environment variable pane - create a 'New' variable and add in c:\sigma\bin

Issue Unable to save a TGML graphic in a Vista database. Save error Error HRESULT E_FAIL has been returned from a call to a COM component. Product Line TAC Vista Environment Vista 5 Workstation TGML Graphic Editor Cause This message occurs when saving a graphic to a folder that has a "/" in the name. Resolution Change the name of the folder to not include a "/"

Issue Opening java or TGML graphics is very slow or they don't open at all. You may also have various java error popups. Environment TGML Graphics Cause The Java applet is limited to the amount of memory it is allowed to use. This will also limit how much memory java or TGML graphics are allowed to use, and can slow the rendering. Resolution It is possible to expand the amount of memory the Java applet has access to, and that seems to help in some cases. To increase this memory, do the following: Open the Control Panel in Windows and double click on "Java" Click the tab "Java" In "Java Applet Runtime Settings", choose "View" Find the most recent Java version runtime line (1.6.0_11) and double click on the "Java Runtime Parameters" box and add "-Xmx300m". This sets the Java maximum heap size to 300 MB. For some unknown reason, some computers with large amounts of installed memory are limited to how much memory they can assign to their Java VM. If you experience problems, just reduce the "300" to some smaller number (like 250, 200, 150, etc). However some computers have no problems setting the value to "1000". This procedure must be done to each computer individually. Also, remember to close all Internet Explorer windows for the changes to take affect.

Issue What's the difference between ordering a Niagara R2 BACnet Supervisor and ordering a Niagara R2 Web Supervisor with an Open Systems Driver that includes BACnet? Environment Niagara R2 Cause Information about the option of implementing a Niagara R2 BACnet supported. Resolution When purchasing a BACnet Supervisor (IA-BAC), support for 500 BACnet points is included. When purchasing an Enterprise Server (IA-ENT-1) with the Open Systems Driver (IA-DRV-OSD), support for 25 BACnet points is included. Support for 500 BACnet points can and must be ordered separately (IA-BAC-500).  Functionally, they are equivalent. Both will run a station that supports up to 4000 BACnet/IP and BACnet/Ethernet points combined. For integrating using BACnet/MSTP, a UNC must be added.

Issue Error using webClient webpinpoint, "You have been assigned a web object but do not have the appropriate permission to view it" Graphic option isn't available in the web browser client, other options are there. Environment webClient Windows XP Windows Vista Windows 7 Windows Server 2003 Windows Server 2008 Cause There are 2 different types of webClient. PM for security and PRO for security and HVAC Resolution WebClient Pro and webClient Personnel are two different products. The Personnel version doesn’t allow for graphics. Verify the serial number of the security key with the Repair Department to determine if the Personnel product is enabled on the key. If so, request a cookie upgrade for the key.

Issue Erie controllers SR-201, 301,601, 201-AT, 301-AT, and 601-AT. Voltage apparent on unpowered Relay Terminals. Environment SR-201 SR-301 SR-601 SR201AT SR301AT SR601AT Cause The large foil surfaces used to carry the high currents of the switched loads of these control boards act as antennas causing the DMM to read a voltage signal. Resolution The voltage as read L2 to X1 approximately 12 VAC and L2 to X2 approximately 25 VAC is not harmful to humans or equipment and will not affect the operation of the unit. When determining if these induced voltages are present, all wiring except power wiring to L1 and L2 should be disconnected.

Issue NEMA 4 classed DuraDrive actuators cannot be used with the VB-7323 diverting valves Environment NEMA 4 DuraDrive actuators VB-7323 diverting valves Cause Which NEMA 4 classed DuraDrive actuators can be used with the VB-7323 diverting valves Resolution There are no NEMA 4 solutions available. Consider using the MA-318 or 481 for two position applications. No modulating spring return options are available but non-spring return gear train actuators with AV-391 (150 pound plungers) can be used when the AM-363 gasket is added.

Issue Configuration help for doors on a 1284, 7920, or 7910 Setting up Access Control on an SCU or DPU Can’t remember if Dip Switch 7 is up for the Card Number equals Individual Number without a MIP on the DPU or was that Card Translation Checked box the issue Product Line TAC INET Environment I/NET Seven Access Control SCU 1284, DPU 7920, DPU 7910 Cause Configuration errors or failure to remember how to properly configure the door editor Resolution SCU 1284 Yes → Large Number Format Yes → In Door Editor, CHECK Using Card Translation     ↓No   ↓No             Card Number equals individual scheme Yes → In Door Editor, UNcheck Using Card Translation     7920 Yes → MIP Board Yes → Using Large Numbers Yes → In Door Editor, CHECK Using Card Translation ↓No   ↓No   ↓No             In Door Editor, UNcheck Using Card Translation         EPROM Yes → Large number format Yes → Dip Switch 7 on         ↓No             Card Number = Individual Number Yes → Dip Switch 7 off 7910 Yes → EPROM Yes → Large number format Yes → Dip Switch 7 on         ↓No             Card Number = Individual Number Yes → Dip Switch 7 off

Issue How to uninstall Privilege software Product Line TAC Vista Environment Vista IV Licensing prior to 4.25 Aladdin Privilege Administrator 2.01 Cause Need to completely remove a Vista IV installation including all traces of Aladdin Privilege Administrator. Resolution Version 2.01 is mentioned in the description below, but process is similar with other Privilege software versions. Also, process may look slightly different in different Windows versions. To remove: Run the uninstaller for Privilege 2.01 Go to the Windows Control Panel and if there is still an entry for Privilege Licenser - if there is - remove it Delete the Privilege directory (default location: C:\Program Files\Aladdin). Go to the system32 folder and delete the directories PLog and PData. From the same folder, delete the files: PLInst.exe, PLockDiag.exe, PLServ.exe, PLAdmin.dll, PLCLNT.DLL, PLEsd.dll, PLInstall.dll, PLLG.dll. Run Regedit, go to HKEY_LOCAL_MACHINE\SOFTWARE\Aladdin Knowledge Systems and delete Privilege Licenser. Go to HKEY_CURRENT_USER\Software\Aladdin Knowledge Systems and delete Privilege Licenser. Reboot and reinstall.

Issue Error "License run-time information is damaged. Contact software vendor. PSU ID: XXXXXXXX PSU Type: Unknown subfamily: 255" PSU ID on the sticker and what is Dongleutil reads out of the dongle do not match. Product Line TAC Vista Environment Aladdin Privilege Administrator 2.01 Vista IV Licensing Cause Mismatch in dongle has to be corrected. Resolution The PSU needs a master reset. This is done at Solution Team in the Malmö office. Contact Product Support to create a case ID to get instructions on where to send the PSU.

Issue DPU Restore, when and what information is downloaded to the Door Controllers Product Line TAC INET Environment TAC I/Net Seven site with DPU or SCU 7910, 7920 1284, 1280 door controllers, download Cause A variety of errors with door access can be attributed to download individual information to the door controller(s). Resolution When changes are made to any one of the following, a download is triggered to each of the DPU/SCU controllers. Name Group Issue Level Card Number If using DPU Restore, remember that during the DPU\SCU restore, these are the items that are being downloaded. Cold Start signal - followed by point data from the SLI Tamper Parameters (SCU Only) Translation parameters Tenant information Floor Mapping\Personnel data for each Elevator\Door Secondary Time Schedules End of the Cold Start process After the Cold Start ends, then the Big Card Numbers (HEX) are restored from the SLI to the DPU\SCU controllers

Issue Error number :      17040 Error description: Invalid format. (Subsystem: LNS, #40) Any tab except "Status" has some strange values. Trying to view or edit some values results in this error. Environment Xenta 102-AX Plug-in Xenta 104 Plug-in LonMaker NL220 Cause A value inside the device has been set with an invalid value.  It could be through an LNS browser, through an M/STAT or just through some glitch when setting a parameter. Resolution The device will need to be recommissioned using default values. CAUTION:  Recommissioning a device with default values will erase any user defined configuration parameters.  Record all important data for the box:  duct area, airflow setpoints, operating parameters, etc. Right-click on the device in the LNS Management tool.  In LonMaker, select Recommission. In NL220, select Repair. Choose "Manufacturer Defaults" for the initial values.  Click OK. Launch the plug-in again.  The values should now be able to be changed to the desired value.

Issue On a fresh install of LonMaker Turbo, inactivated, the first time trying to open a drawing you may get the error:  The object was not found (Subsystem: LNS, #6) Extensions ‘Echelon_LMW_Demo’ Environment LonMaker Vista LNS Cause If you specify a network name with trailing spaces, the LonMaker tool will report an LNS #6 error (object not found), and report an unexpected error. An object has been requested by name or index that could not be found in the databases.  Typically, this would be a request from a LNS collection object with a bad name or index. It should be noted that this error can also occur in some implicit assignments. For example, if the network interface to be used has not been explicitly assigned to the appropriate property, LNS will continue using the network interface previously assigned to the ActiveRemoteNI or NetworkInterface property, respectively. In such a scenario, this exception could occur even though no explicit assignment has been made, indicating that an implicit assignment maps to an unavailable object. A monitor set may be created while offnet (System.MgmtMode is set to lcaOffNet); however, a monitor set cannot be opened while offnet. Furthermore, attempts to query the MonitorSet.IsOpen property will get the error "The object is not found (Subsystem: LNS, #6)" when offnet Resolution Getting the activation code and activating the install should clear the error.

Issue Migrating from LonMaker to NL220 Environment LonMaker NL220 Cause Changing LNS management tools. Resolution If both Lon Maker and NL220 reside on the PC: Migrating from LonMaker (or other LNS management tool) to NL220, all that is required is the LNS database.  NL220 will recognize the LNS Databases which have already been created in LonMaker. Open the database in NL220. There is no need to recommission online devices, so no credits need to be re-purchased.   If the LNS must be transferred onto a PC that only has NL220 installed: Take a copy of the Folder located in the directory Lm/Db/[name of project]/files Place this folder in C:\NLPrj\[name of project]\files Create a new Project in NL220 Name the project Select 'open an existing database' Browse to the Project path (C:\NLPrj\ ) Select OK. NOTE: Migrating from NL220 (or other LNS management tool) back to LonMaker is a little less seamless because LonMaker utilizes proprietary Visio drawings for viewing the network, and these are not native to the LNS database.  Viewing the network may be difficult with the automatically generated Visio drawings.

Issue Could not initialize the LonTalk stack. Environment LNS NL220 LonMaker Vista Cause Could not initialize the LonTalk stack. Resolution First, close the LonMaker tool, then test your network interface using the LonWorks Plug 'n Play utility found in the Windows Control Panel. Once there, press the "Diagnostics" button and then press the "Test" button. If you get a "Failed" message similar to the following: ------------------------------------------------------------------------------ LonWorks® PCC10/PCLTA10/PCLTA20 Device Driver Version: 2.01 Card Type: PCLTA-20 / LMPA Driver Status:           Number of Free LTA Output Buffers-            Non-Priority: 0, Priority: 0           Loaded Image Size: 16384           Interrupt Count: 17333 ------ Network Interface Node Status ------ ** Failed ** ------------------------------------------------------------------------------ Then go back to the main LonWorks Plug 'n Play dialog and change your NI Application to something other than what is currently selected. Click on the "apply" button and do the test again. Don't forget to change it back to its original NI Application. Remember that the LonMaker tool can work with either the "NSI" or "VNI" NI Application images, although "VNI" is preferred due to higher performance. You may also want to try to "reset" and "restart" your network interface card and driver from the "Diagnostics" window. Once you stop getting the "Failed" message and see the network interface statistics, you should be able to open the network from the LonMaker tool. The following is an example of a successful "Test" result. Some of the counts may not be zero, but that should not be a problem unless it increases rapidly as you test again and again. If that happens, it can be due (most of the time) to one of three problems: wiring connections, excessive noise, or excessive traffic on the network. ------------------------------------------------------------------------------ LonWorks® PCC10/PCLTA10/PCLTA20 Device Driver Version: 2.01 Card Type: PCLTA-20 / LMPA Driver Status:           Loaded Image Size: 57344           Interrupt Count: 20345 ------ Network Interface Node Status ------ CRC Errors:                  [00000] TX Timeouts:                 [00000] Lost (APP) Messages:         [00000] Missed (NET) Messages:       [00000] Most recent error:           0 Reset Cause:                 External ------------------------------------------------------------------------------