Building Automation Knowledge Base

Issue What is the procedure on transferring Continuum from one PC to another PC? Product Line Andover Continuum Environment CyberStation SQL Cause Workstation hardware needs to be upgraded or replaced altogether Resolution Collect information from the existing machine Collect all IP address, DNS server and Windows Server IP information from the existing workstation. Run Continuum Database Initialization on the existing machine. Select Workstation and record the following information. Workstation Name Folder Name Device Node ID Network ID Data Source Name Database Name User Login ID Server Name. Verify that correct Database Passwords are known for both Andover97 user and sa accounts Start Continuum and run PinPoint. From the View menu select Options Record the folder path indicated under Graphics (Pin Files) and archive these files.  Record the folder path indicated under Background and archive these files.  If any customization has been done to the menu pages (i.e. hot spot) then the User Profile folder( C:\Program File\Continuum\UserProfile) should also be archived. Backup the Continuum Database Move the database backup and the contents of the archived folders described above to a secure external drive or a network folder (not on the workstation itself). Install CyberStation on the new machine Before removing the existing machine from the network, start the new Workstation without connecting it to the network. Configure the IP Address, DNS server and Windows Server IP address collected from the existing machine. Install CyberStation on the new Workstation PC Note: Do not forget to disable all Virus Protection and Firewalls.  When prompted run Database Initialization Use the information collected on the existing machine to initialize the StandAlone Database. Use the information collected on the existing machine to initialize the WorkStation. Start Continuum and verify that the CyberStation operates normally. Copy data collected from the existing workstation onto the new workstation. Copy Database backup file to the Backup folder under C:\Program Files\Microsoft SQL Server\ Copy contents of the archived Graphics folder to the same folder on the new workstation PC. Copy contents of the archived Background folder to the same folder on the new workstation PC. Copy contents of the archived User Profile folder to the same folder on the new workstation PC. Run PinPoint From the View Menu select Options Under Graphics (Pin Files) enter the folder path to where the Graphics files have just been copied (see above). Under Background enter the folder path to where the background image files (see above). Select the Check button and verify that a failure notice (a red "X") does not appear beside any item. Close PinPoint Restore the Continuum Database. On the new workstation, run SQL Server Management Studio Express. Navigate to the Continuum Database. Right click on the Continuum Database, select Restore Browse to the folder where the existing Database backup file was copied to.  When the restore has completed successfully. Change the DB Owner: Right clicking on the Continuum database Selecting new query. In the query window type SP_ChangeDBOwner Andover97 From the tool bar select Execute. The result window should return............Command(s) completed successfully Reset the passwords for Andover97 and SA Open Security from the main tree, Select Logins. Right click on Andover97 and select properties enter and retype new strong password password, retype the correct password. Repeat for SA password. Now restart the PC. Run Database Initialization Under StandAlone, update the database. Re-Launch Continuum CyberStation and verify that CyberStation is working properly. Shut down the new workstation. Swap the workstations Shutdown the existing workstation and remove it from the network. Connect the new workstation to the network Start the computer. Launch Continuum and verify all functions are operating as expected.

Issue How to show raw card data of a badged card in Security Expert. Product Line EcoStruxure Security Expert Environment Security Expert Custom Card Format Cause Need to configure a custom card format and need to see the raw bit string to determine this. Resolution Displaying a cards raw data is a function that can be set in the Reader expander. 1. Confirm that the Display Card Data When Invalid option is enabled on the Reader tab under Misc Options. Misc options Display Card Detail When Invalid: When enabled, the reader expander will display the actual card data received from the reader when the card number is not known. This can be used to interface with custom third party applications that require their own processing of card information. This option is enabled by default and can be used to add card data to a user when operating Security Expert. When disabled the reader will display the card number not found message. 2. Next, set the Reader format on the Reader tab under Configuration to Any bit (raw). any bit raw 3. Now when badging a card at this reader port it should populate two events. One for the Card Number Raw Data and another for the Facility Code Raw Data.   Example: Read Card Number Raw Data: 46160846 Read Facility Code Raw Data: 436207616 Put the facility code into a Programmer Calculator to convert from Decimal to Binary. This is a 32-bit number. 00011010000000000000000000000000 Of the 32 bit number take the first 8 Binary digits (in the example this is 0001 1010) and convert this back to decimal. 00011010 bin = 26 dec What you should see in the decimal field is the bit length the card uses. Now in the Reader Format, it’s an experiment to find out which of the Bit options would correspond to the cards. (In the example above you would need to look through the 26 bit options.)

Issue When browsing the IP network using the WorkPlace Commissioning Tool, third party devices are displayed in addition to the I/A Series BACnet devices but no information is known about those devices. Product Line TAC I/A Series Environment WorkPlaceTech Commissioning Tool 3rd party BACnet IP & MS/TP devices Cause 3rd party BACnet devices are sometimes connected to the IP network without the knowledge of the engineer  programming the I/A Series system. Resolution When performing a global browse of the IP network, unknown devices are sometimes displayed in the WorkPlaceTech Commissioning Tool device list display.  Since all data columns are not necessarily displayed, some of the device information may not be able to be directly determined. Right-click in the column headers and a menu of available data columns will be displayed. The following columns may be displayed at a minimum to allow identification of the devices on the network as well as the BACnet routing path to those devices:     Instance     Vendor     Model     Router     Network     Address   If the device is a BACnet IP device, the "Address" will be displayed as an IP Address and Port.  For example the address of a BACnet IP device communicating via port 47821 at IP 10.159.34.238 Address   =  10.159.34.238 : 47821   If the device is a BACnet MS/TP device under a BACnet IP device, the address is the MAC address of the device on the MSTP bus and the Router is the address of the BACnet IP router to that device in Hexadecimal numbers.  For example, for MSTP device #4 under BACnet IP Router address, 10.159.34.238 : 47821 10 = 0A, 159 = 9F, 34 = 22, 236 = EC and 47821 = BA CD  Address   =   4 Router      =   0A-9F-22-EC-BA-CD   If the device provides vendor and model information, that information will be displayed in the appropriate columns.

Issue When trying to use WriteProperty to a 3rd Party BACnet device the following error is generated : "An attempt has been made to write to a property defined as inaccessible through the BACnet protocol write service" Product Line Andover Continuum Environment BACnet  Cause The error can be seen when using WriteProperty OR when attempting to Manually Command a BACnet Point on a 3rd Party Device Resolution The property that is being commanded, is not available to be written to in the 3rd party device. Many properties and object classes cannot be written to on BACnet devices, this is often defined in the devices PIC Statement which has hopefully also been BTL Tested. Some BACnet devices allow writing to be enabled/ disabled, but this must be set up on the 3rd Party device itself depending on the site requirements.  An example of this is in the Jace unit where there is a regular BACnet user that has no write capabilities from 3rd party devices, so to allow this requires a tick a box for "Super user".

Issue It is normal for a BACnet network port's Poll Service 'Busy Time' property to be greater than 100%? Eg: Product Line I/A Series Environment G3 BACnet Cause The Poll Service is a common component for typical field bus drivers including BACnet.  The Niagara Ax Drivers Guide defines the Poll Service's Busy Time property as: Displays a percentage of time spent by the poll thread actually polling points, across all poll buckets. Includes (in parentheses) a ratio of “(time spent polling/total time since statistics were restarted)”. Given a small amount of time is spent transitioning between poll buckets, and with the thread sleeping to evenly space out polling messages, it is unlikely to ever see Busy Time reach exactly 100%. However, any percentage above 95% indicates that the poll thread is basically spending all of its time actually polling.  Resolution In the case of the Poll Service for a BACnet network port, because two threads are used for polling, it is possible to see a Busy Time approaching 200%. In this case, divide the Busy Time in half to get an average busy time for each thread. In the case of the Poll Service for a Bacnet network port, because two threads are used for polling, it is possible to see a Busy Time approaching 200%. In this case, divide the Busy Time in half to get an average busy time for each thread. actually polling. However, any percentage above 95% indicates that the poll thread is basically spending all of its time actually polling. to evenly space out polling messages, it is unlikely to ever see Busy Time reach exactly 100%. However, any percentage above 95% indicates that the poll thread is basically spending all of its time actually polling to evenly space out polling messages, it is unlikely to ever see Busy Time reach exactly 100%. However, any percentage above 95% indicates that the poll thread is basically spending all of its time actually polling. Given a small amount of time is spent transitioning between poll buckets, and with the thread sleeping to evenly space out polling messages, it is unlikely to ever see Busy Time reach exactly 100%. However, any percentage above 95% indicates that the poll thread is basically spending all of its time actually polling. Includes (in parentheses) a ratio of “(time spent polling/total time since statistics were restarted)”. Given a small amount of time is spent transitioning between poll buckets, and with the thread sleeping to evenly space out polling messages, it is unlikely to ever see Busy Time reach exactly 100%. However, any percentage above 95% indicates that the poll thread is basically spending all of its time actually polling.

Issue Blank window while capturing a photo using "Logitech HD Pro Webcam C920". Product Line EcoStruxure Security Expert Environment Security Expert Cause While capturing a user photo using "Logitech HD Pro Webcam C920", it shows up as an image source (in the drop-down along with Topaz). When selected however, the screen is blank. Resolution With this webcam, you need LWS software by Logitech installed on your machine. G Hub has replaced LWS however it seems like G Hub is not currently functional with the integration. Find more information about the  "LWS280" driver HERE.  The driver can be downloaded from the attachment.

Issue When the EWS is installed on the same machine using the service then all packets will be going to the localhost and will not hit the NIC so will not be captured in a Wireshark packet capture. Product Line EcoStruxure Building Operation, EcoStruxure Security Expert Environment Security Expert Building Operation Enterprise Server Building Operation Automation Servers (AS-P, AS-B) Cause Packets sent between services on the same machine (like SOAP and EWS) do not hit the NIC and therefore cannot be captured with the default configuration of Wireshark using the WinPcap packet sniffing library.  Resolution Replace WinPcap with Npcap to emulate a loopback NIC for packet capture. Go to https://nmap.org/npcap/ for details on the library. Download the library installer from https://nmap.org/npcap/#download Uninstall WinPcap. Install Npcap. Npcap will then create an adapter named Npcap Loopback Adapter. In Wireshark choose this adapter to capture, loopback traffic will be the seen the same way as other non-loopback adapters. This can be tested by typing in commands like "ping 127.0.0.1" (IPv4)  or "ping ::1" (IPv6).

Issue Need to activate an Output when access is denied to a User at a Door. Product Line Security Expert Environment EcoStruxure 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 How to associate BACnet IO points created under the BACnet Interface of the Automation Server with IO points on the Automation Server's IO bus. Product Line EcoStruxure Building Operation Environment Building Operation Servers 1.4 and above Building Operation Workstation Building Operation Automation Server Building Operation Automation Server Premium Building Operation Automation Server Bundled Cause Connect physical IO points to BACnet network controllers. Resolution BACnet Association Tool (EBO V3.0 or higher) BACnet Association Tool will map properties of a central IO point with corresponding properties of a BACnet point. The tool is capable of mapping a single IO point with a single BACnet point, optionally by also creating a BACnet point, and removing the association between IO and BACnet points. To open the BACnet Association Tool, Select the IO Bus or IO Module, BACnet Interface, Application Folder, or the BACnet point, then in the Actions menu, click BACnet Association Tool. Most useful is the ability to associate multiple IO points with their corresponding BACnet points in one operation. The tool can be run from a variety of different container types in the WorkStation Tree view, including an IO point, BACnet Point, CIO Module, or the entire IO Bus (as shown below). For more information refer to WebHelp articles: Creating and Associating BACnet Points to I/O Points (se.com) and Associating or Updating BACnet Point Associations to I/O Points (se.com) NOTE: Please be aware applying the BACnet Association Tool retrospectively, to an already configured site, can remove bindings to outputs.  For example output bindings in Script or Function Block programs.  As shown below, if the tool is used to create a BACnet Associated point for an output already bound to a program (1) the Requested Value will be replaced by the Associated Value of the BACnet point (2). This is due to how the BACnet Association Tool uses the bindings, where the newly created BACnet point should be used instead of the IO point.  The solution is to update the removed program binding (3) to use the BACnet Associated point value (4).   SBO 1.4 to 2.x To associate BACnet IO points created under the BACnet Interface of the Automation Server to points in the IO Bus in SBO 1.4 and above... The association is made via a read reference, so if we think of the two objects as one being the source and the other the destination you configure the association from the destination object so in the case of an output you configure the association from the BACnet object (in this example BO1). In the case of an input, you'd configure the association from the IO Bus input as that would be the destination object, in other words, the recipient of the value. (NOTE: for versions prior to 1.4 see Bacnet and StruxureWare Building Operation Central IO points) Create the points. In this example, we are associating an IO output point named 'Digital Output 1' with a BACnet Binary Output named BO1. From the properties page of the IO Bus point (Digital Output 1 in this example) click on the gear icon to the right of the 'Requested value' field. In the 'Requested value' editor click the navigation icon (...) to the right of the 'Reference' field and navigate to the 'Associated Value' of the BACnet point. Save the configuration changes. Now that the values have been associated setting the BACnet output value (BO1) will drive the IO Bus output (Digital Output 1)  

Issue When swiping a card in front of the reader, there should be a beep indicating that the reader has read the card. There is no beep. Product Line EcoStruxure Security Expert, Andover Continuum, TAC I/NET Environment Access Control HID Reader Cause There are 3 possible reasons for this issue: The beeper is disabled through a default configuration when the card is shipped The beeper has failed The Reader and Card represent incompatible technologies such as an 125Khz Prox Reader trying to read a 13.56MHz IClass Card Resolution Ensure Reader and Card both support a common technology (125Khz/13.56Mhz etc..) Short the Beeper wire (yellow) and the GND wire (Black) with the reader powered On If there is a beep, that indicates that the beeper can work but is disabled. Ask the manufacturer to send a configuration card to enable the beeper (use 3 seconds after reader power is on) If shorting the beeper produces no sound, the beeper has failed. Send the reader to repair and replace it with a new one.

Issue When performing Continuum Database Initialization from a CyberStation workstation, the workstation cannot connect to the SQL Server with the following error message: "Microsoft SQL Server Login Connection failed or server not available or access denied" Product Line Andover Continuum Environment LAN workstations Single User workstations Cause Possible Invalid Server Name is being used in Continuum Database Initialization:   For Continuum LAN systems, the Server Name attribute of Continuum Continuum Database Initialization includes invalid characters.  For Continuum Single User systems, the Server Name attribute of Continuum Continuum Database Initialization does not include the \SQLExpress attribute after the Computer name.  Resolution For Continuum LAN systems, type the correct computer name of the SQL Server in the Server Name attribute field of Continuum Database Initialization screen such as "MyDBServer". Check that the required strong password is being used, such as "ABCabc123" For Continuum Single User systems, add the qualifier "\SQLExpress" at the end of the computer name in the Server Name attribute field of Continuum Database Initialization screen such as "MySUServer\SQLExpress" . Restart the SQL Server  Service and/or SQL Agent Service Check that the Windows Firewall on the Windows Server PC is turned off. Check Connection with sa Admin account on MS Management Studio and via ODBC.

Issue On a working system, valid access events no longer show in the active event view and are no longer visible in the accessevent table within the Database.   However, invalid events continue to work normally.  Product Line Andover Continuum Environment Access Events Logging Cause An incomplete object may have been added to the Continuum Database recently that is interfering with queries running against that database. Resolution Try the following steps to troubleshoot the issue Does the issue happen on multiple CyberStations? Ensure all the event types are selected in the active event view that is being used on the door(s). Perform a CyberStation Teach It is best to contact PSS and work with them at this point with the following procedures.   Verify that access events are being sent from the controller to the CyberStation using Wireshark. Verify that the issue follows the Database by loading the database in a test environment to see if the issue still happens.  On the TEST database, use SQL Management Studio:  SQL Query: set acdbversion=0  (execute the query)  Update database: launch Database Initialization Server/Stand Alone Enter sa password and update database Restore database or locate incomplete object The quickest fix would be to revert to a known good database. Once restored, the events in the controllers would be downloaded to the database. Finding the object in the database that has caused the issue can be very challenging. Check to see if there was a controller recently added and if the issue began to happen after that. If for some reason a controller had been added and it wasn't completed normally then it could cause this issue. Check to see if there is a controller in the InfinityController table with an objectidhi or objectidlo with a zero value. If so, delete that controller and see if the valid access events start coming in. It may also be necessary to use the SQL profiler to view the entries that are being made into the database. See the following link  below for  more information. http://msdn.microsoft.com/en-us/library/ms181091.aspx   NOTE: Turning off the Primary and Secondary Access Server will cause the access events to buffer in the controllers, so that these events will be inserted into the database once valid access event logging has been restored. After turning off the primary and secondary, check the Access Log infinity system variable on the controllers. If they are non zero values, then events are buffering. There is a limited amount of access events that can be stored in the controllers before loss of data occurs.

Issue Support for HID Corporate 1000 Product Line TAC I/NET Environment HID Corporate 1000 35-bit Wiegand Cause Desire for higher security HID Corporate 1000 Cards Resolution I/NET will work with Corporate 1000 cards, but there are several things to check and go over concerning this type of setup.   Below is a link to the HID Corporate 1000 information page and FAQs https://www.hidglobal.com/access-control/corporate-1000-program   One other consideration is the site will have to go to a Large Number format for the Corporate 1000 format.  The site requesting Corporate 1000 card certification will need to be verified, and though this is not an expense, it will take time.     Note: I/NET will not allow two variations of Wiegand in the same controller. In the door parameters, set up a single Reader type, such as Wiegand 26. 

Issue After installing a new SQL server and installing CyberStation on a workstation PC, Database Initialization is unable to connect to the database. Product Line Andover Continuum Environment SQL Database Initialization Cause The Database has not been assigned with a correct owner. Resolution In SQL Server Management Studio, highlight ContinuumDB. Right Click on ContinuumDB. Select "New Query" In the query field type SP_ChangeDBOwner 'Andover97' Run the query Once the query returns Success, it should be possible to Initialize the Database successfully.

Issue 7790A LAN Interface Unit and Information. Why is the 7790A not shown in my Network Configuration Product Line TAC I/NET Environment I/NET Seven Software v2.45 7790A LAN Interface Unit (LIU) 7791A Door Processing Interface (DPI) 7792A Micro Regulator Interface (MRI) 7793A Micro Control Interface (MCI) Cause Information about the 7790A LAN Interface Unit or LIU Confusion is usually with the Hardware Model when purchasing. Once installed and configured for one of the three common options above, firmware (software) is downloaded to the hardware device (7790A) to become one of the three indicated interfaces, DPI, MRI, and MCI. In the later release of I/NET Seven Software only supports the 7793 MCI.  Resolution Refer to TCON109 attached for further information.    The 7793 has two channels and will handle 32 devices on each channel if addressed correctly. This gives a total of 64 SCU units on a single 7793. The 7790A can be addressed using the HHC to a 7790, 7791, 7792, 7793, 7797.  The 7790A replaces the 7797A-C as of January 1, 2013. The original 7791 was primarily for Access Control. The original 7792 was primarily for HVAC. The 7793 is a combination for both and the most popular of the 7790 series. To clarify, when purchasing a 7790A, you would address as a 7793, then put up to 32 SCUs on each of the channels giving you a total capacity of 64 SCUs.     For access control, the model 7798C has more memory but only one Channel, which means it can handle up to a maximum of 32 SCU controllers and the recommended interface for larger access control sites.  

  Issue Continuum compatibility with Video Expert Product Line Andover Continuum Environment Andover Continuum Video Expert Cause Video Expert is not listed as a video integration for Continuum on the Video compatibility matrix. Is there any way to accomplish the integration? Resolution Continuum and a Video Expert integration is not supported natively (by R&D) like the other Pelco integrations. For Example Digital Sentry and Endura.   The Center of Excellence(CoE) team has a number of add-ons/pay-for Continuum integrations including Video Expert.    However, the Video Expert add-on integration has not been updated since 2018, so the integration is no longer compatible with the current version of Video Expert.   Unfortunately, with Continuum end-of-life approaching the CoE team are no longer upgrading any legacy integration software versions. Link to Continuum Video Compatibility Matrix Article: https://community.se.com/t5/Building-Automation-Knowledge/Continuum-Video-Integration-Compatibility-Matrix-and-Supported/ta-p/531  

Issue A method is needed to automatically schedule and run Continuum standard reports Product Line Andover Continuum Environment Cyberstation Windows10 Cause Sites want Continuum Report to run automatically  Resolution Scheduling Automatic Reports Using a special Continuum application, ReportCmdLine,  and Microsoft Windows Scheduler, reports may be run automatically on a regular basis at a specific time. When the report runs automatically, it can also automatically be emailed to one or more recipients and/or saved to a file.   CyberStation must be running when using the ReportCmdLine application. To set up and run a report automatically, perform the following procedure:   If the report should also email when it runs automatically, check the Output report to email address checkbox on the Output tab, and enter email address recipients. Likewise, if the report should save to file when it runs automatically, check the Output report to file in path checkbox and enter the file's path.   From Start> Run> control (type this command and Enter) This will open up Windows control panel Double-click Administrative Tools> Task Scheduler Click Create Basic Task, Name: ReportCmdLine (or whatever name is needed), Next Select how often the task will be run, Next Specify the start date and how often the task should recur, Next Select which action to be performed, Next Enter the ReportCmdLine executable path and command line options /o - ObjectName Enter the path name of the Report object to run automatically. It is recommended to use a  full path instead of just the name of the object file. /u - UserName Enter the CyberStation User Name /t -Type Enter an integer to specify the type of distribution: 0 — Save to a file 1 — Email 2 — Save to a file and email In the Program/script field, enter the command syntax as follows: “C:\Program Files (x86)\Continuum\ReportCmdLine.exe” /o ObjectName /u UserName /t Type Note: Make sure the command option parameters are set outside the quotes surrounding the path and executable Example with the Continuum objects specified: “C:\Program Files (x86)\Continuum\ReportCmdLine.exe” /o DailyRpt /u acc /t Type 0 If the ObjectName or UserName contains a space, then place quotes around those items: “C:\Program Files (x86)\Continuum\ReportCmdLine.exe” /o “Object Name” /u “User Name” /t Type 0 Parameter Descriptions The email recipients and file path are specified on the Output tab After clicking Next, click Yes to accept the command and arguments Click Finish to create the Task   See the following link for additional information on setting up a Scheduled Task in Windows10:  https://www.windowscentral.com/how-create-automated-task-using-task-scheduler-windows-10    Note: If having problems getting the report to run, try typing the report command from step 7 into a DOS prompt. This will give immediate feedback to make sure the command is getting executed. Doing this prior to using the command in Task Scheduler will help to get the command set up correctly.   For additional information, see Continuum Help (F1) in the Reports> Scheduling Automatic Reports section.

Issue How to configure search object to display SpaceLogic controllers IP settings "Changes pending" in the search's list view Product Line EcoStruxure Building Operation Environment Space Logic IP controllers  Cause Confusion when attempting to find the appropriate type to include in the search  Resolution The IP settings "Changes pending" property is not a property of the device but rather a property of the IP Network Port as seen in the screen shot below  

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 correctly. Before beginning these steps, ensure all necessary 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 MNB firmware may not match the version reported in EBO and Building Advisor Portal. Product Line EcoStruxure Building Operation, EcoStruxure Building Advisor Environment I/A Series MNB I/A Series WorkPlace Tech Building Operation Workstation Building Operation Building Advisor EBO Health Module Cause MNB firmware is upgraded via the WorkPlaceTech Commissioning Tool independent of EBO, and EBO reports firmware to Building Advisor Portal for use in BMS Health Module. Example cases where controllers are upgraded after adding to EBO are: MNB controllers added with factory default firmware version MNB controllers transitioned into EBO with existing older firmware version MNB controller that was upgraded to the latest was replaced with MNB Controller at factory default firmware version Resolution Create a Saved Search to identify all MNB controllers in the system Create New Search Enter * in Object Name Field Click ... button next to Include Types: and add all the MNB controller models Right-click on Column Header and select Add/Remove columns to select Firmware revision and Model name, and remove Description Save the search and select a location and name it Run the search to identify all the MNB controllers Sort by Firmware Revision to find older versions. MNB-1000 will end in 01.5xx and all other MNB ASC models will end in 01.4xx Update firmware version from the controller(s) Select one or more MNB controllers Right-click and select Device -> Upload Configuration. *WARNING*: Ensure you do NOT select Download Configuration  Now EBO is reporting the correct firmware in the controller and will upload this information to Building Advisor Portal, if cloud connectivity is established. Upgrade any MNB controller firmware with WorkplaceTech Commission Tool to the latest version and perform Steps 2 and 3 to keep EBO updated.

Issue It is not clear how to replace an existing AS with a new AS-P Product Line EcoStruxure Building Operation Environment Automation Server (AS) Automation Server Premium (AS-P) First detected in version 1.7 Cause Detailed instructions on how to replace an existing AS with a new AS-P are needed Resolution WebHelp references Automation Server Replacement Using Restore Automation Server Replacement Using Restore Workflow Overview Main differences between an AS and an AS-P: In the AS-P, the RS-485 ports have been re-located to the top. The AS-P has 2 Ethernet ports; port 2 can be used as a switch only as of SBO version 1.81. AS-P device USB port format changed to mini USB. Operator Panel port has been removed. Hardware factory reset has been removed. AS-P uses pluggable connectors for field buses. (not shown in picture above) Consider the power consumption. AS-P requires 10 watts, while the Automation Server only required 7 watts. Preparations In preparation for replacing an Automation Server with an AS-P the following considerations must be made: Power consumption Since the AS-P consumes three more watts than the classic Automation Server, the power budget needs to be reviewed to check whether an additional power supply and/or rearrangement of the current configuration is needed, if the configuration includes IO modules. Terminal base The terminal base for the classic Automation Server can be used with the new AS-P after removal of the upper terminal block. Note though that all field buses wiring has to be moved to the pluggable connectors used with the AS-P. RS-485 field bus re-wiring Since the RS-485 ports and connectors have been relocated, the termination at the server of any field bus located on those ports will need re-wiring. Also, the physical specification of the RS-485 port is changed in the AS-P, so review whether the termination resistors needs to be replaced. Refer to Configuration Selection for Generic RS-485 Network Devices AS-P firmware Unlike the classic Automation Server, the AS-P ships from the factory with no firmware installed. Make sure to procure the appropriate Device Administrator firmware to install in the unit. First version that supports the AS-P is 1.7. Note once again that the USB port format in the AS-P is mini USB, so procure the appropriate USB cable. Backup file Make a backup of the classic AS to be replaced, the AS-P will restore from a classic AS backup but this is a one way process, the classic AS will not restore from an AS-P backup file. If the classic AS is running an older version of firmware, it will have to be upgraded first to at least 1.7.2. Power budget review Since the AS-P consumes 10 watts of power versus 7 watts for the classic Automation Server, it is necessary to review the power budget to ensure there is enough power for the AS-P, if the Automation Server being replaced is hosting IO modules. One power supply (PS-24V) can supply 30W. The following table shows power consumption for the different device types Device Power AS-P 10 AS 7 DO-FA-12-H 1.8 DO-FA-12 1.8 DO-FC-8-H 2.2 DO-FC-8 2.2 DI-16 1.6 RTD-DI-16 1.6 AC-4 11.1 UI-16 1.8 AC-2 5.5 AO-8-H 4.9 AO-8 4.9 AO-V-8-H 0.7 AO-V-8 0.7 UI-8-AO-4 3.2 UI-8-AO-4-H 3.2 UI-8-DO-FC-4 1.9 UI-8-DO-FC-4-H 1.9 UI-8/AO-V-4 1.0 UI-8/AO-V-4-H 1.0 In case one or more additional power supplies are needed, refer to the example given in last part of this article.   Note: The following "replacement procedure" applies to SBO 1.7.x, 1.8x, 1.9x, EBO 2.0x and 3.0.x and 3.1.x. The AS-P must be running the same version as the original AS backup. The AS was no longer supported from EBO 3.2.x. If the site needs to take the AS-P to EBO 3.2 or later, the following should be followed at the AS supported version, then once the AS backup has been restored to the AS-P, the AS-P can be upgraded further, following the supported upgrade path, which can be found in the release notes for the specific EBO version.   Replacement procedure The following procedure assumes the classic Automation Server is being replaced with a brand new AS-P from the factory If the Automation Server is hosting IO modules then perform the steps in the 'Power Budget' section below before going to the next step. Perform pre-maintenance procedure per site requirements, i.e. put equipment in hand control mode etc. Pull out the classic Automation Server from the terminal base. The hardware is designed for hot swapping so there is no need to power down the system. Remove the terminal block from the terminal base as indicated above. Insert the AS-P in the terminal base. Connect Device Administrator to AS-P via USB and install a new database on it. You may want to check the 'Set time on device' check box to initialize the time in the AS-P since its current time is most likely at default if this is a brand new unit or a unit that has been powered down for a while. Using Device Administrator set the communication parameters of the AS-P (IP address etc) to match the settings of the classic Automation Server being replaced. Connect Ethernet cable from network switch to Ethernet 1 port on the AS-P. If a hotfix was installed on the Automation Server that is replaced, apply any hotfix needed to match the version of the firmware in the AS-P to the version of the backup from the Automation Server. Since the AS-P should now be able to communicate over IP the application of any HF can be done either over USB or IP. Using WorkStation, log in directly into the AS-P and restore the backup from the classic AS. Insert pluggable connectors for field buses. If there is an Enterprise Server, log into Enterprise Server from WorkStation and verify the newly swapped AS-P is online. Verify IO modules (if any) are online. Verify field devices (if any) are online. Return the system to software control per site requirements. Verify the system is operating correctly then perform a backup of the AS-P. Power supply addition example Consider the following system If we do the math, the power consumption of this system is 29.8 watts. To avoid exceeding the capacity of the existing PS we need to add an additional PS to the configuration before we replace the Automation Server with an AS-P. In order to maximize the use of the capacity of the first PS we will add a new PS at slot #7 and move the UI8AO4 IO module from slot #7 to slot #8.   Steps Disconnect the UI8AO4 IO module making sure it powers down. It is necessary that any IO modules being relocated on the IO bus are powered down so that they 'forget' their current module IDs. *** Logon to the Automation Server, make sure UI8A04 shows offline then edit the module and change its Module ID from 7 to 8. Insert power supply at slot #7 Attach the UI8A04 after the new PS (slot #8), when it powers up it will obtain its new Module ID (8) from the Automation Server. Last, if the module’s name contains the ID (Slot07:UI8AO4) it may be a good idea to rename it using the new ID to avoid confusion. (Slot08:UI8AO4) *** It is absolutely necessary that all the modules that will change IDs be powered down, if there are multiple power supplies in the chain make sure to power down all power supplies that are supplying power to any modules that will change slot #. When removing or inserting IO modules or handling S-Cables, care should be taken not to bend or otherwise damage the pins that connect the module to its IO terminal base, any damage to the pins may cause the module address to shift.   Tip There is a tool on the community (SBO xbk Analyzer) that can be used to automatically calculate the power budget from a backup of the AS/AS-P. Here is the power budget report generated from the tool after addition of second power supply at slot #7 before replacing the classic AS with an AS-P. The total power consumption is 29.8 watts but we have increased the power capacity of the system to 60 watts with the addition of the second power supply.   The instructions above are available as a PDF: Replacing a classic AS with AS-P