Building Automation Knowledge Base

Issue I can not get my Xenta Groups to come online under my Echelon LTA in Vista classic or Xenta 911, or don't get any alarms from any of the Xenta's. The LTA is online and the LonWorks network is commissioned and online, but the Xenta groups will not come online. Environment Xenta Programmable controllers Xenta 280, 281, 282, 283, 300, 301, 302, 401, 401:B Echelon LTA Vista Classic network Cause The group master may be offline causing the entire Xenta group to also report an offline status. It may also be due to spaces in the naming conventions of the network. Resolution Verify that the Xenta group master controller is online Verify that no object has a name longer than 20 characters LTA name, LonWorks group name, or any Xenta group or Xenta name Verify that there are not spaces in the LTA name, LonWorks group name, or any Xenta group or Xenta name. Use underscores (_) instead of spaces. Verify that there are not \ or / in the LTA name, LonWorks group name, or any Xenta group or Xenta name. Use underscores (_) instead of back slash and forward slash.

Issue Modifying the bypass occupancy override duration of a Xenta 102-AX Environment Xenta 102-AX LNS Cause There are several locations to change the bypass occupancy override duration on a Xenta 102-AX. Resolution To edit the bypass occupancy override duration from the Xenta 102-AX Plug-In: Open the Xenta 102-AX Plug-In Go to the Operating Parameters tab Alter the value under Bypass Override Duration (Hour, Min)   To edit the bypass occupancy override duration from an LNS Browser: Open the LNS Browser The value is represented in the format (days, hours, minutes, seconds, milliseconds).  If it reads (0,2,0,0,0) that would be an override duration of 2 hours. Alter the hours and minutes to the desired value, but leave the days, seconds, and milliseconds at 0.   To edit the bypass occupancy override duration from the Vista Workstation: Navigate to the Xenta 102-AX in the tree structure. Open the VAV_Controller module. Double click the point named UCPTovrdDuration The description breaks out separate values for days, hours, minutes, seconds, and milliseconds.  Alter the hours and minutes to the desired value, but leave the days, seconds, and milliseconds at 0.

Issue Changing ElecTypes on points on a Continuum BACnet controller after the system is saved into the BACnet side can cause major database mismatch problems, COV failures, deletion of EventEnrollment points and graphic points. (Updated 10/27/08) Environment Continuum BACnet Cause Continuum delete the defaults BACnet object type "AnalogValue" in the database and create a new BinaryValue or vice versa. Resolution In a continuum BACnet system, the Continuum BACnet controller creates a BACnet point for every Continuum point that is created on the Infinity side. For instance if you create an InfinityNumeric it defaults as a BACnet object type "AnalogValue" and creates that point in that class in the controller. If that controller is then saved into the BACnet side through Cyberstation it will create that point in the Continuum database under the AnalogValue class. If you then program other controllers to use that point, a COV subscription will be created to the controller owning that point. If you later remember that you wanted this point to be a digital point so you change the BACnet object Type to a BinaryValue. What then happens is the controller changes the class the point belongs to in the BACnet side. When the controller is saved into the BACnet side, Continuum will delete the AnalogValue Bacnet point in the database and create a new BinaryValue point in it's place with a new Object ID in the Continuum database. This creates several problems. The first issue will be that any COV subscriptions for this point will now fail, because the Plain English program that was referencing the point will still try to subscribe to the AnalogValue point, but it is now a BinaryValue point. Data Sharing will stop. The second issue will be that the Save on the BACnet side will find a duplicate point in a different class and it will delete the older AnalogValue point and create a new BinaryValue point. During this process it will also create this point in the BACnet database with the "Full Name" of the object the same as it's Alias. Because the system needs to keep the Infinity side and BACnet side in sync, it will replace the full name on the infinity point with the Alias. Further issues such as this point being used in a graphic, an EventEnrollment, a report, etc.. Will be deleted from these objects because it is now a different point and will have to be reattached to these objects. To avoid these issues You should first disable the BACnet preference "Automatically save new BACnet devices to Database". This will stop automatic database synchronization on the BACnet side when you are creating, deleting and changing points during the site commissioning and programming. Secondly you should create points with the correct BACnet object type before referencing them in a data sharing program. Third you should only save the points into the BACnet side after you have completed the correct point configurations in all classes (Inputs, outputs, numerics, etc). Finally, if after the system configuration and programming is completed, if you need to change a BACnet object type, you should first delete the point from the BACnet side of the database, change and save the point back to the controller, and then recompile any Plain English programs in any other controllers that were referencing that point for a COV subscription. The controller can then be saved back into the BACnet side. If that BACnet point was used in a graphic, or an EventEnrollment it will also need to be reattached.

Issue Error message in Vista System Plug-in: LNS System access failure, (Subsystem: NS,#147) lcaErrNsLicenseViolation 147 LNS license access failure. Product Line TAC Vista Environment LonMaker, NL220 LNS Network Cause Feedback from Echelon on this error message. A variety of conditions may cause this error. Some relate directly to internal licensing components. For example, the license DLLs may not have installed properly, the files that identifies the license (nsseng.exe for the LNS Server, lonmaker.DSL for LonMaker) do not exist, or the Crypkey licensing components (crypserv.exe and ckldrv.sys) are not running properly. You can resolve these problems by deleting the files that may be causing problems, and re-installing LNS. The license DLLs, as well as the crypserv.exe and ckldrv.sys files, can be found in the Windows 'LNS Licenses' folder, and the Crypkey files can be found in the Windows 'system32' folder. Note that you must stop the 'CrypkeyLicense' service and 'NetworkX' driver before deleting the Crypkey files. Certain conditions on the PC operating the license may also cause this error. For example, if the PCs file system is corrupted or low on space, or if the license files have been manually deleted, tampered with in any way, or moved by some disk-defragmentation utilities, this error will occur. You can resolve these situations by ordering a replacement license key. If the PC clock is set back to a time before the creation of the license or before the last time credits were purchased, this error will occur. In some cases, this can be resolved by rebooting the PC. Otherwise, it may be necessary to order a replacement key. The error may occur if the license has been transferred out of the PC, manually terminated, or if there are zero maximum credits. In this case, you need to purchase additional credits for the license. For more information on licensing, see Chapter 13 of the LNS Programmers Guide. Resolution It is very likely that you have corrupted LNS Credits. To determine if this is the case and how to solve it please reference Corrupted LNS Credits.  

Issue Red X in Internet Explorer when attempting to view certain Menta objects in a Xenta 700 Environment Xenta Servers Xenta 701, 711, 721, 731 XBuilder Menta Internet Explorer Cause When importing a Menta object into a Xenta 700 XBuilder project from a file previously created in the normal version of Menta, be very careful with all the comment text within the file. All comment text has to have a defined text type in the file. For example say you had a Menta file with comments throughout that you set all of your font to Arial, bold and 10 point font. Then you created another file and copied the contents of the original file into the second file. You will lose the text attributes of Arial, bold and 10 point font but the normal version of Menta will still display the comments correctly. Now, if you import that second menta file into a Xenta 700 XBuilder database and download the Xenta 700, you will have problems. If any comment text does not have text attributes, Java can not load the file to be viewed in Internet Explorer / Menta viewer and you will get the red X when the file loads. Resolution Go through the entire Menta object in XBuilder, double clicking any comment. Focus efforts on any comments that are known to have been cut and pasted into the file. Check that a font, style, and size it attributed to each comment. Fix and redownload the XBuilder project.

Issue Upgraded Vista 3 to Vista 5 and Digital Points can not be changed on OGC graphic page Environment Vista 3 system upgraded to Vista 5 Digital points OGC Graphics Cause This behavior has only been seen after a upgrade from Vista 3 when following the recommended upgrade path and does not effect every single digital point. Resolution The inability to control a digital point in an OGC graphic page on Vista 5 Webstation can be fixed by opening the offending graphic page in the graphic editor and then saving it back to the Vista DB.

Issue In Niagara R2, how can alarms be viewed and acknowledged using a web browser? Product Line TAC IA Series Environment Niagara R2 Cause Incorrect URL (Alarm Summary) in the address bar of the browser will not display the alarm summary page. The alarm summary page provides a view of exist unacknowledged alarms. Resolution Click below to watch a video document (v-doc) explaining the process of how to View and Acknowledge alarms using Niagara Servlets.  

Issue When running I/NET Seven rev. 2.15, in the I/O Server editor, the "CCTV" button is Grayed out Environment I/NET DVR CCTV Cause Errors occurred during installation Resolution CCTV new DLL file Install Process from I/NET Seven CD (Rev 2.14 and above)  Load the I/NET Seven CD in the CD drive unit (D:\). The CD will try to auto-load, cancel that install. Then go to this location on the CD D:\Support\RVCTL_DLL\Rev 3.6.0.1 Copy the three DLL files (ijl15.dll, rvctl.dll & rview.dll) from the CD. Then paste them into this location C:\Program Files\INET Seven You must register one of the copied DLL files into the Windows Registry. Please follow these steps: Open a “CMD” prompt. Use Start>Run, type cmd and select OK Type the following: Cd\ Cd \Program Files\INET Seven Regsvr32 rvctl.dll You will see a message box with the message “DllRegisterServer in rvctl.dll succeeded” The CCTV Button in the I/O Server is now available to be used for integral DVR’s

Issue Arm/Disarm for I/NET IAS Environment I/NET IAS Cause Configuration Assistance Resolution Are you in the process of using I/Net as an IAS (Intruder Alarm System) and it is not working as you expect? Meaning that you can read a card, but it does not allow access to the door after the pin and code is entered? There is sequence that needs to be followed to ensure that this works properly:  Program door for equivalent reader and PIN if this feature is used. Set the ATS for Sec/Pin Select Features and program these as required Click OK and close out of that Editor, then select Schedules. Verify that the features are available and select the ones that will correspond to the ones set up in step 3 above. Hit OK and exit out. Press # Read card Enter PIN (either enter a leading 0 or press # to complete the string) Press #, the lights should be blinking red/green at this point Press 0 (function code entered in the function editor) Press 1 to Arm or 2 to Disarm

Issue A modem is already connected to a remote site's tap. Settings in the modem need to be changed. Can this be done by dialing into the modem in its present configuration? Product Line TAC INET Environment I/NET remote site communicating via dialup modem Cause The remote site's modem needs to be connected to a PC or Laptop. Resolution No, a modem can not be configured by using its present configurations. Windows HyperTerminal is suggested to edit modem settings.  Refer to TCON 226 (Dial Applications) and TCON 101 (Taps and Repeaters). For emulated tap set up, refer to the appropriate Controller TCON. Issue A new SCU 1284 out of the box that you are setting up and it shows up with an * in Netcon. Product Line TAC INET Environment SCU 1284 Netcon Cause SCU's manufactured before 2009:  There is really nothing wrong with the SCU itself, but there may be an Eprom on the board that is not the correct one. It is the one that is used for the SCU 1280. Newer SCU's: This is generally caused by an incorrect setting in the MCU configuration Resolution Verify that you have the correct MCU configuration settings.  An SCU 1284 should be set to DPU.  An SCU 1280 or 1200 should be set to DIO.  Check Network configuration to see if the issue has cleared up. If it has not cleared up try the following: Delete the item from Network Configuration and allow it to repopulate. Ensure that the DIP switch is set to the correct address. Follow the instructions to reset the SCU located in Reset Instructions for 1200 Series SCU.  Then reload the bin file. If you are still having issues then the best option is to send that unit back and have it replaced with another.

Issue In Niagara R2, how are special events configured within a schedule? Product Line TAC IA Series Environment Niagara R2 Cause Define a single day, consecutive days, or combination of days as special-event days to override weekly and holiday schedule. Resolution Click below to watch a video document (vdoc) explaining the process to configure Special Events.

Issue "Network interface is being initialized" when using Remote Serial Port Driver in Vista Environment Remote Serial Port Driver (RSPD) Cause If using the Remote Serial Port Driver and seeing a "network interface is being initialized" error message in Vista when viewing points, then it might be an issue with the operating system and its Data Execution Prevention (DEP) setting. This problem is most likely found in Windows Server 2003 due to Microsoft using the wrong value as default in SP1. Resolution Verify that the Data Execution Prevention settings are configured for "Windows Services only" rather than "all programs" Reinstall the Remote Serial Port Driver program

Issue Schlage SERIII Weigand Keypad functionality in Continuum for 26 Bit. Environment Continuum version 1.94 and above. Cause The functionality of the Schlage SERIII Weigand Keypad is limited to only sending whatever 4 or 5 Digits are entered on the keypad. It can only do a Site Code or Site Code + Card for 26 Bits in Continuum. This is set on the rotary switches that are on the back of the device. PIN Only and Infinity 37 Bit are not supported by this reader. Resolution To set this up the following procedure can be used: Without powering up the keypad, remove the rear rubber rotary cover for the switches Rotate dials to match Site Code on the top two dials Change the Mode on the lower dial to Mode 2, 3 or 5 for 26 Bit depending on the amount of digits desired Verify that the door that it is being used on is setup correctly for that format Once completed, power up the unit Verify the keys displayed are scrambled after turning on Enter desired digits depending on the mode set up in step 3 to test functionality

Issue SCU in double-address mode and the second station is not responding. Once a card is read at any of the readers, a Reader Entry is displayed in the Transactions Window but the strike never fires. The DO point can be manually controlled through Software but not by any of the readers. Environment I/NET SCU1284 Cause The MCU Configuration must be set to restore the DPU. Resolution Connect to the controller, then go to MCU Configuration. Both of the addresses on the DPU should be Blue. Turn the second address to Internal and exit the editor. Open the Editor again and change the setting to DPU. Perform a DPU restore and try the card again. A Reader Entry should show up in the Transactions Window and the strike should fire, indicating that it is working properly.

Issue Anti-PassBack (APB) Flag functionality Environment I/NET Seven APB Cause Anti-Passback flags will not broadcast across links Resolution Keep in mind the limitations of the APB flag. The broadcast of the APB flag will not cross links nor is it intended to cross links. An NPR is used to connect links to a front end or to another link. The APB flag cannot be broadcast through this device. Only doors and controllers on the same Link (CLAN) as the sending device can receive the APB broadcast. When designing APB systems, ensure that doors for the same zone are all on the same link.  

Issue Importing I/NET 2000 Graphics into I/NET Seven Product Line TAC INET Environment I/NET Seven Cause Have you upgraded from I/NET 2000 to I/NET Seven and the graphics at the site has either stopped working, don’t come up with the correct back ground or bitmaps and the size is all wrong? Resolution There are a few things that you need to verify after the upgrade. Verify that the path for both symbols and bitmaps that was used in I/Net 2000 is the same for I/NET Seven. If this is not done then the pages when opened in I/Net Seven would come up with a blank background or without a bitmap and or symbols. To find the original path (if unknown): Open the Graphics Editor Select File> Open to edit the graphics page  Select View > Page Properties In the Backdrop area (shown below) is the original path of the background bitmap.   If you only have a few graphics then you can edit and modify this for each of the graphic pages  Alternatively make sure all the bitmaps used are still located in the path defined here. All folders with Bitmaps and Symbols are all the same, even if you have to create a new I/Net 2000 folder on the new PC. If you were using 800 X 600 on the original pages, then you’d have to change the resolution on the new PC to the same. If this is not done, then the pages will show smaller and the points would be distorted.

Issue Niagara R2 UNCs using the bacnet-2.305.523b.v1 (or newer) jar file may need  have the bacnet.properties file modified in order to work properly. Environment Niagara R2 UNC with bacnet-2.305.523b.v1 will need the bacnet.properties file modified in order to work properly. If the station is upgraded to bacnet-2.305.527i.v1, -2.305.529.v1, or -2.305.232.v1, the bacnet.properties file modified in order to work properly. New stations created with bacnet-2.305.527i.v1, -2.305.529.v1, or -2.305.232.v1 will have the correct bacnet.properties file  by default. (revised 9-23-2011) Cause Upgrading bacnet jar files. Resolution Two lines near the end of the file must be un-commented by removing the leading # sign. The two lines are: pollHeartbeatCheck=true PollRestartEnabled=true No other modifications to the file are recommended. The UNC must be rebooted to utilize the revised settings. (revised 9-23-2011)

Issue Creating Critical, Priority, Routine, Transaction event pages on a 527/731 Environment Xenta Server Xenta 527, 731 Cause When using Vista to access an I/NET network you have 4 views for the Alarms and transactions. To create these views on the web with a Xenta 527 or Xenta 731 you will need to create event pages with different filters. Resolution Add a new event page in Xbuilder and use the InetAMT filter file. Right click on the event page and select Setup Event Viewer. Click the filter icon in the top left corner and use the following guidelines for the type of page you are trying to create: Critical Alarms - Priority From 1 To 1 Priority Alarms - Priority From 2 To 2 Routine Alarms - Priority From 3 To 3 Transactions - Tenant: * Each event page will have a different filter. To match I/NET or Vista you will need to create four pages.

Issue OPCEnum not at remote OPC server Environment Vista OPC Server Cause Some times the OPCEnum will not exist on remote PC with server installed. In this case, Vista can not find the OPC server and DCOM can not be configured for OPCEnum. Resolution Download and install this small package, and you will have OPCEnum installed. http://ftp.softwaretoolbox.com/support/updates/OPCEnumInst.exe

Issue USB LON adapter from Echelon (PS3 Part Number:ECH-75010R) is not recognized by Workplace Tech. Environment USB LON adapter (ECH-75010R) Workplace Tech Cause The ldv32.dll file (Open LDV driver) loaded with Workplace Tech (located in C:\Program Files\WorkplaceTech directory) is an older version of the driver and it does not support USB interfaces. Resolution Download the latest version of the LDV driver (153-0212-01A_OpenLDV340.exe) The latest version of the LDV driver can be downloaded from the Echelon website (www.echelon.com) and it contains support for USB devices. 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) as "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". The LDV driver is also posted on The Exchange Download Center. Install the new LDV driver Copy the ldv32.dll file from the C:\lonworks\bin directory, and paste it into the C:\ProgramFiles\WorkplaceTech directory. This driver is required for Workplace Tech version 5.6 or earlier. After installing the driver, Workplace Tech will now recognize the USB adapter.