Building Automation Knowledge Base

Issue LON Network - Cable Transient Suppression Product Line EcoStruxure Building OperationTAC IA Series, TAC Vista Environment LON networks that extend beyond the walls of a single building Cause Surge arrestors dissipate transient energy before the cable can provide a low resistance path to the building ground, preventing potential electrical damage. Resolution Click here to download the white paper on this topic: Cable Transient Suppression It is recommended that a Transient Suppression protection device be installed on the LON communications cable at any point where the cable enters or exits the building. The LON is frequently used to connect a collection of controllers in one building with a collection of controllers in one or more other buildings in a campus. The LON may also extend outside the protection of an office building when servicing communications to roof-top equipment and/or outside monitoring equipment. At any location where the LON cable penetrates and extends outside the building compartment, it is recommended that a gas discharge type lightning arrestor be installed across the LON conductor pair and earth ground as shown below. This should be positioned as close as possible to the wall penetration location. The objective is to keep the cable distance as short as possible before the cable suppression is provided. It is important that a heavy gauge earth ground connection be provided to the gas discharge protector with as short a length as possible. Here we want to dissipate the transient energy as soon as possible before the cable extends on into the facility and provide a low resistance path to the building ground. SA2-U8 Surge Arrestor TAC provides a Model SA2-U8 Surge Arrestor which can be used for this purpose. This SA2-U8 device is a gas discharge arrestor packaged in a small DIN rail mountable enclosure. The SA2-U8 is UL864 listed and is the only device that can be used on TAC UL864 listed system. It must be installed on the LON cable at any entry/exit locations. Other Gas Discharge Suppressors On non-UL864 systems, the SA2-U8 may also be used, or the installer may use any one of a number of available 90V gas discharge tube devices. These are typically tubular shaped components and since you need two tubes (one for each of the two LON conductors) a dual element three lead discharge tube is recommended. The device’s leads may be attached to a standard screw terminal block and mounted in most any size electrical box. A collection of some of the suitable gas discharge devices that could be used is as follows: Manufacturer Part Number Bourns 2026-09-C Epcos B88069X8440B202 Citel BTS-90 SRC Devices PMT-090-14   There are other acceptable part numbers available from each of these manufacturers with variations provided in the lead configuration and lengths while maintaining the same 90V protection rating. Devices To Avoid It is not recommended that you use any semiconductor type (Transzorb / TVS / Diode) protection devices. Their higher speed and lower clamping voltage characteristics is not necessary with the inherent protection offered by the FTT-10 and FT-X1 LON transceivers. Such semiconductor based transient suppression devices frequently add some undesirable capacitance to the network which impedes communication performance and most inject signal clamping at voltage levels much lower than necessary or desirable for the Free Topology FTT-10 and FT-X1 based LON networks. The common mode noise immunity of the FTT LON should be much better than that provided by the typical RS485 network. This should provide more tolerance for electrically noisy environments. However, it has been observed that some semiconductor based network protection units have been used that can drastically degrade communications performance. One such device is the Model 91287 from Atlantic Scientific Corp. which was identified by the manufacturer as a LON System protector. This device clamps the signal at one diode drop below ground level which virtually destroys the LON’s common mode noise tolerance. The presence of one of these devices has been found to be the cause of communications problems in a system operating is an electrically noisy environment. This type of communications impairment may be encountered immediately. In other instances, LON retries may cover the problem and the system may operate for extended period of time before environmental or equipment changes raise noise levels above the tolerable threshold. This threshold is now much worse than RS485 networks. This device, and any similar, should be avoided on any LON systems.

Issue In WorkPlace Commissioning Tool, the following error message appears when browsing a BACnet/IP network: "A critical error occurred in the communication server rtmonitor.exe. Please shutdown this application and the communication server then try again." Product Line TAC IA Series Environment WorkPlace Commissioning Tool Cause There could be a Niagara R2 station running on the computer configured for BACnet/IP. Since the Niagara station also uses UDP port 47808 by default, the Niagara service prevented WorkPlace Commissioning Tool from "binding" to the UDP port. Resolution There are two ways to resolve this issue: Disable the Niagara service when using the WorkPlace Commissioning Tool In Workplace Pro, stop the station that has the BACnet/IP service enabled, and configure it so that it does not auto-start. NOTE: If this procedure does not correct the issue and the WorkPlace Tech Tool software is being run on the Windows 7 operating system, refer to WorkPlace Commissioning Tool Windows 7: "A critical error occurred in the communication server rtmonitor.exe" for information on how to correct what may be a program security settings issue.

Issue A PCI I/O board added to allow a parallel port for a security key is not recognized by the key. Environment Continuum Windows XP Windows Vista Windows Server 2003 Windows Server 2008 Cause The default setup for the Sentinel driver does not configure the PCI port Resolution After adding a PCI I/O board to allow a parallel key, the security key is not recognized. Even if a printer works on this parallel port and another machine reads the key perfectly, the security key does not work. Uninstalling and reinstalling the Sentinel driver does not make a difference. The Sentinel driver needs to be configured to allow the parallel port to be accessed via the PCI bus. By default, only the ISA and USB port types are shown. Follow these steps to add the port for the installed PCI board: From the Control Panel, double-click the System icon to open the System Properties page. Click the Hardware tab and then the Device Manager Button to open the Device Manager. Click the + sign next to Ports (COM & LPT) to expand the tree. Double-click on PCI Card (LPT1) to open the property sheet for the PCI adapter. Click on the Resources tab to see the resources used by the adapter. Under Resource Settings, make note of the first number in the range of the first line. Ex. I/O Range 0378-0374 (the number to make note of is 0378) Next, Start the driver configuration utility, SetupSysDriver.exe. It is usually located at C:\Program Files\Rainbow Technologies\Sentinel System Driver Click the "Configure Driver" button, then click the "Add" button. Enter the I/O address of the PCI parallel port adapter into the "Bus Address" field. Ex. 0378. For Port type select PCIbus and Click on OK It will show that a User Created port has been added at address 0378. The Sentinel System Driver should now be configured to use the Parallel PCI adapter.

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 After an uninstall of I/NET Seven and MS SQL, you might verify in the Windows Registry that all the items were deleted. Having issues installing I/NET what can I look for. Product Line TAC INET Environment I/NET all 2.4X versions Cause In some cases when re-installing, installing I/NET after a failed attempt or upgrading I/NET you may want to start fresh. After an uninstall of INET Seven and MSDE if items remain in the registry they will cause issues with future installations. Resolution Go to the bottom Task Bar and choose the “Start” button. Select the “Run” option and enter “Regedit” Once in the Windows registry go to “HKEY_CURRENT_USER, if the “CSI” entry is present delete this entry While still in the HKEY_CURRENT_USER look in the Microsoft File Folder for any “SQL” entries and remove them if they are present. Minimize the HKEY_CURRENT_USER folder and open up the HKEY_LOCAL_MACHINE File Folder, if the “CSI” entry is present delete this entry. While still in the HKEY_LOCAL_MACHINE, go to the Microsoft File Folder and look for any “SQL” entries. If you find any delete then from this file folder. Caution:  Before editing the SQL registry items you should ensure that no other software using SQL is still installed - all software that is installed should be uninstalled prior to modifying any registry entries. See also, MSDE and Windows 7.

Issue Advice on adding a persistent route to the Sigma server PC. Product Line Satchwell Sigma Environment Sigma Server PC Cause General advice Resolution On a Sigma server connected to a "Flat" Ethernet network, where the system is using Ethernet or Arcnet communications via DNN's, and where it is not possible to run RIP on the DNN's, then it will be necessary to add a persistent route or routes to the Sigma server. A "Flat" Ethernet network, is a network that does not contain any subnets, for instance a network who's address is 10.158.0.0 Mask 255.255.0.0 will contain network addresses 10.158.0.1 to 10.158.255.254. To add a persistent route you must go to the Windows command prompt. This is achieved by selecting the Windows "Start" button, then the "Run" command and enter "CMD", a DOS window is now opened. At the DOS prompt type ROUTE ADD -P "Subnet address" "Mask" "DNN Ethernet IP address". So if the DNN Subnet was 192.168.1.0 mask 255.255.255.0 and the Ethernet IP was 10.158.1.6 then the persistent route would be added as below ROUTE ADD -P 192.168.1.0 MASK 255.255.255.0 10.158.1.6 To check that this has been correctly added enter "Route Print" at the command prompt, the route should have been added at the bottom of the list. Add a route for each DNN.

Issue Procedure for balancing a parallel fan VAV box with supply side flow sensing, using the WorkPlace Flow Balance Tool (WFBT). Product Line TAC IA Series Environment I/A Series MNB VAV Cause Request from field Resolution In summary, the procedure is to complete the balancing process with the fan disabled then enable the fan and use the verify functions to check operation with the parallel fan running. Perform all steps of the flow balance procedure as usual up through and including the maximum flow balancing and minimum flow balancing. For the first pass at balancing the reheat minimum flow, use the fan control on the screen to turn the fan ON then set the minimum flow setpoint to 0. Verify that the flow as measured by the pressure sensor goes to zero. Measure the total flow manually using the flow hood and adjust the fan speed so that the required airflow is obtained. The easiest way to do this is to take the first set of readings from all the diffusers then adjust the fan speed as needed and then recheck the sum of the new readings to confirm the adjustment is correct. Click the "Restart" button to restart the Reheat Min Flow balancing process. Set the parallel fan to OFF and re-enter the desired Reheat Min Flow setpoint value. Balance the Reheat Min Flow using the normal balance procedure. For reference, see Chapter 5 of the WorkPlace Commissioning Tool and Flow Balance Tool Users Guide (F-27358).

Issue Original company sold to new company Site License needs to be updated for install/upgrade.  Computer failure and no software/license information is available. Downloaded software and during install it requests a CD Key Product Line Andover Continuum, TAC INET Environment Site Licensing for install/upgrade Cause Changes in company or computer replacement/upgrade or downloaded software and it is requesting a CD Key Resolution I/NET: 1. Original company sold to new company and Site License needs to be updated for install/upgrade: for company naming changes, contact your sales representative who in turn will contact Product Support and request a transfer of information or upgrade/purchase. Once the information has been cross referenced for validity, either a new or replacement CD Key can be generated. Please include the following when requesting transfer: User Name Site Name Site Address Serial Number Version number Build number CD Key 2. Computer failure and no software/license information is available: Send email to Product Support with the following information: User Name Site Name Site Address Serial Number version number Build number CD Key 3. CD Key for licenses on purchase of software can be ordered by contacting Contact Customer Care. Link is available on the Contact tab of this web page. Customer Care offers pricing, order placement, changes, expedites, and order status. Check Licensing of I/NET with SITE and SEAT License with License Key for issues with CD Key and Licensing information. Continuum: since Continuum only has physical security key licensing, the license is owned by the holder of the key. If you hold the key, you own the license. There is no need to contact PSS for moves, changes, restructuring. If the security key's are lost or stolen, you will need to purchase new keys to replace them. Continuum Software Licensing is available with Release 2.0. 

Issue When executing a Find New BACnet Device a third party controller (Alerton) would not come into the system. Product Line Andover Continuum Environment CyberStation BACnet Alerton Cause The third party device did not have a name assigned to it. Duplicate device id on the network. Resolution Check with third party vendor to determine how to assign a name to the device When devices from different vendors are used it is possible to have device id duplication which will prevent one or more of the devices to be found. If device id duplication is detected, Continuum will indicate the condition in the error log. To solve the problem you must change the device id of one of the devices so that they all have unique device ids. You can determine which devices are duplicating by running acctrace and a wireshark while doing a Find New Bacnet and then looking in the database for these objects. If you cannot interpret what is found in those traces, send them to PSS for analysis.

Issue When starting up the Continuum Workstation an error "SmartHeap library out of memory" error is displayed and Continuum does not startup. Product Line Andover Continuum Environment Continuum Cyberstation Microsoft Windows Cause The PC memory allocated for Cyberstation to use is insufficient for the application and the site's configuration. There are three known items that can require more memory to be required on Workstation startup. EventNotifications. If a very large number of them. The Workstation reads all of them and may require more memory at startup. Workstation Programs. Check in the Workstation for many or large Programs. Objects in the Root of Continuum. The startup of WS can be very long with a large number of objects in the Root. Resolution Verify that the PC being used for the workstation meets the minimum requirements as defined in the Install.pdf document for the specific Cyberstation version being used. If other applications are to be run on the PC then the RAM size should be increased accordingly. If the system StandAlone (Single User) 1.81 or before then verify the database size is below 2Gb, For Version 1.82 and above it can not exceed 4Gb. Verify that you have sufficient available memory you have when seeing the error, using task manager. If the above checks confirm that the basic PC memory is sufficient then the following changes can be made to allow the Cyberstation application further resources, this is often required when a number of Plain English programs are running in a Workstation. Shut down Continuum and set the Virtual Memory size Initial to 2048 and Maximum to 4096. Using Regedit go to the registry key HKEY_CURRENT_USER\Software\Andover Controls\Continuum\Settings and increase the setting for omscachesize to 5000 decimal. For systems where the Workstation is known to have an extremely heavy workload, this number may be increased up to 9000 in decimals. If using the Elevator Control Module add-on, it may be necessary to set the size to 5000. Note: For new Continuum or WebClient Workstations, the omscachesize registry key is not created until after the Workstation has first logged in at least once. If you are adding a Workstation to an existing LAN installation with a large ContinuumDB, then the omscachesize may need to be increased right from the start. One way to do this is to: Create  a new "test" database, see Creating a test database for troubleshooting for more information. Connect this Workstation to that test database so that the correct registry keys are created Change the omscachesize value as described above Restart the PC Reconnect to the original production database and start-up Continuum.

Issue When trying to reload a B3867 controller or add log arrays to existing points, a memory error is encountered. Product Line Andover Continuum Environment Continuum 1.xxx B3867 Cause A memory allocation defect that was found in the -V versions of the controller was fixed in drop 51 of the -V firmware. The same issue was resolved in drop 64, but was not listed in the release notes. Resolution Update the B3867 version to the drop 64 rev.

Issue SNP I/O server and NCP I/O server dongleless software download location. Where can I download SNP I/O server and NCP I/O server dongleless software as advised in: PA-00145 - Satchwell MicroNet Range Rationalisation Product Line Satchwell MicroNet Environment MicroNet View. SNP I/O server dongleless software NCP I/O server dongleless software Cause SNP I/O server software can no longer be ordered, it is available as a free download. Resolution Download the software from The Exchange or Click here to be linked to the Monitor tool.(This link will open a new page) Click here to be linked to the SNP I/O server. .(This link will open a new page) Click here to be linked to the NCP/ARCnet I/O server. .(This link will open a new page).  

Issue Is it possible to run TAC Vista 5.X.X in Windows XP compatibility mode (When TAC Vista Installed on Windows Vista, Windows 7, Server 2003/2008) Product Line TAC Vista Environment TAC Vista 5.X.X Windows XP Windows Vista Windows 7 Windows Server 2003/2008 Cause If TAC Vista 5.x.x is Installed on Windows 7, Windows Vista, or Windows Server 2003/2008, is it possible to run the Vista Workstation on Windows XP using Compatibility mode. Resolution TAC Vista has several other applications that work together with Vista. These applications do not support compatibility mode. Upgrade to Vista 5.1.4 or later which support Windows 7. If the operating system is a 64-bit version, upgrade to Vista 5.1.5 or later. For the compatibility matrix see Software and Firmware compatibility matrix for older versions of the traditional product lines.

Issue How to register LonTalk Protocol Analyzer Software Product Line EcoStruxure Building Operation, TAC Vista Environment Vista LPA Cause The LonTalk Protocol Analyzer software is a tool for LonWorks network troubleshooting. There are two kinds of LPA license. Some customers may be confused about it. Resolution To use the LPA, you need to purchase the software license. There are 4 kinds of LPA license. Refer to this page for further explanation. LPA-SW: This license is bound to NIC709-USB.  Need to use specific NIC709-USB to be the network interface of the software. LPA-IP-SW: This license is bound to NIC852. Need to use specific NIC852 to be the network interface of the software. LPA-IP: Same as the above, but includes a dongle.   The steps of registration for the current version of LPA using the current NIC driver is the following: Install the drive for the LOYTEC Network Interface. Refer to Loytec's Website. Open the LPA program Click on "Help->Register Product"   Enter the Registration Code in the product package, and click Add.   The steps of registration for previous versions of LPA using the previous NIC driver is the following: Install the drive for the LOYTEC Network Interface. Refer to Loytec Website. Open the LConfig program.   Click Register / Activate to open the registration window. Enter the Registration Code in the product package, and click Add. Then the registration is finished. Open the LPA software to test whether the license works fine.

Issue What is the part number for the battery in a Network 8000 GCM? Environment Network 8000 GCM-84000 series, GCM-86000 series, LNC-100, SIM-CCN, SIM-MTECH, SIM-TRANE, and SIM-YORK. Network 8000 LCMs. Cause Need to replace a discharged  battery in a GCM or an LCM. Resolution The part number for the replacement battery is E17-129. NOTE:  The E17-131 is a functional replacement for the E17-129 which is now obsolete.  The E17-131 can be found on iPortal   For a GCM-86000 series, LNC-100, SIM-CCN, SIM-MTECH, SIM-TRANE, and SIM-YORK, replace the battery according to F-25895, GCM-861X0 Series Global Control Module Installation Instructions, "Battery", "To Enable Battery", "To Replace Battery", and "Checkout" sections. For a GCM-84000 series or an LCM, replace the battery according to F-23116, "LCM / GCM Battery Installation Instructions".

Issue After successfully logged into Xenta Server web pages, java loading icon will be displayed as shown below. However, after a while it will automatically log the user out as shown below. Product Line Satchwell MicroNet, TAC INET, TAC Vista Environment Xenta Servers 5.1.6 (Xenta 511, Xenta 515, Xenta 527, Xenta 701, Xenta 711, Xenta 721, Xenta 731, Xenta 913) Java 1.6 update 29 Note: This behavior may happen on other Xenta Server versions with different Java versions. Please refer to the Cause section for the reason. Cause Vista may not support the newest Java versions. For Vista 5.1.6, the recommended Java version is Java 1.6 update 20. Please refer to Recommended Java version for TAC Vista 5 for recommended Java version details. Resolution Go to Start > Settings > Control Panel > Add or Remove Programs. Find Java application (in this example is Java(TM) 6 Update 29), and select “Remove”. Reload the Xenta Server webpage, will find the Java icon will not be displayed this time. Instead, “Download Java” request link will be displayed. Click on the link and download the supported version of Java. The issue should be solved after the recommended version of Java is installed.

Issue Sigma BAS Cabling Guide Product Line Sigma Environment Sigma BAS Cause Cabling Guide Resolution Cabling guide for BAS and Sigma.

Issue DC2100 series Optimiser / Compensator Controller requires replacement due to obsolescence. Environment DC2100 series Optimiser / Compensator Controller installed to control Variable Temperature Mixing Valve, Boiler/s, Pumps etc. Cause Obsolescence of DC2100 series Optimiser / Compensator Controller. Resolution OVERVIEW DC2100 series Optimiser / Compensator Controllers are flexible with regard to the number and type of electrical inputs and outputs to which they may be connected, enabling the Controller to be applied to a wide range of control applications.  Of the DC2100 series Optimiser / Compensator Controller models manufactured, the final version was the DC2100H Overview details of the DC2100H Optimiser / Compensator Controller may be viewed here. INSTALLATION AND COMMISSIONING In view of the numerous control applications to which the DC2100 series Optimiser / Compensator Controller may be applied, numerous wiring connection variations will also apply. Please therefore check the number of inputs and outputs connected to the DC2100 series Optimiser / Compensator Controller installed before proceeding, as this will assist in determining the suitability of the possible replacement Controller suggested below. Installation and Commissioning details of the DC2100H series Optimiser / Compensator Controller may be viewed here. POSSIBLE REPLACEMENT  The most common control application to which theDC2100 series Optimiser / Compensator Controller may be applied comprises the following combination of inputs and outputs.  Outside Air Temperature Sensor Inside Air Temperature Sensor Compensated Heating Temperature Sensor Variable Temperature Heating Circuit Valve Actuator Boiler/s (2 maximum) H W S On/Off output (independent) Should such inputs and outputs be confirmed then the DC1100 Optimiser / Compensator may be installed in place of the DC2100 series Optimiser / Compensator Controller. Details of the DC1100 Optimiser / Compensator Controller may be viewed here. Drayton A7xx series Sensors connected to the DC2100 Optimiser / Compensator Controller are compatible with the DC1100 Optimiser / Compensator Controller and may therefore be retained. N.B. It should be noted that where a DC2100 series Optimiser / Compensator Controller is included in an installation of a more complex nature then an alternative solution utilizing different products may need to be considered. In such installations not only will the DC2100 series Optimiser / Compensator Controller need to be replaced but its associated Sensors will also need to be replaced. Resolutions to such installations may best be determined following a review of the control system installed by a member of the local Schneider Electric office.

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 Installation cable requirements Product Line Andover Continuum Environment Continuum Cause Need to specify a cable type for a site Resolution Installation cables have to be chosen taking in to account the local regulations and legislation, the installation environment and the electrical requirements. The Continuum specifications give the electrical requirements. For this reason actual cable types, makes or Belden numbers can not be stated, only as helpful guidance as a cable that may meet the electrical requirements only. BACNET MSTP - See What cable type should be used for BACnet MS/TP communications?. INFINET - See What cable type should be used for Continuum Infinet bus communications. CARD READER - See the manufacturers requirements for the cables, also Maximum Cable Length Between ACX and Card reader. ANALOGUE and DIGITAL INPUTS - See the relevant Continuum specification eg. I/O Modules. See Andover Continuum IO System Reference (especially note screening and grounding requirements) I/O MODULE (RS-485 & LON) - See the relevant Continuum specification eg. I/O Modules See Andover Continuum IO System Reference For ETHERNET, LON, MODBUS RTU, OTHER THIRD PARTY BUS/NETWORK - See the relevant external documents