Building Automation Knowledge Base

Issue In the LON Flow Balance program the k-factor calculated by the balance process can be displayed at the end of the procedure.  I cannot determine how to read it in the BACnet Flow Balance program.  The value is needed so that the application file can be updated so that if the controller needs to be re-downloaded, it will not need to be balanced again. Environment BACnet  MNB-V1 or MNB-V2 controller WorkPlace Tech Tool software release 5.7.2 or newer  (Optional, for backup) Cause The BACnet Flow Balance process uses a procedure that results in a more accurate flow calibration process. As a result of this process the rate box flow value does not get re-calculated during the balance process. Resolution The BACnet MNB-V1 & MNB-V2 controllers do not rely on a calibration constant (k-factor) stored in the application.  The Flow Balance calibration data is stored separately from the application data so that a revised application file can be downloaded to a controller without losing any of the recorded air balance calibration data.  The Flow Balance data is also saved as part of the file produced by the controller backup function of the Workplace Commissioning Tool.  Refer to the WorkPlace Tech Tool 5.7.2 release notes for more information. The Flow Balance calibration data can be displayed after balancing the BACnet MNB-V1 or MNB-V2 controller by clicking on "Balance Data" in the menu on the left side of the Flow Balance screen.  The Flow Balance Data screen shows the data entered and produced as a result of the flow balance process.  Refer to the figure "Flow Balance Reporting -- Flow Balance Details" in the Air Balancing chapter (Chapter 5) of the "MicroNet BACnet Commissioning Tool / Flow Balance Users Guide", F-27358 for more details.  In addition to being able to manually display the balance data for a single controller, both the BACnet Flow Balance program and the WorkPlace Commissioning tool can generate a flow balance for any or all of the BACnet VAV controllers on the jobsite. Refer to the section "Flow Balance Reporting" in the Air Balancing chapter (Chapter 5) of the "MicroNet BACnet Commissioning Tool / Flow Balance Users Guide", F-27358 for more details.  The resulting report is automatically saved when it is generated and the HTML version can be displayed / printed without the need to reopen it in the BACnet Flow Balance program. In addition to being able to manually re-enter the balance data into a replaced controller, Release 5.7.2 of the WorkPlace Tech Tool software introduced a software function that allows the complete application including COV subscription data and flow balance calibration data to be backed up.  Should it be necessary to replace a controller, the WorkPlace Commissioning Tool can be used to restore the backup into the new controller.  Refer to the "WorkPlace Tech Commissioning Tool Backup and Restore feature" section on page 10 of the release notes (F-27526-3) for more information.  The release notes are available here.

Issue Types of TAC Erie Pop Top valves and actuators available from Schneider Electric in the UK  Product Line Field Devices Environment Pop Top Valves Pop Top Actuators Cause Actuator Part no's available in the UK Valve Part No's and connection types available in the UK ZY valve and actuator replacement Resolution   Actuators AH13U230 - High Close Off - Spring Closed 230Vac Actuator c/w 36" Lead AH13U23A - High Close Off - Spring Closed - 230Vac Actuator c/w 36" Lead + Aux Switch AG13A230 - Spring Closed - 24Vac Actuator c/w 36" Lead AG13A23A - Spring Closed - 24Vac Actuator c/w 36" Lead + Aux Switch AG13U230 - Spring Closed - 230Vac Actuator c/w 36" Lead AG13U23A - Spring Closed - 230Vac Actuator c/w 36" Lead + Aux Switch AG23U230 - Spring Open - 230Vac c/w 36" Lead AG23U23A - Spring Open - 230Vac c/w 36" Lead + Aux Switch AG23A230 - Spring Open - 24Vac c/w 36" Lead AG23A23A - Spring Open - 24Vac c/w 36" Lead + Aux Switch Valves (Note:NPT is American connection) VT2222 - 2way - 1/2" NPT 2.5Cv VT2223 - 2way - 1/2" NPT 3.5Cv VT2231 - 2way - 1/2" BSP 1.0Cv VT2232 - 2way - 1/2" BSP 2.5Cv VT2233 - 2way - 1/2" BSP 3.5Cv VT2325 - 2way - 3/4" NPT 5.0Cv VT2327 - 2way - 3/4" NPT 7.0Cv VT2332 - 2way - 3/4" BSP 2.5Cv VT2333 - 2way - 3/4" BSP 3.5Cv VT2335 - 2way - 3/4" BSP 5.0Cv VT2337 - 2way - 3/4" BSP 7.0Cv VT2437 - 2way - 1" BSP 8.0Cv VT3231 - 3way - 1/2" BSP 1.5Cv VT3232 - 3way - 1/2" BSP 3.0Cv VT3233 - 3way - 1/2" BSP 4.0Cv VT3332 - 3way - 3/4" BSP 3.0Cv VT3333 - 3way - 3/4" BSP 4.0Cv VT3335 - 3way - 3/4" BSP 5.0Cv VT3337 - 3way - 3/4" BSP 7.0Cv VT3437 - 3way - 1" BSP 8.0Cv Erie™ PopTop™ Series Valve Bodies and Actuators - Installation Instructions.pdf for the VT and VS valve, AG and AH actuator. Note: Only those listed above are available in the UK.

Issue Automation Servers go OFFLINE Alarms received about duplicate device name and/or duplicate network identifier. Product Line EcoStruxure Building Operation Environment Enterprise Server, ES Automation Server, AS, AS-P, AS-B BACnet Cause In the BACnet interface duplicate information has been entered for the BACnet IP network for 2 or more Automation Servers. Resolution Make sure the BACnet IP network and broadcast address in the BACnet interface of the ES and all the Automation Servers  are set to a unique value and they match the IP address of the Server (AS, ES) You may have to physically disconnect the units from the network and then connect one at a time in order for Workstation to be able to communicate with the AS and change the configuration of the BACnet IP network.  

Issue When starting SigmaX, an error is reported, the error is: - This application failed to start because side-by-side-configuration is incorrect. Reinstalling SigmaX does not help. Product Line Satchwell Sigma Software Environment SigmaX Windows 7 Windows 10 Cause SigmaX error when trying to run on a Windows 7 or Windows 10 machine. Resolution Use the System File Checker tool (SFC.exe) to determine which file is causing the issue, and then replace the file. To do this, follow these steps: Open an elevated command prompt. Click Start > All Programs > Accessories Right-click Command Prompt, and then click Run as administrator. If you are prompted for an administrator password or for a confirmation, type the password, or click Allow. Type the following command, and then press ENTER: sfc /scannow The sfc /scannow command scans all protected system files and replaces incorrect versions with correct Microsoft versions. More Information about SFC scan can be found in this document: http://support.microsoft.com/kb/929833 At the command prompt, type the following command, and then press ENTER: sfc /scannow The sfc /scannow command will scan all protected system files, and replace corrupted files with a cached copy that is located in a compressed folder at %WinDir%\System32\dllcache. The %WinDir% placeholder represents the Windows operating system folder. For example, C:\Windows. Note: Do not close this Command Prompt window until the verification is 100% complete. The scan results will be shown after this process is finished. However Microsoft Visual C++ Redistributable may not be installed sfc /scannow will not detect this, the Visual C++ Redistributable will need installing. Please see Error when trying to run SigmaX.exe and RegSigmaX.exe for further information regarding this.

Issue How to remove unwanted entries from the Alarm log, Access Event log, Error log, and Activity log automatically. Product Line Andover Continuum Environment Continuum SQL Server MSDE, 2000, 2005, 2008 Cause Want to setup automatic truncation of event logs and unsure how to do this in an SQL Server environment. Resolution MSDE Engine For MSDE, you can go to our Exchange online site and download the Standalone MSDE Database Utilities from the Tools, Utilities and Service Packs section of the Continuum part of our Exchange online web site. This is capable of automatically truncating the logs, as well making automated backups, checking for low hard drive space, etc. SQL Server 2000, SQL Server 2005 For full-blown SQL Server, you can easily create a scheduled Job. Details are described below. To create a scheduled Job that will truncate the Continuum logs in the SQL Server: 1. Open up SQL Enterprise Manager. Note that the SQL Server Agent service must be running in order to create a Job. 2. Highlight the Continuum database 3. From the Menu, select Tools \ Job Scheduling A wizard opens; "Welcome to the Create Job Wizard" Hit Next 4. Select Transact-SQL Command 5. Hit Next 6. For the Database Name, select ContinuumDB (or whatever the name of the DB is) 7. In the large white space for the Transact-SQL Command, cut and paste the code from our web site: /****** Replace 90 with the number of days to maintain in each log ********/ delete from accessevent where DATEDIFF(day, timestamp, getdate()) > 90 delete from activityevent where DATEDIFF(day, timestamp, getdate()) > 90 delete from alarmevent where DATEDIFF(day, timestamp, getdate()) > 90 delete from errorevent where DATEDIFF(day, timestamp, getdate()) > 90 8. Hit Next 9. On the next screen, you are asked when you do want to run this job. Select "On a recurring basis" and hit the Schedule button. 10. On the Schedule page, set up whatever schedule you desire 11. Hit OK to close the Schedule Page 12. Hit Next 13. On the Job Notifications screen, you can choose (if you want) any email or net send alerts. This is optional 14. Hit Next 15. In the final page, you are given a summary of the Job you have just created and you can change the name of your Job to anything you want. It might be a good idea to give it a more descriptive name like "Weekly Log Truncation" 16. Click Finish and you are done. You should get a message that the job was created successfully. To verify that the Job is running correctly, you can go to the Enterprise Manager of SQL Server and click on the Management Folder, then expand the SQL Server Agent folder and click on Jobs. On the right-hand pane, you will see a list of created jobs. Scroll down and find the job that you just created. You can get information about the history of the Job, whether it ran successfully or not.   SQL Server 2008 1. Run Mgmt Studio and login as sa. 2. Make sure SQL Server Agent is running. Would expect it is by default. 3. Right-click on Jobs (under SQL Server Agent). Select New Job... 4. General tab - Name: TrimLogs // Owner: sa // Category: Database Maintenance // Enabled checkbox 5. Steps tab - New... // Step name: DateDiff // Type Transact-SQL script (T-SQL) // Run as: [null] // Database: ContinuumDB //Command: [pasted in code below]. Press OK. delete from accessevent where DATEDIFF(day, timestamp, getdate()) > 90 delete from activityevent where DATEDIFF(day, timestamp, getdate()) > 90 delete from alarmevent where DATEDIFF(day, timestamp, getdate()) > 90 delete from errorevent where DATEDIFF(day, timestamp, getdate()) > 90   6. Schedules tab - New... // Name: Weekly // Schedule type: Recurring & Enabled // Occurs: Weekly // Recurs every: 1 week(s) on [whatever date and time]. Press OK. 7. Did not set up Alerts, Notifications or Targets. 8. Press OK. 9. Set it up to run a few minutes after creation. 10. After time passed, opened Mgmt Studio and double-clicked Job Activity Monitor. Saw TrimLogs had successfully run. 11. Ran query: Select count(*) from ActivityEvent to verify count went down.  

Issue What is throttling range? Product Line TAC I/A Series Environment I/A Series controllers Cause Setting a proper throttling range will allow for more accurate control of external actuators and devices. Resolution Throttling range is the amount of change in the process variable that is necessary to cause the controller output to change from 0 to 100%. The controller output may be 4-20mA, a voltage range, or pressure range.

Issue How to get an MSTP capture file so it can be analyzed for comm activity on an MSTP bus How to determine if a site is using bad COV management How to determine if a controller has poor bus design or installation How to determine if a site has multiple BBMD's on the same subnet Product Line Andover Continuum, EcoStruxure Building Operation Environment bCX4000, bCX4040, ASP, ASB b3 controllers Third party BACnet MSTP devices Wireshark Cause Analyze MSTP traffic via capture. Resolution To capture MSTP communication activity to a capture file that can be analyzed using a network sniffer application such as WireShark you will need the following.   Hardware One is required to have an RS-485 Adapter to connect to the MS/TP trunk USB to RS-485 Adapter USB-RS485-WE-1800-BT FTDI, Future Technology Devices International Ltd | 768-1041-ND | DigiKey  RoamIA or RoamIO Any other RS-485 adapter compatible with BACnet MS/TP and baud rates used Software Download and install the following applications: BACnet MSTP Capture Application WireShark Configuration If using the USB to RS-485 Adapter Connect the USB adapter cable to the USB port on a laptop PC Connect the RS232/RS485 adapter to the 9-pin end of the USB adapter cable. Attach a length of MSTP bus cable to the wire terminal on the RS485 adapter. If using the FTDI Connect the TDI RS-485 adapter to the USB port on a laptop PC Connect the cables to the MSTP trunk where Orange = Data+ (A) and Yellow = Data- (B) Ensure the RS-485 adapter driver is installed in Windows by opening Device Manager and ensuring that it is listed as expected under Ports (COM and LPT). Record the COMx being reserved by the adapter.  If using Wireshark with MSTPcap.exe to capture Ensure MSTPcap.exe is installed in the Wireshark Extcap folder per MSTP Capture Application link above NOTE: Wireshark may need to be rebooted if MSTPcap.exe was added while it was open Launch Wireshark Select gear next to BACnet MS/TP on COMx Set known baud rate Click to start a capture.  If using MSTPcap.exe via Command Prompt to capture Copy the MSTP Capture application to C:\ Open a command window. Launch the application by entering C:\> Mstpcap com# ###### where com# is the PC's serial port (Com1, Com2, etc.) and ##### is the current baud rate the bCX/AS MSTP bus is configured for (19200, 38400, etc.). The command window will indicate the name of the file the activity is being captured to. Once done, close the command line window The capture data can be viewed by running Wireshark. Select File > Open and navigate to the folder the capture file was saved to and select the capture file. With the higher-end MSTP capture tools such as tools developed by PolarSoft and Cimetrix, MSTP captures at 76.8K baud are possible. Lower-end capture applications like MSTPCap typically are only able to capture MSTP packets from networks running at bus speeds at or below 38.4K baud. Also, check out the BACnet-Capturing MS/TP Traffic Quick-Help video on the Exchange. This video uses the older pipe method that was used before Extcap was available in Wireshark.

Issue Drayton Theta ll EC Compensator Controller requires replacement. Product Line Field Devices, Satchwell Sigma Environment Stand alone discreet Drayton Compensator Controller :- Theta ll EC Cause Obsolescence of Drayton Theta ll EC Controller. Resolution Replace Drayton Theta ll EC Compensator Controller with Satchwell CSC Compensator Controller. N.B. Two models of the Satchwell CSC Compensator Controller are available. CSC5252 without programmer details of which may be viewed here. CSC5352 including programmer details of which may be viewed here. It should be noted that the Actuator / Valve Body assembly connected to the Drayton Theta ll EC Compensator Controller may be retained for connection to the Satchwell CSC Compensator Controller. It should also be noted however that the associated Drayton Theta ll EC Compensator Controller Sensors are also obsolete. These Sensors are not compatible with the Satchwell CSC range of Compensator Controllers and must also be replaced. Satchwell CSC Compensator Controllers are compatible with the following Sensors :-   STO 600 Outside Air Temperature Sensor, details of which may be viewed here. STR 600 Room Temperature Sensor.(Optional), details of which may be viewed here. STC 600 Surface Mounting Temperature Sensor, details of which may be viewed here. or alternatively :- STP 660 Immersion Temperature Sensor, details of which may be viewed here. plus DWA 0005 Immersion Temperature Sensor Pocket, details of which may be viewed here.

Issue Satchwell CD2201 Compensator Controller–Actuator requires replacement. Environment Stand alone discreet Satchwell CD2201 Compensator Controller–Actuator Cause Obsolescence of Satchwell CD2201 Compensator Controller–Actuator Resolution Replace Satchwell CD2201 Compensator Controller–Actuator with Schneider Electric Satchwell CSC Compensator Controller, compatible Temperature Sensors and MD Series Actuator and Linkage Kit. Replace Satchwell CD2201 Compensator Controller–Actuator with Schneider Electric Satchwell CSC Compensator Controller. N.B. Two models of the Schneider Electric Satchwell CSC Compensator Controller are available :- CSC 5252 Compensator Controller without Time Clock CSC 5352 Compensator Controller with integral Time Clock  Details of the Schneider Electric Satchwell CSC Compensator Controllers may be viewed here. It should be noted however that the CD2201 Compensator Controller–Actuator had no integral Time Clock. Replacement of Air Temperature Sensors It should be noted that the existing Satchwell Outside Air Temperature Sensor associated with the CD2201 Compensator Controller–Actuator is obsolete and should be replaced. Similarly, it should be noted that the existing Satchwell Inside Air Temperature Sensor associated with the CD2201 Compensator Controller–Actuator is obsolete and should be replaced. Details of replacement Schneider Electric STO600 Outside Air Temperature Sensor may be viewed here. Details of replacement Schneider Electric STR600 series Inside Air Temperature Sensor may be viewed here. N.B. It should be noted that the CSC Compensator Controller will perform entirely satisfactorily without the connection of an Inside Air Temperature Sensor. Replacement of Water Temperature Sensor. It should be noted that the existing integral Satchwell Water Temperature Sensor associated with the CD2201 Compensator Controller – Actuator cannot be re-used and should therefore be replaced. In order to minimise mechanical work it is suggested that a Surface Mounting Temperature Sensor is installed on the pipework, rather than an Immersion Temperature Sensor installed in a Pocket in the pipework. Details of replacement Schneider Electric STC600 Surface Temperature Sensor may be viewed here. Replacement of Actuator. Whilst the existing Satchwell MB Valve Body may be retained, a new Schneider Electric Actuator and Linkage Kit will need to be installed on the MB Valve Body in order to permit control from the CSC Compensator Controller. Details of the Schneider Electric MD10B Actuator may be viewed here. Details of the Schneider Electric LMD/AR-MB Linkage Kit may be viewed here. Please be aware: since July 2016 the CSC compensator and other descrete controllers were withdrawn from service. To see "PA-00479 - Discrete Controllers - Notice of Withdrawal - Satchwell" click here.

Issue A Schedule or PE program can not change the value of a point because it is set by another process at a higher Command Priority. Product Line Andover Continuum Environment CyberStation bCX4040 B3s Cause Command value must be Relinquished at the priority that no longer needs to control the point's value so that a command with a lower priority can take control of it. Resolution Edit the point from the BACnet view. Go to the Command Priority tab, this tab shows the 16 priorities and their current statuses   Select the priority to relinquish and then click on the Relinquish button. The command with the next highest priority should then immediately take over.

Issue When accessing an I/A Series R2 or I/A Series G3 station web page, a popup window is displayed warning of a possible security vulnerability. The popup warning is displayed differently depending on the browser version and Java version installed on the computer used for viewing the graphics. -------------------------------------------------------------------------- With Java 7 update 11 or newer, and Internet Explorer 8 or 9, the following popup windows is displayed (location string will vary):   Note that even if you check the "Do not show" checkbox, you will receive additional prompts because the prompt is displayed for each Java applet encountered in the current browsing session.  Likewise, if you close the browser and reopen it, navigating to the same site, the prompts will again be displayed. If accessing I/A Series G3 graphics, the following screen may be displayed: A variant of this message is as follows: --------------------------------------------------------------------------- If using a recent version of the Firefox web browser, the following message is shown in the graphic applet window: "This plugin has security vulnerabilities.  Click here to activate the Java(TM) Platform SE 7 U Plugin."   --------------------------------------------------------------------- When using the Mozilla Firefox browser to access I/A Series G3 graphics, the following security warning may be displayed (Click "I Understand the Risks" and follow prompts to continue):   Environment Windows computer Internet 9 or Firefox web browser Cause Known security vulnerabilities with the Java JRE software Resolution Since the issue is being reported by the Java software or the Java plugin in the browser, there is nothing we can do to directly resolve the issue. There are several workarounds possible, depending on how the site deals with browser security issues. The most secure approach is to allow the applet to be run each time you are prompted. If using Internet Explorer, click the [Run] button on the security warning popup window. If using Firefox, two actions may be needed.  First if the warning "This connection is untrusted" is displayed, click the "I Understand the Risks" Unfortunately, this is a Java issue, not an I/A Series R2 software issue. Oracle has added this popup to its browser plugin to warn the user that a downloaded Java applet may be unsafe to execute. According to information published by Oracle, it may take them up to two years to correct all the known security issues in the Java-JRE. Many of the known issues date back to before Oracle assumed ownership of Java. The only workaround at this time is to downgrade the Java-JRE to a version that does not notify its user that the Java applet to be executed may pose a security risk. We did some testing on Windows 7 with IE9 and found that Java 1.7.0.9 (Java 7 update 9) does not cause the prompt to be displayed. In addition, we found that in some cases we were able to greatly reduce the number of times the prompt appears in Java 1.7.0.17 by setting its security setting to Low (Java control panel applet, Security tab). On one of the virtual machines that we tested this on, the prompt would be displayed the first time you accessed the site and would not be displayed again until you closed the browser and reopened it. On a second computer, the prompt would be displayed each time you accessed a new site or re-opened the connection to the same site but not on multiple screen accesses from the same site. We are not sure at this time why some systems exhibit this different behavior. Note that when using Firefox 19.0.2 and Java 7 update 9 or earlier, a different message is displayed when the web page attempts to open a java window. This window is not displayed when using any version of Java that includes its own security warning popup. The security warning popup I am referring to is the same one displayed when using Java 7 update 17 and other recent versions on Internet Explorer 9 or Firefox 19. This message is designed to notify the user that there is a known security vulnerability with the addon being used, in this case, the out-of-date Java plug-in. There is a workaround published on the mozilla support site that documents a procedure for disabling these warnings when using the earlier versions of Java 7. This workaround does not solve the Java popup warning issue for the Firefox 19.0.2 / Java 1.7 update 17 combination. I did not test it with other combinations other than Firefox 19.0.2 / Java 7 update 9. Here is the configuration change for Firefox 19: Open Firefox Open a New tab Browse to about:config i.e., enter the string in the browser address bar Accept the security warning In the displayed list, right click on extensions.blocklist.enabled In the selection window, click Toggle to change the entry to false Close and reopen the browser. This will disable the security warning for all browser plugin applets, including Java 7 update 11 and earlier, Java 6 Updates 31-38, Adobe Flash Player 10.2.*, 10.3 or 11.0-11.4, Microsoft Silverlight 4.1 and earlier or 5.0/5.1, and about two dozen other plugins that have known security issues. At this time we have not found any workarounds for disabling the Java security warning popup that occurs with Java 7 update 12 and newer with either Internet Explorer or Firefox. As additional information regarding this issue becomes available regarding Java and Internet browser updates, this article will be updated as required.  Depending on site security restrictions, it may be necessary to disable Java when not using it for accessing I/A Series R2 or G3 systems.  See the following instructions from the Java web site: To disable Java - http://java.com/en/download/help/disable_browser.xml To enable Java  - http://java.com/en/download/help/enable_browser.xml In some cases, you may be able to bypass the warning but all your graphics pages do not  load.  This issue is sometimes caused by a security issue with some of the cached java temporary files.  There is a workaround, as follows: In the Windows Control Panel, open the Java applet. Under the "General" tab, "Temporary Internet Files"  section, click [Settings] Uncheck the box "Keep temporary files on my computer" Click [Ok] to save the change then click [OK] to exit the Java control panel.

Issue Controllers underneath a LonWorks Interface are going offline, or values are taking long periods of time to update. Product Line EcoStruxure Building Operation Environment Building Operation Workstation Cause There could be a number of causes for Lon communication problems including running the communication wire near high voltage, the Lon is shorted out, or loose terminations. Resolution In EcoStruxure Building Operation (EBO) Workstation you can use the Diagnostics tab under each controller to help troubleshoot the communication issue. From here you can monitor the device state, packet errors, transaction timeouts, receive transaction full errors, lost messages, missed messages, last reset case, and the last error logged. To access the Diagnostics tab, select the controller in the System Tree, and click the Variables tab. Then click the Diagnostics tab on the right side of the screen. Here you will find the different device statuses and statistics. The Packet errors can be used to help identify controllers that are having severe problems and may need the communication wire to be physically checked. In order to test the Packet errors, first you will want to clear the current packet error count. You can do this by right clicking on the controller and selecting Advanced -> Clear Status. This will set the packet error count back to zero and now you can click refresh to monitor how fast the errors are building up. If this number is climbing quickly then there may be a physical layer communication problem. If a lot of packet errors is found, the next step in the investigation will be a deeper analysis of the Lon network, using, for example, a Lon Protocol Analyzer (LPA). Refer to the Knowledge Base Article Troubleshooting LON Network Communication.

Issue Need information on how exactly SmartStruxure checks whether BACnet devices are still online or have gone offline. Product Line EcoStruxure Building Operation Environment Enterprise Server - ES Automation Server - AS BACnet devices Cause Understanding how communication status is verified can help with troubleshooting comm loss issues. Resolution After a device is discovered via the WHO-IS/I-AM service and moved into the SmartStruxure database, SmartStruxure uses the following scheme to check on the communication status of the device. For IP Device The server will send a Read Property message to read the devices's system status*** every minute, as long as a reply is received the device is deemed to be ONLINE. If no reply is received by the APDU Timeout the server will retry up to 3 times, if there is no response the device will be considered to be OFFLINE. For MSTP Device The server listens as the token is being passed around the bus and if a device fails to get the token it will be tagged OFFLINE. For both IP and MSTP Device Once the device is tagged OFFLINE, the server will check on the device once a minute by sending a WHO-IS message with the ID of the device, if an I am is received the device will be considered back ONLINE and the ReadProperty 'probe' check (for IP) or token pass check (for MSTP) will resume once a minute. ***In version 1.4 and below the ReadProperty will read the name property of the device. See sample Wireshark capture below, NOTE that in the sample below 10.169.90.31 is the Broadcast address of the sub net where the ES is located. NOTE: For efficiency the BACnet engine may combine the reading of the system status property with other read property requests into a single Read Property Multiple.

Issue SER8000 series room controllers communications options Environment SER8000 series room controllers Cause Integration to SER8000 room controllers via Modbus is required.  Resolution Currently, the SER8000 series room controllers communications options are Zigbee Pro or BACnet MS/TP. Refer to the SER8300 datasheet.  To communicate on Modbus RS-485, an option would be to use the multi purpose manager (MPM-UN) as a gateway device.    * Updated July 2015 As per Product Annoucement PA-00428, the SE8000 with firmware 1.3 can now act as a Modbus slave using the RS-485 port. 

Issue When using Advanced Display and logging in to Webstation, it startups in kiosk mode with limited functionality. Example:   Product Line EcoStruxure Building Operation Environment Building Operation Advanced Display Cause When running Webstation in Advanced Display it is by default started in kiosk mode Resolution Open SmartX HMI Kiosk in Advanced Display In "Webstation setup" delete the part ?kiosk# Example: https://192.168.42.116/?kiosk#  Webstation be started in kiosk mode https://192.168.42.116/  Webstation will start normally

Issue Controllers may leave their network and join another if a nearby network has an identical "Extended network ID", "Channel" or "PAN ID" Product Line EcoStruxure Building Expert Environment SmartStruxure Lite Multi-Purpose Manager SE8xxx Room controller SE8000 Series SER8300, SE8300, SE8350 Ex. Viconics branding VT8000 Series Cause Conflict in zigbee networks (Same "Channel", same "PAN ID" or Same "Extended Network ID") Resolution Before deployment, and in order to ensure having a reliable ZigBee network, one has to be aware of the best practices and the limitations of RF signals. Here are some key points to be considered Network Conflicts: Always change your Extended Network ID from the factory default. The best thing is to use a naming convention that makes sense. One suggestion would be to use "SSLLITxx," where "xx" is replaced by the floor the network is on. For example, floor 5 would be "SSLLIT05." If you have multiple networks on the same floor, adding a letter code helps denote them. For example, if there were 2 networks on floor 5, "SSLLI05A" and "SSLLI05B" can be used. Note: In Firmware 2.20.1, the ZigBee Extended Network ID parameter is set by default to a unique string based on the serial number of the MPM. This will eliminate the possibility of having duplicate Extended ID's in a new deployment. For existing installations, the Extended Network ID will remain unchanged if upgrading from a previous version.   Alternating Channels: Alternating channels between network will minimize interference ensure stability. For example, for a 5-story building, alternate between channels 20, 25, 20, 25, 20. Tx Power Upgrade: The default value for "Tx Power" is 5dBm which was designed in order to meet various regulations in certain countries (Europe). However, the "Tx Power" can be increased to 18dBm in other regions of the world (North America) to boost the transmission power of the MPM.   Interference: There are different types of interference when a wireless signal travels through a given space: Physical objects: The number of walls the wireless signal can pass through is determined by the density of the materials used in a building's construction. Concrete and steel walls are difficult for a signal to pass through. These structures will weaken or at times completely prevent wireless signals. Also, the presence of individuals or water will diminish the signal due to the water's ability to absorb the signal. 2.4Ghz Frequency Interference: Cordless Phone - operates on the same frequency as the ZigBee and can cause a significant decrease in performance. Microwave Oven - operates by emitting a very high power signal in the 2.4GHz band. Often emits a very "dirty" signal across the entire 2.4GHz band. Wireless Routers - Wireless Wi-Fi Networks that share the same channel will have a negative effect on ZigBee network performance. Distance: To ensure reliable communications, a suitable distance between two devices has to be calculated before installation. The distance depends on three factors; transmitter power, sensitivity of the receiver and the propagation path loss. The latter is dependent on the number of walls/physical objects obstructing the signal. Locations: The physical location where a router or coordinator is placed also has an impact on the signal. Place the devices in higher ground to reduce the impact of physical objects. Route Redundancy: It is critical that the signal has multiple routes to hop from one device to the other, from one edge of the network to the opposite edge. (See example in images below)

Warning Potential for Data Loss: The steps detailed in the resolution of this article may result in a loss of critical data if not performed 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 Failed to read events from the event log database. Product Line TAC Vista Environment TAC Vista Workstation Cause This error is sometimes displayed upon login to the TAC Vista Workstation. It indicates there is a problem with the connection between the Vista Server and the SQL database that stores event data. Resolution Before making any further tests, make sure you have MSXML 4.0 SP3 installed and then check if it works. It can be downloaded here: https://www.microsoft.com/en-us/download/confirmation.aspx?id=15697 The first thing to check is the SQL connection. Open the TAC Vista Server Setup In version 5.1.3 and prior: Start > Programs > TAC > TAC Vista Server X.X.X > Server Setup In version 5.1.4 and later: Start > Programs > Schneider Electric > TAC Vista Server X.X.X > Server Setup Go to the SQL Server tab In the lower right-hand corner of the tab, press the Test Connection button. If it pops up a window that says "Connection test succeeded!" then your SQL connection is okay. If it fails the connection test, check the instance name. If you are using default settings it should be: SQL Server name: PCname\TACVISTA or (local)\TACVISTA Log database name: taclogdata If these are set correctly and the connection still fails, one method for reestablishing the connection is to uninstall/reinstall the Vista software. Make sure SQL Server Agent is running. Right-click on My Computer and select Manage Navigate to Computer Management (Local) > Services and Applications > Services Find SQL Server (TACVISTA) -- assuming the default SQL instance is being used. Make sure the service status is running.  Start the service if needed. If there is no problem with the SQL connection, check the Server object's Network Master. In Vista Workstation, right-click on the Vista Server object and select Properties On the General tab, in the Network pane, check the Master: name In a one-server network, the Network Master must be set to the Server object name. Check for queued files in the $queues folder Navigate in a Windows Explorer window to the Vista Database. (If you are unsure of the location, you can verify it in the TAC Vista Server Setup Vista Database tab). Go to the $queues folder Look inside the insertevents and insertlogvalues folders. Are they empty or are they consistently growing with files? This is where data is stored temporarily before it is written to the SQL database. Having queued files is not necessarily a sign of a problem. However, if there is a connection problem, these folders will continually grow in size without older queued files being written from the folder. In the case of the error "Failed to read events from the event log database", it is possible that a queued file is causing the error prompt and that deleting it will fix it. If the data is not of dire importance, delete all the files inside both of the $queues folder. For more information see An efficient method for deleting all queued files in the $queues folder. Reconfigure the log database Open the TAC Vista Server Setup In version 5.1.3 and prior: Start > Programs > TAC > TAC Vista Server X.X.X > Server Setup In version 5.1.4 and later: Start > Programs > Schneider Electric > TAC Vista Server X.X.X > Server Setup Go to the SQL Server tab Change SQL configuration from Typical to Custom Change the Log database name Hit Apply. It will warn you: "TAC Vista integrated SQL backup/restore function will not be available in custom configuration." Hit OK. It will then warn you: "No log database was found on SQL Server. Create and configure a log database?" Hit Yes.   At this point, if no backup features are necessary, and the error has cleared, this is a viable solution. It is not, however, recommended to maintain a site without any log backups. The next step would be to switch the Vista Server Setup SQL configuration back to Typical. Hit Apply. You will be warned: "Log database was found but needs to be reconfigured. Reconfigure log database?" Hit Yes.   After reverting to typical SQL settings, the error should clear. If it has not, it may be time for some database management. Performing Database Maintenance Follow the steps in the article Performing database maintenance with Vista 4.5.0  to set up a log and event backup and to clean up old data. Schedule a backup to occur (now or soon after) The next time you log into Vista Workstation, the error should be cleared. If the error is sporadic, it could be the event viewer has too many events If the error only occurs when logging in to Vista Workstation, and doesn't happen every time, it could be that too many events are being brought into the Event Viewer on login. All events specified in the filter for the event viewer are uploaded to the Workstation. If too many events are specified, problems occur. In Workstation, go to the root TAC Vista folder Right-click $Eventview and select properties Go to the Date and Time tab Set the Time period to Last 1 Hour(2) instead of Last 1 Week(s), which is default Check the Windows Event Log If all else fails, check the Windows Event log for more information about the error. Checking this may provide you with the answers you need, or at least give you more information to provide to Product Support if you need further assistance. Instructions available in Viewing, Saving, Sharing Windows Event Logs for Troubleshooting Purposes. Right-click on My Computer and select Manage Browse to Computer Management (local) > System Tools > Event Viewer > Application Look for Type Error events with Source Vista. This may help you determine the source of the error.

Issue Current transducers require an additional external resistor fitting to a Universal input to read the current flow, what resistor and input point settings are required? Environment All controller with Universal Inputs (both 5V and 10V). 4-20 mA Cause There is a requirement to define the resistor value to be connected across the input, also the settings for the upper and lower voltage in the input point configuration. Resolution Download the attached Current Inputs.PDF file, although this was originally written for Infinity controllers it is fully applicable for i2 and b3 controllers. Controllers like the i2/b3920, i2/b3810 have 10V inputs other i2/b3 controllers have 5.12V inputs, check the product datasheet specification if you are unsure. The file details the value of the resistor to use in the circuit and the upper and lower voltage settings to enter in the Auto Conversion box in the input point, these will correspond to the sensor reading at 0mA and 20mA, or 4mA and 20mA depending on your sensor output. For controllers that allow the pull up resistor to be switched out, ensure that it is in circuit for these setting to work correctly. The UI-8-10-10V I/O Modules should be set to 0-5V input with the reference resistor On, then setup as per all other 5.12V input controllers. Note: The part numbers listed for the resistors are no longer available through Order Entry and should be sourced from your local stockist. Link to file: Current Input ISM.pdf   Suitable component resistors: For 10V inputs: RS 165-472 For 5V inputs: RS 165-185

Issue Should automatic updates be turned on for Continuum workstation? Are there certain known issues of updates that have caused problems with Continuum or Webclient? Product Line Andover Continuum Environment Continuum Cyberstation Continuum webClient Server Windows 10 Windows XP  Windows Vista Windows Server 2003 Windows Server 2008 Cause Microsoft Windows has an automatic update feature and frequently releases updates which can potentially affect Cyberstation and Webclient Server. Resolution Automatic updates should not be turned on for a Continuum or Webclient workstation. The Continuum compatibility matrix indicates Windows Operating Systems, Windows Service packs, SQL Server, .Net and Internet Explorer versions that were tested by Quality Assurance at the time of product release. Continuum Quality Assurance does not perform regression testing where new Microsoft updates are tested with Continuum products released in the past. Product Support recommends setting Windows updates to one of the other two options to allow for testing of Microsoft updates: Additional details can be found at: http://support.microsoft.com/kb/306525 Download updates for me, but let me choose when to install them Notify me but don't automatically download or install them   There are several specific updates that have caused issues with Cyberstation or Webclient. This is not a comprehensive list. Occasionally updates will break certain features and we discover this from our internal testing or from reports from partners or branches. Here is a list of some updates that have caused issues. KB835732-  Pinpoint 1.52 crashes when installed on a machine and you are accessing graphics from a network share. If you remove the hotfix the problem goes away.  This is the same hotfix that caused the SmartHeap out of Memory errors that was fixed with SP5 for 1.6.  KB828741- IIS (Webclient) machines without this patch may receive “Unable to establish a link to the remote Infinity services” Webclient 1.73 - Any patches that will install .Net Framework 2.0 will cause problems with webclient 1.73 since we don’t start using .Net 2.0 until webclient 1.74. KB911280 - this update blocks the acc.scp script from setting controller to PPP mode. This will a cause a Cyberstation using RAS controllers to not allow a connection. It will authenticate, but not connect. KB928366 – Webclient machines that use .Net 1.1(Listed on the compatibility matrix) will receive the error "Could not connect to server cause; type missing for member of type object _context id'. Could not create acwppserverproxy."  when opening web pinpoint graphics.  Remove this hotfix or upgrade to webclient 1.74 or greater. KB929969 – this hotfix does not require a reboot by Microsoft, but can cause the Cyberstation install to fail, if the install is performed before rebooting after the installation of the hotfix. See the Technical bulletin. KB968749 - SQL Express install fails on XML6 SP2 See SQL Express install fails on MSXML 6.

Issue The object information received from a MicroNet and IAC controller is based on a request for information from the Xenta. If the local area network receives too many requests, the system will not operate as quickly as expected. It is important to configure the objects with a realistic poll time to avoid issues with slow system response. Product Line Satchwell MicroNet Environment Xenta 500 Xenta 700 Satchwell MicroNet Cause Slow graphic, alarm, updates Resolution Updated June 2019 The MicroNet 50 series range MN350, 450, 550, 650 LCD and Touchscreen have been withdrawn from sale. The IAC 420, 600 and Touchscreen have now also been withdrawn from sale. No direct replacement is offered. Further information on these changes can be found in PA-00495 - Notice of Withdrawal - Satchwell Sigma and PA-00528 - End of Commercialization - Satchwell Sigma. ---------------------------------------------------------------------------------------------------------------------------------------------------------- Network Architecture The size of a MicroNet/Satchnet network within XBuilder is not limited. It is quite possible to have 80 Unifact Pro controllers directly connected on an NCP RS485 network; ARCNET and Satchnet networks with routers can be much larger than this. With such large networks, to achieve acceptable system performance, the number of signals requested and their poll rate must be considered when engineering the Xenta 555. Note that Satchnet networks run four times slower than MicroNet NCP networks. Bandwidth and Performance  Because both MicroNet and Satchnet networks are polled, there is a limited bandwidth available in which to obtain all signal data. This means that it is necessary for the Xenta 555 to request each programmed signal (point) in turn from each controller. There are many factors which deter-mine the performance of a network, however it is generally accepted that certain signal parameters should update more frequently than others. The Xenta 555 has a special dynamic poll scheme that is inherent in the controller and needs no configuration. The polling of any signal depends on the signal type and its poll frequency. Priority is given to signals with the fastest poll rate; therefore some mea-sure of control can be applied to the prioritization of signals. The most important signals should be configured with the fastest poll rate. In the event that a particular signal is referenced more than once, for example, in an alarm, log and web page, that signal appears in the poll scheme once only and is polled at the fastest rate (that is, the fastest of the alarm rate, log rate or web page rate). Typically, the order of engineering priority should be: 1 Alarms 2 Web pages 3 Logs Tip Connection objects should be kept to a minimum because each connection comprises a read signal and a write signal (that is, two operations). Performance example Consider a Xenta 555 ARCNET or NCP network with three web clients showing three web pages (two alarm pages and one values page with 50 signals). The Xenta 555 configuration comprises a total of 480 signals: . 100 alarm signals set with a scan time of four seconds. . 300 logs at a logging interval of one hour. . 30 connection objects at a period of 10 seconds. 50 point signals on a values page with a fixed refresh time of 10 seconds. In this network, the signals will arrive in the alarm pages typically within 60 seconds. Connection objects and signals in values pages will update within 60 seconds. The Xenta 555 polling algorithm computes the optimum poll rate for each signal, therefore if the sum of the poll frequencies exceeds the available bandwidth at any particular time, the lower frequency polls will be delayed. This has the effect of spreading the polls out over the available bandwidth and therefore optimizing performance. Signals on graphics pages and values pages are only polled when the page is being displayed in a web browser, however when a signal is required for logging, alarming or for a connection object, the signals are continuously polled at the configured poll time Web Page Updates Some examples of expected polling rates follow: - In addition to MicroNet network updates, web pages are updated at regularly intervals and this should be considered when analyzing the over-all performance; ten seconds should be considered typical for a web page update. However, polling performance is affected by the number of web clients and the number of web pages. If each web client simultaneously requests a different web page, each with a set of signals not currently being polled (for example, alarms), then the number of polled signals will increase substantially and therefore slow down the rate of web page updates. For this reason it is recommended that the number of web clients is restricted to three for a typical Xenta 555 network as described in the example given earlier. Due to a slightly enhanced Native Communications Protocol (NCP) and Attached Resource Computer Network (ARCnet)  employed by the 50 series controller a small difference between the 100 series and 50 series controller Packets/Min can be seen, these are indicated below. Xenta555 - MNMI NCP Polling 50 Objects 10 Polls/Sec 426 to 595 Packets/Min MN620 526 Packets/Min MN650 567 Packets/Min Xenta555 - MNMI ARCnet Polling 50 Objects 10 Polls/Sec 426 to 595 Packets/Min MN620 484 Packets/Min MN650 495 Packets/Min Xenta555 - SNP 1200 Polling 50 Objects 2.5 Polls/Sec 169 to 174 Packets/Min Xenta555 - SNP 4800 Polling 50 Objects 7.5 Polls/Sec 398 Packets/Min These times are the averages found during testing, these figures will be affected by the following: - 1. The amount of controllers on the LAN (The Xenta 555/731 carries out some background polling an each controller for online and null output status). 2. The controller type has a small bearing on the polling rate per second. 3. Quality of the communications wiring.(poor wiring or incorrect cable specification can cause errors and re-tries) 4. Quality of the controller wiring, particularly with ARCnet installations. (Unscreened inputs ETC can result in noise reaching communications cable causing errors). 5. With the Xenta 731 particularly a high level of Menta programs ETC can cause time delays if the Xenta processor struggles to process all the information in good time. Further information can be found in the TAC Xenta 555 Supplement Manual.