Issue Eventlist in StruxureWare workstation is filled very rapidly with the following messages: - * Modbus group re-factorized - * Modbus group factorized - * Modbus illegal data address Environment StruxureWare Building Operation 1.4.818 Cause The problem is that it is illegal registers in the Modbus register group or groups. Modbus is trying to resolve this by refactoring the factoring and refactoring but is not successful. Resolution The possible solutions are: Identify the illegal Modbus point in SmartStruxure and remove from the subscription. Solution Split the group in to two so that the illegal Modbus point is left out of the groups. Disable group poll and Force individual point polling by setting incorrect function code for the group.   If it is difficult to identify the illegal Modbus point then you can use solution 3 to do this.

Issue b3 controllers in StruxureWare Building Operation do not seem to support Counter inputs. Environment Counter Inputs b3 Cause SmartStruxure does support the creation of Counter inputs within b3 controllers. Resolution Counter inputs are Analog Inputs.  When the Object Creation wizard is used to create an Analog input the user is prompted to select the electric type.  At this point select Counter.

Issue Federal Information Processing Standard (FIPS) Compliance Product Line EcoStruxure Building Operation Environment StruxureWare Building Operation Cause Is the Automation Server or Enterprise Server FIPS compliant? Resolution There is not Federal Information Processing Standard (FIPS) Compliance with the current release of Building Operation.

Issue Is it supported to access an Automation Server 1.4.0 with the Workstation 1.4.1? Are there any problems and what features are supported when accessing a 1.4.0 Automation Server with WorkStation 1.4.1? Environment Enterprise Server / Workstation 1.4.1 Automation Servers 1.4.0, 1.3 with SP1 and SP2 Cause Understanding of the new Runtime Compatibility mode available in 1.4.1 available during system upgrades Resolution Building Operation supports runtime compatibility between servers running two versions on a single system, during an upgrade process. Version 1.4.1 servers are runtime compatible with version 1.3 SP1 and 1.3 SP2 servers. The system is able to exchange runtime information between 1.4.1 servers and 1.3 SP1 or 1.3 SP2 servers. However, configuration changes cannot be made from an upgraded WorkStation via an upgraded Enterprise Server to a non upgraded Automation Server, such as creating, configuring, and deleting objects. There is also no runtime compatibility for WebStation. Runtime compatibility means you can delay the upgrade of some Automation Servers running version 1.3 SP1 or 1.3 SP2 while upgrading the Enterprise Server, WorkStation, Reports Server, and some Automation Servers to version 1.4.1. You cannot make any configuration changes on an Automation Server running the 1.3 SP1 or 1.3 SP2 version with WorkStation and Enterprise Server running the 1.4.1 version. However, you can make the changes using a parallel WorkStation running a 1.3 SP1 or 1.3 SP2 version that is connected to the Automation Server running the 1.3 SP1 or 1.3 SP2 version. Full compatibility is supported on Automation Servers running the 1.4.0 version   Additional detail is available on the Online Help http://help.sbo.schneider-electric.com/topics/show.castle?id=9807&locale=en-US&productversion=1.4&a=1 Supported Features: Navigate You can navigate in the system tree of an Automation Server running the 1.3 SP1 or 1.3 SP2 version, with WorkStation and Enterprise Server running the 1.4.1 version. However, object and property types removed in the 1.4.1 version compared to the 1.3 SP1 or 1.3 SP2 version are not be displayed in the system tree. Search You can perform an object or property search on an Automation Server running the 1.3 SP1 or 1.3 SP2 version, with WorkStation and Enterprise Server running the 1.4.1 version. However, object and property types removed in the 1.4.1 version compared to the 1.3 SP1 or 1.3 SP2 version are not be displayed in the search list. View Events You can view detailed information and perform commands on events on an Automation Server running the 1.3 SP1 or 1.3 SP2 version, with WorkStation and Enterprise Server running the 1.4.1 version. The 1.4.1 Enterprise Server will also store events from an Automation Server running 1.3 SP1 or 1.3 SP2 version. View Trend Logs and Trend Charts You can view trend log lists and trend charts on an Automation Server running the 1.3 SP1 or 1.3 SP2 version, with WorkStation and Enterprise Server running the 1.4.1 version. Extended trend log lists in the server running 1.4.1 version are functional and be able to retrieve values from a server running the 1.3 SP1 or 1.3 SP2 version. View Graphics You can navigate to and view a graphic on an Automation Server running the 1.3 SP1 or 1.3 SP2 version, with WorkStation and Enterprise Server at 1.4.1 version. Graphic variable values can be changed with Graphics Editor, but configuration data cannot be changed. View Alarms You can view detailed alarm information from an Automation Server running the 1.3 SP1 and 1.3 SP2 version, with WorkStation and Enterprise Server at 1.4.1 version. Also actions on alarms can be performed, such as assigning or disabling an alarm and enabling a Change-state logging. View Dynamic Values You can navigate to and view dynamic values in the Watch pane from an Automation Server running the 1.3 SP1 or 1.3 SP2 version, with WorkStation and Enterprise Server running the 1.4.1 version. However, because there is no way to navigate to and view objects or properties that have been removed in the 1.4.1 version, such dynamic values cannot be viewed. Transfer Values You can transfer values from an Automation Server running the 1.3 SP1 or 1.3 SP2 version, with an Enterprise Server or Automation Server running the 1.4.1 version and the other way around. Change and Force Variables You can change and force variables using properties on an Automation Server running the 1.3 SP1 or 1.3 SP2 version, with WorkStation and Enterprise Server running the 1.4.1 version. Lead and Shadow relationships Lead and Shadow relationships work for all objects with the runtime compatibility support. Backup You can make a backup of an Automation Server running the 1.3 SP1 or 1.3 SP2 version, with WorkStation and Enterprise Server running the 1.4.1 version. Log on to the Enterprise Server and then make a backup of the Automation Server running the 1.3 SP1 or 1.3 SP2 version. You can also log on directly to the Automation Server running the 1.3 SP1 or 1.3 SP2 version with WorkStation running the same 1.3 SP1 or 1.3 SP2 version, and then make a backup of the Automation Server.

Issue The Triac (V) outputs on the TAC Xenta 120-FC device goes ON, but never OFF. In this case, it can open the valve, but the device could not close the valve. Environment TAC Xenta 121-FC TAC Xenta 121-HP Cause If the device is powered with 24 VDC, the Triac will not work properly. According to the datasheet, the TAC Xenta 121-device should always be powered by AC, not DC. Triac is an acronym for Triode for Alternating Current, and could only be working with AC power supply. Resolution Correct the power supply to the device to use AC, not DC.

Issue A Plain English program is becoming disabled.  The controller error log logs the following error. 0x01402 (Reached end of the list). Environment Continuum Plain English Error b3 i2 Cause 0x00001402 (Reached end of the list) is a Plain English error.  This error most often occurs when a program is calling a Plain English Function that contains no byte code.. Resolution Edit each InfinityFunction in the controller to determine which function is empty (contains no programming).

Issue Some MSTP Devices show up when learned but other are not coming in. They worked fine on the Continuum install with the same MSTP network. Environment Automation Server Cause The AS has a maximum of 50 MSTP nodes and the b3 controllers that are not coming in are above this NodeId. Resolution Change the b3's NodeId's to a value below 50. 1. Use the Continuum system to change the Id by deleting the device object from the database, recreating it with the new NodeId. 2. Clear the controller to factory default.

Issue Bindings to PVB and PVR blocks in function block programs are lost after upgrading from 1.3 to 1.4.1. Environment StruxureWare Building Operation 1.4.1 Cause Text from Release notes for 1.4.1, page 38 10.2.2 Bindings to Public Variables and Public Constants in Function Blocks Bindings to Public Constants and Public Variables will be lost after upgrade from 1.3 to 1.4.1. The names of these Public Constants and Public Variables will be listed in the Conversion log produced by the 1.4.1 Device Administrator at the upgrade. Resolution After upgrade to 1.4.1 do the following: Locate the Public Constants and the Public Variables listed in the Conversion log. Select the Function Block Program that includes Public Constants or the Public Variables listed in the Conversion log and open the Edit Bindings View. Lost bindings will be displayed with: "Invalid- Variable not allowed to have a reference" Make a note of these bindings. Quit the Bindings View. Select and Edit the Function Block Program(s) that include the Public Constants or Public Variables, move a Function Block slightly to enable an insignificant change of the program to be discovered by the compiler. Save the Function Block program (the program then compiles again). Open the Binding View and re-bind the lost bindings. You will now also be able to select in which direction the value should be transferred. Save the bindings.

Issue How does the documented minimum pulse width translate into maximum pulses per minute? Environment All software/ firmware versions Cause The documentation defines the minimum pulse duration, not the number of pulses per minute. Resolution The documented 20ms min pulse duration for the Xenta 411 applies to both On and Off states. A complete min pulse cycle would be 20ms On + 20ms Off (50% Duty cycle), which equals 40ms. Therefore the max number of pulses per minute is 1000*60/40 = 1500 pulses/min or 25 pulses/ Second (25Hz).  

Issue When a graphic is opened in WorkStation, the graphic work area is just white. If the mouse cursor is moved over the white area, it is possible that some objects will show. Environment Detected in SmartStruxure version 1.4.1 WorkStation Cause This is caused by an issue in the graphics card display driver. Resolution Update the graphics card display driver to the newest version. Sometimes you will need to refer to the manufacturer of the card, and not the manufacturer of the PC.

Issue The option to download the application to a MNL-800 controller is not available in StruxureWare Building Operation Workstation. Environment StruxureWare 1.1 or higher Cause For the download option to be available the MNL-800 version must be 2.0. Resolution There are two options to handle this issue: Upgrade the controller board to version 2.0 Treat the controller as a 3rd party LON device by importing the XIF file and handling the program in an external version of WorkPlace Tech.

Issue Trouble with I/NET to Building Operation bindings. Site can bind an internal I/Net AO to a analogue value in Building Operation but the value won't update. Value appears with a blue triangle that says "unresolved".  Environment I/NET Seven together with StruxureWare Building Operation Cause I/NET points are integrated into Building Operation as points. When you upload the device configuration to the Enterprise Server, the configuration and point information are created in the System Tree pane. You edit and command the points as needed, using WorkStation and I/NET Seven editors. There are ten possible point types available in I/NET: Analog input (AI) Analog output (AO) Discrete input (DI) Discrete output (DO) Discrete alarm (DA) Discrete monitor (DM) Discrete control (DC) Digital input (GI) Digital output (GO) Pulsed input (PI) Resolution For any I/NET inputs (AI, DI, DM, GI and PI) it is only possible for operator changes to be made via the Building Operation Properties. It is not possible to programmatically control I/NET inputs and therefore not to be able to bind an output to an I/NET input point. It is also not possible to programmatically change any points Test state, any outputs (AO, DC, DO and GO) Manual state. And finally it is not possible to programmatically acknowledge an alarm. Therefore it is not possible to bind any script, schedule, FB, etc to any I/NET Points Test, Manual, Alarm Acknowledge or input point.

Issue Is it possible to acknowledge an alarm from a TGML graphic? Environment TGML graphics in StruxureWare Building Operation workstation and webstation. Cause Customers may wish to simplify the user interface and have a TGML graphic as the interface for all user operations. Resolution It is not possible to bind to an "acknowledge" attribute of an alarm from TGML, as this is not exposed. Our recommendation would be to use a panel and have an alarm pane in the panel as well as the graphic.

Issue DMO and SMO from SQL Environment DMO and SMO from SQL Cause A site which was running I/NET and StruxureWare Building Operation, and as required, I/NET is running as a service. The SQL DMO caused an issue with I/NET running as a service and interrupted the INET service. What is SMO and DMO DMO is part of SQL 2005 backwards compatibility. Which has to be installed when going to SQL 2008 to allow the old I/NET database to be imported. With SQL 2008 they now use SMO instead of DMO. You cannot remove DMO without creating a new data base.  Resolution I/NET SQL interface is based on DMO (Distributed Management Objects) so it will not work with SMO (Server Management Objects). That is the reason the backward compatibility must be installed.  Sites that are using a 64 Bit Workstation and 64 bit SQL then there is a 64 bit backward compatibility that should be installed. The 64 bit BCM is in the Support folder on the original install CD called SQLBCM_64Bit.

Issue Unable to find Modbus device on RS-485 line under an Automation Server. Environment Automation Server (AS) Modbus over serial line Cause Common wire is missing. Resolution Connect a common wire to the Shield connection on the COM port terminal

Issue How many events can be saved in the Enterprise server version 1.4.1? Environment StruxureWare 1.4.1. Cause The number of events which could be saved in 1.4.0 was 200 000 which some customers have thought is too few. Resolution The number of events which can be saved in the ES version 1.4.1 is increased to 1,5 million.

Issue The drop down menu to select WorkPlace Tech help manuals does not function in Internet Explorer 11. Environment WorkPlace Tech 5.8.6 Internet Explorer 11 Cause Internet Explorer changes how they handle compatibility mode for websites and webpage used to access the help files requires updating in a new version of WorkPlace Tech. Resolution Use one of the following options to access the help files Access them directly by going to the folder they are stored. On a Windows 7 (64 bit) operating system this is C:\Program Files (x86)\WorkPlace Tech\Help by default. Modify the index.htm, BACnet.htm, LON.htm, search.htm, Sensors.htm, and Software.htm files found in the C:\Program Files (x86)\WorkPlace Tech\Help\bin directory. Add the following line in front of the first "meta http-equiv=" line:   <meta content="IE=EmulateIE8" http-equiv="X-UA-Compatible" />   <meta content="IE-EmulateIE8" http-equiv="X-UA-Compatible" />

Issue Is it possible to acknowledge an alarm from a third party HMI? Environment StruxureWare Building Operation Cause The only way to acknowledge an alarm in SmartStruxure is via the Workstation/Webstation or EcoStruxure Web Service. Resolution The only way to acknowledge an alarm in SmartStruxure from a third party HMI is via EcoStruxure Web Service.

Issue How often is a SNVT in a Lon device polled if an StruxureWare Building Operation alarm monitors that variable? What happens if a shunt variable is used - is the polling rate still the same? Environment Lon Device StruxureWare Building Operation Cause Alarms are to monitor SNVTs in a Lon device put polling may overload the network. Resolution An alarm monitoring a SNVT will be polled every 100 ms. If a shunt variable is then activated the pollrate will drop to 5 000 000 ms. This can be seen in the variable manager: Go to Server 1/System/Modules/RuntimeDBManager/VariableManager/Variables in Workstation Locate the variable in question and ensure that the Imposed Pollrate column is shown.

Issue What SNVT_temp_p value in the AS local node is required to force an MNL controller to fallback to a Not Active (NA) condition?  The AS station is configured to use degrees Fahrenheit and standard SNVT_temp_p definition uses degrees Celsius. Environment StruxureWare Building Operation Cause SNVT_temp_p is defined by the standard as a degrees Celsius temperature with a range of - 273.17 to + 327.66 Deg C (0.01 Deg C).  A value of 327.67 Deg C (0x7FFF) will cause the MNL controller to fallback to an NA condition.  The AS station is configured to use degrees Fahrenheit the value must be entered in Deg F. Resolution Sending a Not Active (NA) To write SNVT values, one is to write from programming logic to the local node out of the mirrored network variable to the controller SNVT.  Example: Mirrored variable, local node -> Vav??? -> nvoSetpoint, writes to VAV??? nviSetpoint [MNL-V2RV3] Go to the local node Find the nvoSetpoint Expand to Temperature value Right-click and select Properties Under Basic tab, General Information Section, Limit Section, locate the Invalid value Use the following value for NA in your programming [for SNVT_temp_p it is 621.81]