Issue Can I/NET 2000 translate key/card numbers greater than 24000 without using “the Key/Card Translation Table? Environment I/NET Site Cause Can I/NET 2000 translate key/card numbers greater than 24000 without using “the Key/Card Translation Table? Resolution I/NET 2000 revision 2.x can translate “large” key/card numbers. However, this feature requires that the SLI and DPU firmware loads are compatible. Refer to TCON 237 for more details.

Issue Most PCs are now shipping with Windows 8 and many drivers for Windows 7 do not exist for the hardware.   Environment Windows 8, CyberStation Cause New PCs and laptop are shipping with Windows 8 and Windows 7 drivers are not available for some newer hardware.   Resolution At this time CyberStation 1.94 and 2.0 are the versions that are shipping and no versions of Windows 8 have been tested with CyberStation. It has not been determined whether a future version of CyberStation will be qualified on Window 8. Refer to the Software and Firmware Compatibility Matrix for the operating systems compatible with CyberStation.

Issue Cable needed to Direct connect a Laptop or Desktop to a PCU Product Line TAC INET Environment I/NET site Cause The first asynchronous port (P4) provides an RS232 port for direct connection to a PC or external direct dial (Hayes) modem. The RS232 port’s baud rate is set using the HHC. Resolution CBL072 for a 9-pin PC connection CBL073 for a 25-pin PC connection Refer to TCON 096 For CBL072 information, please refer to Cable Connectivity to I/NET.

Issue COV values are stale Environment Niagara G3 Cause Recent changes have been made to the BACnet jar file to address this issue Resolution Go to The Exchange Download Center and download the latest niagara BACnet jar file 3.6.47.9

Issue CALC is not an option in the DDC editor of a 7700 or 7716. Environment DDC Editor 7700 7716 Cause The Calculation module exists only in MR controllers and ASCs. Resolution Use the DCU or PCU Calculation editor. Refer to TCON 209 or TCON 237 for more details about Calculations and DDC modules.

Issue There are many situations that a remote computer wants to monitor and control local Vista values. C/S construction (Client/Server) and B/S construction (Browser/Server) are the two solutions for these situations. Environment Multi-PC environment Vista Cause In many cases this application is needed. Resolution The C/S solution for Vista is Remote Workstation and Vista Server. On the client computer, only the Vista Remote Workstation software needs to be installed. Then it can connect to the Vista Server on the server computer. The Remote Workstation software can be downloaded from here. The B/S solution for Vista is Webstation and Vista Server. On the server computer, Vista Webstation software needs to be installed. Then on the client there is no need to install any software. Just open the IE browser, and type the IP address of the server computer, all the content in the Workstation of server computer can be shown in the client computer. The Webstation software can be downloaded from here.

Issue In our portfolio we currently only list VF208 series valves with elongated wafer type eyelets  Environment VF208L VF208W Cause Applications sometimes requires a valve with lugs instead. Resolution VF208 valves with lugged flanges are available on request. Please contact Product Management or Order Entry for information on ordering this option. The Specification sheet can be downloaded here.

Issue Unable to upload the same Lua script to multiple Room Controllers at the same time Product Line EcoStruxure Building Operation, EcoStruxure Building Expert Environment Building Operation Automation Server Premium SSL SE8000 (all) Cause The alternative method of uploading the script to each of the room controllers using a USB cable Resolution To upload a script to multiple Room Controllers, follow the below steps: (This procedure assumes the BACnet MSTP network is already setup) 1 - Log in to Building Operation Workstation 2 - Right-click on MSTP network and click "Search" 3 - Search for "Lua program 1" or any other Lua program object 4 - Highlight all the Room Controllers that the script will be transferred to then click on the "show/hide property grid" button. 5 - Expand the "Basic" tab and copy the Lua script in the "Description" field then click Save. 6 - The script will be uploaded to each of the Room Controllers one at a time and will be played automatically. Recommendations & Limitations: - Each Lua Program can take up to 460 bytes of text (per script). (Total of 10 Lua programs) - Script must be placed on a single line. Use semicolons ( ; ) as carriage return - Use multiple Lua programs if the 460 bytes limit is exceeded - Encapsulate logic inside the following if statement if the logic is intended to run once: if not init then    ---Script logic here    init = true end For general information about Lua programming for SE8000 Room Controllers, refer to the following guide: Custom Programming Guide for SE8000 Series Room Controllers - Application Guide

Issue Browser wbapplet Guest user account login issue with I/A Series G3 versions 3.6.406 and 3.7.106 - indicates syntax error. Environment I/A Series G3 build 3.6.406, web module 3.6.406 I/A Series G3 build 3.7.106, web module 3.7.106.4 Cause Issue with web modules 3.6.406 and 3.7.106.4. Resolution Download and install the latest Consolidated Patches for the 3.7.106 environment.  This is available for download from The Exchange Download Center.

Issue There is potential for confusion around the backward compatibility offered in EcoStruxure when the version of Enterprise Server differs from that of Automation Servers in the same system Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation SmartX Servers Cause The 3.1.1 Release Notes refer to a new 'Multi-version system' with the possibility of a v3.1 Enterprise Server but with v3.0 Automation Servers able to function long term within the same system (albeit with some engineering limitations).    This implies that AS running earlier versions than v3.0 cannot coexist, attempts to add AS running v2.0 to ES running v3.0 have produced errors. However........ The System Upgrade Reference Guide refers to 'Runtime Compatibility' with Version 3.1 that states that Automation Servers running v1.8, 1.9, 2.0 and 3.0 can all coexist with an ES running 3.1 without issue Resolution Both documents are true, but there are two possible situations that need to be considered: Situation 1) A site has a v1.9 or v2.0 system which is required to be upgraded to v3.1. When upgrading, the ES is usually the first device to be upgraded, then depending on the number of AS onsite it may take a period of time to upgrade all the AS (especially if some of these servers are used in hospital theaters etc). For this reason EBO has an Upgrade Runtime Compatibility from v3.1 back to to v1.8, 1.9, 2.0 and 3.0, which means that an AS already in the system when the ES is upgraded to 3.1 will maintain connectivity and functionality while the upgrade takes place. Situation 2) A site has an external v1.9 or v2.0 AS whichis required to be added to an ES which is already running at v3.1. When trying to add in a new controller to a v3.1 ES, an error is produced stating that the version of the AS being added needs to be updated to before it can be added. Error Message when adding v2.0 AS to v3.0 ES Error message when adding 2.0 AS to 3.1 ES (better explanation) To summarize EBO does have Runtime Compatibility from v3.1 back to 1.8 as stated, but only for AS already in the system at the time of upgrade. Once upgraded to v3.1 the multi-version environment can be used to operate AS at v3.0 but adding AS running versions before 3.0 will generate a descriptive error.

Issue What BACnet services and BACnet object types are supported in the AS and ES? Product Line EcoStruxure Building Operation Environment StruxureWare Building Operation Automation Server StruxureWare Building Operation Enterprise Server BACnet IP BACnet MSTP Cause PIC statement for supported services and object types in StruxureWare Building Operation. Resolution Page 5 of the AS BACnet PIC shows the columns of the different types of BACnet devices. Whether it is a B-OWS or a B-BC etc… the x's in the columns show the required services for each particular device according to the BACnet Standard. The last green column in the PIC, show the Product Conformance (AS) and what services the AS supports. For instance COV is not a required service, but a optional one and is selected in the last column. Below are links to the AS and ES BACnet PIC. AS PIC statement link ES PIC statement link

Issue Receive error "Property value out of range" when creating a BACnet interface on the Enterprise Server   Following problems after upgrading SmartStruxure servers to 1.5: Attaching an Automation Server to or detaching it from an Enterprise Server will fail with “Property value out of range” error. Changes to the ~/System/Interface Manager/BACnet fail to be propagated lead-shadow functions through to the child servers. Automation Server controllers dropping offline following an upgrade to 1.5 (BACnet command priority related  also may see numerous "Changeset Rollback errors") Product Line StruxureWare Building Operation 1.1, 1.2, 1.4, 1.5 and above Environment Enterprise Server (ES) BACnet IP Interface Windows XP, Windows 7 and Windows Server 2008 R2 Cause Their may be various items that generate this error, checking the Enterprise Server (ES) system log in the Software Administrator may assist in pin pointing the error.  If you see an error that ends with ~/BACnet Interface/IP Network, then this error is generated when their is no valid IP Network.  For SmartStruxure 1.5 or above or planning to upgrade from 1.4 to 1.5 (and above)  This issue only occurs if a BACnet interface is used and the site has changed the BACnet "Default Priority Level" from the default value of 16, to 8 or a smaller numeric value in the Automation Server while running in V1.4. The "Property value out of range" message relates to the new Force priority level in 1.5 and the Default priority level in 1.4.1 being mismatched. Resolution The ES must be connected to an IP network. To resolve this error follow these steps: Close all Workstations (if running) Connect the Enterprise Server to a valid IP network (with a valid IP address). Stop and Restart the Enterprise Server service through the Software Administrator application. This should now allow the BACnet Interface to be created successfully For SmartStruxure 1.5 or above or planning to upgrade from 1.4 to 1.5 (and above) Please refer to TPA-SBO-14-0005.00 Before upgrading to 1.5 make sure the "Default Priority Level" within the Automation Server is set to 9 or higher.  If the system has been upgraded with the incorrect values, then: If the site uses single servers, or the ES/AS communication still operates correctly, then this can be corrected by changing the setting in both the AS and the ES to a value of 9 or higher.   If after upgrading a multi server configuration and the AS does not stay online, then a Hotfix can be used fix the problem using the following steps: Apply the hot fix #1.5.0.4301; available from Product Support Services Fix the multi-server (by detaching/re-attaching the servers) Correct the two properties (AS and ES). WARNING: It is essential for any BACnet system at 1.5 or later that the "Default Priority Level" must have a larger numeric value than the "Force Priority Level, otherwise some BACnet functions may not behave as expected. Note: This also applies even if the hot fix has been installed. The effects of not setting the Default above the Force Priority level are: If Force Priority Level is equal to the Default Priority Level: Changing the Value of a BACnet value or a BACnet output object will cause the Value to appear Forced. This applies to the BACnet objects in both SmartStruxure servers and those in 3rd party BACnet devices.   If Force Priority Level has a larger numeric value than the Default Priority Level: Changing the Value of objects mentioned above will cause the Priority Override icon overlay to be turned on next to the Value property in the WorkStation’s property grid.   

Issue Why doesn't BACnet/Ethernet work on a Niagara R2 UNC-600 or UNC-610 after upgrading to R2 version 529 (527 or higher)? ERROR: Cannot start Ethernet Packet Driver tridium.nre.DriverException: Cannot open \Device\RTL81391 [ethernet] Environment UNC-600 UNC-610 Niagara R2 version 527 or higher Cause New driver files were generated for BACnet/Ethernet to provide Vista compatibility. As a result, the driver files are unable to properly initialize the Ethernet packet driver on both the UNC-600 and UNC-610 platforms. The error can be viewed using the output window during the station start process. Resolution The solution involves the replacement of three files within the platform's R2 version 529 bin directory. File (UNC-6xx_BACnetEthernet.zip) contains the associated files and includes a readme.pdf with details on how to install on the UNC-600 and UNC-610 platforms.

Issue Can B-Link repeaters be used with EcoStruxure Building Operation? Product Line EcoStruxure Building Operation Environment EcoStruxure Building Operation site release 1.xxx and higher Cause Need to add repeater(s) for EcoStruxure Building Operation Resolution For communication using RS-485, the versions of B-Link BACnet MS/TP Repeaters repeaters shown below were tested and passed for EcoStruxure Building Operation use. Part Number Description B-LINK-AC BACnet MS/TP Repeater, 120/240VAC B-LINK-AC-OP BACnet MS/TP Repeater, 120/240VAC, open class no enclosure B-LINK-AC-S B-LINK, AC, SMK B-LINK-DC BACnet MS/TP Repeater, 24VDC B-LINK-DC-OP BACnet MS/TP Repeater, 24VDC, open class no enclosure B-LINK-DC-S B-LINK, DC, SMK B-LINK-F-AC B-LINK, AC, FIBER B-LINK-F-AC-S B-LINK, AC, FIBER, SMK B-LINK-F-DC B-LINK, DC, FIBER B-LINK-F-DC-S B-LINK, DC, FIBER, SMK   Note the supported cable diameter in microns: 62.5/125. The first number, 62.5, refers to the diameter of the fiber cable's core. The second number, 125, refers to the diameter of the outside of the fiber cable's cladding. For more information see: BACnet b-Link MS-TP Repeaters - Andover Continuum - Specification Sheet b-Link Series - Andover Continuum - Installation Sheet Additional information about Fiber diameters from The Fiber Optic Association Fiber cabling information for an Infilink i2210 and the B-link-F Series

Issue Experiencing issues with I/O modules that may include: Backplane failure causing modules to assume wrong module ID Input filtering problems on RTD modules Stability due to electrical noise Product Line EcoStruxure Building Operation Environment EcoStruxure Building Operation StruxureWare Building Operation Automation Server I/O Modules Cause The latest I/O module firmware version will correct known issues while also ensuring that the system is up to date and compliant. Resolution The latest I/O module firmware can be located on the Exchange by searching for I/O Module firmware. Each firmware download zip file will contain a ReadMe file that explains what was corrected in that version.  Refer to Upgrading SmartStruxure IO Module Firmware for the procedure to upgrade the I/O module firmware. 

Issue Support is required for the Automated Engineering Tool commonly known as AET Product Line EcoStruxure Building Operation, Automated Engineering Tool Environment AET Cause Further support is required for Automated Engineering Tool AET. Resolution For more information including videos, user guides, specification sheets, etc about the tool, please visit the Schneider Electric Exchange and EcoStruxure Building Management System WebHelp. For assistance or to report problems with the AET applications/programs, please post your questions on the Exchange Community.  In order to report functional problems with AET, please reference the support contact information found in Automated Engneering Tool - PA-00559 or email  aet.support@schneider-electric.com  

Issue Does not want to create his application from scratch if there are application templates available. Environment MNL series of standard LON controllers (MNL-50, 100, 110, 130, 150, 200, V1R, V2R, V3R series). Cause Wants to start with a pre-engineered application if one is available. Resolution Download WPT Micronet Applications Library v4.0.zip. Extract the files to the Solutions folder in WPT.

Issue Part numbers for SVEA Lighting modules. Environment SVEA LON Lighting Cause Part numbers no longer listed. Resolution The SVEA Brand of lighting control products became obsolete as of 1st January 2011. Please see Product Announcement PA-00139.

Issue Can replacement RR9 lighting relays still be purchased? Environment LCX89x Infinet Lighting controller range Cause Products not listed in the Catalogue or on the Extranet Resolution LCX890 range are still available, but only until December 31st 2013 and only with the RR9 relays (not RR7). Click here for the Product announcement. Originally the range was available with either General Electric RR7 (with no feedback) or RR9 relays (with feedback and LED indicators), now only the RR9 range are available until the end of the year. The LCX890 has 8 outputs with RR9 relays,   Part # 01-0008-036 The LCX891 has 16 outputs with RR9 relays, Part # 01-0008-039 The LCX892 has 24 outputs with RR9 relays, Part # 01-0008-042 The LCX898 has 48 outputs with RR9 relays, Part # 01-0008-083 Also individual RR9 replacement relays can be ordered part # 01-0100-300 A faulty RR7 relay could be replaced by a new RR9 relay even if the feedback and LED indicators are not required. These parts can be seen on the U.S iPortal website.  

Issue Are symbols allowed in the name of the NPR 2000? Environment I/NET site Cause Are symbols allowed in the name of the NPR 2000? Resolution No. Spaces, underscores and other symbols may not be used. (TCON209, 2-27)