Building Automation Knowledge Base

Issue A floating-point value is displayed incorrectly in a TGML graphic. The presentation field appears to show random numbers. The example shows how the value 11.60 is represented in a TGML graphic. 11.60 is actually stored as 11.600000381469727. In format presentation mode: In none presentation mode: The last 6 digits of the stored floating-point value are seen! Product Line TAC Vista Environment TAC Vista 5.1.X TGML editor 5.1.X A presentation text bound to a floating-point value. Cause Vista uses the PC's default settings for number of decimals, when presenting values in TGML graphics. Resolution To resolve the issue, either set the format property to "Presentation" for the binding object or change the PC's settings to view fewer decimal places eg. 2.

Issue Values are coming into Vista without issue but do not update on the graphics in the Xenta 7XX. Product Line TAC Vista Environment Workstation Graphics Xenta Server 701, 711, 721, 731 Cause If there is a Xenta Server in the database, when connection objects are not used to bind values between a controller and a Menta program in the Xenta Server, this graphic update can occur. It can also be because of the XIF for a device being formatted incorrectly. If the procedure below doesn't solve the issue, refer to LON device can communicate in Vista, but fails in a Xenta Server / XBuilder Resolution There are two options to correct this issue: Re-engineer the XBuilder project to use connection objects between the controller and the Menta program in the Xenta controller. The control task speed of the Menta program in the XBuilder project can be changed to a lower speed setting.

Issue Various errors during installation of I/NET 2.42 and Vista 5.1.7 on a 64-bit Operating system Product Line TAC INET, TAC Vista Environment Windows 7 64-Bit Cause Windows 7 64-Bit Resolution Overview: Install SQL according the instructions found in the SQLExpress folder on the I/NET CD Run the SQL Server 2005 backwards compatibility tool located on the I/NET installation CD Install Vista 5.1.7 Install I/NET 2.42. Step-by-Step Process: Installing SQL Download SQL2008 Express 64 (SQLEXPR_x64_ENU.exe) bit from this location http://www.microsoft.com/en-us/download/details.aspx?id=1695 Run SQLEXPR_x64_ENU.exe In the left hand section, select Installation In the Right and section, select New SQL Server stand-alone installation of add features to an existing installation. At the "Setup Support Rules" screen select OK At the "Product Key" screen, select Next At the "License Terms" screen, check accept and select "Next" At the "Setup Support Files" screen, select Install At the "Setup Support Rules" screen, select Next At the "Feature Selection" screen select: Database Engine Services, SQL Server Replication, Management Tools - Basic (If Present) and SQL Client Connectivity SDK. Leave the Shared feature directory as default. At the "Instance Configuration" screen, select the Default instance option, accept the default Instance ID, accept the Instance root directory default settings and select next. At the "Disk Space Requirements" screen, select Next At the "Server Configuration" screen, under SQL Server Database Engine set the Account name to NT AUTHORITY/SYSTEM, leave the password field blanks, and set the startup type to automatic. Under SQL Server Browser Service, set the Startup Type to Automatic At the Database Engine Configuration screen, set the Authentication Mode to "Mixed Mode", Define a strong password (example: @sql2008), in the Specify SQL Server administrators section click "Add Current User". Select Next. At the "Error and Usage Reporting" screen, select Next At the "Installation Rules" screen, select Next At the "Ready to Install" screen, select Install At the Installation Progress screen, when the setup process is complete, select Next At the "Complete" screen, select Close. SQL Configuration: In the Windows Start Menu, launch the SQL Server Configuration Manager In the Left hand section of the window, highlight SQL Server Services Verify that SQL Server Browser and SQL Server are Running In the left hand section of the window, expand SQL Server Network Configuration and highlight Protocols for MSSQLSERVER Enable Named pipes and TCP/IP Close the SQL Server Configuration Manager Restart the PC Installing SQL Server 2005 Backward Compatibility On the I/NET 2.42 installation CD, look in Support\SQLBCM_64Bit and launch the SQLServer2005_BC_x64.msi file Follow all the prompts on each screen and accept all defaults. Install Vista 5.1.7 Download and Run the TAC Vista Server 5.1.7 installation package. Accept all default settings Do not start the Vista Server at this time Install I/NET Seven 2.42 Install I/NET Seven 2.42 using the installation CD Follow prompts and use defaults When prompted for the SQL password, select "Windows Authentication" Restart the PC Open I/NET Configuration through the start menu. Modify the default Config profile or create a new profile. Close I/NET Configuration Start I/NET Activate any Vista Licensing Start Vista Server Start Vista Workstation

Issue Older I/A Series G3 stations will not connect to an Enterprise Server that has been upgraded to a release with the 2013 security updates.  Versions with the 2013 security updates include: 3.7.106 (AX-3.7u1) 3.6.406 (AX-3.6u4) 3.5.406 (AX-3.5u4) 3.8.37 (AX-3.8) Niagara Network Fox Connections State remains "Not Connected" and the Last Failure Cause indicates ...        com.tridium.fox.session.InvalidCommandException: Expecting 'challenge', not 'rejected' Environment I/A Series G3, Enterprise Server, ENC, SoftJace Cause To increase system security, the update releases significantly modified how I/A Series G3 station password storage is maintained.  Any system with an I/A Series G3 Enterprise Server that transitions to an update release for the first time has a few extra steps involving the Enterprise Server station. Schneider Electric strongly recommends reviewing your security situation and upgrading the latest I/A Series G3 software with updated security measures. Resolution The following is an excerpt from the NiagaraAX 2013 Security Update document included in the docs folder for each of the 2013 security update builds.  The steps detail how to modify the Legacy Authentication setting to relax security for stations operating at previous builds. Setting Legacy Authentication within the Fox Service: In Workbench, open the running Supervisor station (Fox connection). In the Supervisor station, open the property sheet of its NiagaraNetwork - Config > Drivers > NiagaraNetwork. Expand the FoxService and look for a new property Legacy Authentication. Change Legacy Authentication from the default “Strict” to “Relaxed Until” (shown below) and then Save.  For further details, see “Fox Service properties” in the NiagaraAX Drivers Guide. This should be a temporary setting only. Reset this to “Strict” in the Enterprise Server’s FoxService after you complete upgrading I/A Series G3 in the subordinate ENC/JACE hosts (represented in the Enterprise Server’s NiagaraNetwork).  Relaxed authentication in the Enterprise Server’s FoxService allows its subordinate ENC/JACEs to continue to communicate with the Enterprise Server until they have been upgraded.  This is necessary to continue operations like remote alarming, archiving histories, and so on. However, you should NOT leave the Enterprise Server in this state, as this negates much security (see Caution). Caution:  Unless set to “Strict”, either “Relaxed” option is effectively the same as setting the FoxService property Authentication Policy to “Basic”, as this is the only “common ground” authentication between a legacy Fox client (Workbench or another station) and this update release station. Thus, passwords for client connections to this station are passed in clear text. Obviously, this is not a desired operating state.  For this reason, you should seldom (if ever) set the Legacy Authentication property to “Always Relaxed”.

Issue A Door configured with Magstrike status as Door Status re-locks after 2s  even when Door Strike Time is set to 10s. Environment Continuum Access Control Cause The Door output will relock after the Door Strike Time or when the Door is opened. Since you are using the mag lock status as the Door status (not the preferred method), then as soon as the Door is unlocked, the mag lock is de-energized which turns off the Door Status which then relocks the Door 1s later. Resolution You need to monitor the actual physical status of the Door to indicate when it has physically opened and shut. Either that or remove the input from the Door object by setting the Door Status channel to 0. This should allow the Door to stay open the DoorStrikeTime. You can also use a PE program to get around not having a DoorStatus that monitors the actual Door. This post on the Community discusses this and has some good comments about using this type of Door control with the maglock status instead of a true Door Status switch and is worth a read. Below is an example Plain English program that can help monitor the Door for ValidAccess then hold the Door unlocked for the DoorStrikeTime. 1: If Door1 ValidAccess is On then Goto 2 If Door1 ExitRequest is On then Goto 2 2: Door1 = UnLocked If TS > Door1 DoorStrikeTime then Goto 3 ' wait for DoorStrikeTime 3: Door1 = Locked Goto 1

Issue When attempting LonWorks communications in WorkPlace Tech, the following error message is seen. "Failed to get communications type, using LonWorks as default" Environment WorkPlace Tech 5.7.x Echelon U10 USB LON Network Interface (part number ECH-75010) – TP/FT-10 Channel Cause WorkPlace Tech LonWorks communications is not properly initialised.   Resolution Re-initialise WorkPlace Tech LonWorks communications. In WorkPlace Tech, go to 'Tools' > 'Configure Communication'. Change the communications type to 'BACnet' and click 'OK'. Open up 'Configure Communication' again and change the communications type back to 'LonWorks'. This should re-initialise the LonWorks communications.

Issue What configuration is required for a Multical BACnet heat meter Environment Schneider Electric (Kamstrup) heat meter connected to a Continuum or SmartStruxure system on MS/TP. Multical 61/62/601/602/801 Cause Setup information required Resolution With the BACnet interface card fitted in the Multical meter it is a native BACnet MS/TP device. Connect it to the AS or bCX1 depending on your system and Learn/ find BACnet devices. It should appear online and allow the objects to be uploaded. A typical unit like the Multical 602 will contain 12 Analog Inputs for all of the information from the meter. The Meter will operate at 9600, 19200, 38400, 57600 and 76800 Baud rates and autobaud to the connected system. For the Datasheet  Click Here. For the BACnet PICs statement Click Here. For help with Heat meter selection see the online selection tool: Online Heat Meter Selection Tool - PA-00216

Issue Network 8000 Ethernet networks experiencing the following symptoms should be upgraded: GCM panels reporting repeated off-line / on-line messages NIM lock-ups requiring power cycling to recover Loss of global data sharing with Network 8000 (RNET and SNET transmissions fail) Product Line TAC IA Series Environment Network 8000 GCM Ethernet NIM, part number GCM-ETH-001 Network 8000 GCM-86000 Series controller (GCM-86120, GCM-86110, LNC-100, SIM-CCN, SIM-MTECH, SIM-YORK, SIM-TRANE) 802.3U Ethernet (100 Mbps) or 802.3z gigabit Ethernet (1000 Mbps) backbone network Cause Ethernet NIM performance was enhanced in revision 11.2T. Resolution Upgrade all NIMs on the network to firmware revision 11.2T, with the single exception of any with revision 11.2P firmware. Click here to see Announcement 01-105 for more details. For details on the REVISED Flash clear procedure, see the NIM Networking and Configuration Guide, F-25955-4, Chapter 2, section titled "Special NIM Address Switch Functions". Click here to see the procedure. Please reference Verifying the current firmware revision of a Network 8000 GCM and if an upgrade kit is available regarding Network 8000 firmware, including current revisions and upgrade kit part numbers.

Issue When swiping card, the access is denied. The message shown in AMT is "Bad Card Read". Environment I/NET Cause There may be two causes for this message: The tenant code isn't correct when using Wiegand 26 format in the door parameter. The digit of card number exceeds the setting in the setting of card reader type. For example, the card format is Wiegand 35, but in the door parameter, the card reader length is set to 36 digits. Resolution For cause 1, enter the correct tenant code in the Tenant Editor. For cause 2, set the correct card reader type and digit.

Issue Xenta 102-AX version 2.19 included 6 major updates and changes. They are outlined below. Product Line TAC Vista Environment Vista Xenta 102-AX Cause M/STAT Air Flow Calibration Errors Error Description: When calibrating a Xenta 102-AX using the M/STAT a Velocity Pressure Offset is not generated in circumstances where one would be generated in the 102-AX Plug-in. This adversely affects the accuracy of the calibration, in particular at the low flow setting. Note: All steps for calibration using the M/STAT are found in Calibrating Airflow on a Xenta 102-AX (or MR-VAV-AX) using the M/STAT. Workaround: Perform the calibration using the LNS 102-AX plug-in tool or the TMGL plug-in tool Xenta 102-AX does not perform wink function properly Error Description: Attempts to perform the wink function fail. When a wink function is performed, the red light on the controller is expected to come on and flash to identify the controller and the STR-250 should display "00" with the man logo displayed as well. This should last approximately 45 seconds. STR-250 connected to the Xenta 102-AX is not controlling the fan properly Error Description: The STR-250, stat when connected to the Xenta 102-AX, reacts incorrectly to buttons being pressed when in the fan menu. The increase button causes a decrease and the decrease button causes an increase among other odd behaviors. Also, if the fan is set to shut off (this action should not be allowed) the Xenta 102-AX performs a resynchronization. Pressure dependent mode erroneously requires airflow and fan enabled Error Description: The 102AX requires 80% Airflow Setpoint to run Heat1 in Pressure Dependent mode. Xenta 102-AX Hot Water floating control resynch fails Error Description:  When the Xenta 102AX does a hot water floating control valve resynch based on being in the 10-90% "happy" zone for 60 seconds and then goes to 100% it does not resynch at the 100% open position for the full stroke time. It gets to 100% commands the resynch, then closes the valve, re-opens the valve to 100% then allows the valve to control back to a normal position. Xenta 102-AX Floating Hot Water valve control failures Error Description:  Heating outputs stop working on Xenta 102-AX sporadically causing hot water valve to open even though application is calling for it to be closed. This occurs when the 102-AX is set up for a floating valve actuator (PWM 2) and occurs sometimes within a day but could take a few of days to show up. The resynchronization of the valve seems to have no effect and the only way to fix the controller is to cycle power or by switching nviEmergCmd to something other than its default and then back again a moment later. Resolution If any of these errors are occurring, upgrade the Xenta 102-AX to version 2.1.9 or higher. Click here to download the APB file. Complete upgrade instructions can be found at Upgrading a Xenta 102-AX to version 2.16 or later Version 2.19 addresses the problems listed above as follows: M/STAT Air Flow Calibration Errors Fix: When calibrating a Xenta 102-AX using the M/STAT a Velocity Pressure Offset is now properly generated. Xenta 102-AX does not perform wink function properly Fix: After clicking Wink the a red LED on the controller flashes to identify the controller and the STR-250 displays "00" and the man icon. After approximately 45 seconds both the controller and the STR-250 return to normal. STR-250 connected to the Xenta 102-AX is not controlling the fan properly| Fix: The ability of the STR-250 to override the fan command on the 102-AX is disabled by default. If this functionality is required it can be turned on by setting DamperActuator.SCPTdirection.bit15 to 1. Pressure dependent mode erroneously requires airflow and fan enabled Fix: The 102AX no longer requires 80% Airflow Setpoint to run Heat1 in Pressure Dependent mode. Xenta 102-AX Hot Water floating control resynch fails Fix:  Logic has been corrected to only resynch open or resynch closed as needed. Additionally, the heating output resynchronization algorithm has changed to operate as follows: Two internal timers have been added to track the accumulated amount of time that heat load is 0% and at 100%. Once either of these timers reaches 30 minutes, a resynch is initiated in the respective direction of the timer. The resynch consists of activating either the open or close triac output for an amount of time equal to the user defined stroke time. Xenta 102-AX Floating Hot Water valve control failures Fix:  Heating output logic corrected to prevent failure.

Issue ES Database has grown to several gigabyte Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Enterprise Central Cause ES Database size can grow quite large when the ES crashes often. Open Software Administrator and find the location of the ES db folder. Below are two screen shots of the Logs and Crash Information folders. As can be seen, these dump files can increase the size of the database. Resolution Once the reason for the Enterprise Server crash is resolved, these files can be either be deleted or, preferably be moved to another storage/drive location. If the ES/EC is still crashing, all the core dumps should be collected and sent to to your local support team for processing. Due to the size of the crash dumps, upload to BOX or similar and provide the link to the support team.

Issue How to sound a buzzer when a Request To Exit (REX) button is pressed on a Continuum Access system? The inputs to a door are not defined as regular Infinity inputs so how can they be programmed by Plain English programming? Environment ACX57xx (ACX5740, ACX5720) and AC-1 IOU modules (AC-1, AC-1A, AC-1 Plus) Cause When engineering an access control project, there is sometimes the requirement to sound a buzzer or turn on a light when the door is unlocked, or when a Request To Exit button is pressed, as the input points used within the door object configuration are not defined as a regular Infinity Inputs, so how to achieve this functionality? Resolution To use a Request To Exit (REX) switch on any of the ACX controllers or AC1 Modules:  It has to be a supervised input wired with the appropriate resistors in one of the 6 standard configurations defined in the installation guides (All available on the Extranet). You can not use a simple digital input switch without resistors. Incorrect circuitry or missing resistors will result in a Trouble indication on the door. The REX input is not a regular Continuum input point as it is defined within the door configuration, as it is not a Infinity input point directly accessible from Plain English but can be read via the "ExitRequest" attribute of the door. To sound a buzzer from the from the door there are 3 options: Use the existing door output and slave a buzzer circuit from the output that drives the Magnetic lock, so will sound when the door unlocks. If you want the buzzer to sound when the REX button is pressed then use a button with a 2 pole switch (2 separate contacts): Wire one to the REX input with appropriate resistors. Wire the other switch to a spare Input Configure it as either a Digital input or a Supervised input with resistors. This point can be used in your PE programming to drive the buzzer output. The third option is to use a Plain English program to read the "ExitRequest" attribute of the door and turn on an output for a defined time. The ExitRequest attribute may only be on for a short period of time so the program must be constantly looking for this attribute to change as well as keeping the controller Scan time low.  

Issue Offline alarms received from Continuum controllers every few minutes and log error 0x00006c0e Broadcast Storm AKA Error transmitting and/or 0x00006c03 Driver fatal error during operation. Product Line Andover Continuum Environment Continuum Net Controller II Continuum ACX 4 Controller Continuum CX Gen 1 Continuum bCX4040 Continuum bCX9640 Continuum BCX4000 Cause Excessive ARPs and/or other broadcast traffic on the network. Resolution When troubleshooting controller offline issues that are suspected to have excessive broadcast traffic as the root cause it is important to understand how to interpret Wireshark capture to determine whether too much broadcast on the VLAN  is indeed the problem. Note that taking the percentage of broadcast traffic in a Wireshark capture while a good starting point cannot in itself be solely used as proof that excessive broadcast is indeed the root cause of the controllers going offline, this is because in the absence of much unicast traffic the broadcast traffic will make up most of the packets resulting in a misleading high percentage. A much better way to determine whether the controller maybe going offline due to excessive broadcasts is to look at the average broadcast packets per second over a 15-20-minute capture. The screen capture below shows the statistics from a 20 minute capture filtered by broadcast traffic (eth.dst == ff:ff:ff:ff:ff:ff)  The capture shows that about 63% of the traffic is made up of broadcast at an average of 24 packets per second. The Continuum controllers on the network were going offline multiple times an hour. Note that the Continuum controllers are initially able to handle a much higher rate of broadcast traffic, tests performed in the PSS lab show a CX9680 can handled about 10 times  the amount shown here sustained for 5-10 minutes but over a much longer period of time such as several days or weeks the amount of broadcast traffic shown was enough to cause the controllers  to go offline. The screen capture below shows the statistics after the root cause of the excessive broadcast was identified and fixed. The problem at the site in question here was a defect in the network switch that was making the switch duplicate ARP traffic. Note that Cisco switch model Catalyst 4500 is also effected by the firmware bug. Current version which fixed the issue: Catalyst 4500 L3 Switch  Software (cat4500e-UNIVERSALK9-M), Version 03.08.05.E RELEASE SOFTWARE (fc2)   Previous version which caused the broadcast problems: Catalyst 4500 L3 Switch  Software (cat4500e-UNIVERSALK9-M), Version 03.08.02.E RELEASE SOFTWARE (fc2)

Issue Actuator M44 is no longer available (withdrawn in 2000) and needs a replacement. Environment M44 M9B EM9 Forta Cause Depending on application, since the M44 was used for both rotating and sliding valves, a few different replacement actuators could be used. Resolution For valves with rotating stem, (TRV, VTRA, VTRE and STMG), actuators M9/EM9 can be used. For valves with linear moving stems the TAC Forta series actuator is used.

Issue The Extended Trend Logs stop updating in Enterprise Server.  When the ES is rebooted the trend logs resume. Product Line EcoStruxure Building Operation Environment Enterprise Server Cause The Extended Logs Maximum transfer interval is set too low causing it to trigger again before it has managed to finish the last read. Resolution Increase the Maximum transfer interval setting of the Extended Log.

Issue TAC Vista and Peripheral Software Installation Outline Product Line TAC Vista Environment Microsoft Windows 2000/XP (Microsoft) LonMaker (Echelon) Microsoft Visio PCLTA-10/PCC-10/PCLTA-20/SLTA-10/PCNSI Adobe Acrobat  LNS  lmw31.exe lmw313U1.exe LNS3SP8.EXE LNSSP8U1.EXE HASP device driver h4_hinstall hdd32.exe Privilege Licenser 2.01 Aladdin Privilege Administrator 2.01 taclicense201.exe taclicense202.exe .NET Framework 1.1 TACVistaConfig1.2.0 .NET Framework 1.1 SP1 Microsoft SQL Server (MSDE)2000 SP4 MSXML 4.0 MDAC 2.8 Vista Server IV WorkStation TAC ToolPack 4.X   Cause The correct installation procedure for Vista IV and necessary peripheral software. Resolution Below is an outline that can be followed to install Vista in the proper order. Each "*" denotes a software package followed by the associated files/programs that are included. Depending on your specific application, some of the software may not be needed. For example, a Vista Classic network will not need LonMaker. Call Tech Support if you have any questions concerning the software needed for your application. *Microsoft Windows 2000/XP (Microsoft) *LonMaker (Echelon CD) LNS Utilities: Microsoft Visio, PCLTA-10/PCC-10/PCLTA-20/SLTA-10/PCNSI (only if using an Echelon LNS interface), Adobe Acrobat (if you don't already have it) *Update LonMaker to 3.13 and LNS to 3.08.05 (TAC Extranet) lmw31.exe, lmw313U1.exe, LNS3SP8.EXE, LNSSP8U1.EXE *HASP device driver utility (TAC Extranet) h4_hinstall - MUST Execute from a Command Prompt! or... hdd32.exe if using Windows Server 2003 *Privilege Licenser 2.01 - "taclicense201.exe" or 2.02 - "Privilege Windows XP crash hotfix" (TAC Extranet) *.NET Framework 1.1 (Microsoft) *TACVistaConfig1.2.0 (TAC Extranet) .NET Framework 1.1 SP1, Microsoft SQL Server (MSDE)2000 SP4, MSXML 4.0, MDAC 2.8 (Reboot) At this point you could be prompted to choose which type of Licensing to be used. Select which option is best for you, the Site License (Order Entry Department), 30 Day Demo (TAC Extranet), or Engineering dongle. This will write the appropriate license files to the Privilege License Server. *Vista Server 4.X with WorkStation (TAC Extranet) (Reboot) *TAC ToolPack 4.X (TAC Extranet) If you encounter any errors during the installation process, be sure to make a note of specific errors received so Technical Support can better troubleshoot your issue. A simple way to record errors are to capture a "screenshot" (Ctrl+PrintScnr). The screenshot can then be pasted (Ctrl+V) into Paint a text editor like wordpad for later reference. Note: Beginning 2012, PSS will no longer support the Privilege License System. The Tamfs26 Server will be retired along with TAC License Server software. It would be wise to inform the customer of this important information to plan for future upgrade in the event that their site license has issues.

Issue When a modbus AO is created and set to 32-bit real swapped, the correct value is not seen at the modbus device. 1000 is written and 1000 is shown correctly at the Modbus device. 1001, 1002, 1003 are written but 1000 is seen at the Modbus device. 1004 is written and 1004 shows correctly at the Modbus device. And so forth. The larger the number, the larger the error increase. Product Line EcoStruxure Building Operation Environment Enterprise Server (ES) Automation Server (AS) Cause When 32 bit real swapped is selected Further down the configuration page, the write function code defaults to "06". 06 is to set a single 16-bit register write and this needs to be changed. Resolution Use the drop down tab and set the function code to "16". 16 is to preset multiple registers i.e. 2 off consecutive 16-bit registers or a 32-bit register.

Issue Transferring an I/NET Seven system from one PC to another Product Line TAC I/NET  Environment I/NET Seven Site Cause Customer needs to transfer I/NET between two computers Resolution Perform the following steps: Install I/NET Seven on the new PC. Using DBCreate.exe, create a backup of the I/NET database. Copy the backup to the new PC and restore it using DBCreate. If the database needs to be upgraded it will prompt you.  Proceed with the upgrade.  Copy the save files, graphic pages, archives, any custom reports, custom symbols, and custom BIN files (ICI bin files) to the new PC using the same directory path as the previous PC to guarantee that graphic links will still work. The following are default paths for these files assuming it was not an upgrade from I/NET 2000. If it was an upgrade from I/NET 2000 please consult TCON298 the Getting Started guide which includes I/NET 2000 paths. Default location for Archives: C:\Program Files\INET Seven\Arch\ Default location for BIN Files: C:\Program Files\INET Seven\Data\ Default location for Reports: C:\Program Files\INET Seven\Reports\ Default location for Save Files: C:\Program Files\INET Seven\Sav\ Default location for Bin Files: C:\Program Files\INET Seven\Data\ Default location for Graphics: C:\Program Files\INET Seven\ Take a screen capture or write down the active configuration profile in I/NET configuration and manually fill this information into I/NET configuration on the new PC and make it the active configuration profile. Transfer the communication medium to the new PC (serial cable or Ethernet cable) and if communicating via NPR’s set the IP address of the new PC to match that of the old PC and remove the old PC from the network to avoid IP address conflict. Start up I/NET, login, and edit the Host Computer->Network Configuration to verify that the PC is communicating with the controllers.

Issue How can I control a dual duct VAV box with Xenta controllers? Environment Xenta 102-AX Dual Duct heating/cooling Cause The Xenta 102-AX is an application specific controller designed to vary the volume and outlet temperature of a single terminal unit. It does not, by default, control a dual duct, where a constant source of cold air and hot air and delivered in separate ducts. Resolution You could conceivably use a single Xenta 102-AX with the airflow pickup on the discharge of the box instead of the inlet. Then connect the hot deck damper as a 2-out PWM heat stage. A more elegant solution is to use a pair of Xenta 102-AX controllers. One 102-AX is connected to the cool deck and setup normally. Either its heating airflow setpoint is set to match the cooling low flow or heating airflow is set to 0 if you wish the cool deck to shut off in heat. The "Effective Setpoint Source" must be set to "Norm of Heating and Cooling Setpoints" so that the setpoint sent to the hot deck controller will not bounce from heating to cooling when room conditions change. For this reason, it might be preferable to use an STR-202 so that there is no digital display to confuse the occupant. The second 102-AX is connected to the hot deck, space temp is bound from the first and nvoeffectivesp is bound from the first to nvisetpoint of the second. Configure input 1 as a duct temp and connect a 4.7Kohm resistor from it to ground. This will simulate a duct temp of 110°F and keep it in warmup mode. As with the cool deck, you have a choice whether to set the warmup low flow to 0 or to some minimum position. Set your occupied setpoints to the same values as the cool deck controller. (It's actually using them in the setpoint calculation, but for simplicity's sake, set them the same. For a more complete description, consult the reference manual concerning nviSetpoint.) You should also bind nvoOccupancyStatus from the cool box to nviOccCmd on the hot deck box. That way if someone puts the box in to after hours override, they'll both operate. As mentioned before, the room sensor (STR-200/202/250) is connected to the cooldeck controller. You'll need to connect 3 conductors to a 1/8"TRS jack to the hotdeck controller in order to connect the MSTAT for calibration purposes. Otherwise you'll have to crawl into the ceiling to connect it. This arrangement is based on having airflow sensors on the inlets of both the cold and hot deck.

Issue In WorkPlace Tech Tool, the Definition tab of a Custom Object, right click on any object to request Properties info. The response is an error "Exception happened finding Visio shape". What does this mean? Environment WorkPlace Tech Tool 5.7.x Cause There was an error in Visio. The custom object may have been copied from a newer version of Visio to an older version. There may have been an error when creating the custom object. Shapes may have been added to the custom object when opened directly in Visio instead of being opened in WPTech. Some other corruption to the drawing took place. Resolution Do a “Rebuild Application”, and then try opening the shape properties again.  If this does not work, try creating a new custom object, and then try copying the contents of the old custom object definition page into the new custom object definition page (while in WPTech).  Then delete the old custom object, and then try the shape properties in the newly created custom object.