Building Automation Knowledge Base

Issue Can not see bCX4040 in BACnet view following Find New BACnet Devices from the root. CyberStation and controller are located on the same subnet, no BBMD configuration is required. Environment CyberStation bCX4040 b4920 Cause Subnet mask mismatch between PC and bCX Subnet mask not property configured in controller or the PC Resolution Login to controller's configuration web page and set the subnet mask to the appropriate value for the network. Submit the changes and re-start the controller. If the mismatch is on the PC side, fix it in the network properties in windows control panel.

Issue What does it mean on an MNL-800 if both the top green LED (Transmit) and the Amber LED (Receive) are on continuously? Product Line TAC IA Series Environment MNL-50 MNL-100 MNL-200 MNL-800 MNL-V1R MNL-V2R MNL-V3R Cause LEDs indicate LON traffic on the trunk Resolution For an explanation of the Transmit (Green LED) and Receive (Red LED) see F-26724, MNL-800 Installation Instructions, Table 1 LED Indications: LED Operation Status Green ON Normally ON indicating controller is powered and not actively transmitting data on the LON. Flashes OFF Flashes OFF while actively transmitting data on the LON. Amber OFF Normally OFF unless actively receiving data from the LON. Flashes ON Flashes ON while actively receiving data from the LON. Red OFF  (Neuron - normal communications) indicates the Neuron is operating properly allowing normal communications to and from the HVAC application. OFF  (Neuron - Offline) Neuron responds to network management messages only. In this state, communication to and from the HVAC application is not possible. To correct, place the Neuron online by downloading an application using WP Tech or configure using a third party management tool. Blinking The service LED blinks at 0.5 Hz rate (1 second ON, 1 second OFF) to indicate that the Neuron is unconfigured (i.e. communications parameters not loaded). Corrective action: Configure the Neuron by downloading an application using the Work Place Technician's Tool or configure the neuron using a third party management tool. ON Indicates Neuron is not operating properly. Replace controller.  Heartbeat (Green LED) Blinking (Normal Operation) The heartbeat LED blinks at 0.5 second ON, 0.5 second OFF to indicate controller is operating properly. Wink Mode Wink mode provides a visual means for identifying the controller using WP Tech or third party management tool. During wink, the heartbeat LED blinks as follows: With revision 1.x firmware: 2 seconds ON, 0.5 seconds OFF; cycles five times for a total of 12.5 seconds of wink time. With revision 2.x (or later) firmware: 3 seconds ON, 1 second OFF; cycles three times for a total of 12 seconds wink time. Diagnostic Blink (RAM/ROM Failure) The heartbeat LED repeats a pattern of 2 quick flashes followed by pause. To correct, turn power OFF then ON. Replace controller if necessary. Diagnostic Blink (ROM Failure) The heartbeat LED repeats a pattern of three quick flashes followed by a pause. To correct, turn power OFF then ON. Replace controller if necessary. Diagnostic Blink  (RAM Failure) The heartbeat LED repeats a pattern of four quick flashes followed by a pause. To correct, turn power OFF then ON. Replace controller if necessary. OFF Indicates controller is not operating properly. Check power. Replace controller if necessary.      If the amber LED is blinking fast enough, it appears to be ON continuously, so it is receiving data at a high frequency. The other MNL devices on the same LON should all be behaving the same way, indicating a lot of LON traffic. Confirm with a LON protocol analyzer. If excessive LON communications traffic is suspected, see How can LON communications be throttled in MNL-800 controllers? for a method of throttling LON traffic.

Issue Getting error for Weather Server:  ERROR [19:32:28 06-Sep-11 EDT][http.proxy] Error resolving www.weather.gov java.net.UnknownHostException: www.weather.gov - Authoritative Answer Host not found    at java.net.InetAddress.lookupHostByName(InetAddress.java:369)    at java.net.InetAddress.getByName(InetAddress.java:221)    at javax.baja.naming.BIpHost.getInetAddress(BIpHost.java)    at javax.baja.net.BHttpProxyService.get(BHttpProxyService.java)    at javax.baja.net.HttpConnection.connect(HttpConnection.java)    at com.tridium.weather.nws.advisory.BNwsAdvisoryAlarmExt.getFeed(BNwsAdvisoryAlarmExt.java)    at com.tridium.weather.nws.advisory.BNwsAdvisoryAlarmExt.getFeed(BNwsAdvisoryAlarmExt.java)    at com.tridium.weather.nws.advisory.BNwsAdvisoryAlarmExt.getAdvisories(BNwsAdvisoryAlarmExt.java)    at com.tridium.weather.nws.BNwsWeatherProvider.updateReport(BNwsWeatherProvider.java)    at javax.baja.weather.BWeatherReport.doUpdateWeatherReport(BWeatherReport.java)    at auto.javax_baja_weather_BWeatherReport.invoke(AutoGenerated)    at com.tridium.sys.schema.ComponentSlotMap.invoke(ComponentSlotMap.java)    at com.tridium.sys.engine.EngineUtil.doInvoke(EngineUtil.java)    at javax.baja.sys.BComponent.doInvoke(BComponent.java)    at javax.baja.util.Invocation.run(Invocation.java)    at javax.baja.util.Worker.process(Worker.java)    at javax.baja.util.Worker$Processor.run(Worker.java)    at java.lang.Thread.run(Thread.java:823) WARNING [19:32:29 06-Sep-11 EDT][weather] Unable to load advisories for zone MIZ061 java.net.UnknownHostException: www.weather.gov - Authoritative Answer Host not found    at java.net.InetAddress.lookupHostByName(InetAddress.java:360)    at java.net.InetAddress.getByName(InetAddress.java:221)    at javax.baja.naming.BIpHost.getInetAddress(BIpHost.java)    at javax.baja.naming.BIpHost.openSocket(BIpHost.java)    at javax.baja.net.HttpConnection.connect(HttpConnection.java)    at com.tridium.weather.nws.advisory.BNwsAdvisoryAlarmExt.getFeed(BNwsAdvisoryAlarmExt.java)    at com.tridium.weather.nws.advisory.BNwsAdvisoryAlarmExt.getFeed(BNwsAdvisoryAlarmExt.java)    at com.tridium.weather.nws.advisory.BNwsAdvisoryAlarmExt.getAdvisories(BNwsAdvisoryAlarmExt.java)    at com.tridium.weather.nws.BNwsWeatherProvider.updateReport(BNwsWeatherProvider.java)    at javax.baja.weather.BWeatherReport.doUpdateWeatherReport(BWeatherReport.java)    at auto.javax_baja_weather_BWeatherReport.invoke(AutoGenerated)    at com.tridium.sys.schema.ComponentSlotMap.invoke(ComponentSlotMap.java)    at com.tridium.sys.engine.EngineUtil.doInvoke(EngineUtil.java)    at javax.baja.sys.BComponent.doInvoke(BComponent.java)    at javax.baja.util.Invocation.run(Invocation.java)    at javax.baja.util.Worker.process(Worker.java)    at javax.baja.util.Worker$Processor.run(Worker.java)    at java.lang.Thread.run(Thread.java:823) ERROR [19:32:29 06-Sep-11 EDT][http.proxy] Error resolving www.nws.noaa.gov java.net.UnknownHostException: www.nws.noaa.gov - Authoritative Answer Host not found    at java.net.InetAddress.lookupHostByName(InetAddress.java:369)    at java.net.InetAddress.getByName(InetAddress.java:221)    at javax.baja.naming.BIpHost.getInetAddress(BIpHost.java)    at javax.baja.net.BHttpProxyService.get(BHttpProxyService.java)    at javax.baja.net.HttpConnection.connect(HttpConnection.java)    at com.tridium.weather.nws.NwsCurrentReader.getFeed(NwsCurrentReader.java)    at com.tridium.weather.nws.NwsCurrentReader.getFeed(NwsCurrentReader.java)    at com.tridium.weather.nws.NwsCurrentReader.getCurrent(NwsCurrentReader.java)    at com.tridium.weather.nws.BNwsWeatherProvider.updateReport(BNwsWeatherProvider.java)    at javax.baja.weather.BWeatherReport.doUpdateWeatherReport(BWeatherReport.java)    at auto.javax_baja_weather_BWeatherReport.invoke(AutoGenerated)    at com.tridium.sys.schema.ComponentSlotMap.invoke(ComponentSlotMap.java)    at com.tridium.sys.engine.EngineUtil.doInvoke(EngineUtil.java)    at javax.baja.sys.BComponent.doInvoke(BComponent.java)    at javax.baja.util.Invocation.run(Invocation.java)    at javax.baja.util.Worker.process(Worker.java)    at javax.baja.util.Worker$Processor.run(Worker.java)    at java.lang.Thread.run(Thread.java:823) WARNING [19:32:30 06-Sep-11 EDT][weather] Updating current conditions failed for WeatherReport java.net.UnknownHostException: www.nws.noaa.gov - Authoritative Answer Host not found    at java.net.InetAddress.lookupHostByName(InetAddress.java:360)    at java.net.InetAddress.getByName(InetAddress.java:221)    at javax.baja.naming.BIpHost.getInetAddress(BIpHost.java)    at javax.baja.naming.BIpHost.openSocket(BIpHost.java)    at javax.baja.net.HttpConnection.connect(HttpConnection.java)    at com.tridium.weather.nws.NwsCurrentReader.getFeed(NwsCurrentReader.java)    at com.tridium.weather.nws.NwsCurrentReader.getFeed(NwsCurrentReader.java)    at com.tridium.weather.nws.NwsCurrentReader.getCurrent(NwsCurrentReader.java)    at com.tridium.weather.nws.BNwsWeatherProvider.updateReport(BNwsWeatherProvider.java)    at javax.baja.weather.BWeatherReport.doUpdateWeatherReport(BWeatherReport.java)    at auto.javax_baja_weather_BWeatherReport.invoke(AutoGenerated)    at com.tridium.sys.schema.ComponentSlotMap.invoke(ComponentSlotMap.java)    at com.tridium.sys.engine.EngineUtil.doInvoke(EngineUtil.java)    at javax.baja.sys.BComponent.doInvoke(BComponent.java)    at javax.baja.util.Invocation.run(Invocation.java)    at javax.baja.util.Worker.process(Worker.java)    at javax.baja.util.Worker$Processor.run(Worker.java)    at java.lang.Thread.run(Thread.java:823) Environment Niagara G3, Workbench all versions Cause No address entered for DNS or IP Address incorrectly entered. Resolution Configuration for the DNS is located under the ENC/ENS Platform.   Open the Platform Select TCP/IP Enter the IP address for the DNS in the DNSv4 Servers slot and save changes. The network administrator should be able to provide the correct DNS address.

Issue Vista 5.1 License Packages Product Line TAC Vista Environment Vista 5.1 Licensing Cause The TAC Vista software is modular and each function can be purchased separately. For convenience we have bundled modules into various packages: Standalone, Standard, Manager, Professional and Enterprise. Resolution The table below describes the contents of each licensing package. Product Packages Standalone Standard Manager Professional Enterprise Workstation X X X X X Graphics Editor OGC       X X Graphics Editor TGML       X X Report Generator     X X X OPC Tool           IPCL Editor           Central IPCL Editor           Database Generator           I/NET Integrated           I/NET Security           Menta 5.1       X X XBuilder 5.1       X X ZBuilder           Vista Server X 1 X X X X OPC Client           System 7           Webstation3         X 2 ScreenMate3           Limited server. Server-to-Server network and ability to be used with Webstation and ScreenMate is disabled. Three Client Access Licenses, CALs (000882711). See product datasheet for part. nos. for various Client Access Licenses, CALs.

Issue Running Server/Client on a system Environment I/Net Seven version 2.13 and above. Cause Server client on a system that is running on different versions and not working. Resolution For Server/Client to work on a system, I/Net has to be installed on all the PCs and they all must be the same version as well. The following steps needs to be followed to configure this correctly: The Host PC that will be acting as the Server must have the current database. Modify the active profile in the Configuration Editor In the WorkStation Options, set this to be Standalone On the other PCs, this would be set to Remote Client An editor will come up stating the "the database will be replaced" Click on the proceed button to connect to the Server. Once completed, the client PCs would now be looking at the Server

Issue Is a controller reload required when upgrading from v1.74 to v1.93 or 1.94 to 2.02? Environment CyberStation v1.74,1.93 1.94 and 2.02 NetControllers, Infinet controllers Cause We will be performing an upgrade on a site from v1.74 to v1.93. or  v1.94 to 2.02 Do we need to reload every network controller? Resolution In this case it is not a requirement of the CyberStation upgrade that dictates if a controller reload will be required. However, in order to keep the CyberStation and controller versions compatible, a flash upgrade of some controllers may be required. (Refer to Continuum Software and Firmware Compatibility Matrix)  The process of doing a flash upgrade usually requires a reload and is generally a good idea. There are some cases where a minor version upgrade (for only a bug fix, for example) in a controller with a valid flash backup will not require a reload because the controller will reload itself automatically from flash. Even if you think a reload is not required make sure you edit a few objects in the controller after the flash upgrade. If you get an error that the object cannot be found, reload the controller and then do a flash backup. Additionally, a planned "outage"  is a good opportunity to reload a controller that may not have been reloaded in a while. It would be better to know right after the upgrade if there is a problem, than to find out after you leave the site. The Infinet controllers typically do not need to be reloaded - but make sure you test a few infinet controller alarms on all upgraded network level controllers.  

Issue The STR-200 and STR-202 are the recommended replacement for TSS100WJ and S/STAT. Environment STR-200 STR-202 Xenta 102-AX 7728 MR-VAV TSS100WJ S/STAT Cause Obsolete parts Resolution STR200 replaces the TTS100WJ (Temperature Sensor Only, PN) STR202 replaces the S/STAT (Bypass button and Offset wheel) STR200-202 can be used with the 7728, MRs, and Xenta 102-AX controllers. STR200 . . . . . . . . . . . . . . . . . . . . . . . . 004603000 STR200-W (White) . . . . . . . . . . . . . . . . 004603010 STR202 . . . . . . . . . . . . . . . . . . . . . . . . 004603200 Full Datasheet containing additional information is located here.

Issue After starting up the SmartX Advanced Display for the the first time, the operator finds himself stuck in SmartXKiosk mode before having any chance to select a password/PIN code. Product Line EcoStruxure Building Operation Environment Advanced Display v1 Advanced Display v2 Cause SmartXKiosk has been selected as launcher. The first time the SmartX Advanced Display is booted up the operator is presented of a choice to use  SmartXKiosk or TouchWiz as launcher. If SmartXKiosk then is selected instead of TouchWiz the operator will enter SmartXKiosk without having set a password first. Resolution Request an unlock code (PIN) from your local support center, which will enable the operator to exit Kiosk Mode. Press the Home (Hardware) Button at the SmartX Advanced Display. This will enable you to choose launcher again. Make sure that "TouchWiz" is selected. Note: In the next release this will note be an issue, since you are forced to select "TouchWiz" at first use to proceed (if SmartXKiosk is selected, you will be prompted to choose again)

Issue When a Sigma data import is carried out, the following messages are displayed on the SBO ES computer. On the Sigma server computer, the Sigma server service has stopped. Product Line EcoStruxure Building Operation Environment Sigma 4.08 Building Operation Workstation Building Operation Enterprise Server Cause The Sigma database’s longtext file contains unsupported characters. Resolution Option 1: If Sigma longtext is no longer required: On the Sigma computer. 1)      Stop the Sigma server service. 2)      Delete the longtext.rec file from the Sigma Data folder (C:\Sigma\Data\longtext.rec). 3)      Start the Sigma server service. On the SBO computer Carry out the data import again. Option 2: If Sigma longtext is required: On the Sigma server computer. 1)      Start the Sigma server service. Open a Sigma client, either on the Sigma server computer or the SBO ES computer or other. 1)      Log into Sigma’s operator panel 2)      Go to the System Alarm manager 3)      Under the menu “Configure” select Longtext 4)      Open each longtext entry and remove the unsupported characters 5)      Add the longtext message your require. (You may find copies of the original longtext messages you can copy the text from, under “C:\Sigma\Data\Longtext” used by Sigma before the system was upgraded. On the SBO computer 6)      Carry out the data import again.   The data import should now complete.

Issue What needs to be changed in the Sigma configuration? Environment Sigma IP Address Moving Different network. Cause Are any changes required to the Sigma configuration, when a Sigma server is moved or the IP address is changed? Resolution Changes required when moving the Sigma server PC to another location or re-installing the Sigma server software onto another PC in a different location. Locate the PC in the new area and give it an appropriate IP address. Start the Sigma server and local client. Enter Sigma "System setup" and select "Networks and Devices" Select the zone that the server is in. In the "Networks" option, does the network already exist, if not then create it. In the "Servers" option select the Sigma server and select the correct network and IP Address. In the "Clients" option check that all clients are attached to the correct servers. In "Controller Items / Routesets" confirm that the routesets are correctly matched to the clients. Download the "Node Configuration" to all devices Download the Att.set and the Routeset.rec files to all controllers.

Issue Some SNVT's are not updating correctly. Environment Sigma IC IC3 LON SNVT's Cause LON Bindings are not correctly configured as a "Sigma" connection type. Resolution The IC-LON configuration process is explained fully in the "IC-Lon Configuration document attached HERE. Part of the above document deals with the use of the IC-Lon Plug-in. This Plug-in will create the "Sigma" connection type which is used by the IC-Lon. Below is a screen shot of this connection type. This connection type is selected "Unackd", the advanced settings are shown below. If the correct connection type is not used, then the bindings will not operate correctly.

Issue Unable to add PIN to Users in a new v4.2.243 or v4.2.244 Database / Site. Errors similar to below are seen when attempting to add a new PIN.   Fig. 1 - PIN does not meet complexity requirements Fig. 2 - Could not generate a unique 4 digit PIN Product Line EcoStruxure Security Expert Environment Security Expert version 4.2.243 , 4.2.244 Cause The default PIN settings are not be set when the Site is first created during installation of a new Security Expert Database. Resolution Go to Global > Sites and click Save on the newly created Site object to set the default PIN settings.

Issue What can the Boost relay (R2) be used for? Environment Boost Termination Day control Relay R2 Cause The plant continues to operate even when the temperature is greater than the Td setting. Resolution The SVT Optimiser has a primary function of performing and optimised timed start, this is achieved using a space temperature sensor to provide an indication of the buildings internal temperature The controllers secondary function will allow a "Boost Function" or "Day Control" of the plant. The controller output relay R2 is used for this function. Boost Function. Relay R2 contacts 5 - 4 make at the end of occupancy, ready for boost period. Relay R2 contacts 5 - 3 make at Occupancy start and provides a termination of the Boost period. For Boost Operation set the slide switch to position "A" as shown below.   Day control. Relay R2 contacts 5 - 4 make when the space temperature is above the (Td) setting. Relay R2 contacts 5 - 3 make when the space temperature is below the (Td) setting. To review the complete SVT data sheet, please chick HERE.

Issue Selecting the correct SE7000 Controller Model compatible with the user application Product Line EcoStruxure Building Operation, EcoStruxure Building Expert Environment • Building Operation Workstation • Building Operation Automation Server • SSL SE7000 Cause There are several different SE7000 series controllers to choose from and it is important to select the correct one for the application Resolution The online selection tool is available SE7000 Room Controller Selection

Issue Access Control Button not visible on the Toolbar. Environment All versions of I/Net Software. Cause The check box that enables access control in the configuration editor has been unchecked. Resolution To resolve this issue, the following steps needs to be followed: 1. Right Click on I/O Server, select the Configure link and modify the active configuration. 2. In the configuration editor, there is a radio button next to Enable Access Control. 3. Check this box, click on the Okay button, click on the make active button and close I/Net and I/O Server. 4. Restart I/Net and I/O server again, log in and the Access Button should be available now.

Issue Changing the Module ID after physically replacing a modules gives error "Incorrect response (or no response) from IO module" Product Line Andover Continuum Environment CyberStation CX9900 CX9940 CX9680 IOU Module Cause Controller's OMS database is out of sync with SQL database. Resolution To synchronize the OMS database with the SQL database:- Put CyberStation in offline edit mode. Edit the IOU Module object and enter the new Module ID. Save the object Return CyberStation to online edit mode. Perform a Send to controller, reloading the controller will sync the OMS db in the controller with the SQL database. Note the following: Make sure to use the option to reload attached objects but not attached controllers If IOUs go offline when sending to controller after doing this, manually get IOUs online, perform a send to database and send to controller. If a number of IOUs were replaced this process may need to be repeated several times until the send to controller works with no errors.

Issue Since the Cloud Plugin cannot perform search operations on EBO, Building Advisor can only estimate the number of forced points using the event log and, for EBO versions above 3.2.1, the server archive.  Product Line EcoStruxure Building Advisor Environment BMS Health Cause 1. Incomplete Event Log: The event log may be incomplete if the maximum capacity is reached in EBO (events are rolling). When a customer connects their system, some historical events may be missed. 2. High Event Production: If a customer's system generates events at a higher rate than BA can process (currently, BA can ingest 100,000 events every 6 hours), some events may be overlooked, especially if there are many noisy events. 3. Understanding of Events: BA can only recognize forced and unforced events. BA will lose track of that point if an object's absolute path is updated or deleted instead of being unforced. 4. External Tools: BA cannot track it if an external tool forces a point without creating a corresponding forced/unforced event in EBO.   Limitations with EBO Versions 3.2.1 or higher: Building Advisor can resolve issues for each server by retrieving snapshots from the server archive. This method can address the abovementioned issues, except for point number 4. Additionally, Bacnet points forced via commands are unavailable in the server archive, meaning we cannot retrieve those values through the Cloud Plugin. Resolution Check the EBO Version, and If the customer's system is older than version 3.2.1, advise them to upgrade. Verify Server Archive, ensure the issue pertains to Bacnet points, and proceed to the next step. Ensure all servers associated with the mismatched forced items have an updated server archive. This will enable the Building Advisor (BA) to obtain the correct snapshots from the system. You can check this in the building's BA connectivity tab.  If the servers are updated, proceed to the next step. If they are not, ensure that server backups are created periodically. You can check this in the BA architecture tab under the backup section.  If a newer backup is present compared to the "Last Upload" in the server archive table, attempt to send it again. Refer to the instructions on how to send a new backup at the end of the file. If there isn’t a newer backup, create one and send it. Important: Please note that it may take one to two days for the Building Advisor (BA) to reflect the updates. If the object exists in EBO, retrieve the events from the relevant branch and filter for force-type events.  If the last event is unforced and BA is showing as forced, Force it and then unforce it one time. If it was a Bacnet point, try to force it from the basic tab.  Note: If you have multiple points, you can search using the appropriate criteria and perform all the force/unforce operations simultaneously.  If the object no longer exists in the path, you can create a replica of the object in the same path and perform the force/unforce operation. Ensure that events are created for your actions (see Step 5). If the point does not exist for manual override and you cannot set a new device in the path, please open a PSS case. Send a new backup using the following process: Navigate to ~/System/Modules/CloudPlugIn/Statistics/Services Add the Service type and Server name columns in the list view Locate the Service Type of SystemDiscovery, multi-select the server(s) affected, right-click, and select Execute task now If the issue is unresolved two days after uploading the updated SystemDiscovery files, please open a PSS case.

Issue When is an "additional 500 points" license required for an Enterprise Server? Product Line TAC IA Series Environment I/A Series R2 IA-ENT-1 Enterprise Server licensed with the IA-DRV-OSD Open Systems Device driver license Cause The basic Enterprise Server license does not include any external point driver capabilities.   Adding the IA-DRV-OSD allows the enterprise server to communicate with up to 25 points of each type, BACnet, OPC, SNMP and ModBus, all using IP communications. Resolution An Enterprise Server can be licensed to directly communicate with  BACnet, OPC, MODbus and SNMP points by adding the IA-DRV-OSD license and will support communication with up to 25 points of each specific type of points. For each additional block of 500 points of a specific type, you need to purchase an additional points license, IA-BAC-500, IA-OPC-500, IA-MOD-500 or IA-SNMP-500.  Here is an example of how these licenses are used.  The Enterprise Server needs to communicate directly with 1250 BACnet IP points and 60 SNMP points.  The following licenses will be required: IA-ENT-1 -- Enterprise server license IA-DRV-OSD -- Open System Driver for direct point communication, includes 25 points each of BACnet, SNMP, OPC and ModBus. IA-SNMP-500 -- allows ES to communicate with the 60 SNMP points, technically allowing communications with a total of 525 SNMP points (25 points included with IA-ENT-1 and 500 with IA-SNMP-500). IA-BAC-500 -- allows the ES to communicate with an additional 500 BACnet points bringing the total to 525 BACnet points IA-BAC-500 -- this second IA-BAC-500 license will allow the ES to communicate with the additional 500 BACnet points, bringing the total allowable BACnet point count to 1025 points IA-BAC-500 -- this third IA-BAC-500 license will allow the ES to communicate with the required additional 225 BACnet points, actually bringing the total allowable BACnet point count to 1525 points. NOTE: On most computers an IA-ENT-1 with the Open System Driver is capable of supporting a maximum of 4000 external points regardless of the number of points licensed in any one communication type.

Issue CyberStation is unable to connect to the database. ODBC test also fails when testing the connection to the database. Product Line Andover Continuum Environment CyberStation SQL server SQL management studio Cause SQL server not on UPS. Server shut down due to a power failure. Looking at the ContinuumDB using the SQL Management Studio shows the database has been marked as suspect.  ContinuumDB (SUSPECT) The database may be marked suspect for the following reasons System Issues Transaction Log File is Missing SQL Server Crash Database Files are inaccessible SQL Server Database Operation Failures Due to Improper shut down of SQL Server System (as mentioned above) Due to Sudden Power Outage Low Disk Space Issues Hardware Failure Resolution The database may have been damaged by the ungracious shutdown. The restore option is grayed out and must first be re-enabled before a restore operation can be allowed. How to recover a database in suspect mode Clear the suspect mode of the database using sp_resetstatus DatabaseName. This will clear the suspect flag and make the database available online. The SQL Server must be stopped and re-started. Change the database status to Emergency using the following command. ALTER DATABASE DatabaseName SET EMERGENCY; Restrict database to single user by changing the access mode as mentioned below ALTER DATABASE DatabaseName SET SINGLE_USER; If the restore option is now enabled skip step 4 Run the CHECKDB command with “REPAIR_ALLOW_DATA_LOSS” option. This option should be tried as the last option as it always behaves the way it is named. We are not sure of what data it removes. DBCC CHECKDB (DatabaseName, REPAIR_ALLOW_DATA_LOSS) WITH NO_INFOMSGS, ALL_ERRORMSGS If the repair operation is successful the database is now usable but if a recent backup is available it is strongly recommended to restore the database. Restore the most recent backup of the Continuum database. Set the ContinuumDB owner using the query SP_ChangeDBOwner 'Andover97'  

Warning Electrostatic Discharge Required: Always discharge static electricity from your person by touching metal prior to handling any hardware. Failure to do so may result in damage to devices. Issue SmartX SpaceLogic/EasyLogic device is offline, inspection of the device's status LED reveals a solid red pattern instead of the normal solid green.   Product Line EcoStruxure Building Operation Environment SmartX SpaceLogic Controller SmartX EasyLogic Controller Cause A solid red status LED indicates the application can't be launched, typically there could be two reasons as the root cause of this situation: The application has become corrupted, this happens very rarely. Application keeps crashing on startup. To prevent an infinite startup->crash->startup loop, the firmware in the SmartX SpaceLogic/EasyLogic devices implement a feature known as the application startup retry counter, if the application has crashed multiple times, never running for longer than an internally defined time (typically 10 minutes), the boot applet will stop all attempts to launch the application. Resolution We can attempt to recover the device by performing the following steps: Cycle power to the device. Cold start the device by holding down the reset button for more than 5 seconds but less than 9 If the controller starts up and shows a normal status LED (solid green), immediately start  a device upgrade firmware operation, the goal is to get the uprev operation going before the application crashes again.