Building Automation Knowledge Base

Issue Point values are not displayed in Vista Workstation.  Instead, all of them say [??787]. Product Line TAC Vista Environment Vista Workstation Cause The most common cause of the ??787 error message is a mismatch in the XIF between the device and the Vista database.  It may also be duplicate SNVT names in the XIF. Resolution There are a few common troubleshooting techniques that have been applied successfully to the ??787 error and resolved the issue.  The first is to upload parameters from the device.  The second is to browse the correct XIF to the device to eliminate any mismatch. Upload parameters Right-click on the device in Vista Workstation. Select Upload Parameters. Shut down Vista and restart. Make certain you are using the correct XIF The only way to be absolutely certain that the XIF in the device matches the one in the database is to upload the XIF from the device.  You may need to create a dummy LNS database to do so.  Add a generic device and commission with the option to upload the XIF from the device. Update the Vista database.  Again, this may need to be a dummy Vista database. To obtain that XIF, right-click on the device in Workstation and select Properties.  The XIF File tab lists the database copy of the XIF file (hexadecimal file name) that can be found in the Vista database directory in the $thisfil folder. Browse the correct XIF into the Vista Workstation If you are certain you have the correct XIF, right-click on the device in Vista Workstation.  Select the XIF File tab. At the bottom under Source File, click the "..." button and browse to the XIF file. Click okay.  Log out of Workstation and log back in to see the changes take effect. It may then be necessary to right-click on the controller and select Commission and Download. Remove duplicate SNVTs Open the XIF in a word editor (Notepad, Wordpad) Find the duplicate SNVT name using the Find feature Rename one of the SNVTs to a unique name. Use the above steps to browse this new XIF into Vista Workstation. XIF file contains internal variables Open the XIF in a word editor (Notepad, Wordpad) Search for the variable whose value displayed as [??787] If the variable is not listed in the XIF file, it is possible that this is an internal variable which Vista cannot read a value from Contact the manufacture of this device and ask if they can expose the value with a network variable in order for Vista to read it.

Issue Does Outlook need to be installed or running in order for ReportCmdLine to deliver email reports. Does ReportCmd interact directly with the Exchange server. Environment Continuum CyberStation WebClient Outlook Report ReportCmdLine Exchange Cause Troubleshooting problems with email delivery of reports. Resolution The ReportCmdLine.exe has no interaction with Exchange mail services whatsoever.  It simply notifies the report object specified by the /o argument that the report should be created and sent in the form of an email, or a file, or both. The effect is similar, though not precisely the same as opening the report object and selecting the Email button on the tool bar. These two actions, i.e. sending a report email using by selecting the report email button or by using the ReportCmdLine's  /t argument differ in the following way. Report Email button: The report Email button embeds the report HTML in an email. The report email must then be sent manually. If Outlook is not installed on the workstation, selecting the email button generates an error Send Mail failed to send message. ReportCmdLine: When the report object receives the email argument from the ReportCmdLine.exe it creates a report email. The email cannot be sent until Outlook is running. If Outlook is not running the Continuum caches the report email so that it can be sent once Outlook is up and running. If Outlook is not running the ReportCmdLine batch file will not display a failure error. In either case you need a mail client that supports Enhanced MAPI protocol (MS Outlook) installed and running on the Cyberstation in order to deliver the report via email.  Since Continuum is not an Exchange client it cannot interact directly with and Exchange server. Note: If the customer doesn't like the DOS box showing when the report runs. Run DOS minimized by using start/min in a batch file  Ex. Start /min Myreport.bat Note: There has been a case where having Google Chrome as the browser has affected the sending of automatic reports. Removing it corrected the issue. This was not reproducible in PSS.

Issue R2 UNC station fails to start and displays the following error messages in the Standard output window: Tridium Niagara Station, r2.301.529.v1 [UNC9] tridium.foundation.TRuntimeException E_INVALID_DSTABLE_CODE {165.16} at tridium.foundation.DsTable.codeToSpec (bytecode 58) at tridium.foundation.DsTable.codeToClass (bytecode 1) at tridium.foundation.node.NodeProperty.readExternal (bytecode 70) at tridium.foundation.node.Node.readExternalSchema (bytecode 27) at tridium.foundation.node.Node.readExternal (bytecode 50) at tridium.foundation.node.NodeSet.readExternal (bytecode 132) at tridium.foundation.node.NodeSet.read (bytecode 43) at tridium.foundation.prism.LoaderModule.loadFromSns (bytecode 48) at tridium.foundation.prism.Prism.loadFromSns (bytecode 4) at tridium.foundation.Sys.bootLocalSns (bytecode 11) at tridium.tools.StationMain.bootSns (bytecode 0) at tridium.tools.StationMain.doIt (bytecode 352) at tridium.tools.StationMain.main (bytecode 10) at java.lang.reflect.Method.invoke (Native Method) at tridium.nre.Nre.mainImpl (bytecode 271) at tridium.nre.Nre.main (bytecode 1) *************************************************************** FATAL: Cannot boot station from sns java.lang.IllegalStateException: NodeProperty.readExternal: tridium.foundation.T RuntimeException E_INVALID_DSTABLE_CODE {165.16} at tridium.foundation.node.NodeProperty.readExternal (bytecode 143) at tridium.foundation.node.Node.readExternalSchema (bytecode 27) at tridium.foundation.node.Node.readExternal (bytecode 50) at tridium.foundation.node.NodeSet.readExternal (bytecode 132) at tridium.foundation.node.NodeSet.read (bytecode 43) at tridium.foundation.prism.LoaderModule.loadFromSns (bytecode 48) at tridium.foundation.prism.Prism.loadFromSns (bytecode 4) at tridium.foundation.Sys.bootLocalSns (bytecode 11) at tridium.tools.StationMain.bootSns (bytecode 0) at tridium.tools.StationMain.doIt (bytecode 352) at tridium.tools.StationMain.main (bytecode 10)   Environment Niagara R2, UNC-410, UNC-520 Cause A needed Lon module is not installed in the UNC. Resolution Typical the Standard Output Window error messages usually provide some reference to the missing jar file. In this case, the lonTrane module was not installed in the UNC. Check to see what lon devices are installed in the station, and install all of the needed modules (jars) to the UNC.  

Issue In Niagara G3, is there a way to access the Alarm Portal through a web browser? Environment Niagara G3 Alarm Portal Cause Through the web, only the alarm console associated with the connected station can be viewed, and only one station at a time. Resolution The Alarm Portal is a program that runs off the Workbench framework, but can also be purchased as a stand alone product (i.e. no need to purchase Workbench and Alarm Portal, just purchase the portal). With the Alarm Portal software, connecting to multiple consoles at once is possible (similar to using Tools > Alarm Portal within Workbench). The other option is to create a Station Recipient for the desired alarm class in the ENC station's Alarm Service that points to the Enterprise Network Server, and use the server's Alarm Console. As long as the user has permissions to access the alarm console in the server, then the user can navigate to it in the nav tree.  It can also be added as a node in the .nav file for easy access to the location.  The user would still need the appropriate permissions to access the console.

Issue Alarms generated from Sigma controllers are not received at the Sigma server. Product Line Satchwell Sigma Environment Sigma software - All versions Controller firmware - All versions Cause The controller generates the alarm correctly, but is unable to send the alarm to the Sigma server. This can be seen by using the "Comms Stats" request from the Sigma server. The screen shot below indicates that the "Alarm buffers" have 21 alarms waiting for transmission. Resolution To identify the cause of the problem, carry out the following steps. Perform a "Comms Stats" request of the controller from the Sigma server, to establish that an alarm has been generated. Confirm that the Client configuration has been correctly set up by referring to Alarms are not displayed in the Sigma local or remote client Alarm Manager window. Confirm that the Sigma server has been correctly configured in "System Setup / Networks and Devices". Confirm that the Sigma server IP Address matches the address set in "Network Connections" Upload an object with an alarm programmed from the controller, and check that the routing page has no references to "T" present. (T was used in the BAS2800+, but is not in Sigma). Confirm with the IT department that there are no network issues.

Issue Xenta 700 restarts when updating a Menta Time Schedule using a Central Time Schedule in TAC Vista Workstation. Environment Xenta 701 Xenta 711 Xenta 721 Xenta 721 Cause This issue is caused by a bug in the Xenta Server firmware. Resolution This bug has been fixed in the Xenta 700 5.1.7-SP1 firmware, available for download from the Exchange Extranet

Issue Is a Satchwell DWT0002 sensor fitted directly into the waterway? Environment DWT 0002 Sensor Fast Response Cause Customer has to replace this sensor and is not sure how to remove it. Resolution The DWT0002 sensor provides a fast response to temperature changes, and is fitted directly into the pipework. Important Note; When changing this sensor, the water must be isolated and drained from this part of the system. To review the data sheet, please click HERE.

Issue When trying to install Niagara R2 version 2.301.330, the process halts and reports that Java Virtual Machine (JVM) is not installed. What version of JVM is required? Environment Niagara R2 version 2.301.330 Cause All Niagara R2 versions prior to 2.301.514 require Microsoft's Java Virtual Machine.     Resolution All revisions of Niagara R2 prior to 2.301.514 require Microsoft's JVM. To confirm if it is installed, open a Command Prompt window and type "jview" then press Enter. This command will display the current version of Microsoft's JVM (or that it is not installed). Download and install Java_Virtual_Machine_for_WinXP.exe. All revisions of Niagara R2 starting with 2.301.514 and beyond require Sun's JVM. To confirm if it is installed, open a Command Prompt window and type "java -version" then press Enter. Visit http://www.java.com regularly to keep the JVM updated. The Microsoft and Sun JVMs can co-exist on the same Niagara host computer.

Issue Attempts to download images or object files to UNC532 controllers only partially download then fail. This is often seen in the Sigma debug window. Product Line Satchwell Sigma Environment Sigma Ethernet ARCnet UNC532 Cause Large quantities of Sigma global data can adversely affect the ability of the slower processing controllers such as the UNC532 from accepting large files due to communication timeouts.   From experience this affect has been with global levels of 600 broadcasts per minute. Resolution If there are problems on site with downloading files then checking the global broadcast rates can be achieved by; Using Wireshark to trace the Ethernet Backbone communications  (See Using WireShark to analyse communications on an Ethernet network) Email the trace to Product Support and request a global data analysis.

Issue Sigma and BAS - Out of Range value displayed on an AI point when configured as a 0-10V input. Product Line Other, Satchwell Sigma Environment Sigma BAS Cause If a 0-10V analogue input rises to above 10Vdc then the point default value is displayed. Resolution There are several ways to prevent this happening as follows: Follow the example in SHD100 / SHD101 - Humidity Sensors can give a DC voltage signal of greater than 10 Volts using a resistor and lookup table. Or use a Zener diode fitted as per the diagram. Note the maximum input will be the rating of the Zener diode e.g if the Zener diode rating is 9.1V then any voltage from the device higher 9.1V will be pulled back down to 9.1V. Zener diodes are available with fixed voltages, the nearest to 10V is 9.1V. The Zener diode can be fitted at the sensor end (normally slightly easier) or at the controller. The upper limit of the normal operating range of the sensor needs to be below 9.1V. Note: normally a resistor is fitted when using a Zener diode, but because the impedance of the sensor is high, the current will be small, hence the resistor is not used.  Or use a diode, this will work to where the maximum input rises to 10.6V. The diode needs to be fitted in series with the device BMS signal. A diode will drop 0.6V across it, therefore in this case a revised lookup table needs to be created. e.g 10V in will be 9.4V out and so forth. Or in the case of feedback from an actuator, the output to the actuator can be restricted to a value e.g 9.5V, this will then restrict the feedback signal. Care must be taken with this method if the actuator is connected to a valve then the performance of the valve and the system it is connected to will be slightly reduced.

Issue A project requires iClass cards and readers. Are these available in Infinity 37 bit format and are they compatible with Continuum? Environment CyberStation ACX57xx AC-1 family ACX7xx Cause A project requires iClass cards and readers. Resolution HID iClass cards with the Infinity 37 bit format are commonly used with Continuum. If you use the iClass cards you must use an iClass reader since the operating frequency is different than standard prox (13.56MHz vs. 125KHz). Continuum does not know the difference between a standard prox Infinity 37 bit and an iClass Infinity 37 bit card. All Continuum cares about is the data stream from the reader. In Continuum you just set the card format in the door editor to Infinity 37 bit for either type. The iClass cards and readers can be ordered from Schneider's iPortal. You must fill out a form that asks for various card attributes - just like standard prox cards (quantity, start card number, site code, if you want card number printed on it, if you want a slot punch, etc)

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 How to install / add WebClient to existing SU installation of Continuum. Environment Continuum WebClient Cause Existing Continuum SU Cyberstation installed and site is being upgraded with WebClient support. Resolution Perform the following steps to install WebClient on your Single-User installation. Backup the ContinuumDB, Graphics files, and Menus to a safe location. (For detailed steps on how to backup / restore your ContinuumDB see here.) Upgrade security key to allow WebClient. (from supplied serialized upgrade code from Repairs) Uninstall Continuum. Install WebClient from scratch following the Planning and Installation Guide. (IIS then WebClient) Restore your ContinuumDB, graphics files and Menus. Test

Issue Program to calculate the Sunrise time / Sunset time Environment Programmable Object Sunrise Sunset Cause Customer needs a program to calculate the Sunrise / Sunset times in Sheffield. Resolution To review the Sunrise / Sunset times for the required area, please click HERE. When connected to the site, proceed as follows; "Find a Location" enter the required location and select GO. Choose "Almanac" Choose "Sunrise / Sunset" Select the month you require. The required programmable Objects are shown below, or to upload the objects and lookup table details, please click HERE. Day of the Year. Object 1 10 XInt = DAY 20 IF MONTH >= 2 THEN XInt = XInt + 31 30 XFlo = FLOAT ( YEAR ) 40 XFlo = XFlo / 4.00000 50 XFlo = FRAC ( XFlo ) 60 IF XFlo = 0.000000 THEN YInt = 1 ELSE YInt = 0 70 IF YInt = 0 AND MONTH >= 3 THEN XInt = XInt + 28 80 IF YInt = 1 AND MONTH >= 3 THEN XInt = XInt + 29 90 IF MONTH >= 4 THEN XInt = XInt + 31 100 IF MONTH >= 5 THEN XInt = XInt + 30 110 IF MONTH >= 6 THEN XInt = XInt + 31 120 IF MONTH >= 7 THEN XInt = XInt + 30 130 IF MONTH >= 8 THEN XInt = XInt + 31 140 IF MONTH >= 9 THEN XInt = XInt + 31 150 IF MONTH >= 10 THEN XInt = XInt + 30 160 IF MONTH >= 11 THEN XInt = XInt + 31 170 IF MONTH >= 12 THEN XInt = XInt + 30 180 RETURN VIA TEXT 200 VALUE XInt  Sunrise Time Calc.  Object 2 10 XFlo = POINT 0|1 20 YFlo = FLOAT ( YEAR ) 30 YFlo = YFlo / 4.00000 40 YFlo = FRAC ( YFlo ) 50 IF YFlo = 0.000000 THEN YInt = 1 ELSE YInt = 0 60 IF YInt = 1 AND MONTH >= 3 THEN XFlo = XFlo - 1.00000 70 ZFlo = LOOKUP ( 1001 , XFlo ) 80 ZFlo = ZFlo / 60.0000 90 YFlo = FRAC ( ZFlo ) 100 ZFlo = ZFlo - YFlo 110 YFlo = YFlo * 60.0000 120 YFlo = YFlo / 100.000 130 ZFlo = ZFlo + YFlo 140 RETURN VIA TEXT 203 VALUE ZFlo  Sunset Time Calc.  Object 3 10 XFlo = POINT 0|1 20 YFlo = FLOAT ( YEAR ) 30 YFlo = YFlo / 4.00000 40 YFlo = FRAC ( YFlo ) 50 IF YFlo = 0.000000 THEN YInt = 1 ELSE YInt = 0 60 IF YInt = 1 AND MONTH >= 3 THEN XFlo = XFlo - 1.00000 70 ZFlo = LOOKUP ( 1001 , XFlo ) 80 ZFlo = ZFlo / 60.0000 90 YFlo = FRAC ( ZFlo ) 100 ZFlo = ZFlo - YFlo 110 YFlo = YFlo * 60.0000 120 YFlo = YFlo / 100.000 130 ZFlo = ZFlo + YFlo 140 RETURN VIA TEXT 203 VALUE ZFlo  Sunrise/Sunset Interlock.  Object 4 10 XFlo = POINT 0|2 20 YFlo = FRAC ( XFlo ) 30 XFlo = XFlo - YFlo 40 YFlo = YFlo * 100.000 50 IF HOUR >= INT ( XFlo + 1.00000 ) THEN GOTO 90 60 IF HOUR = INT ( XFlo ) THEN GOTO 100 70 XInt = 0 80 RETURN FALSE "Plant Off" 90 XInt = 1 100 IF MINUTE >= INT ( YFlo ) THEN XInt = 1 110 XFlo = POINT 0|3 120 YFlo = FRAC ( XFlo ) 130 XFlo = XFlo - YFlo 140 YFlo = YFlo * 100.000 150 IF HOUR >= INT ( XFlo ) THEN GOTO 170 160 GOTO 180 170 IF HOUR >= INT ( XFlo + 1.00000 ) OR MINUTE >= INT ( YFlo ) THEN XInt = 0 180 IF XInt = 1 THEN RETURN TRUE "Plant On" 190 RETURN FALSE "Plant Off"

Issue Object level security using SecurityLevel Environment CyberStation Cause Documentation Resolution Click -> Continuum Security Levels explained.

Issue How long has an Automation Server been running since the last power cycle or reboot? Environment Automation Server SmartStruxure Device Administrator Cause The uptime of an Automation Server indicates how long the server has been operational since the last power cycle or system reboot. This is not currently visible in the StruxureWare Building Operation Workstation, but it is available through the Console interface in Building Operation Device Administrator. By monitoring the uptime of the device this can be a valuable diagnostic tool to determine if power loss occurred, crashes in Automation Server occurred, or other situations that might have resulted in a reboot and what time this occurred. Resolution In the Building Operation Device Administrator connect to an Automation Server (IP or USB) and select the "Open Console" option. Once logged into the Console issue the "uptime" command in the prompt. The uptime will be listed in Days, Hours, and Minutes as visible below: admin@AS-B-RKFDMW:~> uptime  14:18:20 up 1 day,  1:01, load average: 1.26, 1.16, 1.06   If you are using Report Server, this information is also available using SQL Server Management Studio from the Report Server PC. Enter the following query and the "Runtime" column will provide the current uptime for the specified ES or AS. SELECT Top (1) CAST(CURRENT_TIMESTAMP - DateTimeStamp AS Time) AS 'Runtime' ,DateDiff(Day, DateTimeStamp, CURRENT_TIMESTAMP) AS 'Days Up' ,DateDiff(HOUR, DateTimeStamp, CURRENT_TIMESTAMP) AS 'Hours Up' ,DateDiff(MINUTE, DateTimeStamp, CURRENT_TIMESTAMP) AS 'Minutes Up' ,DateDiff(SECOND, DateTimeStamp, CURRENT_TIMESTAMP) AS 'Seconds Up' ,[DateTimeStamp] ,[TYPE] ,[OriginatedServer] ,[OriginatedDevice] ,[SystemEventId] FROM [StruxureWareReportsDB].[dbo].[tbEvents] WHERE SystemEventId = 'Server initialized' AND OriginatedServer = '/Server 1' ORDER BY DateTimeStamp Desc   NOTE: Change the WHERE statement "OriginatedServer = '/Server 1'" so that '/Server 1' become '/yourServerName'

Issue Unable to update an ASC when adding a new MR to an existing system. Product Line TAC INET Environment All versions of I/Net utilizing HVAC applications. Cause On a system that has multiple sublan devices and adding a new or several devices to the controller, when updating the UPD files it appears to get downloaded but when the MCI update is done, only one point is written to the database. If the points are added manually, a Memory Error would come up indicating that there is not enough memory in the controller to do this. However, this is not seen when doing the UPD file update nor MCI Update. Resolution To resolve this issue, the following steps needs to be done: Connect to the controller Go to Edit/Controller/Configuration Verify that the controller does in fact have memory left If not, look at the trends that are on the resident I/O Points If possible, delete unwanted trends that are using up memory to free it up to allow these devices to be added Once done, go back to ASC Parameters and then update the ASC and MCI again.

Issue The Modbus communication stops from time to time, and never gets back until the COM port is reconfigured. The device is still online; it is only the values that will not update. This is usually only an issue if Modbus groups are used. Product Line EcoStruxure Building Operation Environment SmartStruxure 1.5 Automation Server Cause If a trendlog with a very long sample time (e.g. 1 hour) is set to log a point and nothing else is bound to the Modbus device, all values from the device will be updated at the same interval as the trendlog. This is solved in newer versions. Resolution Add a single Modbus point to a new Modbus group. Set the group poll rate to the same as the Device poll rate. To enable polling of the Modbus point, add an alarm that will not activate. This will result in polling of the device at the group poll rate.

Issue The Vykon Alarm Client will not connect to the Niagara R2 Enterprise Server station. Environment Vykon Alarm Client Niagara R2 Enterprise Server station Cause The Vykon Alarm Client uses TCP port 4321 to communicate with the Enterprise Server. Many firewall, antivirus, and Internet security applications (e.g. Windows Firewall, antivirus & remote access software) block TCP port 4321 by default. Resolution Either disable the offending application, or create an exception policy in the application to open TCP port 4321. To view active TCP connections, open a DOS window, and type: netstat -ano. The output will look something like this: Active Connections Proto Local Address Foreign Address State PID TCP 0.0.0.0:13 0.0.0.0:0 LISTENING 956 TCP 0.0.0.0:37 0.0.0.0:0 LISTENING 956 TCP 0.0.0.0:135 0.0.0.0:0 LISTENING 1368 TCP 0.0.0.0:445 0.0.0.0:0 LISTENING 4 TCP 0.0.0.0:3011 0.0.0.0:0 LISTENING 756 TCP 0.0.0.0:6523 0.0.0.0:0 LISTENING 3752 TCP 0.0.0.0:27700 0.0.0.0:0 LISTENING 748 TCP 10.1.146.152:139 0.0.0.0:0 LISTENING 4 TCP 10.1.146.152:2531 72.247.127.34:80 CLOSE_WAIT 3616 TCP 10.1.146.152:2532 72.5.124.55:80 CLOSE_WAIT 3560 TCP 10.1.146.152:2533 72.247.127.11:80 CLOSE_WAIT 3560 TCP 10.1.146.152:4245 10.1.146.32:4321 ESTABLISHED 216 A successful connection to the Enterprise Server will have an entry similar to the last line, where the Foreign Address (e.g. 10.1.146.32:4321) will have a state of ESTABLISHED.

Issue A Xenta 102-AX accepts a 0-5V input on all external inputs. If Universal Input 3 is designated as CO 2 , the range of the input needs to match the range of the sensor. Product Line EcoStruxure Building Operation, TAC Vista Environment Xenta 102-AX Universal Input 3 CO 2 sensor Cause The default setting (a gain of 1/1) results in 0V = 0ppm 5V = 1023ppm (1023 is a resolution of the onboard analog to digital converter.) Resolution Refer to page 3-66 of the TAC Xenta 102-AX Software & Hardware Manual for more detail. Calculate the required gain for the range of the CO 2 sensor. Ensure the sensor outputs a 0-5V signal. Note the CO 2 level at 5V. In this example, 2000ppm. Divide the maximum CO 2 reading by the analog to digital converter bit resolution (1023). Multiply the result by 1000. (2000 / 1023) * 1000 = 1955 Locate the value for Universal Input 3 SCPTgain. There are four locations to alter this value: Xenta 102-AX Plug-in Go to the Browser Tab > Xenta102AX > UnivIn3 Sense > SCPTgain > multiplier. Over on the right, enter in 1955/1000 and hit Set Value. LonMaker or LNS browser Open the browser window by right clicking on the 102-AX in the drawing and selecting Browser. Look in the Functional Block column for UnivIn3Sense. In that category is a point called SCPTgain. Click on it and then enter up top 1955/1000. Hit the red down arrow to download the value to the device. Enable monitoring on the nvoCO2sensor value or reopen the browser to view the new CO 2 value. Vista Workstation Go to the 102-AX.UnivIn3_Sense module and locate the SCPTgain point. Double click it. By Multiplier enter 1955 and by Divisor enter 1000. StruxureWare WorkStation Go to the 102-AX and click on UnivIn3Sense module and in the Variables tab locate the nciGainUIx point and expand it. For Multiplier, enter 1955 and save. For Divisor, enter 1000 and save.

Issue Certain values in the Xenta 102-AX can be put into override mode through the Plug-In: Airflow Auxiliary Temperatures 1 and 2 Universal Inputs 1, 2, 3, and 4 CO 2 Space Temp Damper Position Universal Outputs 1, 2, and 3 If the plug-in is not available, they can be overridden through the SNVT input nviRequest (type SNVT_obj_request). Product Line EcoStruxure Building Operation, TAC Vista Environment Xenta 102-AX Cause The plug-in might not be available for a multitude of reasons. For example, if the Xenta 102-AX is being integrated into a third party LON system, or no LNS management tool is being used. The values below can be used to implement an override through the SNVTs. Resolution Signals required to perform external control of inputs and outputs on the Xenta 102-AX: Set the override behavior value signal to 1 (OV_SPECIFIED) Set the desired value in the override value signal Send a SNVT to the signal Node_Object.nviRequest. It is a structured SNVT input with the following members: OBJECT_ID - refer to the list below for the appropriate object ID for each override OBJECT_REQUEST - set to value to 6 (RQ_OVERRIDE) to initiate the override, set to value 0 (RQ_NORMAL) to release the override. The tables below specify all necessary signals for each override. They are displayed in the following format: ID Title Overridden Value Desired Override Value Override Behavior   1 Airflow Reading (CFM, l/s) Airflow_Sense.nvoAirFlow.PV Airflow_Sense.nvoAirFlow.SCPTovrValue.PV Airflow_Sense.SCPTovrBehave.PV   2 Universal Input 1 (%) UnivIn1_Sense.nvoUnvInput1.PV UnivIn1_Sense.nvoUnvInput1.SCPTovrValue.PV UnivIn1_Sense.SCPTovrBehave.PV   2 Duct Inlet Temperature UI1 (°F, °C) UnivIn1_Sense.nvoAuxTemp1.PV UnivIn1_Sense.UCPTovrValueTemp.PV UnivIn1_Sense.SCPTovrBehave.PV   3 Universal Input 2 (%) UnivIn2_Sense.nvoUnvInput2.PV UnivIn2_Sense.nvoUnvInput2.SCPTovrValue.PV UnivIn2_Sense.SCPTovrBehave.PV   4 Universal Input 3 (%) UnivIn3_Sense.nvoUnvInput3.PV UnivIn3_Sense.nvoUnvInput3.SCPTovrValue.PV UnivIn3_Sense.SCPTovrBehave.PV   4 CO2 Reading UI3 (ppm) UnivIn3_Sense.nvoCO2sensor.PV UnivIn3_Sense.UCPTovrValueCO2.PV UnivIn3_Sense.SCPTovrBehave.PV   4 Outside Air Temperature UI3 (°F, °C) UnivIn3_Sense.nvoAuxTemp2.PV UnivIn3_Sense.UCPTovrValueTemp.PV UnivIn3_Sense.SCPTovrBehave.PV   5 Universal Input 4 (%) UnivIn4_Sense.nvoUnvInput4.PV UnivIn4_Sense.nvoUnvInput4.SCPTovrValue.PV UnivIn4_Sense.SCPTovrBehave.PV   5 Setpoint Offset UI4 (°F, °C) UnivIn4_Sense.nvoSetPtOffset.PV UnivIn4_Sense.UCPTovrValueTemp.PV UnivIn4_Sense.SCPTovrBehave.PV   6 Space Temperature (°F, °C) VAV_Controller.nvoSpaceTemp.PV VAV_Controller.nviSpaceTemp.SCPTovrValue.PV VAV_Controller.SCPTovrBehave.PV   7 Damper Actuator (%) Damper_Actuator.nviRelStPt.PV Damper_Actuator.nvoActualValue.SCPTovrValue.PV Damper_Actuator.SCPTovrBehave.PV   8 Universal Output 1 (%) UnivOut1_Object.nviUnvOutput1.PV UnivOut1_Object.nviUnvOutput1.SCPTovrValue.PV UnivOut1_Object.SCPTovrBehave.PV   9 Universal Output 2 (%) UnivOut2_Object.nviUnvOutput2.PV UnivOut2_Object.nviUnvOutput2.SCPTovrValue.PV UnivOut2_Object.SCPTovrBehave.PV   10 Universal Output 3 (%) UnivOut3_Object.nviUnvOutput3.PV UnivOut3_Object.nviUnvOutput3.SCPTovrValue.PV UnivOut3_Object.SCPTovrBehave.PV