Building Automation Knowledge Base

Issue Issues resizing SBO graphic editor frames with Windows 10 Lenovo P51 or T470 laptop with a Schneider Electric image. The following picture shows that the Graphic Editor did not re-filled the screen after resizing either the component/snippet area or the Object/property area, a border can be seen to the right and below the editor’s frame. Product Line EcoStruxure Building Operation Environment Lenovo P51 or T470 Schneider Electric imaged laptop. Cause Scale and layout: Microsoft .NET Framework version: Resolution 1. Scale and layout: Right mouse click on the desktop and select “Display settings” Set Scale and layout to 100% Re-boot computer   2. Microsoft .NET Framework 4.7.2: Download and install Microsoft .NET Framework 4.7.2 (Microsoft .NET Framework 4.7.2. can be downloaded from the Microsoft support site) Re-boot computer If these suggestions do not provide a solution or if you would like to provide some other feedback, please contact your local product support entity

Issue When the Ethernet is removed from an AX-SSC controller, all of the devices underneath that controller inexplicably lose their connection to the controller. Product Line EcoStruxure Access Expert Environment AX-SSC Cause The firmware of the SSC is outdated. Resolution The firmware of the SSC needs to be upgraded to version 24.01.241 or newer. This can be accomplished with the following procedure:   1. From Access Expert (the firmware of the SSC can only be updated within Access Expert, not from the Device Administrator), select the "Hardware Provisioning" tab. 2. Click "Controllers", and then select the correct SSC controller. 3. Under "General Info" verify the "Reported Version Number". If less than 24.01.241, the firmware needs to be updated. Click "Update Firmware".

Issue Unable to locate where to configure the SMTP Server in an Acess Expert V3 Instance. Product Line EcoStruxure Access Expert Environment V3 Premise Cause The earlier versions of the on-premise server/client did not have SMTP functioning properly. As a result, the tab to Configure the SMTP server settings was left out of the software. Resolution Newer versions of the software have SMTP functionality working properly. After upgrading the Server and Client software to the newest versions available, the SMTP Configuratiuon tab will be available as shown below.  Note: For Instructions on how to upgrade the Premise Server and Client software, please see Upgrade Premise Software to Latest Version.

Issue The Drayton Theta YBL1A Valve Body / Actuator assembly is to be replaced. Product Line Field Devices Environment Replacement Drayton Actuator Valve YBL1A Cause The Drayton Theta YBL1A Valve Body / Actuator assembly is obsolete. Resolution OVERVIEW The Drayton Theta YBL1A Valve Body / Actuator assembly is obsolete, and there is no purpose built replacement. The Valve Body was available in 1.1/4", 1.1/2" and 2" B.S.P. sizes and was normally installed as a mixing valve in variable temperature, constant volume, compensated heating circuits. No Valve Body / Actuator assemblies are currently available in these sizes. Details of the YB Valve Body may be viewed here.   VALVE BODY REPLACEMENT To replace the YBL1A Valve Body the following is required:- S-E SatchwellMB Valve Body of appropriate size - MB1552 (1.1/4"), MB1602 (1.1/2"), MB1652 (2") Details of the MB Valve Body may be viewed here.   ACTUATOR REPLACEMENT (6-WIRE INSTALLATION) The YBL1A Actuator normally comprised a 6-wire electrical connection enabling it to be operated by a Theta Potentiometric Controller as follows :-  Terminal M1 – Open signal Terminal M2 – Close signal Terminal M3 – Common  Terminal M4 – 135 ohm Feedback Potentiometer – winding Terminal M5 – 135 ohm Feedback Potentiometer – wiper Terminal M6 – 135 ohm Feedback Potentiometer – winding Where 6 wires are connected to the YBL1A Actuator then the Actuator may be replaced by one or other of the following S-E Actuators :- MD10B-24 MD20B-24 (if MD10B-24 not available) Details of the MD10B-24 Actuator may be viewed here Details of the MD20B-24 Actuator may be viewed here. N.B. The YBL1A Actuator also included an additional 3-wire electrical connection associated with an integral S.P.C.O. Auxiliary Switch wired as follows :-  Terminal S1 – Normally Closed Contact Terminal S2 – Common Terminal S3 – Normally Open Contact Where external wiring is connected to the YBL1A Actuator Auxiliary Switch then an Auxiliary Switch Kit containing a S.P.C.O. Auxiliary Switch should be installed on the MD Actuator. Auxiliary Switch Kit MD-S1 (914-1060-000) Details of the MD-S1 Auxiliary Switch Kit may be viewed here. The MD-S1 Auxiliary Switch Kit should be wired as follows :-. Terminal S1 – Common Terminal S2 – Normally Closed Contact Terminal S3 – Normally Open Contact   LINKAGE KIT A Linkage Kit will also be required in order to enable the MD Actuator to be mounted on the MB Valve Body. Linkage Kit LMD/AR-MB (914-1071-000) Details of the LMD/AR-MB Linkage Kit may be viewed here   IMPORTANT NOTE In such 6-wire installations not only will the YBL1A Valve / Actuator assembly need to be replaced but the associated Theta Potentiometric Controller and its Sensors will also need to be replaced.   CONTROLLER REPLACEMENT The Theta Potentiometric Controller may be replaced by the S-E Satchwell CSC5252 or the CSC5352 Compensator Controller. Details of the CSC Controllers may be viewed here.   SENSOR REPLACEMENT Theta 3-wire Temperature Sensors may be replaced by S-E Satchwell 2-wire Temperature Sensors compatible with the S-E Satchwell CSC 5252 or CSC5352 Compensator Controllers selected from the following as appropriate. Outside Air Temperature Sensor (STO 600) Contact Temperature Sensor (STC 600), or alternatively :- Immersion Temperature Sensor (STP 660) + Sensor Pocket Adaptor (DWA 0001) Room Temperature Sensor (STR 600) – OPTIONAL ONLY Details of the STO 600 Outside Air Temperature Sensor may be viewed here. Details of the STC 600 Contact Temperature Sensor may be viewed here. Details of the STP 660 Water Temperature Sensor may be viewed here. Details of the DWA 0001 Sensor Pocket Adaptor may be viewed here. Details of the STR 600 Room Temperature Sensor may be viewed here.   N.B. ACTUATOR REPLACEMENT (3-WIRE INSTALLATION) Should only 3 wires be connected to a YBL1A Actuator then the Actuator may be replaced by one or other of the following S-E Actuators :- MD10B-24 MD20B-24 (if MD10B-24 not available) Details of the MD10B-24 Actuator may be viewed here. Details of the MD20B-24 Actuator may be viewed here. N.B. The YBL1A Actuator also included an additional 3-wire electrical connection associated with an integral S.P.C.O. Auxiliary Switch wired as follows :-  Terminal S1 – Normally Closed Contact Terminal S2 – Common Terminal S3 – Normally Open Contact Where external wiring is connected to the YBL1A Actuator Auxiliary Switch then an Auxiliary Switch Kit containing a S.P.C.O. Auxiliary Switch should be installed on the MD Actuator. Auxiliary Switch Kit MD-S1 (914-1060-000) Details of the MD-S1 Auxiliary Switch Kit may be viewed here. The MD-S1 Auxiliary Switch Kit should be wired as follows :-. Terminal S1 – Common Terminal S2 – Normally Closed Contact Terminal S3 – Normally Open Contact   LINKAGE KIT A Linkage Kit will also be required in order to enable the MD Actuator to be mounted on the MB Valve Body. Linkage Kit LMD/AR-MB (914-1071-000) Details of the LMD/AR-MB Linkage Kit may be viewed here In such 3-wire installations the YBL1A Valve / Actuator assembly only will need to be replaced, while any associated Controller and Sensors may be retained.

Issue Having difficulties integrating an SED-T stat with the MPM (Stat not being "learned" by the MPM) Product Line EcoStruxure Building Expert Environment SmartStruxure Lite Multi-Purpose Manager SED-T00 SED-TS0 SED-TH0 SED-THS Cause Installation manual does not provide enough information Resolution Commissioning tips and recommendations   Dip Switches: SED-T series stats come directly from production with all dip switches set to 0. The dip switches settings must be changed otherwise the device will not send any telegrams. Tip: When pairing an EnOcean Temperature Sensor with the MPM, always set at least one pin of the DIP switch to the ON position before learning it in. Otherwise the MPM will not display any readings regardless of dip switch configuration even if the Enocean ID had been populated in the EODC object. The workaround at this point would be to click on the learn button again, the device will be learned successfully when the “RSSI” value and a “Last Communication” time stamp are displayed.   Example on how to use the dip switches: If the dip switches are set to 1= OFF, 2 = ON, 3 = ON, 4 = OFF, the stat would wake up every 10 seconds and take a look at the values. if they changed, the stat will send a new telegram with the new value. if the value did not change however, the stat will go back to sleep until the next 10 seconds elapse (first iteration). If the value did still did not change before the 7th iteration, then the stat will randomly send a telegram with the unchanged value at any time between the 7th and the 14th iteration. that is a minimum of 10*7 = 70 seconds and maximum of 10*14 = 140 seconds.   Solar cell: When removing the unit from the box for the first time, its energy banks (super capacitor) need to be charged using one of the methods below in order to be able to learn the device. A minimum of 2.1VDC is required before the stat can wake up and send a telegram and Ideally, the Super cap voltage should be between 4 to 5Volts. Method 1: Power the sensor with 24VAC for 1 hour (3volts/hour) Method 2: expose the solar cell to light for x amount of time depending on the light source: 1- Room with LED panels: 24hr minimum charging time (0.1Volts/hour) 2- Lit room with day light: 3-4 hours minimum charging time (0.7Volts/hour) 3- Direct sunlight: 1/2 hour minimum charging time (3.5Volts/hour)   Battery: The 20mm coin cell battery does not charge the super capacitor, however it slows down the depletion of super capacitor once its charge drops below 2.1Volts.

Issue When you're having issues with Continuum you need to check if the Windows account you are logging on with is part of the Local Administrators Group. Product Line Andover Continuum Environment Windows XP Windows Vista Windows 7 Windows 2008 Server Continuum 1.9X Cause Permission issues running or installing Continuum 1.9X Resolution Download the attached TestUserAdmin.zip file unzip the TestUserAdmin.exe file to your Desktop Open the Command window (DOS prompt) and run the TestUserAdmin.exe  The program will indicate if the logged on Windows user is a member of the Local Administrators Group or not.  

Issue No license is available for Vista Webstation Webstation installation issues ASP.NET Authority issue Product Line TAC Vista Environment Vista Windows 2003 Windows 7 Windows 2008 R2 Cause Sometimes it is not enough to let ASP.NET be run by NetworkServices. The user LocalSystem needs to be used instead. Resolution Windows 2003:  Go to Start and administrative tools. Click Internet Information Services (IIS) Manager. Expand application Pools Right click on  "SE ASP.NET v4.0 Classic" and choose Properties. Under "Identity" choose user "LocalSystem" from the Predefined drop list. Click OK and restart webstation. Windows 7: Right click on my Computer and choose "Manage" Go to Services and Application Click on Internet Information Services Click on application pools Right click on  "SE ASP.NET v4.0 Classic" and choose Advanced settings Under "Identity" choose user "LocalSystem" Click ok Restart webstation Windows 2008R2: Go to Start and administrative tools. Click Internet Information Services (IIS) Manager. Click Application Pools under the serve Right click on SE ASP.net v4.0 Classic and choose Advanced setting. See attachment IIS manager 1 Click the button beside Identity under the process model. See attachment IIS manager 2 Change the built-in account from networkservice to LocalSystem. Click OK and restart the webserver in Internet Information Services (IIS) Manager. If the problem persists, please see Problems installing Vista Webstation 5.1.5 or newer for additional helpful information.

Issue Can't communicate with more than 1 device on LG Gateway at the same time. Updated with solution on 12/15/2017 Product Line EcoStruxure Building Operation Environment LG Gateway Model:PQNFB17C1 Firmware version: 1.11.4 Cause The gateway can only provide one source address when there are multiple device IDs. The wireshark capture confirmed that no unique source ID provided by the gateway with different device IDs. Resolution Update the firmware version to 5.08.1h Configure the "BACnet Type Setting" to "B Type".

Issue Installed the tool under Windows 10 but was unable to assign a port in the tool's connection settings because there are no ports showing in Windows Device Manager. Product Line Andover Continuum Environment RoamIO2 BACnet Service Tool Cause Windows legacy hardware configuration. Windows 10 by default does not include the legacy ports. Resolution Legacy ports must be added to the Device Manager. 1. Open Device Manager from Windows Control Panel. 2. Select 'Action' then 'Add legacy hardware' or Go to "Start" and type hdwwiz.exe then press Enter 3. Next 4. Next 5. Next 6. Select 'Ports (COM & LTP) then Next 7. Select Microsoft/Standard Serial over Bluetooth link then NEXT 8. Complete the legacy hardware installation, Device Manager will then show the ports. 9. In the Service Tool select the appropriate port.   When the connection has been established from Windows PC to RoamIO2 device, the BlueTooth settings in Windows will indicate 'Connected'  NOTE that if it only indicates paired there will be no data transfer even though the blue LED is illuminated on the RoamIO2 device. (see screenshot below)

Issue The local time inside a Xenta programmable unit is dependent upon server time, time zone, and daylight savings time settings.  Incorrect DST settings result in incorrect times in the controller which causes problems from incorrect start times on HVAC equipment, to incorrect alarm time stamps in alarm queues. Product Line TAC Vista Environment Xenta Programmables version prior to 3.74 Xenta 280, 281, 282, 283, 300, 301, 302, 401, 401:B Cause In 2007, most of the United States and Canada changed when DST is observed to the second Sunday in March to the first Sunday in November.  Because it had never changed prior to that, programmable controllers retained the old settings (first Sunday in April to last Sunday in October). Resolution The issue was resolved with the release of firmware MOT version 3.74.  Upgrading your controllers to 3.74 is a viable solution, however not always cost effective.  There are two ways to work around the issue. Note: For information on how to download firmware to Xenta programmable devices using the Download Wizard please see Download an .MOT file into a Xenta Programmable controller. Configure TAC Xenta Central DST Settings Refer to the TAC Vista Technical Manual Chapter 19.6 In the folders pane, right-click the folder where you want to place the time event object. Point to New, point to Object, and then click Time Event – Object. Type the name. Open the time event object. On the General tab, type a description. On the Time Event Settings tab, set a suitable repeat interval, for example, first Monday in each week. Click OK. In the folders pane, right-click the folder where you want to place the Central Daylight Settings – Xenta object. Point to New, point to Object, and then click Central Daylight Settings – Xenta. Type the name. Open the Central Daylight Settings – Xenta object. Two options are available. You can use Windows start and end times for the daylight saving time or specify your own start and end times. If you want to specify your own start and end times: Clear the Use Windows settings check box. In the Daylight saving starts box, set the start time for the daylight saving time. In the Daylight saving ends box, set the end time for the daylight saving time. In the Update schedule box, browse to the time event object that triggers the push to the TAC Xenta devices. Click Select. Click OK. Note: You must select Manual DST Mode and Central DST for each controller in the system for a global change to take effect. Manually set DST Settings for each controller The DST Xenta object is not available in all versions of Vista.  If that is not an option, DST settings on each controller can be manually set for the start day and stop day.  Unfortunately, time settings do not allow for designations of "first Sunday" or "last Sunday," only calendar dates.  So each controller will have to be edited each year to maintain correct time settings. In order to facilitate this, this utility:  ODXentaTimezoneChanger was created.  It must be used each year to update the settings, but it will allow you to change all time settings on all controllers in a Vista database simultaneously, greatly reducing the time it takes to correct a system. NOTE: If the Lonworks network has not been properly commissioned & downloaded the tree will not properly communicate with the Vista Server. Check your network tree for asterisks to see if any downloads are 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 Services for assistance. Issue Is it possible to have a link on a GxPage to run an executable file to launch an external application outside of the web browser? Product Line TAC IA Series Environment I/A Series R2 graphics Firefox web browser Cause To launch an external application via a link on graphics page in a web browser. Resolution It is not possible to launch an external application from an I/A Series R2 GxPage. Two suggested workarounds are as follows. Create a hyperlink on a GxPage that links to a standard HTML web page. There would be a link to run a script on the standard HTML page to launch the external application. If the site graphics has a HTML tree created, create a new link in the tree which will run a script to launch an external application. * Take note that the HTML web page with the script link has to reside on the same computer as the external application. As an example the following script and procedure which will launch an external application in a Firefox web browser. In this case, the script will launch Windows notepad.exe. This method has been provided as a workaround but you should use and troubleshoot any information given below at your own discretion. Example of a script to launch an Notepad in Firefox: Right Click on this link and select "Save target as" to download this script as a text file We also need to configure Firefox to allow Java script to run. Run Firefox and type in 'about:Config' at the address field. Set the 'signed.applets.codebase_principle_support' to true. Be careful not to make any other changes. NOTE: This script and browser configuration may or may not work in other web browsers. Further changes may be required for this functionality in any other web browser other than Firefox.

Issue User is not being logged out of the Keypad after the log out time. Product Line EcoStruxure Security Expert Environment Security Expert SX-KLCS (Security Expert Keypad) Cause The User had an access level with a Menu Group that had the "Installer Menu Group" option enabled. This option disables the logout time for the keypad so the user is not logged out while the system is being configured. Resolution 1. Disable the "Installer Menu Group" option under the associated Groups | Menu Groups | Option menu; 2. Which will allow the keypad to log the user out after the (10s) "Time User Is Logged In (Seconds)" [2] value set under Expanders | Keypads | Configuration.

Issue A method to remove access from a large number of Personnel by changing the Expiration Date using a Template. Product Line Andover Continuum Environment Continuum Access Control Cause Need to know how to disable large numbers of Personnel at one time using the Personnel Expiration Date. Resolution The Personnel Expiration Date is distributed down to the Controllers and used to allow or deny access at the Door. If a future date is set then the Personnel has normal access, if a past date has been set then they do not have access and a "Person Expiration Date Passed" error will be displayed when they are refused access. See the steps below on how to use a template to mass set this Expiration Date field for a large number of Personnel at the same time.   1. Create a Personnel Template in the Personnel Templates Folder. Notice that the Expiration Date defaults to a future date of "12/31/2099 11:59:59 AM". 2. Go to the Attribute Data Source tab and set the ExpirationDate attribute to InheritFromTemplate. 3. Use this Template to create your Personnel objects. 4. Notice that Personnel created from this template should show the Expiration Date in Blue which is also un-editable in the Details tab. 5. Edit the Template and change the Expiration Date to a date that has already past. After saving the Template the changes will be made to all attached Personnel and those Personnel distributed to all online controllers. Viewing the Distribution Properties, you should see an entry for each object refreshed by the Template. 6. Looking at the Access Distribution View you should see that the Personnel have been redistributed down to the controllers successfully. 7. Test your Personnel at the Door and they should no longer have access. Looking in an active Event View you can see that the Personnel are not being granted access with the Message "Person Expiration Date Passed". When setting the ExpirationDate back to a future time they will now have normal access.

Issue Unable to access SE8000 parameters as shown in the user interface guide. Product Line EcoStruxure Building Expert Environment   SE8000 Cause Parameters to configure SE8000 are inaccessible Resolution To access SE8000, touch and hold the top middle screen until the thermostat display the SETUP menu. If the thermostat requests a password, please refer to your local customer care team for password combination.

Issue Double click on a point in Vista. The Edit Properties window should pop up allowing you to view the value, set the Forced-By-Operator setting, and set the forced value. Sometimes double clicking it does not open any window. Product Line TAC Vista Environment Vista Workstation Double or dual monitor Cause The Edit Properties window is popping up off of the screen. Either it was dragged off of the screen accidentally or a second monitor was removed or is not accessible through remote connections. Resolution To display the dialog on the main screen: Double click a point in Vista. Do not click on anything else. The invisible Edit Properties window should be the current window. Press three keystrokes in this order: Alt + Space + X.  This is the Windows hotkey combination to the File menu, and will maximize the current window on the monitor. Possibly try hitting the Alt key twice. This brings the current window to the front. Alt + Space bar, then select Move with the mouse, after a tap of any arrow key, the mouse should lock onto the window allowing you to move it To prevent this from happening in the future: Download the TAC Vista Dialog Position Reset utility. Unzip and double click the executable file to run. Hit the Reset button.

Issue When the TE2 has been added to an MPM controller and the required Zigbee setting entered, the controller will not come online. The TE2 has been setup and joined the Zigbee network shown by a solid blue light on the front. The settings in the MPM have been entered correctly and the number from the label on the TE2 has been used as the ID. Product Line EcoStruxure Building Expert Environment SmartStruxure Lite Multi-Purpose Manager SEC-TE (TE2) Cause It has been seen that the Extended Node ID sticker on the back of the TE2 is missing or has incorrect digits. Resolution Use the comm log on the MPM by pressing the service button on the TE2 for 6 seconds. This broadcasts the TE2 Extended node ID. That ID can then be copied to the Zigbee setup for correct communication.

Issue Need an example on how to program a required action where a Door Switch activation triggers alarm sounder to turn on and stay on until a Key Switch is closed. Product Line EcoStruxure Security Expert Environment Security Expert Cause Require a programming example. Resolution There may be a number of ways of doing this, one solution is to have a Door Switch trigger an alarm in the Door's Area which triggers an Alarm Output to turn on. A Key Switch Input is linked to another Automation Area that will disarm the Door's Area which turns off the Alarm Output.   In this example we will use the following objects: Input        Door_Switch_Input Input        Key_Switch_Input Output        v_Alarm_Output        (a virtual output for this test) Area        Door_Opened_Area Area        Area_Automation Input Type        KeySwitch_InputType   Setup 1. Create an Output, in my example this is virtual output v_Alarm_Output. 2. If not already created create the Area your Door is located, in my example I created Door_Opened_Area.   3. On the CONFIGURATION tab set the alarm timings to 0. 4. On the OUTPUTS tab set the Alarm Memory Output to your alarm output. 5. create the Area that will be used as an automation area to reset the door alarm. In my example I created Area_Automation for this purpose.   6. On the CONFIGURATION tab set the alarm timings to 0. 7. Create a new Input Type, in my example this is KeySwitch_InputType. On the GENERAL tab set the Control Area to the area with your door switch in it. (Door_Opened_Area) 8. On the OPTIONS (1) tab, under MISCELLANEOUS OPTIONS, set the Disarm Control Area On Input Restore and Arm Control Area On Input Alarm options. 9. If not already created, create your door switch input. In my example this is Door_Switch_Input.   10. On the AREAS AND INPUT TYPES tab set the Area to your door area and the Input Type to Instant. 11. If not already created, create your key switch input. In my example this is Key_Switch_Input.   12. On the AREAS AND INPUT TYPES tab set the Area to your automation area and the Input Type to the input type you created earlier (KeySwitch_InputType). 13. Go to a Status Page view with these two Areas listed and disarm then arm each of them. This needs to be done after any change to the Area or objects within it (such as inputs) so they will function properly with the new changes.   Notes: KeySwitch = Closed -> Alarm disarmed (Area_Automation) KeySwitch = Open -> Alarm armed (Area_Automation) To disable alarm and reset area, KeySwitch must be Closed and then Opened. DoorSwitch needs to be closed for Alarm to be re-enabled with KeySwitch.   Usage 1. Armed normal state. 2. Door Alarmed. Door_Switch opens triggering alarm in Door_Opened_Area triggering v_Alarm_Output to turn On. 3. Alarm silenced by Key_Switch. Key_Switch is Closed triggering Door_Opened_Area to be disarmed and v_Alarm_Output to turn Off . Key_Switch is Opened triggering Door_Opened_Area to re-arm. 4. Alarm will not re-trigger again until Door_Switch is closed and Area re-armed.

Issue Integration to the Powerlogic CM4000 power meter with the Xenta 500 \ Xenta 700 \ Xenta 900 and Modbus RTU Environment Xenta 511, 527, 701, 711, 721 (5.1.5 up) Xenta 731, 913 (all versions) XBuilder Powerlogic CM4000 Power Meter Cause Disclaimer: This device template is intended to provide a starting point for an integrator, and is in no way written to be the mandatory points list for your integration effort. Product Support Services-Dallas has written this device template in an effort to give our customers a starting point and solid example of how to develop a device template for the above product. The integrator will be responsible for any additions or modifications to this device template. Please report any problems to PSS Dallas at product.support@buildings.schneider-electric.com Resolution Please us the following .dev file as a starting point and a guide to the integration. This .dev file contains a set list of registers that PSS assumed would be seen as critical and important to the integration process. If any other data is needed please see this supported document to make the necessary changes.   To use these files in Xbuilder please follow these steps: Extract the .dev file from the .zip file in the link above, and place it on your harddrive. In Xbuilder, right click on the Modbus Master device and chose Add Device Browse to the needed .dev file and choose Open. Rename the newly added device to a unique name within the Modbus Master network.

Issue Security Expert PSU has Fault Icon lit and Status Light Flashing Red Every 3 Seconds indicating an issue with PSU Addressing Product Line EcoStruxure Security Expert Environment Security Expert PSU Cause The module address 254 is the default value which all modules are shipped with and is outside the range the controller can accept. This must therefore be changed during commissioning. See Page 41 of the Operator Reference Manual for details. There is an overall limit of 250 modules that can be connected to a single controller with the following limit on each type of module: Keypad Modules: 200 Input Expanders: 248 Reader Expanders: 64 Output Expanders: 32 The module addressing is defined per module type not by the position of that module on the network. You could have all modules at the same address as long as they are all different types. Example: With the following modules we could have all modules be set to use address 1: 1 x Controller 1 x Keypad 1 x Reader Expander (In this case onboard Reader) 1 x Analogue Expander (PSU) Resolution 1. Right Click on the SP-C Controller and select Module Addressing. Change the Address of the Analog Expander (PSU) from its default value of 254 in this case to a value of 1. 2. Then Update all Modules. 3. Select the Analog Expander (PSU) in the System and also change its Physical Address to also be 1. Save the changes. 4. The PSU should now come online and the Fault Icon on the PSU will no longer be lit.

Issue Need the procedure to create an Unlock Door Schedule. Product Line EcoStruxure Access Expert Environment Version 2 Hosted Version 3 Hosted Premise Cause How to create a schedule for a door to unlock during business hours and then relock afterwards. Resolution To unlock a door or doors during a particular time, a schedule needs to be created for that duration and then assigned to the Mode of the necessary doors. The following steps describes how this should be done: 1. Create a schedule for the time duration 2. Select the particular doors from the Hardware Tree 3. Select the Mode Tab on the door editor 4. Add Mode to the Door based on what is being accomplished 5. Click on the Schedule Icon to add the necessary Schedule    6. Add Schedule, Action and Access Method  7. Save and Close the Editor 8. Once the controller verifies the configuration, the Door will follow the Mode