Building Automation Knowledge Base

Issue How and when are Modbus points polled? Product Line EcoStruxure Building Operation Environment Building Operations Enterprise Server Building Operation Automation Server Cause Need to understand the Modbus poll mechanism Resolution Consult the 'Modbus Deep Technical Reference' chapter of EcoStruxure Technical Reference Guide Or use WebHelp to find information on the Modbus Poll Manager, which manages all polling of the points/data and devices, and the Poll List which contains all the current subscriptions (eg. data being referenced within Programs, Listviews, Graphics, Logging, etc) These mechanisms isolate the Modbus Polling from programs and graphics. Note: For each network, the poll manager operates with a poll list and a poll task. If a Modbus Object value is only required for logging purposes, then the  "Requested poll interval" is set to a high number (typically 2,147,483,647 ms) This means the object values are not currently being polled. When the time arrives for the log value to be collected, the "Requested poll interval" is set to 1000ms, until the value is collected, at which point it reverts to this higher number.

Issue Connecting a serial cable to a Xenta 5/7/9xx controller Product Line Satchwell MicroNet, TAC INET, TAC Vista Environment Xenta Servers Xenta 511, 527, 555, 701, 711, 721, 731, 913 Cause Xenta Servers have a service portal for use with HyperTerminal with a serial connection to the RS-232B port. Resolution Connect a serial cable, Programming Serial Kit, part no. 0-073-0920-0, between the PC and the RS232 port B on the TAC Xenta.  For more information about the cable see Cable Guide OFL-3972. Go to Start/All Programs/Accessories/Communications/HyperTerminal, and open the HyperTerminal. In Connection Description Windows, type any name you like in the Name box. Click OK. In the Connect to window, choose the correct COM port that the RS-232 cable is using. If you do not know which COM port it is using. Go to your computer device manager. (Right click on “My computer” icon, and choose “Manage”. Then under “System Tools”, choose “Device Manager”. Find “Ports (COM & LPT)” and expend it Find the COM port number that is used by the RS-232 cable. Click OK. In the COM Properties window, type 9600 for “Bits per second”, 8 for “Data bits”, “Parity” is None, “Stop bits” is 1, and “Flow control” is None. Click OK. Options: you can save this setting for future use. Click on File Menu and Save. Press ENTER to activate the command prompt. Default username and password is both “root”. Type “root” and press ENTER for both the username and password. Type “setip” and press ENTER. NOTE: Product support has also witnessed strange behavior with serial connections when certain laptops were not plugged into a power source or the Xenta Server was not grounded. If connection problems persist after the connection setting above are verified, make sure the Hyperterminal PC is plugged into a 120 vac power source.

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

Issue SmartStruxure integration with BMS, CRM, SQL, SCADA, PLC, HMI, TouchPanels, Citrix, or UNIX types of systems Product Line EcoStruxure Building Operation Environment SmartStruxure Site Cause Can SmartStruxure integrate or be used with other BMS, CRM, SQL, SCADA, PLC, HMI, TouchPanels, Citrix, or UNIX types of systems? Resolution Integration and use with third party systems is sometimes possible with SmartStruxure. The question is how much is the third party system willing to integrate or be used with SmartStruxure? OnQ, which is a proprietary CRM or Contact Resource Management built by the Hilton company and deployed to more than 2,100 hotels worldwide, is using the same communication protocol than Micros Fidelio/Opera so you can use a Bacnet to Fidelio gateway. Fingi Operational Services(FOS) All features of the Fingi Mobile Platform operate from within FOS server. There has not been an integration with FOS for an example. We have several references with these systems (Hilton Manchester, Hilton Copenhagen, Hilton America, ...) - some information are in the Solution Toolbox/Hotel under BMS to PMS integration. Some gateway examples are available: Hotels Gateway - Lonbox PFG4000 is a Fidelio Lonworks® hotel booking gateway The Lonbox PFG4000 Users Guide IntesisBox BACnet gateway catalogue - designed to allow supervision and bidirectional control of all the parameters and functionality of systems and equipment with KNX, ModBus, LonWorks and Fidelio systems from BACnet/IP networks IntesisBox BACnet Server – Fidelio IP - Datasheet Citrix - Building Operation is not Citrix verified, nor has it been put through the process of Citrix Ready. The Building Management WorkStation and WebStation have not been tested on a Citrix platform. One solution would be to inquire through your local sales/marketing channel to see if this is something they want to pursue with the business case which has been put together. Integration is a proposed TVDA for 2013 - to be confirmed depending on resources on StruxureLab.

Issue Send an SMS text message when an alarm occurs. Product Line EcoStruxure Building Operation Environment Alarming SMS Text Cause Sending an SMS Text message in response to an alarm condition will allow the responsible personnel to react immediately, even if they are not currently at the workstation. Resolution EcoStruxure Building Operation does not support direct SMS texting. One workaround is to use an Email to SMS Test service provider that handles conversion of emails to SMS, as emails are easily created in EcoStruxure Building Operation.   If direct SMS functionality is required there are work arounds with 3rd party programs such as SysManSMS via file output options (see Using Sysman alert server with StruxureWare Building Operation). Note that this third party products such as this are not supported or tested by Schneider Electric.

Issue Activation of the Security Expert SSN with a new installation of the client software, software extensions (e.g. SX-VIM, SX-DOR-50) and integration licenses (e.g. SX-NVR, SX-CAM-10) need to be completed manually because there is no Interne access. Product Line EcoStruxure Security Expert Environment Licensing Cause The computer which the Security Expert client is installed on, does not have Internet access to use the 'Automatic License Update' method to activate the license. The manual method must be used to register and obtain the new license. Resolution In the Security Expert client go to About | License | information make a note of your system's SSN In the Security Expert client go to About | License | License Update and select Generate a License Request File for this System Copy the 'ICT_LicenceRequest.req' license request file produced onto a machine that has Internet access. Navigate to https://se.ict.co/license/ and enter your details on this web page. Enter the SSN for your system Upload the 'ICT_LicenceRequest.req' license request file generated previously and Submit. You should then be able to download a 'Security Expert YJWB...............O4PJ5W License.lic' file. Return to your offline Security Expert Client and go to About | License | License Update , Select Browse for your Downloaded License file Select the 'Security Expert YJWB...............O4PJ5W License.lic' file downloaded previously. Once the license update is complete shut down the client and restart the services   Support for manual activation: v4.2.194 - Manual activation is supported. v4.2.216 - Manual license activation's are no longer supported and an Internet connection is required on the Security Expert installation to be able to perform a new activation or update a license. v4.2.243 - Manual activation is supported. v4.3.x - Manual activation is supported.

Issue Documentation supplied with new UNC, ENC, or Jace 8000 was discarded.  Is there a way to determine the default, the factory-defined IP address, for the Ethernet port on the controller? Product Line TAC IA Series Environment I/A Series (Niagara) R2 UNC I/A Series (Niagara) G3 ENC Niagara N4 or G3 Jace 8000 Cause Lost or discarded document, shipped with the controller, that contained the configured IP address. Resolution The default Ethernet IP address for an I/A Series (Niagara) UNC or ENC is based on the serial number and type of device. For a UNC or ENC, the default address is 192.168.1.14X where X is the last digit of the device serial number.  The default serial number is found on a sticker on the controller circuit board.  This sticker has the full model number, date code, and the serial number of the controller.  The serial number is preceded with S/N:.The subnet mask is 255.255.255.0 in all UNCs, ENCs, and Jace 8000 The default address base address (192.168.1.140) is the same for all UNC-410, UNC-510, UNC-520, ENC-410, and ENC-520 controllers. The default IP address of a Jace 8000 for PRI (LAN1) is 192.168.1.140.  SEC (LAN2) is by default disabled.

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

Issue Instructions are needed to configure the new SMTP configuration. Product Line Andover Continuum Environment Continuum Non-Microsoft Exchange/Outlook SMTP Email Cause Configuration for the SMTP Configuration for email alarming in Continuum 2.00 through 2.03 Resolution In Cyberstation 2.0 and above, you no longer need Microsoft Outlook and Exchange to send email alarm notifications. Other SMTP servers can be used on the network and other email clients can be used also to send email alarm notifications directly to an intended recipient. Note: Public SMTP servers such as Gmail SMTP and Yahoo SMTP do not currently work with this solution as they require SSL or certain unsupported port combinations. The connections these servers establish cause connection issues within the SMTP application. Private SMTP (In-house) servers can be set up and used.   Steps to Configure SMTP Email Alarming   Open and Event Notification Navigate to the Actions Tab Select which events to receive email alarms Select the Delivery Tab Click the Add Recipient button to open the recipient configuration Browse for the recipient Cyberstation by click the ellipsis Select the recipient Cyberstation Select the SMTP Configuration button in the Recipient Configuration window Fill in the Server Configuration fields in the SMTP Configuration window Specify the SMTP Server address, port and login information Fill in the Email Configuration Specify the sender's email address - this is the email address the email will be sent from and it is also the email address that failed emails will be sent to    Type in a Subject line if needed or the default Continuum email subject line will be used Alarm Option Settings - Fill in the RetryCount and Retry Time fields  Retry Count - once you pass this value the email is dropped. The maximum Retry Count is 10  Retry Time -  field is in minutes. The maximum is 1440 minutes (24 hours) Adding an email address to the recipient list Click the Display Master List to open the SMTP Master Email Configuration Dialog Place a check in the check box to add an email address from the existing Master List to the Event Notification's recipient list and then click OK Adding or deleting email addresses from the Master Email list Open the SMTPMasterEmail Event Notification in the templates folder In the opened SMTPMasterEmail Event Notification click the Display Master List button Click the Add Recipient or Delete Recipient button depending on what is needed After selecting Add Recipient supply the email address in the recipient field and click Add Recipient After selecting Delete Recipient, select the address to highlight it and then click the Delete Recipient button. Multiple Selection is supported To deliver email notifications to the added email address, select the check box next to it Testing to ensure email address recipients receive emails Select the address you wish to test and click the Test Selected button Successful email to SMTP Server test will display a pop-up Failed email to SMTP server test will display a pop-up to the Sender's email address Final address configuration Recipients Configuration Options Place a checkmark next to the option needed Ex. Primary or Backup  SMTP Email A checkmark next to Repeat. Repeat will function as if it were an Outlook email alarm and send until the alarm is acknowledged. Known issues: In order for BACnet controllers to use the new SMTP feature, the following hotfix from the following link is needed.  CyberStation v2.00 (Only) SMTP Emailing & BACnet Alarms - Hotfix 2.03 contains the hotfix listed above   For additional information, see the Cyberstation Help, search for SMTP.

Issue A warning banner is displayed at the top of the Workstation window that states "A license violation has been detected." even though a valid evaluation license has been activated on the machine or site. The user will also find another warning message on the LicenseManager screen, under the System folder, that provides greater detail. This message will state specifically what is missing, for example "An additional X automation server license(s) are required. Please purchase the required licenses." Product Line EcoStruxure Building Operation Environment EBO Enterprise Server 2.X and newer EBO Workstation 2.x and newer Cause The new scalable licensing structure established in version 2.0 requires licenses for each automation server device (and field devices if the system is a new database). The evaluation (demo) license will account for the required licenses as long as it is valid but sometimes can be stuck in a state where it has not been validated.  Resolution In the majority of situations, simply rebooting or performing a warm start of the Enterprise Server will clear this warning as long as there is a valid evaluation (temporary) license hosted in the license administrator the ES is referencing. Troubleshooting Steps: Restart the Enterprise Server. Restart the License Server (if on a different machine as the ES). If required, restart the ES again. Check for any errors in the License Server and verify that the Vendor Daemon is up and running. See Unable to log into WorkStation due to license error codes -12, -15, -18 or -97 for more details around this troubleshooting step. If these steps have not resolved the issue, then open a support case with your local country support organization.  For more information about the enforcement of licenses see the EcoStruxure Building Management WebHelp article, Licensing Enforcement. 

Issue Need to configure SMTP settings to use a Google SMTP server Product Line EcoStruxure Building Operation Environment Building Operation Workstation Cause There is no SMTP settings configured by default Resolution Note: As of May 30, 2022 please also consult Less secure apps & your Google Account 

Issue Why do controllers go into bootloader mode? Product Line Andover Continuum Environment Bootloader NC2 BCX CX99xx CX96xx i2 b3 Cause Continuum controller are placed into bootloader mode if they repeatedly hit a firmware level exception. An exception is when the controller tries to do something that cannot be done.  Some examples of an exception are... A controller tries to read from memory that it cannot read from. A controller attempts write to memory that cannot be written to. On startup, flash generation controllers load the application from flash RAM.When they hit an exception, older, non-flashable controllers would simply clear the application software from ram, power up and wait for the software to be loaded from the front end.  If there is a bad application there needs to be a means by which a user can intervene before the application is loaded so that the controller firmware can be reloaded or upgraded.  When a flashable controller hits more than three exceptions within a ten minute time period the controller is placed into bootloader mode intentionally. Resolution When a controller repeatedly goes into bootloader mode it is time to take a close look at environment which might be driving the controller to hit exceptions A controller usually goes into bootloader mode due to environmental issues such as Heavy ARP traffic Controller grounding Controller power issues Problems with the communication bus. A controller that repeatedly hits exceptions is placed in bootloader mode by design.  Flashing a controllers firmware is the only way to get a controller out of bootloader mode. 

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. If the device is new out of the box, or has attempted recovery after a format command, please see Default IP address following Xenta Server "format" command is different than from factory for the known default IP addressing. Resolution Preparation: You need to have an RS-232 serial cable (TAC Xenta Programming Serial Kit 0-073-0920-0). Plug the RS-232 cable in to the RS-232 B port. The RS-232 B port is the second left port at the front. Then connect the other end to the computer. Configuration steps: Go to Start > All Programs > Accessories > Communications > HyperTerminal, and open the HyperTerminal. In Connection Description Windows, type any name you like in the Name box. Click OK. In the Connect to window, choose the correct COM port that the RS-232 cable is using. If you do not know which COM port it is using. Go to your computer device manager. (Right click on “My computer” icon, and choose “Manage”. Then under “System Tools”, choose “Device Manager”. Find “Ports (COM & LPT)” and expend it Find the COM port number that is used by the RS-232 cable. Click OK. In the COM Properties window, type 9600 for “Bits per second”, 8 for “Data bits”, “Parity” is None, “Stop bits” is 1, and “Flow control” is None. Click OK. Options: you can save this setting for future use. Click on File Menu and Save. Press ENTER to activate the command prompt. Default username and password is both “root”. Type “root” and press ENTER for both the username and password. Type “setip” and press ENTER. Type the appropriate information for DHCP, IP-address, Subnet mask, Default gateway, DNS, Website name, Domain name, and Host name. Type “yes” for “Do you want to restart the IP interface”. Quit HyperTerminal when the restart is finished. See [Video] Setting the IP address of a Xenta 5/7/9xx through serial communication to watch a video of this process.

Issue Solid red light Blinking red light Blinking green light Product Line TAC Vista Environment Xenta Programmable Controllers Xenta 280, 281, 282, 283, 300, 301, 302, 401, 401:B Cause The indicator lights on the face of the Xenta controllers can help explain the state of the controller with different actions.  Resolution There are two LED indicators – one red and one green on the Xenta programmable controllers.   The red service diode is primarily an error indication. It also lights up if the Service pin is activated. A solid red light usually indicates that the hardware has failed.  Please see a few simple steps to deactivate the solid red light below. Use a reset dongle to wipe the controller then reinstall the firmware and menta program. If the controller is the group master you might try to assign a different controller to group master.  This method has not been proven but has worked before during internal testing. NOTE: The hardware may need to be replaced if the solid red light continues after these steps. If the red indicator light is blinking once per second this will indicate a non-configured node. If the controller has been commissioned you might try to decommission the controller and try again. If the red indicator light is off this would indicate that it has been commissioned and added properly to the network.  You should not see the red indicator light if the controller is working properly. The green status diode blinks once per second to indicate that the program is running properly.

Issue BACnet COV subscription system Product Line EcoStruxure Building Operation Environment BACnet Settings COV subscriptions v1.7 and earlier Cause A site will have a problem with the amount of traffic because of misconfigured COV Increments. The problem is that Building Operation, the  ES and AS resubscribes to values every 10 seconds and one by one. So for example: hh:mm:ss 00:00:00 Value1 00:00:10 Value2 00:00:20 Value3 00:00:30 Value4 ... 05:00:00 Value1800 If you have more than 1800 subscriptions the ES or AS is not able to do all subscriptions in 5 hours.   5 hours is used because Building Operation subscribes to the values with a lifetime of 5 hours.   Resolution BACnet COV subscription system is not influenced by the requested transfer rate in the edit bindings system (Subscriptions using BACnet). That is used in the case where the external device does not support COV, and read-property must be used instead. The design in 1.4 and 1.5 simply did not anticipate such large numbers of COV subscriptions. Workaround: 1.Exit Workstation 2. Stop the Enterprise Server Edit using notepad the server.properties file located in "C:\Program Files\Schneider Electric StruxureWare\Building Operation 1.x\Enterprise Server\etc\ Find at the bottom: # Set GenericConsume communication defaults Add the two following lines: NspServer.BACnetPlugIn.COVSubscriptionLifetime entry = 28800 NspServer.BACnetPlugIn.COVTimerPeriod entry = 5 Save your changes and close the server.properties file. This changes the default values from 5 hours to 8 hours and 10 seconds to 5 seconds. NOTE From version 1.8 the BACnet Interface manager (/Server 1/System/Interface Manager/BACnet) provides access to these settings (COV subscription lifetime (default 8 hours) and Server COV renew rate(default 5 seconds)) The settings will be controlled via the Enterprise Server if connected.

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 SQL Database is full, or the partition the SQL is installed is full Product Line EcoStruxure Building Operation Environment Building Operation Report Server Cause If a site is using SQL Express 2008, the limit is 10 GB. If using the full version(s), it is unlimited. If the database or the partition where the Reports Server resides is full, here are some steps to reduce the SQL table volume and offer a short-term solution. Resolution Before continuing, make sure there is a good backup of the database. Using SQL Server Management Studio, highlight the StruxureWareReportsDB and select New Query Use the following Script in that Query: SELECT t.NAME AS TableName, s.Name AS SchemaName, p.rows AS RowCounts, SUM(a.total_pages) * 8 AS TotalSpaceKB, SUM(a.used_pages) * 8 AS UsedSpaceKB, (SUM(a.total_pages) - SUM(a.used_pages)) * 8 AS UnusedSpaceKB FROM sys.tables t INNER JOIN sys.indexes i ON t.OBJECT_ID = i.object_id INNER JOIN sys.partitions p ON i.object_id = p.OBJECT_ID AND i.index_id = p.index_id INNER JOIN sys.allocation_units a ON p.partition_id = a.container_id LEFT OUTER JOIN sys.schemas s ON t.schema_id = s.schema_id WHERE t.NAME NOT LIKE 'dt%' AND t.is_ms_shipped = 0 AND i.OBJECT_ID > 255 GROUP BY t.Name, s.Name, p.Rows ORDER BY t.Name Select Execute to run that Query as shown in the screen capture below: The Results show each of the tables and the size of those tables as shown in the screen capture below: Purely for example purposes, a script to reduce the number of Events would be delete from tbEvents where DATEDIFF(day, datetimestamp, getdate()) > 180 To gain back the space after deleting rows, right-click on StruxureWareReportsdb > Tasks > Shrink > Database

Issue How to decode BACnet errors when they are encountered in the following products. Product Line EcoStruxure Building Operation, Andover Continuum, TAC IA Series Environment EBO Error Log Tool Continuum bCX4040 (BACnet) Continuum b3s Building Operation Multi-purpose Controller (MPC/V) Building Operation Room Controller (RPC/V) Building Operation IP-IO EBO Trace and System logs Cause Documentation is unavailable for these errors when reviewing log files against any captures.  Resolution The error in log files is composed of two fields, BACnetErrorClass and BACnetErrorCode. The BACnet Error Class (BEC) field is made of the high 16 bits and the BACnet Error Code (BE) of the low 16 bits.  0x800 indicates the error class and error code are in Hexidecimal format. Error Class 0x8001, when remove 0x800, 1 decodes to Object Error Code 001f decodes to Unknown Object Therefore, the error code is Object_Unknown Object, where the device indicates it has no knowledge of the object, either it does not exist or the device does not have the expected program/database installed. For b3, it could be memory was wiped on power failure and needs to be reloaded. It could mean the expected application needs to be downloaded for other devices.   The following are a subset of BACnet errors defined in the specification. If you have questions or encounter ones not listed, please contact Product Support Services.   Error Class List High 16 bits of Error. See BACnet spec clause 18. May not include 0x8000. (Example: could be 0x5002B instead of 0x8005002B for COV subscription failed) Error Class Hex(0x800) Dec Notes device 0 0   object 1 1   property 2 2   resources 3 3   security 4 4   services 5 5   vt 6 6   proprietary     64 is the first available code for proprietary error classes client 7FFD   0x7FFD0000 Reject 7FFE   0x7FFE0000 (error code is BACnetReject) Abort 7FFF   0x7FFF0000 (error code is BACnetAbort)   Error Code List Low 16 bits of Error. See BACnet spec clause 18. Error Code Hex (0x) Dec other 0 0 authentication_failed 1 1 configuration_in_progress 2 2 device_busy 3 3 dynamic_creation_not_supported 4 4 file_access_denied 5 5 incompatible_security_levels 6 6 inconsistent_parameters 7 7 inconsistent_selection_criterion 8 8 invalid_data_type 9 9 invalid_file_access_method A 10 invalid_file_start_position B 11 invalid_operator_name C 12 invalid_parameter_data_type D 13 invalid_time_stamp E 14 key_generation_error F 15 missing_required_parameter 10 16 no_objects_of_specified_type 11 17 no_space_for_object 12 18 no_space_to_add_list_element 13 19 no_space_to_write_property 14 20 no_vt_sessions_available 15 21 property_is_not_a_list 16 22 object_deletion_not_permitted 17 23 object_identifier_already_exists 18 24 operational_problem 19 25 password_failure 1A 26 read_access_denied 1B 27 security_not_supported 1C 28 service_request_denied 1D 29 timeout 1E 30 unknown_object 1F 31 unknown_property 20 32 removed 21 33 unknown_vt_class 22 34 unknown_vt_session 23 35 unsupported_object_type 24 36 value_out_of_range 25 37 vt_session_already_closed 26 38 vt_session_termination_failure 27 39 write_access_denied 28 40 character_set_not_supported 29 41 invalid_array_index 2A 42 cov_subscription_failed 2B 43 not_cov_property 2C 44 optional_functionality_not_supported 2D 45 invalid_configuration_data 2E 46 datatype_not_supported 2F 47 duplicate_name 30 48 duplicate_object_id 31 49 property_is_not_an_array 32 50   Common BACnet errors you may see: Error Code Translation Notes 0x8000001e Device + timeout likely something is offline 0x8001001f Object + unknown object likely b3/AS memory was wiped in power fail 0x80020020 Property + unknown property   0x80020025 Property + value out of range likely writing 0 to a multistate object 0x80020028 Property + write access denied   0x8002002c Property + not cov property trying to subscribe to non COV property  0x8002002e Property + invalid configuration data likely configured a change-of-value alarm on non-analog 0x80030000 Resources + out of memory   0x80050007 Services + inconsistent parameters   0x80050019 Services + operational problem   0x8005001D Services + service request denied   0x8005002B Services + COV subscription failed (0x5002B may show, not including the 0x800)   In Wireshark, using the display filter bacapp.type == 5 one will see errors dissected in the APDU packets in Decimal format. In this example, the BACnet device returns an error for Device (0) and operational problem (25) when responding to a readPropertyMultiple.

Issue Connecting to a Link or Site Environment I/NET Seven Site Cause Knowledge on how to connect to a Link or Site Resolution I/NET displays this dialog box when you select Connect from the main menu. This dialog box allows you to choose a link or remote site. Connect to a device as follows: Select Connect from the main menu. The system displays a summary list of available link devices or sites. Note: A dash (-) appearing next to a device name indicates that the device is not currently available for communication. An asterisk (*) indicates that the name of the controller or the type has changed. Highlight a link device or site in the list. Select OK to connect. After the system connects to the selected device or site, the status bar at the bottom of the screen shows the connected levels.

Issue What is the purpose of the Max Info Frames attribute in a Continuum BACnet controller? Product Line Andover Continuum Environment BACnet MS/TP, MaxInfoFrames Optimizing MSTP Cause Information on the Max Info Frames function. Resolution The Max Info Frames setting on the BACnet controller object editor specifies how many messages that the controller can send out to other controllers when it has the token on the network. For instance, a B3 controller has a default of 2 for this setting. If it receives the token on the MSTP network and it has 5 COV or Event notifications to send to other controllers or workstations, it will send the first 2, and wait until it gets the token the next time around and send 2 more, etc. The BCX controller has a default of 8 for Max Info Frames. This setting is changeable through the BACnet controller editor, however care should be taken not to increase it to too large a number. The larger the setting, the more time that particular controller can hold the onto the token, which in turn denies other controllers on the network the capability of sending out their data in a timely manner. It should only be adjusted if there is a definite need for increased messaging, but on the MSTP network it is not recommended to go above 10, although we do not limit the value. In a Cyberstation Version 1.8 or above the setting can be made on the details page of the BACnet controller device editor. If adjustment of this parameter is done using any Cyberstation prior to version 1.8, the setting will not stay at the new value after a controller reload from the Infinity side, it will revert to it's default. You will need to create a PE program in the controller to set this parameter to the desired value if it is reloaded. The program should be autostart and fallthru, and use the "Writeproperty" keyword to set the parameter. The syntax should be as follows: Line SetMaxInfo WriteProperty ("Full Bacnet path name of controller", MaxInfoFrames, "New Value") Stop

Issue For further information, refer to the FLEXnet Licensing End User Guide, available on the Flexera website. Product Line TAC Vista Environment Vista 5 Workstation FLEXnet Licensing Cause If you get this error and attempt to find the End User Guide, you will discover that the company that produces the FLEXnet software has gone through several name changes: Macrovision to Acresso to Flexera. Resolution If you would like a copy of this document, you can find the FLEXnet License Administration Guide (previously called the End User Guide) here.