Building Automation Knowledge Base

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 Where can I find information on LCX89x controllers. Environment LCX89x LCX890, LCX898 Cause While LCX89x controllers are being sold by Schneider Electric as of April 19, 2013, there is not a lot of information on the LCX line at the Extranet website. Resolution Series LCX 890 Infinet Controllers       Part Number Description     01-0008-036 LCX 890 Lighting Controller, 8 outputs w/RR9 relays     01-0008-037 LCX 890 Lighting Controller, 8 outputs no relays     01-0008-039 LCX 891 Lighting Controller, 16 outputs w/RR9 relays     01-0008-040 LCX 891 Lighting Controller, 16 outputs no relays     01-0008-042 LCX 892 Lighting Controller, 24 outputs w/RR9 relays     01-0008-034 LCX 892 Lighting Controller, 24 outputs no relays     01-0008-081 LCX 898 Lighting Controller, 48 outputs no relays     01-0008-083 LCX 898 Lighting Controller, 48 outputs w/RR9 relays   LCX890 Series Controller Installation Guide

Issue How to display custom text and properties of an alarm in the email notification. Product Line EcoStruxure Building Operation Environment Email Notification Substitution Codes Cause There may be certain situations where a specific property of the monitored value needs to listed in the alarm email that is sent out. For example when an alarm is triggered, the value at the time the alarm state changed my need to be documented in the notification email. These are called substitution codes. Resolution The properties of the Email Notification can be set to customize the message that is sent out when an alarm changes states. As seen in the properties window of the Email Notification above, the "Subject" and "Text" can be changed to say whatever is desired. There are special codes that can also be entered into these fields to pull actual properties from the value that went into alarm. Below is a table that lists all of the Codes for the different value properties. This same information can also be found on the EcoStruxure Building Operation WebHelp. Substitution Codes for Notifications Code Description @(AcknowledgedBy) Writes the user that acknowledged the alarm. @(AcknowledgeTime) Writes the time the alarm was acknowledged. @(AckRequired) Writes an indicator if the BACnet alarm requires acknowledgement. @(AlarmState) Writes the present state of the alarm. @(AlarmText) Writes the alarm messages that is added to the alarm. @(AssignedID) Writes the unique ID of the user the alarm is assigned to. @(​AssignedState) Writes the current assigned state the alarm is in. The possible values are Unassigned, Assigned, and Accepted. @(​AssignedTo) Writes the name of the user or group that the alarm is assigned to. @(​AssignedToDomain) Writes the domain of the user or group that the alarm is assigned to. @(BACnetEventType) Writes the BACnet event type for this alarm. @(BACnetNotificationType) Writes whether the BACnet notification was an alarm or event. @(BasicEvaluationState) Writes if the alarm is active or not. @(Category) Writes the category name of the alarm. @(CommandValue) Writes the value which was commanded for a BACnet command failure alarm. @(ConfirmedNotification) Writes an indication whether a BACnet notification was issued as a confirmed or unconfirmed BACnet message. @(Count) Writes the number of times the alarm has toggled between the alarm and reset states. @(Deadband) Writes the value of the deadband used for limit checking for BACnet out of range alarms. @(DeviceName) Writes the name of the I/NET device that generated the event. @(​DisabledCause) Writes the cause of the alarm being disabled. An alarm can be disabled by User, Shunt variable, and System. If the alarm isn't configured correctly it can be disabled by System. @(ErrorLimit) Writes the difference limit that was exceeded for BACnet floating limit alarms. @(EvaluationState) Writes the present evaluation state of the alarm. For example, Upper limit alarm is displayed when the monitored value reaches the upper alarm limit. @(EventFromState) Writes the event state of the object prior to the occurrence of the alarm condition for BACnet alarms. @(CWSid) Writes the EcoStruxure Web Service identification of the alarm on the external system. @(CWSSourceId) Writes the EcoStruxure Web Service identification of the external object that generated the alarm. @(ExceededLimit) Writes the value of the limit that was exceeded for BACnet out of range alarms. @(ExceedingValue) Writes the value that exceeded a limit for BACnet out of range alarms. @(FeedbackValue) Writes the value that differs from the commanded value for a BACnet command failure alarm. @(FirstName) Writes the first name of the individual whose key/card was used at the I/NET door point. @(Hidden) Writes the visible status of an object. False is displayed when the object is shown. @(IndivNdx) Writes the individual number of the individual whose key/card was used at the I/NET door point. @(LastName) Writes the last name of the individual whose key/card was used at the I/NET door point. @(Logging) Writes whether the alarm should be logged or not. @(MessageText) Writes the text of an I/NET action or dispatch message, if there is one. @(MonitoredObject->DESCR) Writes the description property of the monitored object. @(MonitoredObject->NAME) Writes the name property of the monitored object. @(MonitoredObject->NOTE1) Writes the note 1 property of the monitored object. @(MonitoredObject->NOTE2) Writes the note 2 property of the monitored object. @(MonitoredObject->LabelText) Writes the label text of the monitored object. This requires that a MonitoredVariable is configured. @(MonitoredValue) Writes the value depending on the alarm states selected under 'Notify on transition to'. @(​MonitoredVariable) Writes the path of the monitored variable. @(NewMode) Writes the new mode of the monitored object for a BACnet change of value alarm. @(NewState) Writes the new state of the monitored object for a BACnet change of state or change of life safety alarm. @(NewValue) Writes the new value of the monitored property for a BACnet change of value alarm. @(NotificationClass) Writes the distribution information of an alarm notification within a BACnet system. @(OperationExpected) Writes the next operation requested by the monitored object for a BACnet change of life safety alarm. @(OriginalAlarmText) Writes the alarm text from the matched alarm. This substitution code is only available for Alarm Decorators. @(PossibleOperatorActions) Writes the possible actions one can perform on the record, given permissions. @(PreviousAlarmState) Writes the previous alarm state. @(Priority) Writes the current priority level of the alarm state. @(ProcessId) Writes the process identifier configured by the notification for a BACnet alarm. @(ReferencedBitString) Writes the new value of the monitored bitstring property for a BACnet change of bitstring alarm. @ (Report) Writes the name of the report connected to the notification. @(SEQNO) Writes the sequence number of the record. @(SetpointValue) Writes the value of the setpoint when the alarm condition occurred for a BACnet floating limit alarm. @(​Source) Writes the path of the source object. @(SourceName) Writes the name of the source object that generated the alarm. @(SourceObject->DESCR) Writes the description property of the source object. @(SourceObject->NAME) Writes the name property of the source object. @(SourceObject->NOTE1) Writes the note 1 property of the monitored object. @(SourceObject->NOTE2) Writes the note 2 object of the monitored object. @(​SourceServer) Writes the path to the server where the source object is located. @(StatusFlags) Writes the status flag of the object. @(SystemAlarmId) Writes the alarm ID generated by the system. @(TenantNdx) Writes the tenant number of the individual whose key/card was used at the I/NET door point. @(TimeStamp) Writes the time and date when the event was generated. @(TriggeredTimestamp) Writes the time and date of the last state transfer from normal state to alarm state. @(TYPE) Writes the record type.

Issue Cannot find manual service pin location Environment Schneider Electric SE76xx, SE73xx and SE72xx Viconics VT76xx, VT73xx, VT72xx Ready7 Commissioning Neuron ID Lonworks ID Service Pin message Cause The Service PIN is used to identify the device at commissioning. There is not a visible service pin button located on the Viconics device. Resolution A Service Pin will transmit the program ID and the Neuron ID (LonWorks Unique ID) contained in the device to the commissioning or service tool. The Status LED will blink when the device accepts the Service PIN command. VT7600 device - Press simultaneously the “Yes” button and the “No” button located on the keypad interface VT7300 and 7200 device - Pressing simultaneously the “Up” button and the “Down” button located on the keypad interface.       Additional Information on Viconics VT7600 series can me found in this Viconics Lon Integration Manual. Additional Information on Viconics VT7300 and VT7200 series can me found in this Viconics Lon Integration Manual.

Issue Using BACnet IP to add a SmartStruxure Lite MPM to a StruxureWare Building Operation Enterprise Server or Automation Server Product Line EcoStruxure Building Expert, EcoStruxure Building Operation Environment StruxureWare Workstation Cause SmartStruxure Lite systems may desire an Enterprise Level Solution to bring multiple sites into one system. Resolution Configure the SmartStruxure Lite MPM for BACnet IP as shown in MPM BACnet Integration. Ensure that the BACnet Network ID is Unique to the system and does not match the Network ID in use by the Enterprise Server Save the BACnet Configuration Be sure to Right Click on the Root Object of the MPM and save the database. Open StruxureWare for Building Operation Workstation Right Click on the Server Object and add a BACnet Interface Ensure that the BACnet interface has a unique BACnet Network ID which does not match the Network ID used by the MPM Expand the BACnet Interface Click on the Server Object and select the Device Discovery Tab Select BACnet Devices NOTE: There have been instances of Skype causing interference with this process. Please completely close Skype if you are using it and unable to discover any devices. ALSO NOTE: There may be 2 instances of the MPM shown. If so, use the MPM that is part of the Enterprise Server BACnet Network Drag the MPM to the BACnet Interface/IP Network object in the Enterprise Server System Tree Right Click on the Device and Upload it If any devices are connected to the MPM such as a Zigbee Wireless State or Enocean switch, these will be discovered in the BACnet Network configured in the MPM Add these devices to the Enterprise Server by dragging and dropping them to the BACnet Interface/IP Network object Right Click and upload all devices.

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 Under rare circumstances, resetting your Manager to its factory defaults may be necessary.  For example, if you have forgotten your Manager's IP address, or if you are experiencing login problems.  Environment SmartStruxure Lite Web Browser SmartStruxure Lite MPM Cause All SmartStruxure Lite™ Managers are equipped with a bootloader, accessible via a special IP address that lets you access several Manager firmware functions, among them, a factory reset.  Resolution WARNING: Restoring your Manager to factory settings should only be performed as a last resort; doing so will erase all its objects and devices, requiring you to reconfigure your Manager from scratch. Accessing the Bootloader As its name suggests, you access the bootloader at boot time, i.e., when you power up your Manager. To perform a factory reset: 1. Disconnect electrical power from your Manager by unplugging its power connector or unplugging its power supply from the AC outlet. 2. Ensure that your computer's TCP/IP settings are on the same subnet as the bootloader IP address:10.50.80.X.     IMPORTANT: Upon restarting your Manager, you will have only a brief interval–approximately 5 seconds–during which you will be able to access the bootloader. As such, we recommend that you perform the following steps 3.  Open your browser and type the following IP address into the address bar, but do not click the browser's Go icon or press any  key on your keyboard: 10.50.80.2 4. Reconnect your Manager's electrical power. 5. Within approximately 5 seconds, click your browser's Go icon or press the key to navigate to the  bootloader's IP address.  The bootloader screen displays.    6. In the Restore factory defaults area, click Submit. The Manager begins restoring its settings to the factory defaults. When completed, a success message displays.  7. Restart your Manager by clicking the Submit button in the Restart system area. 8. You may now log in to the Manager using its restored IP address: 10.50.80.3. If you cannot connect successfully to the bootloader using the above steps, chances are you are not navigating to the bootloader's URL within the defined 5-second window.       As an aid, some users may find it useful to do the following:      Open a command window and type the following: ping 10.50.80.2     As soon as you see a ping reply, return to your browser window and press the key to navigate to the address previously entered into the address bar.   Restoring your Manager to Factory Settings download as PDF.

Issue When a TGML graphic is opened from Webstation red crosses is shown on the whole graphic or sometimes over certain components. After a few seconds the red crosses disappear. Product Line EcoStruxure Building Operation Environment Building Operation Webstation version 2.x and 3.0.x Cause The red crosses only appear when values from field bus devices are displayed in in the TGML graphic, and only in Webstation version 2.x and 3.0.x. When the graphic is opened from Workstation no red crosses are shown in the graphic. Resolution This issue is fixed in EBO version 3.1.1

Issue Automation Server Classic support for hosting MPX or RPC Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Classic, AS-P, AS-B Building Operation SmartX MPX, MPC, MPV field controller Building Operation SmartX RPC field controller Cause The original Automation Server (Classic) can be set up to fully host (host server) and configure both MPX and RPC devices, but the Architectural Guidelines do not specify how many devices can be fully hosted. Resolution Full hosting of MPX, RPC is only supported and tested on AS-P, AS-B and Enterprise Server. This is confirmed in the MPX and RPC Specification Sheet. "MP-C/MP-V/RPC can either be used as a standalone BACnet/IP field controller or as part of an EcoStruxure BMS with a SmartX AS-P or AS-B server or an Enterprise Server as the parent server." MPX, RPC can be simply be BACnet hosted on an Automation Server Classic, but the use as parent or host server is not supported or tested.

Issue WorkPlace Tech will not recognize the Echelon U10 USB Lon Network Interface adapter. The “Loading Device Driver” is displayed but nothing happens after that. Environment WorkPlace Tech 5.8.x Cause LON1 port may have been previously assigned to another LON interface. Resolution 1. Make sure the Echelon Open LVD 4.0 is installed on PC. 2. Close WorkPlace Tech if open 3. Disconnect the Echelon Lon USB adapter from the PC. 4. Open Control Panel and open LonWorks Interfaces 5. Select View from the Menu and check “Show Detached Interfaces” 6. Highlight LON1 in the tree and click the “Remove” from the menu        - Click Yes in the “Confirm Removal” window to remove the detach device 7. While in same widow, reconnect the Echelon USB Lon Adapter to the PC        - The messages: “Installing device driver” will display in the system tray followed by “Echelon USB Network Interface Installed.        - The LON1 interface should now be displayed You can test the communication if you like Now open WorkPlace Tech and you should be able to discover the LON devices.  

Issue When SmartStruxure and TAC Vista is installed on the same PC, the license system for one of the products doesn't work properly and you get no license. Product Line EcoStruxure Building Operation, TAC Vista Environment Flexera license system Cause SmartStruxure and TAC Vista uses the same license system vendor and also the same vendor daemon. That causes a conflict, and a special configuration is needed. Resolution To move a TAC Vista license to the EcoStruxure Building Operation(EBO) license server See video:       Or follow the steps below: Disable TAC Vista's license server and host the TAC Vista licenses in the SBO license server. Stop and disable the service "TACLicenseServer". This is done through "services" (Start-->run-->services.msc) on the PC. Make sure the correct license setup is made for TAC Vista. Refer to No license after reboot when TAC Vista Server (TACOS) runs as a service for further explanation. Create a folder for the TAC Vista licenses as a subfolder in the SBO license server installation folder. Give it the name "licenses" and place all TAC Vista customer licenses here. Do not place demo licenses in this folder. Open the SBO license server web page (http://localhost:8888) preferably with Chrome or FireFox Click on "Administration" Sign in using "admin" as user name. If you have logged in before, use the password you have defined. If not, enter "admin" as password and create a password as indicated in step 6a and 6b. If it is the first time you log in, enter a new password and click "Save". If it is the first time you log in, now click "OK". Click on "Vendor Daemon Configuration" Click on "Administer" Click the field "License File or Directory" and enter the folder name "licenses" on a new line. Scroll down and click "Save" Restart the SBO license service (Building Operation 1.6 License Server) Additional notes If your TAC Vista license is locked to a dongle, you need to replace the SBO vendor daemon file (taclic.exe) with the on from the license server hotfix produced for TAC Vista 5.1.9. Please contact Product Support Services for assistance and refer to this article.

Issue How to set the IP address of a Xenta 5/7/9xx through serial communication. Product Line Satchwell MicroNet, TAC INET, TAC Vista Environment Xenta Servers Xenta 511, 527, 555, 701, 711, 721, 731, 913 Cause If the IP address of a Xenta 5/7/9xx is not known initially, then no configuration can be done through the IP interface. The IP address must be set through serial communication. Resolution IP setup for a Xenta server (Xenta 5/7/9xx) through serial communication for step-by-step instructions for this process.

Issue If the STR 350 plug-in is missing, then the STR 350/351 setup needs to be performed manually in NL220, LonMaker, TAC Vista Workstation, or TAC Menta. Product Line TAC Vista Environment TAC Vista 5.1.4, TAC Vista 5.1.5 Windows 7, Server 2008 Cause Not all plug-ins in the TAC ToolPack can run on Windows 7 or Windows 2008. Read details in TAC ToolPack plug-ins are not showing up. Resolution If the STR 350 plug-in is missing, then the STR 350/351 setup needs to be performed manually in NL220, LonMaker, TAC Vista Workstation, or TAC Menta. NL220 STR 350/351 setup steps are shown below: Use the STR 350 device template to create a new node on the channel. Note: the device template is located at C:\LonWorks\import\TAC\IO Modules (Default location) Double click on the STR 350/351 device and make necessary changes to any signal under “NVs” tab. TAC Workstation STR 350/351 setup steps are shown below: Expand the tree structure in the left panel. Select the desired signal to change in the right panel. If a STR 350/351 is connected to a programmable controller (Xenta 280/300/400), then the STR 350/351 can be added in the Menta file similar to an IO module. Setup steps are shown below: Under “Options/Device Specification” select “Add STR Module…" Under “Type” Select “STR350/351” and Under “Bit(s)”, choose the desired bit(s). Note: hover over each bit, there is a short description about the selected bit. If a STR 350/351 is connected to a Xenta Server (Xenta 7XX), then the STR 350/351 can be added in the Xbuilder project similar to an IO module. Setup steps are shown below: In Network panel,  under “LON", right click and select “Add IO Module->STR35X". Right click on the STR35X model just added, and select "Configure". A configuration pop up window will be displayed.  Make any desired changes. Note: Neuron ID can be manually typed in the Xbuilder or get from service pin in the Workstation. If choose to service pin, need to create and commission a LNS network in Workstation. Save and download the project. Below is a table of each bit in nciOption1 and nciOption2 and its brief description. nciOption1: Bit 0, 1: Fan type 00: No fan (Default) 10: On/Off fan 01: 2 speed fan 11: 3 speed fan Bit 2: Fan auto state 0: Not allowed (Default) 1: Allowed Bit 3: Fan off state 0: Not allowed (Default) 1: Allowed Bit 4: Fan speed 1 0: Not allowed (Default) 1: Allowed (On/Off fan type needs to be activated) Bit 5: Fan speed 2 0: Not allowed (Default) 1: Allowed (2 speed fan type needs to be activated) Bit 6: Fan speed 3 0: Not allowed (Default) 1: Allowed (3 speed fan type needs to be activated) Bit 7, 8 ,9: Not used   Bit 10: Temperature presentation 0: °C (Default) 1: °F Bit 11: Temp. normally displayed 0: Setpoint temperature (Default) 1: Room temperature Bit 12: Setpoint temp. presentation 0: Absolute temperature (Default) 1: Offset temperature Bit 13: Bypass button usage 0: Bypass (Default) 1: On/Off Bit 14: Not used   Bit 15: Supported protocols 0: Standard LonTalk protocol only 1: Standard LonTalk protocol and TAC proprietary protocol (Default) nciOption2: Bit 0, 1: Sunblind - Switch 1 00: On/Off (Default) 10: Up/Down 01: On/Off/Up/Down 11: Not used Bit 2, 3: Sunblind - Switch 2 00: On/Off (Default) 10: Up/Down 01: On/Off/Up/Down 11: Not used Bit 4: Light - Switch 1 0: Disable (Default) 1: Enable Bit 5: Light - Switch 2 0: Disable (Default) 1: Enable Bit 6, 7, 8: Local sensor 000: None (Default) 100: CO 2 010: RH 001: Occupancy Bit 9: CO 2 /RH value 0: Hidden (Default) 1: Display Bit 10-15: Not used  

Issue The ACCDataServices application is crashing on start up of CyberStation Product Line Andover Continuum Environment CyberStation Windows XP Cause Windows permissions issue Windows Firewall Configuration  Resolution Make sure when installing CyberStation the user has Local Admin rights to the computer Make sure Windows Firewall is turned off during the install Make sure all VirusScan software is turned off during the install. Check the event notifications and verify that none of them are set for the recipients to have pager, log, forward or any unused option which can create unnecessary traffic when using enhanced alarm delivery. To check if you are using enhanced alarm delivery Database Initialization > Server (or Stand Alone) > see check box for enhanced alarm delivery An example of possible unnecessary check box recipient options:  Check that each action in the event notification i.e. 'Display Graphic' has a corresponding object for the point alarming. If no object is selected it may cause accdataservices errors. Run acctrace and/or the Continuum error  log and wireshark to determine if there are errors. Cleaning up these issues can relieve the system and these errors. The Windows application/system logs and system.nfo/Belarc advisor can help gather info about the PC. See Top 10 Steps for Troubleshooting Cyberstation and webClient issues. If there is a 3rd party bacnet device, disable or unplug the device to see if the issue is related to the flooding of traffic into Continuum Liebert Sitelink- If you are on 1.93 and below, the Sitelink trendlogs could affect Continuum. Upgrade to 1.94 and disable trendlogs. Engineering is working on a hotfix for this issue. (Not released as of 11/29/12) Stand Alone Windows 7 system - A stand alone system can easily tax resources when extended logging, graphics, SQL Server, Cyber, etc. are all running on the same system. Eliminate any errors in the error log and disable certain functions to see if this helps. Consider a server class PC depending on what the system functions that are required by the site. Install Cyberstation 1.94 SP1 and related firmware updates as there are many fixes to address accdataservices.exe crashes (See Continuum 1.94 SP1 Service Pack to address accdataserices.exe crashes and other issues) Do not mix 1.94 and 1.94 SP1 Cyberstations on the same db, this could cause accdataservices crashes

Issue Xenta Server reports it is in FAILSAFE mode without shorting out terminals 9 and 10. After connecting via HyperTerminal, restarting and trying to reset the IP address, the screen continues to scroll back to dsh/> Xenta Server has gone offline and can not connect directly to it using Ethernet. The Run light is flashing Green on first start up but then reverts to red and the LON light also flashes red. During boot up it pauses and reports an error (via HyperTerminal) in loading the RAM disk.  IP Address is set to 172.22.1.5 and can not change it.  Not able to load any firmware into the device – error received. "Error: Could not create remote directory." Product Line Satchwell MicroNet, TAC INET, TAC Vista Environment Xenta Server 527, 511, 555 Xenta Server 701, 721, 731 Cause Unknown corruption of the Xenta Server hard drive / flash drive, possibly due to electrical noise. Resolution To attempt to recover this device, try to format the device’s flash drive. To achieve this you can follow these steps using HyperTerminal or an equivalent application: (For further assistance with connecting to Xenta Servers and HyperTerminal refer to Connecting a serial cable to a Xenta 5/7/9xx controller).   Login and type the command FORMAT.  (May require device to be placed physically into the fail-safe mode by shorting terminals 9 and 10). The format command can take up to 3 minutes to complete but you should see the confirmation through HyperTerminal while this is occurring. If you have placed the device into Fail-safe mode, remove the link on terminal 9 & 10. Restart the device, by either cycling the power or typing the command RESTART through HyperTerminal. Set the IP address and IP settings (command SETIP). Install the latest firmware. You can download the latest firmware from The Exchange Extranet; ensure that you use the correct version since there various versions for the Xenta Servers. Run the firmware download to the device. During the download you may receive an error regarding "Failure to get the hardware version from the target device…", select OK Continue the installation The download will then occur, it will take some time and may appear that the software is not responding but this is normal. Be patient and if you don’t receive any errors then all should be ok. The device should now restart, after a 1-2 minute window the “RUN” LED should be a solid green. If after following these procedures, the device is still not responding as expected please send into Repairs via your normal repair process.

Issue Active alarms are appear stuck in the alarm viewer for objects that are no longer in alarm.   Alarm notifications will not clear from Active Alarm View. How can obsolete alarms be removed from the Active Alarm View Product Line Andover Continuum Environment CyberStation WebClient Cause When a Return to Normal (RtoN) notification is reported by a controller, if Cyberstation is unable to receive the notification due to a loss of communication, the status of the alarm notification will not be updated and the alarm will continue to be displayed as though it were active even though the point alarm state is now inactive. Resolution Method 1 Disable the object and change it's value so that a new alarm is induced. Refresh the object editor until it indicates that the alarm state is active. Enable the object so that it returns to a normal value. If necessary, acknowledge the alarm so that it can be removed from the alarm list. Method 2 Backup the Continuum Database. Edit the object to confirm that it is no longer in an active alarm state. From the Root/ListView folder, open the Alarms_AllActive Listview. Locate the alarm entry associated with the object. Right click on the line and select Delete. Restart Cyberstation to update the Active Alarm View from the alarm log.

Issue As of Continuum version 1.82 the standalone Database Engine is SQL Express, which offers inbuilt backup and restore functionality via Microsoft SQL Server Management Studio (SSMS). What is the process for backing up and restoring Databases prior to 1.82? Product Line Andover Continuum Environment Standalone CyberStation v1.81 and below. Backup/Restore  Cause As of Continuum version 1.82 the standalone Database Engine is SQL Express. Prior to that it was MSDE. What is the procedure to backup/restore an MSDE database? Resolution Visit the Download Center for MSDE Database Utilities:  MSDE Database Utilities Move SQL DB to a different hard drive

Issue Controller loses data following power failure or mains noise (from transients or spikes). Product Line Andover Continuum Environment All CX, ACX, i2, bCX, b3 controllers Cause Controllers are exposed to operating conditions outside their operating envelope and tested limits. This can cause them to reset, go offline or lose data. In extreme circumstances, poor installation can take controllers outside their operating envelope and cause damage requiring a repair. Resolution If a controller is setup on a bench with a clean power supply and the correct grounding, you will be able to turn off/ on the power and the controller will warm start every time. This test will confirm the controller is operating correctly, not faulty and that the software settings are correctly set for warm starting. Also that the RAM backup battery is connected and operating. If site resets, lockups, loss of memory or other corruption are seen on a site, then here are some of the installation issues to consider: Grounding - All controllers require a clean low impedance earth to sink all of the noise and emission energy a controller may be exposed to. The noise protection circuitry within a controller is designed to dissipate this energy down to earth, if this path is not low impedance the energy can cause a controller to reset or even be damaged permanently. Shared Ground - The earth cable to the Controller should not be shared with any other equipment that is a high inductive or capacitive load, these can generate noise spikes back into the controller. This includes motors (pumps/ fans etc) lighting circuits (capacitive loads), inverters (high frequency noise). Induced emissions - The controller should not be installed near any equipment that may induce excessive radiated emissions into the unit, the radiated emissions from Motors, inverters, radio & microwave equipment, lighting circuits, power wiring can all produce radiated emissions that could exceed the specified limits of the Controllers. By fitting the controllers into earthed metal enclosures you can minimize the external emissions by effectively creating a Faraday cage protecting the controllers circuitry. Power feed - The power requirements for every controller is defined in its datasheet with the defined tolerance, taking the power levels outside these limits can cause incorrect operation. Power spikes - Surges or spikes in power feeds or connection I/O cabling can cause controllers to reset, lose data or even become damaged. Fitting varistors to the power supplies and across any output loads can minimize the impact on the controller, See What Varistors should be used?. Shared Supply - The power feed to a controller should never be shared with other equipment that can generate electrical noise. Never use the same supply to power both controllers and field equipment like valve/ damper actuators in BMS systems or magnetic door locks in Access control, both actuators and the solenoids in Mag locks can generate large back EMF pulses into the controllers that can cause resets or even damage.. Fitting power filters or an external UPS on the controller can protect it from spikes on power up/ down, it is however always best to remove the noise spikes at source, so fit filters the generators, motors, contactors etc. It is also possible for the above issues to cause Infinet networks to Reconfig as well as other networking problems. Note: All controllers are approved and tested to the defined limits for FCC and CE induced and radiated emissions as detailed in the datasheets, for a controller to fail, restart or lose data it must be exposed to levels exceeding these specifications. They are not however power equipment and cannot be exposed to the noise levels power and industrial controls equipment is designed to withstand.

Issue Is there a way to specify the priority that the system should use by default when writing to the value of BACnet objects in EcoStruxure Building Operation (EBO)? Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Automation Server Building Operation WorkStation BACnet Cause It may be necessary, especially in a legacy b3 environment, or third party BACnet network integration, to write by default to a priority other than 16 in the Command Priority stack. Resolution The default Command Priorities within a system used when writing to BACnet objects are governed by the Interface Manager in the ES.  These settings are then inherited to all AS. Command Priority 16 is used by default writing to the Value Property of a BACnet Object Command Priority 8 (Manual Operator) is used by default when Forcing the Value BACnet Object in EBO. Both defaults can be changed but care should but be taken here as any changes will ripple through the entire system and may have unforeseen consequences. Script programs created in a b3 will still use Command Priority 10 by default. It is still possible to write at any other priority in EBO by Binding directly to the desired command priority.

Issue Locate the Evaluation license for TAC Vista or EcoStruxure Building Operation Product Line EcoStruxure Building Operation, TAC Vista Environment TAC Vista EcoStruxure Building Operation Cause EBO 7.0 and later: Building Operation 7.0 introduces the Engineering license, which enables a system to run during the project phase without the need for commercial licenses or what has previously been referred to as demo licenses/evaluation licenses which have a short validity and require frequent updates and re-engineering.   EBO 2024 (6.0) and earlier: There is an evaluation license for EcoStruxure Building Operation valid 3 months.    TAC Vista: Starting September 1, 2025, the evaluation license will only be available upon request for Schneider Electric employees using the support@Schneider portal. Should an EcoXpert™ partner require an evaluation license, they must request this from their Schneider Electric contact. Resolution EBO 7.0 and later: Engineering licenses can be downloaded from the EcoStruxure Power & Building Software Companion during the project phase, and when the time comes to commission and hand over the project to commercial operation, the portal provides the ability to convert Engineering licenses to Commercial licenses by simply submitting a license purchase order. No replacement or re-engineering of the license is required thanks to this one step operation.   Engineering licenses have a validity of 6 months, after which it is possible to extend for another 6 months if the project timeline demands it.   *Note that Demo licenses are still available for WorkStation Pro, enabling a limited time operation of WorkStation Pro use. For full uninterrupted operation, please use a commercial WorkStation Pro license.   EBO 2024 (6.0) and earlier: Evaluation license files are available for licensed partners on the EcoXpert Extranet. Follow the link and search for "evaluation". You must first register using your business email (i.e. CustomerName@partnerdomain.com) address to gain access to these files. Note: You may use any email address to register and view content, but downloads will only be granted to approved partner domain names.   TAC Vista: Only be available upon request for Schneider Electric employees using the support@Schneider portal To request a TAC Vista evaluation license, follow the steps outlined below: Open a case on ”Digital Offer Sales & Provisioning App Request” - What is your request related to? > Digital Supply Chain – Request - Please Select the Environment > Production - Please select the Offer > TAC VISTA - Please enter the SESA ID… > The SESA ID of the Schneider employee creating the ticket - Please select the type of Request > Create - Please select the type of Create new request > Demo license creation - Please select your country > The country of the person creating the ticket - Please provide business justification > Reason why the license is needed When submitting the ticket as above, the ticket will be handled automatically, and an email will be sent to the user. Subsequently the ticket will be closed automatically.

Issue A BACnet devices can contain 1000's of objects, performing an upload on these devices can take upwards of 30 minutes to complete when only a few objects are required for integration. Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Automation Server Premium Cause Uploading all objects in a controller can take a lot of time and is often not required. Resolution From version 2.0 Open the device discovery view / BACnet - then Discover All. Once the Device is hosted, click on the device (in the Device Discovery window) and open the right-hand Object pane. Drag/drop the required Object into the hosted BACnet device Application folder. Alternatively, the Hardware folder can be used, this was the best method for some earlier versions Perform the BACnet discovery, then view the Hardware folder at /ServerName/System/Hardware/BACnet devices. Navigate to the required Device/Object, then Drag and drop the Device and Object as above.