Building Automation Knowledge Base

Issue When the EWS is installed on the same machine using the service then all packets will be going to the localhost and will not hit the NIC so will not be captured in a Wireshark packet capture. Product Line EcoStruxure Building Operation, EcoStruxure Security Expert Environment Security Expert Building Operation Enterprise Server Building Operation Automation Servers (AS-P, AS-B) Cause Packets sent between services on the same machine (like SOAP and EWS) do not hit the NIC and therefore cannot be captured with the default configuration of Wireshark using the WinPcap packet sniffing library.  Resolution Replace WinPcap with Npcap to emulate a loopback NIC for packet capture. Go to https://nmap.org/npcap/ for details on the library. Download the library installer from https://nmap.org/npcap/#download Uninstall WinPcap. Install Npcap. Npcap will then create an adapter named Npcap Loopback Adapter. In Wireshark choose this adapter to capture, loopback traffic will be the seen the same way as other non-loopback adapters. This can be tested by typing in commands like "ping 127.0.0.1" (IPv4)  or "ping ::1" (IPv6).

Issue As a part of the drive to improve information regarding our products, this document has been created to assist and clarify methods of connecting Touchscreens to newer and older series MicroNet controllers, and the controllers on the sub LAN under the Touchscreen unit. Product Line Satchwell MicroNet Touchscreen Environment Touchscreen wiring Cause Connecting MicroNet Touchscreen to microNet controllers. Resolution Updated June 2019 The MicroNet 50 series range MN350, 450, 550, 650 LCD and Touchscreen have been withdrawn from sale. The IAC 420, 600 and Touchscreen have now also been withdrawn from sale. No direct replacement is offered. Further information on these changes can be found in PA-00495 - Notice of Withdrawal - Satchwell Sigma and PA-00528 - End of Commercialization - Satchwell Sigma. ---------------------------------------------------------------------------------------------------------------------------------------------------------- Remote Mounted Touchscreen (NCP) Connected to MN550/MN650 Controllers. Fig.1  Fig.2 If the system has a front-end, or local interrogation is required, connection to the Touchscreen and its sub LAN should be done via LAN A of the Touchscreen. The address of the Touchscreen should start at 1/2. (See fig 3)  Fig. 3                                                                             Fig. 4 The sub LAN number, under the Touchscreen, is dictated by the address of the Touchscreen. We do not recommend the use of address 1 for Touchscreens, as this creates a sub LAN 1 under main LAN 1. The Touchscreen is supplied with 2 jumpers across the top two auxiliary connector pins. (See fig. 4) A visual check should be carried out to insure the jumpers, are fitted to the auxiliary pins and they have a good physical connection. Connection to controllers on the sub LAN is done via LAN B of the Touchscreen to LAN B of the other controllers on the sub LAN. If the option of an isolated LAN for the 50 series controllers on the sub LAN is to be utilised, then a separate 24 Volt power supply should be used to supply the Touchscreen. Touchscreen (NCP) Directly Mounted on MN550/MN650 Controllers.   Fig.5  Fig.6 If the system has a front-end, or local interrogation is required, connection to the Touchscreen should be done through LAN A of the controller the Touchscreen is mounted on. The address of the Touchscreen should start at 1/2. (See fig 7)  Fig. 7                                                                           Fig. 8 The sub LAN number, under the Touchscreen, is dictated by the address of the Touchscreen. We do not recommend the use of address 1 for Touchscreens, as this creates a sub LAN 1 under main LAN 1. The Touchscreen is supplied with 2 jumpers across the top two auxiliary connector pins. (See fig. 😎 A visual check should be carried out to insure the jumpers, are fitted to the two auxiliary pins and they have a good physical connection. The MN50-TS-NCP specification of the Touchscreen differs from other variants and only has these 2 pairs of pins. This is to allow the Touchscreen to mount directly onto the controller; the other auxiliary pins are not fitted when manufactured. The controller that the Touchscreen is to be mounted on must not have the jumpers fitted to the auxiliary pins. These are fitted at the factory, and should be removed. Connection to other controllers on the sub LAN should be done via LAN B of the base controller to LAN A of the other controllers on the sub LAN.  If the option of an isolated sub LAN, using 50 series controllers, needs to be fully utilised, the Touchscreen would need to be mounted remotely with a separate 24 Volt power supply. If the Touchscreen must be mounted directly onto a controller, that controller and the Touchscreen would not be fully isolated, but provided the Touchscreen /controller has a separate supply to the rest of the sub LAN, other controls on that sub LAN could be isolated. Remote Mounted Touchscreen (NCP) Connected to MN500/MN620 Controllers. Fig.9 Fig.10 If the system has a front-end, or local interrogation is required, connection to the Touchscreen and its sub LAN should be done via LAN A of the Touchscreen. The address of the Touchscreen should start at 1/2. (See fig 11) Fig. 11                                                                                 Fig. 12 The sub LAN number, under the Touchscreen, is dictated by the address of the Touchscreen. We do not recommend the use of address 1 for Touchscreens, as this creates a sub LAN 1 under main LAN 1. The Touchscreen is supplied with 2 jumpers across the top two auxiliary connector pins. (See fig. 12) A visual check should be carried out to insure the jumpers, are fitted to the auxiliary pins and they have a good physical connection. The controller on the sub LAN needs to have the jumpers fitted to the auxiliary pins. Connection to controllers on the sub LAN is done via LAN B of the Touchscreen to LAN B of the other controllers on the sub LAN. Touchscreen (NCP) Directly Mounted on MN500/MN620 Controllers.    Fig.13 Fig.14 If the system has a front-end, or local interrogation is required, connection to the Touchscreen should be done through LAN A of the controller the Touchscreen is mounted on. The address of the Touchscreen should start at 1/2. (See fig 15)  Fig. 15                                                                           Fig. 16  The sub LAN number, under the Touchscreen, is dictated by the address of the Touchscreen. We do not recommend the use of address 1 for Touchscreens, as this creates a sub LAN 1 under main LAN 1. The Touchscreen is supplied with 2 jumpers across the top two auxiliary connector pins. (See fig. 16) A visual check should be carried out to insure the jumpers, on the Touchscreen, are fitted to the auxiliary pins and they have a good physical connection. The controller that the Touchscreen is to be mounted on must not have the jumpers fitted to the auxiliary pins. Connection to controllers on the sub LAN should be done via LAN B of the base controller to LAN B of the other controllers. Caution to be taken when replacing an MN500 or MN620 controller if a Touchscreen is directly mounted on the unit. When replacing an MN500 or an MN 620 controller that has a Touchscreen directly mounted with a 50 series MN550 or an MN650 controller. The Touchscreen auxiliary pins 6 and 7 foul components on the controllers back plate, and will need to be cut. Pins 6 and 7 are identified in figure 17 below, will need to be cut close to the isolation strip A Once this modification has been carried out to the Touchscreen, the unit will no longer be suitable to run ARCnet communications. Fig. 17 An option would be to replace the Touchscreen at the same time as replacing the controller, with specification number MN50-TS-NCP. The MN50-TS-NCP specification of the Touchscreen has been modified, in production, starting Q2 2007, to allow direct mounting onto the MN500, MN 620, MN 550 and MN 650 controllers. Note: The 50 series controllers can be on the same LAN as the old 100 series of controllers. The LAN connections previously described, for the particular controller should be observed. Further information regarding these controller can be found in the product data sheets. See MicroNet 100 series controller MLi's and Data sheets See MicroNet 50 series controller MLi's and Data sheets

Issue Can a MNB-1000 be configured to get an IP address via DHCP? Product Line TAC IA Series Environment MNB-1000 Cause End user does not want to use fixed IP addresses on their network. Resolution The MNB-1000 does not support the use of DHCP for setting the IP address.

Issue Importing an existing Xbuilder project into a Vista Database. Environment XBuilder Vista Workstation Cause Site moving from Xenta Server only to Vista Server Front End Resolution Open your existing Xbuilder Project Select Project>Settings check the box labeled "Send Project backup file to target device" Click OK Press F11 to Sent the project file to target. Once this process is complete you will be able to recover the project file Open Vista workstation. Create a Xenta Server Right-click and edit the Xenta Server XBuilder will open Configure the Xenta servers IP and password information to match the existing device Select Project>Get From Target XBuilder will import the project files from the field device In XBuilder click on Vista Database and chose "Save As..." and browse down to the Xenta Server and click "Select" Click "OK" to the message "The LonWorks network in your XBuilder project will be replaced by the LonWorks network under the Xenta Server in Vista." In Vista, click on Refresh to refresh the Xenta Server

Issue Changed MNL controller application engineering units to Metric (Celsius temperature) using the hardware wizard. After downloading the modified application, the setpoints and setpoint range on the MN-Sx sensor are still reading in degrees Fahrenheit. Product Line TAC IA Series Environment I/A Series WorkPlace Tech Tool software. I/A Series MNL I/A Series MNB Cause Changing the engineering units from English to Metric using the Hardware Wizard does not alter the values already configured for the setpoints or setpoint ranges in the MN-Sx sensor. The standard applications have predefined setpoint values and setpoint ranges based on the application type and MN-Sx type. These setpoints and setpoint ranges are configured with values appropriate for the operation of the controller using English engineering units (Fahrenheit temperatures). When the controller's engineering units have been changed to Metric, the appropriate temperature setpoint values and temperature setpoint ranges must be entered via the appropriate screen of the Resolution After using the WorkPlace Tech Tool Application Wizard to change the controller's application engineering units, the entered values for any setpoints and setpoint ranges must be reentered as numbers appropriate for the new engineering units. The application template files are configured for English (standard) engineering units with temperatures in Degrees Fahrenheit. For example, the default space temperature setpoint is 70 degrees. By default, the controller is configured for English engineering units, resulting in the space temperature setpoint is 70 degrees Fahrenheit. Changing the controller engineering units to Metric will result in the default space temperature setpoint being 70 degrees Celsius unless the setpoint and setpoint range is redefined using the Hardware Wizard.

Issue Safety information can be requested when distributing thermostats, particularly via airplane. Product Line Field Devices Environment Room thermostat Cause Not all documentation is available to download. Resolution TC300 3AxL Series Low Voltage Certificate of Conformity TC300 3AxL Series Electromagnetic Compatibility Certificate of Conformity TC300 3AxLM-DLS-DLMS Series Low Voltage Certificate of Conformity TC300 3AxLM-DLS-DLMS Series Electromagnetic Compatibility Certificate of Conformity Battery material safety data sheet. Identification and classification report for air transport of goods.  

Issue Can not edit the graphic pages of a Niagara G3 ENC station via a Web Browser Environment Niagara G3, ENC-410, ENC-520 Cause The PxEditor Module must be loaded on the ENC in order to edit PxViews via a browser. Resolution The PxEditor Module must be loaded on the ENC in order to edit PxViews via a browser. Open the Platform of the ENC Double-click on Software Manager Scroll down and highlight the PxEditor module (is will read “not installed”) Click the “Install” button and then “Commit” button at the bottom of the screen. The PxEditor module will now be installed to the ENC. Once the module installation is completed, the ENC’s graphics can then be edited via a web browser.  

Issue How to collect log files from the Project Configuration tool. Product Line EcoStruxure Building Operation Environment Project Configuration Tool Cause When contacting Product Support about issues with the Project Configuration tool, log files should be provided. Resolution Go to the PCT installation folder and run the program called LogCollector.exe located there. The default installation folder for versions 1.2 and higher is: "C:\Program Files (x86)\Schneider Electric EcoStruxure\Building Operation\Project Configuration Tool" and "C:\Program Files (x86)\Schneider Electric StruxureWare\Building Operation\Project Configuration Tool" for previous versions. Click Collect logs A program log of what LogCollector has done is displayed. A zip-file containing the collected PCT logs is created on the desktop.

Issue There are a number of reasons that RPC error occur on Cyberstation and troubleshooting steps are needed Product Line Andover Continuum Environment Continuum Webclient Windows XP Window Vista Windows 7 Windows Server 2003 Windows Server 2008 Cause RPC (Remote Procedure Call) errors happen on Cyberstation when the connection to the SQL database is not available Resolution There are many reasons that RPC errors can occur. A Google search of RPC errors will indicate that many applications have similar issues with these errors. An RPC error on a Cyberstation means that it has lost connection to the database for some reason and you will need to restart Cyberstation in order to recover. Below is a list of things to check when dealing with RPC errors on CyberStation.   Multiple Cybers Does the issue occur on multiple Cyberstations? Database Does the issue follow the database? i.e. load the database onto a test server or try a test blank database. Were some new objects recently added to the database when this started happening? Does reverting to a backup stop the errors? Increase Virtual Memory Right Click on My Computer> Properties> Advanced System Settings> Under Performance select the Settings button> Advanced tab> Under Virtual Memory click the Change button Recommended is 4096 Network disruption or slowness Networking  -  Verify all aspects of your networked environment.  This includes, but not limited to, slow networks, possible problems with your network interface card (NIC), cabling issues, switch/router issues, busy networks.  As you can see from the above definition of what RPC is it can be heavily reliant on the stability of the network and all it’s interfaces. Continuum does not support DHCP Multiple NIC cards – ensure there is only 1 NIC card enabled. No all NIC cards are created equal. Connections issue can be caused by an integrated NIC card of low quality. There can be settings within the NIC card itself that could affect consistent communication. Check the manufacturers website for details. Verify that there is no duplication of IP addresses on the network. Pull a cable and ping the address, if you still get a response there are 2 devices with the same IP address. WINS -  Verify your WINS settings and make sure there are no issues with the WINS Server.  This is known by Microsoft to cause RPC errors. DNS - Verify your DNS settings and make surer there are no issues with the DNS server.  This also is known by Microsoft to cause RPC errors. Verify that  the "TCP/IP NetBIOS Helper" service is running. Check and see if “File and Print Sharing” is enabled.  There are references in a lot of online articles, on RPC, problems that turning on “File and Print sharing” resolves RPC errors. Ping and SQL Is the SQL database still available to Cyberstation? From a DOS prompt> Ping IP (SQL Server) –t (continuous) Ex. c:\> ping 192.168.1.5 –t Note the number of responses as well as the time in milliseconds to respond. A local SQL server would usually be under 100ms. Check resources on the SQL Server (CPU, I/O Read/Write, memory usage, etc.) Windows Server 2003 Network card setting (This setting isn’t available in Windows Server 2008) Shut Continuum down on the machine having the problem. Start>Settings>Network Connections>Local Area Connections>Right Click and select Properties> Click on File and Printer Sharing for Microsoft Networks>Click Properties button> Select 'Maximize data throughput for network applications'. (Default is Maximize data throughput for File Sharing) Ok through all the screens and start Continuum and see if this makes a difference. XP/Vista/Windows 7 Start> Settings> Network Connections> Local Area Connection> Properties> Advanced tab> Windows Firewall - Click the Setting button> Click the exceptions tab Verify that File and Print Sharing is selected. File and printer sharing are disabled by default with XP SP2. There is no network throughput option in XP, Vista or Windows 7 like there is on Windows Server 2003. Windows Event Viewer Take a look at the Windows Event Viewer Application Log (Start> Run type ‘eventvwr’ or Launch Windows Control Panel> Administrative Tools> Event Viewer Examine the events and look for RPC error indications in the details. There may be a pattern of which executable is causing the errors. You may also see informational events that indicated momentary disconnects. A large number of these can indicate an issue with the Cyberstation being able to connect to the database consistently in a timely manner. Monitoring tools Run an acctrace.exe (C:\Program Files\Continuum) and a wireshark capture at the time of the RPC error to see the Continuum and network processing going on at the Cyberstation. Windows Process Monitor may also be helpful in seeing which process is having trouble. http://technet.microsoft.com/en-us/sysinternals/bb896645 Check the system for SpyWare and/or Viruses. Workgroup versus Domain connection An excerpt from the Continuum System Admin manual In a LAN Configuration, the Continuum CyberStation must be in a “Microsoft Domain “ type installation. This is because the Continuum CyberStation will use Named Pipes Interprocess Communication System (IPC). This is accomplished with Windows remote procedure call (RPC). In a Microsoft Domain model installation, once the session is established between the Continuum Cyberstations Client(s) and the SQL server it is a persistent connection once authentication is established.   In a Workgroup installation, the database connectivity session is re-authenticated and re-established for each database transaction. This results in much slower performance and an inconsistent connection. If you are running a LAN system using Windows 2003 server SP2/R2 and SQL 2005 try disabling the TCP Chimney Offload feature by following the below. Disable the TCPchimney setting on the SQL server and application server Windows 2003 SP2 comes inbuilt with a new network scalability pack which is supposed to accelerate the Windows networking stack. But this setting may not be compatible with all the network cards and it could pose connectivity issues as well. For more information you can refer to http://support.microsoft.com/kb/912222 http://support.microsoft.com/kb/942861   To disable this feature please take the following steps on both the SQL Server and application server.   Open up a command prompt on the machine. Run the following command: "Netsh int ip set chimney DISABLED" Change the values of the following registry keys to 0 a. HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\ EnableRSS   HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\ EnableTCPA Reboot the machine after the above changes. ==========================================================   Disable SynAttackProtect on SQL server: Windows 2003 Sp1 and Sp2 introduces this new feature which monitors processes getting high number of connections and if it detects that too many connections are being made, the connections will be rejected. Click Start, click Run, type regedit , and then click OK. Locate and then click the following registry key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters On the Edit menu, point to New, and then click DWORD Value. Type SynAttackProtect , and then press ENTER. On the Edit menu, click Modify. In the Value data box, type 00000000 . Click OK. Quit Registry Editor. Sound Card In some cases it was found that the built in sound card is causing the problem. If your not using WAV files for alarms then try disabling the integrated sound card in the BIOS.  If WAV files are being played then try disabling the integrated sound card and put in a PCI sound card. There have also been problems with OEM versions of the Operating system of the client machines.  A lot of vendors, like Dell, add additional applications to the systems they ship to assist them if they need to remote into the computer for troubleshooting purposes.  It is strongly recommended that these OEM versions of the Operating System is removed and install the system from a genuine Microsoft installation CD. Go to Control Panel-> Administrative Tools -> services, click with right mouse button Remote Procedure Call -> click properties. remote procedure call properties window is now open, go to recovery and you´ll see: First failure, second failure, subsequent failures -> choose : restart the service. In this setup the system will automaticaly restart RPC when something shuts it down. Check all your Firewall settings.  If possible turn off the firewall for testing and see if the problem goes away. Check to make sure there are no ports being blocked that the RPC Server uses.  See KB 908472 (http://support.microsoft.com/kb/908472) details the steps for specifying the RPC port range.  Also, be aware of the consequences of reserving the RPC ports. This has the potential to break other applications that assign ports in this range. KB 812873 discusses this, too. http://support.microsoft.com/kb/812873 Make sure all Peripheral devices like Network cards, Video cards, Sound Cards, etc. have the latest drivers for them installed. http://support.microsoft.com/kb/913384 Control Panel > AdminTools >Services and selected the Properties for Remote Procedure Call (RPC)  In the Log On tab, they changed the Log on as: to the Local System Account. It had been "This Account" NT Authority\Network Service. Is an EventNotification configured to send a page on alarm? If a PC running Continuum did not have a modem but on startup Continuum was trying to send an alarm with a page then accdataservice was crashing causing an RPC. Microsoft KB177446 article that describes in depth RPC troubleshooting procedures http://support.microsoft.com/kb/177446

Issue At times it is necessary to get the Cyberstation product and database version without launching Cyberstation Environment Cyberstation Webclient Windows XP Windows Vista Windows 7 Window Server 2003 Windows Server 2008 Cause Need the ability to get the Cyberstation version without launching Cyberstation Resolution Using My Computer or Windows Explorer Navigate to c:\program files\Continuum Right Click on Continuum.exe Select Properties Select Version Select Product Version 1.74.0.20070914= 1.74 with No Service Pack Ex. 1.74.0.20070914 SP2 = 1.74 with Service Pack 2   To determine the database version in SQL: Use the SQL Server Studio Management Express and open the table "dbo.ACCDBVersion". This will show the database version as well as the Enhanced Alarm Logging and Enhanced Alarm Delivery status. 

Issue Solid red light Blinking red light Blinking green light Product Line TAC Vista Environment Xenta Programmable Controllers Xenta 280, 281, 282, 283, 300, 301, 302, 401, 401:B Cause The indicator lights on the face of the Xenta controllers can help explain the state of the controller with different actions.  Resolution There are two LED indicators – one red and one green on the Xenta programmable controllers.   The red service diode is primarily an error indication. It also lights up if the Service pin is activated. A solid red light usually indicates that the hardware has failed.  Please see a few simple steps to deactivate the solid red light below. Use a reset dongle to wipe the controller then reinstall the firmware and menta program. If the controller is the group master you might try to assign a different controller to group master.  This method has not been proven but has worked before during internal testing. NOTE: The hardware may need to be replaced if the solid red light continues after these steps. If the red indicator light is blinking once per second this will indicate a non-configured node. If the controller has been commissioned you might try to decommission the controller and try again. If the red indicator light is off this would indicate that it has been commissioned and added properly to the network.  You should not see the red indicator light if the controller is working properly. The green status diode blinks once per second to indicate that the program is running properly.

Issue Where to find a statement of discontinued products if needed. Product Line Andover Continuum Environment Obsoleted Continuum Controllers DCX250 DCX 250, Netcontroller CX9000, CX9400 Infinity products Cause Which products are no longer available? Resolution The following link details all products that were discontinued in 2007/ 2008: 2007/ 2008 Discontinued Products Also the DCX250 was obsoleted in 2011 see Product Announcement Discontinuation of Infinity 01-0008-300 (DCX 250) Also see Display options now the DCX250 is no longer available for DCX250 alternatives.  Search for all discontinuation announcements on The Exchange.

Issue Tables needed for linearizing a 10K thermistors for an I/Net 7716, 7718, 7728 and 7756 (upper board). Product Line TAC INET Environment 7716 7718 7728 7756 Cause Thermistors require the use of a look up table to linearize the data. Resolution Thermistor Inputs on PCU's 7716, 7718, 7728 and the upper board of a 7756 Enter the Temperature data in °C (First Column - 31 entries) Enter the corresponding resistance data in Ohms (Second column - 31 entries) Enter the dissipation constant in milliwatts per °C: 2 Low Temperature: -22.11°F (-30.06°C) High Temperature: 247.92°F (119.95°C) Point Value in °F: M=0.065942; b=-22.11377 Point Value in °C: M=0.03663447; b=-30.063207 Look Up Table: °C Ohms Current Self Htg Adj °C Adj °F VDC Counts Adj Cts 120 389 0.000481 0.045052 119.95 247.92 0.1872172 153 4095 100 680 0.000468 0.074521 99.93 211.87 0.3183521 261 3548 90 917 0.000458 0.096177 89.90 193.83 0.4199872 344 3275 80 1258 0.000444 0.12407 79.88 175.78 0.5587138 458 3001 70 1753 0.000425 0.158633 69.84 157.71 0.745767 611 2727 60 2489 0.0004 0.199471 59.80 139.64 0.9964769 816 2453 55 3045 0.000383 0.223671 54.78 130.60 1.1671138 956 2316 50 3602 0.000368 0.243359 49.76 121.56 1.32407 1084 2179 45 4368 0.000348 0.264484 44.74 112.52 1.5200445 1245 2042 40 5326 0.000326 0.283435 39.72 103.49 1.7375701 1423 1905 35 6691 0.0003 0.300218 34.70 94.46 2.0043736 1642 1768 30 8056 0.000277 0.308878 29.69 85.44 2.2308374 1827 1631 28 8777 0.000266 0.311174 27.69 81.84 2.3371678 1914 1576 26 9572 0.000255 0.312351 25.69 78.24 2.4453301 2003 1522 25 10000 0.00025 0.3125 24.69 76.44 2.5 2048 1495 24 10450 0.000244 0.312349 23.69 74.64 2.5550122 2093 1467 22 11420 0.000233 0.311127 21.69 71.04 2.665733 2183 1413 20 12490 0.000222 0.308669 19.69 67.44 2.7767897 2274 1358 18 13680 0.000211 0.304953 17.70 63.85 2.8885135 2366 1304 16 15000 0.0002 0.3 15.70 60.26 3 2457 1249 14 16470 0.000189 0.29383 13.71 56.67 3.1110691 2548 1195 12 18090 0.000178 0.286579 11.71 53.08 3.2200071 2637 1140 10 19900 0.000167 0.278241 9.72 49.50 3.3277592 2725 1086 8 21920 0.000157 0.268921 7.73 45.92 3.433584 2812 1032 6 24180 0.000146 0.258715 5.74 42.33 3.5371562 2897 977 0 32660 0.000117 0.224329 -0.22 31.60 3.8279419 3135 815 -4 36200 0.000108 0.211999 -4.21 24.42 3.9177486 3209 706 -10 55340 0.0000765 0.162028 -10.16 13.71 4.234772 3468 543 -14 69000 0.0000633 0.138199 -14.14 6.55 4.3670886 3577 435 -20 97130 0.0000467 0.105789 -20.11 -4.19 4.5332773 3713 272 -30 177200 0.0000267 0.063207 -30.06 -22.11 4.732906 3876 0 This spreadsheet is for a thermistor rated at 10,000 ohms at 25°C. Install a 10K Ohm Resistor in the "B" terminal (consult the TCON for the controller you are using for details) This look up table program is based on using 31 entries The data points do not have to be evenly spaced For the look up table to the 7756 lower board, see 10k Thermistor Look Up Table for an I/Net 7756 (lower board).

Issue Fluctuating temperature readings where they jump up to +327 randomly. Product Line Andover Continuum Environment Continuum controllers i2866-V Cause Readings like that are usually caused by wiring or power issues. There was also a Firmware fault that caused this in an old version of the i2866-V Firmware. Resolution Confirm the following wiring considerations:   That your input and output cables shield is wired to Earth ground at one end of the run only (preferably the controller chassis). That your controllers power supply is earthed on the secondary side of the 24vac transformer to ensure a proper controller ground to Earth. Confirm that the power supply is not being shared with any field devices, especially field devices feeding inputs back into the controller. One way to troubleshoot if it is a cabling or controller problem is to replace the sensor cable with a 10K ohm resistor. See Temperature inputs not reading the correct value for details. Also, in i2866-V controllers with firmware versions less than v3.501049, temperature inputs could randomly go to +327 when Analog Outputs were changing value frequently. Uprev your controller. See TPA-BOST-09-0007.00 for details.

Issue Procedure for installing PCC-10 or PCLTA20/21 network cards on a Windows 7 PC Product Line TAC Vista Environment Vista Menta LonMaker Windows 7 Cause Installation procedure differs from earlier versions of driver software. Resolution The PCC-10 and PCLTA-20/21 network cards work on Windows 7 (32 bit) PCs when the OpenLDV 4.0 driver is installed. This driver is installed automatically when Lonmaker Turbo SR4 is installed, but if this version of Lonmaker is not present the driver must be installed manually.  The latest drivers can be obtained from the Echelon download site: http://www.echelon.com/support/downloads Note: The PCLTA-20/21 card is only supported on 32bit windows operating systems. For 64bit systems use a NIC-USB as mentioned in this article: Computer will not recognize NIC709-USB. Install the drivers before fitting the card in the PC. Please note that OpenLDV4.0 requires .NET Framework 3.5 SP1.  This is not included as a subset of .NET Framework 4 or later, so must be installed separately.  You can have multiple versions of .NET framework installed on the same PC. The following description is for the PCLTA-21 but the PCC-10 is similar. To change the system image or perform diagnostics, you must go to Control Panel and open the Lonworks Interfaces application: Click Start on the taskbar, point to Settings, click Control Panel, and then open the LONWORKS Interfaces application. Click the PCLTA-21 interface in the list view on the left side of the user interface to display the interface's properties in the details pane in the right side. The details pane lists the PCLTA-21 card's system image and transceiver properties. To change the system image used by the PCLTA-21 card, click anywhere in the NI Application property, click the box to the right, and then browse to and select the desired system image from the LonWorks\Images\PCLTA21 folder. Note: For more information on configuring, testing, and diagnosing the PCLTA-21 network interface, see the LonWorks Interfaces online help.

Issue How long can the power to AS be interrupted Product Line EcoStruxure Building Operation Environment PS Power Supply Automation Server Cause Question regarding the AS and the power supply module. If the power is interrupted from the 24VAC power supply for say, 100 milliseconds, will the power to the AS be interrupted? There is a cold cap in the PS, and how long does it maintain power supplied to the AS? What about the RTC?   Resolution The power to the AS will be interrupted if there is a 100mS main power fail. The AS will then save the server cache. When the power returns the AS will make a restart that will take approx. 2 minutes. The AS Power supply fully complies with the IEC 61000-4-11 standard and can withstand voltage dips, with a 20mS dip and a 0% residual voltage.  The Power-fail process: When the AS loses power the super-cap keeps the AS alive for 15 seconds. 10 seconds of it dedicated to power-fail process to flush all the data that that are currently in the RAM to the SD card(That data can be anything with any value they have before power-fail). When power comes back that data is retained and are stored in appropriate place on the SD card. Real-Time-Clock(RTC) is maintained when the AS loses power by a dedicated capacitor which backs up the RTC chip for a minimum of 30 days in the absence of power since there is no battery in the AS.    

Issue CXR5805 CXT5605 and CZT5305 Climatronic Controller display flashing. Environment Satchwell CXR5805 CXT5605 CZT5305 Cause Manual Override Switch is set in a mode other than AUTO (Clock symbol) Resolution Reset Manual Override Switch to AUTO (Clock symbol) mode. N.B. Details of this and other Manual Override Switch mode options and associated selection / de-selection may be found in the respective Climatronic User Guides. CXR5805 User Guide may be viewed here. CXT5605 User Guide may be viewed here. CZT5305 User Guide may be viewed here.

Issue CSC4201 CSC4202 CSC4301 CSC4302 Climatronic Compensator Controller display flashing. Environment Satchwell CSC4201 CSC4202 CSC4301 CSC4302 Climatronic Compensator Controller Cause Manual Override Switch is set in a mode other than AUTO (Clock symbol) Resolution Reset Manual Override Switch to AUTO (Clock symbol) mode. N.B. Details of this and other Manual Override Switch mode options and associated selection / de-selection may be found in the CSC4201 CSC4202 CSC4301 CSC4302 Climatronic Compensator Data Sheet, a copy of which may be viewed here.

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 project folder size increases when an object is deleted. Product Line EcoStruxure Building Operation Environment Project Configuration Tool, PCT Cause Any change made in PCT increases the size of PCT project folder. This is by design and it is a normal behavior of PCT. The reason for this is that a project is a virtual machine using a dynamically allocated image that grows when memory is needed, but the image will not shrink when something is deleted.  Resolution The only way to reduce the folder size of a project is to backup all servers in the project, create a new project, restore the server backups to the new project and then delete the old project.

Issue Many LonWorks network installation problems can be avoided if the appropriate network design rules are followed when the network is being designed. Product Line TAC IA Series, TAC Vista, Satchwell Sigma Environment I/A Series MicroNet (LON) Controllers Satchwell Sigma MicroNet series LON Controllers Vista Xenta Controllers Cause The I/A Series MicroNet System Engineering Guide (F-26507) was written as a resource of information for the installation of the I/A Series MNL-100, 200 & VAV controllers as well as the Sigma MicroNet 440 and 620 controllers.  The Resolution, below, is a summary of the LON design rules presented in this document. Resolution FTT-10 LON network wiring must be installed using Echelon-approved wire.  The most common type of wire used is described as Category 4  cable.  This wire is normally unshielded stranded twisted-pair 22AWG (0.65mm).  An example of this wire is the W221P or W222P series cable from Connect-Air International (http://www.connect-air.com).  This type of cable is normally available both in plenum rated and non-plenum rated types.  Consult the job specifications to determine if plenum-rated or shielded cable is required. The LON network can be wired using "Free Topology" or "Bus Topology" wiring segments.   1.  BUS Topology Guidelines BUS Topology LonWorks wiring extends from device to device (daisy chain format) with no branches or stubs. A LON-TERM-2 terminator must be installed at each end of the LON bus. When using standard Category 4 LON cable with the recommended terminators, the bus may be up to 4593 feet (1400 meters) in length. When extending LON wire to the MN-Sx sensor base in a bus topology network, the sensor base must be wired as part of the daisy chain and not as a stub connection. 2. FREE Topology Guidelines Free Topology imposes essentially no restrictions on the layout of the network -- some controllers may be wired point to point and others branching from a common point.  The free-topology LON network must be terminated at one point with a LON-TERM-1 terminator. When using standard Category 4 LON cable, the total wire length in a free topology LON network may not exceed 1641 feet (500 meters).  In addition, the longest wire path between any two controllers on a free topology LON network may not exceed 1312 feet (400 meters). 3. Common LON Network Wiring Guidelines LON wiring can not be part of an active bundled telephone trunk even if the telephone trunk is wired with Category 4 wire. Shielded Category 4 wire may be used in high EMI/RFI environments.  The shield must be wired continuously and grounded through a 470 Kohm resistor at one end. LON wiring must not be bundled with or housed in the same conduit as controller I/O and power wiring.  4. LonWorks Network Wiring and Addressing Guidelines When the number of controllers on a LonWorks network exceeds 60, the network must be split into segments with not more than 64 controllers or devices per segment using LonWorks Repeaters or Routers.  When counting the controllers and devices on a LonWorks network segment, a LonWorks Network Interface Device and the repeater itself must be included in the device count in each segment. In a LonWorks network containing repeaters or routers, each LonWorks network segment must be properly terminated, as described above. Domain / Subnet / Node addressing is used when configuring the LON controllers. A LonWorks Subnet consists of a series of LonWorks controllers all configured within the same LON Subnet number. A single LonWorks Subnet can have a maximum of 127 device and controller Node addresses.  This Node address count includes the LonWorks Network Interface, all controllers on the subnet, and repeater and/or router node addresses.  An allowance is typically made for additional addresses to be used by LonWorks tools connected to the Subnet.