Building Automation Knowledge Base

Issue CX level controller was once online and now appears as offline Product Line Andover Continuum Environment Continuum Netcontroller CX ACX BCX Cause From time to time issues will be reported that controllers are offline at the IP level. Resolution Troubleshooting steps to perform:   From one of the existing sites Cyberstations perform a ping of the controller. If there are responses, verify that the response is from the controller and not another device. Verification of the response can be done via Wireshark capture if the CX appears to be responding. If there are responses to the ping, then attempt to open up the web-configuration page for second generation controllers. Verify the site’s Cyberstation is online itself. (Right-Click/edit the workstation and view the Comm Status. It will be either Online or Offline.) With CyberStation installed on technician’s laptop with the same version as the site version. Plug an Ethernet cable into the same hub the controller is plugged into. Connect to the site database with the local laptop's CyberStation and start Continuum. Check the controller in Continuum Explorer to see if it shows offline to the local laptop's CyberStation. If the controller is online to the local laptop's Cyberstation, then it is clearly a site network issue. At that point we will need to make sure all the IP address info is correct; there is no port blocking, subnet masks, gateways etc… Standard network troubleshooting. If the controller shows offline to the local laptop's CyberStation, then look at the CPU lights on the controller for activity. Watch the link light, CPU, IO bus lights if there is IO modules, etc… If those look abnormal and you have a smart phone it will be worthwhile to try and get a video of them to send into support for review. If there is no link light then try disconnecting the Ethernet cable from the NETWORK SWITCH and plug it back in to check if it brings the controller back online. If that does not bring the controller back online try disconnecting the Ethernet cable from the CONTROLLER and then immediately put it back and check if the controller comes back online. If all of the above fail then the next step will be to power cycle the controller to try and bring it back online. If communications cannot be established, contact support and open up a case for additional troubleshooting to determine if the controller needs to be sent to repair. If communications is restored and further investigation is required, please retrieve the following information and open a case with support for review. Controller error log Controller offline listview exported to CSV A Wireshark LAN capture at the controller level with peak traffic occurring Additional information may be requested including a controller core dump. This is a very intensive process. Support will supply the Core Dump Utility if needed.   Please click HERE for a copy of these instructions in PDF format.

Issue Procedure to activate the Add-on reports module. Environment Continuum Add-on reports module. Cause Received an Activation Code from the COE Team, need to know the procedure to activate the Add-on reports module. Resolution You will receive an Email from the COE Team with the Activation Code along with Instructions on how to activate it. For your Convenience the instructions are below. ACTIVATION INSTRUCTIONS - CONTINUUM REPORTS INSTALLED IN C:\PROGRAM FILES Make sure Continuum is not running Make sure Continuum Reports is not running Launch a DOS Command Window CD "Program Files\Continuum_Reports" Enter in lower case: reports key writer Enter the activation code. (Note: Case sensitive)   -(OR)-   ACTIVATION INSTRUCTIONS - CONTINUUM REPORTS INSTALLED IN C:\PROGRAM FILES (X86) Make sure Continuum is not running Make sure Continuum Reports is not running Launch a DOS Command Window CD "Program Files (x86)\Continuum_Reports" Enter in lower case: reports key writer c:\progra~2\continuum_reports 6. Enter the activation code. (Note: Case sensitive)Activation Instructions - Continuum Reports installed in C:\Program Files 1. Make sure Continuum is not running 2. Make sure Continuum Reports is not running 3. Launch a DOS Command Window 4. CD "Program Files\Continuum_Reports" 5. Enter in lower case: reports key writer 6. Enter the activation code. (Note: Case sensitive) -or- Activation Instructions - Continuum Reports installed in C:\Program Files (x86) 1. Make sure Continuum is not running 2. Make sure Continuum Reports is not running 3. Launch a DOS Command Window 4. CD "Program Files (x86)\Continuum_Reports" 5. Enter in lower case: reports key writer c:\progra~2\continuum_reports 6. Enter the activation code. (Note: Case sensitive)

Issue Need to bring Continuum system into SmartStruxure. Product Line EcoStruxure Building Operation Environment StruxureWare Building Operation v1.3, Continuum v1.94 system with BACnet bCX and b3 devices Cause b3 devices under the bCX become BACnet devices as if they were 3rd party BACnet devices. Resolution Test Environment: Cyberstation 1.94, SmartStruxure 1.3 Released, (1) AS-B, (2) bCX4040, one bCX hosting (2) B3 devices. Do BACnet discovery from SmartStruxure. Both bCX's and the b3 devices can be seen From the Hardware\BACnet devices folder, multi-select both bCXs and drag them into the BACnet Interface\IP Network. Upload their BACnet objects to SmartStruxure. From the Hardware\BACnet devices folder, multi-select both B3 controllers and copy/paste them into the BACnet Interface\IP Network. The B3 devices are hosted as, and look like, generic BACnet devices. Once the two B3s have been copied to the IP Network, an upload to SmartStruxure can be done. BACnet Digital Values and BACnet Analog Values on the b3 devices can be seen updating on a SmartStruxure listview. Note: Currently in SmartStruxure v1.3 there is no method to multi-select and host B3 Devices, within an MS/TP network. This functionality is part of the Continuum Migration project (a future version). Also check out the b3 VAV Quick Start Video on the Exchange.

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 Proxy objects were successfully created in a G3 obix integration of a R2 station.  The writable proxy objects (ie: setpoint overrides) in the G3 station do not propagate the new value to the native object in the R2 station. Environment Niagara G3 Niagara R2 Cause This is a known issue with the G3 obix driver. Resolution Right-click the proxy object in the G3 station and do a 'forceUpdate'. If there are several dozen proxy objects affected, download this program object.  Paste it anywhere in the Obix Network and execute it.  A 'forceUpdate' will be done to all proxy objects. As of June 2013, these are the most up to date jar files for an obix integration:  2.301.535i.beta.jar, 2.301.535i.beta.jar.pc, and niagaraDriver.zip. Extraction password:  niagara (all lowercase)

Issue There are many existing TGML graphics templates, components and snippets. Many of them have the animation binding with the digital value 0/1. But for SmartStruxure, especially the values from Continuum controller, it will show ON/OFF or ACTIVE/INACTIVE instead of 0/1. If binding these values directly to the graphic, the animation will not work. Environment SmartStruxure Cause The binding text or property should match the real value from the controller. Resolution Instead of modifying the TGML graphic, we have a better way to solve this problem. Double click the value that needs to be bound, and open the property window of the value. There is a property called 'Active Text' and 'Inactive Text' for this value. We can change the 'Active Text' to '1' and 'Inactive Text' to '0', then all the bindings can be used without any modification. But it depends on the workload of the project. If there are many values with a few controllers, maybe modifying the graphics is a more efficient way.

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 Default IP address of a SmartStruxure Lite MPM Product Line EcoStruxure Building Expert Environment MPM Cause What is the default IP address of a SmartStruxure MPM? Resolution Out of the box, the default IP is 10.50.80.3 subnet mask 255.0.0.0 This should be changed to suit the project requirement. Log into the controller using the default IP address. Edit the Ethernet setting, changing the IP address, Subnet Mask and Default Gateway. Click save.

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 What is the procedure for using a BCX9640 to replace a CX controller. Environment BCX9640 Comm Port Cause Need to change the Infinet Controller type. Resolution A BCX9640 is not the preferred replacement for a NetController for several reasons, among which are the following..  Can only support one Infinet port (Comm 2). Does not support L-Bus Does not support IO Module control. The process for replacing a NetController with a BCX9640 is as follows. Print a list view off all Infinet Controllers under the NetController.  This list must include the following columns... SerialNum CntrlType InfinetID Create a new BCX9640 with a new ACCID and bring it online. Switch Cyberstation to offline editing mode. Change the serial numbers of all Infinet Controllers under the NetController false serial number (so that the serial number for each Infinet Controller will be available for each new Infinet Controllers created under the BCX9640). With the workstation in Offline mode, manually create all the Infinet Controller object that existed under Comm 2 of the BCX9640.  Use the following information, The same controller model that the Infinet Controller had under the NetController. The same Infinet ID that the Infinet Controller had under the NetController. Drag and drop copy all the points and programs from the original controller to the new controller. Verify that all the points and programs were correctly copied and are intact. Go into the new Infinet Controllers and change their serial numbers to the serial number it had under the NetController. Next go back to online editing. At this point you should see all your infinet controllers come back on line. Finally reload the complete site. It is important to note that any controllers that are referencing points in the relocated controllers will have to have these object references verified and repaired in cases where the references have been lost.

Issue Alarm window either does or does not display on alarm as desired Product Line EcoStruxure Building Operation Environment Building Operation Workstation Cause The Alarm View Properties are not set correctly Resolution Right Click in the Alarm View window and select Alarm View Settings>Properties Change the Display on Alarm Property to the desired state.

Issue Is it possible to prevent a 3rd party BACnet Operator Workstation (BOWS) from deleting the BACnet objects in an Enterprise/Automation server? Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Automation Server Cause Current version of EBO/SBO puts the responsibility of creating & deleting BACnet objects to the site administrator.  The enhanced security on this issue will be added in the later version. Resolution The following video demonstrates how to protect the BACnet objects in ES/AS by utilizing shortcut objects.    

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 The output of the actuator block in a MNB-Vx sometimes shows 'NaN' (Not a Number) instead of a valid position. The only way to clear it is to drive it fully open or fully closed. The issue is intermittent and it is not specific to the same installed controllers. It appears on different controllers at different times. Product Line TAC IA Series Environment MNB-Vx Cause The actuator can be initialized to avoid displaying 'NaN'. The setting in the VAV actuator block is called InitMode. Here's a description of this setting from the WorkPlace Tech Engineering Guide Supplement (F-27356): Abbreviation Configuration Property Description Range InitMode Initialization Mode Class: Enumeration - The initialization mode configuration property controls synchronization of the VAV object position output after a rest. 0 - No automatic synchronization of the position output. Synchronization occurs when normal control causes the actuator to drive full open or full closed. 1 - Actuator drives full closed after a controller reset to synchronize position output 2 - Actuator drives full open after a controller reset to synchronize position output 0-2 If InitMode = 0, and the actuator doesn't drive full open or full closed for a long period of time, the NaN value will continue to be displayed. Resolution Ensure InitMode is set to either 1 or 2 so that it synchronizes after a power cycle or database download.

Issue Modem commands for the internal modem for the 9680 are needed Environment 9680 RAS Cause Troubleshooting the modem in the 9680 may require knowledge of the Microtech modem and the commands Resolution The Netcontroller II Operation and Technical Guide references "RJ Modem AT Commands Reference" in order to customize the modem initialization string Click her to download RJ Modem AT Commands Reference There is no option for changing the DTMF frequency Guide"

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 Site Access Control lockdown for the entire complex. But, also allow certain cards to override certain doors during an emergency situation. Environment I/NET site with access control Cause There is a requirement to lockdown an entire complex with a single toggle switch, but allow First Responders access to certain locked doors in the building. Resolution  There are two different Demo programs for this process One Link program (Download One Link Zip file): MCI -- 7798 DPU – SCU1284 (2 addresses) A maintained switch SPDT   Two or more Links program (Download Two Link  Zip file) MCI – 7798 Link1 MCI – 7793 Link2 – Channel “B” SCU1284 (2address) Link1 SCU1284 (2address) Link2 – On second channel A maintained switch SPDT Each of the above zip files have the following inside: Note: This would be restored to your test bench, and then configuration implemented into a production site.

Issue Require method on how to Arm and Disarm an Area by Triple Badging at the Door. Product Line EcoStruxure Security Expert Environment Security Expert Cause Require Door to be controlled by a Schedule but also to allow a valid User to override the Schedule with three consecutive valid badges. Resolution Required Objects virtual Output - Flag to control area status (v_TB_AreaArmedFlag) Area - Area to control (TB_Inside_Area) Programmable Function - Arms Area when virtual output ON (TB_Inside_Area_Arm_PF) Programmable Function - Disarms Area when virtual output OFF (TB_Inside_Area_Disarm_PF) Schedule - Operating hours of Area (TB_Schedule) Door - Door to control Area status (TB_Entrance_Door) Configuration Create virtual Output v_TB_AreaArmedFlag. Set Module Type to Output (PX) and Module Address and Module Output channel to ones that do not exist. virtual Output On the Reader Expander > Reader 1 tab - Set Reader 1 Arming Mode to Toggle Function Output on 3 Reads Set Reader 1 Function Output to v_TB_AreaArmedFlag Reader Expander - Configuration Under Reader Options section set Allow Reading Opened/Unlocked. Under Misc Options section set Allow Access When Area Armed Reader Expander - Misc Options On the Doors > General tab - Set Area Inside Door to to TB_Inside_Area - Set Unlock Schedule to Never Door - General On the Options tab under Door Options 2 section  - Set Door Lock Follows Inside Area Door - Options On the Area > Configuration tab under Schedule set Arm/Disarm Schedule to TB_Schedule Set Disarm Area When Schedule Starts Set Arm Area When Schedule Ends Area - General On Outputs tab set Armed Output to v_TB_AreaArmedFlag Area - Outputs Go to Automation > Programmable Functions and create TB_Inside_Area_Arm_PF - Set Type to Area Control - Set Mode to Normal Programmable Function - Arm - General Under Area Control tab - Set Area Function to 2 - Area Arms on Output Turning On - Set Output To Check to v_TB_AreaArmedFlag - Set Area To Control to TB_Inside_Area - Save changes - Right-click TB_Inside_Area_Arm_PF function and select Start Programmable Function - Arm - Area Control Go to Automation > Programmable Functions and create TB_Inside_Area_Disarm_PF - Set Type to Area Control - Set Mode to Normal Under Area Control tab - Set Area Function to 5 - Area Disarms on Output Turning Off - Set Output To Check to v_TB_AreaArmedFlag - Set Area To Control to TB_Inside_Area - Save changes Right-click TB_Inside_Area_Disarm_PF function and select Start Programmable Function - Disarm - Area Control