Building Automation Knowledge Base

Issue What is valve authority? Product Line Field Devices Environment Any valve Cause Information on Valve Authority to obtain good control. Resolution Valve Authority = (Pressure drop across fully open control valve) / (pressure drop across the remainder of the circuit) + (pressure drop across fully open valve) In other words, valve authority within a system indicates how much of the system's total pressure drop comes from the control valve. It is common practice to consider the range between .2 to .5 as "acceptable" authority for proportional valve.

Issue Needing to monitor a controller's online or offline status. I/NET AMT will generate a station lost alarm when a controller is offline, however it is sometimes desired to have a point that can be monitored to alarm as well. Product Line TAC INET Environment subLAN Controller Lan; C-LAN Xenta 527 Cause I/NET AMT will generate a Station lost alarm when a controller is offline, however it is sometime desired to have a point that can be monitored to alarm as well. Resolution Monitoring SubLAN Controllers Connect to the Sub Lan Interface Controller (7798, 7793) Create an internal DA point called LLSSPP_Offline, with LLSSPP being the address of the subLAN device Add a Calculation to the point LLSSPP_Offline Enter this Calculation: OLD(P0) Set P0 to equal any External input point the subLAN device LLSSPP Click okay The result of this calculation is that the point will equal 1 whenever the referenced point goes old Monitoring Controller LAN or C-LAN devices Connect the Controller you wish to monitor Change an external point's Global Level to "Link" (If a point already is set to system, use it.) Connect to a second Controller on the same physical C-LAN (for best results use one physically closer to the NPR or Tap) Create an indirect point referencing the point created in step 2 Create an internal DA point called LLSS_Offline, with LLSS being the address of the controller Add a Calculation to the LLSS_Offline point Enter this Calculation: OLD(P0) Set P0 to equal the indirect point created in step 4 Click OK The result of this calculation is that the point will equal 1 whenever the indirect point goes old, which should only occur when the controller is offline.  Monitoring NPR or Xenta 527 devices Connect to a Controller under the device you wish to monitor Change an external point's Global Level to "system" (Use an existing global point if available) Connect to a second Controller under the device you wish to monitor Change an external point's Global Level to "system" (Use an existing global point if available) Connect to a controller underneath a different NPR or 527  Create an internal DA point called Link _LL_Offline, with LL being the Link address of the 527 or NPR being monitored Create 2 indirect points referencing the global points created in steps 2 and 4 Add a Calculation to the Link _LL_Offline point Enter this Calculation: OLD(P0)&OLD(P1) Set P0 and P1 to equal the indirect points created in step 7 Click okay The result of this calculation is that the DA point will equal 1 whenever both of the referenced indirect points go old.  This should only happen when communication is interrupted to both controllers indicating the most likely cause is the NPR being offline. Please be aware of other potential causes of 2 controllers on the same link going offline. Examples include power circuit failure or cut wire when selecting which controllers to monitor. 

Issue Modbus device is offline in Vista. Product Line TAC Vista Environment TAC Vista Xenta 511 Xenta 913 Xenta 700 Cause The Modbus device online check has to read at least one variable for the device to come online in Vista. If you only write values to the Modbus device, it will appear offline.  Resolution As a workaround, you may create a dummy variable that you read from in Xbuilder

Issue Windows crashes after performing a Doc to Dif conversion Environment I/NET Site Cause Why does Windows crash after performing a Doc to Dif conversion? Resolution Do not define more than 164 cells per conversion.

Issue What is the pin configuration for Modbus RTU when using a 9 pin comm port on a BCX controller. Environment BCX Modbus RTU Cause Connecting a BCX or CX controller to a Modbus RTU device. Resolution RS232 connection for a 9 pin BCX comm port.   BCX Comm 1 (9 Pin)            RJ 45 Connector @ Modbus device Pin 1 CXD        -->                 Pin 1 DTR Pin 7 RTS        -->                 Pin 2 CTS  Pin 4 DTR        -->                 Pin 3 CXD Pin 8 CTS        -->                 Pin 4 RTS Pin 5 GND       -->                 Pin 5 GND Pin 3 TD           -->                 Pin 6 RD Pin 6 DSR        -->                 Pin 7 DSR Pin 2 RD           -->                 Pin 8 TD        

Issue  Error  'Communications failure due to device not online' during personnel distribution Environment CyberStation CX9900 CX9702 CX9680 ACX5720 ACX5740 ACX701 ACX781 Cause By default CyberStation will try to speed up the personnel distribution as much as possible in order to expediently distribute all the card records to the controller. There may be situations where the controller may be overwhelmed,  100MB NIC in the controller  versus a 1Gig NIC in the Cyberstatom and by the amount of traffic caused by multiple CyberStations distributing multiple records simultaneously. Resolution Continuum contains some facilities available in the General Preferences window where adjustments can be made to throttle the personnel distribution. Lines 12 and 13 are the settings used to throttle personnel distribution going to field devices such as ACX701 or ACX781 Lines 14 and 15 are used to throttle personnel distribution going to LAN controllers such as the CX9680 (NC2), ACX5740 (ACX2), CX9900 etc The interval between personnel distribution is in milli seconds, a reasonable value to start at when issues are encountered is 50 milli seconds. Ex. Line 15 change from 0 to 50 Increase by 25 milliseconds after that to get better results. Ex. 50, 75, 100

Issue Getting a “500: Internal Server Error” when clicking on hyperlink in G3 station. The following error is also displayed in the Application Director window: javax.baja.naming.SyntaxException: Illegal char '?' in body: /ord?file:^gfx_Lib/www/nav.htm javax.baja.naming.SyntaxException: Illegal char '?' in body: /ord?file:^gfx_Lib/www/Top.htm Note:  The last part of the file path after "file:" will be different based on your station's file structure.   Environment Niagara G3, version 3.8.37 Cause A second “/” mark was being added to the hyperlinks’ paths in the htm file.  In this case, hyperlinks in the Top.htm file are the culprit. The Hyperlinks read: To date, Tridium has not determined how the second slash gets added.   Resolution The solution is to find out which htm file contains the error and correct it. Use WorkBench’s Text File Editor to examine the htm file to find the error.  - Open the station’s Files folder  - Right-click on the htm file and select “Text File Editor” - Once the htm file is found that contain the error, remove all second slashes.      Change <a href="/ord/?...     To          <a href="/ord?... (removed the second “/”) - Save changes and reopen page in new browser Note: There may be a need to clear all caches.   

Issue Unable to bring interfaces(downstream devices) online, showing as unknown Product Line EcoStruxure Access Expert Environment Access Expert in Cloud or On-Premise SSC (Security System Controller) Downstream controllers Cause Offline interfaces can occur under a number of circumstances, below are the most common reasons. The controller is not yet active. Once all interfaces, readers, and I/O have been added, it’s important to remember set the device as active. Interfaces were added to the controller after it was made active. The controller requires a reboot to download the correct configuration. Dipswitches and addressing on the board may be incorrect Check Wiring  Resolution Go through the following steps to get interfaces online Set the device as active (Go go back to the controller page ) Reboot the controller (containing the interface) Check that the DIP switch settings are correct on the controller (see the Mercury hardware manual) Switches 1-5 on an interface module set the address in binary, this means 32 addresses are available (0-31). Users must set the correct address inside Access Expert that matches the DIP switch value. Switches 6 & 7 set the Baud rate, both on for default 38400. Switch 8 should be off to disable AES key encryption. (Communication is instead encrypted over TLS 1.2) Note: The orientation of the DIP switches may be upside down compared to some labels on other connectors, so it's easy to have everything inverted. On this MR52 board, the On label on the connector is DOWN. These dip switches are configured for address 0, baud rate 38400, and no encryption. Check wiring Ensure that the panels are wired correctly. Verify your RS485 communication and refer to the hardware installation guides Verify End of Line Termination Verify End of line termination jumpers are set, refer to hardware installation guides

Issue Unable to connect Remote Client to Standalone Server ASTDIR error when attempting to configure I/NET is sometimes caused by not being logged in as an administrator. Product Line TAC INET Environment I/NET Seven Remote Client Workstation type Cause In most cases, the issue that blocks the remote client connection is port 50069. This must be opened between the two workstations, and use an admin-level I/NET password must be used to initiate communication as well as having to be logged in as an administrator on the local machine. Resolution Log in to Windows as an administrator-level user Make sure that the I/O server is not running Open I/NET Configuration Modify the active profile or create a new one Set TCP/IP settings as well as required reference hosts For Workstation type, select Remote Client or Remote Client (w/IO) When the authentication screen comes up, enter an I/NET operator name with full access. Enter the Host name of the standalone machine functioning as the server. (IP address can be used instead) Leave Authentication Type as default. Press OK Press OK and start I/NET For more information, see Remote Client Configuration Issues I/Net 2.31 and prior and Remote Client with I/O in the Workstation Type of the I/O Server 2.4 and later.

Issue When trying to create or update a Security Expert database the error 'Invalid Database Server is displayed Product Line EcoStruxure Security Expert  Environment EcoStruxure Security Expert  Microsoft SQL Server Cause The path to the SQL Server from the Client is incorrect or inaccessible and will not resolve Resolution There are a number of resolutions to this issue depending on the cause. This article mainly focuses on a configuration where the Security Expert and Microsoft SQL Server are on separate PCs. The error can happen locally also but is less likely. One or more of these resolutions may be required to fix the issue. 1. The Server / Instance name is incorrect when typing it into the Database Server dialogue box during installation. (Local SQL Server) Default Database Server Dialog Box    There can be some confusion on what to enter into the dialogue box because, by default, the instance name and the main database name are the same. Ex. Server Name\Instance Name    Database       localhost\SecurityExpert            Security Expert   (Remote SQL Server) Ex. Server Name\Instance Name    Database       SVR19SQL19\SecurityExpert     Security Expert Note: If just the ServerName SVR19SQL19 or SVR19SQL19\SecurityExpert\Security Expert The Invalid Database Server error would occur   Copy and Paste the Server and Instance Names using SQL Management Studio (SMSS) This method can help to avoid typing errors Install SMSS on the same PC that has Security Expert Installed or use SMSS on the SQL server with Remote Desktop From the Connect to Server dialog> Server name, select <browse for more...> Select Network Server and then select the remote SQL server and click OK Right Click> Copy on the blue highlighted server name and instance Paste into the Security Expert Database Server Dialog box   For a detailed description of Instanced and Database, click on the following link Microsoft Database and Instance Article  Note: Try using the IP address instead of the SQL server name. 2. Make sure SQL Server Service is running on the remote SQL server 3. If using a named instance, make sure the SQL Server Browser Service is running on the remote SQL Server 4. Ensure Firewalls have an open port for SQL server (default 1433) 5. Make sure the SQL Server is configured to allow remote connections 6. The Windows account being used to do the Security Expert Installation must have access to create the database on the remote SQL Server.  7. Check the Windows Application and System logs on the Security Expert and SQL Server for errors related to the Security Expert Install, DNS or Connection errors 8. Examine the SQL Server Log for error messages   Ex. If Active Directory is being used, the error “The SQL Server Network Interface library could not register the       Service Principal Name (SPN)” This issue can be fixed by giving the domain account the appropriate permissions in Active Directory. Permissions required are:  ServicePrincipalName: Read  ServicePrincipalName: Write   Log in to the server running your Active Directory service and execute the following steps: Run Adsiedit.msc In the ADSI Edit snap-in, expand Domain [YourDomainName], expand DC= RootDomainName, expand CN=Users, right-click CN= [YourAccountName, and then click Properties. In the CN= AccountName Properties dialog box, click the Security tab. On the Security tab, click Advanced. In the Advanced Security Settings dialog box, select one (any) of "SELF"'s row Click Edit, Open Permission Entry dialog box. Make sure the Principal is "SELF", Type is "Allow" and "Applied to" is "This Object Only", in the Properties section, select the properties below: Read servicePrincipalName Write servicePrincipalName Click OK to apply all changes and exit the ADSI Edit snap-in Finally, you need to restart the SQL Service(s) that use the account in question.   9. If you are still unable to get passed the "Invalid Database Server' error, please open a case with Technical Support.

Issue Sample Plain English program to set up a door to allow for either keypad OR card validation. Environment Continuum Plain English Infinity NetController Cause Allowing the NetController to respond to a keypad as well as a card reader allows for flexibility in the security solution. Resolution How do I setup a door for keypad OR card validation Create the following InfinityProgram in the NetController for each door. Change each program to the correct door name. NOTE: If using this program, make sure that you do not have validate pin mode selected on the entry reader tab of the door editor. -------------------------------------------------------------------------------------------------- 'Looping, AutoStart Program 'Change officedoor to the name of your door Watching: IF officedoor\doorfault IS 2 THEN '0 for normal operation 2 if Fault (Tamper) detected officedoor\entrynormmode = 8 'PINMode officedoor\entrynocommmode = 8 'PINMode GOTO Counting ENDIF Counting: IF TS > 5 THEN 'Wait 5 seconds before switching back to SiteMode + CardMode officedoor\entrynormmode = 3 'SiteMode + CardMode officedoor\entrynocommmode = 3 'SiteMode + CardMode GOTO Watching ENDIF --------------------------------------------------------------------- Press the # key once, it will place the door in PINMode (8) for the 5 seconds then back to SiteMode+CardMode (3). -------------------------------------------------------------------------------------------------------- Here are the available EntryNormMode and ExitNormMode values SiteMode = 1 CardMode = 2 GeneralMode = 4 PINMode = 8 If you plan to use more than one add the two numbers together (Example: SiteMode + CardMode + PinMode = 11) ------------------------------------------------------------------------------------------------------ Here are the available DoorFault values 1 = Database of doors, areas, and personnel is not functioning normally 2 = Entry Keypad is being tampered with 4 = Exit Keypad is being tampered with 8 = Entry Card Reader is being tampered with or has failed 16 = Exit Card Reader is being tampered with or has failed --------------------------------------------------------------------------------------------------------- My Test case: I created a person with a valid card and a valid PIN. When I used the card the door would open, after relock I pressed the # and immediately entered the PIN plus the #, the door unlocked. If you have a door switch you could probably use it instead of the 5 second timer this would give you a little more control over the door so that the next person in line (with a card) would not have to wait. CyberStation (v1.52.0.20021120) NetController (v1.520010) AC1 (v22) HID ProxPro with Keypad Note: this works on an ACX(5740/5720) also IMPORTANT: The sample PE program above only sets the EntryNormMode of the door. The program needs to set also the EntryNoCommMode and possibly the EntryNodataMode. If the door is a dual reader door then the corresponding attributes on the exit side of the door must also be set.

Issue Alarms show up in Active Alarm View but do not show up in any Alarms listviews and do not seem to be logging to the Database. Environment Continuum Cyberstation Cause Enhanced alarm logging does not automatically log intrinsic alarms (Controller Offline alarms). Improper time synchronization between Workstations and field Controllers. Due to this, Listviews were not showing most recent entries as they were being sorted on "TimeStamp" (controller time of the alarm) attribute. Resolution Intrinsic alarms (controller offline alarms) need to have a Workstation setup in the delivery tab of the EventNotification (in the Templates folder). The Workstation needs to have the "Log" box ticked so this alarm to be logged in the database. Normally when using enhanced alarm logging, ticking this box is not required as the enhanced alarm logging takes care of the logging. These intrinsic alarms in the Templates folder are the exceptions to that rule. Confirm the times on your controller and WS are configured properly and showing the same time. Add the TimeOfLog attribute to the AllAlarms listview and change so it sorts on this to see if your alarms have been logged but at a different time. If there are no new entries, then try removing the alarm links to your points (on the alarms tab) and then re-add them and save. Reload the controllers as well.

Issue LON communications not working and error in Application Director: Error initializing LonNetwork javax.baja.LonWorks.LonException: Unable to initialize local lon port {Lon1} Environment G3, ENC, niagara Cause Typically this indicates a hardware issue with the neuron in the ENC. Resolution Open the platform for the ENC and use the Commissioning Wizard to commission the ENC again and see it if recovers.  If error remains the unit must be replaced.

Issue Customer has requested and received the Unlock code for WorkPlace Tech 5.7.7 and does not know where to enter it in WorkPlace Tech. Environment WorkPlace Tech Tool version 5.7.x or 5.8 Cause Needs to enter an unlock code for WorkPlace Tech Tool software. Resolution This process is documented in the section "Installing Unlock Codes" of chapter 5 of the WIBS Installation and Configuration Guide, document, F-26641 and is summarized here.  The installation instructions can be downloaded from the Publication Zone on iPortal (https://iportal2.schneider-electric.com/). Run "Purchase Workplace Tech Software" icon on computer desktop (See below if the ICON has been removed). Click "Unlock" Click on license to be unlocked. Enter unlock code in appropriate field on form Click [Generate License] Click [Done] to exit the Unlock window Click [Done] to exit "Purchase..." program. If the  "Purchase Workplace Tech Software" icon has been removed from the desktop, and WPT 5.7.x or 5.8.x was the first version ever loaded on the computer, the program will be found at: C:\Program Files\WorkPlace Tech\Licensing\Core\WPTLPurchase.exe After opening the program continue with step 2, above.

Issue How to set up ID Works 6.5 in Windows 7 64-bit. Product Line TAC INET Environment ID Works version 6.5 I/Net Seven rev 2.4X SQL2008 R2 (Full) SQL2008 R2 Express Cause Normally this is needed for an upgrade or a new install of ID Works and I/Net Seven on a new Windows 7 64-bit PC. Resolution See ID Works Win7 64-bit Setup.pdf for step by step instructions for setup.

Issue This is a short guide to show the correct use of output blocks with forced values in Function Block programs Environment SmartStruxure AS using Function Block programs Cause There is a design difference between the Vista Menta function block programming and the new version for SmartStruxure. In the old Menta programs it is possible to connect the output from an output block and connect it to an expression block. The forced value from the output block was passed to an expression block connected downstream of the output block. This is NOT supported in SmartStruxure at the current release Ver 1.3 (April 2013) If this is done in SmartStruxure then should the output block be forced in any way the forced signal is ignored by the downstream block Resolution Follow the guidelines as detailed in the attached document.

Issue Satchwell RM3601 mains voltage Light Duty Actuator split phase capacitor motor rating is 24 volts. Environment Satchwell RM3601 mains voltage Light Duty Actuator mounted on Satchwell MB Rotary Shoe Valve Body.. Satchwell RM 3601 mains voltage Light Duty Actuator mounted on Satchwell MB Rotary Shoe Valve Body.. Cause Satchwell RM3601 mains voltage and XRM3201 24 volt Light Duty Actuator both utilise a 24 volt rated split phase capacitor motor. A dropper resistor installed across the RM3601 input terminals during manufacture is designed to enable this Light Duty Actuator to be utilised in mains voltage applications. Resolution The presence of a 24 volt split phase capacitor motor within a RM3601 mains voltage Light Duty Actuator should not lead an installer to believe that the Actuator has been manufactured incorrectly.. A dropper resistor installed across the RM3601 input terminals during manufacture is designed to enable this Light Duty Actuator to be utilised in mains voltage applications.   Please check the latest catalog for current equipment.  

Issue What happens when a device that SmartStruxure has COV subscriptions with goes OFFLINE for a while and then comes back ONLINE? Environment ES AS BACnet devices Cause Documentation Resolution QUESTION: What is the limit on number of COV subscription AS/ES support. ANSWER: There is no hard limits in the AS/ES for number of COV subscription, the server is limited only by resources. QUESTION: How often does the Automation Server subscribe (sends the subscription requests) for the very first time to the other devices? ANSWER: When the subscriptions are first established they are sent immediately to the devices, for example when you save a PE script program any COV created as a result of compiling the program are sent immediately to the device. QUESTION: In the case that the other device (the gateway) restarts or goes OFFLINE, how does the Automation Server handle the sending of the re-subscription requests? ANSWER: If a renewal fails due to device offline, it will be retried every minute indefinitely until it succeeds or the subscription is canceled. So if the device goes offline for a while some of the re-subscriptions will fail and will be re-tried once a minute, when the device is back, within a minute all the failed re-subscriptions will be sent again. QUESTION: Can the COVSubscriptionLifetime and the COVTimerPeriod  be set in the AS? or is it only in the ES ANSWER: They can be set in both the ES and the AS by editing the server.properties file in versions of SBO prior to 1.8.1 In SBO 1.8.1 and above, the settings can be accessed from the BACnet interface manager. QUESTION: Where is the server.properties file located in the server file system? ANSWER: AS: /opt/tac/etc (1.4.1 and below) AS: /opt/sbo/etc (1.5.0 and above) /opt/tac/db (1.4)   /var/sbo/db (1.5) /opt/tac/db (1.4)   /var/sbo/db (1.5) /opt/tac/db (1.4)   /var/sbo/db (1.5) ES:  "C:\Program Files\Schneider Electric StruxureWare\Building Operation 1.x\Enterprise Server\etc\  

Issue Procedure to replace Satchwell MicroNet MN300, MN440, MN500 or MN620 controller with Satchwell MicroNet 50 series controllers MN350, MN450, MN550 or MN650 Environment Satchwell MicroNet series controllers: MN300, MN440, MN500, MN620 MN350, MN450, MN550, MN620 Satchwell VisiSat version 2.1 and above. Cause Satchwell MicroNet series MN300, MN440, MN500 and MN620 are no longer available for sale and they are replaced by the MN350, MN450, MN550 and MN650 controllers respectively. See Product Announcement for details. MN300, MN440, MN500 and MN620 controllers installed on existing installations that are required to be replaced would have to be replaced with the new range of controllers. Resolution To replace Satchwell MicroNet MN300, MN440, MN500 or MN620 controller with Satchwell MicroNet 50 series controllers MN350, MN450, MN550 or MN650 follow the procedure below. Pre-VisiSat 2.1 projects (VisiSat 1.2 and VisiSat 2.0) should be upgraded to VisiSat 2.1 using the Project Upgrade Utility. Download VisiSat 2.1 Engineering Guide here. Refer to pages 47 - 50 for using the Project Upgrade Utility Open the VisiSat project Right-click on the existing controller and select "Upgrade Controller." There is a prompt to save the controller configuration (.CLC file). Select 'Yes'. The controller object in VisiSat will now be converted to a MN50 Series controller. Replace the controller hardware. Make sure the jumpers are set correctly and that communications card, if existing should  be taken out and installed into the new controller. Right-click on the controller object in VisiSat and select 'Configuration Library'. Select 'Download Configuration' (2nd button from the left in the Configuration Library). This will download the configuration to the new controller. Refer to pages 135 - 140 in the VisiSat 2.1 Engineering Guide for using the Configuration Library. NOTE: In the Configuration Library, the first button from the right is the "Upgrade Controller" option. This performs the same function as the "Upgrade Controller" mentioned in step 3 above.

Issue Error "Invalid Server Type" when attempting to log into the Project Configuration Server (PCS) Product Line EcoStruxure Building Operation Environment StruxureWare Building Operation 1.5 and newer Cause Attempting to log into the Enterprise Server IP and Port address with Workstation for Projects Resolution Ensure that the Project Configuration Server is installed. Open Software Administrator and check that the Project Configuration Server tab is shown. If not then the server has not been installed. Install this first When using Workstation for Projects, make sure you use the correct port setting (HTTP or HTTPS) as defined in the Software Administrator