Building Automation Knowledge Base

Issue A script program monitors the value of a digital input on an IO module. The input is wired to a switch that, when pushed by an operator, will toggle a digital output ON/OFF to start/stop a piece of equipment. The issue is the program will randomly fail to see the input changing when the operator releases the button too quickly. This happens even though the IOU module detected the input change as indicated by the LED on the input channel of the UI-16 module. Environment Automation Server SXW UI module Script Program Cause In SmartStruxure, Script programs are executed by a task and then go dormant until the task schedules the program to run again. If the input changes and then returns to the value it had the last time the program executed, the change will be missed. Resolution Instead of a digital input, use a counter input and modify the PE Script to toggle the output when the count increments. EXAMPLE: Numeric Input theINPUT Numeric Output theOUTPUT Numeric thePreviousInVal 1: thePreviousInVal = theINPUT goto 2 2: if theINPUT > thePreviousInVal then goto 3 3: if theOUTPUT = off then theOUTPUT = on else theOUTPUT = OFF goto 1

Issue How to have visibility into what a controller sees in its list of peer controllers and Cyberstations following a tech. Product Line Andover Continuum Environment All CX controllers Cause Documentation Resolution If controller is 9900 you can perform a "dump controller" from Hyper Terminal and see the list of peer controllers and CyberStations the controller has been taught. For Second Generation Continuum controllers that do not have a terminal interface you can put a program in the controller to get information about the list. (You can use the program in the 9900 as well.) Click HERE to see a sample PE program. IMPORTANT UPDATE: If the site has more than just a few (3-5) controllers comment out the line in the program that gets the controller names. Also, comment out the line that gets the security flag if there are first generation (9900, 9640) controllers involved.

Issue preventDefault() Javascript function not working on Mouse Up Environment TGML Editor Cause Users want to override the default function showing the StruxureWare Building Operation properties editor by preventing the default action for the Up function. The Building Operation Properties editor is not launched on Mouse Up but on Mouse Click. Resolution Select The TGML Script Add the line "evt.preventDefault();" to the onClick function

Issue Programming an application that requires a setpoint and deadband that operates in the same manner as the WorkPlace Tech Tool Thermostat object. Environment SmartStruxure AS or ES Cause No object exists in the Function Block library that is functionally equivalent to the I/A Series WorkPlace Tech LON/BACnet "Thermostat" object.   Resolution This is only one of several methods by which a differential type thermostat object can implemented in Function Block programming. The following Binary Expression (XPB) function block object can be used to simulate the differential type thermostat. Analog Input A is the "Input" Analog Input B is the "Setpoint" Analog Input C is the "Input Differential" Binary Input d is the "State Feedback"  This feedback link insures that the output state does not change when the input is within the range specified by the input differential The output of this object turns on when the Input value exceeds the Setpoint + 1/2 of the Input differential. The output of this object turns off when the Input value falls below the Setpoint - 1/2 of the Input differential. The xml file can be downloaded from here.

Issue Will the Multi-Purpose Manager (MPM) act as a BACnet IP BBMD?   Product Line EcoStruxure Building Expert Environment Site using BACnet and one or more  SmartStruxe Lite Multi-Purpose Manager (SSL MPM)  Cause Can the MPM act as a BBMD Resolution The MPM cannot act as a BACnet Broadcast Management Device (BBMD), but it can be a foreign device to another BBMD BACnet protocol includes broadcast traffic which does not pass through on-site routers. For BACnet devices to network across a wide area or across multiple separate sites connected by the Internet, it is necessary to register the BACnet devices with a Schneider BBMD using the Foreign Device Registration function in Building Expert. For a Multi-Purpose Manager (MPM) running Building Expert to function as a BACnet device, when being managed remotely over a standard TCP/IP network, it must be configured as a Foreign Device. It must also be registered on an Automation Server (AS) on the remote network that acts as a BBMD. Once done, BACnet devices can send messages to the BBMD, which are translated by the BBMD so they can pass over a standard on-site router. Then BBMD forwards the messages to the appropriate destination MPM controlling the Devices for which the BACnet messages were originally intended. Then the MPM translates the messages received over the network from the BBMD into standard BACnet messages and passes them on to the intended Devices as if they were direct BACnet messages. This Foreign Device Registration feature allows a single user with a StruxureWare Building Operations (StruxureWare Building Operation) terminal to remotely oversee multiple disparate sites simultaneously using BACnet, without having to install expensive direct connections to each site. You must have Firmware release version 2.9 or higher installed on your Manager to use Foreign Device Registration function. Here is the BACnet-Specifications-PIC-Statement.pdf And the  explanation on how to setup the DR-ForeignDeviceRegistration.pdf

Issue How to discover MNL Lon devices or other Lon devices in an SmartStruxure Automation Server. Product Line EcoStruxure Building Operation Environment Building Operation Workstation Building Operation Automation Server Cause Use the below instructions when you need to find all Lon devices on a Lon network. Resolution To discover a LonWorks device In WorkStation, in the System Tree pane, select the server that is connected to the device you want to discover. Click the Device Discovery view. In the Select device type box, select LonWorks. Select the Devices folder. Right click on the Devices folder and take "Scan network for devices" In the Device Discovery view, ensure that the LonWorks device is displayed in the Devices folder. This may take up to 5 seconds. Drag the discovered device to the System Tree pane: Drag to an existing device to associate it with the discovered physical device. Drag to the LonWorks network to create the device.   NOTE: You cannot drag a standard MNL LonWorks device to the System Tree pane if the discovered device is in an unconfigured state For more information, refer to the Creating and Configuring a LonWorks Network with MNL LonWorks Devices [102423].pdf document 

Issue When configuring a BBMD what is the Broadcast Distribution Mask and what are the valid settings for the field. Continuum EcoStruxure Building Operation Product Line EcoStruxure Building Operation, Continuum Environment Building Operation Automation Server Building Operation Enterprise Server Continuum CyberStation bCX4xxx Cause Documentation Resolution When configuring a BBMD the BACnet protocol defines two methods of propagating the broadcasts messages to other networks. The two methods are referred to as One-Hop also known as a Directed Broadcast and Two-Hop.   Note: In this article the subnet mask is shown using Classless Inter-Domain Routing(CIDR) notation. An IPV4 address is 32 bits long, CIDR notation defines the number of bits used for the subnet mask. The most commonly used are: /8 or 255.0.0.0 /16 or 255.255.0.0 /24 or 255.255.255.0 /32 or 255.255.255.255 One-Hop With the One-Hop method the local BBMD transfers the message directly to the remote devices via the remote router. In this case the IP routers have to support the transfer of IP broadcast messages to remote IP subnets Figure 1 Figure 1 above illustrates the one-hop method, when the bCX1 which has been configured to take the role of BBMD for network 172.16.0.0/16 detects broadcast messages such as WHO-IS, I-AM etc, it sends a message directly to the broadcast address of the 192.168.1.0/24 subnet, it is then up to Router2 to send the directed broadcast to all devices on the subnet. Any device on the subnet that is acting as a router to other networks will then also re-broadcast the message on those networks. (i.e a bCX hosting an MSTP network on COMM2)   Two-Hop With the Two-Hop procedure a BBMD device transfers broadcast messages to a further BBMD in the remote IP subnet, which then distributes the messages in its local network as IP broadcast messages for its IP subnet. Any device on the subnet that is acting as a router to other networks will then also re-broadcast the message on those networks.(i.e a bCX hosting an MSTP network on COMM2) Figure 2 Figure 2  above illustrates the two-hop method, when the bCX1 which has been configured to take the role of BBMD for network 172.16.0.0/16 detects broadcast messages such as WHO-IS, I-AM etc, it sends a unicast message to each BBMD device on its table, it is then up to each BBMD device on each subnet to send a broadcast that will be heard by all devices on the subnet. Which distribution mask should be used? As mentioned earlier, in order for the one-hop method to work, the router on the remote subnet MUST be configured to process incoming messages sent to the broadcast IP address, the two-hop method on the other hand is guaranteed to work, so when in doubt use the two-hop method. Most sites use two-hop distribution for the reason stated above,, the only obvious disadvantage of the two-hop method is that it is a little more verbose than the one-hop method since the message appears twice on the subnet, once as a unicast sent to the BBMD device and then again as a broadcast sent by the BBMD device. In Building Operation and Continuum the distribution mask defaults to the two-hop method (/32 or 255.255.255.255) How to configure the distribution mask For one-hop enter the subnet mask of the remote network in the distribution mask, the system will apply the mask to the IP address to obtain the broadcast address for the remote network. For two-hop enter 255.255.255.255, this tells the system not to do a direct broadcast and instead do a unicast to the remote BBMD device. Sample distribution mask In the BBMD table of a bCX shown in the screen shot above, BDT #1 and #3 use the two-hop method while BDT entry #2 uses the one-hop method.

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 Deleting reports built in Reports Builder using Building Operation WebReports Environment SmartStruxure Building Operation running Reports Server and Microsoft Report Builder Cause Reports built using SQL interface such as Microsoft Report Builder cannot be deleted using the Manage Reports in Building Operation WebReports Resolution Building reports on the SQL side must be deleted on the SQL side.   From the first screenshot below, you can see that when using WebReports, in the Manage Reports tab, custom reports which are made are considered System Reports and the Delete button is grayed out.  Here I have created Top Alarms Test 1 report, which has been selected. Using SQL Server Management Studio, I penetrate to the tb.ReportGroups and see the isSystemOwned is True for the report Top Alarms Test 1 The isSystemOwned is changed to False for the selected report(s) Top Alarms Test 1 Viewing WebReports, in the Manage Reports tab, the Top Alarms Test 1 report is selected and the Delete option is available.

Issue Separate a 7792 or 7793 into two 7798C Split SAV files  Product Line TAC INET Environment I/NET Seven 779x Controllers Cause Need to replace a 7792 or 7793 which has two station addresses and replace with two 7798C Controllers which have one station address Resolution To split the required SAV Files: Download and Extract the attached SAV_Split_EXE.zip Make a backup of the I/NET Seven system using DBCreate. Perform Station Save to all the required controllers Copy the SAV files that need to be split to the same location where the ZIP file was extracted too in step 1. Run the SAV_Splt.exe The commands are showing the Sav_Splt.txt file contained within the ZIP file and shown below Purpose: Use this tool to create two 7798 SAV files from a dual-station 7793 SAV file. Syntax: Sav_Split.exe (with no parameters will check all save files in the current directory and split 2 station 7793s.) Sav_Split.exe LLSS (where LL = Link and SS = Station) Result: The resulting files will be named DCULLSS-0.SAV and DCULLSS-1.SAV. Rename these files appropriately to match the link and station of the 7798 into which each will be loaded. Example: SavSplit.exe 0906 Results: DCU0906-0.SAV and DCU0906-1.SAV     Finally check the split files using the "Work Offline" mode within I/NET Workstation. Any issues or additional questions please raise a case with your local support   For SAV file upgrade information see How to upgrade bin and SAV files in I/NET controllers.

Issue TGML pages are slow to load in Workstation TGML objects are not responsive Product Line EcoStruxure Building Operation Environment EcoStruxure Building Operation TGML Cause The driver of the graphic card is outdated or not supported. Resolution Visit the webpage of the PC's brand and update the driver for the graphic card.

Issue Can Strings be used in all controller types? Product Line Andover Continuum, EcoStruxure Building Operation Environment All Continuum Controllers b3, i2 Controller (EcoStruxure Building Operation) Cause Some Controllers do not support strings Resolution The String class of object are supported in the following products: CX series (including all Netcontrollers), bCX series, CMX series, ACX series, i2 series (except i2885, i2887), BACnet series (except b3885, b3887), DCX 250, CyberStation.

Issue Sales literature shows the use of NV202, are these the only supported device and are these provided by Schneider  Product Line TAC INET, Security Expert Environment Security Expert SP-C I/NET Access Control Hardware   Cause The NetSys NV202 product was sourced to provide a solution for a large I/NET Site that had multiple 7798B / 7798C controllers communicating back to a single Xenta 527.  As these I/NET Controller LAN devices only communicate via RS-485, a method of using this existing RS-485 cabling to support the SP-C Ethernet connection needed to be sourced.  Tests were carried out to see their performance, which is provided in the resolution below.  These devices are provided by NetSys and if necessary should be purchased directly through their distribution centers.  Documentation for this device is also provided on their website.  Resolution The following shows the tests, methods, and results performed with the NetSys NV-202 on a transition I/NET Database with over 25,000 users and over 5,000 doors. Testing and Validation of proposed NV-202 based RS485 Network Replacement Solution Test Equipment 49 Netsys NV-202 devices and power supplies 25 SP-C Controllers Security Expert Software 4.2.251.19 installation on a PC with the following specification: Processor Intel(R) Core(TM) i7-3820 CPU @ 3.60GHz Installed RAM 16.0 GB 240m Belden 9842 Twisted Pair cable PLUS 50 Ohm resistances for line length simulation to an equivalent run length of 840m 100Mbps switch for interconnection of server PC and controller LAN Test Scenario 30 NV-202 units and in the following network topology. Figure 1: Test System Topology Method The Security Expert server was loaded with a database backup from an I/NET Transitioned Site, which was then modified to include: Connection to the SP-C’s on the IP range 192.168.1.200-192.168.1.224. by modifying existing real-world controller records to match (Database ID’s 149 onwards) Increasing the record load on each controller to the full set of users in the database (21,522) to be downloaded by adding an Access Level containing a door on each controller to each User A Status Page containing an All Events window All controllers were connected to the same 100Mbps switch as the test PC containing Security Expert The last controller in the daisy chain had one input wired into Relay 1 of the controller; this was used to validate input change timing. Download was forced to all controllers Timing for each required parameter (as noted in Figure 2) was measured using the final controller at the end of the cable run, having worst-case characteristics of bandwidth/latency due to maximum number of daisy-chained NV-202 devices Figure 2: Tested Timing Parameters Results Command Response Time Manual commands (by right-clicking and selecting ‘Unlock Door’) were performed on the first door programmed on the SP-C. 25 activations were run and the worst-case results selected. Command response time is less than 2 seconds as stipulated. See Wireshark capture: Figure 3: Packet capture of a Manual Door Unlock command to the worst-case SP-C from Security Expert Software Status Changes Response Time Relay 1 of the SP-C was activated, which is wired to Input 1 of the same SP-C in order to close the input and trigger a status change. 25 activations were run and the worst-case results selected. Status Change response is less than 1 second stipulated. Door Status Changes response time Manual commands (by right-clicking and selecting ‘Unlock Door’) were performed on the first door programmed on the SP-C. 25 activations were run and the worst-case results selected. Door status change response is less than 1 second stipulated. Retrieve access data or user’s data Not applicable. This data is stored in the server database. Generate any single ad-hoc reports Not applicable, reports are generated by the server using data from the server database. Multiple access control levels Not Applicable to this test - Security Expert can store unlimited Access Levels, and associate any of them to a given User. Access Level/User quantity limitations are not affected by the NV-202. EOD download time: A Force Download operation was performed on the SP-C, and the time to completion recorded. 25 activations were run and the worst-case results selected. Maximum download time: 58 seconds per controller (noting 21,522 Users) Time synchronization – maintain synchronism Time update packets are successfully sent, Server and controller time maintained within 1 second. Time synchronization – accuracy Not Applicable to this test – time is updated periodically (not constantly) so not significantly affected by bandwidth or latency.

   

Issue What are the fields in the FIPS-201 PIV FASC-N? Product Line Andover Continuum Environment CyberStation NC2 (9680) ACX2 (ACX5720, ACX5740) Cause Documentation Resolution The Federal Agency Smart Credential Number (FASC-N) consists of 40 total characters encoded as Packed Binary Coded Decimal (BCD) format with odd parity creating a 200 bit (25 byte) record.

Issue When evaluating Inet Transition sites, a common error seen when uploading I/NET controllers under the  Inet Interface is an upload failure.  The Background Status and trace log will contain a changeset error as shown below: UploadDevice failed to process changeset on link: 93 station: 10, type index: 17 cannot continue upload Product Line EcoStruxure Building Operation, TAC INET Environment Ecostruxure Building Operation Inet Interface  Cause Understanding the ChangeSet Indices used by the developers will help pinpoint where the issue is originating from.  The message typically isolates the Link and Station but does not identify where within this controller the problem may lie.  Resolution The current list of ChangeSet Indices are listed below and attached Changeset_index.txt Index Affected 9 DCU passwords, States, Eng units, Conversion Coeff., Controls, Holidays, DDC history, Override access, Sunrise/Sunset 11 Points 15 Action message, DCU DDC, Event sequences 17 Calculation 19 Event extension 21 Extension general (can be one of: Runtime, Consumption, or Alarm inhibit - depends on DCU type) 23 ATS 25 ATC 27 Extension application (can be one of: Demand, ORB, ORBEM, UC, LZ, LC, Elevator - depends on DCU type) 29 Trend 31 Lookup table (raw data) 33 Demand load (raw data) 35 MCU 37 MR DDC 39 AIC sequence (raw data) 43 LCD page, Istat param, IAS (raw data) 45 Access control (raw data) Note: "raw data" indicates user cannot manipulate in EBO but it is uploaded and save in raw form to allow for a download/restore Working with the example shown in the Issue, the message indicates a changeset value of Index: 17.  Using the attached list, Index 17 indicates that the issue is within the Calculation Editor. Using the SAV file from the site and working offline within I/NET open this SAV file and check each of the editors, in this case, calculations. In most cases, it will either be an invalid character or invalid point address - which will be shown as 'blank' as seen below: Correcting this and updating the SAV file to the controller (Station Restore) will typically correct this issue. If the same error persists then please provide an Export of the Inet Interface and the SAV files of the controllers having this problem through your local support channel.   

Issue The SE8000 documentation states that the power supply voltage is 7 Volts DC but the circuit board sticker says 7 VDC/24 VAC. Can the controller be powered from 24 VAC? Product Line EcoStruxure Building Operation, EcoStruxure Building Expert Environment Building Operation Workstation Building Operation Automation Server SSL SE8000 Cause An incompatible relay pack might have been used. Resolution Typically the SER8300 range are intended to have power supplied by the SC3000 relay pack which supplies the 7VDC. If an SC3000 relay pack is not used, for example, if the SER8300 is just being used as a wireless device then it is acceptable to power it from 24VAC.

Issue BACnet devices not found but are visible in other third party BACnet applications An update may cause devices to go offline Product Line EcoStruxure Building Operation Environment BACnet IP Network Building Operation EnterpriseServer Building Operation Automation Server (AS, AS-P, AS-B) Cause According to BACnet routing rules, each BACnet Device should have a unique BACnet Instance ID and each BACnet Network should have a unique BACnet Network ID  When a BACnet interface is created on an EBO Server, a BACnet IP network is created with default Network ID of 1. This is a local Network address and in not published on the network, it is therefore not a problem if this is duplicated with other EBO Servers. On many site this will remain at 1 for multiple EBO servers with no problems. If a third party BACnet device uses a published Network ID that is identical to the EBO local Network ID, then it will be ignored. There will be a "Duplicate of local network"  System Alarm and line similar to below in the trace log "nsp.pin.BACnet Device <device name>claims to be router to Network #1234 but that is a local network (BACnetMain)" Resolution If the EBO Server is not finding a BACnet device on a different network type (via BACnet routing like MSTP or virtual IP) then it could be the Network ID is identical to the local EBO Server Network ID. If this is the case, then simply change the EBO local Network ID and retest. BACnet Devices on the same IP network, including those on different IP subnets and linked via BBMD or Foreign Devices are not BACnet routed and therefore will not have this issue (no BACnet Network ID route is involved) Some earlier versions of EBO did not ignore these duplicate Network IDs, thus when up grading some devices could go offline. The workaround would be the same. The correction to the BACnet operation occurred in v1.9.3 and v2.0.2

Issue Controller Health Status shows, "Controller (ID **) has too many Remote Controllers assigned." What does this message mean, and is it a cause for concern? Product Line Security Expert Environment Security Expert Client SP-C Controller Cause This error message is related to cross controller communication. When using cross controller communications, the maximum number of controllers that can be linked together is 64. For additional details on cross controller communications, see page 4 of AN 180 Security Expert - Cross Controller Operations - Integration Guide. Resolution The controllers that are not taking part in cross controller linking are the ones that are showing the "Controller (ID **) has too many Remote Controllers assigned." message. Evaluate what values/controllers are being shared to ensure your programming is performing as expected. See AN 180 Security Expert - Cross Controller Operations - Integration Guide for further details on cross controller communications and which values use this. Limit the number of sharing controllers to 64 or split the controllers up into two systems.

Issue Looking at the Status Information on the MSTP network object under the BACnet Interface of the Automation Server, the status read online FALSE Environment Automation Server - AS Cause The AS is not being passed the network token. If the Automation Server sees the token being passed on the bus but it never receives the token the AS will tag the MSTP network status as OFFLINE.. Resolution Possible reasons/solutions. CAUSE: Baud rate mismatch with third party devices. SOLUTION: If device does not support auto-baud change the speed of the MSTP to that of the device. CAUSE: A device on the MSTP is using the same mac id as the MSTP port. SOLUTION: Resolve the duplicate id issue. CAUSE: A defective device on the MSTP SOLUTION: Identify the defective device and replace it.

Issue Would like the ability to disable "Ping Failed" alarms in G3 Environment Tridium Niagara G3 (AX) network controllers (ENC, JACE-645, JACE6, JACE7) Cause Network communication issues sometimes causes device to timeout on a ping request, but quickly recovers. This failure causes an unnecessary alarm to be generated. Resolution 1.  Go to the Property Sheet of the appropriate network (e.g.. Lonworks Network, Bacnet Network) 2.  Expand Monitor, and set the Alarm on Failure field to False. 3.  Click Save