Building Automation Knowledge Base

Issue Although all the cameras connected to Pelco Endura SM5000 system manager can be found by the video server, when using "Video Administrator" to try to assign alarm points to cameras, sometimes cameras cannot display properly,  such as "1-192.168.5.10"(SM5000 IP Address),  or return "not found' and get an error message such as "Camera or Video server maybe offline....". Environment Windows XP SP3 Cyberstation 1.92, Cyberstation 1.93 Pelco Endura SM5000 system manager Cause It is an Endura configuration problem. A camera should be added into a group. In and Endura system, there is a default group, if no additional group is created. Normally, cameras should be added into this default group. However, in some situation, some cameras will not be automatically added into that default group. In this situation, those cameras do not belong to any group; therefore, those cameras will not display properly in the camera's field drop down menu and cannot be selected. Resolution Create one or more groups in Endura system. Add the desired cameras into the groups created in step 1. Learn cameras again from the video server. Reopen the video administrator and add points to cameras.

Issue Define what Network 8000 devices that can be integrated with EcoStruxure Building Operation. Product Line EcoStruxure Building Operation, TAC I/A Series Environment EcoStruxure Building Operation Automation Server version 1.2 until and including 3.2 Network 8000 Cause Need to know the supported devices for a Network 8000 to EcoStruxure Building Operation upgrade.  Resolution EcoStruxure Building Operation supports the following Network 8000 LCM devices: LCM EcoStruxure Building Operation supports the following Network 8000 ASD devices: Microzone II MicroFlo II LIM PEM  The following Micronet 2000 products are supported: MN-FLO MN-FLO3T MN-HPFC MN-ASDI  The following Network 8000 products are not supported in EcoStruxure Building Operation: CCL GCM LNC SIM GCM PLC Note: EcoStruxure Building Operation version 4.0 (EBO 2022) and higher are not supported

Issue Living Space Sensore goes offline after upgrading SmartX Controller firmware from 2.0x to 3.01 or later Product Line EcoStruxure Building Operation Environment Building Operation Room Controller (RPC) v3.01 or later Building Operation SmartX Living Space Sensor Cause Living Space Sensor RJ-45 connector is plugged into Room Bus port on RPC. Resolution Move RJ-45 connector from Room Bus port to Sensor Bus port.

Issue An "Internal Server Error 500" message appears when attempting to access a Niagara G3 ENC station via a web browser. Environment Niagara G3 ENC station Web browser Cause Typically, this issue is caused by the Module Content Filter Level in the ENC being set to "RUNTIME". In order for an ENC to host Web Services, the ENC needs to have the Module Content Filter Level set to "UI+RUNTIME". Resolution Use the Commissioning Wizard in the Platform Administration section of the ENC's Platform to set the Module Content Filter Level to "UI+RUNTIME". In some cases, the error message persists even after re-commissioning per the above instructions. To correct this problem, go to the Software Manager in the ENC's Platform, highlight all the modules that are marked "Up To Date", and re-install them.

Issue Satchwell Sigma integration to BACnet Environment Satchwell Sigma IC-GEN-DDE PolarSoft BACdoor DDE Server Cause There is a need to integrate BACnet devices / system into Sigma. Resolution Refer to Product Information Bulletin 02.07.05-3 - BACnet I/O server for IC-GEN-DDE for details on the integration. Other than purchasing the IC-GEN from Schneider Electric, you will also need to purchase the BACdoor DDE Server from PolarSoft. Purchasing information can be found here.

Issue Personnel.csv file fails to import into Continuum No error message is shown Product Line Andover Continuum Environment Continuum access control Keywords: CSV, Import, cardholder, personnel Cause CSV file gets modified by MS excel such that the import fails During the process of manually changing and saving a personnel.csv file within MS excel, a number of commas are added to the first line (corresponding to the number of column fields in the CSV) Resolution Use notepad or similar to delete commas before importing into Continuum as Microsoft Excel does not show up any trailing commas This will NOT import correctly Personnel,,,,, Name,FirstName,LastName,CardNumber,CardType,SiteCode Smith_Fred,Fred,Smith,10,Infinity_37,3701 This will import correctly Personnel Name,FirstName,LastName,CardNumber,CardType,SiteCode Smith_Fred,Fred,Smith,10,Infinity_37,3701 For more information on CSV imports Click Here For an example .csv file for testing Click Here Note: If importing X Driver points using a .csv file the comm port attribute "Port" must always be defined before the X Driver parameters Param1, Param2 etc. The Port must contain the full path e.g. "Network1\CXName\Comm1" Example X Driver Numeric: InfinityNumeric Name,Alias,Format,Description,Port,Param1,Param2,Param3,Param4 XDRPoint1,XDRPoint1,##,First X Driver Point,Network1\CX1\comm4,1,3,10001,1

Issue SLP BACnet Setpoint limits Product Line EcoStruxure Building Operation, Andover Continuum, Field Devices Environment SpaceLogic SLP Series Cause The BACnet Object "Temperature Setpoint" includes properties Minimum and Maximum values These can be used to limit the setpoint, however the values are not saved in non volatile memory, thus the value revert to default after a power cycle (0 and 50 degC). The Setpoint object needs to be manually downloaded from EBO following a power cycle to set these properties. These properties cannot be written to individually. Thus changing these properties is unlikely to be good practice. Resolution A script program can be used to set limits to the Temperature Setpoint. Example below Note the "Value transfer settings" need changing to "Transfer value each time..." as below

Issue Experiencing issues with I/O modules that may include: Backplane failure causing modules to assume wrong module ID Input filtering problems on RTD modules Stability due to electrical noise Product Line EcoStruxure Building Operation Environment EcoStruxure Building Operation StruxureWare Building Operation Automation Server I/O Modules Cause The latest I/O module firmware version will correct known issues while also ensuring that the system is up to date and compliant. Resolution The latest I/O module firmware can be located on the Exchange by searching for I/O Module firmware. Each firmware download zip file will contain a ReadMe file that explains what was corrected in that version.  Refer to Upgrading SmartStruxure IO Module Firmware for the procedure to upgrade the I/O module firmware. 

Issue Can the xPBD4 be used with an i2 or b3. Environment xp Expansion Module Cause Is the xPBD4 compatible with an i2 or b3. Resolution No. The following note is from the xP Expansion Datasheet: The xPBA4 and xPBD4 Expansion Modules can only be connected to the bCX1 Controller/Routers and ACX Series Access Controllers. The other xP expansion modules do work with the i2/b3 controllers. See the attached data sheet for more info.

Issue TAC Vista database export/import. Description texts are missing when the .zip file is imported. Product Line TAC Vista Environment TAC Vista Server TAC Vista Workstation Export/Import Cause Changes to the object description text fields made in TAC Vista Workstation are not automatically saved in the .mta file. Resolution To make sure that the description texts will be included in a database export (physical structure only): Edit the Xenta application with text description fields added or modified through Workstation. Save the Xenta application to the database. If you do this, the description text will be written in the .mta file and will be included in a database export.

Issue  Interstation links between UNC and Enterprise Server are not functioning. Product Line TAC IA Series Environment Windows 7 Windows Vista Windows XP Niagara R2 Cause Windows Firewall is enabled by default on desktop operating systems post Windows XP SP1. The Windows Firewall must be configured to allow unsolicited messages such as alarms and inter-station links from UNC's to be received by the Enterprise Server. Resolution WINDOWS FIREWALL OVERVIEW Windows Firewall is a “state-full packet filter” firewall by default. This means that all TCP packets trying to enter a system with the Windows Firewall enabled will be discarded unless those packets are responses to queries from that system, or if the packet is destined for a port that has an exception create for it. In other words, unless an exception is created, or the Windows Firewall is disabled a valid message such as an alarm or an inter-station link from a UNC will be blocked by the Windows Firewall and won’t be received by the Enterprise Server. Windows Firewall allows for exceptions to be created for particular ports and from particular ranges of IP addresses. For example, one could create a rule that accepts unsolicited packets on port 25, but only from the range of addresses from 192.168.0.1 through 192.168.0.254. There are two kinds of exceptions: program exceptions and port exceptions. A program exception is where the Windows Firewall is instructed to open ports that a certain program needs for unsolicited communications. This is the preferred method since Windows Firewall is only open while the program is waiting to receive the connection. In contrast, a port exception is the Windows Firewalls' way of acting like a port-filtering router. In other words, Windows Firewall can be configured to let in any traffic on a particular port whether it's solicited or not. Creating a Program Exception Windows XP Open Windows Firewall from the Control Panel and from the exceptions tab click "Add Program..." Click the browse button Navigate to the c:\Niagara\Version\Nre\Bin folder. Select the file “nre.exe” adding it to the list of programs. To specify which TCP/IP devices can use the port, click Change Scope and select one of the following To allow connections from any device, including those on the Internet, select “Any computer (including those on the Internet)”, and then click OK. (This is the default and least secure option) To allow connections from your local subnet only, select “My network (subnet) only”, and then click OK. (This is more secure than the previous option but will still allow a malicious attack from a PC on the network) To define a custom list, select “Custom list”, and then type a list of IP addresses separated by commas. (This is the most secure option) Click OK. The program will appear selected on the Exceptions tab under Programs and Services. Click OK to finish. Windows 7 Open Windows Firewall from the Control panel then select Advanced Settings: Right click Inbound Rules and select New Rule Select program and click Next. Click the Browse button Navigate to the c:\Niagara\Version\Nre\Bin folder. Select the file “nre.exe” and click Open to add it to the list of programs. Click next. Select Allow the connection and click next Select the Network profiles that the rule applies to and click next Domain The domain profile applies to a network when a domain controller is detected for the domain to which the local computer is joined. If you select this box, then the rule applies to network traffic passing through a network adapter connected to this network. Private The private profile applies to a network when it is marked private by the computer administrator and it is not a domain network. Newly detected networks are not marked private by default. A network should be marked private only when there is some kind of security device, such as a network address translator or perimeter firewall, between the computer and the Internet. The private profile settings should be more restrictive than the domain profile settings. Public The public profile applies to a network when the computer is connected directly to a public network, such as one available in airports and coffee shops. The public profile settings should be the most restrictive because the computer is connected to a public network where the security cannot be as tightly controlled as it is in an IT environment. Name the exception and click Finish Creating a Port Exception Windows XP Open Windows Firewall from the Control Panel and from the exceptions tab click "Add Port..." In the Port number field type 80 Select TCP. Type a short name for the port To specify which TCP/IP devices can use the port, click Change Scope and select one of the following. To allow connections from any device, including those on the Internet, select “Any computer (including those on the Internet)”, and then click OK. (This is the default and least secure option) To allow connections from your local subnet only, select “My network (subnet) only”, and then click OK. (This is more secure than the previous option but will still allow a malicious attack from a PC on the network) To define a custom list, select “Custom list”, and then type a list of IP addresses separated by commas. (This is the most secure option) Click OK twice. The Port will appear, selected, on the Exceptions tab, under Programs and Services. Repeat the procedure to add an exception for port 3011 Click OK to finish. Windows 7 Open Windows Firewall from the Control panel then select Advanced Settings: Select  Connection Security Rules: From right side menu, select “New  Rule” Select Rule Type then select Custom then click Next: Select “Protocol and Ports” then select the TCP protocol type, specify required ports, then click Next. This screen capture     shows the configuration for the I/A Series (Niagara) R2 required ports: On the “When does this rule apply screen, click Next, leaving all three areas checked. On the next screen, name the rule “Niagara 80, 3011 TCP” and click “Finish”. Repeat steps 3 through 7, above, selecting UDP instead of TCP.  All other entries are the same except in step 7 the rule name will be UDP instead of TCP. After completing step 8, the Connection Security Rules will be displayed in the center section of the program window.  You should see the following two rules:  

Issue Configured Loytec LConfig application as a service but still do not get communication from the LonWorks Network. Not able to get Service pin from LON devices connected with Loytec NIC from Enterprise Server Product Line EcoStruxure Building Operation Environment Enterprise Server 1.1 Loytec NIC852 (LConfig Tool) Windows 7 Cause LConfig tool version is too old. The LConfig tool, even if set to start as a service, also still needs to start before the Enterprise Server (ES), otherwise the Enterprise Server fails to establish its connection with the LonWorks interface. For information on how to set LConfig to run as a service refer to Not able to get Service pin from LON devices connected with Loytec NIC from ES. Resolution To rectify the cause 1, click here to verify if the LConfig version is the most recent one. If not please download the most recent NIC - LOYTEC Network Interface Software. To rectify the cause 2, you must set the Loytec (LConfig) application service to be a dependency of the Enterprise Server (ES), to do this follow these instructions: Using RegEdit (or similar) edit the Registry Key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\StruxureWare 1.1 Enterprise Server NOTE: For SmartStruxure version 1.3 and above, go to path: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\Building Operation 1.3 Enterprise Server Locate and edit the DependOnService string Add the text LoytecSrv (service name for the LConfig application). Close the editor and reboot the PC Note: When running the LConfig as a service the LConfig Tool is not available from the System Tray and must be started from the program shortcut, located under Start > Programs> LOYTEC Network Interfaces> LConfig As a quick visual check, to see if configured correctly, you can perform a LonWorks Device Discovery on your Enterprise Server, this will show the NIC which has been defined with a red box (see image below). If these are all blue then you will not be able to receive any communications from your devices. Also remember if using the Loytec LIP devices that these should be configured in Smart Mode.

Issue How to protect an OAT sensor from the sun? Product Line Field Devices Environment Outside Air sensors, Outdoor Temperature Sensor STO100 System Vista, Xenta STO200 System I/NET STO500 System Continuum STO600 System Satchwell STO600D System Drayton STO300 Outdoor temperature transmitter ETO100, ETO200, ETO500, ETO800 Cause Direct solar heating will affect the outside temperature reading. Resolution We do not supply sun shields for an Outside Air Sensors as there should never be a requirement to fit one. The Outside Air Temperature sensor for a building should always be fitted to the North side of the building where it will not be in direct sunlight (or the South side in the southern hemisphere). The temperature on the East, South or West sides of any building will always be higher than the North side (in the northern hemisphere) and give inaccurate readings if the sensor is mounted there. Also any sort of sunshade will also act as a shield to retain the heat also giving an erroneously high reading. For sites like weather stations where the measurements are to be taken in a field installation a Stevenson screen could be used, these are available from specialist instrument suppliers. A web search should provide local suppliers. Also see Recommended locations for Temperature Sensors, Valves, and Actuators for further details on sensor location.

Issue This video details some of the troubleshooting and diagnostics tools available in the Macrovision/Flexnet License Server LMTools. Product Line TAC Vista Environment LMTools Cause See below for a video tutorial of LMtools diagnostic utility overview.   Resolution

Issue Alarm queue in the Vista Workstation states "No license for LonWorks communication" Product Line TAC Vista Environment Vista Workstation Cause The simplest cause of the issue, and the one that should probably be checked first, is that the license for LonWorks communication was not present at the time the server was started.  Oftentimes, this is due to starting server, realizing the engineering or end user dongle was not plugged in (or license server was not started) and then plugging it in.  The server will not actively poll for this license, it must be present at startup. Resolution Stop the Vista Server Ensure the license dongle is plugged in, or the license file is activated and installed on the license server. Restart the Vista Server Related Articles: "No license for LonWorks communication" with TAC Vista Server LE "No license for LonWorks communication" error when using a non LE dongle "No license for LonWorks communication" - LonMaker Recovery Folder "No license for LonWorks communication" error message in Classic Network "No license for LonWorks communication" Error in Windows 2008 Server X64 TACOS startup delay utility

Issue Clicking a graphic page link fails to open any graphic page, but when opening the path using the System Tree of the server that contains the graphic page, successfully allows the link to open the graphic page. When opening the same page using WebStation, the graphic pages all open successfully. Product Line EcoStruxure Building Operation Environment Building Operation WorkStation 1.9.x or below. Cause Typically having 'dead links' or unresolved binds in any graphic page is the reason for the issue. WorkStation pre-loads all objects of the references to the graphics. This call (CSP GetObjects) fails since (at least) one path of the objects points to a server that does not exist. Unfortunately the protocol can't return the objects that do exist and WorkStation then marks all these objects as non-existent and fails to open the respective binding. This operation cannot be corrected in this version of WorkStation and requires an upgrade to 2.x or above to correct this. Resolution Two options are available Correct/remove all link bindings that are shown with unresolved references to invalid server paths. Example showing an Unresolved Binding Upgrading to Building Operation 2.0 or higher will also resolve this issue.

Issue Unable to use plug-ins to configure devices in LonMaker or NL220, even after installing the DRF kit. Product Line TAC Vista Environment LonMaker NL220 Device Plug-in Cause The DRF (Device Resource Files) kit is not installed before devices are added in Lonmaker or NL220 (and other tools) Resolution The DRF kit must be installed and properly registered in the PC before any devices are created. If you are in this situation you will need to remove all devices and the device templates and you need to start all over. It is therefore recommended that the DRF kit are installed before adding any device and that you create one device and test the plug-in to make sure that the DRF kit are properly registered before adding a number of devices into the database.

Issue The TAC Xenta group master is online but not the other Xenta devices in the group. Product Line TAC Vista Environment TAC Vista 5.1.x Classic network Menta 5.1.x Cause The TAC Xenta Group Master is a TAC Xenta 301/302/401/901 (in the TAC Xenta Group) that monitors the on-line and off-line status of the TAC Group and its members. The Group Master forwards the on-line and off-line information to TAC Vista. If devices have been added it's possible that  the current group isn't updated. Resolution The entire Xenta group must know it has a new device for proper communication to occur. To accomplish this download the applications and parameters to the entire group.  If the Group master goes offline, the whole group will be considered off-line by TAC Vista. The separate on-line group members, however, can send alarms and other information directly to TAC Vista as usual. Information about resolving this issue with an LNS network can be found in Xenta Programmable Device is Offline in Vista but Online in LonMaker.

Issue How to find out the Continuum serial number if it cannot be seen on the key or software licensing is used? Environment Cyberstation Security Key, Dongle Software licensing Cause When upgrading features or version on a Continuum system the Serial Number is required by Order Entry / the factory to process the upgrade and generate the upgrade file. If using software licensing or the number is not on the workstation key, it can still be found using a separate application. Resolution Run the application "CyberKeyWriter2.exe" that can be found in the Program files \ Continuum directory on the workstation (or WebClient Server). The following screen will appear showing the serial number:

Issue Is there a limit to the number of read/writes available for a BACnet Setpoint object? Environment WorkPlace Tech versions 5.1 and later Cause Not applicable Resolution The BACnet Setpoint object (analog or binary) is used for writing setpoint values to a controller, where it is stored in EEPROM. Observe normal precautions to avoid frequent writes to EEPROM. Excessive writes (typically greater than 100,000) can greatly shorten the life of the EEPROM and adversely affect its reliability. The BACnet Setpoint Priority object (analog or binary) represents a Value BACnet object type, of which the data is read-write accessible. This object can be used to write data to the controller. The Setpoint Priority object provides access to temporarily stored application values, usually setpoints or setup values, that are stored in RAM.  These setpoint values can be monitored and changed via BACnet communications, using the BACnet priority array.  When written from WP Tech, the default value is written to the priority array “relinquish default” location. Only this default value is stored in EEPROM. For more information, refer to the WorkPlace Tech Tool Engineering Guide Supplement (F-27356)