Building Automation Knowledge Base

Issue I/NET action messages are triggering audible alarms AMT is not functioning as expected for points that have action messages associated with them. Environment I/NET Cause As a best practice, I/Net action messages should be masked and grouped the same as the point which is triggering the message. When this is not done, AMT gets harder to manage. Resolution Edit the Resident I/O configuration of  the point which is triggering the event action. Note the Distribution group and Mask Edit the Event Action that is being triggered. Ensure that the Event Action has the same masking as the Resident I/O point.

Issue What is the benefit in having separate MPM monitor and coordinator? Product Line EcoStruxure Building Expert Environment MPM Cause In smaller networks, it is acceptable to have the monitor function as the coordinator. However, in larger networks, the monitor becomes occupied with managing the traffic of all the remote MPMs, resulting in significant CPU usage. This applies to zigbee, UDP, and CANbus networks. Making the monitor a coordinator does not provide any advantages; it only introduces disadvantages. Resolution In smaller networks, it is acceptable to have the monitor act as the coordinator. However, in larger networks, the monitor's workload increases as it manages the traffic of multiple remote MPMs, consuming a significant amount of CPU resources.

Issue I have package units with point count that exceeds the SE78600 capacity, can I simply add the SEC-TE in order to complete I/O points requirements? Environment SEC_TE MPM SE8600 Cause Unfortunately, the SEC– TE can’t be used as extended I/O modules with the SE8600 however; you may use SEC-TE with the MPM-UN. Resolution SEC – TE can not communicate directly with the SE8600. However you can use the SEC-TE with the MPM-UN.

Issue System configured with an AS, a number of IO modules and several power supplies, everything works fine BUT when viewing the IO configuration in the IO Management Tool the AS appears in the wrong slot. In the screen shot below the AS reports that it is occupyng slot #10 instead of slot #1, slot #10 is physically occupied by a power supply. No address shifted or black listed devices are reported and everything works fine. Environment Automation Server WS Cause A pin has been bent or otherwise damaged during installation of the AS The system does not report any problem because in this particular case the address that the AS assumed corresponds to a power supply, because power supplies do not report the slot they occupy. Eventhough everything is operating normally, it is recommended that the issue be resolved by removing the AS and identifying the root cause of the problem which could be in the AS itself or in the TB where the AS sists. As seen above, the problem in this case was a bent address PIN on the AS itself, the problem was resolved by making the pin straight and re-inserting the AS in its terminal base. Resolution The problem was resolved by making the pin straight and re-inserting the AS in its terminal base.

Issue UI-8-10 input reads only 5 volts dc  when dip switch is set for 10 volt input. Environment UI-8-10 Input Cause Improperly configured input. Resolution Page 40 of IO Module System Reference Guide states.  The 0-10V range allows connection to signals up to 10.00V. In this mode the circuit actually uses the same input measuring circuit as the 0-5V range, however, it divides the voltage present by two thereby limiting the internal circuitry to 0-5V. When you read a 0- 10V input the actual reading will be 0-5V. You must adjust your readings for the higher range via formula. This is accomplished by applying a conversion factor to the reading. When creating a 10V InfinityInput, set the Conversion to ElecValue * 2.   When using the 10V mode be sure to set the Reference resistor switch to Off.   Note: Setting the Reference Resistor enable switch to ‘ON’ and setting the Range to ‘10V’ is invalid. Switching to 10V inputs dramatically lowers the impedance of the input to 4.4 KΩ.

Issue From Continuum version 1.94 when you enable the Operator text when acknowledging alarms prompt, the messages will not save Environment Continuum Alarm acknowledgement Windows  Cause This was caused by a defect in the software which includes version 1.94 to version 2.0  Defect #368 = Alarms - Operator text entered before ACKing an alarm, is not stored in regions other than US. Resolution There is now a hotfix which corrects this issue which you must apply after you have Continuum 1.94 SP1 This hotfix has also been applied and tested successfully on version 2.0  Please download this file and replace the file as instructed in the READ ME.txt document 

Issue L1 Biometric Reader not accepting default Custom Format. Environment Continuum version 1.9X and above. Cause L1 Biometric Reader sometimes does not accept the default custom Wiegand format created in the integration program. Resolution To resolve this issue, the following steps need to be followed: Follow the documentation on the Integration as it works most of the times. In the event it does not work, use the Secure Admin to select the default Wiegand 26. Recommission by clicking on the Commission Tab and click on the Refresh  Button. Additionally a Custom Weigand 26 Format can be created and selected as well as seen on page 54 of the integration manual.

Issue Unable to communicate to a PIM Environment Continuum version 1.9X and above. Cause Wrong PIM Type Resolution For a Schlage integration, the PIM required is the RSI version, not the VBB version, which is used for a Vanderbuild System.

Issue IO module status shows 'Bootloader' Product Line EcoStruxure Building Operation Environment Building Operation Workstation Building Operation Automation Server IO Module Cause The most likely cause is a failed upgrade process.  During an upgrade, the IO module's firmware is deleted allowing it to be replaced with the new firmware.  If the process fails before completion the module will be left without the application and in bootloader mode. Resolution Upgrade the firmware by following the instructions at Upgrading Automation Server IO Module Firmware. The operation takes less than a minute and the Module status should show status 'Configured' or 'Unconfigured' depending on whether points have been created on the module.

Issue Web pages opened in TAC Vista Workstation is shown in compatibility view. That might have unwanted impact on some web pages. Product Line TAC Vista Environment TAC Vista Workstation Cause By default TAC Vista Workstation will use the newest version of Internet Explorer installed on the PC, but enable compatibility view. That might have unwanted impact on some web pages. Resolution Add a registry entry to define what version of Internet Explorer you want TAC Vista Workstation to use. Navigate to the following registry key: 32 bit OS: [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Internet Explorer\MAIN\FeatureControl\FEATURE_BROWSER_EMULATION] 64 bit OS: [HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Internet Explorer\MAIN\FeatureControl\FEATURE_BROWSER_EMULATION] Add a new DWORD (32 bit) value Give it the name "TACVistaExplorer.exe" Give it the decimal value 11000 to set Workstation to use IE11 This ZIP file contains registry imports that will set the browser used to IE9, IE10 or IE11

Issue How to modify a single trend sample value in Reports Server. Product Line EcoStruxure Building Operation Environment SQL  Reports Server Cause In some cases the user may wish to edit a single value from a trend log stored within the Reports Server Resolution Log into the Reports Server PC Copy the 2 Queries below into separate Queries in SQL Management Studio. - Click Here to download both queries. Open these Queries in SQL Management Studio Open Workstation Browse the Extended Trend Log you wish to change a value on Copy the Path from workstation Open the Query GetInfo in SQL Management Studio and paste the path to the @myLog parameter in the query. Remember to enter the data between the single quotes. In Workstation, open a Trend Log list. Browse to the Time stamp for the value you wish to change Type that time between the single quotes for the parameter @thisTime. Format the data as shown Year-Month-Day Hour:Min:Second Set the @oneSecondLater parameter to one second in time later than the @thisTime parameter Execute the Query or press F5 The Result should be a single row showing 3 columns Open the Query UpdateDb in SQL Managment Studio Set the @DateTimeStamp by Coping the result of the GetInfo query and pasting it between the single quotes. Set the @thisParentID and the @OriginalFloatValue parameters by copying the data in the same manner. Type the desired new value between the single quotes of the @newFloatValue parameter. Press F5 to execute the Query Re-Run the get info Query to verify the change Query 1 - GetInfo Declare @myLog nvarchar(1024) Declare @thisTime datetime2(3) Declare @oneSecondLater datetime2(3) SET @myLog = '' SET @thisTime = '' SET @oneSecondLater = ''   SELECT sampledata.DateTimeStamp, sampledata.ParentID, sampledata.floatvalue from dbo.tblogtimevalues as sampledata join dbo.tbLoggedEntities as logs on sampledata.ParentID = logs.ID   WHERE logs.Path = @myLog AND sampledata.DateTimeStamp between @thisTime and @oneSecondLater Query 2 - UpdateDb Declare @thisDateTimeStamp datetime2(3) Declare @thisParentID int Declare @OriginalFloatValue float Declare @newFloatValue float   Set @thisDateTimeStamp = '' Set @thisParentID = '' Set @OriginalFloatValue = '' Set @newFloatValue = ''   UPDATE dbo.tbLogTimeValues  Set FloatVALUE=@newFloatValue,OdometerValue=@newFloatValue  WHERE DateTimeStamp = @thisDateTimeStamp AND ParentID = @thisParentID

Issue Is it possible to have different stop bit settings in different Serial Modbus devices on the same bus? Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Modbus serial communication Cause In Building Operation there is an "Auto" setting for the Serial Modbus communications "Stop Bit" setting. This could be interpreted as "automatically" detecting the Serial Modbus devices stop bit setting. Resolution The "Auto" setting is only designed to detect how many stop bits are required in certain circumstances, such as when the parity setting is set to none and therefore 2 stop bits must be used. The settings used are the Serial Client settings for the entire bus and all the Modbus devices have to be set to match the Serial Client.

Issue When SE7000/SE8000 Series Room Controllers are bound to the MPM via ZigBee, "Effective Occupancy" does not follow "Occupancy Command" if the COV box is checked. Product Line EcoStruxure Building Operation, EcoStruxure Building Expert Environment SSL MPM SSL SE8000 SSL SE7000 Cause Data type mismatch Resolution Uncheck the COV box for Effective Occupancy

Issue Having issues configuring the pulse counter on the SEC-TE (TE2) Environment SmartStruxure Lite Multi-Purpose Manager SEC-TE (TE2) Cause N/A Resolution Navigate to the ZVC object of the SEC-TE and change "Analog Input 3 Mode" to "pulse counting". The value in AI3 (the counter) will then be incremented every time the pulse goes from 1 to 0 regardless of how long that takes. However, to convert the value of the counter to a more meaningful reading (e.g. water flow), you would need to use a Lua script in the MPM.   To reset the counter, click on the "Reset" button   Possible issues while testing: Using the Binary outputs of the TE2 for testing purposes will cause the counter to display unreliable readings. In fact, any binary output that induces voltage in AI3 will in inaccurate readings due to the noise induced. Instead, The binary outputs of the MPM can be used for testing before deploying the equipment on site.

Issue Public Signals, Inputs and Outputs in a Xenta are not accessible through Webstation Environment Webstation Xenta Cause The public signals are currently not objects but properties on a Xenta Resolution 1. Right click the Menta program under the Xenta, and click "Properties"   2. View "Public Signals", "Inputs" and "Outputs" and change if needed by clicking the three dots (...) next to the signal

Issue Requirement for a demonstration license for the OPC Server to get an idea about how it functions and to demonstrate to potential customers. Environment Continuum OPC Server Cause Require demonstration license for the software. Resolution There is a one hour demonstration mode that the software goes into if there is no valid license found. This should provide enough time for demonstration purposes. When starting the application without a valid license the below dialog is displayed.   You can download the Continuum Controller OPC Server from the downloads website at this link.

Issue Managing the address table in a Lonworks device Product Line EcoStruxure Building Operation, TAC IA Series, TAC Vista Environment I/A Series MNL TAC Xenta Third-party LON devices Building Operation Automation Server Cause A LonWorks device contains an Address Table which will hold a maximum of 15 addresses. Once this table is full, all bindings will only be able to use the broadcast setting which is not desirable. A Xenta 200,300 or 400 controller will have its first 2 address tables used with TAG 0 and TAG 1 binding. This leaves only 13 addresses for user bindings not the 15 addresses like other LonWorks devices. Resolution ​When you create a binding in LonWorks, you decide its behavior by selecting a binding profile. You either select a binding profile, or you use the default profile. There are basically three types of binding profiles: Acknowledged profiles Unacknowledged profiles Broadcast profiles Using an Acknowledged profile will consume one of the 15 available address table addresses on both the sending and the receiving device. The Unacknowledged profiles will only use one Address on the sending device's address table. Broadcast binds do not use an address but are not recommended. Use an acknowledged binding profile when the sending device should receive an acknowledgment from the receiving device indicating that the value of the bound variable was successfully sent. Binding profile Transmit timer Retry count Acknowledged Profile 96 ms 3 Acknowledged, Tx tmr 256, 3 retries 256 ms 3 Acknowledged, Tx tmr 256, 5 retries 256 ms 5 Acknowledged, Tx tmr 1024, 5 retries 1024 ms 5 Be careful of creating large, acknowledged fan-out bindings because they generate a lot of traffic, especially if the device of one of the recipients is offline.  Use an unacknowledged binding profile when the sending device should not receive an acknowledgment from the receiving device. Use this type when the value being sent is not critical and is of low importance to the control logic. Binding profile Repeat timer Repeat count Unacknowledged Profile   0 Unacknowledged Repeated Profile 48 ms 3 Unacknowledged Repeated, 5 repeats 48 ms 5 Use a broadcast profile when you do not want to use up an entry in the address table. The device address table has 15 available entries for bindings but the first entry is a reserved broadcast entry that all broadcast bindings can share. Binding profile Repeat timer Repeat count Broadcast Profile   0 Broadcast Profile, 5 repeats 48 ms 5 If no binding profile is selected, a default profile is used: Point-to-point bindings use the Acknowledged profile as default. Fan-out bindings use the Unacknowledged Repeated profile as default. Building Operation uses the broadcast profile as default when the device address table has run out of entries. If a point-to-point binding is changed to a fan-out binding, the binding profile is automatically updated to an Unacknowledged Repeated profile. If a fan-out binding is changed to a point-to-point binding, the binding profile is automatically updated to an Acknowledged profile.  This and other information about lon bindings is available on the online help guide Using a Lon Binding in StruxureWare Building Operation More information on the different tables used by each LON device

Issue Allowing write access from BACnet Product Line TAC IA Series Environment I/A Series G3 BACnet Integration Cause By default, the BACnet driver provides external BACnet (client) devices "read access" to all exposed (exported to BACnet) objects in the station. Access depends on a station user named "BACnet." If this user does not already exist in the station, the Bacnet driver automatically creates it, upon startup. The BACnet user is initially created without any permissions. Resolution See below which is extracted from the Niagara Ax BACnet Guide: To allow any external writes (from BACnet) to properties of exported components, including invoking commands (actions), you must assign the BACnet user the necessary permissions to those components. For example, to allow an invoked "Active" action from BACnet to an exported BooleanWritable, in addition to making it "BACnet Writable" at priority level 8 when exporting, you must configure the station’s BACnet user to have operator write permissions on that BooleanWritable, at a minimum. Or, if an exported NumericWritable has an alarm extension, and you want to permit external BACnet writes to its "alarm limit" values, configure the BACnet user to have admin write permissions on the exported NumericWritable. In either example, to allow an external BACnet write to a property like "Out Of Service" or "Notify Type," you must give the BACnet user admin write permissions on the BACnet export descriptors. For details about station user security, see "About Security" in the User Guide. Note: BACnet user permissions also apply to writes of any exported files and histories. Also, note that while a password for the BACnet user is technically not needed (for external BACnet access), you should assign one anyway, because of the write permissions typically assigned. Make it a "non-blank" password, and guard this password carefully.

Issue The default dynamic port range for TCP/IP has been changed with Windows Vista and later Microsoft operating systems. Product Line Field Devices, Satchwell Sigma Environment Microsoft Windows Vista Microsoft Windows 7 Microsoft Winsow 8/8.1 Microsoft Windows Server 2008 Ethernet communications Microsoft Windows 10 and server 2012, when Sigma is part of an SBO/EBO front end system. Cause To comply with Internet Assigned Numbers Authority (IANA) recommendations, Microsoft has increased the dynamic client port range for outgoing connections in Windows Vista, Windows 7 and in Windows Server 2008. The new default port range starting at port 49152 through to port 65535. This is a change from the earlier Windows configuration that used a default port range of 1025 through to 5000. Sigma used port 49152 as default for communications between Sigma server and Sigma controllers. Resolution You can use SE Legacy Port Reservation to reserve the port used by Sigma. Another resolution would be to redefine the dynamic port range Windows Server 2008 can use to 50000 to 65535, hence keeping the port free for Sigma. (Sigma port requirements can be found in What port numbers are used by the Sigma system?). You can view the dynamic port range on a computer that is running Windows Vista, Windows 7, Windows Server 2008 or 2012 by using the following netsh commands: netsh int ipv4 show dynamicport tcp netsh int ipv4 show dynamicport udp netsh int ipv6 show dynamicport tcp netsh int ipv6 show dynamicport udp Note The range is set separately for each transport and for each version of IP. The port range is now truly a range with a starting point and with an endpoint. Microsoft customers who deploy servers that are running Windows Server 2008 or 2012 may have problems with RPC communication between servers if firewalls are used on the internal network. In these cases, we recommend that you reconfigure the firewalls to allow for traffic between servers in the dynamic port range of 49152 through 65535. This range is in addition to well-known ports that are used by services and by applications. Or, the port range that is used by the servers can be modified on each server. You adjust this range by using the netsh command, as follows: netsh int set dynamic start=number num=range This command sets the dynamic port range for TCP. The start port is number, and the total number of ports is range. The following are sample commands: netsh int ipv4 set dynamicport tcp start=10000 num=1000 netsh int ipv4 set dynamicport udp start=10000 num=1000 netsh int ipv6 set dynamicport tcp start=10000 num=1000 netsh int ipv6 set dynamicport udp start=10000 num=1000 These sample commands set the dynamic port range to start at port 10000 and to end at port 10999 (1000 ports). The minimum range of ports that can be set is 255. The minimum starting port that can be set is 1025. The maximum end port (based on the range being configured) cannot exceed 65535. To duplicate the default behavior of Windows Server 2003, use 1025 as the start port, and then use 3976 as the range for both TCP and UDP. This results in a start port of 1025 and an end port of 5000. Note When you install Microsoft Exchange Server 2007 on a Windows Server 2008-based computer, the default port range is 1025 through 60000. Click here to be linked to the Microsoft Knowledge Base Article Number 929851.

Issue The Area schedule assignments from "Loose" Areas (ones that are individually attached to the Personnel object) can interfere with those assigned through a Template. Product Line Andover Continuum Environment Continuum Access Control Cyberstation Cause Wish to remove the "loose" Areas so that those assigned by the Template take over. Resolution Here are two methods to do this that will resolve this issue. For large numbers of affected Personnel, use the Personnel Import Utility for this by removing the areas you do not want from the import file. You may need to re-apply the template you want after this as well. See How to conditionally assign areas to personnel objects using the Personnel Input Utility XSLT transformation file that describes this method.  For smaller numbers of Personnel the manual method may be better. For each Personnel object. Clear out template assignment. Save the object. Remove all Areas left assigned. Save the object. Re-assign the previous template. Save the object.