Issue Unable to connect to the detected RPCs using Engage app v1.2.1 or later and RPC 3.02.01 Product Line EcoStruxure Building Operation Environment Building Operation Room Controller (RPC) (all types) v3.02.01 Building Operation Engage Application Cause EFR32 BLE chip needs to be upgraded to fw3.01.00.00012 but looking at the device report you see there is a Failure to upgrade EFR32 error. Resolution Roll the RPC back to 3.01.02 and then upgrade to 3.02.01. If not upgraded in this order, the Bluetooth Chip isn't correctly upgraded and will fail.

Issue Unable to log into Workstation because the user password is unknown. Product Line EcoStruxure Building Operation Environment Building Operation Workstation Building Operation Automation Server (AS, AS-P or AS-B) Building Operation Enterprise Server Building Operation Project Configuration Tool (PCT) Cause The password for an Automation or Enterprise server has been forgotten. Resolution If the password is unknown or forgotten to an Automation or Enterprise Server, please refer to WebHelp article 6749. The Quick-Help video on the Exchange Community can be referred to. For EBO servers with 3.1: *Ensure that you have the AS-P connected to your machine via USB cable In Device Administrator, select the AS-P you need to perform the reset to. Check the box and click the hyperlink   From the top bar select Password Reset Select OK when you get the “Password reset token created” pop-up For servers with EBO 3.2.1: *Ensure that you have the AS-P connected to your machine via USB cable In Device Administrator, select the AS-P you need to perform the reset to In WorkStation, hold shift and left-click the area near the SE Icon.   This will populate the Session ID. Click the Copy button. Send the Session ID to PSS Once PSS provides you with the unlock key In WorkStation, ensure that the Session ID is still visible, enter UN: Admin and in the Password field, paste the unlock key you received from PSS and click Log On This will pop-up the Change-Password form Fill in the “old password” field with the unlock Key Put in new password you want to use and then enter the new password in again. Click OK

Issue b3 i2 going offline and logging multiple 0x1408s in its error log. Product Line EcoStruxure Building Operation Environment b3 Controllers i2 Controllers Cause Excessive traffic on the network causes controller to run out of message buffers. Every time a controller receives a communication packet it has to allocate a block of memory (a buffer) to place the packet until it can be processed. Under normal network conditions the packets are processed at a rate that exceeds the rate at which they are coming in, in some cases typically associated with network configuration issues or malfunctioning nodes on the network, (i.e. broadcast storms) the firmware in the controller is unable to keep up with the amount of packets being received which exhausts message buffers available and renders the controller unable to communicate properly. In many cases the condition is temporary and does not result in a major problem, it is not unusual to see sporadic 0x1408s in the error log but when the condition persists for longer periods it will have an impact on the ability of the controller to communicate properly on the network. Resolution Use LAN captures to identify and remove the root cause of the excessive traffic.  Take steps to reduce the occurrence of many concurrent trend data requests being made of the b3 i2 controller such as staggering trend collection times, varying log-intervals or configuring some logs as COV (interval = 0).   Adjust the configuration to collect fewer trend records more frequently. 

Issue When attempting a login from a Security Expert client PC, it generates a "Network SSPI error" when using Windows Authentication and the machine name.   Product Line Security Expert Server Environment Security Expert 4.3.285.21 Multiple PC Security Expert Installation using Windows Authentication   Cause The Network SSPI error is generated at the Client PC Login because of how Security Expert implements RFC1034 which stipulates how machine names are used for DNS.  Resolution 1. Place a period at the end of the Security Expert Server machine while logging into the client only Security Expert PC   Example: Using "WIN-B0DOGEHESMN" as the server name will not work Using "WIN-B0DOGEHESMN." will work Notice this works because of the "." at the end   Here is a graphical example of logging in with the correct server name by adding the "." 2. The other workaround would be to use the IP address of the server instead of the fully qualified domain name (FQDN). *Note* IT departments typically prefer the use of the FQDN name    

Issue Using a Door's Card Reader to Inhibit and Enable Alarms Product Line TAC I/NET Environment I/NET Cause Access Initiated Control (AIC) can be used to trigger points based on reader entry.  This is triggered regardless of if the door is open or closed. Also, when using multiple commands, such as inhibit/enable alarms, one would need multiple readers to trigger the points.  The following process allows you to use the same reader to trigger both the enable, and inhibit alarm function. Resolution Create Points: If you have not done so yet, build a point for the Door Status.( These directions assume that 1= Open and 0 = Closed) Build an internal point called AIC Trigger. Create a calculation that keeps this point in the off state Configure AIC Create an AIC that will turn the AIC Trigger point on with a reader entry Assign this AIC to the appropriate door Create Event Sequences Create an event sequence called Enable Create an event sequence called Inhibit Modify the Inhibit event Sequence Add lines that will Inhibit each alarm For the last line, set a delay equal to the strike duration and the type as Skip if non-Zero Set the point as the Door Status and the Sequence as the Enable Sequence # Click OK Modify the Enable sequence Add lines that will Enable each alarm Click OK Click close Select Edit>Controller>Point Extensions>Event Definition Double Click on the AIC Trigger Point Set the Event type to Specified State Select "Sequence" and set the sequence number as the Inhibit sequence Select the State/Value as On Click OK Results Entering the door with a valid card read will cause all alarms to go to an inhibit state After exiting the door and allowing it to close, one can scan a card to enable the alarms. This will take effect after a delay equal to the strike duration. This process is based on the door position switch being open or closed as the strike duration expires. So that arming the system will only occur if the door is closed. There is a potential flaw if someone is able to scan a card, enter the room, and close the door before the strike duration expires.  If this happens the system will re-arm itself as the strike duration expires. For this reason, it is important to have as short a strike duration as possible.

Issue After 2000 backups an attempt to perform a backup to flash results in the error 'Flash backup for this controller has been disabled.' Product Line Andover Continuum Environment Continuum b3920 controller Continuum i2920 controller Cause Flash memory has a limited write count; Controllers implement a flash circuit breaker that trips after 2000 backup operations in order to protect the flash device from damage. Resolution (Applies to all b3 and i2 controllers) EcoStruxure Building Operation In EBO, a command has been added that will re-enable backup to flash after the circuit breaker has been tripped (2000 backups) From Workstation, in the object tree, right-click the i2/b3 device. From the context menu select, DEVICE->ENABLE BACKUP TO FLASH Andover Continuum From CyberStation command line set the ACCStatusBackup system variable of the device to ACCBackupEnable. NOTE: The flash circuit breaker CANNOT be reset from Script/Plain English.  This is by design as it was deemed too risky to allow resetting it programmatically.  A poorly written program could very quickly cause damage to the flash device.

Issue On a 7718 controller, why do none of the discrete outputs provide 24vdc when energized? Product Line TAC INET Environment I/NET site Cause Using the 7718 controller, why do none of the discrete outputs provide 24vdc when energized Resolution Verify that fuse F9 is not open. (TCON106)

Issue What is the unit load of the SpaceLogic SLP Room Units that will help me to calculate how many SLP Room Units that can be added on ComA and ComB of a SmartX Server. Product Line EcoStruxure Building Operation, Field Devices Environment SpaceLogic SLP Room Unit SmartX Server Cause Documentation does not state the Unit Load (UL) of the SpaceLogic SLP Room Unit. Resolution The Generic application note AN01 can be applied with answers to the transceiver interface attributes below. The SpaceLogic SLP Room Unit range use the SN65HVD1781DR transceivers which are a failsafe transceiver (not requiring bias) and reduced 1/10 UL. In addition there are no local bias resistors and therefore the 1/10 UL of the transceiver would be the total UL presented to the bus by the SpaceLogic SLP Room Unit. Transceiver Xcvr Unit Load Xcvr Failsafe Adaptor Circuit Bias Circuit Bias Load Total Unit Load Isolated 485 Bus SN65HVD1781DR 0.1 Yes None None 0.1 No Based on the above the total number of devices can be calculated as 32/0.1 = 320. The BACnet MSTP standard specifies that the address range for BACnet master devices is 0-127 and therefore a SmartX Server is limited to 127 devices per com port (254 total per Server) so this should effectively be the limiting factor. Since the SpaceLogic SLP Room Unit does not have an isolated RS-485 interface it conforms to Generic RS-485 Network Device Configuration 1 in EBO Webhelp.  A network consisting of only SpaceLogic SLP Room Units should only require a 120 ohm termination resistor at each end of the bus and not require any bias resistors. Also check out the SmartStruxure-RS485-Controller Unit Load Quick-Help video on the Exchange.

Issue When opening a BACnet AnalogInput  from (the Blue) BACnet device side, the value of the object displays as 3 decimal digits by default. The format can be changed in the format field as desired, however when clicking the "Apply" button, an error prompt box pops up with the message "An attempt has been made to write a property defined as inaccessible through the BACnet  protocol write services". if the "Apply" buttonis clicked again, the error disappears and the format is been changed successfully. Product Line Andover Continuum Environment Continuum BACnet BCX1 B3s Cyberstation V2.02 and earlier. Cause Format is not a standard BACnet property, it is a Continuum attribute and when the format is changed Cyberstation sends a command to change the "present value" of the point in the controller. The present value of AnalogInput cannot be written so the error occurs. When clicking "apply" or "OK" for the second time Cyberstation only writes the attribute of the point in the database rather than the controller. Therefore we can get a successful change of format for AnalogInput by clicking "Apply" twice. For AnalogValue, the "present value" of  AnalogValue can be written in BACnet, so there is no error when changing the format of an AnalogValue. Resolution Ignore the error when making the change, click the "Apply" button twice after updating the "Format". Or upgrade to V2.03 where this issue has been resolved.

Issue Need to activate an Output when access is denied to a User at a Door. Product Line Security Expert Environment Security Expert Cause In the Door object, there is a facility for triggering Outputs on Pre Alarm, Door Left Open, and Door Forced Open but nothing for when a User is denied access. Resolution There were new Door commands added to SP-C firmware 2.08.1018 and newer to add this functionality. AccessDeniedTime = # has been added to the Door commands which will specify the duration in seconds that an output or output group will be activated for when access to the door has been denied. This must also be paired with one of the following 2 commands in order for the functionality to occur. AccessDeniedOutput = # has been added to the Door commands which will specify the output that will be activated when access to the door has been denied. The # will be the database ID of the output/output group. AccessDeniedOutputGroup = # has been added to the Door commands which will specify the output group that will be activated when access to the door has been denied. The # will be the database ID of the output group. As an example, if you wanted the Output with an Id = 3 to turn on for 5 seconds when access is denied at the Door, the following lines would need to be added to the Door object in the Commands section. AccessDeniedTime = 5 AccessDeniedOutput = 3 Door Command - Access Denied Output

Issue Setting up, using, and troubleshooting Windows Active Directory with Building Operation Workstation and WebStation. Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation WebStation Windows Active Directory Windows Server Cause When integrating EcoStruxure with Windows Active Directory, NO user accounts need to be created in EcoStruxure, all that needs to be done is map the EcoStruxure User Account Group(s) with the Windows group(s) that will be used.  You can map Windows Active Directory groups to Building Operation user account groups if Building Operation runs on a network that uses this directory to manage users and user account groups. A Building Operation user account group that includes a Windows account group can also be a member of another Building Operation user account group. Mapping Windows Active Directory account groups to Building Operation user account groups has advantages both for administrators and operators. Administrators can manage the user accounts in the Windows Active Directory, rather than managing the accounts in two places. Any changes are instantly implemented to the mapped Building Operation user account group. Operations only have to remember the Windows login. Once logged in to a Windows user account that is mapped to a Building Operation account, the user is authenticated to access WorkStation without having to log in a second time. Note: The Building Operation domain used to map the Windows Active Directory user account groups must be a member of the Windows domain where the Active Directory is located. Windows Active Directory account groups can only be mapped on servers that are based upon Microsoft Windows operating system. Automation Servers, cannot map Windows Active Directory groups. For example, the Windows Active Directory user account groups Main Admin and Main User are mapped to the Building Operation user account groups Administrators and External Users. The External Users user account group is a member of the Operator user account group. The Administrators account group, which is a member of the External Users, inherits access to the Operation workspace. The user will then log into Windows on the PC where the WorkStation is installed. When logging into EcoStruxure Workstation the authentication is automatically done from the Windows user account. Resolution NOTE: Active Directory association cannot be achieved using the inbuilt Local Domain Create a new EBO Domain and associate it with your active windows Domain. Create an EBO Domain Group within that new Domain and associate it with the Windows Domain Group in which the Windows Active Directory user(s) reside. Log in using Windows Username, Password, and Domain rather than EBO credentials.  When logged on the Enterprise Server PC as a Domain User it is also possible to select the "Log on as" box. See WebHelp: How to Create and Configure a Domain Conceptual Information on Windows Active Directory User Groups How to Create User Account Groups Troubleshooting Windows Active Directory with Workstation Log in Error: Wrong user name or password If the EcoStruxure Building Operation Domain has the same name as the Windows Active Directory domain name, it will expect the user account to exist locally in the Building Operation domain. Log in Error: "User account not associated with a group. Contact your Administrator." Verify that the Windows user is a part of the Windows group configured in the Building Operation Group settings. In order to identify every group that the current windows user belongs to, run the command: whoami /groups Once the Windows user has been confirmed as a member of the configured Windows group, try changing the Log On as credentials for the Enterprise Server service. The default user that is used when installed is the "Local System account". The Windows account used to run the Enterprise Server service needs "read access" to all places (e.g. OUs) in the Active Directory where user groups potentially involved in an EBO Windows log on can be found. Note: By default, all domain users in an Active Directory have read access to Active Directory "Users and Computers" objects so it is the sites which have restricted this in some way which may face issues. You do not need to use “domain admin” type accounts for this as they are granted way too much authority in general. An account has read access to sufficient parts of the AD while having only normal local user privileges on the machine where the Enterprise Server is running will suffice. From the Windows Start menu, launch Computer Management. In Computer Management go to Services and Application > Services. Find Building Operation X.X Enterprise Server, select it and Stop the service. Right-click on Building Operation X.X Enterprise Server and go to Properties. Select the Log On tab. Under Log On as select "This account". Enter a Windows user login that has sufficient Windows rights for the Enterprise Server to log on as. Click OK and then start the service again. Log in to Workstation again using Active Directory. Troubleshooting Windows Active Directory with WebStation From version 1.5.0 and up, using Windows Domain accounts is supported in WebStation. However, the following must be done in order to log in. You need to use HTTPS. Use your Windows username and password.  The Windows domain must be defined (It needs to be the actual Windows domain, not what you named the domain in SmartStruxure). Download a TVDA for Single Sign-On Instructions

Issue DPU Restore, when and what information is downloaded to the Door Controllers Product Line TAC INET Environment TAC I/Net Seven site with DPU or SCU 7910, 7920 1284, 1280 door controllers, download Cause A variety of errors with door access can be attributed to download individual information to the door controller(s). Resolution When changes are made to any one of the following, a download is triggered to each of the DPU/SCU controllers. Name Group Issue Level Card Number If using DPU Restore, remember that during the DPU\SCU restore, these are the items that are being downloaded. Cold Start signal - followed by point data from the SLI Tamper Parameters (SCU Only) Translation parameters Tenant information Floor Mapping\Personnel data for each Elevator\Door Secondary Time Schedules End of the Cold Start process After the Cold Start ends, then the Big Card Numbers (HEX) are restored from the SLI to the DPU\SCU controllers

Issue How to get answers for project specification responses or how to get a product enhancement implemented. Product Line Security Expert, EcoStruxure Building Operation Environment Security Expert EcoStruxure Building Operation Cause Unsure who to go to for help with specification replies or how to get a potential product enhancement added to the offer. Resolution Create an idea on The Exchange Community for your specific Offer. The more Likes an idea floated on the Community receives, the more attention it is given by offer management for that associated product line. Even if you do not yourself have an Enhancement Request, help raise the profile of others by Liking theirs Contact your local solution category manager for the Offer as they will be able to point you in the right direction for answers to specification questions and can help escalate enhancement requests to Product Management. Americas: Americas.EcoStruxureBuilding@schneider-electric.com EMEA: EMEA.EcoStruxureBuilding@schneider-electric.com Asia Pacific & India: AsiaPac.EcoStruxureBuilding@schneider-electric.com When providing your feature request make sure to include as much detail as possible about the feature as well as any specifics that might help justify the need for the new feature.

Issue After downloading application and parameters to a TAC Xenta from TAC Vista, get an error message "OUT OF MEMORY (RAM)" When trying to edit a Xenta trend in TAC Vista Workstation get an error message "Could not save the object: OUT OF MEMORY (RAM)" Product Line TAC Vista Environment TAC Vista Workstation TAC Menta Cause The error message means that a trend log definition exceeds the capacity on the TAC Xenta unit. Resolution In Menta: Select the "Option" menu, and click on "Trend Logs". In the Select Trend Log dialog box, double click on the trend log that need to be edited. In the "Trend Log Definition" window, under "Signal" section: Increase the "Log Interval" time Decrease the "Log Space" time In TAC Vista Workstation: Right click on the Xenta log that needs to be edited. Select "Properties". Under the "Signal" Tab: Increase the "Log interval" time. Decrease the "Log space" time.

Issue Are 64-bit operating systems supported on the Andover Continuum product line? Product Line Andover Continuum Environment CyberStation webClient Cause Compatibility requirements for Andover Continuum with 64-bit operating systems Resolution Release 1.93 and earlier: For all machines with CyberStation or webClient software installed, only operating systems running in 32-bit environments are supported. 64-bit environments are not supported.  However, for the Database Server on a LAN system where no Cyberstation or webClient software is installed, a 64-bit version of Windows Server 2008 (SP2) or Windows Server 2008 R2 may be used on systems running V1.92 and above. These will also require Microsoft SQL 2008 running in 64-bit mode. Release 1.94 and later: Release 1.94 supports 64-bit Operating Systems, however, Microsoft recommends the 32-bit version of Office 2010 because it prevents potential compatibility issues with other 32-bit applications, specifically third-party add-ins that are available only for 32-bit operating systems. Please refer to the release notes for compatibility notes in specific versions.

Issue Can a Remote Client run I/NET Reports (SevenReports) from the I/NET Seven Server's SQL database? Product Line TAC INET Environment I/NET Seven SevenReports Cause In a Remote Client configuration, the local SQL database is not used and is typically blank.  To enable the local SevenReports engine to connect to the I/NET Server the ODBC data source must be configured to successfully connect to this server workstation.  Resolution To download more detail instructions please Click Here Remote Client: The following procedures describe how to configure the local I/NET Seven ODBC data source to communicate with the SQL server on another I/NET Seven workstation. Open the ODBC Data Source Administrator editor. (Control Panel / Administrative Tools) In the ODBC Data Source Administrator editor, click the System DNS tab, highlight the Seven ODBC data source, and click Configure.... In the DSN Configuration editor, use the Server field to specify the name of the I/NET Seven workstation and SQL Server instance that will be used as the server for this workstation. Click Next and enter the third-party Login ID and Password appropriate for the selected server. If the server is using the default settings for these parameters, the Login ID will be INetThirdParty and the Password will be passinetdb3p_SE. Click Next two more times and then click Finish. In the resulting window, review the summary of settings. If necessary, you can use the Back button to return to previous screens and make changes to the configuration. Click the Test Data Source... button to test the connection. Click OK to close the Test Results window. Click OK to close the DSN Configuration editor. Click OK to close the ODBC Data Source Administrator editor. Third-Party Applications Use the following procedures to create a new ODBC data source on a PC that is not running I/NET Seven. The purpose of this task is to allow local third-party applications to communicate with I/NET Seven running on another PC. Open the ODBC Data Source Administrator editor. (Control Panel / Administrative Tools) In the ODBC Data Source Administrator editor, click the System DNS tab and click Add.... In the resulting window, scroll through the list and highlight the driver appropriate for the version of SQL Server installed on your PC:  - For MSDE/SQL Server 2000, select SQL Server. - For SQL Server 2005, select SQL Native Client. - For SQL Server 2008, select SQL Native Client 10. Click the Finish button. In the DSN Configuration editor, make the following settings:  - Define the data source Name as “Seven ODBC”.  - Define the Description as “ODBC Connection for I/NET Seven”.  - Use the Server field to specify the name of the I/NET Seven workstation that will be used as the SQL server for applications on this PC. Click Next and make the following settings:  - Select the With SQL Server authentication using a login ID and password entered by the user option. - Near the bottom of the editor, enter the third-party Login ID and Password appropriate for the selected server. If the server is using the default settings for these parameters, the Login ID will be INetThirdParty and the Password will be PassInetDb3p_SE. Click Next two more times and then click Finish. In the resulting window, review the summary of settings. If necessary, you can use the Back button to return to previous screens and make changes to the configuration. Click the Test Data Source... button to test the connection. Click OK to close the Test Results window. Click OK to close the DSN Configuration editor. Verify that the new ODBC data source has been added to the list of System Data Sources. Click OK to close the ODBC Data Source Administrator editor. More detailed information is also available on Extranet in TCON301 Chapter 2 - ODBC Driver Interface section.

Issue After connecting a new Optimum Living Space Sensor, the LCD is blank other than being backlit. Product Line EcoStruxure Building Operation Environment Building Operation SmartX Living Space Sensor Optimum Building Operation Multi-purpose VAV fw 2.00.03.02000 or older Cause Only Living Space Sensor bases running application version 1.0 or later can read the Optimum cover models Resolution Upgrade EBO to v3.1.x or later and SmartX controller to fw v3.01.x or later. At the time of this being published, firmware revisions prior to 3.01.x are not compatible with the Optimum Living Space Sensors (SXWSCDPSELXB, SXWSCDPSELXW, SXWSCDXSELXB, SXWSCDXSELXW).

Issue When multiple Vista servers are networked up each Vista server displays all of the alarms. Product Line TAC Vista Environment Vista 5 and greater Cause Each Vista server is set up to look and synchronize to the Master Server alarms by default. Resolution In each node object, there is an option to send and receive alarms. Here are the steps to stop a slave server from receiving alarms from the master. From the Master Server locate the slave node that the alarms are to be local only. The slaves' node name will look like this format.   $lan."servername" Right-click on that slave node and select properties. Uncheck the receive alarm option and select OK. This stops that slave receiving alarms form that server. The send alarm option can be used in a similar way to stop alarms being sent to the master if required.

Issue Which printers, signature pads, and capture devices are supported with the badging editor? Product Line Andover Continuum Environment Epi-Suite Epi-Builder Cause Determine which ImageWare systems (Epi-Suite or Epi-Builder) to use with the Continuum system. Resolution Continuum OEM's third-party badging software from Image Ware Systems are Epi-Suite and Epi-Builder. If your using Continuum version 1.8 and newer versions, Continuum uses the Epi-Builder version. For versions of Continuum 1.74 and prior, they use Epi-Suite as the badging editor. The hardware compatibility list for the Image Ware products can be found on their website. www.iwsinc.com Once on their website select Support/Customer Service/ either IWS Epi-Builder or IWS Epi-Suite. The page that is displayed after these selections you'll notice a link on the left-hand side of the page for Compatible Hardware. The lists for printers, capture devices, and signature pad readers can be displayed when clicking on the links for each. The peripherals can be found at: https://www.iwsinc.com/support/epi-suite-builder-hardware-compatibility/

Issue How many messages are buffered on a Door Controller 7910A and 7920 DPU? Product Line TAC INET Environment I/NET Seven Door Controllers: DPU 7910A, DPU 7920, and SCU 1284 Cause Even though every device in the system contains a message queue, only a few of the devices will successfully buffer the queued messages for later distribution. All controllers and Taps distribute messages out of their RS485 port even with the absence of any LAN communication. This is due to the fact that there is no requirement for an acknowledgment to be received at the generating device. The RS485 LAN is for both solicited and unsolicited message traffic. The only devices that perform extended buffering are the ones that directly communicate to polling devices such as the 7801 Taps, 7803 Taps, 7804 Taps, and all DPUs/SCUs. The MRs, ASCs, and UCs do not generate messages; messages relating to these devices are generated by the relevant MRI, MCI, etc. Resolution Refer to the Database Caching in the Door Controller Chapter 9-11 in TCON 300-05/17 for full details. For the 7910A and 7920 see the following details:  Controller software before v.2.20 = 100 messages Controller software for 2.20 and later = based on the number of resident individuals (see table below).