Building Automation Knowledge Base

Issue What does default.db contain? Which objects does config.db contain? Do i need to upload both files to the MPM? Product Line EcoStruxure Building Expert Environment SmartStruxure Lite Multi-Purpose Manager Cause Unable to download config.db from Building Expert; There are two files for the database Resolution When the database is saved using the "save database to flash" button, the MPM saves its data into two files; config.db and default.db 1 - Configuration Objects (config.db): The config.db file includes "system configuration objects" which show up in Building Expert when logging into a brand-new MPM. BAC1,C2G1, CFG1, EOC1, ETH1, MOD1, SNTP1 and ZBC1 Note: Depending on the model of the MPM, some objects in the above list may not be there. Note: CBC1 is part of default.db   2 - Control Objects (deafult.db): Objects that are manually added in Building Expert are part of the default.db database. Some examples are - Analog Values (AVs) - Binary Values (BVs) - Lua Programs (PGs) - etc...   The following items are also part of default.db: - Devices (ZigBee, EnOcean, Modbus etc...) - Dashboards - Permissions - Login Credentials (Username and password)   Backing up the database: The files can be downloaded by entering the following in the address bar of the browser: (assuming the IP address of the MPM is set to the default IP 10.50.80.3) 10.50.80.3/root/default.db 10.50.80.3/root/config.db   To upload the database to an MPM refer to Uploading Database files to an MPM (Cloning).

Issue Upgrading SQL Express to a paid Edition of SQL for EcoStruxure Reports Server Product Line EcoStruxure Building Operation Environment WebReports Reports Server SQL Express Cause SQL Express 2008 R2 (for example) is limited to 10 Gb of Storage and 1 Gb of Ram usage. Many sites need a larger, more robust database than this allows. Resolution NOTICE: Before beginning, it is important to understand the difference between the Instance name and the version of SQL running.  The default instance name used in the the SQL Express version of SQL is SQLEXPRESS. This can be changed to anything during installation, but cannot be changed later.  This means that when upgrading to SQL Enterprise edition, the SQL instance name will still need to be SQLEXPRESS. The instruction below assumes the instance name is SQLEXPRESS and will be typed in that manner.   Perform a full backup of the Enterprise Server and Reports Server before beginning any upgrade process. Save these files to an external drive. Purchase a supported edition of SQL for the revision of EcoStruxure Building Operation WebReports being used. Please check the data sheet for the release to obtain this information. Open the Command Prompt and Browse to the location of the installation files for SQL. This should be the folder containing the setup.exe file for the new version of SQL Enter the Command "setup /ACTION=editionupgrade /INSTANCENAME=SQLEXPRESS /PID=XXXXX-XXXXX-XXXXX-XXXXX" NOTE:If  not using the default instance name, enter the correct instance name in place of SQLEXPRESS. PID is the product ID that came with the installation media. In some cases, this will be left out of the command string and entered later. (setup /ACTION=editionupgrade /INSTANCENAME=SQLEXPRESS) The SQL Installer will open. After the Setup Support Rules operation runs, click OK Click Next Verify the Product Key and click Next. Accept the License Agreement and click Next Ensure that the correct instance of SQL is selected and click Next. After the Edition Upgrade Rules runs, click Next Review the Upgrade Summary and click Upgrade When Complete click Close Open the SQL Server Configuration Manager using the start menu and verify that the SQL Server (SQLEXPRESS) service is running and that the SQL Server Reporting Services service is running. If either are stopped, right click and select the start option. Verify the upgrade is successful by opening a Web Browser and entering the URL "http://localhost/Reports_SQLEXPRESS" It should now be possible to see the option to directly edit reports in Report Builder. Log into the WebReports Interface. Notice that the initial report showing Database usage no longer runs.

Issue Continuum running under MS Windows 7, Vista or MS Windows Server 2008 (including R2) Access event viewers at workstations other than the primary access server do not show events. Alarms acknowledged at one CyberStation would remain unacknowledged in the other CyberStations.  Product Line Andover Continuum Environment CyberStation Microsoft Windows 7 Microsoft Windows Server 2008 Microsoft Windows Server 2008 R2 Cause Problem in Microsoft MSMQ component. MSMQ service might not send or receive messages after you restart a computer that is running Windows 7, Windows Server 2008 R2, Windows Vista or Windows Server 2008. This will cause any Continuum component that uses MSMQ (such as Alarms and Access Events) to fail. Microsoft has issued a hot fix for this MSMQ problem. Resolution Use the following command prompt test to verify the problem netstat -ano | findstr 1801 The command tests whether MSMQ is listening for messages. For example, Continuum WS 'A' is the primary access server (PAS) with an Event Viewer 'EV' up,  a second Continuum WS 'B'  is also displaying the same EV. If MSMQ is functioning normally you should see the following. 1. is the IP address of WS 'B' that has established a link to WS 'A'  2. is the IP address of WS 'A', the PAS in this case. 2560 is the listening MSMQ process PID  You can clearly see that there is a MSMQ process (2560) in WS 'B' LISTENING on port 1801 If there is no MSMQ process listening the output of the command will show the loopback or localhost IP address 127.0.0.1 and you have to install the following Microsoft hotfix: Package: ----------------------------------------------------------- ----------------------------------------------------------- See Microsoft KB Article Number: 2554746   ** In very rare occasions, removing MSMQ and adding MSMQ again to the PC is required. ** Once it is re-installed, please refer to Access event viewers running in a workstation other than the Primary Access Server stop displaying events to set the MSMQ CleanupInterval setting to one hour in the primary access server.

Issue Does Modbus TCP/IP xDriver opens socket connection per each device or the gateway of the devices? Environment NetController - CX9900, CX9940, CX9680, bCX9640. BACnet Controller - bCX4040. Cause As some Modbus TCP/IP gateways have the limitation of maximum TCP/IP connections, if Modbus TCP/IP xDriver opens a socket per modbus device and keeps it open, the gateway might run into a problem due to the limited number of socket connections. Resolution The Modbus TCP/IP xDriver opens one(1) socket connection per server not device. So for a gateway that has a number of devices, the Modbus TCP/IP xDriver only uses one(1) socket connection.

Issue Test and air balance procedure for balancing airflow Product Line TAC Vista, EcoStruxure Building Operation Environment Building Operation Automation Server Premium  TAC Xenta 102-AX  TAC Xenta 102-AX Plug-in Cause Each 102-AX controller must be calibrated on-site to report accurate airflow readings.  The LNS Plug-in provides this functionality, but it may not be immediately clear what the correct procedure is to perform a valid calibration. Resolution Check the firmware version of your 102-AX controllers in the plug-in, Node Configuration tab. It will be shown under Program Revision. If it's anything earlier than 2.1.6 then the calibration won't work properly. The airflow setpoint changes but the damper does not modulate to maintain setpoint in the calibration mode. Your options in that situation are to manually manipulate the damper to maintain airflow setpoint in order to facilitate calibration or upgrade the controllers firmware. Also verify that the box is set to "Pressure Independent" mode on the Unit Parameters tab.  Pressure dependent boxes do not use airflow sensors, and therefore cannot be calibrated. To balance the 102-AX in Building Operation version 1.4 or higher where the LNS plug-in is no longer provided, review the article TAC Xenta 102-AX TGML plug-in for Building Operation To calibrate airflow using the 102-AX LNS plug-in:  Go to the Node Configuration Tab. Select "Set Default m & b." This is a good idea before each calibration attempt since incorrect calibration values can make it more difficult to perform a valid calibration. (NOTE: The m & b values can be viewed under the Airflow Parameters Tab of the 102AX LNS plug-in...m = Velocity Pressure Gain & b = Velocity Pressure Offset) Select "Start Calibration." At this point the airflow setpoint should go to the minimum. You can check the Cooling Minimum airflow setpoint on the Airflow Parameters tab. The damper now modulates to maintain the minimum cooling flow setpoint. Watch the VAV Reading (Low) and wait for it to hit the minimum flow setpoint and level out. If the airflow is fluctuating a lot, it could be that the low setpoint is below the threshold the box can confidently supply. Or it could be bad placement of the flow sensor in a turbulent area of the duct. It can affect your calibration greatly if the value is fluctuating too much. A relatively level reading will provide a good calibration. When it levels out, measure the actual airflow with a highly accurate magnehelic hood. Enter the actual value into Reference (Low) and select "Continue." The damper now modulates to maintain the maximum cooling flow setpoint. Watch the VAV Reading (High) and wait for it to hit the maximum flow setpoint and level out. When it levels out, measure the actual airflow with a highly accurate magnehelic hood. Enter the actual value into Reference (High) and select "Finish." The new calibrated m & b values are shown. The gain (m) is shown in the format of multiplier/divisor. Divide the values to get a decimal format of the gain. The closer to 1 this value is, the less calibration was required. actually gains of 2 or more indicate probable airflow reading problems. It may be advisable to reset factory calibration values and try the calibration again. The box should now be displaying values very close to actual measured readings. Test the low and high flow during normal operation using the Status Tab, Right click on the Space Temp and override the space temperature to a value equal to or greater than the Occupied Cooling Setpoint plus half the Cooling Band to drive the airflow setpoint to the cooling maximum airflow setpoint (you can find the Occupied Cooling Setpoint and Cooling Band on the Operating Tab).  With the space temperature already in override, left click the Space Temp to change the space temperature without taking it out of override, and set the space temperature to the Occupied Cooling Setpoint minus half the Cooling Band to drive the airflow setpoint to the cooling minimum airflow setpoint.  With the space temperature in override, right clicking it will take it out of override.

Issue Embedded WebStation client licenses were needed when logging directly into a SmartX server as of 3.0.1 but are no longer needed Product Line EcoStruxure Building Operation Environment Building Operation Webstation Building Operation SmartX Server Cause The license requirement is being removed due to market feedback. The quantity of direct web connections to the SmartX server is restricted by the Architectural Guidelines only. Resolution Important for version 4.0 (EBO 2022) and above:  Note that in Building Operation 2022 (v4.0.x) and above, WebStation licenses have now been enforced at the server level and are required.   If there is no embedded server license for example "XWSWXBU0000SD ASP Bundle - Standard" in the SpaceLogic server it will not be possible to login to the server using Webstation. The Webstation license is included in the embedded server license.   For version 3.0.x The change is available via a HotFix to version v3.0.3 and will be incorporated into Maintenance Release v3.0.4. In both the HotFix and the Maintenance Release, license status presentations in the Device Administrator and Control Panel will indicate the availability of 99 client licenses. However, the supported quantity of direct web connections to a single SmartX server is established by the Architectural Guidelines; currently, the maximum is five concurrent connections. In v3.1, the Device Administrator and Control Panel will not list client license availability at the SmartX server level since it is not constrained by licenses.  

Issue When attempting to log on to an Automation Server with Workstation receive error: Can not continue because server is offline or temporarily unavailable. Product Line EcoStruxure Building Operation Environment Automation Server  StruxureWare Building Operation Workstation Cause This error message indicates that the Automation Server can not communicate with the Enterprise Server that it was associated too.  The Automation Server has been associated to an Enterprise Server where a new default (StruxureWare) domain has been added / created. The image below shows a second domain that has been created and been set as the default, this can be seen by the tick box on the second domain entry. When attempting to use the default admin account (by leaving the Domain blank) the Automation Server attempts to contact the Enterprise Server to authenticate the user.  If the Enterprise Server is offline or you are working with a database away from the Enterprise Server then you will receive this message. Resolution Two possible resolutions exist for this: Re-establish the communication for the Automation Server with the Enterprise Server to allow authentication for the user attempting to log in to be verified. Log on with a known "Local" domain or admin account.    Note: The domain name is case sensitive, even the Local domain. Make sure to type the name of the domain with appropriate capitalization. In this example, when trying to login to the Local domain, typing "local" fails to login, where typing "Local" logs into the AS correctly.

Issue When performing Continuum Database Initialization from a CyberStation workstation, the workstation cannot connect to the SQL Server with the following error message: "Microsoft SQL Server Login Connection failed or server not available or access denied" Product Line Andover Continuum Environment LAN workstations Single User workstations Cause Possible Invalid Server Name is being used in Continuum Database Initialization:   For Continuum LAN systems, the Server Name attribute of Continuum Continuum Database Initialization includes invalid characters.  For Continuum Single User systems, the Server Name attribute of Continuum Continuum Database Initialization does not include the \SQLExpress attribute after the Computer name.  Resolution For Continuum LAN systems, type the correct computer name of the SQL Server in the Server Name attribute field of Continuum Database Initialization screen such as "MyDBServer". Check that the required strong password is being used, such as "ABCabc123" For Continuum Single User systems, add the qualifier "\SQLExpress" at the end of the computer name in the Server Name attribute field of Continuum Database Initialization screen such as "MySUServer\SQLExpress" . Restart the SQL Server  Service and/or SQL Agent Service Check that the Windows Firewall on the Windows Server PC is turned off. Check Connection with sa Admin account on MS Management Studio and via ODBC.

Issue Is the new PSI / XPSI rev 4.1 compatible with Windows XP and Vista? Environment PSI / XPSI rev 4.1 Windows XP and Vista Cause Install PSI / XPSI rev 4.1 in a Windows XP or Vista Operating System (OS) Resolution The new PSI / XPSI rev 4.1 is compatible with Windows XP and Vista. Download PSI rev 4.1 from The Exchange. The zip file includes an installer and a READ.ME file that includes Release Notes and Installation Instructions. Note that the Patton Electronics RS-232 / RS-485 converter that has been widely used with the earlier versions of PSI (3.13) will not work with the new PSI / XPSI rev 4.1.  The B&B Electronics model USOPTL4 USB converter has been successfully tested with PSI / XPSI rev 4.1. Other recommended converters are listed in the Release Notes.

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 What is the best way to upgrade Continuum Single User system from 1.5x to 1.9x? Product Line Andover Continuum Environment Continuum 1.5x, 1.5, V1.5 Continuum 1.6x, 1.6, V1.6 Continuum 1.9x, 1.9, V1.9 SQL Server Cause Continuum Upgrade from older versions of Continuum. Resolution First upgrade to 1.74, then upgrade from 1.74 to 1.9x.    PART I - Preparation: Acquire all software necessary to bring the workstations into compliance with 1.9x platform requirements. For each Cyberstation machine, make a record of the following Workstation name Folder name Device Node ID Network ID. From https://ecobuilding.schneider-electric.com Download Cyberstation 1.74 Download Cyberstation 1.9x Download Microsoft SQL Server Management Studio Express Run Continuum Analyzer and resolve any issues.  An upgrade should not be done until the analyzer test report is clean. IMPORTANT - Make a backup of the Continuum database just prior to upgrading. PART II - Upgrade Workstation 1 (Database server PC) Uninstall 1.5x or 1.6x Shut down the Cyberstation applications on all workstations. Power down the workstations that are not running SQL and leave off until Part III Backup the contents of C:\Program Files\Continuum\UserProfile by copying contents to a flash drive or another folder. Backup the contents of the graphics file directory to a flash drive or another folder. Delete C:\Program Files\Continuum Uninstall SQL from Workstation 1 (DB server) Install 1.74 Install Continuum 1.74  (SQL 2000 SP4 will be installed automatically as part of the install) Run Database Initialization Create new database Initialize workstation using information from Part I. Launch Continuum to test that Cyberstation startup normally. Shut down Continuum Run Microsoft SQL Server Management Studio Express Navigate to ContinuumDB and Right Click Restore database backup from PART I Run Database Initialization. Update Continuum DB Update Workstation using information form Part I Launch continuum and verify that everything looks normal. Verify the integrity of the database by running Continuum Analyzer and correct any database issues before proceeding.. Run Microsoft SQL Server Management Studio Express Navigate to ContinuumDB and Right Click Backup Database – name file so that it is clearly 1.74 Uninstall 1.74 Uninstall Continuum Delete C:\Program Files\Continuum Uninstall SQL from Workstation 1 Install 1.9x Install all platform software necessary to bring the workstation into compliance with Continuum 1.9x requirements. Install Continuum 1.9x - (SQL Express will be installed automatically as part of the install) Run Continuum Database Initialization Create new database Update workstation with information from Part I. Launch Continuum to test that Cyberstation startup normally Shut down Continuum Run Microsoft SQL Server Management Studio Express Navigate to ContinuumDB and Right Click Restore 1.74 database backup. Run Continuum Database Initialization Update database Update workstation with information from Part I. Launch Continuum and verify that everything looks good. Run Continuum Analyzer and verify the integrity of the database. Backup Database PART III - Upgrade Workstation 2 and 3 Install all platform software necessary to bring the workstation into compliance with Continuum 1.9x requirements. Backup the contents of C:\Program Files\Continuum\UserProfile by copying contents to a flash drive or another folder. Uninstall Continuum from Workstation  Delete C:\Program Files\Continuum Install Continuum 1.9x Run DB Initialization and update database and workstation. Launch Continuum and verify that all looks well. Backup Database

Issue Verifying the Com Port on a PC is working properly by using "Loopback" test in Terminal Emulator. Product Line Andover Continuum, Field Devices, Other, Satchwell MicroNet, Satchwell Sigma, TAC IA Series, TAC INET, TAC Vista Environment Hyperterminal RS-232 serial port Cause The following test writes to the serial port and reads from the same port. This will verify the Full duplex operation of the RS-232 communication. Resolution Short the TX and RX pins of the cable (pins 2 and 3) following the pinouts below. Gender is determined by pin type.                Male DB9 (Left) and Female DB9 (right)   Launch Hyperterminal by selecting Start>>Programs>>Accessories>>Hyperterminal. If you do not have Hyperterminal, please read Hyperterminal on Microsoft Windows Operating Systems. If you are asked if you would like to install a modem, select No. Choose any icon and name the session, select "OK". In the next Pop-Up menu, choose direct to COMx (where x is the number of the COM Port you are testing.) Set the flow control setting to None. Leave the other settings to default settings, select "OK" Select File » Properties from the menu bar, select the Settings tab, and then push the ASCII Setup button. Check the option for Echo typed characters locally. Type something. If you see double characters the serial port is setup correctly and is functional. The display is showing characters that are sent out and what is read in. The Emulator will send and display the TX and immediately read and display  RX. If you see exactly what you are typing, you have a communication issue. which could be: Bad Com Port Bad cables Pins not shorted correctly If you are out of physical ports to try, use a USB Serial Port converter. If you are using a USB, use Reassigning a USB Serial Adaptor to a desired COM port for instructions of assigning Com to another port.

Issue The PID controller object provided as part of the MPM software does not allow for any means of programmatic override i.e. forcing the loop output to 0%, 100% or other user defined position.  If you force the referenced Manipulated Variable (output) to a particular position by programmatically disconnecting it from the PID object, there can be a large overshoot when the PID output is reconnected.   Product Line EcoStruxure Building Expert Environment SmartStruxure Lite Multi-Purpose Manager (MPM) Cause If you force the referenced Manipulated Variable (output) to a particular position by programmatically disconnecting it from the PID object,  the PID controller will be 'open loop' and any integral parameter will wind up the output to its max or min position.  This can cause a large overshoot when the PID output is reconnected.   Resolution One option is to write a Lua script that forces the Controlled Variable and the Setpoint Reference to receive the same value when you override the loop output. This would freeze the output of the PID controller and prevent any integral wind up. There would still be a 'bump' when you remove the override, but it should be reduced.   Another option is to replace the PID controller object with a Lua script that provides the same the same functionality but with the addition of an override mode. You can find a sample Lua script here

Issue What is the recommended process for Database and Workstation Initialization Product Line Andover Continuum Environment Database Initialization Workstation Initialization Cause Sometimes it is necessary to do Workstation and/or Database Initialization eg. following a Continuum service pack install Resolution Database initialization LAN systems (SQL is on a separate SQL server PC) Close all connections to the database (all cyberstations, webclient servers etc.) Open "Database Initialization" from Start/All Programs/Continuum Select "Server" Select "Update Existing Database", ensure Database Information is correct, fill in User Login Password Usually Enhanced Alarm Logging and Enhanced Alarm Delivery are ticked. Then select Continue Database initialization Stand Alone (Single User) systems (SQL is on a CyberStation PC) Close all connections to the database (all cyberstations, webclient servers etc.) Open "Database Initialization" from Start/All Programs/Continuum Select "Stand Alone" Select "Update Existing Database", ensure Database Information is correct, fill in User Login Password Usually Enhanced Alarm Logging and Enhanced Alarm Delivery are ticked. Then select Continue WorkStation Initialization Close the CyberStation on the PC being initialized (other CyberStation can be running) Open "Database Initialization" from Start/All Programs/Continuum Select "Workstation" Check both tabs and fill in the User Password Then select Continue See the Continuum Installation manual for further information   NOTE 1 With the some domains the following has been found - XP - "Right click" on the "Database Initialization shortcut" and “Run As” use local admin - Windows 7 - "Shift" & "Right click" on the "Database Initialization shortcut" and “Run as a different user”, use local admin To log on use the workstation name followed by user eg. WSUK1AB123ABC\dave   NOTE 2 Long CyberStation names can result in the error "Workstation name with invalid characters. Please enter it again" In this case use a shorter name, below 16 characters is best. This can occur even with an existing longer CyberStation name.

Issue Xenta Controllers can report "offline" status if they encounter bandwidth limitations Completion Event Failure warnings CRC Errors showing in controller properties Loytec Multi-port router/switch channel LED blinking fast red (traffic overload) Product Line TAC Vista Environment Lon Networks Vista Xenta LPA Loytec Protocol Analyzer Cause HMI Vista on-line/off-line presentation is based upon receipt of the heartbeat messages. Every TAC Xenta 280/300/401 controller is periodically sending a message to the other members of its TAC Xenta reporting (including the group master) that it is on-line. Proprietary "LACNet-IAm" and "LACNet-GroupIs" are sent every 15 seconds to HMI Vista. Without the HMI receiving these heartbeats, Vista will display the controller or group in an offline state. The TAC Xenta group is specified by the tag_0 and the TAC Group is specified by tag_1 bindings in LonMaker or NL220. Resolution Actions for reducing Bandwidth: TAC Xenta 100s Slow down the SendHeartBeat Check sensors etc that are affecting all bound nvo's Decrease traffic of SNVT group bindings. For large groups of bound controllers, use UNACKD/RPT instead of ACK service type. 3rd Party LonWorks devices Change update rates for nvo's. If possible, the product manual should show how. Decrease traffic of SNVT group bindings. For large groups of bound controllers, use UNACKD/RPT instead of ACK service type. TAC Xenta 280/300/401 TACNV and SNVTs Verify delta and period values make sense for the particular signal and application. Decrease traffic of SNVT group bindings. For large groups of bound controllers, use UNACKD/RPT instead of ACK service type. Increase the trend log time span (the total log time) if possible. Of course, this will increase the memory usage in the Xenta, but this will make TAC Vista to do the fetch more seldom and result in reduced traffic. TAC Xenta 280/300/401 + TAC Xenta I/O Modules If sensitive sensors (i.e. pressure sensors) are connected to I/O Modules, a high load of communication will be generated. Bandwidth issues may arise when 401s with many I/O Modules are each reading multiple sensitive sensors. Increase the Min Send Time for every I/O Module. Min Send Time is how often the I/O module is allowed to communicate with the TAC Xenta. This setting is located in Device Specification in Menta. Reduce Trend Log definitions in the controllers. If possible, try to have all your "high speed sensors" connected to one, or a few I/O modules, so it's only a few I/O modules sending a lot to the Xenta. LonWorks routers Implement L-Switch routers to reduce traffic on high bandwidth segments. Set router to Configured Mode, not Repeater Mode. Vista Server Trend Log Stagger Vista server Trend Log start times so that they do not all attempt to get fetched at once. See also Troubleshooting LON Network Communication More information can be found in Tool for LON / LPA Capture Traffic Analysis (login required) which discusses the LPA Analyzer Tool. This may be useful for interpreting the LP file data.

Issue BACnet/IP port supported with EcoStruxure Building Operation Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Automation Server Building Operation Automation Server Premium Building Operation Automation Server Bundled Building Operation Edge Server - Standard Cause Which BACnet/IP ports are supported with EcoStruxure Building Operation, and can there be more than one port? Resolution By default, the BACnet/IP network uses UDP port 47808 (0xBAC0), this is adjustable higher or lower. The BACnet/IP network supports a single BACnet UDP port, Additional IP networks can be created in the BACnet system as long as each network has a unique identifier (network Id and name) and UDP/IP port number. Refer to: Creating an Additional BACnet IP Network (se.com) and Best Practices When Configuring BACnet IP Networks and BBMDs for EcoStruxure BMS Servers Please note that BACnet/IP uses UDP as its transmission protocol. For more information read the BACnet/IP basic design criteria.

Issue License requirements for standalone Automation Server at a site Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Building Operation Automation Server Premium Building Operation Automation Server Bundled Building Operation Edge Server - Standard Cause Question on License requirements for standalone Automation Server at a site Resolution EBO 2022 or higher: Standalone Automation Server need software bundle license in addition to add-on option license if required, check Part Number Summary and Hardware Software Matrix. Webstation license is included in the embedded server license. EBO 3.2 or lower: A standalone Automation Server where no web services, Technician Tool (discontinued), SNMP, MQTT, Personal Dashboards and TimeScale DB  are used does not require a license. Use of one of these features requires license which means the use of a single Automation Server or multiple Automation Servers without license is a legal breach.

Issue Ports are required to be open for I/NET to communicate Need to know the UDP TCP/IP port settings for I/NET. File Equalization failure or NPR devices not coming online Some links (NPRs) are showing offline and can not be connected too, while others work fine. Product Line TAC INET Environment I/NET NPR NPR-527 Cause A Firewall may be blocking ports required for File Equalization and I/NET communication to occur. Resolution You will need to work with the IT department to verify these settings. I/NET communications occurs through port 50069. When using File Equalization you will also need to ensure that ports 1433 and 1434 are open as these are used by SQL. Integral DVR communicates to I/NET on port 18772 For systems with 527 devices or other Xenta servers, please review Ports used by TAC Vista System.

Issue What is the data format for the OPC and ModBUS options in the ModBMS software? Product Line Satchwell Sigma Environment ModBUS Slave OPC Server ModBMS OPC DA AE OPC XML Cause Supported Data formats Resolution The supported data formats are listed in the configuration and release note for the ModBMS software. See ModBMS Release Note 3.2.pdf. OPC XML is not supported by ModBMS (see IC GEN OPC and XML-DA data type)

Issue Continuum crashes with RPC error "The RPC server is unavailable" shortly after launching. RPC Server Error Product Line Andover Continuum Environment Cyberstation Cause Possible causes: Virtual memory, make sure virtual memory is set to recommended value. (see virtual memory requirement in Cyberstation installation document) Remote Procedure Call (RPC) locator service not started (Should be configured for automatic start) A resource needed by Continuum is not available. For example if an EventNotification is configured to page on alarm and there is no modem installed in the workstation then if an alarm is active on start up Continuum will encounter RPC error. Resolution Set workstation virtual memory to recommended value. Configure Remote Procedure Call (RPC) for automatic start. Make sure resource needed is available or reconfigure as needed.

Issue Basic test of communication port on the Carrier DataLink, as accessed by the Network 8000 SIM-CCN. Environment Carrier DataLink communication gateway to a bus with CCN controllers Network 8000 SIM-CCN (Systems Integration Module for Carrier Comfort Network) Terminal emulator, such as HyperTerminal Click here for the SIM-CCN Installation Instructions, F-26167-2. See Figure 6 for detail of the serial cable required. Cause In some cases it is necessary to verify that third-party equipment is functional, independent of the SIM-CCN. Resolution Unplug the serial cable from the SIM, leave the other end connected to the Carrier  DataLink. Set up HyperTerminal: 8 data bits, no parity, 1 stop bit, 9600 baud, no flow control. Type " RT 1 DPTCONFG",  expect a "?" prompt.  If a prompt is returned, the port on the DataLink is functional; if no prompt is returned, the port may not be functional. If necessary, change the baud rate used by the terminal emulator to 300, 1200, 2400, or 4800 bits per second and repeat the test step 3. If the test fails at all of the possible baud rates supported by the DataLink, the port may not be functional.