Building Automation Knowledge Base

Issue When changing name of a trendlog in Vista will the name of the trendlog in the SQL server also change? This is when using Vista 5.1.7 and have upgraded the SQL database. Environment TAC Vista 5.1.7 Cause The name of the trendlog in the SQL database will change when the next value for that trendlog is written in to the SQL database. Resolution The name of the trendlog in the SQL database will change when the next value for that trendlog is written in to the SQL database

Issue After a valid door unlock, Continuum, by default, turns off the door lock output one second after the door opens when a door switch is used. How can this sequence be modified? Environment ACX AC1 Cause Due to the locking hardware used, sometimes it is necessary to make sure the door is closed before energizing the maglock. Resolution Use a Plain English program as follows: ' File Name: LONGLOCK.TXT ' Program name: LongLockProgram ' '   This program keeps the door strike energized until after the door '   closes. This is needed for certain types of door hardware. Normally, '   the door strike is de-energized 1 second after the door is physically '   opened. ' ' Flowtype: Looping, Autostart 1:   If Door1 ValidAccess is On then Goto 3   If Door1 ExitRequest is On then Goto 2 2:   If Door1 DoorSwitch is Opened then Goto 3   If TS > Door1 DoorStrikeTime then Goto 1    ' in case the door doesn't get opened 3:   Door1 = UnLocked   If Door1 DoorSwitch is Closed then Goto 4   If TS > 60 then Goto 4    ' safety 4:   If TS >=1 then    Door1 = Locked    Goto 1   Endif

Issue Jace 8000 versus Jace 9000 WiFi specifications Product Line TAC IA Series Environment I/A Series N4 Jace 8000 I/A Series N4 Jace 9000 Cause Defining WiFi feature differences Resolution The JACE 9000 includes a WiFi 5 radio supporting Bluetooth 5.2LE that is currently disabled.   Below is a table of the differences between the JACE 8000 and JACE 9000 WiFi:   Feature JACE 8000 WiFi JACE 9000 WiFi WiFi Standard WiFi 4 (802.11n) WiFi 5 (802.11ac) Switch Type Hardware Switch Software Switch Modes Off, Access Point (WAP), or Client Off, Access Point (WAP), or Client Security WPAPSK / WPA2PSK supported WPAPSK / WPA2PSK supported Bluetooth Not Supported Yet Bluetooth 5.2 LE WiFi Disabled at Factory Depending on SKU Depending on SKU   SKU Details: JACE 8000: JACE-8000-CSE-001 US JACE-8000-CSE-002 WW JACE-8000-CSE-003 NON WIFI JACE-8000-CSE-004 China JACE 9000: JACE-9000-CSE-001 US, CA JACE-9000-CSE-002 WW JACE-9000-CSE-003 NON WiFi JACE-9000-CSE-004 China JACE-9000-CSE-005 EU The JACE 9000 includes a button behind the door that can be configured as "Access Point Controlled" mode, enabling the use of an inactivity time limit for access point availability.  Selecting this mode activates a configurable time limit property for inactivity and the use of the Wi-Fi button to toggle on or off the Access Point availability.   This is similar to the hardware switch of the JACE 8000.    Figures Figure 1 shows the front panel of the New JACE 9000 WiFi Figure 1.1 shows the JACE 8000 hardware switch indication Figure 1.2 shows the JACE 9000 software switch indication  Figure 1 - Front of JACE 9000 panel – WiFi LED and button location   Figure 1.1 - JACE 8000 hardware switch indication   Figure 1.2 - JACE 9000 software switch indication   NOTE: WiFi will not be supported in Jace 8000 with N4.15 release. Blackberry QNX chipset support has been dropped in the Jace 8000. Details and Summary 

Issue PCT2 is unreachable using IP 192.168.10.2, with messages similar to: 504 Gateway Timeout Server error - server 192.168.10.2 is unreachable at this moment. Product Line EcoStruxure Building Operation Environment Project Configuration Tool (PCT) 2 Cause The Hyper-V Virtual Ethernet Adapter in Windows, labeled vEthernet (SwitchPctInternal), is not configured with the proper static IP address. It may be incorrectly configured as DHCP or with an incorrect static IP address Resolution Open Properties for vEthernet (SwitchPctInternal) Go to the Networking tab. Select Internet Protocol Version 4 (TCP/IPv4) and click Properties. Configure the IP Address: Select Use the following IP Address. Ensure the IP address is set to 192.168.10.1. Set the subnet mask to 255.255.255.0. Leave the gateway field blank. Additional Notes Ensure that no other network adapters are conflicting with the vEthernet (SwitchPctInternal) settings. Verify that the PCT2 device is properly connected to the network.

Issue The RoamIO2 does not seem to be able to communicate with an ACX5740, why? Environment RoamIO2, RoamIO Cause What must be done to get a RoamIO2 to communicate with an ACX57xx controller? Resolution The ACX57xx must have comm1 configured as Infinet. This is because the RoamIO2 hardware only communicates via the Infinet protocol (when running the InfinetServiceTool software) or BACnet protocol (when running the BACnetServiceTool software). An ACX57xx is not communicating either of these protocols unless comm1 is configured for Infinet.

Issue What do the LEDs indicate on a MSC-NC or MSC-NCM? Environment DMS Cause Communications is down on a jobsite.  Trying to troubleshoot the MSC-NCM. Resolution Here is the function of each LED: WDT:  indicates processor and MSC-NCM communication status.  One blink/second indicates that the MSC-NCM is communicating with at least one Microsmart controller.  Two blinks/second indicate that the MSC-NCM processor is functioning but the MSC-NCM is not communicating with any controllers.  If it is blinking very fast, the MSC-NCM processor is functioning but the MSC-NCM program has not been downloaded into the controller (hence, the system is down). ALARM:  indicates a service or point alarm condition exists somewhere on the controller trunk TxD:  indicates data transmitted RxD:  indicates data received DCD:  illuminates when the Data Carrier Detect signal is active (used with modems) RING:  illuminates when the modem detects an incoming call

Issue When printing a multiple page application, i.e., an application consisting of a device definition and one or more custom object pages, all pages are numbered 0 of 0. Environment WorkPlace Tech Tool release 5.8.0 or release 5.8.1 Cause The title block stencil script created in WorkPlace Tech release 5.8.0 or release 5.8.1 does not execute properly resulting in all pages showing "Page 0 or 0". Resolution Update to WorkPlace Tech Tool release 5.8.2.  Note that upgrading will not automatically correct the issue in application files created with release 5.8.0 or release 5.8.1.  Use the following procedure to correct the issue in application files created with those releases of the WorkPlace Tech Tool software. Open the application using WPT 5.8.2. Select the "Background" page of the drawing. Press Ctrl-A to select everything on the page then press the Delete key to delete everything from the page. Select the "Annotation" style sheet (stencil page). Drag a new copy of the "Schneider Electric Border" stencil onto the page. Drag a new copy of the "Controller Info Block" stencil onto the page.  This block is normally placed in the lower left corner of the drawing. Save the updated application file.

Issue Added multiple Lon devices to Lon Network and need to mirror SNVTs from more than one device to the Local Node Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Premium Building Operation Enterprise Server Cause Using SNVT bindings between devices and the Local Node of the EBO server allows LON communications bandwidth to be optimized by using the LonWorks protocol Send and Receive Heartbeats configured per device. However, it can be a time-consuming task to mirror SNVTs from multiple identical devices. This time can be reduced by selecting SNVTs in multiple devices using search. Resolution Create a new search Search for one SNVT that is available on multiple devices Use this article to create the mirrored SNVTs in the local node: Creating Network Variables Automatically Search for the next SNVT that is available on multiple devices Repeat until all desired SNVTs are mirrored. RECOMMENDATION: Save the searches for use later when adding more new devices.

  Issue When attempting to add a downstream device to an SSC the error "exception of type \'Feenics.Keep.DomainModel.KeepException\' was thrown" Product Line EcoStruxure Access Expert Environment  Access Expert V3 Cause The SSC has a limitation of 32 downstream devices no matter what port(s) are being used either RS485 or virtual.  Resolution The SSC specification data sheet indicates the SSC can manage up to 64 downstream devices. However, R&D has corrected our understanding of this limitation which is only 32 downstream devices. Attempting to add a 33rd downstream device will result in the   \'Feenics.Keep.DomainModel.KeepException\' error. An additional SSC or Mercury upstream controller will be necessary to commission greater than 32  downstream devices.   From R&D: "The SSC can support a Total of 32 downstream devices no matter what port they are connected to either RS485 or Virtual. The SSC can also support 64 doors total." SSC data specification sheet  *Note: The specification sheet will be corrected in the future by the Product Owner.

Warning This article describes a feature that is not standard functionality within the Product Line.  It has been provided to allow customers the option to use this requirement.  Pay particular attention to the Prerequisites of the required programming. Issue Customer requires the functionality for Individuals  to double badge (present their credentials twice) to gain access. Product Line TAC INET Environment Access Control Cause Customer application requirement Resolution Prerequisites: LIMITATIONS: As this is not a standard access control feature within I/NET, it uses custom programming, which therefore reduces/limits the standard features within I/NET The description provided below must be set for ALL individuals with access to the door that requires double badging.  It does NOT cater to custom individual use.  It may be possible to provide additional programming to achieve this, but this is not detailed in this article. Door Automatic Time Schedules (ATS), if applied, can be overridden if the door reader is badged during the scheduled operation.  The functionality of this feature uses event-driven programming, which in its nature is single-shot programming and therefore relies on the following:  Requires reliable communication between SLI/MCI (779x) and the SCU (Door Controller).  The door reads from the SCU must be received by the SLI/MCI to activate the badge/read occurrence. Requires SLI/MCI (779x) CPU loading below 65%. LAN Load of this controller should be below 2%; anything above this can cause the operation to fail/be inconsistent.  Removes the standalone capability of the Door controller (SCU) POINTS The points required for each door that requires this functionality are Door Reader (Internal DO door point as required in I/NET)  Door Strike (External DO Point) must be programmed within the controller Door Intermediate (Internal DO Point). :: Scan Rate 1 second Door Read Count (Internal AO Point). :: Scan Rate 1 second I/NET Controller Summary Note: The address order, as shown in the screenshot above, is important for the overall operation.   That is Read Count must be at a lower address than all other points.  Next the Intermediate point.  The Strike and Reader addresses are fixed by I/NET but must be at a HIGHER address than the Read count and Intermediate points.    DOOR Intercard Interval (sec) should be set as low as possible.  This allows the card to be present within this time setting (minimum is 1 second) Door strike: Configuration of the door/reader must have this set to either. None: When a valid read is received, no action is sent to the strike Exit: Only when an Exit read to Request to exit (REX) is received by the door does it activate the strike.  Strike duration (sec): Should be set 1 second above the scan rate of the Intermediate / Read Count points above.  In this case, it is set to 2 seconds.  Note: this does not have any bearing on how long the strike remains "unlocked" Door editor Programming DOOR No additional programming is required for the door apart from the details provided in the above prerequisites.  ACCESS INITIATED CONTROL (AIC) Add an AIC that will trigger the Intermediate point on a "valid" reader entry for the nominated door. Select the Target point (DR1 Intermediate) Select either Use all individuals in the range which will trigger this action for all individuals.  Note: If selected Individuals are needed to activate this feature, then additional programming is required and not detailed in this article.    Select Reader entry to START the target point  Select which Doors are to trigger this action Access Initiated Control editor POINTS From the screenshots below, it can be seen that: Point DR1 Read Count has two extensions: Calculation (C)  Operation: The result of this calculation is displayed on the DR1 Read Count point.  The calculation adds the value of itself (P0) DR1 Read Count and point (P1) DR1 Intermediate point (where 0=OFF 1=ON), the result of which is then multiplied by the NOT (~) the value of (P2) Door Strike (where sec = 0 Unlk = 1). Result: DR1 Read Count is incremented by one on each valid read.  The counter is reset (zeroed) when the Door Strike is energized.        Event Definition (EV)   Operation: When the point DR1 Read Count crosses the value 1 (the value of 2 represents the double (2) badge), Sequence/Action #1 is triggered.  From the above Event Definition (EV), this runs Sequence/Action Num 1, which is shown below:  Operation: When triggered by the (EV) above, the Door Strike is immediately "Stop"  (Unlocked); after a 5-second delay, the Door Strike is "Start" (secured). Note: The delay of 5 seconds on line #2 determines how long the strike remains in the unlocked state.  Modifying this value will shorten or extend the unlocked state.     Point DR1 Intermediate has only one extension: Calculation (C)  SUMMARY OPERATION A valid card read is presented to the reader; this triggers AIC to turn point DR1 Intermediate to ON. This increments DR1 Read Count by 1 to the value of 1 via its Calculation (C) extension The additional card read repeats Steps 1 and 2 above;  DR1 Read Count value increments to a value of 2. Event Defintin (EV) high-value crossing (>1) triggers Event Sequence #1 Event Sequence #1 unlocks Door Strike 1 and, after a 5-second delay, relocks (secures) Door Strike 1 point. This relock (secure) of Door Strike 1 zeros the DR1 Read Count value via its Calculation (C) extension.  ATTACHMENTS - for reference showing the above details  I/NET Controller SAV file (DCU0201.zip) Backup InetDb (SQL.bak).  (InetDb_DoubleBadge.zip)  

Issue When performing a backup of all Servers and All Data on an Enterprise Server the backup fails and generates an error in Software Administrator indicating the backup is corrupt although the backup is not corrupt. Product Line EcoStruxure Building Operation Environment EcoStruxure Building Operation Workstation EcoStruxure Building Operation Enterprise Server Cause There is not enough free disk space on the Enterprise Server to save the backup file created.  The error generated in Software Administrator is a generic error. Resolution Check the Trace Log for Internal Server Error: Insufficient_Space_For_Backup If this is evident free up additional space on the Enterprise Server and re-try saving the backup.

Warning Hazard of Electric Shock: Remove all power from all devices before removing any covers or doors of the system. Disconnect power at the device and at the power source. Electrostatic Discharge Required: Always discharge static electricity from your person by touching metal prior to handling any hardware. Failure to do so may result in damage to devices. Issue There is an alarm showing after adding a downstream controller Product Line EcoStruxure Access Expert Environment Access Expert Hosted V3 Cause Instructions needed to eliminate the power failure and  tamper alarms showing on newly added downstream devices Resolution When adding downstream devices, for example, An MR50, MR52 or MR16In/Out to an SSC, EP1501 or EP1502 controller, an alarm may show in the hardware tree. To get the controller out of this state, the following steps need to be taken: a. Locate the terminal block(TB) on the panel which contains the connections for CT (Cabinet Tamper) and BA (Power Fault) Note: You may need to consult the specific controller documentation since the TB#  with these connections are different on each board. It will look similar to the following: b. Remove the connector Cut two small pieces of wire, one for each Alarm Use the 2 wires to jumper each connection (CT and BA) to create a closed circuit. This assumes these contacts are not being used for their usual purpose. No resistors are required Place the connector back on the board The downstream devices no longer show alarms for the respective addresses.

Issue On many occasions with PC upgrades and replacements, there is the need to re-download the link for the application software as it gets somewhat difficult to know where to go and find it from the Feenics website Product Line EcoStruxure Access Expert Environment Access Expert Hosted software V3 Cause Unable to find the correct link Resolution The following steps show the URL address that is needed as well as how to log on to the instance once the software is downloaded and installed: 1. Enter https://www.feenics.com/training/lesson/downloads/ on internet browser as seen  2. Once completed and installed, launch the app and log on the instance

Issue Is it needed to connect DC voltage to trigger the DI of the 301 and 421A What is the max current/voltage that a DI point can handle. Environment Xenta 301, Xenta 302, Xenta 4xx Cause The inputs on the Xenta 300 and 4xx are active inputs from the terminals X1, U1 etc. Meaning the terminal is at high voltage when open.  For a UI (act as a DI) channel, the voltage across open contact is approximately 20 V DC, and for a XI channel,  the voltage across open contact is approximately 33 V DC. To activate the digital input, engineer needs to connect the signal to M ( = 0 volt) terminal, so current flows FROM the X1 to M. So basically we expect a switch that connects M and X1 (U1). Resolution No you only need a switch that connects M0 to X1 or U1 (or other digital, universal input). Note: It is recommended to have a non-voltage dry point relay switch to protect the digital input on the controller and IO module.

Issue Setting up camera motion detected or camera image lost camera events to trigger an Output or Output Group. Product Line EcoStruxure Security Expert Environment Security Expert Video Integration Cause Through various Video Integrations, Security Expert is able to use camera events (such as camera motion detected) to popup a camera window when those events are seen. However, camera events are not associated with an Input or Door and therefore Security Expert is not able to trigger Outputs or Output Groups directly from these camera events.  Resolution Camera events are not able to be used to trigger Outputs or Output Groups in Security Expert. If this is a requirement, contact local solution category management to have this setup as a new feature. 

Issue Information needed for Integrating Access Expert BACnet objects into Continuum and EBO Product Line EcoStruxure Access Expert Environment Access Expert V3 Hosted EcoStruxure Building Operation Andover Continuum BACNet Cause BACnet objects from Access Expert may show in Andover Continuum, but will not function. An integration using EcoStruxure Building Operation is needed. Resolution BACnet objects from Access Expert may show in Continuum when a BACnet discovery is done, but they will not function.  An integration using EBO with a SmartConnector is required to use Access Expert BACnet objects. Further details on the EcoStruxure Access Expert Smartconnector are available from the Exchange Marketplace.  

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 adding a new Domain an error shows “Object does not exist – The domain “your Domain Name” does not exist, and the Domain is not created.   Using control panel Or using System/Domains folder Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Building Operation Enterprise Server Building Operation Enterprise Central Cause A Content Type rule could be incorrectly configured Resolution Navigate to /Your Server Name/System/Content Types/Rules/ If there is a “*” in the “Container Name Pattern” of any of the rules, correct this or delete the rule.     Once completed, new domains can be added.

  Issue Is it possible to use the RP-C relays to control LED Light?  The specification sheet does not specify the maximum inrush current. Product Line EcoStruxure Building Operation Environment Building Operation Room Controller (RPC) 24 V Building Operation Room Controller (RPC) 230 V Cause RP-C is not designed for switching light loads, and especially not LED loads. LED loads will result in a very high inrush current and require relays that are designed for that. Furthermore, the light application often requires relays that keep the light on in case of power failures which is not the case for RP-C. Resolution The CRS light modules and the Hotel Relay modules have that type of relays and can handle peak currents up to 800A, which is typical for LED loads. If using the CRS modules is not an option for the customer another possibility is to use a contactor connected to the RP-C.

Issue The Zenitel integration to Access Expert provides the ability to add Zenitel ICX-500 controllers and stations for interaction with intercom devices and monitoring Zenitel events. In the Access Expert Windows Client, Zenitel Exchanges are accessible from the Intercom tab within the Hardware Provisioning section. The associated list of stations will appear when selecting and opening an Exchange. Product Line EcoStruxure Access Expert Environment Access Expert Hosted software Cause While trying to integrate a Zenitel intercom system to Access Expert there are some very specific steps that need to be followed Resolution Zenitel Exchanges Exchanges are used to group together and connect a specific set of Zenitel Stations. Through the Exchanges list, the following functionalities and properties are accessible: Add an Exchange: To add an Exchange, navigate to the Exchanges list and click “Create Exchange” in the upper left-hand corner. A dialogue will appear, prompting for a Display Name and MAC Address. Additional properties and information are available for viewing on the Exchange document once it’s been added. Note: It is important that the MAC address is valid. This is how the stations connect and populate in the instance. Note: The MAC address is not editable in the Exchange document after creation. Stations List: Each Exchange document has a read-only list of Stations connected to it. The system automatically populates the list based on Stations with a connecting MAC Address. This list is automatically updated with the most current available stations.   Zenitel Stations Stations are used to make calls. Stations can be accessed via the Exchange to which it’s connected, the global search bar, or the hardware tree. The Station contains the following properties: Display Name (Editable): This is the editable display name associated with the station. Connected To (Read-Only): Display name of the connected Exchange Configured Name (Read-Only): This is the non-editable original display name of the station configured by the ICX-500. Exchange Number (Read-Only): Number of the associated Exchange. Directory Number (Read-Only): Number to dial to reach this station. Connected Reader (Editable): Reader associated with the Station. Users may specify a reader in case they need to perform actions on surrounding hardware. Cameras/Views (Editable): Multiple cameras and views may be added via the Cameras tab. Reader functionality: Within the Stations form, users may specify a connected reader. Associated functionality to the reader is accessible directly through the “Actions” dropdown list or in the context menu when right-clicking a station that has a connected reader attached.   Functionalities for the associated readers include: Pulse Connected Reader Turn Connected Reader to Online Mode Unlock Connected Reader Lock Down Connected Reader Reset Connected Reader Floor Plans Edit Floor Plan: Stations may be added to floor plans. In the left-hand list of Available Hardware, all stations within the current instance will appear and may be added using the plus button to the right. At the top of the available hardware, a station icon exists for filtering.   View Floor Plan: When viewing a floor plan with connected stations, the station's alarm status will appear in real-time. The appropriate statuses and line states of the stations are also displayed and changes occurring with the stations are updated on the floor plan accordingly.   Hardware Tree Stations can be accessed via the hardware tree and can be filtered from the top of the list via its icon. The color of the Station object is used to determine its state (Green for Online, Red for Offline). Status is also viewable via an icon that appears on the Station (Black “X” indicating that a station is busy, grey phone symbol indicating that a station is in a call). Since a standalone list of all stations is not available via the Windows client, the hardware tree is the only place all stations within the current instance can be viewed at once.   Licensing Licensing of the Zenitel integration is based on the number of stations. Instances may be licensed for any number of specified Stations and thus, the system will not allow Stations within the instance to exceed the amount in which it’s licensed. If the instance is not licensed for any stations, the “Intercom” section in the Hardware Provisioning tab will not be visible.

Issue Can a MN-Sx differential setpoint be defined using the WPT Hardware wizard? Environment MNL or MNB controller with any MN-Sx sensor Cause Project specification requires that all temperature setpoints for a site be fixed and the facility users be allowed to adjust the setpoint  with a relative positive or negative offset. Resolution In the Workplace Tech Tool use the hardware wizard to configure the setpoint with an initial value of 0.0, one decimal place and no limits. Configuring the setpoint in this manner allows the setpoint to be changed over the range of -99.0 to +999 without limit. If limits are required by specification, such as a +/- 3 degree limit, the setpoint value from the sensor would need to be passed through a Limit control object to prevent extreme setpoint offset adjustment.