Building Automation Knowledge Base

Issue When accessing an I/A Series R2 or I/A Series G3 station web page, a popup window is displayed warning of a possible security vulnerability. The popup warning is displayed differently depending on the browser version and Java version installed on the computer used for viewing the graphics. -------------------------------------------------------------------------- With Java 7 update 11 or newer, and Internet Explorer 8 or 9, the following popup windows is displayed (location string will vary):   Note that even if you check the "Do not show" checkbox, you will receive additional prompts because the prompt is displayed for each Java applet encountered in the current browsing session.  Likewise, if you close the browser and reopen it, navigating to the same site, the prompts will again be displayed. If accessing I/A Series G3 graphics, the following screen may be displayed: A variant of this message is as follows: --------------------------------------------------------------------------- If using a recent version of the Firefox web browser, the following message is shown in the graphic applet window: "This plugin has security vulnerabilities.  Click here to activate the Java(TM) Platform SE 7 U Plugin."   --------------------------------------------------------------------- When using the Mozilla Firefox browser to access I/A Series G3 graphics, the following security warning may be displayed (Click "I Understand the Risks" and follow prompts to continue):   Environment Windows computer Internet 9 or Firefox web browser Cause Known security vulnerabilities with the Java JRE software Resolution Since the issue is being reported by the Java software or the Java plugin in the browser, there is nothing we can do to directly resolve the issue. There are several workarounds possible, depending on how the site deals with browser security issues. The most secure approach is to allow the applet to be run each time you are prompted. If using Internet Explorer, click the [Run] button on the security warning popup window. If using Firefox, two actions may be needed.  First if the warning "This connection is untrusted" is displayed, click the "I Understand the Risks" Unfortunately, this is a Java issue, not an I/A Series R2 software issue. Oracle has added this popup to its browser plugin to warn the user that a downloaded Java applet may be unsafe to execute. According to information published by Oracle, it may take them up to two years to correct all the known security issues in the Java-JRE. Many of the known issues date back to before Oracle assumed ownership of Java. The only workaround at this time is to downgrade the Java-JRE to a version that does not notify its user that the Java applet to be executed may pose a security risk. We did some testing on Windows 7 with IE9 and found that Java 1.7.0.9 (Java 7 update 9) does not cause the prompt to be displayed. In addition, we found that in some cases we were able to greatly reduce the number of times the prompt appears in Java 1.7.0.17 by setting its security setting to Low (Java control panel applet, Security tab). On one of the virtual machines that we tested this on, the prompt would be displayed the first time you accessed the site and would not be displayed again until you closed the browser and reopened it. On a second computer, the prompt would be displayed each time you accessed a new site or re-opened the connection to the same site but not on multiple screen accesses from the same site. We are not sure at this time why some systems exhibit this different behavior. Note that when using Firefox 19.0.2 and Java 7 update 9 or earlier, a different message is displayed when the web page attempts to open a java window. This window is not displayed when using any version of Java that includes its own security warning popup. The security warning popup I am referring to is the same one displayed when using Java 7 update 17 and other recent versions on Internet Explorer 9 or Firefox 19. This message is designed to notify the user that there is a known security vulnerability with the addon being used, in this case, the out-of-date Java plug-in. There is a workaround published on the mozilla support site that documents a procedure for disabling these warnings when using the earlier versions of Java 7. This workaround does not solve the Java popup warning issue for the Firefox 19.0.2 / Java 1.7 update 17 combination. I did not test it with other combinations other than Firefox 19.0.2 / Java 7 update 9. Here is the configuration change for Firefox 19: Open Firefox Open a New tab Browse to about:config i.e., enter the string in the browser address bar Accept the security warning In the displayed list, right click on extensions.blocklist.enabled In the selection window, click Toggle to change the entry to false Close and reopen the browser. This will disable the security warning for all browser plugin applets, including Java 7 update 11 and earlier, Java 6 Updates 31-38, Adobe Flash Player 10.2.*, 10.3 or 11.0-11.4, Microsoft Silverlight 4.1 and earlier or 5.0/5.1, and about two dozen other plugins that have known security issues. At this time we have not found any workarounds for disabling the Java security warning popup that occurs with Java 7 update 12 and newer with either Internet Explorer or Firefox. As additional information regarding this issue becomes available regarding Java and Internet browser updates, this article will be updated as required.  Depending on site security restrictions, it may be necessary to disable Java when not using it for accessing I/A Series R2 or G3 systems.  See the following instructions from the Java web site: To disable Java - http://java.com/en/download/help/disable_browser.xml To enable Java  - http://java.com/en/download/help/enable_browser.xml In some cases, you may be able to bypass the warning but all your graphics pages do not  load.  This issue is sometimes caused by a security issue with some of the cached java temporary files.  There is a workaround, as follows: In the Windows Control Panel, open the Java applet. Under the "General" tab, "Temporary Internet Files"  section, click [Settings] Uncheck the box "Keep temporary files on my computer" Click [Ok] to save the change then click [OK] to exit the Java control panel.

Issue Get "Device has a different hardware version (hardware version X) than the project (hardware version X)" error message, when downloading an Xbuilder project to a device. Environment Xbuilder 5.1.X Xenta Server 5.1.X with hardware 1, 2 or 3 Cause There is a mismatch between the project's settings and the device's hardware version. Resolution Correct the Xbuilder project's setting to match the device's. Ensure that the hardware version shown in the "Hardware Version"  property field is the same as the device's.

Issue When sending Xbuilder Project to Xenta Server, an error will prompt that the Xbuilder project of hardware version 3 will be sent to a hardware version 2 controller, which is not allowed. Environment Xenta 500/700/913 Hardware version 3 Cause The hardware version setting in the Xbuilder doesn't match the real hardware version of Xenta Server. Resolution There is a hardware version option in the property window of Xenta Server. Check the hardware version of Xenta Server on the label of the controller, and choose the right hardware version in the Xbuilder to match the controller.   For more information about the hardware 3 Xenta Server, refer to TPA-VSTA-12-0029.00.

Issue After installing WorkPlace Tech, the Purchase program is accessed with no issue.  All the information is added including a Field Office Information, Shipping Information, End Customer Information, a WIBS serial number and a Part Number from the Package List.  When clicking on the Add to Order List button, a pop-up window indicates that the program cannot open the License File.   The license file does not accept any attempts to write to it. Environment WorkPlace Tech 5.x Windows 7 Cause A Windows user account setting is preventing proper operation of executable files. Resolution If the user account settings cannot be modified, then right-click on the executable file and select "Run As Administrator".  Right-click on the executable file and go to Properties > Advanced and select the checkbox for "Run As Administrator".  This applies the "Run As Administrator" setting always.  Now just double-clicking on the executable file is sufficient.

Issue Epson LQ-300+ II Printer does not work correctly in Windows 7 when used as an Alarm printer. Epson LQ-300+ II fails to print. Product Line Satchwell Sigma Environment Epson LQ-300+ II Sigma Windows 7 64-bit Cause When the printer is set to Continuous Print, alarms are spooled but the printer fails to print. The printer only prints if a change is made within Sigma > Alarm Manager > Configure > Live Printers. Resolution In this example the Epson LQ-300+ II printer was used. Remove the printer from the Devices and Printers window. Re-install the printer by "Add Printer." Use the CD that came with the printer and load the Windows XP 32-bit driver. Do not use the Windows 7 driver. Note: the printer name will be slightly different! Set the Printer Properties > Advanced tab > Print Processor to "Raw [FF auto]" Set the Printer to "Spool directly to the printer" Set the paper, fanfold or A4. Shut down the Sigma Client and Sigma Server, delete the printerconfigsnn.rec file in C:\sigma\data folder. (This will remove the old printer name in Sigma with the Windows 7 driver and avoid any confusion) Start Sigma Server and the Sigma Client, in Alarm Manager, highlight and re-assign the printer, set to continuous, tick LF and CR boxes.

Issue Insufficient information for the STR602 terminal detail / assignment Environment Sensor Cause The installation instructions does not give insufficient information regarding the connections of a STR602 sensor. Resolution The STR602 combines the RPW4425 and DRT3453 into one temperature and setpoint unit. The STR602 is a 3 wire device using a common 0V between the setpoint adjust potentiometer and the temperature sensing negative co-efficient thermistor. The terminations are: STR602 term 22 (Setpoint) STR602 term 23 (Temp 'C) STR602 term 24 (0Vcom) - this is the common of both the temperature sensor and the setpoint potentiometer. Setpoint Resistance (for BAS/Sigma use Lookup table 1, for SmartStruxure use the Satchwell thermistor ) Sensor Resistance  (for BAS/Sigma use Lookup table 1, for SmartStruxure use the Satchwell thermistor )

Issue Getting errors when opening Web Pinpoint or a Web client schedule. Environment Web Client Browser. Cause Communication back to the Web Client server is being blocked for Web Pinpoint and Web Schedules but other parts of Web Client are operating correctly. Errors displayed are: Resolution These errors are caused by a proxy server or firewall used on the site that is blocking some of the Web client data. Typically to remove: • Go to the Web Proxy or Firewall software • Edit settings - typically in the Advanced Tab • Disable HTTP Strict Mode • Save • Restart Proxy/ firewall   These steps may vary from product to product, but it is letting the majority of the Web Client data through in order to logon and view points etc, but blocking the Web Pinpoint and Scheduler data.

Issue When running TreeTech revision 3.1 or 3.2 attempts to open projects and edit object properties could result in the following error messages: "Failed to start viewproperty.exe. Verify path is correct" "Failed to start propeditor.exe. Verify path is correct" Environment TreeTech 3.1, 3.2 Windows XP,Vista, 7 Cause In TreeTech 3.1 the default path for projects was changed to support newer operating systems. Operating System Default Path Windows Xp\P C:\Documents and Settings\All Users\TAC\TreeTech\Jobs\ Windows Vista/7 C:\ProgramData\TAC\TreeTech\Jobs\ In revision 3.2 the path changed to use Schneider Electric.  Operating System Default Path Windows Xp\P C:\Documents and Settings\All Users\Schneider Electric\TreeTech\Jobs\ Windows Vista/7 C:\ProgramData\Schneider Electric\TreeTech\Jobs\ This can be seen live by creating a new project in TreeTech and observing the default path. Resolution Due to the fact that any previously created projects will not be moved when installing TreeTech revision 3.1 or 3.2 these files must be moved manually to the new default path. Once the project has been moved it will function normally without the error messages.

Issue DPUs / SCUs with addresses 28 thru 31 will give you "Deny Entry Tenant" message Environment 7798C & I/Net Seven rev 2.41 & above Cause During this time period, was the release of the OP5. This device occupies this address range. In I/Net Seven Rev 2.41 and 2.41A the 7798C has BIN file rev 1.12. With this BIN loaded on the 7798C will give you a "Deny Entry Tenant" on any card read. Resolution Replace the existing 7798C.BIN file with the 7798C.BIN rev 1.13 (out of I/Net Seven rev 2.43)   Please note that this bin file is not SBO compatible. At this time SBO has only a limited feature set for access control integration from I/NET.  Any SBO integration will limit DPU and SCU to addresses 0-27 on the 7798C  

Issue Are replacement covers available for the MicroNet 2000 wall sensors (MN-S, MN-SO, MN-SDK)? Environment MicroNet 2000 wall sensors: MN-S MN-SO MN-SDK Cause Customer wants replacement covers. Resolution As of February 28, 2013 replacement covers are available, part number MNA-STAT-1. Contact Customer Service to confirm price and availability, as they are subject to change.

Issue Getting the following error when trying to add a license. System error message: A value for property SalesContactEmail is required. Environment License Administrator Cause Incomplete or incorrect registration details Resolution Make sure all fields in the registration details are filled. Any field with a red border has not been correctly entered.

Issue Values only appear to update in Workstation when performing an upload. Environment I/NET Seven 2.43 and above StruxureWare Building Operation 1.3.0.978 and above Cause I/NET Interface Global scan rates are set to 0 (disabled) Resolution The Global scan rates defined within the properties of the I/NET Interface should be set to a value greater than 0 to display and automatically update values and controller status from the I/NET system.  The default settings are set to 60 seconds and 5 seconds for the device updates and point updates respectively. Image below shows the location of these settings within Workstation:

Issue Attempting to download and commission a Xenta programmable controller beneath a SmartStruxure AS results in the following error. The application generates successfully, the application downloads successfully, but the commission step fails. Environment SmartStruxure Automation Server Xenta programmable controller Cause There is some difference in the files generated on a save from the old Vista Menta editor, and the new SmartStruxure Menta editor. Resolution Create the Xenta programmable device Browse in the existing Menta file Service pin the device Open the Menta file from StruxureWare Building Operation. Go to File > Save. Close the Menta file. Commission and download.

Issue After creating a new Project and a new E: Equipment Database in TreeTech, the following error message appears when adding a new Network: Product Line TAC IA Series Environment Windows 7 TreeTech Cause TreeTech requires administrative rights to the Windows user account Resolution Right-click on the TreeTech shortcut Select 'Run as Administrator'

Issue Auto Generated Reports not running in 64-bit Environment Environment I/NET 2.43 64-bit I/NET 2.42 64-bit Cause Issue with windows scheduler is causing Auto Generate reports to fail. Resolution Modify existing or newly created auto generate reports. Click on the Recurrence button On the "Task" Tab, modify the "Run" string. At end of the string you will notice sch=<ScheduleName>. Add the characters"/T0" or "-T0" as shown below Before:   After:

Issue When point goes in alarm nothing is displayed in the active alarm viewer but when the point returns to normal the RTN shows up in the alarm viewer. Environment CyberStation Cause The Alarm Enrollment allows you to specify the transitions that gets sent to the active alarm viewer, make you the appropriate check boxes are checked. Resolution Configure the alarm enrollment to deliver both the alarm and the RTN

Issue Key for the standard Door Control Graphic Product Line Andover Continuum Environment Door Control Graphic PinPoint Cause Require a key for the standard Door Control Graphic Resolution

Issue Integrating several MNB-300 controllers to a UNC-510.  Bias resistors are available on the UNC-520 but not the UNC-510.  How can bias resistors be added to this MSTP trunk? Environment Niagara R2 UNC-510 Cause The UNC-510 was not designed to include built-in bias resistors for a BACnet MSTP trunk. Resolution The MNB-300 has built-in bias resistors that are disabled by default.  Remove the cover and enable them with the jumpers provided.  Keep in mind that no more than two sets of bias resistors are to be enabled for any MSTP trunk.  For more information, see the MicroNet BACnet Wiring, Networking, and Best Practices Guide (F-27360).  

Issue How to change the update rate for variables read from an OPC server in Vista server.  Vista in this case is running as the OPC client and therefore determines the request rate from the OPC server. Environment Vista 5.1.X OPC client (built in in Vista) 3rd party OPC server. Cause To optimise communication loads and efficiency it may be desirable to set the update interval for values read from an OPC server. A user may wish to reduce the update from a couple of milliseconds to 1 minute for example for values that don't fluctuate that much. Resolution The default value (which can be found on the Properties tab for the OPC server object in Vista under "Requested Update rate (ms) ) is set to 0ms. This is effectively "update as often as possible" and the actual update rate can be seen under the "Actual Update rate" property. To select another update interval, simply set "Requested Update Rate (ms)" to the desired value.

Issue How to configure individual alarm viewers for users. Environment StruxureWare Building Operation Workstation 1.3.0 Cause If all users workspaces are connected to the same alarm view then if one user changes the filter the alarmview will change for all users. This is because they are all links to the same object. To have individual filters you have to create multiple alarm views and attach them to the workspaces. Resolution Create a new alarm view by In workstation Right click and select new-view Select Alarm View Type in a name, click create Attach the alarm view to a workspace. Open the control panel in Workstation, click on account management Select the workspace you want to add the alarm view to in the drop down list under Workspaces Click on content. Click on the alarms pane (or add one) and click edit. In the field "initial path" browse to the alarm view you created before. Click close