Building Automation Knowledge Base

Issue I/NET Anti-Passback (APB) rules. Product Line TAC INET Environment I/NET Cause Assistance with setting up Anti-Passback (APB). Resolution Note: Use of the Anti-passback option described below requires that a DPU have both an entry reader and an exit reader. An elevator DPU will support only an entry reader, and therefore, will not support anti-passback. Activate or deactivate the Anti-passback option. This option is not available if you have activated the Elevator option described in the previous step. Activate the Anti-passback option to prevent persons who have successfully gained access into an access-controlled area from passing their key/card back to another person desiring access. Refer to Implementing Anti-passback for more information. Note: The actual system response for both anti-passback and anti-tailgate (below) is controlled by the anti-passback scheme selected for the individual (see Individuals Parameter Editing). Activate or deactivate the Anti-tailgate option. This option is only available if you have activated the Anti-passback option described in the previous step. Activate the Anti-tailgate option to discourage users from following another person through an access-controlled door without reading their own keys/cards for access. Refer to Implementing Anti-tailgate for more information. If you activated the Anti-passback option in the previous step, the Entry Zone and Exit Zone parameters will become enabled. The valid range is 0–64. Enter an Entry Zone number. This is the number of the zone where the entry reader is located. Refer to Implementing Anti-passback for more information about entry and exit zones. Enter an Exit Zone number (0–63). This is the number of the zone where the exit reader is located. Leave this field blank if there is no exit reader. Refer to Implementing Anti-passback for more information about entry and exit zones. Note: If the Anti-tailgate option is enabled, any door between the secured area and the non-secured area must have the same zone number for both exit and entry. The non-secured area is any region not under access control, such as a lobby, public area, or the outdoors. Set the Anti-passback Reset Time (0 to 60 minutes). Any value higher than zero (default) will cause the anti-passback flag to be reset for each individual the specified number of minutes after the individual passes through the door. If an "APB Reset" action has been defined in the mode schedule of this door point, it will still be honored (i.e., the individual's anti-passback flag may be reset by the APB Reset action before the time specified in this field has expired). If you leave this parameter at the default value of zero, no timed reset of the anti-passback flag will occur. In this case, only an APB Reset action defined in the door's mode schedule will reset the anti-passback flag. Refer to Resetting the Anti-Passback Flag for more information. The purpose of the anti-passback function is to prevent persons who have successfully gained access into an access-controlled area from passing their key/card back to another person desiring access. Activate anti-passback for a particular door in the Door Extension editor. The system response depends on the anti-passback scheme selected in the Individual Parameters editor. The options are as follows: Hard (default) — access is denied, generates an alarm. Soft — access is granted, generates an alarm. Graced — access is granted, no alarm is generated. This effectively cancels anti-passback for the individual. Although the Anti-passback parameter (activated from the Door Extension editor) is used to enable anti-passback, implementing anti-passback also requires that you define access control zones (refer to Entry and Exit Zones, below). Note: Anti-passback requires that a DPU have both an entry reader and an exit reader. An elevator DPU will support only an entry reader, and therefore, will not support anti-passback. If you wish to have a more stringent control, you may also implement anti-tailgating.   Entry and Exit Zones Depending on the version of host software loaded on your workstation, I/NET supports either 32 or 64 zones (assigned from the Door Extension Editor). When anti-passback is enabled, the system will allow a user to be in only one zone at a time. When a user moves between zones (e.g., uses a key/card at an entry or exit reader), the system generates a zone exit message followed by a zone entry message, and broadcasts these messages to the other readers in the system. A user may enter a zone, but must use their key/card to exit the zone. If they do not (i.e., they leave a zone when another person uses their key/card), then I/NET will not allow them to re-enter any other zone using their key/card. Zones Example:   Zone Numbering Rules When populating the door editor, enter the zone number where the reader is physically located. Entry readers should be located on the exterior of a controlled zone. Exit readers should be located on the interior of a controlled zone. Exterior doors, in access control terms, are doors that lead from a non-controlled area into an access controlled area. These doors are not necessarily on the exterior of the building. The entry reader at an exterior door is physically located in an area that has no zone number (i.e., a non-controlled area). The zone number assigned to the entry reader of an exterior door should match the zone number assigned to the exit reader of that door. The example above shows a facility with three anti-passback zones that share doors. Using the example, the door leading from zone 1 to zone 3 has an entry reader physically located in zone 1. The zone number assigned to the entry reader is 1, even though this reader is used to gain access into zone 3. This door also has an exit reader that is physically located in zone 3. The zone number assigned to the exit reader is, therefore, 3. Each exterior door shown in the example has entry reader and exit reader zone numbers that match. This causes I/NET to generate only one zone entry or exit message after a valid read at an exterior door. This also makes it unnecessary to use a zone number for the exterior (non-controlled) area of the building.   The following two types of anti-passback are available: Soft anti-passback — The anti-passback flag is set when a key/card is successfully read, and a door sense switch is activated. This would occur when the door is opened. Hard anti-passback — The anti-passback flag is set when a key/card is successfully read at the entry reader. In this case, the anti-passback flag would be set even if the door were never opened. If anti-passback is enabled, hard or soft anti-passback is automatically selected by I/NET. The system looks at the Door Sense Switch parameter setting (this parameter is available from the Door Extension Editor). If a sense switch is defined (normally-open or normally-closed), the system uses soft anti-passback. If no sense switch is defined, the system uses hard anti-passback. Although the Anti-passback Type parameter (available from the Door Extension Editor) is used to enable anti-passback, implementing anti-passback requires that you define access control zones (refer to Entry and Exit Zones, below). Note: Anti-passback requires that a DPU have both an entry reader and an exit reader. An elevator DPU will support only an entry reader, and therefore, will not support anti-passback.   Additional Clarification: Anti-passback can be very complicated or simple depending on the site. Hopefully after looking at these documents, and reading this example, explains what the site setup could be. Let’s assume each door has an entrance and exit reader. This is required for anti-passback. Let’s also assume that all the readers are on the same Link (NPR). This is required for anti-passback. This example is a hallway with 32 rooms such as a hospital or school. Let’s set the hallway up as zone 1. Scenario 1: If you want the 32 rooms to have the same zone, set them all up as zone 2. This will allow the individuals to pass into any of the 32 rooms. Room 2 – Zone 2 Room 3 – Zone 2 Room 4 – Zone 2 and so on. Scenario 2: If you want to keep the individual(s) specific to their room and not all 32 rooms, you want to have different zones for each of the 32 rooms. Room 2 – Zone 2 Room 3 – Zone 3 Room 4 – Zone 4 and so on. There are other considerations, if the rooms have access to each other without scanning back into the hallway (zone 1). If there are exterior door from the hallway, it also would be zone 1.

Issue IT departments want to install just the client software without attaching to the webclient server and want to know if there is a way to accomplish this. Product Line Andover Continuum Environment webClient Windows XP Windows Vista Windows 7 Windows Server 2003 Windows Server 2008 Cause Webclient deploys activex controls using several .cab file from the C:\program files\redist folder on the webclient server. These files must be delivered to the browser PCs with admin privileges on the client PC in order for webclient and webpinpoint to work. Here is a list of the .cab files and ActiveX controls that get installed AccWebUtils.cab - AccDotNetBootstrap Control, Crypto Class (Used for  regular webclient use) WebclientPinpointSetup.cab - PPBrowserMgr Control (WebPinpoint) WebclientVideo.cab - TACVideoControl.VideoControl (Viewing Video layouts) ** The other piece that doesn't get installed are the permissions for the caspol commands that must be set for zones in order to run schedules. See webClient schedules getting error 'request for permission of type' system.security.permissions or .net control error on Webclient reports related to webclient schedules and running the caspol commands 1.94 SP1 requires that Microsoft VC++ 2005 Redistributable SP1 x86 to be installed for webpinpoint, it prompts to install when accessing a graphic the first time Resolution There is no client side webClient PC installation. The method for delivering the necessary activex controls and files are triggered by the browser PCs access to the webclient server PC and then the files are delivered to the client.  Some IT departments use Microsoft  SMS or Active directory to deploy software in a locked down environment. To deploy webclient to these types of browser PCs, they would have to logon with Admin privileges to perform the one time install of these files. The only other method if the IT group has InstallShield or WISE package creation software would be to capture the browser PC installation and use the produced .msi file for client delivery. This is informational only and has not been tested by Schneider Electric.

Issue How to set up a Operator Panel to only see the TAC Xenta controller it is plugged into Product line EcoStruxure Building Operation Environment TAC Xenta Operator Panel firmware 3.7 TAC Xenta Programmable controller 3.85 or higher Cause When the Operator Panel is plugged into a TAC Xenta programmable controller the whole network of TAC Xenta controllers are listed. Resolution This option and the requirements are described in this TPA To enable the option in the TAC Xenta: How to enable this in the TAC Xenta: Edit the application and create a Public PVI-block with the name XENTASYSREG and set this block’s initial value to 8. If you have multiple TAC Xenta OP panels in the network, each one connected to a specific TAC Xenta Controller, it will be required to create this special PVI block in every one of these TAC Xenta Controller’s application code.   To enable the option in the OP Panel: 1. Open the TAC Xenta OP local service menu, by pressing and holding the “escape” and “enter” buttons for a few seconds. 2. Enter the bottom command: “11 OP connects to”. 3. Enter this sub-command, and then type in, using “+” or “-“, the specific TAC Xenta controller’s subnet and node address you want this OP to be “locked” to. The TAC Xenta controller subnet and node addresses can easily be found in TAC Vista Workstation; select “properties” for the TAC Xenta controller and the subnet/node address will be displayed. Observe that when you select, in the OP panel’s new menu, the node number and press enter the TAC Xenta OP will restart and seek for this now selected TAC Xenta controller. Note that it is still possible to access this specific TAC Xenta controller from another TAC Xenta OP in the network if that TAC Xenta OP is of a version prior to 3.70 or this new “lock-function” is not enabled in that TAC Xenta OP. However doing this, you will only here also “see the local TAC Xenta controller”. In this case you will be able to exit this TAC Xenta controller again by pressing “escape”. While in the locked TAC Xenta OP you will not be able to exit from the TAC Xenta controller it is locked to.

Issue There is a need to know which versions of Digital Sentry was tested with version 1.94 Environment Continuum Windows XP Windows 7 Windows Server 2003 Windows Server 2008 Cause Certain versions of Digital Sentry may or may not be supported in some versions of Continuum. Resolution Digital Sentry versions 7.2.xx and 7.3.54 were tested with Continuum 1.94

Issue When Forcing a value from SBO, it is just overwritten by the Lua script all the time. Product Line EcoStruxure Building Expert Environment MPM SE8000 Cause By default, the MPM executes the program once every second, so if written simply like: Output_1 = Off the output will be turned Off every second. Resolution Declare a few variables in the Lua script that will help you implement the logic you need, here is an example: var("Override_Status","ME.BV1") var("Override_Value","ME.BV2") if changed.Override_Status and Override_Status == 1 then ME.BO1 = Override_Value elseif changed.Override_Status and Override_Status == 0 then ME.BO1 = ME.BI1 end Basically, an override status points will act as a "Override button", and when it is active, The output will be equal to override value specified in SBO. Else, if it is disabled, the output will be set to what ever you currently have in your script. In the example above, the output will be equal to the input.

Issue Poor communications, communications failure or packet being corrupted Product Line Andover Continuum,EcoStruxure Building Expert,EcoStruxure Building Operation,Satchwell MicroNet,Satchwell Sigma,TAC INET,TAC Vista Environment Communications networks, BACnet MSTP, LON FT10, Infinet, Modbus RTU, Ethernet EMC (Electromagnetic compatibility) VSD Variable Speed Drive, VFD Variable Frequency Drive, Inverter Drive Cause Electrical Interference from Inverter (variable speed drives or VSD) Radiated or Induced RFI (Radio Frequency Interference) Resolution A VSD has the potential to create a large amount of electrical noise, to avoid causing issues it is vital they are installed as the manufacturer's instructions.  (Other devices also have this potential) Our systems are often used to control VSDs on fan motors, so if poor communications is found during the commissioning process, then try stopping all the fans in the area then re-testing the communications. A recent example was seen where LON FT10 communication was working ok until some VSDs were started, at this point LON devices and Object went offline intermittently. When all the VSDs were stopped the communication become completely stable. It was then possible to find which VSD was causing the problem and correct the VSD installation. In this case a LON analyzer would also have helped diagnose the issue.

Issue Access Denied NO access at the door Product Line Access Expert Environment Win Server 2012 R2 and above Cause 1) The cardholder does not have sufficient Access Levels assigned. 2) The Max access levels has been reached by the intelligent controller. 3) The access levels were not successfully downloaded to the controller. Resolution To resolve this, the following steps need to be followed: 1. Ensure that the access levels contains a door group which consists of the trouble reader. 2. Check that the person has the correct access level assignment, 3. Try saving the access level again so that it is pushed to the controller. 4. If possible, issue a reboot command to the intelligent device to ensure database synchronization. OR if the system database limit on access levels has been reached, take the following steps. Verify the user has permissions on the Role Go to the General Configuration Select System Settings Select the Hardware Tab on the bottom Change the Max Access Level to a higher level than the default (100). Save and Reboot the controller for the changes to take effect

Issue If a Xenta 913 with SNVT(s) is added as a Lon device to an Automation Server Lonworks network the commission process fails in the last step with error 0 Product Line EcoStruxure Building Operation Environment Building Operation Automation Server TAC Xenta 913 TAC Xenta 700 Cause This is a bug in the Xenta Server firmware. Resolution This issue will be fixed in Xenta 913 firmware version 5.1.9, however  hotfixes have been made for 5.1.8 and can be requested from PSS (TACXenta913-5.1.8.15 and TACXenta700-5.1.8.47). Note: All data will be lost in the Xenta Server when applying the hotfix.

Issue Self-Registration Error while installing Remote Workstation (some of the "dll" files are not installed). The following files did not self-register or unregister. Environment TAC Vista 5.0.X Remote Workstation Cause When uninstalling the TAC Vista Remote Workstation some of the "dll" files will not un-install from "TAC Shared" folder (Find the TAC Shared folder in "C:\Program Files\Common Files). Due to this, while reinstalling the Remote Workstation pop-up an error-"Self-Registration" and few "dll" cannot install, then the Installation terminates. Resolution Uninstall the Remote Workstation. Delete the TAC Shared folder from C:\Program Files\Common Files Reinstall Remote Workstation. Note: Install .NET Framework 2.0 before installing the Remote Workstation software.

Issue There's a need for information on the Personnel Import Utility Product Line Andover Continuum Environment Continuum Windows XP Windows 7 Windows Server 2003 Windows Server 2008 Cause Finding the information on the Personnel Import Utility may be difficult to locate. Resolution The information for the Personnel Import Utility can be found in the latter part of Chapter 19 on Personnel. There is additional information in Appendix C related to the tables and XSLT file. Click here to download a copy of just the PIU Manual.

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 Not possible to see live values in a Xenta 700 Menta program from web interface or TAC Vista Can't see Menta online values in Xenta Server Control Applications graphical view The Menta application displays fine, but it's not possible to see the live values (true/false et c) Product Line TAC Vista Environment Xenta 731 Xenta 711 Xenta 721 Xenta 701 Xbuilder Menta Cause This is an uncommon error and the cause is not known, however it may occur when copying a HFB block within or between X700 Menta applications. Resolution In the Xbuilder projects folder, find the file [project name]\TargetImage\configdb\menta\mentablocks.xml and open it in Internet Explorer. Search for Menta blocks that have CodIndex='0' and note (copy) the GUID of those (for example 3C02F735-E375-45d0-99A8-6CFC402DE5D0). Now open the file [project name].xbp518 (in the project's root folder) with notepad or similar and search for these GUID(s). Note the Menta block(s) name (before the GUID) and the menta block type (just after the GUID), for example HFDI. Close all previously opened files (no save). Open the Xbuilder project normally, and open/edit the troublesome MTA. Search for the menta block(s) name and check that it also is the same block type (most likely a HFB block), then delete it. Create the block again with the same name (no copying from similar blocks!). Save and download the project to the X700. Now it should work fine viewing the live values in Control Applications. If still same issue, redo step 1-7, there may be other blocks with CodIndex='0'.   Note: If you can't see the Menta application at all it's likely a different error, see Can't see the Xenta Server Menta program online in the browser.

Issue Error importing a StruxureWare Building Operation export file. Below is an example of the error.  ERROR: Import failed to commit changeset transaction with an exception. RecoverableException: /home/ci/ci-build/rb-rb-1.8.1-system/source/server/nsp_servers/csc/changesetmanager/source/ChangeSetTransaction.cpp(1442) Invalid Data Error: File_Extension_Not_Permitted (0x10048) in module Security_Manager(74). "Not permitted to store the file "htgseqintro.wmv" with the current Document Policy." - Stack Environment StruxureWare Building Operation 1.8 Cause The export file contains a document file extension that is not permitted in the Document Policy Permitted File Extensions Resolution The file extension has to be added to the Permitted File Extensions list. See Adding a File Extension to the Permitted File Extensions List on Web Help. For the error example shown in the issue of this article, the extension wmv has to be added to the Document Policy Permitted File Extensions. list. 

Issue In EBO there is no build in way to view b3 array element value. In Continuum there is a command line that allows printing array elements by specifying the array index. Product Line EcoStruxure Building Operation Environment Building Operation ASP, ASB, AS b3 BACnet devices Infinet i2 device Cause The Infinet i2 device object array values can be viewed as WebHelp. This option is not available with b3 BACnet controllers. Resolution A workaround is to use a Script program to expose the array element value. See Sample Script Program to expose b3 array element value.

Issue When a XIF file contains NCI's (SCPT's and UCPT's) default values (NVVAL) must be described in the XIF file. In some cases if NCI's are present, but some or all NVVAL initializers are missing commissioning the device will fail. For information regarding NCI's that are part of a FILE definition, please refer to Understanding the FILE part of a XIF file. Product Line EcoStruxure Building Operation, TAC Vista Environment LonWorks XIF Cause When commissioning a device default values to configuration variables must be assigned. If the tool (TAC Vista, SmartStruxure, LonMaker, NL220) does not know what default value to assign, it can cause an error. Resolution Make sure all NCI's have proper initializers defined. Read XIF file - NVVAL initializers.pdf guide as reference. Here is an example of a NVVAL section: VAR nciHrtBtRcv 2 0 0 0 0 1 63 0 0 1 0 1 0 1 0 0 1 "&1,0,0\x80,48; 107 * 1 4 0 2 0 0 VAR nciHrtBtSnd 3 0 0 0 0 1 63 0 0 1 0 1 0 1 0 0 1 "&1,0,0\x80,49; 107 * 1 4 0 2 0 0 VAR nciLocation 4 0 0 0 1 1 63 0 0 1 0 1 0 1 0 0 1 "&1,0,0\x80,17; 36 * 1 4 0 31 0 0 VAR nciDeviceName 5 0 0 0 0 1 63 0 0 1 0 1 0 1 0 0 1 "&1,0,6\x80,3; 36 * 1 4 0 31 0 0 NVVAL #VAR nciHrtBtRcv \x00,\x00 #VAR nciHrtBtSnd \x00,\x00 #VAR nciLocation = empty string \x00,\x00,\x00,\x00,\x00,\x00,\x00,\x00,\x00,\x00,\x00,\x00,\x00,\x00,\x00,\x00, \x00,\x00,\x00,\x00,\x00,\x00,\x00,\x00,\x00,\x00,\x00,\x00,\x00,\x00,\x00 #VAR nciDeviceName = empty string \x00,\x00,\x00,\x00,\x00,\x00,\x00,\x00,\x00,\x00,\x00,\x00,\x00,\x00,\x00,\x00, \x00,\x00,\x00,\x00,\x00,\x00,\x00,\x00,\x00,\x00,\x00,\x00,\x00,\x00,\x00

Issue TAC Vista Web Settings > Preferences > Login and Logout > Automatic Logout (An inactive user is automatically logged out after a specified period of time) Selection for automatic logout time is restricted to 5, 10, 15, 20, or 30 minutes. Set the logout time to less than 5 minutes Set the logout time to more than 30 minutes. Customize the logout time to something other than specified intervals.  Environment Vista 5.1.5 Webstation TAC Vista Web Settings Cause Selection for automatic logout time is restricted to 5, 10, 15, 20, or 30 minutes. Resolution Navigate to C:\Inetpub\wwwroot\TACVistaWeb515 Open the file web.config. Use, for example, Notepad2 (Do not use wordpad as it formats the file differently) Search for "sessionState" Change the "Timeout" for the SessionState to the desired logout time in minutes Save the file 

Issue Satchwell MBX 3-port Rotary Shoe Valve Body Open / Close status determination from Spindle position. Environment Satchwell MBX 3-port Rotary Shoe Valve Body installations. Cause Satchwell MBX 3-port Rotary Shoe Valve Body is installed in pipework and Open / Close status cannot be determined by observing Valve Body Shoe positions. Resolution The Satchwell MBX 3-port Rotary Shoe Valve Body Spindle protrudes through the side of the Valve Body. The position of the Valve Body Shoes may be determined by observing the angle of the Slot in the end of the Valve Body Spindle. If the slot is ( \ )  then Valve Body is fully open to Port 2 If the slot is ( / )  then Valve Body is fully open to Port 3 If the slot is ( | )  then Valve Body is half open to Port 2 and half open to Port 3 With the Spindle Slot in the 10 o'clock position the Valve Body is fully open to flow and fully closed to bypass. With the Spindle Slot in the 2 o'clock position the Valve Body is fully open to bypass and fully closed to flow.   With the Spindle Slot in the Vertical position the Valve Body is half open to flow and half open to bypass.   Please check the latest catalog for current equipment.

Issue Will NC2/ACX2 controller warm or cool start after its IP address is changed from the configuration web page? or is it the case that the controller must be reloaded? Environment CX9640 CX9680 ACX5720 ACX5740 Cause Function as designed Resolution Changing the IP address or ACCNetId of a 9640/9680 or ACX5720/40 invalidates the backup in the controller's flash memory. Controller will have to be reloaded from CyberStation after it re-starts.

Issue Standard Applications for I/A Series Micronet BACnet (MNB) controllers Product Line I/A Series Environment I/A Series WorkPlace Tech 5.x and above I/A Series MNB controllers Cause A library of standard pre-engineered applications for MNB controllers is available. These can be modified and used as a reference for creating MNB applications. Resolution The library of standard applications can be downloaded from Exchange Extranet. Below is a list of the applications available for downloads.  DUI Application Stencil Operation Guide Application Objects Visio Stencil (Includes DUI_App) Applications - BACnet Zone, VAV, and Unitary Applications using SP and SPP Momentary Start/Stop Object Application Operation Guide Application - BACnet Zone Controller Applications Application - BACnet VAV Box Applications Application - BACnet Unitary Applications Stencil - Application Stencils Application - VAV_Staged_Heat.vst Application - FC_1DX_1EH.vst Application - FC_1PropCL_1PropHT.vst Application - FC_2Pipe_2PosHC_wCO.vst Application - All BACnet Unitary Applications.zip Application - All BACnet VAV Box Applications.zip Application - VAV_Cooling_Only.vst Application - VAV_Floating_Heat.vst Application - AHU_HeatPump.vst Application - VAV_Parallel_Fan_Staged_Heat.vst Application - VAV_Parallel_Fan_Floating_Heat.vst

Issue Reset Instructions for 1200 Series SCU Product Line TAC INET Environment SCU 1200 series controllers I/NET Cause Need to restart SCU, perhaps after a reload of firmware or dip switch settings Resolution Follow the written instruction carefully.   Reset Instructions: Locate the 3-pin connector labeled P610 and the reset push button switch. Refer to the above diagram. Momentarily short P610 pins 1 and 2 while simultaneously pressing the reset push button switch. (Note: P610 pins 1 and 2 are the pins located nearest the dip switch.) Re-download the proper BIN file to the SCU.

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.