Building Automation Knowledge Base

Issue Calculation for converting static air pressure to cfm Product Line TAC INET Environment INET HVAC Site Cause What are the calculations for converting static air pressure to cfm? Resolution SRVP ("water column") * 4005 = FPM (feet per minute). The second calculation is FPM * AreaFtSQ (size of box) = CFM You will need an airflow monitoring device and duct static pressure sensor to measure SRV P (v of Vs of P).

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 for assistance. Issue Error: "Could not create remote directory" or "Failed to establish connection with the target device" when trying to upgrade/downgrade a Xenta 5/7/9xx controller     Product Line TAC INET, TAC Vista, Satchwell MicroNet Environment Xenta Servers Xenta 511, 527, 527-NPR, 555, 701, 711, 721, 731, 913 XBuilder Cause This error can be caused by any of the following reasons: Trying to downgrade a Hardware version 2.x Xenta Server device to System Program version 2.10 or older Internet Options are configured to use a proxy server IP communication is not properly established due to incorrect IP settings, a bad cable or a faulty device The controller is 5.1.8 or lower and Microsoft KB 2661254 or KB 2661254-V2 is installed on the PC. In this upgrade Microsoft has changed the criteria for the certificate Key. Service packs are available on the extranet to correct this issue. Download blocked because of other Windows updates SSL 2 and 3 is not activated Resolution First, establish that the System Program that you are attempting to load is compatible with hardware version of the device. The older HW 1 versions can be upgraded to System Program 5.1.2 or older. Only system program versions 2.2.0 and newer can be loaded into devices that are hardware version 2.X. Hardware Version System Program 1.0 5.1.2 or older 2.X 2.2.0 or newer 3.X 5.1.6 SP1 or newer Note: Hardware version 1 devices are not labeled as HW 1 since only one version of hardware existed at the time. Hardware devices can be identified by the lack of any hardware version printed on the Neuron ID sticker. Note: If running the firmware update software, ensure you are running as an administrator. Next, check to verify that IP communications are configured properly and are functional: Check the IP address defined in XBuilder Verify a good connection to the IP port of the controller (10Base-T port on the far right) with a crossover cable. If that is all good, then a reformat of the controller may be necessary. Connect via Hyperterminal to the unit and at the dsh> prompt type format and press enter command . This will recreate the directory structure of the controller and allow you to attempt the upgrade/downgrade again. Finally, verify that the Internet Options are not configured to use a proxy server or, if they are, temporarily change them as follows: To temporarily change this setting follow these steps: In Internet Explorer select the Tools Menu and select Internet Options. Or select Internet Options from your Control Panel. Go to the Connections tab. Click the LAN settings button. Uncheck the Use a proxy server for your LAN box. Click Ok in the LAN settings window and the Internet Options window. Complete the System Program download. Return to the Internet Options window and re-check the Use a proxy server for your LAN box in the LAN Settings found in the Connections tab. Another Matrix explaining the compatibility of each with Vista versions can be found in Xenta-Server-firmware-versus-Vista-Server-versions If you have the Xenta FW 5.1.8 or lower and KB 2661254 or KB 2661254-V2 were installed during a Windows Update you will need install the service packs. These new service pack builds have been released and are available on the extranet. See TPA-VSTA-12-0028.00 - TAC Xenta Servers, Not Possible to Download Firmware for more info. Another issue has been reported to support relating to the bit length of the Xenta server boot certificate. The Xenta server installer uses a 512 bit key length of the boot certificate, and Windows in some instances can be configured for a 1024 bit length certificate. If the issue still exists after removing the above mentioned Windows Updates, or if you are getting this error and the Windows Updates are not on your machine. Download the attached tool, Allow Weak Certificates.zip, and execute the file, chose "Allow Weak Certificates", and "Update".   Here is what the tool set: Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Cryptography\OID\EncodingType 0\CertDllCreateCertificateChainEngine\Config] "EnableWeakSignatureFlags"=dword:00000002 "minRSAPubKeyBitLength"=dword:00000200 If taking the preceding steps fails to resolve the issue then see the following articles for additional steps that can be taken: Xenta Server "Run" light is solid red, with no communication via Ethernet,  Fail to upgrade the TAC Xenta Server system software (firmware)  An unexpected error occurred while downloading using a Xenta Server

Issue Need to mirror a switch port in order to capture controller data with Wireshark.   Product Line Access Expert, Andover Continuum, EcoStruxure Building Expert, EcoStruxure Building Operation, TAC IA Series, TAC INET, TAC Vista Environment NETGEAR Prosafe Plus Switch Cause Need a step-by-step guide to set up a mirrored port and an understanding of how it works.  Resolution View the attached video.   Use the link to the original post in Area360 to get written instructions.

Issue Running I/NET Seven as a service on Windows Product Line TAC INET Environment I/NET Seven All supported Operating Systems Cause When you log out of Microsoft Windows or restart the computer, all running processes are shut down. These processes are not resumed at log on or at restart. You have to start I/NET manually again. To get I/NET to start up when the computer restarts, you can run it as a service. Running a program as a service means that it runs in the background, but it is not visible on the Windows task bar. Resolution Use the INET Run Mode tool available on the Community.  Alternatively, you can perform the following steps to set/unset the InetIoSrv.exe as a service or application. To register I/NET Seven to run as a service Open a Windows command prompt. Go to Start > Run and type "cmd" Use right-click on the command prompt and select "Run as Administrator" Use commands cd.. (to go back one directory) and cd (to go into a folder) to navigate to the following location: C:\Program Files\INET Seven\ If this is being run on a 64 Bit OS, the location then would be: C:\Program Files (x86)\INET Seven\ Type the following command. This will unregister I/NET as an application inetiosrv /unregserver Type the following command. This will register I/NET to run as a Windows service inetiosrv /service To verify the changes have taken effect Right-click on "My Computer" and select "Manage" Select Services and Applications > Services Look for Inet7Iosrv. It should be set to Automatic. You are now running I/NET as a service. IOSrv will now be running in the background when the PC boots up. This does not require a Log On to the PC, however, you will have to Log On to the PC as a user to launch I/NET or AMT from the desktop icon. You will notice that IOSrv has been logging all AMT transactions, messages and alarms. The SQL Server and Agent were also running in the background receiving data to the database. To set I/NET back to running as an application Open a Windows command prompt. Go to Start > Run and type "cmd" Use right-click on the command prompt and select "Run as Administrator" Use commands cd.. (to go back one directory) and cd (to go into a folder) to navigate to the following location: C:\Program Files\INET Seven\ Type the following command. This will unregister I/NET as a service inetiosrv /unregserver Type the following command. This will register I/NET to run as an application inetiosrv /regserver

Issue What is the recommended method to upgrade a Niagara R2 station to a newer version? Product Line TAC IA Series Environment I/A Series Niagara R2 Cause Unsure how to upgrade station databases. Resolution The published upgrade procedure is provided in F-27334. Below is a modified method that also works. Doing station upgrades on the server first is preferred. If there are any errors, they can be addressed without operational interruptions. Using the existing version of WorkPlace Pro (WPP), backup ALL of the UNC and Server databases into XML format. Methods of backing up and converting databases. Open the Enterprise server in WorkPlace Pro. Double click the station name. Select "Commands" and "Backup XML to save the server in XML. Then select "Backup Subordinate XML" to pull all of the UNC databases as XML into the server stations folder.   If not on site but the UNC and Server databases are available, use the DB Admin tab of the Admin tool to convert the databases locally to XML. Now install the newer Niagara revision onto the Server. Copy the stations containing the XML files to the desired WPP revision station folder. Enable and open the new revision of WPP. Use the Admin Tool to convert locally all of the stations from XML to DB. (If there are any errors, they can be addressed without affecting the running installation.) After all the databases have successfully converted to DB, convert them to SNS. (This saves time later if the UNCs need reloading) Use the Enterprise Server to upgrade the UNC. During the upgrade process of the UNC it will ask to backup the database. If the database had upgraded with no issue in the previous step, enter the username and password to proceed with this backup. This will backup the station, upgrade the UNC, and then upgrade and reinstall the station. The previous station upgrade will be needed only if there is an issue. If after following this procedure the station still fails to start, contact Product Support Services.

Issue Receive "Initialization error" when trying to start I/NET with SQL 2008 When we installing SQL Server 2008 Standard for I/NET Filemaster, what are the main components we should include? When editing / adding a new I/NET Configuration Profile the Database Server section is blank DBCreate does not start.  Appears in task Manager but no user interface is shown. Within DBCreate the restore option is grayed out Product Line TAC INET Environment I/NET Seven 2.4x Microsoft Windows Server 2003, Windows XP, Windows Vista, and Windows 7 families of operating systems. (both 32 and 64 bit) Microsoft SQL 2008 Standard or Express Editions Microsoft SQL 2008 R2 Standard or Express Editions Cause I/NET must have the SQL 2005 Backward compatibility file installed.  If this is not installed I/NET will not locate the SQL Server and hence will issue an “initialization failure” error.  This is can also be identified in either the DBCreate or I/NET Configuration application editors which will show no entries in their "Database Server" settings. The document also details information that is necessary for a Standard or Express editions of SQL 2008 / SQL 2008 R2. Resolution Follow the instructions below extracted from the document called "SQL2008 Expr Install Inst.pdf".  This document is found on I/NET Seven CD under the 'SQLExpress' folder.  For SQL 2008 R2 installations refer to the following document SQL2008 R2 Expr Install.pdf, also found in this same folder .  Installing SQL Server 2005 Backward Compatibility SQL Server 2005 backward compatibility must be installed for SQL 2008. To install SQL Server 2005 Backward Compatibility Navigate to the SQLBcm directory on the TAC I/NET Seven installation CD. Launch the SQLServer2005_BC.msi file. Follow the prompts on each screen and accept all defaults. After the install check the SQL Server Services SQL Server Browser is RUNNING SQL Server (MSSQLSERVER) is RUNNING Check the SQL Server Network Configuration Protocols Enable Named Pipes Enable TCP/IP Completing the Installation Proceed with the installation of TAC I/NET Seven on your PC. For installation instructions, refer to TCON298, TAC I/NET Seven Getting Started. Note: Run Inetcfg.exe before starting TAC I/NET Seven for the first time. This is necessary to attach TAC I/NET Seven to the database and avoid an “Initialization failure” error. Note: Before file equalization will operate, the system must be rebooted or the INETEQZMERGE service must be manually started.   Also refer to Installing I/NET 2.42 or higher and Vista 5.1.7 or higher on a 64-bit operating system for additional details on installing I/NET with SQL 2008 R2.

Issue Temperature Sensor Location Valve Location Actuator Location Product Line Field Devices Environment Actuator Sensor Valve Cause Where to fit and locate field devices. Resolution Valves: If the valve is lift and lay type and the application is diverting, then the valve must be fitted in the return. If the valve is lift and lay type and the application is mixing, then the valve must be fitted in the flow. The rule of thumb for lift and lay valves is "2 ins and 1 out" Rotary (shoe) valves can be fitted in either the flow or return for either mixing or diverting applications. Use pipe unions, so that the valve can easily be removed. Actuators on Valves: If the heating medium is steam then the actuator/valve arrangement is not fitted vertically, tilt the valve/actuator to an angle so that heat can convect away vertically and the actuator is not subjected to as much heat. In all cases, do not fit the actuator/valve arrangement so that the actuator is vertically under the valve. If the valve leaks, it will damage the actuator. Temperature Sensor location, in both wet and air applications the sensor need to sense correctly the medium it is in. Where possible install in a location for easier maintenance e.g. at a height reachable from a fixed floor level. Pipe Temperature Sensors: The tip of the sensor needs to be in the core of the medium i.e. the centre. The sensor needs to be fitted where stratification does not take place or is reduced. This can be achieved by fitting after a pump or after a bend where turbulence provides a good mix. If the sensor is fitted on a bend, then the probe faces the flow of/oncoming water. In CHW applications, fit the pocket just off horizontal, so that any condensation forming in the pocket can drain away. Adequate insulation will prevent condensation forming in the pocket. If fitting vertically in the top of the pipe is unavoidable see Oil for the DWT0001 (or STP660) pocket sensor to prevent problems with condensation. Duct Temperature Sensor: Supply Air - If a probe type sensor is fitted, it needs to be ideally 3 meters downstream and in the centre of the duct from the supply fan and preferably after a bend fitted with turning vanes. Return Air - The temperature sensor needs to be fitted before/upstream of the extract fan. Frost Coils - Temperature sensor, due to the short distance available, probe sensors are difficult to locate, but try to be as far away from the coil e.g. on the other side of the pre-filter bank and in the centre of the duct/AHU. Even better is to use an averaging type temperature sensor. Frost Coils - Fan Hold Off thermostat. Allow sufficient capillary to cover the battery surface. Lace the capillary across the frost battery on the downstream side using the correct clips. If the thermostat body needs to be fitted on the external side of the AHU, then fit with the minimum of capillary on the external of the AHU. Use a grommet or stuffing gland to protect the capillary as it goes through the AHU skin. If the AHU is fitted outside or is in an unheated space then the thermostat needs to fitted internal to the AHU. Do not cut the capillary if it is too long. Tidy capillary ends so they do not flap in the airstream. Outside Temperature Sensor: Outside temperature sensors should be located correctly to the local region you are in and the application they are serving i.e. compensated outside sensor in the UK are fitted on a wall facing north. The sensor should not be fitted on flues, chimneys, near opening windows. They should not be fitted near to compounds containing plant expelling heat e.g. chiller compounds. The sensor should be fitted at a height that does not require the use of steps or ladders for maintenance. Room Temperature Sensor: Sensors should be fitted at an agreed height and not fitted on external walls, near opening windows and doors or above radiators. They need to be exposed to the area they are controlling and not be directly influenced by heat sources e.g. computers. Sensors with exposed setpoint adjust or controls need to be fitted at a lower height so that people with disabilities can adjust them. Sensors that are fitted onto partitioned walls or have a conduit need the hole plugging so that there are no draughts. Sensors that are fitted directly to concrete or steel beams should be packed out with a thermal insulating material. Valves and Sensor Wiring: Allow sufficient cable to allow removal of actuator or sensor without having to disconnect the device. See the full Building Controls Group - Control Sensor Installation guide.

Issue How to collect log files from the Project Configuration tool. Product Line EcoStruxure Building Operation Environment Project Configuration Tool Cause When contacting Product Support about issues with the Project Configuration tool, log files should be provided. Resolution Go to the PCT installation folder and run the program called LogCollector.exe located there. The default installation folder for versions 1.2 and higher is: "C:\Program Files (x86)\Schneider Electric EcoStruxure\Building Operation\Project Configuration Tool" and "C:\Program Files (x86)\Schneider Electric StruxureWare\Building Operation\Project Configuration Tool" for previous versions. Click Collect logs A program log of what LogCollector has done is displayed. A zip-file containing the collected PCT logs is created on the desktop.

Issue Is there support for the C-Bus protocol in StruxureWare Building Operation? How can we integrate C-Bus into StruxureWare Building Operation? Product Line EcoStruxure Building Operation Environment StruxureWare Building Operation 1.0, 1.1 and 1.2. Cause Requirement to integrate C-Bus protocol into StruxureWare Building Operation, Automation Server or Enterprise Server. Clipsal C-Bus integrated service provide two gateways (BACnet / OPC), that may provide a suitable integration option. Resolution StruxureWare Building Operation does not directly support the C-Bus protocol at this point. Currently Schneider Electric Buildings integration with the C-Bus protocol is typically through the Xenta 913 (See Tip and tricks for communication between Xenta 913 and C-Bus on how this is achieved). When Interfacing the Xenta 913 to the Building Operation offerings you must create connection objects to and from the C-Bus objects via SNVTs, which need to be separately created within the Xenta 913 XBuilder project. Once these SNVTs are exposed, then the Xenta 913 can be added on the LonWorks network allowing the unit to be discovered as a LonWorks device (i.e. only acting as a third party LonWorks device). There are also two offerings provide by the Clipsal Integrated Services division that can be integrated with Building Operation, these are:   1. C-Bus BACnet Gateway (5000BACnet) The C-Bus BACnet Gateway is an embedded device that provides a field bridge between Clipsal C-Bus lighting control systems and the BACnet open protocol. The C-Bus BACnet Gateway provides 255 group addresses from a single application address. The C-Bus BACnet gateway supports the reading and writing of BACnet objects between C-Bus and BACnet and is supplied pre-configured from the (Clipsal) factory. Below is the link to detail of the C-Bus BACnet Gateway (5000BACnet) https://www.clipsal.com/Trade/Support/Software   2. C-Bus OPC Server For larger C-Bus systems (i.e. >255 group addresses) then the C-Bus OPC Server provides a gateway for C-Bus and the OPC Data Access protocols. Current releases of Building Operation does not support OPC, so you will require either an OPC to BACnet or OPC to LonWorks application which can be purchased through third party vendors. SCADA Engine is the preferred Clipsal BACnet OPC Client solution used. http://www.scadaengine.com/ Even though this solution is focused on BACnet, it may also be possible for a similar solution using LonWorks. Below is the link to detail of the C-Bus OPC Server https://www.clipsal.com/Trade/Support/Software There are additional requirements for each of these options that may need to be considered, it is best to discuss these directly with your regional Clipsal representative.

Issue How to reset an existing EBO Licensing installation Product Line EcoStruxure Building Operation Environment Building Operation Licensing Cause Most of the time, issues with damaged or corrupted EBO Licenses can be resolved by simply returning and re-registering the affected License, either manually or with the help of Product Support. However, on some occasions, this is not enough, as the actual Licensing installation is affected.  Even re-installing the License Server does not fix the issue because of unwanted data left over in the registry. Resolution A License Server Reset Tool capable of partial or complete reset of an EBO License Server installation has been developed and available for download from the Community: SBO License Server Reset.

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 User of EcoStruxure Building Operation WorkStation used the "Remember me on this computer" option and logged into an account that does not have account rights to logout. Product Line EcoStruxure Building Operation Environment WorkStation Cause A situation such as this could happen either due to inattention of the user or because of planned system design (Kiosk with Building Operation WorkStation logged into a read only account). However it might be necessary due to maintenance to adjust the login option. In the absence of a kiosk situation, it is recommended to always leave the ability for a user to logout by only hiding the toolbar instead of disabling it. Resolution The solution can differ depending on the installation or usage scenario. User has access to log off option Once logged into Building Operation WorkStation use the log off option to return to the login prompt Uncheck the "Remember me on this computer" option. Enterprise Server on another computer or accessing an Automation Server Disconnect the Ethernet cable for the computer or disable the network port Building Operation WorkStation attempts to login returning user to the login prompt. Enterprise Server on same computer The Enterprise Server can be stopped temporarily and the next attempt to start Building Operation WorkStation will result in a communication failure allowing you to modify the "Remember me on this computer" selection. This could result in loss of data while the Enterprise Server is stopped. Delete the Building Operation WorkStation configuration file (named either SBO.ClientUserProfile.bin or TAC.ClientUserProfile.bin for older versions) stored in the computer application data. Deletion of this file will result in loss of custom settings such as column widths and similar customizations.

Issue What is the latest specification For a Continuum PC Product Line Andover Continuum Environment Cyberstation SQL Server Cause Computer specification required. Resolution The PC specifications for a version does not change from the time of release, so there is no "Latest Specification" as such. For all versions the hardware requirements are defined in the installation guide (Installation.PDF) on the software CD, or in the downloaded zip file from The Exchange Download Center for the version to be used. This document will contain the minimum and recommended specification required for that Cyberstation version on a typical site, if any other software is to be installed on the computer or the computer is to be heavily loaded; the requirements should be increased accordingly. The same RAM and Processor requirements will also apply to the SQL Server on a typical LAN system. You also need to check the Software and Firmware compatibility matrix for older versions of the traditional product lines for details on the compatible operating system requirements for the version to be used. For a V2.01 system the recommended hardware for servers and workstations are: Intel 8 Cores, 2 GHz or better 8Gb RAM 30Gb Available HDD space (NTFS Partition) CD ROM Drive Video resolution: 1024 x 768 pixels Parallel or USB port For larger systems and where there will be a lot of Extended logging or Alarming, the Hard drive, RAM size and processor speed should be increased.  

Issue When attempting to register a system, an error page is shown indicating a server error in the /ebo application   Error Text: Runtime Error An application error occurred on the server.  The current custom error settings for this application prevent the details of the application error from being viewed remotely (for security settings).  It could, however, be viewed by browsers running on the local server machine.  Product Line EcoStruxure Building Operation Environment WorkStation Registration Windows Server 2012 R2 and above Cause While the error message points to an error in the back end server, it is actually due to a setting on the client PC. Enhanced security configurations in Internet Explorer on Windows Server systems, is blocking required content from being run. EcoStruxure Building Operation WorkStation uses Internet Explorer as the built-in browser and is therefore affected by this. Resolution While the enhanced security measures can be disabled altogether, the resolution with the smallest impact is to add the URL of the registration portal to trusted sites in Internet Explorer. Open Internet Explorer Open Internet Options Select the Security tab Click Trusted Sites Click Sites Enter the registration portal URL: https://registration.smartstruxure.schneider-electric.com Click Add Click Close Click OK After doing so, restart WorkStation, and attempt the registration again. For more information, refer to the WebHelp topic EcoStruxure Building Operation Registration Page is not Displayed.

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 Upgrading the MPMs firmware through the boot loader was unsuccessful. 10.50.80.2 is pingable, but not the default IP 10.50.80.3. The LED's keep blinking in tandem (alternating one after the other), even after having the MPM powered over 10 seconds. Product Line EcoStruxure Building Expert Environment SmartStruxure Lite Multi-Purpose Manager Cause This can be triggered by multiple events: - MPM was interrupted (powered off) while the firmware was still being upgraded. - Database does not exist; MPM was formatted and does not have firmware installed. - Database is corrupt (for any reason) Resolution It is strongly recommended that a firmware upgrade be done via the "File Manager" tab in Building Expert. However, if this is not possible, an upgrade can be performed through the bootloader using the following steps: 1 - At the top left part of the screen, make sure "Status" says "Connected". 2 - Format the SD card clicking on the "Submit" button next to "File System Format". "Format Done" will be displayed next to the button once the format has been completed 3 - Click on the "Browse" button and Navigate to the Firmware_update_V2.XX.bp" on your computer then click on "Submit Query". 4 - The previous step will upload the firmware file to the MPM's SD card. Once the file has been transferred, the following message will appear: or 5 - The MPM Must be kept powered-up for at least 15 minutes in order to allow the MPM some time to unpack the firmware file. The best way to determine whether the MPM is back online is to ping its IP address using a "Command Prompt" window. 6 - Once the MPM replies to the ping, Building Expert can be accessible though 10.50.80.3   If the above solution does not work; meaning that every time a new firmware is pushed to the MPM, the MPM keeps coming back to the bootloader, contact technical support

Issue Steps on how to setup BACnet Time Synchronization to 3rd Party BACnet controllers. Product Line EcoStruxure Building Opertaion Environment SmartX Enterprise Server (ES) SmartX Automation Server (AS) BACnet Cause It is not always clear what is required to setup BACnet Time Synchronization and how to confirm that EcoStruxure Building Operation is actually performing it properly. Resolution To use the Time Synchronisation you will need to bring the 3rd Party BACnet device (Eg. Continuum bCX) under the EBO BACnet Interface -> IP Network: Go to the BACnet Interface Time Synchronization Recipients Tab. Add a new Local time synchronization recipient with the '+' button. Select recipient type as 'reference' In the Recipient device object reference field browse for your BACnet Device. Press OK and then save the changes. Right-click on the BACnet Interface and select send time sync now. This will send out an unconfirmed-req TimeSynchronization to that specific Device only.   Test Scenario with a bCX setup as a third-party BACnet controller You will see a unconfirmed-req TimeSynchronization packet being sent from the ES in WireShark but with no response from the bCX.  You may not see responses back from other 3rd party devices. The time in the bCX should be seen to change from within Continuum, (assuming it was incorrect in the first place) 

Issue How can a BACnet b4920 be reset back to its factory default IP address? Product Line Andover Continuum Environment BACnet b4920 Cause There is no Reset IP switch on the b4920 Resolution There are 2 ways of accomplishing this.   Method One - The first method resets the controller to factory default address settings: IP Address: 169.254.1.1 Subnet Mask: 255.255.0.0 Gateway: 0.0.0.0 Webserver Port: 80 Web User Name: acc Web User pwd: acc EnergyNet ID: 1 BacNetMstpNetId: 2764 BacNetUDPNetId: 2765 During controller startup, there is a 2 minute window in which the controller will be restored to factory defaults based on the following: Seconds since startup is < 120 A Ping packet is received by the controller with a matching Ethernet address but unmatched IP address. Ping payload size of 255 bytes. Prior to running the procedure, the controller must be on the same network as the PC that that is used to issue commands.  The engineer will need to have on hand (1) IP address that is both valid and NOT in use on the network that the PC and Controller are connected to.   Get the Controller's MAC Address Each controller has a 6 byte hardware address, also known as the MAC address or Ethernet address. The address is represented in HEX. The first three bytes of the MAC address are constant and represent Andover Controls vendor ID : 00-40-11 The last 3 bytes of the MAC address are derived from your controller’s serial number. The controller’s serial number is printed on the board and is represented as an Integer value. You must convert this value to HEX in order to obtain the last 3 bytes of your controllers MAC address. Ex. Integer Serial Number: 1033394 Converted to Hex: FC4B2 Controller’s MAC: 00-40-11-0F-C4-B2   Create a batch file Create a batch file named Acc.bat with the following content: arp -s %1 %2 ping -l %3 %1 arp -d %1   Restart the b4920 Controller Within 2 Minutes of restarting, run the batch file with the 3 arguments: Acc.bat IP_Address 00-40-11-XX-XX-XX 255 Where IP_Address = valid IP on the network Where XX-XX-XX = last 3 bytes of controller’s MAC Where 255 = Ping Payload size   After Issuing the command, the controller should restart, and the factory default address settings are restored.    Method Two - Capture the Controllers Currently Configured IP Address This second method is easier to do and is currently recommended because of its ease. Download and install a network sniffing application, such as Wireshark which can be downloaded from their website here. Connect a Cross over Ethernet cable between the b4920 and a PC running the network sniffing application. Start up the network sniffing application and then reset the b4920 by hitting the reset button on the controller. On start up, the controller will send out the IP address (Gratuitous ARP Packet) which it currently has assigned to it.  Once this IP address is captured with Wireshark etc the IP of the Workstation can then be changed to allow connection to the controller's web configuration page to change its IP address as required.  

Issue What is the correct procedure for replacing a Continuum bCX 4040 controller Product Line Andover Continuum Environment CyberStation bCX 4040 Cause Considering both Continuum and BACnet 'sides' replacing a bCX4040 can seem a complicated process. Resolution Commission new/replacement bCX through its default webpage just as the as old bCX except for the BACnet Configurable Properties section. Set the BACnet Device ID = The same ID in the old bCX (serial number of controller by default) Set the BACnet Port Number UDP = same as old bCX (BAC0 by default) Set the BACnet Network ID UDP = same as old bCX (1 by default) Set the BACnet Network ID Comm2 = same as old bCX (2765 by default) Set the BACnet MAC ID Comm2 = Same as old bCX (0 by default) Set the BACnet MS/TP Enhanced Mode = Same as old bCX (TRUE by default) Set BACnet BBMD Enabled/Disabled = Same as old bCX (False by default) Bring the bCX online in Continuum Explorer, Select menu item Options | Send to Controller options Select "Reload attached objects, but not attached controllers" - select ok Verify the bCX Comm2 settings and baud rate speeds. In Continuum Explorer, right click on the bCX and perform a "send to controller" Verify points and communications.

Issue The Enterprise Server service keeps stopping, and Windows restarts it right away. This is preventing WorkStation or WebStation from logging on. When viewing the Building Operation Software Administrator, the "Start Service" option is greyed out, and the server status is Stopped. Product Line EcoStruxre Building Operation Environment Building Operation Software Administrator Building Operation Enterprise Server Building Operation Enterprise Central Building Operation Workstation Cause The Enterprise Server or Central service uses TCP port 80 by default.  If another service on the PC is using port 80 (e.g., Internet Information Services), this will cause the service to stop and re-start constantly. Resolution Two options: Stop the conflicting service from running (e.g., IIS, Dropbox, Skype) Change the HTTP or HTTPS port in Enterprise Server or Enterprise Central to a unique port (e.g., 8080) To change the ports, open Software Administrator and stop the server if it is not already. Then the port fields will no longer be grayed out, and they can be changed. Finally, restart the server. Refer to: Configuring Server Port Settings Note: Once the port has been changed to a unique one, this must be specified when logging into WorkStation, as seen below.

Issue Procedure for installing PCC-10 or PCLTA20/21 network cards on a Windows 7 PC Product Line TAC Vista Environment Vista Menta LonMaker Windows 7 Cause Installation procedure differs from earlier versions of driver software. Resolution The PCC-10 and PCLTA-20/21 network cards work on Windows 7 (32 bit) PCs when the OpenLDV 4.0 driver is installed. This driver is installed automatically when Lonmaker Turbo SR4 is installed, but if this version of Lonmaker is not present the driver must be installed manually.  The latest drivers can be obtained from the Echelon download site: http://www.echelon.com/support/downloads Note: The PCLTA-20/21 card is only supported on 32bit windows operating systems. For 64bit systems use a NIC-USB as mentioned in this article: Computer will not recognize NIC709-USB. Install the drivers before fitting the card in the PC. Please note that OpenLDV4.0 requires .NET Framework 3.5 SP1.  This is not included as a subset of .NET Framework 4 or later, so must be installed separately.  You can have multiple versions of .NET framework installed on the same PC. The following description is for the PCLTA-21 but the PCC-10 is similar. To change the system image or perform diagnostics, you must go to Control Panel and open the Lonworks Interfaces application: Click Start on the taskbar, point to Settings, click Control Panel, and then open the LONWORKS Interfaces application. Click the PCLTA-21 interface in the list view on the left side of the user interface to display the interface's properties in the details pane in the right side. The details pane lists the PCLTA-21 card's system image and transceiver properties. To change the system image used by the PCLTA-21 card, click anywhere in the NI Application property, click the box to the right, and then browse to and select the desired system image from the LonWorks\Images\PCLTA21 folder. Note: For more information on configuring, testing, and diagnosing the PCLTA-21 network interface, see the LonWorks Interfaces online help.

Issue When using mstpcap.exe to capture, it automatically stops after 65535 packets. Similarly, when using Wireshark, it will stop capturing if the dissector encounters an issue. This article provides a solution to continuously capture BACnet MS/TP traffic in a ring buffer and store it as files. Product Line Andover Continuum, EcoStruxure Building Operation, TAC IA Series Environment Wireshark Any BACnet MSTP RS-485 network Cause Analyze BACnet traffic via capture files. Resolution Install Wireshark. Ensure TShark is checked when installing options.  Ensure Wireshark is installed with Npcap (default) or WinPCap has been installed by IA Series Workplace Tech. Install mstpcap.exe referencing BACnet MSTP Capture Application. Ensure that mstpcap.exe has been configured for the correct port and baud rate. Here is an example for Command Prompt and PowerShell: # Command Prompt cd "C:\Program Files\Wireshark\extcap" mstpcap.exe com3 38400 # PowerShell cd 'C:\Program Files\Wireshark\extcap' ./mstpcap.exe com3 38400 Run Tshark to determine the interface being used by mstpcap so that one can reference it by number. For this example, we are going to choose 9. COM3 (BACnet MS/TP on COM3). Please change the number below to the number of your interface.  Start Tshark capture by entering the following command, updating as needed. The commands below save Test01.pcap to the Username's desktop. Please store to a location that the user has access to write.  # Command Prompt cd "C:\Program Files\Wireshark" tshark.exe -i 9 -b duration:3600 -b files:72 -w "C:\Users\Username\Desktop\Desktop\Test01.pcap​"​ # PowerShell cd 'C:\Program Files\Wireshark' ./tshark.exe -i 9 -b duration:3600 -b files:72 -w 'C:\Users\Username\Desktop\Desktop\Test01.pcap​' Note: Change  -i 9  to the number of the interface on the capturing machine. Change  -b duration  to time in seconds (3600 is one hour). Change  -b files  to the number of files to cycle through (72 is 3 days of 1-hour captures, 3x24). Change  -w  to write to the location and filename you choose. Change  \Username\  to your Windows User, if you want to save to that user's Desktop Reference: tshark(1) Manual Page (wireshark.org)