Building Automation Knowledge Base

Issue Replacement an AF24-S Actuator? Environment AF24-S Damper Cause Customer requires a replacement actuator for a AF24-S. Resolution The AF24-S is a 24v power open, spring return damper actuator, it has a torque of 15 Newtons. To view the data sheet, please click HERE. The replacement actuator range is the MD10SR/MD20SR ranges. The MD10SR damper actuators have a torque of 10 Newtons (dampers up to 2m2) and are available in the models shown below. To view the full data sheet, please click HERE.   The MD20SR damper actuators have a torque of 20 Newtons (dampers up to 4m2) and are available in the models shown below. To view the full data sheet, please click HERE. In the specific case of the AF24-S the replacement would be the MD20SR-T or -TS if auxiliary switches are required.

Issue MESSAGE [08:29:10 31-May-13 CDT][sys] *** Station Started (203ms) [1919ms total] *** niagara>MESSAGE [08:29:12 31-May-13 CDT][history.db] Starting async warmup of history config index... MESSAGE [08:29:12 31-May-13 CDT][history.db] Async history config index warmup completed in 15 ms. ERROR [08:29:16 31-May-13 CDT][web.server] HTTP Server failed to bind to port. Address already in use: JVM_Bind ERROR [08:29:21 31-May-13 CDT][web.server] HTTP Server failed to bind to port. Address already in use: JVM_Bind Product Line TAC IA Series Environment I/A Series G3 Enterprise Server, all versions Cause Another service on the pc is using port 80, conflicting with the Enterprise Server. For example, Skype will use port 80 as an alternative unless you uncheck the box in Skype options. As a second example, another Niagara station may be running on the same computer. See Changing the HTTP, HTTPS, or TCP ports of the Enterprise Server for a similar port conflict issue with SmartStruxure. Resolution In the Skype menu > Tools > Options > Advanced > Connection, uncheck the box for "Use port 80 and 443 as alternatives for incoming connections"

Issue Older I/A Series G3 stations will not connect to an Enterprise Server that has been upgraded to a release with the 2013 security updates.  Versions with the 2013 security updates include: 3.7.106 (AX-3.7u1) 3.6.406 (AX-3.6u4) 3.5.406 (AX-3.5u4) 3.8.37 (AX-3.8) Niagara Network Fox Connections State remains "Not Connected" and the Last Failure Cause indicates ...        com.tridium.fox.session.InvalidCommandException: Expecting 'challenge', not 'rejected' Environment I/A Series G3, Enterprise Server, ENC, SoftJace Cause To increase system security, the update releases significantly modified how I/A Series G3 station password storage is maintained.  Any system with an I/A Series G3 Enterprise Server that transitions to an update release for the first time has a few extra steps involving the Enterprise Server station. Schneider Electric strongly recommends reviewing your security situation and upgrading the latest I/A Series G3 software with updated security measures. Resolution The following is an excerpt from the NiagaraAX 2013 Security Update document included in the docs folder for each of the 2013 security update builds.  The steps detail how to modify the Legacy Authentication setting to relax security for stations operating at previous builds. Setting Legacy Authentication within the Fox Service: In Workbench, open the running Supervisor station (Fox connection). In the Supervisor station, open the property sheet of its NiagaraNetwork - Config > Drivers > NiagaraNetwork. Expand the FoxService and look for a new property Legacy Authentication. Change Legacy Authentication from the default “Strict” to “Relaxed Until” (shown below) and then Save.  For further details, see “Fox Service properties” in the NiagaraAX Drivers Guide. This should be a temporary setting only. Reset this to “Strict” in the Enterprise Server’s FoxService after you complete upgrading I/A Series G3 in the subordinate ENC/JACE hosts (represented in the Enterprise Server’s NiagaraNetwork).  Relaxed authentication in the Enterprise Server’s FoxService allows its subordinate ENC/JACEs to continue to communicate with the Enterprise Server until they have been upgraded.  This is necessary to continue operations like remote alarming, archiving histories, and so on. However, you should NOT leave the Enterprise Server in this state, as this negates much security (see Caution). Caution:  Unless set to “Strict”, either “Relaxed” option is effectively the same as setting the FoxService property Authentication Policy to “Basic”, as this is the only “common ground” authentication between a legacy Fox client (Workbench or another station) and this update release station. Thus, passwords for client connections to this station are passed in clear text. Obviously, this is not a desired operating state.  For this reason, you should seldom (if ever) set the Legacy Authentication property to “Always Relaxed”.

Issue When a modbus AO is created and set to 32-bit real swapped, the correct value is not seen at the modbus device. 1000 is written and 1000 is shown correctly at the Modbus device. 1001, 1002, 1003 are written but 1000 is seen at the Modbus device. 1004 is written and 1004 shows correctly at the Modbus device. And so forth. The larger the number, the larger the error increase. Product Line EcoStruxure Building Operation Environment Enterprise Server (ES) Automation Server (AS) Cause When 32 bit real swapped is selected Further down the configuration page, the write function code defaults to "06". 06 is to set a single 16-bit register write and this needs to be changed. Resolution Use the drop down tab and set the function code to "16". 16 is to preset multiple registers i.e. 2 off consecutive 16-bit registers or a 32-bit register.

Issue Choosing a terminator, found there were several choices (Loytec and TAC). Which one should I choose? What are the differences between them? Environment Vista LON physical network FT-10 Cause There are several types of terminators for different use in the LonWorks network. Resolution TAC terminators One TAC terminator has 4 wires, however, only need to connect two wires (red or green). Red wires are used for bus topology Lon structure. And, green wires are used for free topology Lon structure. TAC terminators can only be used in FT-10 (78kbps) LonWorks network. In addition, one TAC terminator can only connect to ONE end of a channel. Which means, a channel without a repeater, you need TWO TAC terminators, and a channel with a repeater, you need FOUR TAC terminators. Note: To test an end of the line resistor (EOL), take a reading of the capacitance across the leads (either the two green or two red leads). You should read somewhere around 50 uF.  LOYTEC terminators (L-term) For LonWorks networks, Loytec has 3 different types of terminators: LT-03, LT-13, and LT-33. LT-03: One network terminator for TP/FT-10 channel (bus or free topology), similar to TAC terminators.  LT-13: One network terminator for TP/FT-10 channel (bus or free topology), and one network terminator for TP/XF-1250 channel (bus or free topology). Barely used in TAC Vista system. LT-33: Two network terminators for TP/FT-10 channel (bus or free topology).  One connection is on the top, and one is at the bottom.  Since you cannot separate two connections, most likely it is used before and after a repeater.

Issue A Door configured with Magstrike status as Door Status re-locks after 2s  even when Door Strike Time is set to 10s. Environment Continuum Access Control Cause The Door output will relock after the Door Strike Time or when the Door is opened. Since you are using the mag lock status as the Door status (not the preferred method), then as soon as the Door is unlocked, the mag lock is de-energized which turns off the Door Status which then relocks the Door 1s later. Resolution You need to monitor the actual physical status of the Door to indicate when it has physically opened and shut. Either that or remove the input from the Door object by setting the Door Status channel to 0. This should allow the Door to stay open the DoorStrikeTime. You can also use a PE program to get around not having a DoorStatus that monitors the actual Door. This post on the Community discusses this and has some good comments about using this type of Door control with the maglock status instead of a true Door Status switch and is worth a read. Below is an example Plain English program that can help monitor the Door for ValidAccess then hold the Door unlocked for the DoorStrikeTime. 1: If Door1 ValidAccess is On then Goto 2 If Door1 ExitRequest is On then Goto 2 2: Door1 = UnLocked If TS > Door1 DoorStrikeTime then Goto 3 ' wait for DoorStrikeTime 3: Door1 = Locked Goto 1

Issue Extended Logs have stopped updating on the Enterprise Server. Product Line EcoStruxure Building Operation Environment Extended Trend Logs Cause Extended Trend logs have been set up on the site for some time and have operated correctly. Now some of them have stopped updating.  Resolution This issue can be caused by a Server backup being restored. Trend logs and Extended Trend logs are allocated sequence numbers, and if the sequence numbers do not follow the correct sequence, the Extended Trend log may not update. To confirm that this is the issue; Trend Log. Navigate to the Trend log and open it in a "Trend Log List" view. Add an additional column to show the Sequence number. Note the highest sequence number used. Extended Trend Log. Navigate to the Extended Trend log that is referencing the above Trend Log. Open it in a Extended Trend Log properties. Press and hold down the "ALT" key and click where the dot is indicated on the screen shot below, (just below the Basic tab).       This will show some more properties for the Extended Trend Log, the one you are interested in is “Last transferred sequence number”.   If the last transferred sequence number on the Extended Trend Log is higher than the Trend log’s highest sequence number, then that is why the Extended Trend Log has stopped. How can this issue be resolved? Increase the sample interval of the Trend log until it has caught up. The Extended Trend Log will only fetch new records that has a sequence number higher than the last transferred sequence number. So until the sequence has caught up, you will not see any new records in the Extended Trend Log, and only records created after you have caught up in sequence numbers will be fetched. Re-create the Extended Trend Log. The new Extended Trend Log will fetch every record the log has and continue from there, but you will lose the records the old Extended Trend Log had that the log does not have anymore. Backup / restore on the AS. The Trend log will be cleared but the Extended Trend Log will start fetching new records.    

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 The Modbus Server / Client is unable to read the values from address of a 32 bit Modbus register in a Building Operation server Product Line EcoStruxure Building Operation Environment Building Operation server Modbus Cause The original Modbus/JBUS protocol specifies the use of 16-bit integer registers for Analogue Inputs and Analogue Outputs. The number range able to be represented in 16-bits is: Unsigned: 0 to 65353 Signed:     -32768 to 32867    In order to represent larger numbers, it is common for 16-bit registers to be combined to represent 32-bit or 64-bit numbers. When a Modbus Client or Server reads a 32-bit Modbus value, it will be reading two consecutive 16-bit registers. An error will occur if  two 32-bit Local Modbus registers are created in Building Operation using consecutive register addresses since only the starting modbus register address is used for the request.  Resolution When configuring 32-bit Local Modbus registers in Building Operation, the next register address should not be used. Create the next Local Modbus register using the 3rd available Modbus register address. 

Issue Some links in graphics are unresponsive on Advanced Display when running EBO 1.9.4. Product Line EcoStruxure Building Operation Environment Building Operation Advanced Display V2 Building Operation Advanced Display V3 EcoStruxure Building Operation v. 1.9.4 Cause The links that are unresponsive are trying to open the target in a floating window. This is not supported on Advanced Display with WebStation when using EBO v. 1.9.4. More specifically the graphics script function is not supported under the conditions mentioned above. invoke("Link", "OpenInFloatingWindow"); Resolution Use alternative arguments other than "OpenInFloatingWindow" such as "OpenInNewWindow". See the WebHelp Section Invoke Function for more information about the Invoke function.

Issue SEC-TE (TE2) smart terminal controller / SED-0 (DA2) smart wireless actuator will not come online in an MPM controller. Product Line EcoStruxure Building Expert, Field Devices Environment SmartStruxure Lite Multi-Purpose Manager Smart Controllers Cause The Zigbee network configuration parameters in the MPM have been entered incorrectly. Resolution The application version of the SEC-TE/SED-0 must be determined before proceeding forward. Sticker on device should read V13 or V14. To check/modify the current settings, navigate to the "ZigBee Configuration" object (ZBC) under the MPM. For Application Version 13: Stack profile should be set to "Custom" and Security profile should be set to "None." For Application Version 14: Stack profile should be set to "ZigBee Pro" and Security profile should be set to "Home Automation."

Issue What type(s) of 125 kHz proximity cards are supported by Security Expert Card Readers? How to configure Secure Expert to read an Indala card (125 kHz)? Product Line EcoStruxure Security Expert Environment Security Expert Smart Card Reader Cause Card readers work by modulating the electromagnetic wave in different ways to resolve between 1s and 0s. There are several different ways to bring card data across 125 kHz; ASK, FSK and PSK. ASK : Amplitude Shift Keying FSK : Frequency Shift Keying PSK : Phase Shift Keying Since the technology used is determined at the hardware level,  a reader would need to have the hardware to read a specific type. Security Expert 125 kHz readers make use of FSK only, which means that e.g. Indala cards (125 kHz PSK technology) will not work with them. Resolution Use FSK technology 125 kHz cards with Security Expert Smart Card Readers.

Issue When a user logs on to Workstation and accesses the hyperlink, the website is displayed without prompt for login credentials Product Line EcoStruxure Building Operation Environment Building Operation Workstation Microsoft Internet Explorer Cause EcoStruxure Building Operation software uses Microsoft Internet Explorer to present web pages. How the page logs on is an IE function and not a function of EBO Workstation Resolution  Log off from the web site before logging off from Workstation  Configure Internet Explorer to delete browsing history on exit Go to Internet Explorer settings and then the Internet Options On the General tab, under the Browsing history, enable the checkbox for 'Delete browsing history on exit' (computer restart may be required)

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 for assistance. Issue When you attempt to save a Menta application in Workstation you will get an "Invalid Data" Error. Product Line EcoStruxure Building Operation Environment Building Operation Workstation Building Operation Menta Editor Cause Some public variable in the Menta application has had Initial bindings added that conflict with the EBO bindings. Resolution Remove the Initial bindings from the variables in the Menta application and use EBO bindings. To find these Initial bindings follow these steps, Edit the Menta device with the issue From the File Menu "export" the Menta application to a known location on the PC and save it as a MTA file. Browse to this MTA file you exported and open this file with the Menta Editor From the File menu select "Save as" option. Give the file a name and in the Save as Type select FDB (*.AUT) Using Note Pad++ edit the AUT file you just created. Search the AUT file for the label "InitialBindings" [see Figure1 below] Make a note of the objects with Initial bindings so the initial bindings can be deleted from the Menta file. In Workstation edit the Menta device and remove the initial bindings from the objects found in step 7 and change the name of the object noting the original name down. Save the Menta application to the server. In Workstation edit the same Menta device and rename the object back to the noted name in step 8. Save the Menta application.

Issue Following an upgrade to V1.5 from V1.4 the AS goes off/ online. Environment Automation Server AS Enterprise Server ES V1.50 and above. Cause Following an upgrade to V1.5 from V1.4 the AS goes off/ online caused by an incorrect setting of the Default Priority Level. Resolution This issue only occurs if the site has changed the BACnet "Default Priority Level" from the default value of 16, to 8 or a smaller numeric value in the Automation Server while running in V1.4. So before upgrading to 1.5 make sure the "Default Priority Level" within the Automation Server is set to 9 or higher. If the system has been upgraded with the incorrect values, then:  If the site uses single servers, or the ES/AS communication still operates correctly, then this can be corrected by changing the setting in both the AS and the ES to a value of 9 or higher. If after upgrading a multiserver configuration and the AS does not stay online, then a Hotfix can be used fix the problem using the following steps: 1. Apply the hot fix #1.5.0.4301; available from Product Support Services 2. Fix the multi-server (by detaching/re-attaching the servers) 3. Correct the two properties (AS and ES). WARNING: It is essential for any BACnet system at 1.5 or later that the "Default Priority Level" has a larger numeric value than the "Force Priority Level, otherwise some BACnet functions may not behave as expected, this also applies even if the hot fix is installed. The effects of not setting the Default above the Force Priority level are: 1. If Force Priority Level is equal to the Default Priority Level: Changing the Value of a BACnet value or a BACnet output object will cause the Value to appear Forced. This applies to the BACnet objects in both SBO servers and those in 3rd party BACnet devices. 2. If Force Priority Level has a larger numeric value than the Default Priority Level: Changing the Value of objects mentioned above will cause the Priority Override icon overlay to be turned on next to the Value property in the WorkStation’s property grid. Note: The Default and Force Priority Level are located/ defined in the Green "System" folder, "Interface Manager", "BACnet" for each Server.

Issue Values are coming into Vista without issue but do not update on the graphics in the Xenta 7XX. Product Line TAC Vista Environment Workstation Graphics Xenta Server 701, 711, 721, 731 Cause If there is a Xenta Server in the database, when connection objects are not used to bind values between a controller and a Menta program in the Xenta Server, this graphic update can occur. It can also be because of the XIF for a device being formatted incorrectly. If the procedure below doesn't solve the issue, refer to LON device can communicate in Vista, but fails in a Xenta Server / XBuilder Resolution There are two options to correct this issue: Re-engineer the XBuilder project to use connection objects between the controller and the Menta program in the Xenta controller. The control task speed of the Menta program in the XBuilder project can be changed to a lower speed setting.

Issue Need to capture steps taken to reproduce a problem or a solution Product Line Andover Continuum, EcoStruxure Building Expert, EcoStruxure Building Operation, Field Devices, OTHER, Satchwell MicroNet, Satchwell Sigma, TAC IA Series, TAC INET, TAC Vista Environment Windows 7 Windows 10 Windows Server 2008, 2012, 2016 Cause A series of screen captures will help to demonstrate the steps needed to reproduce a problem or a solution. You can use this tool to capture the steps you take as a problem occurs and send the output to someone so they can see a screenshot of each step. Resolution In Windows click on the Start menu button  Type "PSR" Windows 7Windows 7 Windows 10, 2012, 2016Windows 10, 2012, 2016 Open the Problem Steps Recorder Windows 7Windows 7 Windows 10. 2012, 2016Windows 10. 2012, 2016 Click Start Perform the desired tasks Click Stop Choose a location to save the file output The .zip file will contain a .mht file which can be opened in a web browser The screenshots will appear in order  This will be followed by a detailed output of keystrokes and mouse movements. For additional information please refer to Microsoft webpage on this topic: Record steps to reproduce a problem 

Issue Relay Control With Xenta Analog Output Product Line TAC Vista Environment Xenta programmable controllers Xenta 281, 282, 283, 301, 302, 401 Cause Occasionally installers of Xenta controllers are using the Analog Output (AO) of the Xenta controllers to control one or two external relays. This is being done when the HVAC application needs one or two more points of discrete on/off control and when the AOs are not needed for proportional control. Obviously, this deviation from normal I/O application is being entertained in a effort to avoid additional costs of higher capacity controllers and/or the Xenta I/O expansion modules. Implementation has consisted of a 12Vdc relay connected to the AO output and the AO is directed to 100% output (10V) to energize the relay and 0% output (0V) to de-energize the relay. Resolution While this AO relay control application has not been recommended for typical designs, it should be possible to accommodate it reliably as long as some specific considerations are included in the relay selection and installation. For more information please use the following link: Xenta Analog Output

Issue Extended Elevator control (Step by step instructions) Product Line TAC INET Environment I/NET Seven DPU Firmware 3.20 or above. (DPU7920 with 48k MIP or SCU1284) Cause Extended elevator control allows support up to 79 floors and easier programming methodology than the traditional method.  This has been added to I/NET Seven software and DPUs as detailed in the environment.  Resolution To use any of these features requires that the DPU be a 7920 w/ MIP board or the new SCU1284. 7910 and 7920 w/o MIP board will still work with the I/Net system but they cannot use these functions. The host prevents the download of these features to any DPU revision prior to 3.10.   Extended Elevator Control Setup Example This is based impart on basic prior knowledge of InetSeven Host software setup and configuration to include but not limited to Controller Station Parameters, Resident I/O, Point Extensions, Operations of Network Configuration, and Access Configurations (Doors, Tenants, Groups, Individuals and Personnel Schedules). Hardware required: DPU 7920 48k (The following control will only apply to the 7920 48k) Please follow these steps to configure extended elevator control. Resident I/O Editor Edit / Controller / Resident I/O – Add the following Internal DO Door Reader point Internal DI point for each Floor DO External DO point for each Floor button DI Note – Save Door in the Network Configuration editor. Controller Door Editor Edit / Controller / Door Editor Select Door to add Elevator Control Modify – check Elevator Control box Select “Message type” Alarm / Transaction Note – Ensure a Schedule (s) has been assigned to the Door reader point. Controller Elevator Parameter Edit / Controller / Elevator Add Elevator Extension to reader point. Add Floor parameters. Complete the following; Floor Index Selection Floor designation Button Enable (DO) Button Selection (DI) Note – When finished “STOP” Do not select floors, Select OK and Close. Network Configuration  Edit / Host Computer / Network Configuration. Penetrate down to the DPU (Door Read Point) with Elevator Control Penetrate one more level and SAVE all your floor extensions. Tenants Access / Tenants Select Tenant Locate Door Reader point – Remove “X” (Unselect). Place an “X” next to all floors that tenant will have access to – Select Ok At this time I would suggest performing a save function followed by an SLI and DPU restore. Individual Editor You are now ready to add individuals or assign individuals access to floors.

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 Dependencies for Vista Server running as a service Product Line TAC Vista Environment Vista Server Cause The Vista server can run into issues if it starts up before other services. Resolution Ensure that Vista Server does not start up before Aladdin Privilege Server by making some changes to the registry. Select the start menu, select run, and type “regedt32”. Once the program opens you should browse to the following path: HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\TACOS\ The key named DependOnService should by default contain the value RPCSS. To add a dependency to this service just modify the value of the key and add the name of the service you wish to start before this one. In the case of Aladdin Privilege Server just add the text “Privilege Win32 Server” to the registry key. Close the registry editor and the dependency will be visible in the services properties window for TACOS. Note: If you need Vista to start late in the boot cycle but you do not have a specific service dependency, as explained above, then choose one of the services which startup last as the data value for the value "Depends on Service". Services commonly selected are Spooler and Messenger.