Issue Satchwell “AL..S” series Spring Return Linear Actuator requires replacement Product Line Field Devices Environment Satchwell “AL..S” series Spring Return Linear Actuator installed on Satchwell MJF, MZ, MZF, VJF, VSF, VZ or VZF series Plug and Seat Valve Body. Actuator type :- AL..S series. Cause Obsolescence of Satchwell AL..S series Spring Return Linear Actuator. Resolution Replace Satchwell AL..S series Spring Return Linear Actuator with S-E M700 Spring Return Linear Actuator and Linkage Kit : AL..S = M700 + L7SV (880-0126-000) Linkage Kit. N.B. M700 is available with two different spring return actions M700 - SRSU (880-0430-000) = Spring Return Spring Up          ( M700 - SRSU will CLOSE a Satchwell Valve.) M700 - SRSD (880-0440-000) = Spring Return Spring Down     ( M700 - SRSD will OPEN a Satchwell Valve.) Should the Satchwell AL..S series Actuator include a wired Auxiliary Switch then the following S-E M700 Actuator specifications which include 2 independent 24 volt 4 amp AC-1 rated SPDT Auxiliary End Point Switches should be considered as appropriate: M700 - S2 - SRSU (880-0431-000) M700 - S2 - SRSD (880-0441-000) Alternatively Auxiliary Switch Pack S2 (880-0104-000) - Two independent 24 volt 4 amp AC-1 rated SPDT Auxiliary End Point Switches may be purchased separately permitting local installation.  Particular care should be taken when selecting a TAC Forta M700 Spring Return Actuator to replace an existing Satchwell ALMS, ALXS or ALES Spring Return Actuator.  Please refer to Replacement of Satchwell "AL..S" series Spring Return Linear Actuator by S-E M700 Spring Return Linear Actuator due to obsolescence.(Actuator Wiring). Please check the latest catalog for current equipment.

Issue Satchwell ALM series Linear Actuator requires replacement. Environment Satchwell ALM series Actuator installed on Satchwell MJF, MZ, MZF, VJF, VSF, VZ or VZF Series Plug and Seat Valve Body.    Satchwell ALM series Linear Actuators. Cause Obsolescence of Satchwell ALM series Linear Actuator. Resolution Replace Satchwell ALM series Linear Actuator with MV15B-230 Linear Actuator and Linkage Kit and wire as follows :- ALM = MV15B-230 + L7SV (880-0126-000) Linkage Kit. Actuator wiring :- ALM Terminal Number 1  =  MV15B-230 Terminal Number Y2  ALM Terminal Number 2  =  MV15B-230 Terminal Number Y1  ALM Terminal Number 3  =  MV15B-230 Terminal Number N N.B. ALM power consumption  =  4.5 VA          MV15B-230 power consumption  =  12 VA operating and 15 VA Transformer sizing Should the Satchwell ALM series Actuator include a wired Auxiliary Switch (ALA1211) then the following Accessory should also be installed on the MV15B-230 Actuator as appropriate and should be wired as follows :- S2 - MV15B = Two independent 250 volt 10 amp / 3 amp rated SPDT Auxiliary End Point Switches. Auxiliary Switch wiring :- ALA1211 Terminal S1  =  S2 - MV15B Switch 1 Terminal C ALA1211 Terminal S2  =  S2 - MV15B Switch 1 Terminal B ALA1211 Terminal S3  =  S2 - MV15B Switch 1 Terminal A ALA1211 Terminal S4  =  S2 - MV15B Switch 2 Terminal C ALA1211 Terminal S5  =  S2 - MV15B Switch 2 Terminal B ALA1211 Terminal S6  =  S2 - MV15B Switch 2 Terminal A   Please check the latest catalog for current equipment.  

Issue Replacement for discontinued I/A Series hardware UNC-410, UNC-520, ENC-410 & ENC-520 Product Line TAC IA Series Environment I/A Series R2 Universal Network Controllers UNC-410 and UNC-520 I/A Series G3 Enterprise Network Controllers ENC-410 and ENC-520 Cause Due to component availability, the following UNC/ENC parts have been discontinued as of 1st December 2013.  Resolution Discontinued UNC/ENC controllers can be replaced with the JACE 603, JACE 645 controllers series. The JACE 603 and JACE 645 are the first network controllers that can run either R2 or G3 Niagara applications when a corresponding license is installed.  New sites and expansions – these Network Controller parts come with the same metal box enclosure as the products they replace: Retrofit applications – these Network Controller parts are a replacement board that fits into an existing UNC/ENC enclosure: Refer to PA-00251 for details.  *Note - The parts for new sites and expansions are not available for all regions. Contact your local Schneider Electric sales representative if you have any questions.  * Updated May 2015 The parts TRD-RB-603-R2 and TRD-RB-645-R2 are not longer available. See below for the equivalent parts. TRD-RB-603-R2 > TRD-RB-603 + TRD-R2-RB-6XX TRD-RB-645-R2 > TRD-RB-645 + TRD-R2-RB-6XX _______________________________________________________________________________________________________ * Updated March 2019 The JACE-603 and JACE-645 has been discontinued as of June 2018.  The recommended replacements are the EcoStruxure Building Operation AS-P or the I/A Series JACE-8000. Refer to PA-00592 I/A Series JACE 600 End of Commercialization. 

Issue What are the replacement battery part numbers? Product Line Andover Continuum Environment Continuum and Infinity controllers i2, b3, CX, bCX1 SCX920, LCX810, LCX800, TCX850 Cause Replacement part numbers required. Resolution All the i2/b3 controller battery types are covered on pages 48/49 of the b3 Controller Technical Reference The CX9200, CX9400, and CX9900 all use 2 off: 12V 6.5A lead acid gel cells, Part number: 01-2100-423 The Part number for the bCX1 battery is: BCX1-BAT-KIT The Part number for the ACX57xx battery is: ACX2-BAT-KIT The Part number for the NC2 battery is: NC2-BAT-KIT For the older Infinity Controllers: SCX920, LCX810, LCX800, TCX850 – ½ AA 3.6V 850mA-Hr  e.g. LS14250

Issue Switched out IOU Module AC1Plus without powering down CX controller. Environment Continuum Cyber CX 99xx controller IOU Module AC1Plus Cause Switched IOU module with a new module without powering down the CX controller. Cannot hot swap out IOU modules Resolution Follow 'Replacing or Adding I/O Modules' section on page 26 located in the I/O Systems Reference Manual. Power down CX controller Replace IOU module

Issue You need to replace a faulty Xenta 301 controller. However, the existing unit is running System Version 1, and the network comprises approximately 12 Xenta controllers on a Menta-only network using the .nwc and .ndb configuration tools. Product Line TAC Vista Environment TAC Xenta 300 Cause New Xenta 301 controllers are shipped with System Version 3 by default. System Versions 1 and 3 are incompatible on the same network. Resolution To ensure compatibility, downgrade the new Xenta 301 controller to System Version 1.17 before installation. Steps to Downgrade and Replace: Download TAC Xenta 300 system program version 1.17 Use the Download Wizard as usual. Important: When downgrading from Version 3 to Version 1, do NOT retain the old application in the Download Wizard. Select "Clear Application" during the process. Manually Download the Menta Application and Network Configuration Use a serial cable to perform the manual download. Apply the appropriate TAC Menta versions for your network setup. Additional Notes Mixing different system versions on the same network can lead to unpredictable behavior and communication issues. Always verify the version compatibility before deploying new hardware.

Issue Uninstalling KB2858725 removed MS Dot Net 4.0 from the system and Web Client no longer accepts connections. Product Line Andover Continuum Environment Continuum 1.9x Windows 7 Windows 2008 Server Windows 2008R2 Server Cause Removal of KB2858725 not only removes the update it also removes Microsoft Dot Net 4, Dot Net 4.0 Client and Dot Net 4.5 extended. Resolution   Microsoft Dot Net 4.0 Extended. http://microsoft-framework-4-extended.en.lo4d.com/ Reinstall Microsoft Dot Net 4.0 Client profile. http://www.microsoft.com/en-us/download/details.aspx?id=24872 Note: Link to TPA-CONT-13-0005.00 for .Net Control errors with schedules once update for 4.5.1 is installed.

Issue Registering/Unregistering TAC Vista Server as a Windows service will allow the server to start automatically and run in the background of the PC (it won't show up on the Windows taskbar). This is not the same as having it run on Startup (for information on that, please see Configuring Vista Server to run on Startup). Product Line TAC Vista Environment Vista Server Microsoft Windows -- All versions Windows XP Windows Vista Windows 7 Windows Server 2003 Windows Server 2008 Cause Reference Chapter 16.3 of the TAC Vista Technical Manual "Running TAC Vista Server as a Service in Microsoft Windows XP" for more information. When you log out of Microsoft Windows or restart the computer, all running processes, for example, Vista Server, are shut down. These processes are not resumed at log on or at restart. You have to start Vista Server manually again. To get Vista Server to remain running at log off and automatically start up when the computer restarts, you can run Vista Server 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. Before you start Vista Server as a service, you must first install and configure your Vista Servers and your network and have everything running satisfactorily. It is not advisable to start Vista Server as a service until you have completed all the settings (including security and authority) and the TAC Vista system is running well. Resolution Register Vista Server to run as a Windows service Go to Start > Run Register the service by typing: Tacos.exe /service When you register TAC Vista Server as a Windows service, it will default to run under the "Local system" account.  This is not supported by TAC Vista Server. Right-click on My Computer and select Manage. Browse to Computer Management (local) > Services and Applications > Services Find TACOS, right-click and select Properties On the Log On tab, specify "This account:" with admin authority.  It is ideal to use a domain account with local administration authority if your system is a member of a domain. At this point, if you would like to start the service, highlight TACOS in the Services window and select Start the service. If you choose to run Vista Server as a service in a multi-computer network, we recommended that you run every Vista Server as a service. Change from running as a service to running as interactive Go to Start > Run Unregister the service by typing: Tacos.exe /unregserver You must then register the server back to interactive by typing: Tacos.exe /regserver Helpful Utility This utility will read in the current run mode of the Vista Server and allow you to switch between running as a service and an application. It also lets you set the user to run the service under. Click the image to the right to go to a Community post containing the utility .exe file. Accessing Vista Server Menus and Dialog Boxes Once the service has started, it is not possible to use the Vista Server menus and dialog boxes. To be able to use these, you have to unregister the service and start Vista Server in the normal way. LonTalk Adapter from Loytec When TAC Vista is running as a service and you are using a LonTalk adapter from Loytec, you must ensure that the program LConfig is also running as a service. You do this when you configure the network interface card. TAC Vista Tools and Microsoft Windows Vista Some of the tools installed in the installation folder of TAC Vista cannot run if TAC Vista is running as a service in Windows Vista. These are TAMIAN, CIPCL, SYSDOC, TADRAW, and DBGEN. Related Articles: Unable to save periodic report to network drive when Vista is running as a service Regional settings might differ when TAC Vista server runs as a service Dependencies for Vista Server running as a service Upgrading Vista while running Server as a service

Issue References Guide and changes from release 1.3 to release 1.4.x and forward Product Line EcoStruxure Building Operation Environment StruxureWare Building Operation site with regards of release 1.3 to release 1.4.x Cause In release 1.3 and earlier the reference system was relaxed allowing for bindings to be created in ways that made the applications error prone. In release 1.4 this is now being more strictly controlled, which will allow the system to: Help the user to not unintentionally create faulty combinations of references, resulting in bad/unpredictable application behavior and last man win situations Better understand and control how references will behave in copy/paste/move/delete situations. Improve performance in the system, e.g. the limitation of variable connectors is removed. For the complete Reference Guide, please download the pdf from the Download Center For instructions on how to upgrade an Automation Server and how to get the conversion log, See Upgrading Automation Servers from 1.3 to 1.4. For explanations of the entries found in the conversion log, See AS Conversion Log Analysis. Resolution What has changed There are 2 areas which have changed:   1. Rules Programmatic control: A reference means that data is sent from A to B. In Release 1.3 it was possible to send data from A to B and from C to B. This gave a "last man win" situation. In Release 1.4 it is only possible to send data from exactly one source to a recipient. This means A to B and C to B is no longer allowed. User control: This is where properties are displayed in graphics, watch windows and other client components. In release 1.3 it was possible to change a property that was programmatically controlled. This gave a "last man win" situation. In release 1.4 it is not possible to change a property as a user if this property is programmatically controlled by something else. The property will automatically be read only for the user.   Public signals: In release 1.3 and earlier, it was possible to programmatically control a public value in programs. Public signals are intended to be used for user control, while inputs are intended for programmatic control. In release 1.4 this is now changed to the following: Public signals in programs (FB/Script/Menta) can be referenced by user control - NOT by programmatic control Public signals intended for programmatic control must be changed to inputs and rebound. This will give the following benefits: Public signals cannot be forced, while inputs can. If a user needs to take control of a programmatically controlled input, via e.g. graphics or watch window", he will force the signal and there will be no risk of a program overwriting the user value. As stated above - if an input is programmatically controlled, this will for the user be read only. However, force is still possible. There is no more risk for "last man wins" situation between user control and programmatic control. The system will remove any ambiguity with these new sets of rules. Update: Release 1.4.1 and later version add the feature of binding to PVB/PVI/PVR back. But for Script, it still keeps the same. LonWorks Local Node nvis: In release 1.3 it was possible to programmatically write to local node NVIs. These NVIs exist to receive data from the LonWorks network. This gave a "last man win" situation. In release 1.4 it is no longer possible to programmatically control local node NVIs.   2. Definitions In release 1.3 a reference could be a) relative b) system absolute c) server absolute In release 1.4 a reference will be a) "normal" b) Locked A reference created by the user will always be normal (which means relative). In the bindings view the user can then choose to "lock" a reference (which means server absolute). The references will behave identically until a copy/paste (or import/export)  operation is done.         Upgrade Upgrading from release 1.3 to release 1.4 will apply the new sets of rules. It is there for very important to read the log to understand if any existing references in release 1.3 will be impacted during the upgrade For AS: In the Device Administrator the logs are available before the upgraded DB is deployed to the AS. It is up to the user to either examine the upgrade log, make changes in running release 1.3 and rerun the upgrade, or to make the changes after upgrade. It is recommended to do changes prior to upgrade to ensure a fully functional system directly after upgrade. Some warnings are benign and can be disregarded, please refer to release notes for more information. IF an upgrade detects that references will be impacted, the user will be informed about this with a orange progress bar indication and a written information that the upgrade succeeded with warnings. After upgrade, all invalid or unresolved references will be visible from WorkStation for further examination if needed.

Issue Recommended USB to Serial RS-232 adapter Environment I/A Series R2 UNC’s, G3 ENC’s, MicroNet 2000 MN-CIM, and MicroSmart MSC-LIM. (NOTE: MN-CIM is obsolete as of December, 2011. See Product Announcement PA-000164. There is no functional replacement available) Cause PC or Laptop without RS-232 Serial Port (DB-9 male) connector. Resolution IOGEAR (p/n: GUC232A) has been validated to work in the following applications: 1. HyperTerminal  with a direct connection to the ENC/UNC’s serial port (COM1) using RS-232 adapter and Schneider Electric p/n: UNCC-405 (RJ-45 socket to DB-9 socket adapter, null modem) and CBL-RJ45-** (flat silver satin cable). 2. MN-CIM interface module for use with the TAC MicroNet 2000 series controller interface and Air Balance software. 3. MSC-LIM interface module for use with the DMS MicroSmart Controller Interface (equipment with a handheld port). Click here for product data sheet on the IOGEAR adapter

Issue TAC Xenta Server webpage does not work smoothly. A typical example is when you try to change a value. The small dialog that should pop up to change a value might pop up and immediately disappear. Product Line Satchwell MicroNet, TAC INET, TAC Vista Environment TAC Xenta Severs Xenta 511, 527, 701, 711, 721, 731, 913 TAC Vista 5 Webstation Cause Using unsupported version of Java may cause various issues. For example, Xenta server webpage does not display smoothly, time schedule does not show up or can not be edited, etc. Resolution Below is the Java compatibility matrix of TAC Vista 5.   5.1.9 5.1.8 5.1.7 5.1.6 5.1.5 5.1.4 5.1.3 5.1.2 5.1.1 5.1.0 5.0.3 5.0.2 5.0.1 5.0.0 Java 1.5 update 06               X X X X X X X Java 1.6 update 11           X X               Java 1.6 update 17            X 1                 Java 1.6 update 20 X X X X X                   Java 1.7 update 51 X                           1  TAC Xenta Server 5XX/7XX/913 SP1. Log into The Exchange and then click here to download the full Vista Compatibility Matrix. To uninstall an unsupported version of Java and install the supported version, refer to Xenta Server webpage automatically logs out while waiting for Java to load.

Issue Is there any way to get the Xenta Server trend log data without TAC Vista? How to get the Xenta Server trend log values from the web interface How to e-mail the Xenta Server trend log values Product Line Satchwell MicroNet, TAC Vista Environment TAC Xenta Server TAC Xenta 511, 527, 555 TAC Xenta 711, 731 Cause The TAC Xenta Server is installed standalone and TAC Vista can not be used to view or save the trend logs. However if you want to collect and store data from multiple trend logs on a regular basis we do strongly recommend using TAC Vista. Resolution There are two ways to get the trend log data from a Xenta Server (except for TAC Vista): 1. Manually copy the trend log values from the Xenta Server web interface In XBuilder, create a trend log page and drag the trend log to it Log in to the web interface and go to the trend log page Right click the trend log signal name and choose "view values" Copy/paste the values to for example Excel.   2. Forwarding the trend log data as an e-mail First make sure that the SMTP settings in XBuilder are correct. For troubleshooting on this, see Troubleshooting sending emails from a Xenta Server Create a receiver group and define one or more e-mail addresses to receive the trend log data. Highlight the trend log.  Under Log Data Transfer Settings, click the Receiver Group box, and select the Receiver Group list. In the Subject box, type a suitable subject. If desired, also type a suitable text in the Body box. In the Log Events Included box, click Yes to attach log events to the e-mail message. You must also specify when the log data is forwarded. For this, create a time object which you drag to the "send data" signal on the trend log. When the trend log data is forwarded, the receiver group e-mail addresses will receive the trendlog data as an attached .log file. For more information, see chapter 8.2.2. in the TAC Xenta Server – Web Server, Technical Manual

Issue Receiving the following error when attempting to navigate to the Xenta web interface. "TAC C503Boot/x.x.x.x not configured". Product Line Satchwell MicroNet, TAC INET, TAC Vista Environment Xenta Server 511, 527, 555 Xenta Server 701, 721, 731 Cause Device web interface has stopped working or flash drive / hard disk has been corrupted on the Xenta Server. Resolution Attempt the following steps to resolve this problem: Try restarting the device and see if the unit comes back online, remember to wait 1-2 minutes for the unit to restart.  Check the RUN LED on the panel, if the LED is a solid green this indicates the device is running normally, and your access should be restored. If the LED is RED, solid or flashing this would indicate a problem with the device. Attempt to restore or upgrade the device to the latest firmware.    You can download the latest firmware version from the Schneider Electric Exchange. If this fails then then reference Xenta Server "Run" light is solid red with no communication via Ethernet.

Issue Receive Error: "Unexpected file format" when attempting to open Graphic Page Environment I/NET Seven 2.41 graphic pages Cause When creating, modifying and saving graphics in revision 2.41 and then attempting to open these graphic pages in previous versions of I/NET this error "unexpected file format" is presented. Resolution This issue has been rectified in 2.41A and above. I/NET Software are available for licensed Partners to download on The Exchange Download Center.

Issue Changing between view and edit modes using Workbench after adding a PxInclude object to a parent px file with a schedule causes Workbench to lockup and fail. A restart of the Workbench application is required. Environment TAC I/A Series G3 ENC-410, ENC-520, and Enterprise Network Server Cause Workbench failed to process the scheduler within the PxInclude. Resolution The issue has been resolved in bajaUi module versions 3.3.34.2, 3.4.64.1, 3.5.34.1 and higher.  The files, bajaui 3.3.34.2 is available for download from The Exchange Download Center.  Download the bajaUi version zip file for the required G3 build. Caution: Always backup the station database before performing any upgrade.   If Enterprise Network Server, stop running station and close the Workbench application.  Extract the file and replace the existing bajaUi jar file in the appropriate modules directory of G3. Start Workbench and start station if Enterprise Network Server. Use the Workbench Platform Software Manager to the upgrade the bajaUi module in ENCs as required.

Issue Can the actuator collar and set-screws for the VAV controllers (MNL, MNB, MicroNet 2000 product lines) be purchased separately? Product Line TAC IA Series Environment VAV controllers (MNL, MNB, MicroNet 2000 product lines) Cause Replace parts in the VAV (Variable Air Volume) controllers. Resolution Actuator collars and set screws for VAVs can only be purchased in a retrofit/enhancement capacity as detailed in Product Announcement 06-030. The part number for ordering is DCQC-234-10.

Issue With triac digital outputs, such as those in the i2866-V, what is the fastest they can switched for Pulse Width Modulation (PWM) applications? Product Line Andover Continuum Environment Continuum controllers with triac digital outputs. Cause Require information on using triac outputs for Pulse Width Modulation control. Concerns over minimum pulse times and frequent switching. Resolution The triac outputs on some Continuum controllers (such as the i2866-V) will be able to perform pulse width modulation from a minimum of 0.1s pulses. As apposed to relays, outputs using triac's have negligible wear and tear during extended use. Switching the outputs frequently, such as once a second, should not cause any premature failure issues.  Further data on the triac outputs on the i2866-V: Specification sheet Installation Guide for wiring details. i2 Technical Reference Manual

Issue Where can I find information on EWS? 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 SmartConnector Cause Documentation required Resolution Documents can be downloaded from The Exchange Download Center - EcoStruxure Web Services EcoStruxure Web Services Specification can be found at: SmartConnector Server

Issue Problems installing Vista Webstation 5.1.5 or newer Product Line TAC Vista Environment Vista Webapps (Webstation) 5.1.5 Windows 2008 Server 32-bit or 64-bit. Cause In order to install TAC Vista Webstation successfully on Windows Server 2008, there are a number of steps and prerequisites to be checked. Resolution In order to install TAC Vista Webstation successfully on Windows Server 2008 it has to be done in the following order: PC Preparation – Only if you can not access the Run as administrator context-menu! Log in as an administrator and create a new administrator group (eg. VistaAdmin) and add a user to this group. By doing this you will be able to access the Run as administrator context menu later on (users added to the Windows administrator group do not always receive full administrator rights). Install IIS 7 and ASP.net Start the Server Manager (Right-click on Computer in the start-menu or the Computer desktop icon if running classic start-menu and select Manage). Right-click Roles and click Add roles. In the dialogue that opens up click Next and then select Web Server (IIS). In the dialogue that follows click Add Required Features. Click Next (twice). On the select Role services page select ASP.net. In the dialogue window that appears click Add Required Role Services. Click Next and then click Install. NOTE FOR WINDOWS 7 USERS! Whilst Windows 7 is not officially supported for running Webstation it may be used in a test environment. It's important to note that the IIS and ASP.net installation is slightly different - the user is not asked to add roles, the user is asked to add windows features (see screenshot below). Ensure .net framework 4.0 is installed Open Server Manager and select Features. Scroll down and ensure .net framework 4.0 is installed. If not: Open Internet Explorer. From the menu select Tools\Windows Update (Safety\Windows Update in IE8) Run windows update and install .net framework 4.0 Install TAC Vista Server and any hotfixes Install TAC Vista Webstation and any hotfixes As administrator, register ASP.Net version 4.0 Click on start and then All programs\Accessories. Right-click on Command Prompt and select Runs as administrator. If using 32-bit: Open explorer and locate the %SystemRoot%\Microsoft.NET\Framework\v4.0.30319\aspnet_regiis. If using 64-bit: Open explorer and locate the %SystemRoot%\Microsoft.NET\Framework64\v4.0.30319\aspnet_regiis. Ensuring that the directory is set to C:\ copy the file path into command prompt and the add the following text : aspnet_regiis.exe -i -enable Press Enter Confirm the installation was successful Click on start and then type inetmgr in the search box. This will open IIS manager. Expand the hierarchical menu on the left and then expand the Sites folder. Expand Default Web Sites and select Webstation Right-click on webstation and select manage application > Advanced Settings. In the Application Pool field it should say SE ASP.NET v4.0 Classic All that is left now is ISAPI, CGI (see "HTTP Error 404.2 - Not found. The page you are requesting cannot be served because of the ISAPI and CGI Restriction List settings on the web server") and DCOM settings (see TAC Vista Installation Manual or Helpful Vista Utilities - Configure DCOM instantly, Register ASP.NET). License problem: Webstation - No license Available

Issue Problem with Override control of BACnet Binary Output (BO) on IA Series BACnet Unitary, VAV and Zone controllers with firmware version 1.420 or earlier. When a BO override is released the value will not reflect the correct null state and may appear to still be in the previous state. After relinquishing the priority from the point, the actual Priority status shows up correctly as "Null". However, this is not reflected in the Building Operation Workstation "Watch" window. (Click on image below for larger view) Product Line TAC IA Series, EcoStruxure Building Operation Environment StruxureWare Building Operation 1.2 Automation Server BACnet Interface with MNB 1000 with MNB 300, MNB-Vx, or MNB-70. Cause When requesting the complete "Priority Array" for an output object, the values returned match their actual values, i.e. 0, 1 or "null". When requesting individual "priority array indexes" index numbers that are "null" will incorrectly return a 0 or a 1. Resolution MNB series V1.424 firmware for the VAV, Unitary, and Zone controllers resolves this issue. When an individual "priority array index" is requested, the priority input value of 0, 1, or “null” is returned. The issue only applies to the MNB-V1, MNB-V2, MNB-70, and MNB-300. The MNB-1000 does not have the "Priority Array" problem. The MNB series V1.424 firmware files are placed in the WorkPlace Tech firmware folder during the installation of WorkPlace Tech 5.8.2.