Building Automation Knowledge Base

Issue PE program that locks a door getting disabled with error "Unable to lock door while timed unlock is in effect" or "Unable to lock door while permanent unlock is in effect" Environment CyberStation CX9780 ACX5720 ACX5740 Cause Door has been timed unlock. When a door is unlocked via the PermanentUnlock flag or the Timed Unlock attribute, PE programs are not allowed to re-lock the door. Resolution From the command line print the permanent unlock attribute of the door, if attribute is true re-set it to false. The name of the attribute is PermanentUnlock From the command line print the timed unlock attribute of the door, if attribute is > 0 re-set it to 0 The name of the attribute is TimeUnlock Add a line E to the program to keep it from getting disabled.

Issue Every time the Time Sync service runs, an error is generated in the Application Director console window.  The message reads "Error:  NTP in use, RFC868 clients ignored".  What is NTP and why is the system reporting the error.  I have the Time Server function configured in the same manner and with the same servers that I always use. Environment I/A Series G3 release 3.4 or newer Cause Both the "Time" and "NTP" time sync services have been enabled in the system. Resolution The I/A Series G3 software was modified in Release 3.4 to allow the use of the use of NTP protocol time servers in addition to the older "TIME" protocol time servers. If the I/A Series G3 system software detects the use of the more accurate NTP protocol, the error message "Error:  NTP in use, RFC868 clients ignored" is reported and the attempt to synchronize the time to the TIME server will be ignored. The use of "TIME" protocol servers and clients are configured in the "TimeSyncService" service in the station services.  The use of "NTP" services is configured in the "NtpPlatformServiceQNX" under the Platform Services.  If you desire to use the TimeSyncService instead of NTP, you need to disable the "NtpPlatformServiceQNX" by opening the "Ntp Platform Service Editor QNX".  To disable the service, set "Enabled" to FALSE as shown below.

Issue Is it possible to override interlocked doors with a user card? Product Line EcoStruxure Security Expert Environment Security Expert Door interlocking Cause Require an option to allow specific users to access through locked down interlocked doors. The "User has Super Rights" option in the User record seems to provide this since it notes that one of the permissions this option provides is to "Unlock doors that have been locked down". user has super rights Resolution Unfortunately the User has Super Rights option does not work in this scenario. The option was never designed to work with interlocked doors.  To request for this feature to be implemented, a new feature request can be made with your local solution category management team.

Issue WorkPlace Tech is connection to the site via VPN. An ENC-520 on site is setup as a BBMD device. The ENC and MNB-1000 are on the same subnet. The ENC’s address is entered in the “Access a remote internetwork” in WPT Commissioning Tool. WorkPlace Tech initially discovers the MNB-1000 device. The MNB-1000 is displayed in the Commissioning Tool, but grayed out. The MNB-1000 controller eventually displays the Lost Communication Icon. Environment WorkPlace Tech Commissioning Tool - all versions Cause The default gateway is incorrectly set in the MNB-1000. Resolution MNB-1000 controllers must have a valid IP address, Subnet Mask address and Default Gateway address for the communication ports to function properly.   Use WorkPlace Tech Commissioning Tool to set the correct default gateway IP address in the MNB-1000.

Issue The Xenta Group Master is offline in Vista Workstation but  the rest of that masters group is online. Environment Workstation TAC Vista System Plug-In Cause The issue occurs most of the time when dealing with a system that is using a Loytec NIC 852 card. Somehow the address table entry for tag_0 can become corrupted, lost, or not updated.  Resolution Open up the TAC Vista System Plug-In through LonMaker or NL220. Click on the LNS Network menu > Create Group Bindings. Now go to the TAC Network menu and click on Commence Communication. Once the Commence Communication operation is complete, click Close. Update Vista Database. Refresh the system tree in Vista Workstation.

Issue Getting "Failed CreateDNWACServer. Cause: Object reference not set to an instance of an object. URL: “http:///DNWACServerFactory/WACServerFactory.soap" when trying to open a graphic through WebPinpoint with Continuum version Product Line Andover Continuum Environment Windows XP Windows Vista Webclient Windows Server 2003 Windows Server 2008 Cause Configuration of mime types and correct path to the file must be made Resolution Make sure Microsoft .Net 2.0 is not installed as this will cause the above error message. We did not support Microsoft .Net 2.0 until the 1.74 release. Check to make sure that on the machine that the browser is being run from has the NetBIOS over TCP/IP enabled. This can be found in the advanced properties of the TCP/IP settings on that machine. Make sure that “Directory Browsing” is enabled for the NewGraphicsFiles in the IIS configuration. This can be found by running the IIS Service manager and expanding the explorer until you see the NewGraphicsFiles virtual directory. Right-click on the virtual directory and select properties. There will be a checkbox for “Directory Browsing” in the middle of the page, make sure this is selected. On XP add the aspnet to the DNWACServerFactory folder security tab on the folder.

Issue In declaring a variable, the binding qualifier PUBLIC in a BACnet b3 controller's script program such as "Numeric Public numPoint" gives the error "Unsupported feature" when saving script program. Product Line EcoStruxure Building Operation Environment AS BACnet b3 i2 Infinet controller Script Numeric Public Cause Need Numeric variable to be readable and writable in BACnet b3 or Infinet i2 controller script programming. Resolution The Public qualifier is supported in SmartX servers (AS, ASP, ASB) and SmartX IP controller script program only.   For BACnet b3 or infinet i2 controller script programming, use Input and Output qualifier and bind to the same object's property outside the program. .

Issue Endura 2 Integration in Continuum V1.92.  Having issues with VideoLayouts not showing the video properly but displaying the date and time properly. Environment CyberStation 1.92 Endura Video Cause Revision incompatibility Resolution See document "Andover Continuum Software and Pelco Video Compatibility Matrix" for video products that can be integrated using Andover Continuum’s video features.

Issue Getting error "Unable to find an object in the database.Root\FolderName\OldAreaName" when creating new Personnel, in Personnel Manager. Following a change to Area names, the Personnel Profiles no longer contain these changed Areas. Product Line Andover Continuum Environment Continuum 1.81 and above Cause Do not rename Areas without removing/replacing them from the Personnel Profile. Resolution Always remove Areas from Personnel Profiles before changing the Area name, then replace Area If you simply rename the Area without removing that Area from the Personnel Profile, then the Personnel Profile will either get corrupted or the changed Areas will get removed from the Personnel Profile. If the Personnel Profile is corrupted then it needs deleting. Delete from Personnel Manager, if the corruption is such that it cannot be deleted from Personnel Manager, see Cannot delete personnel profiles Once the Personnel Profile deleted, recreate as required.

Issue How are the existing Areas manually assigned to a Personnel object affected when that Personnel is referenced to a Personnel Template that has existing Areas set to InheritFromTemplate. Environment Continuum Access Control Cause An existing site had manually assigned Areas to Personnel and wants to consolidate common Areas for groups of Personnel by using Personnel Templates with pre-defined Areas. It was unclear what would happen to existing Area assignments once the Template was assigned to the Personnel. Resolution If you have manually assigned Areas to a Personnel and then attach a template, the AreaLinks in the Template will "compliment" the Areas you already had assigned to your Personnel. It will add any additional Areas in the Template. As well, if you update your Template and add new Areas to it, these get pushed to all Personnel that are linked to that Template. If you delete Areas from the Template then this gets pushed out as well, unless the Personnel already had the Area assigned manually - in which case they retain access to it. I guess the simplest way to think of it is that the relationship is like a binary OR operation. Area Assigned = "Manually Added" OR "Defined in RefTemplate"

Issue MN-Sx, MN-SxHT sensors calibration Environment I/A Series MicroNet Sensors (MN-Sxxx series) Cause Sensor readings inaccurate Resolution 1. Calibration in WorkPlace Tech application program Calibrate the temperature and / or humidity offset in the Hardware Wizard. Enter a positive or negative offset value. For examples, -0.5 or 0.5. The WorkPlace Tech application has to be compiled and downloaded to the controller for the offset to take effect.   2. Calibration via sensor's Diagnostic Mode (only available in MN-S3xx, MN-S4xx, MN-S4xx-FCS, and MN-S5xx) To enter the sensor's Diagnostic Mode, press the Up and Down buttons simultaneously until the sensor enters the Diagnostic Mode. Press the Override button (while still in Diagnostic Mode). This will lead you to a display where you can enter an offset for sensor calibration. Allow the sensor to return to the normal display (takes about 30 seconds).

Issue When copying a graphic point, symbol, bitmap, table or anything from one page to another, everything is placed to the upper left of the new page and is all jumbled up. The user has to move each one separately and the attributes do not remain the same. In I/NET 2.40 and above Windows will still cause text object to be placed in the upper left hand corner. This also occurs in the Windows Paint program. Environment I/NET Seven revision 2.16 and higher, but below 2.40 I/NET 2.40 and above Cause Copying a graphic point, symbol, bitmap, table or anything from one page to another. Resolution This issue is resolved in I/NET 2.40.  If upgrading is not an option: Contact PSS and request the patch that is available to fix this issue. Copy the files into the root directory of I/NET Run the graphic again Workaround for I/NET 2.40 and above Group the objects you wish to copy by pressing CTRL+G Copy the group Paste the group and move it as desired Ungroup the objects.

Issue How to select a platinum sensor compatible with the Analog Input (AI) object in WorkPlace Tech. Environment WorkPlace Tech I/A Series Lon (MNL) controllers I/A Series BACnet (MNB) controllers Cause Sensor manufacturers provide platinum sensors with different Temperature Coefficient of Resistance (TCR). Resolution The Analog Input (AI) object supports 1Kohm platinum sensor with Temperature Coefficient of Resistance (TCR) equal to 0.00385 OHM/OHM @ °C. Check manufacturer's datasheet and select sensor with TCR of  0.00385 OHM/OHM @ °C

Issue Satchwell ZRM series or AZ2451 Rotary Actuator requires replacement.. Environment Satchwell ZRM Rotary Actuator installed on Satchwell MB Series Rotary Shoe Valve Body. Satchwell AZ2451 Rotary Actuator installed on Satchwell MB Series Rotary Shoe Valve Body. Satchwell ZRM Rotary Actuator installed on Satchwell MC Series Step Controller. Satchwell ZRM Rotary Actuator installed on Satchwell MD Series Step Controller. Cause Obsolescence of Satchwell ZRM series and AZ2451 Rotary Actuator Resolution Please check number of wires connected to ZRM Actuator as this will assist in determining a suitable replacement. The Satchwell ZRM Actuator or AZ2451 would normally have been installed on a Satchwell MB Valve Body. The Satchwell ZRM Actuator could however have been installed on a Satchwell MC or MD Series Step Controller. The Actuator comprised a 6 wire electrical connection enabling it to be operated from a Satchwell Z Monotronic or CZT Climatronic Proportional Controller as follows :-  Terminal 1 – Open signal Terminal 2 – Close signal Terminal 3 – Common  Terminal A – 135 ohm Feedback Potentiometer – winding Terminal B – 135 ohm Feedback Potentiometer – wiper Terminal C – 135 ohm Feedback Potentiometer – winding 1. If all 6 wires are connected then the ZRM Actuator or AZ2451 may be replaced by one or other of the following SE Actuators :- MD20B-24 + Linkage Kit 914-1071-000 from Schneider Electric and an accessory kit  P140A from Belimo 2. ALTERNATIVE REPLACEMENT If in some installations, 3 wires are only connected to the ZRM Actuator. Terminal 1 – Open signal Terminal 2 – Close signal Terminal 3 – Common In such instances the ZRM Actuator or AZ2451 may be replaced by the XRM3201 or MD10B-24/MD20B-24 + Linkage Kit 914-1071-000

Issue IIS is a Microsoft product that is included on your typical Microsoft OS software but is not active by default. Product Line TAC Vista Environment Webstation Windows 7 Windows Vista Cause Webstation requires for IIS to be active in your OS before you complete the installation of Webstation. Resolution Follow these steps to initiate your IIS service in Windows 7 or Windows Vista. How to Activate IIS 7: To open the Windows Features dialog box, click Start, and then click Control Panel. In the Control Panel, click Programs. Click Turn Windows features on or off. You may receive the Windows Security warning. Click Allow to continue. The Windows Features dialog box is displayed. Expand Internet Information Services. Additional categories of IIS features are displayed. Select Internet Information Services to choose the default features for installation. Expand the additional categories displayed, and select any additional features you want to install, such as Web Management Tools. Click OK to start installation. The progress indicator appears. When the installation completes, the Windows Features dialog box closes, and the Control Panel is displayed. IIS 7 is now installed with a default configuration on Windows Vista or Windows 7. To confirm that the installation succeeded, type the following URL into your browser, http://localhost Use Internet Information Services Manager to manage and configure IIS. To open IIS Manager, click Start, type inetmgr in the Search Programs and Files box, and then press ENTER. See Problems installing Vista Webstation 5.1.5 or newer for more information on configuring Webstation.

Issue What can be displayed in an OP7? Can signals from programmable Xenta (Xenta 401, Xenta 301, Xenta 302, Xenta 281, Xenta 282, Xenta 283) be monitored/changed from OP7? Environment TAC Xenta Server (Xenta 701, Xenta 711, Xenta 721, Xenta 731) TAC Xbuilder TAC Xenta 401, Xenta 301, Xenta 302, Xenta 281, Xenta 282, Xenta 283 Cause This is a way to display values from a Xenta server without using a PC Resolution The OP Tree contains all possible pages (not Graphics) and values that can be generated from the Xenta 700 web pages: • Values pages • Alarm pages • Time Object pages • Trend Log pages • Variables • System variables • I/O signals Any type of signal that can be displayed on either off these pages can be displayed in OP7

Issue Error "Not enough space in RTI device"   Product Line TAC Vista Environment Aladdin Privilege Administrator 2.01 Vista IV Licensing Cause Memory in PSU is corrupt. Resolution Run Dongleutil, a dongle reset utility software. This utility resets the memory in the PSU that is connected to the PC. You need to install the license file again after this operation. This problem is usually seen when Inhouse PSU is used. In TAC Vista version 4.10 and later, it’s no longer necessary to install the engineering file when Inhouse PSU is in use. Just connect the PSU to the PC, and everything should work fine.

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 How to restore and view a Log backup without overwriting current database How to view backed-up events without overwriting current database How to restore a SQL database  without overwriting current database Environment TAC Vista 4.3 and higher running a typical (not custom) SQL. Cause The event and logs will be backed up as a SQL backup file. This means that restoring a backup on the same PC that it was made on replaces the SQL database.    Resolution To view old data, restore the log database backup file on a different PC that has the same TAC Vista database on it. Create a copy of the TAC Vista database (or make a backup) Copy / restore the database to a computer that is running the same version of TAC Vista Go to the Server application and log in Go to File > Restore Log Database Browse in the backup file, the path should be filled in automatically

Issue After running LANMON 3 on an I/NET C-LAN, it may return some error codes. The list below will help determine what they mean and the best way to address them. Environment I/NET Controller LAN LANMON output text file Cause Controller LAN errors captured by the LANMON program. Resolution One of the most useful new features of LANMon 3.0 is the detection and labeling of several types of communications errors. The label associated with the detection of a communications error is stored in the disk file just in front of the communications packet to which the error label applies. The error labels are presented in ASCII text along side the hexadecimal data. This text should allow most I/NET technicians to perform some level of useful investigation into controller LAN communications problems and reduce the necessity for sending LANMon files in to Technical Service for analysis. The following paragraphs lists the error descriptions associated with the type of errors detected by LANMon. The Bold text represents the label you will see on the screen or in the capture file when LANMon detects that type of error. ERR: Retry This error indicates that LANMon has detected a retransmission of the same command. This is the most common error type and can be used to find which controllers are having problems receiving from others. You should reference the destination and source addresses listed in the retry packet and accumulate/record this information. If there is a prevalence of specific nodes (destination or source) showing up in the retry packets, this would serve as a significant pointer to examine for network problems in that physical area (possibly in the cabling, environmental disturbances, power, grounding, and controller hardware and/or application software) ERR: LAN reconfiguration This error indicates that LANMon detected the occurrence of a LAN reconfiguration. This is a normal expectation when a controller/node is added or removed from the network as a result of LAN cable disconnect or power. When intentional changes are not in-work on the network configuration, a LAN reconfiguration is typically the result of several sequential errors (typically retry’s) which prompts the sending controller/node to initiate a LAN reconfiguration on the basis that it appears a node has been lost and everyone needs to have a new picture of the network layout. ERR: SDLC CRC Error This error indicates that the LANMon Tap received an RS485 packet with incorrect CRC indicating the packet is corrupted in some way. This error results from data distortion on the cabling or from intermittent disruptions such as from EMI, noise or grounding fault. With this error, the primary address you are interested in is the source address. If you are seeing a number of CRC errors from the same node address, or a collection of node addresses, you may want to look for cabling or loading problems in that area, or the length of cable getting to the area. You should make note of where LANMon is positioned when seeing this error. The error could be expected to get worse as to get further away from the reporting node address. For this reason, it is often recommended that you perform LANMon captures and analysis from at least two points on the network and those points should be the two most distant ends of the network. ERR: LAN master conflict with ## This error indicates LANMon has detected a NULL command output from a controller/node other than the currently recorded LAN master. The ## number will show the address of the node currently understood to be the LAN master. The packet following this error message will contain the address of the contending LAN master. This master conflict error is frequently the result of multiple simultaneous LAN reconfigurations. There should only be one LAN master and it is the function of that one LAN master to output the NULL command each time the token makes one pass around to all the network addresses and arrives back at the LAN master.   The following error descriptions will be encountered far less frequently and are not typically used for LAN diagnosis. ERR: Bad address LANMon detected a destination or source address greater than 3F16 (6310) ERR: Bad NULL LANMon detected that NULL was sent out without the same destination and source address, or without the broadcast header. ERR: Bad reconfigure LANMon detected that reconfigure command “01” was sent out without the same destination and source address, or without the FF broadcast header. ERR: Bad token LANMon observed what appeared to be a token command but had byte count greater than 3, or had destination and source addresses the same. ERR: Frame overrun LANMon received >160 bytes on the Async port from the LANMon Tap which exceeds design limits/expectations. ERR: Frame underrun Async frame from LANMon Tap to PC was considered too short to contain any SDLC (CLAN) data. ERR: Lost frame synch The LANMon program running in the PC got out of synch with the data stream from the LANMon Tap. This should be an unusual error. If it is repeatedly encountered, You can try running the LANMon utility on a faster PC, or you can try running it with Monitor mode OFF. B E1 m N O ERR: Bad frame CRC The LANMon program detected a CRC error in the Async frame of data from the LANMon Tap. With the standard short (6 ft.) RS232 cable between the PC and Tap, this should be a very infrequent error. ERR: Unknown error code This is a catch-all error indication intended to present any error codes returned from the SDLC controller in the Tap that are not currently defined. You should not see this error message. ERR: Frame too short The Async frame of data from the Tap to the PC is considered too short to contain a valid SDLC packet.

Issue Field office needs to access the Web Service page so that they can perform an Ethernet network packet capture for communications troubleshooting purposes. Product Line TAC IA Series Environment I/A Series MNB 1000 with firmware 1.510 and later only. Cause The field office needs to access the Web Service page so that they can perform an Ethernet network packet capture for communications troubleshooting purposes. Resolution The Web Service page has been removed from the MNB-1000 Plant Controller firmware effective with release version 1.510.   All functions that were previously included on the MNB-1000 Web Service page are now included in the WorkPlace Commissioning Tool -- Device Properties window for MNB-1000 controllers.  The changes to the Device Properties screens were documented in the WorkPlace Tech Tool 5.7.7 release notes, available here.