Issue DBCreate database restore fails with error message: "The backed-up database has on-disk structure version 611. The server supports version 539 and cannot restore or upgrade this database. [Microsoft][ODBC SQL Server Driver][SQL Server]RESTORE DATABASE is terminating abnormally." Product Line TAC INET Environment I/NET Seven SQL Server 2000 all editions and SQL 2005 all editions Cause It is not possible to restore a SQL Database which was backed up using SQL 2005 back into a SQL 2000 database. Resolution The simplest method to rectify this problem would be to uninstall I/NET and SQL (Refer to Procedure for uninstalling I/NET Seven on a stand-alone host on how to do this) and then re-install I/NET using SQL 2005. The second method would be to upgrade the installed MSDE Default instance to SQL 2005 Express. There is a published white paper from Microsoft on this and is attached here: MSDEtoSQLExpress.doc.  Refer to the steps on page 11 to 14. The SQLExpress installation file is available on the I/NET CD under the folder SQLExpress\.SQLEXPR32.EXE. After performing these steps its advisable to run up DBCreate and upgrade the SQL database.

Issue There is a need to know if Continuum and/or EcoStruxure BACnet support NAT. Product Line Andover Continuum, EcoStruxure Building Operation Environment Continuum EcoStruxure BACnet BBMD NAT Cause Many sites use NAT for security purposes.  Resolution NAT traversal is not supported in BBMD implementations (Continuum or EcoStruxure). It is an optional feature that has not been implemented. Requests to add this feature should be directed to Product Marketing to include on the backlog for prioritization. Related Continuum article: Can Continuum operate over a NAT Ethernet connection? Ashrae information: here

Issue What are the typical steps to install and configure Vista OPC Server? Product Line TAC Vista Environment Vista 5.1.x Vista OPC Server 1.6.1 Cause OPC Server can be used in many integration situations to provide data to other parties or bring third party data into the Vista front end. Resolution  Install TAC Vista OPC Server 1.6.1 installation package Add a Windows Account for Vista OPC Server Start Computer Management In System Tools\Local Users and Groups\Users click New User Name the user OPC_Communication Provide a password Uncheck the User must change password at next logon checkbox Check User cannot change password checkbox Check Password never expires checkbox Click Create and Close. Add user to the Administrators group Configure Service In Services right click on TAC Vista OPC Server and click properties Ensure Startup type is Manual On Log On tab select This Account Browse to the local account OPC_Communication Provide the password in the Password and Confirm password fields Click OK Configuring DCOM Start Component Services Double click Component Services\Computers\My Computer\DCOM Config Locate the COM Server TAC Object Server OPC DA Services and select properties Click the Identity tab Select This User Select the local account OPC_Communication Provide the password in the Password and Confirm password fields Click OK Locate the COM Server TAC Object Server OPC AE Services and select properties Click the Identity tab Select This User Select the local account OPC_Communication Provide the password in the Password and Confirm password fields. Click OK Create a Vista User Account Start Vista Server Start Vista Workstation and Log In In the root TAC Vista folder create a new account (User - Vista or User - Windows Domain Group) Name the user TACOPC Modify the properties of the account Set the password Set an authority level that OPC Clients should use when accessing the OPC Server Set the Logout time to zero(0) Configure the Vista OPC Server Login Open TAC Vista OPC Server Setup (Program Files\Schneider Electric\TAC Vista OPC Server\Vista OPC Server Setup) Ensure the Retry connect period is 360 seconds. In the logon to TAC Vista Server click Login using the following Vista Account In the Username type TACOPC Type the password Click OK Confirm the change took place, if it is not refer to OPC server for TAC Vista will not keep the login settings in the TAC Vista OPC Server setup. Configuring Windows Firewall If Vista Server and OPC Server are on the same computer then no firewall exceptions are required. Consult the OPC Server manual (Chapter 4) for the firewall exceptions if using a separated OPC Server and Vista Server setup. Configuring OPC Client DCOM Settings If the OPC Client is on another computer then create a user account to match the one used by Vista OPC Server. Start Computer Management In System Tools\Local Users and Groups\Users click New User Name the user OPC_Communication Provide a password Uncheck the User must change password at next logon checkbox Check User cannot change password checkbox Check Password never expires checkbox Check Create and Close Configure Access Permissions Start Component Services on the Vista OPC Server computer under Administrative Tools In the Tree Structure right click on Component Services\Computers\My Computer and click properties Click the COM Security tab In Access Permissions click Edit Limits Click Add Select the local account OPC_Communication (EXAMPLE: W7USCNU1342VXXX\OPC_Communication) In the allow column select Local Access and Remote Access Click OK In Access Permissions click Edit Default Click Add Select the local account OPC_Communication In the allow column select Local Access and Remote Access Click OK In Launch and Activation Permissions click Edit Limits Click Add Select the local account OPC_Communication In the allow column select Local Launch, Remote Launch, Local Activation, and Remote Activation Click OK In Launch and Activation Permissions click Edit Default Click Add Select the local account OPC_Communication In the allow column select Local Launch, Remote Launch, Local Activation, and Remote Activation Click OK Configure Local Security Policy Select the Local Policies\Security Options\Network Access: Sharing and security model for local accounts policy Set the policy to Classic - local user authenticate as themselves Click OK Repeat these steps for the OPC Client computer Configuring OPCEnum Start Component Services on the Vista OPC Server computer In the tree structure Component Services\Computers\My Computer\DCOM Config right click on OPCEnum and click properties On the general tab change Authentication Level to Default Ensure Run Application on this computer is checked on location tab Click the Identity tab Select This User Browse to the local account OPC_Communication Provide the password in the Password and Confirm password field Click OK Repeat these steps on the OPC Client computer Start the TAC Vista OPC Server In Services right click on TAC Vista OPC Server and click start For more OPC Server issues please see Vista OPC Server Installation and Known Issues. A good overview of  OPC integration and the necessary COM and DCOM settings is located here.

Issue bCX9640, CX9680, ACX5720 and ACX5740 do not have ACCRestartMode system variable. Product Line Andover Continuum Environment CyberStation bCX9640 CX9680 ACX5720 ACX5740 Cause The restart mode of the second generation Infinity CX controllers (9640, 9680, 5720/40) is not user selectable. Resolution The second generation Infinity CX controllers (9640, 9680, 5720/40) have a fixed startup sequence as follows: Warm to Cool to Cold, meaning the controller will ALWAYS first attempt to WARM start, if warm start is not possible the controller will attempt a COOL start, if cool start if not possible the controller will attempt a COLD start. Warm start: Controller is re-starting with its RAM memory intact because the controller has remained powered or the memory has been kept by the battery. In this case all the configuration data (points, programs) and run time data (logs, points current values) is restored. Cool start: Controller is re-starting with its RAM memory erased or is unable to restore data from RAM for whatever reason. In this case the configuration data only (points, programs) is restored provided it has been previously backed up to flash memory. NOTE: Personnel objects are NOT kept in flash, upon cool start the controller will automatically request a personnel distribution from its access server CyberStation. Cold start: Controller unable to warm start or cool start, all configuration and runtime data will be lost. It must be reloaded from CyberStation.

Issue All inputs on an i2920 controller read 999.9 volts even when all input connections are removed. The controller error log shows error number 0x00002809. Product Line Andover Continuum Environment i2920 Cause The 0x00002809 error is logged by the Analog to Digital conversion process when the V Zero is greater than the V Reference.  This would indicate a controller calibration failure or a controller hardware failure. Resolution The controller should be returned for repair.

Issue Automation Server -Trend does not record at time interval when it is stopped and restarted by AS power cycle or reboot. Trend log cycle is thrown off when the trend is stopped and started again due to an AS power cycle or reboot. For example, an Interval Trend Log set up to log ever 15 minutes with an activation time right on the hour (1:00, 1:15, 1:30 etc.) that lost power for a while would start logging as soon as the power was restored (this might be 2:07, 2:22, 2:37 etc. for example). UPDATE: This issue has been corrected in SBO version 1.5, any SBO version 1.5 or grater will synchronize the interval log to the clock. Product Line EcoStruxure Building Operation Environment Automation Server Struxureware Workstation Cause This is how Interval Trends behave. For interval trending based on the time a different approach must be taken. UPDATE: This issue has been corrected in SBO version 1.5, any SBO version 1.5 or grater will synchronize the interval log to the clock. Resolution Rather than using Interval Trend Logs use Variable Triggered Trend Logs and trigger them using the following method: Create a new binary value and a new function block program. The value will serve to trigger the Variable Triggered Trend Logs. The program will set the trigger variable based on a certain time interval (for example on the hour, 15 minutes, 30 minutes and 45 minutes). Edit the program and configure it as seen in the image below. This include an integer input, an expression that will evaluate the minutes attribute of the AS and a binary output. You can also download an export of the program and value here. Bind the input of the program to the minutes attribute of the Automation Server and the output to the trigger value that you created. Note that you should also bind the Task to Task 1 (100 ms) for best performance. Create your Variable Triggered Trend Logs on the points that you want to trend. Do this by right-clicking the point to trend and selecting New > Trend and then in the dialog select Variable Triggered Trend Log. Click Next and then set the Trigger Variable to the value that you created. Make sure Trigger when is set to Change to true. Note that this example will create a log at 0, 15, 30 and 45 minutes past the hour. You can modify the program to trigger only every hour, every half hour or however you want.

Issue Is it possible to override interlocked doors with a user card? Product Line EcoStruxure Security Expert Environment Security Expert Door interlocking Cause Require an option to allow specific users to access through locked down interlocked doors. The "User has Super Rights" option in the User record seems to provide this since it notes that one of the permissions this option provides is to "Unlock doors that have been locked down". user has super rights Resolution Unfortunately the User has Super Rights option does not work in this scenario. The option was never designed to work with interlocked doors.  To request for this feature to be implemented, a new feature request can be made with your local solution category management team.

Issue Replacement for defective controller is unable to be brought online in Security Expert. The online status is offline and last download shows as failed. controller status A review of the event server diagnostic window shows it is full of "Unencrypted event packet received" messages. event server diagnostics window Product Line EcoStruxure Security Expert Environment Security Expert Client Security Expert controller (SP-C, SP-AC1, SP-ACX) Cause The previous failed controller had been setup for encrypted communications with the Security Expert server. Since the newly installed replacement controller did not have the encryption keys to be able to decode the packets from the server it was not able to be brought online. Resolution On the controllers Configuration tab press the Disable controller encryption, then Yes to confirm. Wait for communications to be established with the controller, review the controller health status and update any modules that require it. To re-initialize encrypted communications with the controller press the Initialize controller encryption button to establish a new encryption key with the new controller. controller encryption buttons

Issue When upgrading Building Operation do new licenses need to be purchased? Product Line EcoStruxure Building Operation Environment Building Operation (All Versions) Cause Is there a requirement to upgrade (purchase new) licenses when performing software upgrades to Building Operation to make use of the new features available. Resolution Building Operation software version numbering consists of 3 fields the first of these denotes the major release version. For example: 1.9.4 - Release 1 2.0.1 - Release 2 3.0.1 - Release 3 3.2.4 - Release 3 4.0.4 - Release 4 (EBO 2022) 5.0.3 - Release 5 (EBO 2023) 6.0.2 - Release 6 (EBO 2024) An upgraded license will be required when moving between major versions of Building Operation. For example: An upgrade license needs to be purchased when a 1.9.4 system is upgraded to 2.04. An upgrade license is not required to upgrade a 3.0.1 system to 3.2.4 There is currently one exception to this rule, licenses previously purchased for EBO 2022(4.0) can also run a EBO 2023(5.0) system.   From EBO 2.0 onward a scalable licensing model has been adopted and the cost of upgrades are determined based on the declared size and capability needs of the system. For more information please refer to the Pricing Policy - EcoStruxure Building Operation and the Part Number and Hardware and Software Matrix - EcoStruxure Building Operation 2023

Issue InfinityInput configured as counter does not count any pulses. Environment i2 devices B3 devices IOU modules Cause Here are two common reasons why the counter input may not be counting as expected: 1. No accumulation logic used with input. 2. Signal from the count source does not conform to specifications. Resolution 1. No accumulator logic used with input. The value of a counter input is reset to zero at every scan, in order to maintain the count value an accumulation strategy must be used, this can be accomplished via a conversion at the input or by using a PE program to accumulate the count in an InfinityNumeric object. a) Enter the following conversion in the counter input’s conversion field: Value + ElecValue Or b) Use the following logic in a PE program CountAccumulator = CountAccumulator + WaterMeterCount  (Where CountAccumulator is an InfinityNumeric object and WaterMeterCount is the name of the counter input)   2. The signal from the count source (Water meter, Power meter etc) does not have the minimum pulse width required by the input. For example, Infinet 2 devices (i.e. i2687) only support counter signal with a maximum frequency of 4 hertz and a minimum pulse width of 125 milliseconds. The DI8 IOU module has 2 channels that support counts of up to 10Khz with a pulse width as short as 50 microseconds. XPUi modules support counter inputs with a frequency up to 140 Hz and a minimum pulse width of 3.5 milliseconds. Refer to the manual for your count source (Meter) and verify the signal generated by it complies with the requirements of the Continuum hardware. For more information see the attached Infinity Technical Journal article. It describes several ways to reset the counter.   Note: Some meters will put out a pulse with a voltage equal to the supply voltage. In this case add a relay so the controller sees a dry contact per pulse.    

Issue Values are coming into Vista without issue but do not update on the graphics in the Xenta 7XX. Product Line TAC Vista Environment Workstation Graphics Xenta Server 701, 711, 721, 731 Cause If there is a Xenta Server in the database, when connection objects are not used to bind values between a controller and a Menta program in the Xenta Server, this graphic update can occur. It can also be because of the XIF for a device being formatted incorrectly. If the procedure below doesn't solve the issue, refer to LON device can communicate in Vista, but fails in a Xenta Server / XBuilder Resolution There are two options to correct this issue: Re-engineer the XBuilder project to use connection objects between the controller and the Menta program in the Xenta controller. The control task speed of the Menta program in the XBuilder project can be changed to a lower speed setting.

Issue Tables needed for linearizing a 10K thermistors for an I/Net 7716, 7718, 7728 and 7756 (upper board). Product Line TAC INET Environment 7716 7718 7728 7756 Cause Thermistors require the use of a look up table to linearize the data. Resolution Thermistor Inputs on PCU's 7716, 7718, 7728 and the upper board of a 7756 Enter the Temperature data in °C (First Column - 31 entries) Enter the corresponding resistance data in Ohms (Second column - 31 entries) Enter the dissipation constant in milliwatts per °C: 2 Low Temperature: -22.11°F (-30.06°C) High Temperature: 247.92°F (119.95°C) Point Value in °F: M=0.065942; b=-22.11377 Point Value in °C: M=0.03663447; b=-30.063207 Look Up Table: °C Ohms Current Self Htg Adj °C Adj °F VDC Counts Adj Cts 120 389 0.000481 0.045052 119.95 247.92 0.1872172 153 4095 100 680 0.000468 0.074521 99.93 211.87 0.3183521 261 3548 90 917 0.000458 0.096177 89.90 193.83 0.4199872 344 3275 80 1258 0.000444 0.12407 79.88 175.78 0.5587138 458 3001 70 1753 0.000425 0.158633 69.84 157.71 0.745767 611 2727 60 2489 0.0004 0.199471 59.80 139.64 0.9964769 816 2453 55 3045 0.000383 0.223671 54.78 130.60 1.1671138 956 2316 50 3602 0.000368 0.243359 49.76 121.56 1.32407 1084 2179 45 4368 0.000348 0.264484 44.74 112.52 1.5200445 1245 2042 40 5326 0.000326 0.283435 39.72 103.49 1.7375701 1423 1905 35 6691 0.0003 0.300218 34.70 94.46 2.0043736 1642 1768 30 8056 0.000277 0.308878 29.69 85.44 2.2308374 1827 1631 28 8777 0.000266 0.311174 27.69 81.84 2.3371678 1914 1576 26 9572 0.000255 0.312351 25.69 78.24 2.4453301 2003 1522 25 10000 0.00025 0.3125 24.69 76.44 2.5 2048 1495 24 10450 0.000244 0.312349 23.69 74.64 2.5550122 2093 1467 22 11420 0.000233 0.311127 21.69 71.04 2.665733 2183 1413 20 12490 0.000222 0.308669 19.69 67.44 2.7767897 2274 1358 18 13680 0.000211 0.304953 17.70 63.85 2.8885135 2366 1304 16 15000 0.0002 0.3 15.70 60.26 3 2457 1249 14 16470 0.000189 0.29383 13.71 56.67 3.1110691 2548 1195 12 18090 0.000178 0.286579 11.71 53.08 3.2200071 2637 1140 10 19900 0.000167 0.278241 9.72 49.50 3.3277592 2725 1086 8 21920 0.000157 0.268921 7.73 45.92 3.433584 2812 1032 6 24180 0.000146 0.258715 5.74 42.33 3.5371562 2897 977 0 32660 0.000117 0.224329 -0.22 31.60 3.8279419 3135 815 -4 36200 0.000108 0.211999 -4.21 24.42 3.9177486 3209 706 -10 55340 0.0000765 0.162028 -10.16 13.71 4.234772 3468 543 -14 69000 0.0000633 0.138199 -14.14 6.55 4.3670886 3577 435 -20 97130 0.0000467 0.105789 -20.11 -4.19 4.5332773 3713 272 -30 177200 0.0000267 0.063207 -30.06 -22.11 4.732906 3876 0 This spreadsheet is for a thermistor rated at 10,000 ohms at 25°C. Install a 10K Ohm Resistor in the "B" terminal (consult the TCON for the controller you are using for details) This look up table program is based on using 31 entries The data points do not have to be evenly spaced For the look up table to the 7756 lower board, see 10k Thermistor Look Up Table for an I/Net 7756 (lower board).

Issue Creating an Extended Trend Log for b3 (Infinet i1/i2) Point and Value Logs Product Line EcoStruxure Building Operation Environment b3 BACnet Controller Infinet i1 & i2 Controller Building Operation Automation Server, AS, ASP, ASB Extended Trend Logs (ETLs) Cause Using an extended trend log to store log records for long periods of time. The extended trend log is often saved on a higher-level server with more storage capacity. This extra storage capacity enables the server to store more records before overwriting the old ones. For more information, see WebHelp. Configure extended trend logs for b3/i1/i2 devices the same way as configuring extended trend logs in other Building Operation devices. There is one difference, however. do not use smart logs when configuring extended trend logs in b3 BACnet devices. Instead of using smart logs, use the Maximum Transfer Interval property to specify the transfer interval. Resolution In Listview, select the b3/Infinet Object (point or value), click Properties/Advanced Multiply the "Log records" by the "Log interval" to calculate the maximum transfer interval. The "maximum transfer interval" is the frequency at which the extended trend log will transfer log records from the b3/Infinet Object before any entries in the b3/Infinet controller log are overwritten Right click the object, choose New then "Extended Trend Log" In the Create Object box, set Smart Log to False, Set the "Maximum transfer interval" to less than that calculated above (2) Click Create For Infinet systems always refer to Infinet under the hood otherwise the creation is as the Webhelp for creating BACnet B3 Logs In theory it would be possible to create the Extended Trend Log in an ES (where there is more storage capacity), but this could introduce other timing and bandwidth issues, so it is usually best to keep the first Extended Trend Log in the AS, then extend this to a second Extended Trend Log in the ES, as shown. (the second ETL in the ES scan use smart logging in the usual way) If significant logging is required then External Log Storage should be considered. (the B3 or i1/i2 logs still need to be collected via Extended Trend Logs)    

Issue When starting Continuum version 1.94 (64-bit OS), the main screen is blank.   Product Line Andover Continuum   Environment CyberStation 1.94 (64-bit OS) WebClient 1.94 (64-bit OS) Cause When Continuum is installed on a 64-bit OS, the Main.bmp file is stored in: C:\Program Files (x86)\Continuum\UserProfile  However the application is looking for the file in C:\Program Files\Continuum\UserProfile.   Resolution Configure the Main Menu to search for the Main.bmp file in the correct directory: In the "blank" Main menu, right-click in the white space, and select Edit Right click in the white space again, and select Page Properties In the Background File field, press the "..." button.  In the "Open" window, navigate to the  C:\Program Files (x86)\Continuum\UserProfile directory Select the Main.bmp file.  Press Open Click OK on the Page Edit window In the Edit window, press the Run Page button (looks like a Lightning Bolt) to close the Edit window Re-start Continuum (if necessary)

Issue Cannot get the BACnet IP port to enable in a JACE-6 or JACE-6E controller. Environment I/A Series G3, JACE-6, JACE-6E, BACnet/IP Cause The JACE-6 and JACE-6E controllers include two Ethernet ports LAN1 and LAN2 and the user must select the appropriate interface adapter. Resolution The JACE-6 and JACE-6E controllers include two Ethernet ports LAN1 and LAN2 which represent Interface 1 (en0) and Interface 2 (en1).  The user must select the appropriate interface adapter.  To configure a BACnet/IP port: Expand the Ip Port in the property sheet view. Set the Network Number from “-1” to the BACnet network number for the network segment to which you are connecting.  If this is an existing BACnet installation, make sure to use the same network number already in use.  If this is a new BACnet installation, you can choose this number (for example: 100). Expand the Link component in the property sheet. Under Link, use the drop-down list for Adapter to select the network adapter to use. These adapters are automatically discovered and validated by G3. Review the Udp Port setting being used for BACnet communications.  By default, UDP port 47808 decimal (0xBAC0 in hexadecimal) is used. If your BACnet/IP installation is using another UDP port, enter this port number in the Udp Port property. Be sure to enable the IP port: right-click on the IP Port, go to Actions, then click Enable 

Issue The SUM Alarm does not generate an alarm when an Automation Server goes offline Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Enterprise Central Building Operation Automation Server Building Operation Automation Server Premium Building Operation Automation Server Bundled Building Operation Edge Server - Standard Cause The online status of the Automation Servers needs to be monitored so that an alarm can be generated if any of them go offline. Using the following configuration does not work. 1. Create a sum alarm 2. Add Source and set to AS path (e.g /SWXnetwork/servers/AS1). Replacing AS1 with a * makes no difference 3. Add System alarm ID and set to "Server Offline" 4. Add Alarm State and set to "Selection as required" Resolution Options that do work Option 1 System Alarm ID = Server offline Alarm Text = */Servers/* Alarm State = Alarm and Alarm Acknowledge - (Select as required). Option 2 System Alarm ID = Server offline Alarm State = Alarm and Alarm Acknowledge - (Select as required). Source Name = AS1 or AS*   Option 3 System Alarm ID = Server offline Alarm State = Alarm and Alarm Acknowledge - (Select as required). Source = /SWXnetwork/System/Server Communication/To/AS* - (As the alarm is in the ES, the path comes from the ES).

Issue What are the new features that are available in the 3.xx firmware version of the DPU. Should we upgrade to the latest EPROM revision for the DPU 7910A / 7920A If we do not upgrade the EPROM will I/NET work properly. 7910 / 7920 DPU Transactions not showing up in AMT - including Disabled / Deny Entry Sel / Deny Entry Schd (Schedule) 7910 / 7920 DPU Door Editor changes not downloaded to controller. Editor changes revert back to None. Product Line TAC INET Environment I/NET Seven DPU 7910A / 7920A 2.23 and above. Cause The recommendation is to always upgrade to the latest revision. In some cases this is not always possible. Please review the information below to determine if these features and fixes are required for your installation. Note: The implications are that if you choose to leave the EPROMs at the earlier revision, and you enable the new features which are a "Global" setting (for example User defined PIN) then the DPUs with the unsupported firmware will not accept these changes even though you have defined this at the Host. If you require these features then you MUST upgrade the DPU which require these features and / or fixes. Resolution I/NET Seven is backward compatible with all previous hardware firmware revisions of the DPU. The recommendation is too always upgrade to the latest revision to enable all of I/NET's features and fixes included in these revisions. In some cases this is not always possible. Please review the information below to determine if these features and fixes are required for your installation. Note: The implications are that if you choose to leave the EPROMs at the earlier revision, and you enable the new features which are a "Global" setting (for example User defined PIN) then the DPUs with the unsupported firmware will not accept these changes even though you have defined this at the Host. If you require these features then you MUST upgrade the DPU which require these features and / or fixes. If you have any additional concerns then please contact Product Support. Below are the New Features introduced in firmware revision 3.00: This release contains changes to support a real time clock and the ability to report messages with seconds. The DPU now supports generating an alarm for a card read of a card that has been disabled. The DPU now supports the use of User defined PIN numbers. The DPU now supports soft and graced APB. The DPU has been modified to handle the new user defined Duress scheme. The DPU now has the capability of generating a Reader Tamper Alarm by configuring a two bit DA at bit offset 4 for door 1 and 5 for door 2. Click Here to review the changes for EPROM firmware revisions 2.23 through to 3.04 for both the DPU 7910A and DPU 7920A. For SCU range of controllers refer to I/NET Security Control Unit (SCU) firmware releases. 

Issue Looking at the Status Information on the MSTP network object under the BACnet Interface of the Automation Server, the status read online FALSE Environment Automation Server - AS Cause The AS is not being passed the network token. If the Automation Server sees the token being passed on the bus but it never receives the token the AS will tag the MSTP network status as OFFLINE.. Resolution Possible reasons/solutions. CAUSE: Baud rate mismatch with third party devices. SOLUTION: If device does not support auto-baud change the speed of the MSTP to that of the device. CAUSE: A device on the MSTP is using the same mac id as the MSTP port. SOLUTION: Resolve the duplicate id issue. CAUSE: A defective device on the MSTP SOLUTION: Identify the defective device and replace it.

Issue Error displayed: Enhanced Alarm Delivery "There appears to be a problem with the configuration of this system. Please check to make sure that you have correctly installed MSMQ. The system will now shutdown."   Product Line Andover Continuum Environment Windows OS Cause The issue is that MSMQ is not installed on the machine or the installation is corrupted. MSMQ is a windows component that needs to be installed for enhanced alarm delivery. Resolution Install MSMQ from the Windows Control Panel > Add/Remove programs or Add/Remove Windows Components Reinstall Continuum NOTE: There have been instances where uninstalling MSMQ from Add/Remove Windows Components then allowing Continuum to install MSMQ resulted in a successful installation of the MSMQ.

Issue External resistors are required for Biasing and Terminating RS-485 trunks connected to an Automation Server (AS) Product Line EcoStruxure Building Operation Environment SmartStruxure Automation Server (AS) with  RS-485 trunk(s) under it. Field controllers on the RS-485 trunk; for example, the Network 8000 ASD controllers (MZ2, PEM1, etc)  Cause Bias and terminating resistors are not built into the AS hardware. Resolution External resistors are required for Biasing and Terminating RS-485 trunks connected to an  Automation Server (AS). See the Technical Reference Guide, revision 1.3, pages 2723, 2724, and 2771. Also check out the SmartStruxure-RS485-Network Installation Quick-Help video on the Exchange. Biasing and Termination details are now found in the "RS-485 Communications" chapter of SpaceLogic - Hardware Reference Guide