Building Automation Knowledge Base

Warning Potential for Data Loss: The steps detailed in the resolution of this article may result in a loss of critical data if not performed properly. Before beginning these steps, make sure all important data is backed up in the event of data loss. If you are unsure or unfamiliar with any complex steps detailed in this article, please contact Product Support Services for assistance. Issue Process to restore MNB-1000 to factory default. Product Line TAC IA Series Environment MNB-1000 Cause If the IP address has been lost or unit has been misconfigured how can this be restored the factory default. *This step should only be taken if the data on the unit is not to be maintained * Resolution On the DIP switch settings, set all of the switches (1-8) to the ON position. Cycle power on the controller. Unit will boot up in reset mode (red flashing status light) Once completed the status light will be solid green. The unit is now in factory default mode The IP address will be 10.1.10.2 with a 255.255.255.0 subnet mask. BACnet IP will be disabled by default and BACnet Ethernet will be active.

Issue There are many issues that can happen at Cyberstation and some methods are needed to troubleshoot. Product Line Andover Continuum Environment Continuum Cyberstation Continuum webClient Server Windows XP Windows Vista Windows 7 Windows Server 2003 Windows Server 2008 Cause There are a number of steps and tools that can be used to troubleshoot Cyberstation Resolution This subject encompasses software and hardware. It isn't a comprehensive list but should offer some methods and tools to help troubleshoot Cyberstation or webClient. Typically errors that are Cyberstation or webClient related will display some sort of an error message on the screen which can be used to diagnose the problem. Isolated or System Wide - Is the issue happening on 1 or multiple Workstations? If so, it could be a system wide issue, but if it's just one workstation then it is isolated to this PC and could be an install, Windows OS, hotfix or hardware issue. Continuum Compatibility Matrix - A number of issues can happen if Continuum Service Packs or hotfixes or Windows Operating System (including Service Packs), Microsoft SQL Server, Internet Browser version and the version of Continuum or webClient do not match the matrix. See document Software and Firmware Compatibility Matrix Version 2.03 Cyberstation Error - Is there an error message that is being displayed. A list of some Cyberstation specific errors can be found by pressing F1 with Cyberstation open, select index, type in Error, select error messages, Cyberstation How do you locate error messages in Cyberstation? Windows Error - Is there an error showing in the Windows event viewer? This step can be very useful when troubleshooting Cyberstation problems from issues installing Cyberstation or SQL to problems happening because of a Windows Operating System issue. Typically there are errors, event ids, and details that occur at the time of an issue that can be used to search the web for a solution. These can also be sent into support for some help analyzing the issue. Viewing, Saving, Sharing Windows Event Logs for Troubleshooting Purposes Windows Service Pack or hotfixes- Were any Windows Service Packs or hotfixes recently applied to this PC that could be affecting this installation? To display all the hotfixes on a PC, see the following MS article: Windows: How to List All of the Windows and Software Updates Applied to a Computer Installed Software- Since the issue started happening has any additional software been installed on the PC. Take a look in Start> Settings> Control Panel> Add/Remove programs(XP) or Programs and Feature (Windows 10) and see what may have been recently installed. Antivirus / Malware -  On some occasions, we have seen Cyberstations or webClient PCs affected by viruses or malware. If an issue is specifically related to one PC and particularly if that PC is exposed to the internet, but doesn't have any Anti-Virus software installed, it could be infected. Updating Anti-Virus definitions and Malware/Spyware programs and running scans is recommended to clean up the PC. Hardware Issues - PCs will break over time from wear and power bumps, etc. Memory, NIC cards and Hard Drives are typically what goes first. *Memory - Many PC manufacturers supply memory diagnostic features in the system bios to detect if a RAM module is bad. This will often show in a certain spot every time in a certain program, not necessarily Cyberstation and can actually indicate that is can't access a memory reference. *Hard drives - drives can crash or certain files can become damaged. Checkdsk and the Windows OS attempts to keep the drive clean, but sometimes reformatting the Hard Drive and reinstalling the Windows OS will be required to correct the issue. If it's a physical issue with this drive then the problem could come back and a new hard drive may be needed. *NIC (Network Interface Cards) - can cause connection issues and affect system performance. Not all NIC cards are created equal and at times integrated NICs(built into the motherboard) can be less robust than a third party NIC card. See the following for extensive troubleshooting advice, but often swapping the card is easier. Advanced network adapter troubleshooting for Windows workstations *Graphics Displays - Some issue are more related to Pinpoint or Video. Check the graphics display and see if the most up to date video driver has been installed. Run any diagnostic that may be supplied by the video card manufacturer or swap out the card. Windows Device Manager - In Windows device manager you may see a black exclamation point on a yellow field which indicates the device is in a problem state. There can be many reasons this can happen and is beyond the scope of this article. See the following MS article for more information. Error codes in Device Manager in Windows System Info and Belarc Advisor - These tools can be used to see what hardware and software are installed on the PC. System info is installed with Windows. Description of Microsoft System Information (Msinfo32.exe) Tool This can be sent into Product Support as a .nfo file and can be brought up with details. This information can be difficult to work with. Belarc Advisor - This is a free tool that can be installed on a PC and will display the information in a very readable browser format. This tool will often find things that may have shown in System Info but was difficult to find. Belarc Advisor Restore Point - Windows XP, Vista and Windows 7 all have the ability to restore the system to a previous place in time by using Windows Restore Point. This is a Windows Operating System function and has some risks associated with it, but can be very useful to get back to especially when the issue is happening on a Stand Alone setup. What is System Restore? If the restore point doesn't work then a reinstall of Cyberstation or the Windows OS could correct the issue. Lastly, a reformat of the hard drive and a complete reinstall of the Windows Operating System and then reinstall Cyberstation or webClient may be needed.

Issue Capability to import a BACnet device objects via an EDE file? Product Line EcoStruxure Building Operation Environment StruxureWare Building Operation site with BACnet Cause Questioning if StruxureWare Building Operation has the capacity to import a BACnet device objects via an EDE file? Resolution We do not support importing from EDE files. We would like to have a good solution for pre-engineering 3rd-party BACnet devices. This is a problem that R&D has looked at on several occasions. The Engineering Data Exchange (EDE) concept is one way to address this issue. Although the BACnet community is in favor of solving this problem, they are not aligned on using EDE files as the solution. The EDE file concept was introduced through the BACnet Interest Group Europe (BIG-EU) by Siemens as an attempt to mimic LonWorks functionality. For worldwide adoption it must become an official extension to the BACnet standard as an approved addendum via the ASHRAE BACnet committee SSPC 135. The BACnet committee has reviewed the EDE file concept and feels that the solution does not fit in with the BACnet roadmap and is not technically ideal. The EDE file is a CSV format and the BACnet committee favors a more modern standard that has extensive self-describing features such as with XML or JSON. For example, BACnet Electronic PICS (EPICS) and BACnet Web Services is XML based and their is an active XML Working Group within the BACnet committee. We understand the BIG-EU is looking to ASHRAE for guidance on this issue and would like to be aligned with the standard going forward. There is a deeper issue beyond adoption by ASHRAE and the technology choice. The reliability of the EDE file cannot be guaranteed. The BACnet Device and Network IDs and objects contained within must be set exactly in the EDE file or configured offline to match the actual device in the field. If these BACnet addresses and objects don't match you will most likely end up with major problems when the database is brought online. Packet captures will reveal duplicate messages and excessive network traffic and references will fail to work. EDE Files for application specific (ASC) devices are likely to have a longer shelf life then EDE files for free-programmable building controllers. However, if an ASC has it's firmware updated, even an ASC EDE file will become outdated and useless. It is rumored that EDE files have been used successfully in the field but want to point out that this is not a fail-safe method nor is it tested and supported. As we continue to participate in the ASHRAE BACnet working groups, we will activity engage ourselves in the pre-engineering solution discussions. Our hope is that a universally accepted solution that can address most of the concerns can become an approved addendum to the ASHRAE BACnet standard.  It turns out that the ASHRAE BACnet committee is further along than reported above. ASHRAE 135-2008 Addendum which added the XML file formats to the standard addresses this application: http://www.bacnet.org/Addenda/Add-135-2008t.pdf Looking at the rational section of this addendum you will see a list of the intended applications: This syntax is intended to be the core data representation for the following use cases: An electronic version of a PICS document, consumable by workstations and other tools, to describe the capabilities of a device. An XML version of an EPICS, defining not only the capabilities of the device, but also including the complete test database and other test-oriented data. An "as built" description of a deployed device, distributed either as a separate file or as a File Object resident in the device itself. Descriptions of proprietary objects and properties and datatypes (in any of the above three uses). These descriptions may be minimalistic, providing basic data sharing capabilities, or extremely rich, providing complete descriptions of the meaning and usage of the data to enable a comprehensive user interface, including the capability of providing such descriptions in multiple human languages. An export format for tools and workstations to export or publish their knowledge of the arrangement and configuration of a device or a complete system of devices and networks. Web services that exchange complex or constructed data With an official ASHRAE BACnet solution it is just a matter of determining which method to go with. Despite the format, it is possible to have a utility application that can automatically generate an export file. It would even be possible to convert an EDE file to XML. Albeit, I believe the EDE file would be less descriptive then an XML file generated from the actual device. It may be better to natively import via XML. We would then either get a BACnet XML file from the vendor or have a small external utility gather from the live device or convert an EDE file.

Issue Wire colour coding for the SPP110 Product Line Field Devices Environment SPP110: 004702020 004702040 004702060 004702080 004702100 004702120 004702140 Cause Wire colour coding SPP110 required. Resolution Due to supply problems, between week 23 to week 32, there was a change to the sensor's cable and the wire colours. This was implemented by the manufacturer without Schneider Electric's knowledge. So no product announcement was produced.                      Original       Week 23 to Week 32 No. Function Colour                Colour 1     Y            Brown                Green 2    GO         Black                  White 3    G            Red                    Brown   Standard                                                                                           Week 23 to Week 32   Refer to the SPP110 Pressure Transmitter Wet Media Specification Sheet for more information.   The SPP110 installation sheet showing the standard wire colouring is available here The SPP110 installation sheet showing the wire colouring is attached.

Issue Program IDs do not match. There is an incorrect or out-of-date program version. (Subsystem: NS, #38) Product Line TAC Vista Environment LonMaker 3.X NS Error codes are not specific to any one LON environment, the display of the error may vary, but the steps to resolve should be the same. Cause A Program ID is a unique identifier assigned to each XIF (or device template) in an LNS database. Controllers with different XIFs cannot share the same Program ID. When a device is created in an LNS database, its Program ID is extracted from the XIF and stored in the database. When a controller is downloaded, the Program ID is transferred and stored in the controller. If the Program ID that resides in the controller differs from the one stored in the LNS management tool, the commission command will fail due to the Program ID mismatch. Resolution The appropriate resolution to the NS, #38 error depends on which controller is failing to commission. Select from the categories below which best describes the offending controller.  Xenta Programmables (follow steps below) Xenta 28X, 30X, 401(:B) Download the controller through the Vista System Plug-in before attempting to commission. If the error remains after a download, then the download did not go through, despite all indications that it did. Connect to the RS-232 serial port of the controller and attempt to download the Menta file directly. This will often bring to light parsing errors that are not detected by the System Plug-in. Find and correct the errors to allow the file to download properly. See Menta Parser Errors for more information on parser errors. The controller should then commission successfully. --- If the error persists, continue ---   Open the Menta file of the controller that will not commission. Under Options > Device Specification, uncheck the box for "XIF-Header generated according to LonMaker standard." (You may have to temporarily assign a System Version to activate this checkbox.) LonMark standard headings only use 255 combinations of IDs. It may be that two controllers just happened to be assigned the same Program ID. After unchecking this box, go to Options > Simulate, Commands > Generate to regenerate a new Program ID without using the LonMark standard header which opens up many more Program ID combinations and lessens the already low probability of two being the same. Download the new Menta file with the new XIF and new Program ID into the controller. It should now commission successfully.   Xenta 5/7/9XX Xenta 511, 527, 701, 711, 721, 731, 913 The XIF in the LNS database must be updated. See How to update a modified Xenta 5/7/9xx XIF file in LonMaker for detailed instructions.   ASCs/LON Devices (choose an option below) Xenta 100 series, third-party devices Replace the device using the correct XIF obtained from the manufacturers website. Replace the device using the correct XIF obtained from https://www.lonmark.org/. Replace the device with a generic device. Commission with the option of getting the XIF from the device.   Xenta 400 Series I/O Module (choose an option below) Xenta 42X(A), 45X(A), 47X, 49X Be sure the correct module is defined in Menta if adding I/O modules automatically. If adding I/O modules manually, be sure to use the correct stencil on the LonMaker drawing. You will get this error if you try to commission a 451A module with a 451 stencil.

Issue The functionality of the different tools and/or software does not operate as expected. Issues can appear related to controller functionality or possibly issues with how the standard programs work.  Product Line EcoStruxure Building Operation Environment Automated Engineering Tool (AET) Project Configuration Tool (PCT) EcoStruxure Building Operation (EBO) Cause When the latest versions of software and firmware are not being used, previously identified issues can cause problems with downloads or the operation of controllers. In other situations, it is possible that the proper steps or tools are not being used correctly. This could require further instruction and information.  Resolution In most situations, the troubleshooting steps below will address a majority of issues encountered while working with the AET and the standard applications. EBO software and SmartX firmware being used should be at the latest version Between updates and fixes to the software/firmware, you should be using the latest versions found on the Exchange.  AET software should be up to date Between updates and fixes, make sure you are using the latest version of the AET software which can be found on the Exchange.  AET templates should be up to date You can reference the AET Quick Help - Downloading AET Templates video or the SmartVAV: Software Engineering Process document for further direction.  Understanding the proper way to use the Automated Engineering Tool There exist a number of AET Quick Help Videos available on the Community to help with AET user skills. If there are any topics not covered in a video that you are searching for, be sure to leave a post with the new video idea.

Issue MNB Controller firmware upgrade failed, which resulted in the device showing a blinking-red status LED. Product Line TAC IA Series Environment I/A Series MNB Controllers (ASC) (All firmware revisions) Note: This does not apply to the MNB-1000 Cause A blinking-red status LED means the MNB controller is in Boot Loader mode and it cannot reboot. It is now a "slave" unit, listening to traffic, not initiating communication. Resolution Using the WorkPlace Commissioning Tool, click on the File pull-down menu and select "Add MS/TP Slave". If asked to select from IP, Ethernet or MS/TP, select MS/TP. (Note: It's a good idea to have the controller isolated from the trunk, so the firmware upgrade process runs less risk of being interrupted.) At the prompt for the address, enter the address set on the controller DIP switch. The controller should get added to the list. If it is already in the list, a message will indicate that there's a duplicate address. Answer prompts in such a manner to get the controller added to the list. The 'slave' controller may show up with a blank name. Do the firmware upgrade again. This procedure works 80% of the time. If the upgrade fails, put the controller into Dedicated Boot Loader Mode. Take the controller off the MSTP trunk, set the DIP switch address to 254, cycle power, and try another firmware upgrade (keep it addressed as 254). Following a successful firmware upgrade, set the DIP switch back to the correct controller address and cycle power to the controller.

Issue Device Administrator is not able to load new database version into AS-P. Error message “New database failed” Product Line EcoStruxure Building Operation Environment Building Operation Workstation Building Operation Automation Server Cause The new McAfee firewall policy where Local the firewall is blocking ICMP6 to the PC. The device needs to be able to "call back" to the PC. If that doesn't happen, the upgrade will not continue and stop at exactly 70%. This is seen in 3.x, EBO 2.0 does not exhibit this issue The device may be defective due to software or hardware error. Resolution   The McAfee firewall issue can be resolved by:  Temporarily disabling the local firewall Trying another PC since McAfee policy or some restriction might have caused installing 3.2 to fail. Another possible solution for this issue which we have seen working is to first install version 3.1 using DFU mode and create a new database and then upgrade to version 3.2 using IP connection.   How to cross-testing and identify if the device is defective? Use the same PC and Device Administrator to install a new DB on a different AS-Ps.  If the same PC can install a new DB on a different AS-P then the issue is not on the PC. Use another PC with the same version of Device Administrator to install a new DB on the suspecting device. If it fails to install a new DB then RMA is needed. Remember to DFU the device before installing a new DB.

Issue Communications failure due to transaction timeout when reloading b3 device. b3's version number as seen from the Infinity side reads 0.0000 Product Line Andover Continuum Environment CyberStation bCX4040 b3 Cause A b3 BACnet controller is found to exist in the BACnet folder under an MSTP Network which is different from the Network specified in the bCX's comm2 Port. Resolution Delete the MSTP network under the BACnet folder and perform a 'Find new BACnet devices'.  A new MSTP network should be created with the right network ID.

Issue Certain Xenta controllers and I/O modules can accept 1.8k thermistor temperature inputs. Product Line TAC Vista Environment Xenta 121-FC Xenta 200 Xenta 300 Xenta 420A Xenta 450A Cause What is the temperature vs resistance curve of the 1.8k thermistors for Xenta 300? Resolution All Xenta controllers and I/O modules, except the Xenta 102-AX use the same 1.8k thermistor (type 1.8KA1). The following table shows details the Temperature vs. Resistance characteristics for this thermistor. Temp (°C) Minimum kΩ Nominal kΩ Maximum kΩ -50.0   60.87  63.88  67.03  -45.0   45.41  47.5   49.68  -40.0   34.23  35.68  37.2   -35.0   26.04  27.07  28.13  -30.0   19.99  20.72  21.47  -25.0   15.48  16.0   16.54  -20.0   12.09  12.46  12.84  -15.0   9.512 9.779 10.05  -10.0   7.541 7.733 7.929 -5.0   6.021 6.16  6.301 0.0   4.84  4.94  5.042 5.0   3.916 3.988 4.061 10.0   3.189 3.24  3.293 15.0   2.612 2.649 2.686 20.0   2.151 2.177 2.209 25.0   1.782 1.8   1.818 30.0   1.478 1.496 1.514 35.0   1.233 1.25  1.267 40.0   1.033 1.049 1.065 45.0   0.8698 0.8848 0.9001 50.0   0.7357 0.7497 0.7639 55.0   0.6251 0.638 0.6511 60.0   0.5334 0.5453 0.5573 65.0   0.457 0.4679 0.479 70.0   0.3931 0.4031 0.4132 75.0   0.3395 0.3485 0.3578 80.0   0.2942 0.3025 0.311 85.0   0.2559 0.2634 0.2712 90.0   0.2233 0.2302 0.2373 95.0   0.1956 0.2019 0.2083 100.0   0.1718 0.1775 0.1835 105.0   0.1514 0.1566 0.1621 110.0   0.1338 0.1386 0.1436 115.0   0.1186 0.123 0.1276 120.0   0.1054 0.1095 0.1136 125.0   0.094 0.0977 0.1015 130.0   0.084 0.0874 0.0909 135.0   0.0753 0.0784 0.0816 140.0   0.0676 0.0705 0.0735 145.0   0.0609 0.0635 0.0663 150.0   0.0549 0.0574 0.0599

Issue Troubleshooting steps for the Infinet and MSTP bus. Product Line Andover Continuum, EcoStruxure Building Operation Environment Continuum SmartStruxure RS-485 Infinet BACnet MSTP Cause Methods are needed to troubleshoot the Infinet and MSTP bus Resolution This is not a comprehensive list of all methods for troubleshooting, but a starting point. The Infinit-mstp troubleshooting document is available here. NOTE If BACnet MSTP devices do not support COV subscriptions, then care must be taken when reading values (eg EBO trends or alarms) as excessive traffic can be created that overwhelms the communication bus. For example, if 30 non-COV BACnet devices have EBO alarms (or EBO change of value trends) bound to 4 objects in each controller, this will create 240 packets (reads/replies) that will be attempted every "Minimum polling Interval". This is likely to fill the MSTP bus bandwidth  

Issue Where can I find the current documentation for the WorkPlace Tech Tool software, MNL LON controllers, MNB BACnet controllers and their associated specification data sheets? Product Line TAC IA Series Environment WorkPlace Tech Tool software I/A Series MNB BACnet family of controllers I/A Series MNL LON family of controllers Cause There is no single online source for the all the current documentation for the WorkPlace Tech Tool software, MNL LON controllers, MNB BACnet controllers and their associated specification data sheets. Resolution All documentation related to the WorkPlace Tech Tool (WPT, WPCT & WPFB) and related controller documents are installed to your computer when you install the WorkPlace Tech Tool software. At the time of release, the current version of each software manual, hardware installation manual (LON & BACnet), specification data sheet (LON, BACnet & Software) and the software release notes document is built into the software installation program. These documents are all accessible under the \WorkPlace Tech\Help folder on any computer where the WorkPlace Tech Tool software is installed. All documentation can be displayed from the list displayed by the WorkPlace Tech Help menu. This was done to insure that all WorkPlace Tech Tool users would have access to the version of all documents related to that specific release of the software. Since these documents are included in the installation package for any version of the WorkPlace Tech Tool software, you can download the latest WorkPlace Tech Tool installation file from The Exchange Download Center to get the complete set of documents. These documents are also available individually from the 'Publication Zone', accessible from the 'Links' menu on iPortal (https://iportal2.schneider-electric.com).

Issue What are the IO wiring requirements for the IO Modules? Product Line EcoStruxure Building Operation Environment Analogue, Digital, Input, Output Cables UI-16, DI-16, AO-8-x, AO-8-V-x UI-8, DO b3 Inputs Cause The existing documentation does not specify the exact cable types to be used. Resolution Different types of sensors can be used that come from different legacy systems, so cable types specified for the legacy systems will be appropriate for the same sensor type being connected to an Automation Server I/O module. If you are using Xenta sensors with the 1.8K Ohm thermistors you should use the wiring rules as per the Xenta documentation. Of if you use Continuum 10K Ohm sensors, use the Continuum IO wiring rules etc. Some suitable cables for most Analogue and Digital input, also analogue output applications are: 18 AWG (16 x 30) 0.823 mm2 - single pair screened e.g. Belden 8760 22 AWG (7 x 30) 0.325mm2 - single pair screened e.g. Belden 8761 The maximum distances that these cable can be run are dependent on the input requirements, for Temperature inputs this will depend on the temperature range and accuracy required. For examples of of these cable distances see links below: Continuum 10K Ohm sensors (also applicable for b3 controller inputs). Xenta 1.8K Ohm sensors For digital outputs cable should be used with appropriate size (current rating) to the loads being switched. It is recommended to use screened cables and also ensure correct connections for analogue inputs as detailed in How to wire an Analog input to an IO Module.

Issue Alarm code, configuration code passwords for DC1100 and DC1400 Product Line Field Devices Environment DC1100 controller DC1400 controller Cause Configuration Resolution Passwords are: 0112 for configuration mode 0402 for fast run mode

Warning Potential for Data Loss: The steps detailed in the resolution of this article may result in a loss of critical data if not performed properly. Before beginning these steps, make sure all important data is backed up in the event of data loss. If you are unsure or unfamiliar with any complex steps detailed in this article, please contact Product Support for assistance. Issue PCT client can't start properly with "Hardware virtualization is not enabled" error. Product Line EcoStruxure Building Operation Environment Building Operation Project Configuration Tool (PCT) (All Versions) Cause Hardware Virtualization is Disabled or not available for PCT Resolution  Install "Intel® Processor Identification Utility" then verify the status of "Intel® Virtualization Technology" from the Utility. Using the table below, you can see if your processor supports Intel® Virtualization(provided by Intel).  The above information can also be found on Intel® Virtualization Technology web page If Virtualization is disabled in BIOS then enable it from BIOS else identify other software utilizing the Virtualization and stop the application.  Use Win key or press the Windows Start button Type: cmd Select Run as Administrator  Verify command prompt window title bar is Administrator: Command Prompt Type: shutdown /r /fw/ /f  Press enter and the computer will shut down immediately forcing all applications to close (/f) and restart (/r) into firmware interface (/fw)   If the issue persists, the following article may provide the answer Knowledge Base article - PCT error Hardware-virtualization is not enabled-Please-enable.

Issue Replace Invensys Actuator Model MA5-419-500-0-3 Environment Damper Control Actuator site Cause Replacement Specifications for Obsolete Invensys MA5-419-500 which is a Two Position Damper Actuator, SR, 240V, 50 Hz, 60 lb-in, w/SPDT Aux. Switch Resolution The closest replacement would be the MD5B-24(-S)/-230(-S) On/Off or 3-point 24 V AC/230 V AC Damper Actuator 5 Nm (45 in-lb). Note: This is a Rockford, Illinois offering, which we would not normally have offered this in Europe in the past. There is a range of Non-Spring Return Damper Actuators detailed in Pages 54 and 55 of the below Schneider Electric Catalogue. Similarly there is a range of Spring Return Damper Actuators detailed in Pages 56 through 58 of the below Schneider Electric Catalogue. Damper Actuator Accessories are shown on Page 59 of the below Schneider Electric Catalogue. Schneider Electric HVAC Valve and Actuator Catalogue  

Issue Serial connection to I/A Series R2 UNC VxWorks Target Shell using Windows HyperTerminal Product Line TAC IA Series Environment I/A Series R2 Universal Network Controllers: UNC-410-1 UNC-410-1-N UNC-520-2 UNC-520-2-N Cause There maybe a need to access the UNC via its serial port if the IP address of the UNC is unknown or for troubleshooting purposes when the UNC's Ethernet port is not functioning. Resolution Hardware required for connection to UNC's RS-232 port: 8-conductor flat silver satin stranded cable with standard male (plug) RJ-45 connectors RJ-45 to DB-9 adapter (part number: UNCC-405) or a socket-to-plug type RJ-45 to DB-25 adapter (part number: UNCC-430) A functioning COM port on a computer A 2-pin jumper for connection to the UNC's "Mode" connector Refer to the Installations Instructions for UNC-520 (page 15) for details on the cable and adapter (applies for both UNC-410 and UNC-520). Pinout configuration for a RJ-45 to DB-9 Null Modem Adapter (part number UNCC-405) also refers to these pin outs. Connection to UNC's VxWorks Target Shell using Windows HyperTerminal (for operating systems without HyperTerminal, please refer to Hyperterminal on Microsoft Windows Operating Systems😞 Connect the cable and adapter between the UNC's RS-232 port and the RS-232 COM port used on the computer. Start HyperTerminal (Programs > Accessories > Communications > HyperTerminal). In the 'Connection Description' dialog, type a name for this session. For example, 'Connection to UNC'. Click OK. In the 'Connect to' dialog, use the 'Connect using' drop-down list to select the COM port used on the computer. Click OK. In the Com(n) Properties dialog, choose the following settings: Bits per second: 9600 Data bits: 8 Parity: None Stop bits: 1 Flow control: Hardware Click OK. On the UNC circuit board, locate the 4-pin Mode connector and put a 2-pin jumper on the 2 outer pins. Refer to page 17 UNC-520 Installation Instructions for position of the Mode connector (top right corner). With the HyperTerminal session active, remove power from the UNC, let it cycle down, then reapply power. After some number of seconds, text should appear in the HyperTerminal window similar to: Press any key to stop auto-boot... To enter commands to the UNC, press any key to break out of the boot sequence. A prompt similar to the following is shown: [VxWorks Boot]: To determine the IP address / subnet mask of the UNC, do not break the auto-boot sequence as described in step 7. Allow the UNC to finish booting. When the controller stops displaying new messages, press ENTER to reach the command prompt. The prompt is similar to the following: -> Using the scroll bars on the HyperTerminal window, scroll up until the section that begins with the line 'Press any key to stop auto-boot...'. The IP address of the UNC is listed on the line that begins 'inet on ethernet (e)' The IP address is listed (in dotted decimal), followed by a colon, and then the subnet mask (in hexadecimal). Disconnect from the UNC when complete. Press the 'Disconnect' button on the HyperTerminal toolbar. Exit from the HyperTerminal application, selecting to Save if planning to reuse this HyperTerminal setup for future connection to an UNC. Remove the 2-pin jumper from the Mode connector of the UNC. Reboot the UNC by removing the power connector, waiting for all lights to extinguish, and plugging the power connector back in. * If troubleshooting the UNC, send the HyperTerminal start up messages to Product Support for analysis.

Issue Documentation for KLR-E AC Room Controllers / Thermostats Environment AC Room Controllers Thermostats Cause Documentation for KLR-E type thermostats. Resolution KLR-E Thermostats are manufactured by EBERLE (Invensys) and available from Schneider Electric in Europe. Click here to download KLR-E documentation in French Click here to download KLR-E documentation in English/German

Issue Getting javax.baja.xml.XException: Error parsing value error message when attempting to add a new driver network to the I/A Series G3 station's Drivers container. Drag and Drop - drag network container from palette and drop onto the Drivers container Copy and Paste - copy network container from palette and paste into the Drivers container Drivers Manager (New selection) - wizard to add new driver Error details displayed:  com.tridium.fox.session.ServerException: javax.baja.xml.XException: Error parsing value [38:4] Environment Enterprise Network Server, ENS, ENC, JACE Cause The module associated with the driver has not been installed in the local modules folder or remote station. Resolution Enterprise Network Server Stop Workbench Copy the missing module directly into ~\modules directory for the version of I/A Series G3 being used. Restart Workbench ENC or JACE Open the platform for the ENC/JACE Install the module using the Software Manager. A station reboot may be required.

Issue How to discover MNL Lon devices or other Lon devices in an SmartStruxure Automation Server. Product Line EcoStruxure Building Operation Environment Building Operation Workstation Building Operation Automation Server Cause Use the below instructions when you need to find all Lon devices on a Lon network. Resolution To discover a LonWorks device In WorkStation, in the System Tree pane, select the server that is connected to the device you want to discover. Click the Device Discovery view. In the Select device type box, select LonWorks. Select the Devices folder. Right click on the Devices folder and take "Scan network for devices" In the Device Discovery view, ensure that the LonWorks device is displayed in the Devices folder. This may take up to 5 seconds. Drag the discovered device to the System Tree pane: Drag to an existing device to associate it with the discovered physical device. Drag to the LonWorks network to create the device.   NOTE: You cannot drag a standard MNL LonWorks device to the System Tree pane if the discovered device is in an unconfigured state For more information, refer to the Creating and Configuring a LonWorks Network with MNL LonWorks Devices [102423].pdf document