Issue Care must be taken about the precedence of operators in Plain English programming to achieve expected results. The following PE program was created with the intent of monitoring how long a point has been in alarm and unacknowledged The user intent was to have the program increment  ‘TimeInALM’ for every minute the point has been in alarm without an ACK WaitOneMin: IfTS > 59 then Goto CheckALM CheckALM:   TimeInALM = TimeInALM + PSS\ACX2.48\Num1 Alarm1 = On and PSS\ACX2.48\Num1 AckTransToOffNorm <> 255   IfTimeInALM > 4 thenGotoAlertGuard ElseGotoWaitOneMin AlertGuard:   TimeInALM = 0   GotoWaitOneMin Instead of incrementing as was the intent, ‘TimeInALM’ kept toggling between 0 and 1. Product Line Andover Continuum Environment Continuum Cyberstation Continuum (All CXs) Continuum Plain English Cause The rules of precedence dictate that the + is done first then the AND. So this is what happens: TimeInALM = TimeInALM + PSS\ACX2.48\Num1 Alarm1 = On and PSS\ACX2.48\Num1 AckTransToOffNorm <> 255 We start with TimeInALM = 0 PSS\ACX2.48\Num1 Alarm1 evaluates to 1 and so does PSS\ACX2.48\Num1 AckTransToOffNorm So we have 0+1 = 1 ANDed with 1 = 1 Now TimeInALM = 1, so second pass is 1+1=2 ANDed with 1 = 0 So TimeInALM is now zero and the cycle repeats Resolution Use parentheses to enforce the order of operations.  This resolves potential ambiguities. TimeInALM = TimeInALM + (PSS\ACX2.48\Num1 Alarm1 = On and PSS\ACX2.48\Num1 AckTransToOffNorm <> 255) Here is the complete PE Operator Order of Precedence for reference.

Issue How to determine if a controller is capable of Full Duplex and the Link Speed used. Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Cause How to determine if a controller is capable of Full Duplex. Link Speed can also be determined. Resolution Windows Powershell can be used to determine if a controller is capable of Full Duplex. The Link Speed and MAC address can also be identified. Identify the testing PC's network adapter name that will be used to connect to the controller. Using an Ethernet cable, connect directly to the controller's Ethernet port. Set the PC's IP address to one that is on the same subnet (but not to the exact same IP address of the controller). Using Windows Powershell, enter the following command line: Get-NetAdapter | Select-Object -Property Name, FullDuplex, LinkSpeed | where name -eq 'card name' where 'card name' is the name of the adapter as identified in 1. If the controller is capable of Full Duplex, it will be shown along with its LinkSpeed. Note, Full Duplex and Link Speed can only be achieved by the IT equipment the controller is connected to.

Issue Need to re-add firmware package to EBO for SmartX controllers and receive the error "firmware already exists" Product Line EcoStruxure Building Operation Environment Building Operation Workstation Building Operation Multi-purpose Controller (MP-C) Building Operation Multi-purpose VAV (MP-V) Building Operation Room Controller (RP-C) - all Building Operation IP-IO Cause Cannot add a firmware package of the same revision if one is already in the firmware list. Resolution Open the Control Panel within WorkStation and select Firmware Management Select the firmware package you want to delete and click the delete button

Issue When doing an "import Trend Logs" in TAC Vista Conversion Tool only HTTPs works and not HTTP. When using HTTP the error message below is shown: "Log on to Building Operation server failed because Failed to access the server, a network error occurred" Product Line EcoStruxure Building Operation Environment TAC Vista Conversion Tool version 3.1.1 Cause This is an issue fixed in TAC Vista Conversion Tool version 3.2. The issue is that the "Import Trend Logs" tab looks at the HTTP/HTTPS settings of the "Convert Database" tab instead of its own. Resolution Use TAC Vista Conversion Tool version 3.2 when available. Workaround: Set the HTTP/HTTPS settings on the first tab(Convert Database) even if "Import of trend logs" is done.

Issue License Administrator shows failed when adding a new license file. Product Line EcoStruxure Building Operation  Environment StruxureWare Building Operation 1.1.x License Administrator Windows XP Chinese Version Cause The License Administrator can not load the license file correctly that path contains non-English characters. Resolution Move the license file to a new location where the path does not contain non-English characters. (eg. "C:\")

Issue If a user is created in an ES domain, will that user be visible under the AS if the AS is in the same domain? Product Line EcoStruxure Building Operation Environment Building Operation Workstation Cause When a user is logging in for the first time to the AS, the AS will ask the ES for the user and password and then save it in the AS, but this will not visible for the user. The next time the user can log in to the AS even if the connection to the ES is broken as the user is now saved in the AS. Resolution Users will not be visible in the AS, only in the ES.

Issue Cannot connect to, and send reports to a monitoring station through a reporting service Product Line Security Expert Environment Security Expert Server Cause Trouble connecting to a central station Resolution All the necessary information for a reporting service should be provided by the monitoring station. These can include the following: Client Code Reporting Protocol Any necessary encryption information IP Address Port Number Phone Number Steps: Ensure all of the information provided by the monitoring station has been entered correctly. Ensure the Service is running. Has the controller downloaded the change? Ensure the Service has been assigned to the appropriate area. This is done in the Programming > Areas > Configuration menu. Ensure the Area's main portion / 24hr portion is armed. Ensure the Inputs that are being monitored have an input type assigned and are in the area. Ensure the Input Type has the correct options selected (e.g. generate alarms) Under Programming > Services > Options, ensure you have selected the checkboxes are selected for what you'd like to report to the monitoring station. Has the IP Port been opened on the controller's network to allow outbound and inbound traffic? Report IP services have some checkboxes in the Options tab that can help diagnose where the issue is. If the message is failing to reach the station, enable these options for troubleshooting. Log Acknowledge Response Log Polling Message Log Message Retries Log Reporting Failure ContactID also has a checkbox that will produce events for each step in the communication process and will indicate where the problem is. If the message is failing to reach the station, enable this option for troubleshooting. Log Modem Events to Event Buffer Important Note Always disable these troubleshooting options when the site is running without service issues as they will fill up the event database very quickly.

Issue When trying to lock the path of a binding point, the path doesn't change. Right clicking on a binding path to lock the path The locked symbol appears (1), but nothing happens to the path (2). 1. The path is unchanged. 2. The lock symbol is displayed When trying to save the changes the locked symbol (1) disappears. Product Line EcoStruxure Building Operation Environment Building Operation Workstation v. 3.0 Cause Lock Path is not converting the relative path to an absolute path hence the save is not working as expected. This works fine in version 2.0 and is fixed in version 3.1. Resolution Upgrade to version 3.1 where this problem is fixed. In version 3.0 the path can be manually updated to the correct locked path before saving. Manually updated binding path to a correct locked path In the example above the path to the Analog Value in the binding point is  /Server 1/test/Analog Value Therefore the correct locked path should be ~/test/Analog Value/Value Make sure you have locked the path before saving.

Issue Users login to EBO using Windows Authentication via the Workstation client encounters the error "User account not associated with a group. Contact your administrator".  Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server - SXWSWESXX00001 Building Operation Enterprise Central - SXWSWECXX00005 Building Operation Workstation - SXWSWWORK00002 Cause The "Local System account" used to run the "Building Operation Enterprise Server" service does not have sufficient permissions for EBO/Active Directory integration. One function call from EBO to the Active Directory fails when EBO tries to fetch the groups for the user logging in. Resolution The service account used to run the "Building Operation Enterprise Server" service must be able to read the token-groups-global-and-universal (TGGAU) attribute. The IT department or the Active Directory administrator needs to grant this explicit access to the service account by adding the service account to the built-in group in Active Directory called "Windows Authorization Access Group". For more details regarding the TGGAU attribute, see this article from Microsoft Support, Some Applications and APIs Require Access to Authorization Information.

Issue Digital SAT outputs are not available when using the EBO MN-HPFC object Product Line TAC IA Series. Environment I/A Series Network 8000 MN-HPFC Building Operation Automation Server Premium Building Operation Automation Server Cause The standard MN-HPFC device object in EBO cannot be used when the device was previously configured for Satellite Mode used in a Network 8000 system or R2 integration. Resolution Use the MN:MicroNet 2000 Generic object to interface to an MN-HPFC when configured for satellite mode.  This object provides a set of generic inputs and outputs that map over to the satellite controller points.  See the attached MN-HPFC Reference Manual that details the inputs and outputs starting on page 6-11.   DIN6 ( Digital Input 6 ) controls DO1 Sat Cmd DIN7 ( Digital Input 7 ) controls DO2 Sat Cmd DIN8 ( Digital Input 8 ) controls DO3 Sat Cmd

Issue What is spacing for the screw terminal blocks of the SP-MRDM2 2 Door Mini Expander, and what do the terminal blocks look like? Product Line Security Expert Environment Security Expert 2 Door Mini Expander Cause Screw terminal block details needed for ordering spare parts. Resolution The 2 Door Mini Expander uses two different screw terminal blocks. The lower is the normal terminal with 5.08 mm pitch labelled 2EDGK, and the upper is upside down, also 5.08 mm pitch and labelled 2EDGKF. See also data on the manufacturer's website.

Issue Error message when trying to edit the Licensing Settings for an Automation Server in Device Administrator. Error message: Failed to get current data from server: Error when attempting to get license information: :Request to [AS-IP-ADDR]:443 failed. [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:833) Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Premium Building Operation Automation Server Bundled Building Operation Automation Server Cause The Server has been added with EBO server protocol HTTPS, but no SSL certificate has been transferred to the server. The error message is displayed after taking the following steps: In Building Operation Device Administrator check Show licenses Select an Automation Server by checking the box in front of the question mark displayed instead of the server name Click License Settings Resolution This problem can be resolved either by adding a SSL Certificate to the server, or by changing the connection type to HTTP. Solution I: Adding an SSL Certificate to the server Click the server name in Device Administrator. (The server name will be a question mark as DA will not be able to communicate with the AS in this state.) Select SSL Certificate in the left menu and click Generate new certificate. Click OK if you agree to use an auto-generated password. (Otherwise click Cancel enter a password and click Generate new certificate again) Click OK Click Transfer to server Click OK Go back to the server list and verify that the State says Ready and that the name is displayed correctly. Solution II: Changing connection type to HTTP Remove the server from the Device Administrator Uncheck Show licenses if it is selected Select the server by checking the box in front of the question mark displayed instead of the server name Click Remove in the green bar above the server list Confirm by clicking Yes Add the server with connection type HTTP Click Add Server Enter the server address, password and choose HTTP as EBO server protocol

Issue Tolerances for resistors when used for RS485 bus termination and EOL for double balanced inputs. Product Line Security Expert Environment Wiring Cause Resistor specification required for ordering purposes. Resolution 330 ohm EOL resistors are required for the RS-485 bus and 1K ohm resistors for EOL zone (input) configuration. 330 ohm = 5% tolerance, Metal film 1000 ohm = 1% tolerance, Metal Film

Issue The value of an exported Infinet point is not updated in some or all of the subscribing controllers. Product Line EcoStruxure Building Operation, Andover Continuum Environment Building Operation Automation Server Continuum i2 Controller Cause The subscribing controller is offline or inaccessible when the IE update is broadcast. Resolution The main disadvantage with the Continuum Import/Export (IE) system is that, in certain cases, it is possible that the updated value may not reach one or more of the subscribers due to various reasons such as network or controller down problems, excessive traffic on the network, etc. This is not of big concern when the point is of an analog type that changes frequently such as a temperature input since the point will update again when the temperature changes in a matter of seconds or minutes at the most.  For binary values though, a missing update is a big concern. Consider an occupancy schedule point that turns ON at 08:00 and off at 17:00.  If a subscriber misses the 08:00 update the zones under control by the subscriber will be unoccupied the entire day. The Point’s Refresh Attribute. Continuum points have a ‘Refresh’ attribute that is used to force the IE system to send a new updated value, setting the refresh attribute to true forces the Infinity controller to export the point’s value regardless of whether it has changed or not. It is IMPERATIVE that a PE program periodically refreshes binary points that are exported in Infinity controllers such as i2 devices. In the schedule example described above, a program* can be added to the Infinet controller that hosts the exported point.  This program should be triggered by the minute system variable and coded as follows: *make sure the program is of the type Infinet Script Program This will ensure that any subscribers to the schedule OCC flag won’t go more than a minute with a stale value of the point. Refreshing points that reside under the Infinet interface of the Automation Server (EBO 3.1 and greater) If the point to be refreshed resides under the Infinet interface of the AS-P then there are some differences in the way the refresh is accomplished. The program will be of the type Script Program. The point will have a REFRESH property, you bind to the refresh property in the Script Program instead of the point's value. The most important difference is that while in the i2 device the export takes places when you set the value of the refresh property to true, in the Automation Server the export takes place when the value of the refresh flag is toggled, regardless of the value (true or false) Below is an example of a Script Program refreshing some value objects that reside at the Automation Server under the Infinet interface The statement DigValue1 = (DigValue1 = false) is just a very efficient way to toggle the value of the refresh property, it is equivalent to saying.... If DigValue1 = false then set it to true and if DigValue1 = true then set it to false. Things to consider when refreshing exported points. Do not refresh points at a fast rate as this will cause unnecessary traffic on the Infinet field bus, refresh rates of one minute or more are strongly recommended. For the same reason, when refreshing many points, the operation should be staggered to avoid flooding the Infinet bus with an avalanche of IE traffic at the same instant.

Issue Alarm values from LonWorks units in TAC Vista Product Line TAC Vista Environment Vista Workstation LON devices ASCs Xenta 102-AX, Xenta 104-A, Xenta 121 Cause Vista Workstation alarm objects can be used to monitor SNVT values from LON devices and alert the user when a value has gone outside of acceptable limits. For example, An alarm in TAC Vista if the nviSetpoint of a Xenta 104-A goes over 75ºF. This could also be used on programmable controllers -- any point in the database -- to avoid having to make Menta programming changes in order to alarm a point. The only issue with a Vista Server Change of state object is that the Vista Server will need to be running in order for the alarm to be received and actioned.  If multiple change of state objects are to be used consideration must be taken into the interface type as these points will be polled every second to check the state so actions can be taken on an alarm condition. This can easily overload a Lonworks interface if it is already managing lots of messages.  Resolution Create an object of the type "Change of state Dynamic SNVT" Right-click and go to properties. Click on the ALARM tab. Type in the alarm text for the Alarm. In this case, the alarm triggers if the temperature is over 75°F, so set the High limit to 75. Go to the Object tab and browse in the point that you want to monitor. In reference property select value. Click ok Go to the monitored point, right-click and select properties, change the watch setting to "watch"

Issue Are AS-P and AS-B full duplex? Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Premium Building Operation Automation Server-Bundled Cause Are AS-P and AS-B controllers Half Duplex or Full Duplex? Resolution AS-P and AS-B controllers are capable of Full Duplex 10/100BASE-TX communications.

Issue How to run the Import/Export Fixup Utility Product Line Andover Continuum Environment CyberStation Import Export Fixup Utility, I/E Fixup, IEFixup, IE,ImpExpFixupUtil.exe CX Controller, i2 Controller, Infinet Controller Cause Points not updating or alarms not coming in have resulted in PSS asking for the import export fixup utility to be run. Resolution Note: Before performing the steps listed below, make sure a database backup has been performed. Navigate to the \Continuum directory. The Import Export Fixup Utility is located here The filename is ImpExpFixupUtil.exe. Double-click it. It runs in a DOS window and when complete, creates a file in the format IEFixuptimestamp.log. In some cases the log file will open; in others it will be saved to the \Continuum directory.

Issue Minimizing network traffic when sharing data between Continuum Infinity controllers Product Line Andover Continuum Environment CyberStation All CXs All i2s, Infinet Controllers Cause Accessing a remote point’s attribute other than value is a point to point operation that generates extra traffic. Resolution Continuum controllers implement an Import/Export strategy in order to minimize network traffic when accessing the value of a point in a remote controller; this is in some ways similar to BACnet COV. When the value of a remote point is referenced in a PE program the system takes care of making sure the owner of the point sends the value to the subscriber(s) via the Import/Export system ONLY when the value changes. Consider the following PE program line… MyNum1 = RemoteCX\Num1 If a looping PE program sits on the line above no extra traffic is generated as the PE program gets the value of RemoteCX\Num1 from its local Import/Export table, information only goes on the wire when RemoteCX\Num1 changes value. The only problem here is that the Import/Export system ONLY works for the VALUE attribute, any other attribute requested from a remote object results in a point to point message on the network to obtain the requested attribute value. Consider the following PE program line in a CX controller we will call LocalCX NyNum1 = RemoteCX\Num1 size If a looping PE program sits on the line above a number of point to point messages would go on the wire every time the line executes. If there are many requests for attributes on remote objects a degrading in communications could take place. One way to avoid degrading communications as explained above is expose the value of the attribute in question by placing it in the value of a numeric object. Example: In RemoteCX create a numeric point (Num1Size) to hold the size of Num1 and use a PE program to set Num1Size Then the program in LocalCX will look like this… NyNum1 = RemoteCX\Num1Size Since the program is now going after the value attribute of Num1Size the import/export system will be used instead of point to point.

Issue When a TGML graphic is opened from Webstation it takes 30-120 seconds, depending on the number of values in the graphic, before the values appear in the graphic. It takes a long time before the actual graphic is opened. When the same graphic is opened using Workstation, it only takes a few seconds before the values in the graphic are updated. The problem is seen when Webstation is connected to the Enterprise Server (ES) if connecting directly to the SmartX server the values come in fast. Example of how it looks in Webstation before the values come in: Product Line EcoStruxure Building Operation Environment Building Operation Webstation version 3.0 and earlier Cause For every value in the graphic Webstation need to read the type of the value to know what kind of object it is and that is what takes time. This information is cached in Workstation and that is why the values are updated much faster in Workstation than in Webstation. This is changed in Webstation version 3.1. Now the type of information is cached in Webstation also. The first time the graphic is opened from Webstation it will take the same period of time as before. After that the type is cached and the values will be updated much faster the next time the graphic is opened. Resolution Upgrade the ES (Webstation is a part of the ES installation) to version 3.1 or higher

Issue The Xenta 102-AX Plug-in Airflow Parameters tab has a section called Airflow Reset. There are three values listed: Airflow Reset (%) CO 2 Low Limit (ppm) CO 2 High Limit (ppm) Product Line TAC Vista Environment Xenta 102-AX Plug-in Cause The Xenta 102-AX Product Manual states: The minimum airflow volume may be reset by a valid value at the network input variable, nviCO2. When the value received is at or exceeds the threshold value defined in configuration parameters nciCO2LoLimitCln and nciCO2HiLimitCIn the current cooling or heating mode’s minimum airflow volume will be changed by applying the network input variable nviAirFlowReset. The percentage value of this input variable is applied to the current minimum airflow value for an increase in air volume. This is not 100% accurate and will be fixed in later revisions of this product manual. Resolution To activate airflow reset based on CO 2 : nvoEffectOccup must not be OC_UNOCCUPIED or OC_STANDBY Both CO 2 Low Limit and CO 2 High Limit must be non-zero values There must be a valid CO 2 reading (either via SNVT nviCO2 or hardwired input) And the Airflow Reset (%) must be INVALID. (If the Airflow Reset has been changed to a valid value, to set it back to INVALID you can enter 163.835 or higher either in the plugin or on the snvt nviAirFlowReset in the LNS browser) The effect of a CO 2 based airflow reset are: If the CO 2 level is above the High Limit, the minimum airflow is reset 100% (set to maximum airflow) If the CO 2 level is below the Low Limit, the minimum airflow is reset 0% (set to its original value) If the CO 2 level is between the Low and High Limits, the minimum airflow is reset linearly between 0 and 100% as the value modulates from Low to High Limit. All of this can be overridden at any time if nviAirFlowReset has a valid value (either from a SNVT binding or via a value entered in the plug-in. This value will be limited between 0 and 100% and passed through to the airflow reset regardless of the CO 2 values. Example: If the Cooling Minimum Airflow Setpoint is 400 CFM and the Cooling Maximum Airflow Setpoint is 1400 CFM. The Airflow Setpoint can be determined based on the Terminal Load. If the Terminal Load is 50% then the Airflow Setpoint will be 900 CFM. Now if the CO2 Low Limit and CO2 High Limit are given values of 400 ppm and 800 ppm respectively, then the Airflow Adjustment would look like this: If the CO2 level was 700 ppm then the Cooling Minimum Airflow Setpoint would adjust up 75%. With a 75% adjustment the Airflow Setpoint would be calculated: ((Cooling Max - Cooling Min) * Airflow Reset) + Cooling Min  So in this example, that would be: ((1400 - 400) * 75%) + 400 = 1150 and the Airflow Setpoint table would now look like this: So if the Terminal Load is still 50% and the CO2 was 700 ppm then the Airflow Setpoint would be 1275 CFM. The Airflow Reset works a little differently if the 102-AX is in the heat mode.  Since the CFM setpoint does not modulate in the heat mode as it does in the cooling mode, the Terminal Load is not a factor.  Instead, the Airflow Adjustment percentage is applied to the Heating Minimum setpoint and the Warmup Maximum setpoint.  Let's say your Heating Minimum is 600 CFM and the Warmup Maximum is 1400 CFM.  And using the same CO2 high and low limits as above 400 and 800, if my CO2 reading is 500 then the CFM Setpoint will be 800 CFM. Additionally, if a valid value was entered on Airflow Reset (%) in the plugin or on nviAirFlowReset from an LNS browser then there would be the same effect of increasing the Cooling Minimum Airflow Setpoint by the value entered. Whereas by using the Low and High CO2 limits it is on a sliding scale as the CO2 moves up and down, the Airflow Reset increases the Cooling Minimum Airflow Setpoint by that specific amount. Then is still figured from the Adjusted Table based on the current Terminal Load from 0% to 100%. For example, if the Airflow Reset is given a value of 30% and the Terminal Load is 25% then the Airflow Setpoint would be 875 CFM as seen below: