Building Automation Knowledge Base

Issue How to set the neuron ID of an I/O Module in a Vista classic network. Product Line TAC Vista Environment Vista Classic Network Xenta I/O modules Cause Xenta I/O modules beneath a base unit (300 or 400 series) do not show up in the Folder view tree structure.  You cannot right-click and set a neuron ID the same way you do for a base unit. Resolution Click on the Xenta base unit (300 or 400 series controller) in the tree structure. This brings up a list of modules inside the Menta file as well as two option modules that cannot be seen from the tree structure-- $IO and $LOGS. Double click the $IO module. All of the I/O modules defined in the Menta file are listed here.  Right-click, properties, to set the neuron ID.

Issue Some BACnet devices advertise support for services such as RPM, COV, etc but malfunction when the service is used. An example of such a device is the Johnson Controls TEC2627VVT which advertises support for RPM but fails to upload its objects when SBO uses RPM to get the object list. Product Line EcoStruxure Building Operation Environment BACnet Automation Server Enterprise Server Cause Some BACnet devices with inconsistent protocol implementation cannot process BACnet services such as RPM, COV, etc. Resolution Feature Supported in Version <no-rpm/> 1.8.1 and higher <no-cov/> 1.8.1.23701 and higher <ignore-unhosted-devices/> 3.2.3.9005 and higher (*)   Users can create a rule under the BACnet interface to configure SBO not to use the service. Some rules are global, while others can be for specific BACnet devices. For particular BACnet devices, they are specified by 'Vendor Identifier' and 'Model Name,' which need to match exactly as shown in that device's Properties - Advanced Tab.   Ensure you have installed the version that supports the feature you want to change. Setup file using the no-rpm rule. Use a text editor like 'Notepad' to create a text file or download the same file below. Enter the device's vendor ID (5)  and model name (TEC2627VVT) followed by the rule (no-rpm) using the format seen in the screenshot below. Save the file to the desired location on the PC with a name aiding later identification. Under the BACnet interface, create a new 'Document' object in the 'Application' folder. NOTE: The object MUST be named 'service_blacklist' in all lowercase. Click 'Next,' import the text file created in step 1, and save the 'Document' object. Restart the Server  Once the device is on the block list, SBO will not send 'readPropertyMultiple' requests to the device using only individual 'readProperty' requests. Add the service_blacklist to the EBO Server. Add the no-cov tag if you would like to block that service for this device:  Extended for multiple devices from different vendors simultaneously using this example for reference.   One can add a global rule using this syntax to ignore unhosted devices. * NOTE: It is recommended to remove <ignore-unhosted-devices/> after upgrading to EBO 4.0/2022 and higher because this feature is supported in the BACnet Interface Properties and BACnet Device Discovery view. Device Discovery for BACnet Controllers and IO Modules (se.com)  Once the Server has restarted, check the trace.log file and search for service_blacklist, there should be entries similar to this. 

Issue Double click on a point in Vista. The Edit Properties window should pop up allowing you to view the value, set the Forced-By-Operator setting, and set the forced value. Sometimes double clicking it does not open any window. Product Line TAC Vista Environment Vista Workstation Double or dual monitor Cause The Edit Properties window is popping up off of the screen. Either it was dragged off of the screen accidentally or a second monitor was removed or is not accessible through remote connections. Resolution To display the dialog on the main screen: Double click a point in Vista. Do not click on anything else. The invisible Edit Properties window should be the current window. Press three keystrokes in this order: Alt + Space + X.  This is the Windows hotkey combination to the File menu, and will maximize the current window on the monitor. Possibly try hitting the Alt key twice. This brings the current window to the front. Alt + Space bar, then select Move with the mouse, after a tap of any arrow key, the mouse should lock onto the window allowing you to move it To prevent this from happening in the future: Download the TAC Vista Dialog Position Reset utility. Unzip and double click the executable file to run. Hit the Reset button.

Issue Xenta Server is marked with an asterisk and says "Needs to be Commissioned" Environment Vista Workstation Xenta Server Xenta 511, 527, 555, 701, 711, 721, 731, 913 Cause The files in the Xenta Server do not match the Xbuilder project stored in the Vista Database. Resolution Right-click on the Xenta Server in Vista Workstation and select Edit.  This will open XBuilder. In Xbuilder, click "Send to Target" to download the files to the Xenta Server.

Issue When using the Modbus RTU and Modbus IP XDrivers it is important to determine which controller and port can support the electrical standards used by the 3rd party device. Product Line Andover Continuum Environment Continuum Netcontroller II and bCX1 controllers that have been XDriver enabled. XDriver, Modbus RTU, IP, Infilink, Infilink200, B-Link. RS-232, RS-485 JBUS Cause Controller ports and 3rd party devices come in various electrical standards (RS-232, RS-485, RS-422), which ports support the various standards? Resolution There are two Continuum Modbus XDrivers: Modbus RTU: This allows the connection of 3rd party Modbus RTU slaves via the serial data RS-232, RS-485 or RS-422 electrical standards. RS-232 is a point to point connection to 1 device, RS-485 & RS-422 support a bus topology for connection of multiple 3rd party devices. The Continuum controller will be the Modbus RTU Master and will poll the 3rd party device that must be a slave. The bCX1-CR controllers have 2 ports that can be configured for Modbus: Comm1 RS-232 Comm2 RS-232 or RS-485 port The Netcontroller II controllers support: Comm1 - RS-232 or RS-485 Comm2 - RS-485 Comm3 - RS-232 Comm4 - RS-422 The ACX57xx controllers support: Comm1 - RS-485 Notes An Infilink200 or B-Link may be used to convert RS-232 to RS-485 if required. The J Bus protocol is a subset of the Modbus protocol and so the Modbus XDriver is used for J Bus Systems. Modbus IP: The bCX1, ACX57xx and the Netcontroller II all support the Modbus IP protocol that connect via the Ethernet IP connection. This XDriver can be configured to support either Client or Server modes. Although the communication is physically via the Ethernet port, one of the Serial ports is required to be X Driver enabled to load the software, this serial port is then no longer available for other purposes. This XDriver requires Ethernet X Driver support to be enabled on the port. NOTE Netcontroller II and bCX1 can have an XDriver ENABLED on more than a one Comms port, however only one IP XDriver should be INSTALLED on each controller, also only one Modbus RTU XDriver should be INSTALLED on each controller. It is possible to INSTALL a Modbus RTU and a Modbus TCP/IP XDriver on a single controller, but it would be very easy to overload the controller, so this setup is only suitable for smaller networks. (note the difference between enabling XDriver support and Installing an XDriver) See Articles Can multiple Modbus TCP/IP XDrivers be installed on a single 2nd Generation NetController? and BCX Controller can use Comm 1, Comm2, or both ports for Modbus RTU X-Driver  

Issue Current information will be stored and updated in release notes and online documentation. Compatibility Matrix of Operating Systems, Video, Product Announcements, SQL Compatibility Product Line Andover Continuum, EcoStruxure Building Expert, EcoStruxure Building Operation, Satchwell Sigma, TAC IA Series, TAC INET, TAC Vista Environment Windows Operating Systems and iBMS (intelligent Building Management System) Software Cause Compatibility, Firmware, Product Announcements Resolution Please see release documentation for current and recent products. For the Firmware compatibility matrix for: I/NET, it is available HERE or the EcoBuilding Download Center Continuum, click HERE Xenta Software Downloads HERE Vista, click HERE EcoStruxure Building Operation, click HERE Product Announcements can be a great tool for discovering which products have been tested and are compatible with the different versions. These documents are available on the Extranet, but have been compiled here for ease of access: I/NET 2.40   Product Announcement 2.41   Product Announcement 2.41a Product Announcement 2.42   Product Announcement and Compatibility Matrix (page 5) 2.43   Product Announcement PA-00239 2.44a Software Available from Exchange Download Center 2.45   Software Available from Exchange Download Center 2.46 Software Available from Exchange Download Center 2.47 Software Available from Exchange Download Center 2.47a Software Available from Exchange Download Center 2.47b Software Available from Exchange Download Center 2.48 Software Available from Exchange Download Center Operating Systems and SQL Supported Video Compatibility Support Policy PA-00279 Software Support for TAC I/NET Continuum v1.92 Product Announcement v1.93 Product Announcement v1.94 Product Announcement PA-00210 1.94 SP1 Product Announcement PA-00273 1.9 - 2.1 Software, Firmware, & Video Compatibility Matrix Concerning IE10 and IE11 browser support  2.0 Feature Blast 2.0 + 2.01/ 2.02 Update Compatibility Matrix 2.0  Product Announcement PA-00353 2.0 CyberStation Installation Guide 2.0 WebClient Installation Guide 2.0 Software License and Ordering Activation Process 2.0 Software and Controller Upgrade Process Andover Continuum PA-00333 Support Policy PA-00272 for Andover Continuum Vista v5.1.5 Product Announcement v5.1.6 Technical Product Advisory v5.1.7 release note document, TAC Vista Compatibility Matrix, SNVT Matrix documents, and TPA-VSTA-11-0020.00 v5.1.7 Product Announcement x5.1.8 Release Note TAC Vista 5.1.8 and TAC Xenta 500/700/900 5.1.8 v5.1.9 Vista Compatibility Matrix SecurityIAS Product Announcement PA-00291 Product Announcement TAC Vista transition to SmartStruxure solution overview  Support Policy PA-00274 for TAC Vista Satchwell Sigma v4.05 SEB Release Notes v4.06 Release Notes v4.06 Release Note Supplement v4.07 Release Notes Satchwell Sigma Standard Edition Installation and User’s Guide Support Policy PA-00297 for Satchwell Sigma v4.08 Release Notes PA-00397 Sigma Version 4.08 Sigma server on a virtual machine Satchwell Micronet data sheet - MicroNet View 2.1 OS Compatibility - Micronet View PA-00228 Product Announcement Support Policy PA-00298 for Satchwell MicroNet PA-00228 Satchwell MicroNet End of Commercialization Announcement I/A Series PA-00163 I/A Series R2 & G3 Product Announcement PA-00114 Legacy Products Windows 7 Compatibility I/A Series R2 with Windows Compatibility Chart PA-00243 Software Product Update - Q2 2013 PA-00251 Hardware Product Update - Q2 2013 PA-00278 Software Product Update - Q3 2013 I/A Series (Niagara) R2 Windows Compatibility Matrix with additional detail I/A Series (Niagara) AX/G3/N4 Windows Compatibility Matrix with additional detail Support Policy PA-00280 R1 for TAC I/A Series StruxureWare Building Operation Please visit Maximum number using StruxureWare Building Operation (Scalability and Capacity) SmartStruxure Lite Please visit SmartStruxure Lite solutions

Issue TAC Graphic Clipart library is a collection of clipart to use as a starting point for an image based graphic page. There are pieces for building air handler ductwork, controlled equipment, dampers and actuators, and water side equipment. Product Line TAC INET, TAC Vista Environment I/NET gpg graphic Vista ogc graphic Cause Without libraries to build a background image for HVAC equipment, it can be difficult to create user-friendly graphic pages to display dynamic data.  In a graphic editor that relies on bitmaps or jpgs to build the airflow diagrams, floor plans, water side diagrams, etc, this library can be used as a starting point. Resolution Download the attached .zip file. Unzip the contents to a location on the hard drive of the computer that will be used to edit the graphic pages. Browse the contents of the .zip file.  It will be separated into logical folders.

Issue Knowing the types of licenses, differences between each one, and the revisions supported by the license. Product Line TAC Vista Environment Vista 5.X Cause There are three different types of licensing for a Vista system. Resolution There are three types of TAC Vista software licenses. TAC Vista Demo License This type of license is for temporary use. It expires every thirty days. It is the full version license excluding OPC server licenses. The demo license is available on Schneider Electric buildings business extranet. (Products >TAC Vista > Vista Software > Evaluation License File). No activation required, ready to use after downloading. (Store the license file into C:\Program Files\Schneider Electric\License Files, by default.) Monthly demo licenses only work locally for the PC where they are installed.  You cannot use a License Server to serve up remote Workstation licenses to a remote PC, for example. For remote Workstation usage, please use the TS version of demo license instead. Demo licenses contain unlimited TAC Vista Webstation seats which allow multiple people log into Webstation simultaneously on the server PC and other computers.   TAC Vista Engineering Dongle This type of license is for Schneider Electric engineers or partners use. It comes with the full version license besides the OPC server licenses.  Please read Part number for Vista 5 engineering dongle for more purchasing information. No activation required, ready to use after receiving. Simply put the engineering dongle into one of the USB ports. You may be asked to install some software upon first time use. Note:  Insert the engineering dongle prior to starting the TAC Vista server. Engineering dongles only work locally for the PC where they are plugged in.  You cannot use a License Server to serve up remote Workstation licenses to a remote PC, for example. Engineering dongles contain only one (1) TAC Vista Webstation seat. In addition, user can log into Webstation only on the sever PC.   TAC Vista Customer License This type of license is for end user use. Depending on the customer needs, different features of Vista software can be purchased standalone or in packages. For more information about each software feature or packages, please read the Vista 5 Software license packages and Vista 5 product catalog. Customer licenses are restricted to the minor revision of the Vista software or lower. A Vista 5.0 license will not function on a Vista 5.1 installation. However a Vista 5.1 license will work for all 5.1.x installations as well as all 5.0.x installations. Maintenance agreements ( XXXX 1 year licenses) are available for most TAC Vista 5.1 software modules. An active maintenance agreement ensures that the license has access to any new, minor and major, versions. Maintenance agreements are automatically renewed at the end of each 12 month period. The termination notice is three months. Minimum agreement time is three years. Activation of the license is required. You can generate the license on the https://schneider-electric.flexnetoperations.com website with the entitlement ID received via email after purchasing. The license needs to be locked to: Computer MAC address If you lock the license to a computer's MAC address, the license needs to be stored on this particular computer (C:\Program Files\Schneider Electric\License Files, by default), and it can only be used on this computer.   An onsite dongle (end-user dongle) The dongle needs to be purchased separately (name: Vista 5 Hardware Dongle, part number: 000857510 on the iPortal).  If you lock the license to the onsite dongle, you can use TAC Vista software on any computer as long as this dongle is plugged in. You can re-host the license to another MAC address or onsite dongle up to 4 times in a 1 year period. If you exceed this re-hosting limit you will need to contact Product Support with a valid reason why this occurred, and the limit can be reset. For additional customer licensing information please read TAC Licenses Installation Manual and TAC Vista 5.0 to 5.1.7 license does not work after installation for how to use LMTOOLS to manually read site license.

Issue Step by step instructions to configure the Lonworks Network Interfaces application to communicate over IP-852 to a Loytec L-IP router using the Echelon driver Product Line Field Devices, Other, TAC Vista Environment LNS Turbo Lonmaker turbo Lonworks Network Interfaces Loytec L-IP  Cause Instructional how to document steps through the necessary set-up to get a Loytec L-IP to communicate in a Vista system using the Echelon driver Resolution It is preferred to use Loytec's own driver rather than Echelon's driver, and also the Loytec driver is the only one supported in SmartStruxure, how ever it is possible to use Echelon's driver following the guide below. To learn more about the L-IP and understand the difference between two drivers, check this video: https://www.youtube.com/watch?v=cLNBv6tEDXg or Loytec L-IP 101 Note 1: The first steps would be to verify the IP addresses needed for both the computer and the Loytec L-IP router. In this example, we will be using 10.159.5.39 for the L-IP and 10.159.3.26 for the computer running LNS. The default IP address of the Loytec L-IP router is 192.168.1.254. In most cases the default IP needs to be changed to match the system network. Please reference the L-IP Users Manual page 20 for instructions on how to change the IP address of the device. Note 2: In our example there is only one L-IP, so it is configured as the configuration server. Remember: One L-IP within any Vista Server system has to be configured as the configuration server. Please reference page 52 of the L-IP users manual for instructions on how to set a L-IP as a configuration server. This document has the web instructions in step 12. Navigate to the windows control panel and open the Lonworks Interfaces application. In lonmaker 3.1 with LNS 3.1 the program will be lonworks IP channels: Within the Lonworks Interfaces application choose the IP-852 tab: Under network interface click the Add button: In the Network Interface Add window you will need to name your connection. In this example it is just simply named IP for the IP channel within LNS. The IP Address should be set to the local IP of the computer. The IP Port should be left at the default 1628 and Channel Timing should be LAN. Click OK: Back within the LonWorks Interfaces application you should now see the named IP network, the IP address, and the IP port number: Next, Click the Test button to test the communications from LonWorks Interfaces to the L-IP configuration server: Check the box to Set the Configuration Server Address and type in the IP address of you configurations server L-IP router. The default IP port used in network interfaces is 1628 so requesting a communication test from the L-IP requires the configuration server return port to be set to 1629. Then click the Start Test button: After clicking Start Test you will see a message verifying the test has started. If your test is successful you will see the following message: Your Lonworks Network Interfaces is now configured for a TCPIP connection and properly setup to communicate to a Loytec L-IP router configured as a configuration server. If you never receive a message showing a successful test, please proceed to step 9. Login to the L-IP web interface by opening a web browser and typing the IP address of the device. In our example it is http://10.159.5.39. This is the default web page within the L-IP web interface: Click the Config button: You will now be prompted to login to the controller. The default username is Administrator and the default password is admin Note: for new version of L-IP, its username is admin and password is loytec4u. Click on EIA-852 Server and make sure the Config server status is enabled and the Config server port is 1629. If any changes are necessary, a message will appear at the bottom of the web page to reboot the device for the changes to take effect. And if there are more than one LIP in this network, all the other LIPs apart from the first one need to choose disabled option for the Config server status. Click on EIA-852 Ch. List. In the channel list you should see your local L-IP device and IP address. The next step is to add the IP address of the HOST PC running the Lonworks Network Interfaces application. Click the Add Device button. Name your device. In this example it is named PC. Then type in the IP address and the port number of the HOST PC and click save. Click in the Recontact button and go back and repeat step 7. You should now see a successful test from your configuration server. If there are more than one LIP in the network, add all the other LIPs in this list. Now your Loytec L-IP router is communicating to the Lonworks Network Interfaces program. This will allow your LNS server to communicate on the IP channel connection within Lonmaker or NL220 and use this Loytec L-IP as its connection to the Lonworks network. Additional setup information is available here in the L-IP Users Manual.

Issue Certain Xenta controllers and I/O modules can accept 10k thermistor temperature inputs. Product Line EcoStruxure Building Operation,TAC Vista Environment Xenta 102-AX Xenta 420A, Xenta 450A Cause The Xenta 102-AX has always used 10k thermistors. Now some of the I/O modules and programmable controllers also have an option for 10k thermistor inputs. A common question is -- what type of 10k thermistors? Type 2? Type 3? Resolution The reason there is no reference to 10k Type 2 or 10k Type 3 is because these are Continuum-specific terms. The 10k thermistor that is compatible with Xenta 42XA and 45XA I/O modules are the same that I/NET uses. They are Vishay Dale Curve #1. View this PDF for the Resistance vs. Temperature Conversion Tables for this thermistor.

Issue Certain Xenta controllers and I/O modules can accept 1.8k thermistor temperature inputs. Product Line TAC Vista Environment Xenta 121-FC Xenta 200 Xenta 300 Xenta 420A Xenta 450A Cause What is the temperature vs resistance curve of the 1.8k thermistors for Xenta 300? Resolution All Xenta controllers and I/O modules, except the Xenta 102-AX use the same 1.8k thermistor (type 1.8KA1). The following table shows details the Temperature vs. Resistance characteristics for this thermistor. Temp (°C) Minimum kΩ Nominal kΩ Maximum kΩ -50.0   60.87  63.88  67.03  -45.0   45.41  47.5   49.68  -40.0   34.23  35.68  37.2   -35.0   26.04  27.07  28.13  -30.0   19.99  20.72  21.47  -25.0   15.48  16.0   16.54  -20.0   12.09  12.46  12.84  -15.0   9.512 9.779 10.05  -10.0   7.541 7.733 7.929 -5.0   6.021 6.16  6.301 0.0   4.84  4.94  5.042 5.0   3.916 3.988 4.061 10.0   3.189 3.24  3.293 15.0   2.612 2.649 2.686 20.0   2.151 2.177 2.209 25.0   1.782 1.8   1.818 30.0   1.478 1.496 1.514 35.0   1.233 1.25  1.267 40.0   1.033 1.049 1.065 45.0   0.8698 0.8848 0.9001 50.0   0.7357 0.7497 0.7639 55.0   0.6251 0.638 0.6511 60.0   0.5334 0.5453 0.5573 65.0   0.457 0.4679 0.479 70.0   0.3931 0.4031 0.4132 75.0   0.3395 0.3485 0.3578 80.0   0.2942 0.3025 0.311 85.0   0.2559 0.2634 0.2712 90.0   0.2233 0.2302 0.2373 95.0   0.1956 0.2019 0.2083 100.0   0.1718 0.1775 0.1835 105.0   0.1514 0.1566 0.1621 110.0   0.1338 0.1386 0.1436 115.0   0.1186 0.123 0.1276 120.0   0.1054 0.1095 0.1136 125.0   0.094 0.0977 0.1015 130.0   0.084 0.0874 0.0909 135.0   0.0753 0.0784 0.0816 140.0   0.0676 0.0705 0.0735 145.0   0.0609 0.0635 0.0663 150.0   0.0549 0.0574 0.0599

Issue The OrOr object in MNB controllers always reports that it is "ON". Product Line TAC IA Series Environment I/A Series WorkPlace Tech I/A Series MNB Controllers  Cause  Input to the OrOr object is inverted and has nothing attached to it. When an "OR" input property of a logic object is inverted with nothing attached to it, the input will be seen as an "Off," resulting in an output of 100. Resolution If the input of an OrOr object is not connected to I/A Series BACnet controller, an "OR" input should not be inverted.   If another object outputting a "NA" is attached,  the "OR" input will function correctly.

Issue When directly connected to a Xenta programmable controller through a serial cable, and observing live Menta, it is possible to override inputs and outputs.  This override is the same override attribute that can be set from the OP and from the Workstation. Environment Menta Xenta programmable Xenta 280, 281, 282, 283, 300, 301, 302, 401, 401:B Cause Overriding points while simultaneously witnessing live updates of all program values is an effective troubleshooting technique. Resolution Directly connect live to a Xenta Programmable Download the correct Menta file to the hard drive of a laptop. Right click on the controller in Workstation and select Edit. File > Save As ... to the hard drive. The Menta file must exactly match what currently is downloaded into the controller or else it won't connect. Connect to the RS-232 port on the face of the Xenta programmable. Open the Menta file. Options > Simulate Click the Online button in the top left corner. Select "Connect" from the menu. View I/O and override Options > I/O Configuration This brings up a list of all inputs and outputs in the controller.  The last column says "Not overridden" for any point not currently overridden.  If it is, it will show the override value.  Choose a point and click the Override button at the bottom. Check the box to override and enter the desired value.  Click OK. The point is now in override. NOTE: This override attribute is the same override that is available through the OP and through Vista Workstation.  Points can be put into override and taken out of override from any of these 3 locations and it will dynamically update any other concurrent users.

Issue At times numbered errors pop up in Cyberstation or you may see a numbered error in the Error Listview Product Line Andover Continuum Environment Continuum Cyberstation Windows Cause Numbered errors appear in Cyberstation or in an Error Listview and an explanation is needed for troubleshooting Resolution With Continuum running and with the focus on the main Continuum screen or Continuum Explorer, press F1 to bring up the help menu Select index Type in ‘error’ Select Error Messages, Cyberstation This displays a list of some of the error messages that may come up in Cyberstation. This is not a comprehensive list and it doesn’t provide solutions, but gives an initial idea of what is happening for troubleshooting.   Below is the error list that you will find in the Help   OS Error Messages Error Hex Code Error text 1 0x0001 No message block available 2 0x0002 No message queue available 3 0x0003 Invalid message block 4 0x0004 Invalid message size 5 0x0005 Message is blocked 6 0x0006 Can't deallocate message, it is on a queue 7 0x0008 Invalid message queue 8 0x0008 Invalid message blocking order 9 0x0009 Invalid process ID 10 0x000A Duplicate queue ID 11 0x000B Timed out waiting for message CPL Error Messages Error Hex Code Error text 1024 0x0400 Name has more than 16 characters 1025 0x0401 Comment has more than 132 characters 1026 0x0402 Comment has more than 132 characters 1027 0x0403 Symbol(s) are not from the correct set 1028 0x0404 Field is too long to display 1029 0x0405 Statement or expression is not correct 1030 0x0406 Array is longer than 32,767 entries 1031 0x0407 FOR and NEXT use different index var names 1032 0x0408 GOTO is not allowed inside a loop 1033 0x0409 Fatal, not enough free memory 1034 0x040A Same line name given to more than one line 1035 0x040B No line has this line name 1036 0x040C Same name for more than one local variable 1037 0x040D No item with that name exists 1038 0x040E Cannot define any more local variables 1039 0x040F BREAK or CONTINUE is outside a loop or block 1040 0x0410 Same name or number for more than 1 argument 1041 0x0411 Operation is not available 1042 0x0412 Number is not valid 1043 0x0413 Number cannot be longer than 132 digits 1044 0x0414 Fatal, bad stack address 1045 0x0415 Fatal, illegal stack operation 1046 0x0416 No function with that name exists 1047 0x0417 Attributes do not apply to local variables 1048 0x0418 No quotation marks at end of string 1049 0x0419 Data type is not same as field type 1050 0x041A Data has more chars than field allows 1051 0x041B Record has too many or too few fields 1052 0x041C More records than RECORD statement allows 1053 0x041D Date or time is not valid 1054 0x041E Path name has too many names 1055 0x041F Attribute does not apply to the item type 1056 0x0420 Local variable name cannot be an argument 1057 0x0421 Incorrect array entry type 1058 0x0422 Alarm expression is too long 1059 0x0423 You cannot set that item value 1060 0x0424 You cannot change that attribute value 1061 0x0425 Name is not a program or function name 1062 0x0426 Cannot enable/disable all of one type 1063 0x0427 You must give a name of a local data file 1064 0x0428 Parser stack overflow 1065 0x0429 Cannot use that var as FOR...NEXT index var 1066 0x042A Data file is too long 1067 0x042B You cannot change value of system variable 1068 0x042C Statement is too long 1069 0x042D 0, C or E is a reserved line name 1070 0x042E Feature not available on this controller 1071 0x042F Number must be an integer 1072 0x0430 Passed too many arguments to a function 1073 0x0431 An argument index must be from 1 to 15 1074 0x0432 No chars allowed after continuation symbol 1075 0x0433 Cannot run or stop program from command line 1076 0x0434 Report files are not supported yet 1077 0x0435 Unknown command option 1078 0x0436 Name given is not a controller name 1079 0x0437 Command is valid only from the command line 1080 0x0438 Command is valid only in a program or function ITP Messages Error Hex Code Error text 2048 0x0800 Tried to set item you cannot set 2049 0x0801 Set point or var to value of wrong type 2050 0x0802 Tried to use local var that does not exist 2051 0x0803 An expression uses an operand incorrectly 2052 0x0804 Must set HOUR to value from 0 to 23 2053 0x0805 String is too long 2054 0x0806 Operation is not available 2055 0x0807 Scanner runtime stack overflow 2056 0x0808 Used an incorrect function argument 2057 0x0809 Tried to print to a non-string item 2058 0x080A Tried to rotate prog to nonexistent line 2059 0x080B Used an item type when it is not allowed 2060 0x080C Tried to divide a value by zero 2061 0x080D Gave an array entry that does not exist 2062 0x080E Gave non-numeric var as array index 2063 0x080F Gave more or less arguments than allowed 2064 0x0810 Date or time is not valid 2065 0x0811 Executed too many statements on one line 2066 0x0812 Function did not give the expected result 2067 0x0813 FOR...NEXT loop index variable not numeric 2069 0x0815 Invalid import point address 2070 0x0816 Used name that is not a data file name 2071 0x0817 Used rec or field data file does not have 2072 0x0818 Cannot read data file 2073 0x0819 Cannot write to data file 2074 0x081A Path name is not an actual path 2075 0x081B Attribute does not apply to the item type 2077 0x081D Tried to set attribute to an invalid value DCP Error Messages Error Hex Code Error text 3072 0x0C00 Operation is not available 3073 0x0C01 String is too long 3074 0x0C02 Fatal, not enough free memory 3075 0x0C03 Exceeded number of displayable lines 3076 0x0C04 Invalid import point address 3077 0x0C05 Statement is too long 3078 0x0C06 Controller cannot find an item 3079 0x0C07 Controller cannot open a file of this type 3080 0x0C08 Date or time is not valid OMS Error Messages Error Hex Code Error text 5121 0x01401 Cannot find the item 5122 0x01402 Reached end of the list 5123 0x01403 Attribute does not apply to the item 5124 0x01404 Name is too long 5125 0x01405 Attribute is inappropriate 5126 0x01406 Cannot access file on other controller 5127 0x01407 FatalErr__ Gave invalid hash table size 5128 0x01408 Not enough memory 5129 0x01409 SysErr__ Passed invalid info to database 5130 0x0140A Item is being used and not available now 5131 0x0140B Access to the item denied 5132 0x0140C Array index too large or too small 5133 0x0140D SysErr__ Invalid format for retrieving data 5134 0x0140E Cannot associate these items 5135 0x0140F No relationship of the type defined for item 5136 0x01410 SysErr__ Passed invalid setup to database 5137 0x01411 Reached end of the list of related items 5138 0x01412 Line is too long 5139 0x01413 Value does not apply to the attribute 5140 0x01414 File read error 5141 0x01415 Duplicate item name 5142 0x01416 SysErr__ Cannot set/get attribute 5143 0x01417 SysErr__ Terminal communication error 5144 0x01418 Lbus creation failed 5145 0x01419 String display failed 5146 0x0141A SysErr__ Cannot access the item in database 5147 0x0141B Incorrect path name 5148 0x0141C Incompatible value 5149 0x0141D SysErr__ Invalid message queue Id 5150 0x0141E SysErr__ Session not found 5151 0x0141F Attribute not defined yet 5152 0x01420 Invalid auto-conversion 5153 0x01421 Zero string size 5154 0x01422 Not allowed to delete a system variable 5155 0x01423 SysErr__ System hash tables locked 5156 0x01424 The class object list locked 5157 0x01425 Duplicate handle Id 5158 0x01426 Not enough memory - reset log array size 5159 0x01427 HardwareErr__ Bad RTC chip 5160 0x01428 Duplicate serial number 5161 0x01429 Duplicate Infinet Id number 5162 0x0142A Infinet learn mode is in process 5163 0x0142B Line name is undefined 5164 0x0142C SysErr__ Reserved line label 5165 0x0142D Unable to send the message 5166 0x0142E Dump process stopped 5167 0x0142F Controller not found 5168 0x01430 Invalid handle Id 5169 0x01431 Incorrect line or statement 5170 0x01432 Missing end of controller statement 5171 0x01433 Does not know the type 5172 0x01434 Not allowed to set the attribute 5173 0x01435 Not allowed to set the description 5174 0x01436 Not allowed to set the format 5175 0x01437 Not allowed to set the engineering unit 5176 0x01438 Item already exists 5177 0x01439 Not allowed to set the attribute 5178 0x0143A SysErr__ Invalid controller path 5179 0x0143B SysErr__ Invalid current controller message 5180 0x0143C Invalid response from other controller 5181 0x0143D Item is already being used 5182 0x0143E File is being saved by another operator 5183 0x0143F File is too long 5184 0x01440 Cannot access the item on other controller 5185 0x01441 SysErr__ Passed invalid indicator to database 5186 0x01442 Invalid Energynet ID 5187 0x01443 Invalid Infinet ID 5188 0x01444 Invalid Infinet port 5189 0x01445 Missing end of dictionary statement 5190 0x01446 Missing end of import/export statement 5191 0x01447 Unable to compile the file 5192 0x01448 Invalid dump file statement 5193 0x01449 Missing end of block statement 5194 0x0144A Missing end of code statement 5195 0x0144B Missing end of object statement 5196 0x0144C Unable to rename the controller 5197 0x0144D Unable to rename the comm port 5198 0x0144E Item has no type 5199 0x0144F Undefined alarm 5200 0x01450 Attribute can only be retrieved, not set 5201 0x01451 Conversion too long 5202 0x01452 Not allowed to retrieve the attribute value 5203 0x01453 No default format defined 5204 0x01454 SysErr__ Passed invalid indicator to database 5205 0x01455 Invalid schedule type 5206 0x01456 Missing colon in the statement 5207 0x01457 Incorrect name 5208 0x01458 Incorrect header for the code block 5209 0x01459 Incorrect header for a sub block 5210 0x0145A Incorrect header for the object block 5211 0x0145B Undefined system variable 5212 0x0145C Undefined comm port 5213 0x0145D Not allowed to create an alarm 5214 0x0145E Inappropriate request for the comm port 5215 0x0145F Invalid mode for the comm port 5216 0x01460 LBus is already set up 5217 0x01461 Invalid program file 5218 0x01462 Program is already in the firing order 5219 0x01463 Unable to access the item 5220 0x01464 No response to the Infinet token pass 5221 0x01465 NetworkErr__ Received incorrect CRC on Infinet 5222 0x01466 SysErr__ Invalid error value from Infinet 5223 0x01467 Attribute does not apply to the point type 5224 0x01468 Attribute does not apply to the port type 5225 0x01469 Item must be a program 5226 0x0146A File must be open 5227 0x0146B File took too long to open 5228 0x0146C Cannot alter the file 5229 0x0146D Cannot add or remove records 5230 0x0146E The relationship is already set up 5231 0x0146F CAnnot dump dictionary block of controller 5232 0x01470 Cannot dump the controller 5233 0x01471 Cannot dump associated items 5234 0x01472 Undefined IOU number 5235 0x01473 Invalid channel number 5236 0x01474 No free alarm links 5237 0x01475 Cannot access next Enet controller in list 5238 0x01476 Cannot access next Infinet controller in list 5239 0x01477 Incorrect header for the log array block 5240 0x01478 Invalid log array index 5241 0x01479 Cannot modify the file 5242 0x0147A Unable to create the Infinet controller 5243 0x0147B Zero is not a valid serial number 5244 0x0147C Invalid baud rate 5245 0x0147D Comm port is not set up for Infinet 5246 0x0147E Controller is not online 5247 0x0147F Not allowed to delete a comm port 5248 0x01480 Cannot define any more handle IDs 5249 0x01481 Invalid controller name 5250 0x01482 Invalid Infinet controller name 5251 0x01483 Invalid Energynet controller network ID 5252 0x01484 Controller doesn't know Infinet ID 5253 0x01485 Invalid electrical type 5254 0x01486 Invalid DateTime value 5255 0x01487 Invalid log type 5256 0x01488 Invalid floating point number 5257 0x01489 Attribute doesn't exist for the item 5258 0x0148A Access to the conversion denied 5259 0x0148B Number of array entries is too  arge 5260 0x0148C Invalid program status 5261 0x0148D Unable to access the comm port 5262 0x0148E Cannot overwrite the item 5263 0x0148F New default mode is current mode 5264 0x01490 Cannot set export flag for Enet controller 5265 0x01491 Operation is not supported 5266 0x01492 SysErr__ Unused sched events are inaccessible 5267 0x01493 Sched occup/unoccup variable not DateTime 5268 0x01494 Holiday schedule doesn't exist 5269 0x01495 Import/Export item must be a point 5270 0x01496 Point must export to controller/alarm 5271 0x01497 Sched occupancy flag not output/numeric point 5272 0x01498 Item is not a holiday schedule 5273 0x01499 Cannot dump the import/export block 5274 0x0149A Cannot set up the port 5275 0x0149B Index number for the alarm is too large 5276 0x0149C Invalid state 5277 0x0149D Comm port is busy 5278 0x0149E Reference array is full 5279 0x0149F Undefined alarm type 5280 0x014A0 Item is not local controller 5281 0x014A1 HardwreErr__ Bad EEPROM chip 5282 0x014A2 Cannot retrieve controller model number 5283 0x014A3 Cannot retrieve controller serial number 5284 0x014A4 Unspecified Enet ID 5285 0x014A5 Undefined controller model number 5286 0x014A6 Controller has no assigned Infinet port 5287 0x014A7 Cannot find controller in the Infinet list 5288 0x014A8 Invalid password 5289 0x014A9 Cannot retrieve controller version number 5290 0x014AA Handle ID is out of range 5291 0x014AB Not allowed to delete user ACC 5292 0x014AC Not allowed to use this many Infinet devices 5293 0x014AD Not allowed to change user ACC's security level 5294 0x014AE Full path is not set 5295 0x014AF Access denied 5296 0x014B0 User passwords are mismatched 5297 0x014B1 User doesn't exist on remote controller 5298 0x014B2 Invalid stop bits 5299 0x014B3 Invalid data length 5300 0x014B4 The user is logged in 5301 0x014B5 Not allowed to change user name 5302 0x014B6 Not allowed to delete this controller 5303 0x014B7 No TankProbe extension block installed 5304 0x014B8 No TankNet exists 5305 0x014B9 TankNet is already set up 5306 0x014BA Can't change a TankProbe to another electrical type 5307 0x014BB Duplicate PIN 5308 0x014BC There is no card information available for this person 5309 0x014BD Invalid card entry 5310 0x014BE Duplicate card 5311 0x014BF Invalid schedule 5312 0x014C0 Attribute does not apply to object type 5313 0x014C1 Undefined card type 5314 0x014C2 Invalid PIN value 5315 0x014C3 Same area on both sides of a door is not allowed 5316 0x014C4 The maximum number of doors allowed has been reached 5317 0x014C5 Personnel cleanup in progress.  Please try again. 5318 0x014C6 Unable to delete one or more personnel objects on rip 5319 0x014C7 Personnel distribution in process.  Please try again. 5320 0x014C8 Not allowed to set an area in a DefaultDoor 5321 0x014C9 Unable to set remote sync bit for one or more personnel objects 5322 0x014CA Could not synchronize CX and SX databases 5327 0x014CF Event log size has been automatically adjusted 5328 0x014D0 No XDriver code module installed 5329 0x014D1 XDriver code module installed 5330 0x014D2 XDriver code module incomplete 5331 0x014D3 Checksum error detected in S-record 5334 0x014D6 Duplicate XDriver parameter 5338 0x014DA Invalid IP parameter 5339 0x014DB Invalid Subnet Mask for the IP class 5340 0x014DC IP network number should not equal 0 5341 0x014DD IP host number should not be all 1s 5342 0x014DE Possible Infinet bus short detected 5345 0x014E1 Update operation still in progress 5348 0x014E4 Invalid NetWare frame type 5349 0x014E5 UTC Offset is out of range 5350 0x014E6 No personnel cache entries available 5351 0x014E7 Memory expansion board not installed 5352 0x014E8 Flash memory operation failure 5353 0x014E9 Too many IOUs 5354 0x014EA The maximum number of areas allowed has been reached 5355 0x014EB Attempt to lock door has failed 5356 0x014EC Attempt to unlock door has failed 5357 0x014ED OMS database has become corrupt 5358 0x014EE OMS internal error 5359 0x014EF Buffer too small for data requested 5360 0x014F0 OMS database not currently available (backing up) 5361 0x014F1 String size exceeds implementation limit 5362 0x014F2 Backup disabled due to excessive use (requires manual enable) 5363 0x014F3 Schedule events are out of order 5364 0x014F4 Invalid bookmark for error log 5365 0x014F5 Duplicate SmartSensor control point 5366 0x014F6 Inappropriate value for current restart mode 5367 0x014F7 Copy protection violation has occurred —  please contact your ACC dealer 5368 0x014F8 Error sending CustomABAFormat string to IOU module 5369 0x014F9 OBJ_ERR_BACnet_ERROR  - A BACnet error occurred. 5370 0x014FA OBJ_ERR_DABL_OVERFLOW - The controller has reached its BACnet device binding limit. LAN Error Messages Error Hex Code Error text 6144 0x1800 Comm user return 6145 0x1801 Comm invalid message length 6146 0x1802 Comm invalid destination address 6147 0x1803 Comm invalid source address 6148 0x1804 Comm invalid QID 6149 0x1805 The port is not an Infinet 6150 0x1806 The controller is not responding 6151 0x1807 Comm LAN reconfig in progress 6152 0x1808 The controller is offline 6153 0x1809 The EnergyNet is not configured 6154 0x180A Comm destination node paused 6155 0x180B Send request timeout 6156 0x180C Send error 6157 0x180D NULL message received 6158 0x180E Unable to send message 6159 0x180F Invalid EnergyNet node ID 6160 0x1810 Duplicate Ethernet ID 6161 0x1811 Duplicate EnergyNet ID 6162 0x1812 Out of memory 6163 0x1813 Ethernet RAM test faillure 6164 0x1814 Undefined EnergyNet ID 6165 0x1815 Undefined Ethernet ID GLB Error Messages Error Hex Code Error text 7169 0x1C01 Symbol name too long 7170 0x1C02 Invalid characters in symbol 7171 0x1C03 Symbol cannot be a system variable 7172 0x1C04 No items 7173 0x1C05 Too many items 7174 0x1C06 First character must be alpha 7175 0x1C07 System internal error 7176 0x1C08 System clock was changed IES Error Messages Error Hex Code Error text 8192 0x2000 Cannot build IE API request 8193 0x2001 Cannot send IE API request 8194 0x2002 IES has bad OMS pointer 8195 0x2003 IE handle points to wrong network address 8196 0x2004 IE handle is invalid 8197 0x2005 IE bad data in ObjKey 8198 0x2006 IE API response not received 8199 0x2007 IE no Infinet 8200 0x2008 Could not establish import 8201 0x2009 IE database locked LBS Error Messages Error Hex Code Error text 9217 0x2401 LBus not ready 9218 0x2402 wait_collect or wait_update timeout 9219 0x2403 Invalid IOU number 9220 0x2404 LBus database is locked 9221 0x2405 An active IOU exists 9222 0x2406 LBus error no memory 9223 0x2407 Comm channel specified is invalid 9224 0x2408 Sensor's channel is invalid 9225 0x2409 LBus does not exist 9226 0x240A The IOU number has not been defined yet 9227 0x240B Bad electrical type 9228 0x240C Value is too large or too small 9229 0x240D IOU communication status = online 9230 0x240E IOU communication status = offline 9231 0x240F IOU number is not between 1 and 16 IOS Error Messages Error Hex Code Error text 10240 0x2800 NULL 10241 0x2801 Type not valid for this IO channel 10242 0x2802 IO channel number out of range 10243 0x2803 IO channel already assigned 10244 0x2804 Vref out of tolerance 10245 0x2805 IO channel is unassigned 10246 0x2806 Tri-state partner is already assigned 10247 0x2807 AD converter trashed 10248 0x2808 AD converter timed out 10249 0x2809 Reference channels not initialized 10250 0x280A Adjacent channel is already in use 10251 0x280B Invalid channel for RTD use 10252 0x280C Cannot delete IOU module until all associated objects are moved to other IOU modules or deleted 10253 0x280D Duplicate module ID 10254 0x280E Insufficient memory for IO operation 10255 0x280F IO module is not commissioned 10256 0x2810 Incorrect channel type 10257 0x2811 Channel doesn't exist 10258 0x2812 Error installing IO system 10259 0x2813 Error in IO database 10260 0x2814 Module is not saved 10261 0x2815 Attribute does not exist 10262 0x2816 IO message queue does not exist 10263 0x2817 Illegal IO queue designator 10264 0x2818 IO module number is too large 10265 0x2819 IO queue is full 10266 0x281A No IO message buffers available 10267 0x281B Unknown IO message buffer size 10268 0x281C IO routing table section doesn't exist 10269 0x281D IO routing table entry not saved 10270 0x281E IO module response was lost 10271 0x281F IO MIP interface initialization error 10272 0x2820 No response from IO module 10273 0x2821 Illegal message received from IO module 10274 0x2822 IO module message data error 10275 0x2823 IO module message is not a service pin message 10276 0x2824 No IDs available for IO module commissioning 10277 0x2825 Too many IO modules for the controller 10278 0x2826 IO module domain update error 10279 0x2827 IO module read memory command failed 10280 0x2828 IO module update address command failed 10281 0x2829 IO module update NV cnfg table failed 10282 0x282A No message tags available for IO message 10283 0x282B Not a suitable replacement IO module 10284 0x282C Error in routing IO module response 10285 0x282D Incorrect response from IO module INF Error Messages Error Hex Code Error text 11264 0x2C00 NULL 11265 0x2C01 Comm port cannot connect an Infinet 11266 0x2C02 Comm port already set up for another purpose 11267 0x2C03 Comm port has not been assigned a purpose 11268 0x2C04 No Infinet controller with that serial number 11269 0x2C05 Infinet is not set up 11270 0x2C06 Infinet ID is already in use 11271 0x2C07 ID is not valid for Infinet 11272 0x2C08 Message received is not for an Infinet controller 11273 0x2C09 Controller received message from an unknown source 11274 0x2C0A Learn mode currently in use 11277 0x2C0D Learn already in process on this port 11280 0x2C10 Infinet controller is not responding 11281 0x2C11 NULL buffer passed to Infinet server 11282 0x2C12 Message type is not supported by Infinet server I2LD Error Messages Error Hex Code Error text 202752 0x31800 No model matching download header exists on this CX 202753 0x31801 Error found in I2 download header 202754 0x31802 Error found in I2 model information 202755 0x31803 Models in I2 download exceeds maximum 202756 0x31804 Received download message type out-of-service 202757 0x31805 Begin I2 download header not received 202758 0x31806 Comm Error - socket receive 202759 0x31807 Comm Error - socket send 202760 0x31808 No comm buffers available 202761 0x31809 Download state machine error 202762 0x3180A Illegal message type response from Infinet controller 202763 0x3180B Listen call failed 202764 0x3180C Bind call failed 202765 0x3180D Socket call failed 202766 0x3180E Received short packet - not enough data 202767 0x3180F Application type unknown by I2 202768 0x31810 Download model does not match I2 model 202769 0x31811 Unknown/unsupported message type 202770 0x31812 I2 download out-of-sync 202771 0x31813 I2 received unknown/unsupported packet type 202772 0x31814 I2 received segment that exceeds block storage 202773 0x31815 I2 received block address out-of-range for flash 202774 0x31816 I2 detected end of download CRC error 202775 0x31817 I2 does not support download revision 202776 0x31818 I2 is running in boot loader mode 202777 0x31819 I2 total received block count does not match 202778 0x381A I2 detected external RAM failure 202779 0x3181B I2 malloc failure during boot-up 202780 0x3181C I2 detected unknown flash device

Issue Supplemental Documentation on the Menta OPT block for optimized start and stop. Product Line TAC Vista, EcoStruxure Building Operation Environment Menta Function Block Cause The document below is intended to clarify the inputs and configuration parameters of the Menta OPT block and when/how to use them. Resolution Click here to download the example Menta macro A Brief Overview of Optimized Control Optimal Start Optimal Start measures how long it takes a room temperature to reach setpoint each morning when the air-handling unit is enabled. These measurements are then used to predict how long it will take the next time. As time goes on, the predictive algorithm is refined until it becomes quite accurate. An optimally started unit saves energy by only starting as early as is needed, not just an arbitrary hour or two before occupancy. Optimal Stop Optimal Stop is less common. An optimally stopped unit stops running prior to the end of the day. It measures how long it takes before the measured room temperature drifts outside of an acceptable range around the setpoint. This saves energy on cooling a building until 5:00pm (for example) when the occupants are just about to walk out the door. The example in this document will not implement Optimal Stop. Inputs to the OPT Block RoT Room Temperature. If there is just one room temperature sensor being served by the optimally started unit, then this is where it would be used. However, if the unit has several room temperatures or serves many VAV terminal units, consider the following options: Average all temperatures Pick one interior zone Highest room temperature for cooling/lowest room temperature for heating Use return air temperature In all of these scenarios, some consideration should be made for if the input sensors fail: Averaging all temperatures is the most robust method. However, if SNVT inputs are used, it may be necessary to discard invalid values (621.8°F) from the averaging calculation. If one interior zone is used and the temperature sensor fails, the unit will eventually revert to starting as early as is allowed every day. The default value for this is 12 hours early; the example in this document uses 2 hours. If the primary sensor fails, use a secondary, or disable optimal start on a failed condition. Instead of the highest and lowest room temperatures, it may be wise to use the second highest and the second lowest room temperature. This allows for one failed sensor in each direction before the Optimal Start calculation is affected. Using return air theoretically is a lot like using the average of all room temperatures. Adjusting the setpoint to get the desired result might be required. A failed sensor input should disable the Optimal Start calculation. SP Setpoint. Using two OPT blocks – one for Optimal Start cooling, one for Optimal Start heating – allows each to be fine tuned. If there is a morning warm-up sequence, then the heating Optimal Start may be much quicker than the cooling. Using one block requires the internal calculation to adjust as the needs change from cooling to heating, and can be less agile when switching from cooling to heating requirements. OuT Outdoor Temperature. Resets to the curve occur based on the outside air temperature. If it is very cold or very hot outside, the unit will start sooner. This curve is reset automatically as time goes on to better predict the effect outside air temperature has on the controlled space (if AutoAdjust > 0). OpI Operation Indication. In the example of an air-handling unit, OpI would be the fan status. If the configuration parameter OperIndicF is set to 1, then this will be used for internal calculations. Otherwise, it will just use the command as status. This prevents a mechanically failed unit from affecting the calculation. A good rule to follow is if fan status is available, use it. TmL Time left. A time schedule (TSCH) input goes here. This tells the calculation how much time is left before the unit is scheduled to turn on (or off). The OPT block then starts the unit early based on this number. It also ensures that the unit always runs during the scheduled occupied time. Mode Mode is for heating/cooling or enabled/disabled. It is advantageous to always program in a method for disabling Optimal Start through a public variable (PVB). Many times the seeming complexity of Optimal Start is found to be undesirable by building operators and they will ask to have it disabled. Mode could be programmatically set for heating/cooling based on outside air temperature (or some other factor), but in the example in this document, two separate OPT blocks are used and are hard-coded for their respective modes. Configuration Parameters of the OPT Block AutoAdjust AutoAdjust refers to whether or not the OPT block gets smarter by adjusting the curves set initially on the first download. If AutoAdjust is set to 0, then the OPT block will still adjust the start time every day based on the room temperature and outside air temperature, but it will not adjust those early start times based on past experience. Set the AutoAdjust to 1, and the curves will adjust a little every day. Set AutoAdjust to 2 and the OPT block will also adjust the holiday compensation (the unit will start a little earlier after a 3-day weekend, but may need to learn exactly how much as time goes by). To maximize the potential of the OPT block, it is suggested to set this value to 2. RoomTempF Room Temperature Flag. Is a room temperature sensor present? Without a room temperature sensor, it is not possible for the OPT block to adjust its curves. It is guessing at that point based on pre-determined curves. It is not recommended to use OPT without a room temperature sensor. OperIndicF Operation Indication Flag. If OperIndicF is set to 1, then the OpI input will be used for internal calculations. Otherwise, the OpI input is ignored and the command is used as status. This prevents a mechanically failed unit from affecting the calculation. A good rule to follow is if fan status is available, use it. StartTimeLo Start Time at Low Outside Air Temperatures. When it is cold outside, how much earlier should the unit start? This will change between a cooling and a heating optimal start block. If AutoAdjust is set to 1 or 2 then this is just a default value. It will adjust as needed each day, but a good default value is important. StartTimeHi Start Time at High Outside Air Temperatures. When it is hot outside, how much earlier should the unit start? This will change between a cooling and a heating optimal start block. If AutoAdjust is set to 1 or 2 then this is just a default value. It will adjust it as needed each day, but a good default value is important. HolidayComp Holiday Compensation. This is the default compensation for a holiday (longer than 48 hours of continuous unoccupied time). The value is a percentage. If there is a 3-day weekend, how much earlier should the unit start on the following Tuesday? If AutoAdjust is set to 2 then this is just a default value. It will adjust it as needed each day, but a good default value is important. MaxStartTi Maximum Start Time. This is the maximum amount of hours the unit is permitted to start prior to the occupied time. The default value is 12 hours. The first time the unit is downloaded, it will start this early and measure how long it takes to achieve setpoint. 12 hours is very early. The example in this document uses 2 hours. Even if something goes wrong with the internal calculation (failed sensor input, for example) the earliest it could start would be 2 hours early. ETol Error Tolerance. How close to the desired setpoint does the temperature sensor need to be to be considered at setpoint? An error tolerance of 0.5°F is default and is usually acceptable. StopLoTemp, StopTimeLo, StopHiTemp, StopTimeHi, StopTimeErr All of these parameters refer to the Optimal Stop portion of the OPT block. Setting them to 0 disables the Optimal Stop functionality. Output of a OPT Block There are three possible output values of an OPT block: 0 = The unit is off, unoccupied 1 = The unit is on, occupied 2 = The unit is on, optimally started Putting It Into Practice The example below is a Menta Hierarchy Function Block (HFB) and shows HFB inputs to the blocks. The top OPT block is set to heat mode and looks to a heating setpoint. The bottom OPT block is set to cool mode and looks to a cooling setpoint.   OPT_START_HEAT OPT_START_COOL AutoAdjust 2 2 RoomTempF 1 1 OperIndicF 1 1 StartTimeLo 60 0 StartTimeHi 0 60 HolidayComp 0 0 MaxStartTi 2 2 Etol 0.5 0.5 StopLoTemp 0 0 StopTimeLo 0 0 StopHiTemp 0 0 StopTimeHi 0 0 StopTimeErr 0 0 Using the hints and tips suggested will allow not only for proper programming techniques, but also for creation of macro libraries that can be reused and shared to improve effectiveness across business units.

Issue When copying a graphic point, symbol, bitmap, table or anything from one page to another, everything is placed to the upper left of the new page and is all jumbled up. The user has to move each one separately and the attributes do not remain the same. In I/NET 2.40 and above Windows will still cause text object to be placed in the upper left hand corner. This also occurs in the Windows Paint program. Environment I/NET Seven revision 2.16 and higher, but below 2.40 I/NET 2.40 and above Cause Copying a graphic point, symbol, bitmap, table or anything from one page to another. Resolution This issue is resolved in I/NET 2.40.  If upgrading is not an option: Contact PSS and request the patch that is available to fix this issue. Copy the files into the root directory of I/NET Run the graphic again Workaround for I/NET 2.40 and above Group the objects you wish to copy by pressing CTRL+G Copy the group Paste the group and move it as desired Ungroup the objects.

Issue Downloaded the WPT (WorkPlace Tech Tool) software.  How do I get a serial number so that I can complete the licensing form displayed with the "Purchase WorkPlace tech Software" program? Product Line TAC IA Series Environment WorkPlace Tech Tool 5.x.x Cause The WPT license generator program requires a "WIBS serial number" so that the license request can be generated. If the field is left blank, the program will not allow the license request to be generated.   Resolution The serial number is provided on purchased CDs so as to provide a method of tracing the manufactured CDs. To license the downloaded version of the Workplace Tech Tool software, you must enter an 8 digit serial number.  It is suggested, although not required, that you enter the current date as the serial number. When using the date as the serial number, enter the four digit year followed by the two digit month followed by the two digit day, i.e., in the format YYYYMMDD. For example, 20230203.

Issue Confusion over behavior of the Xenta 121 when using a occupancy sensor. Environment Xenta 121-FC Xenta 121-HP Cause When an occupancy sensor is not defined in the configuration of a Xenta 121 controller the effective occupancy will follow the command given by nviOccManCmd. However, when an occupancy sensor is defined, either as a network bound point or a hardwired sensor, the effective occupancy of a Xenta 121 will behave differently. Resolution The Xenta 121 operates as follows when using an occupancy sensor: The most notable difference in how the Xenta operates are: When nviOccManCmd is in either the OC_UNOCCUPIED or the OC_STANDBY modes then the Xenta 121 will ignore the state of the occupancy sensor. When nviOccManCmd is in the OC_OCCUPIED mode the Xenta 121 will follow the state of the occupancy sensor. Note that this means that the controller could actually enter the unoccupied mode even though nviOccManCmd is set to be occupied. When nviOccManCmd is in the Oc_Nul mode the effective occupancy of the Xenta 121 will Oc_Standby until a signal is received from the occupancy sensor at which time it will change to be Oc_Occupied. This behavior should be taken into consideration when deciding on how to implement an occupancy sensor. It may be desirable to set the nviOccManCmd to Oc_Nul whenever the occupancy sensor should be considered and to set it to Oc_Unoccupied when the occupancy sensor should be ignored. This effectively utilizes the occupied, unoccupied and standby modes as three distinct modes of operation to maximize comfort and efficiency.

Issue DC1100 / DC1400 Displays two horizontal black lines when powered up. Product Line Field Device Environment DC1100 / DC1400 Discrete Controller. Cause Cold Start has not been performed. Cold Start has been performed incorrectly. Mains borne corruption has affected processor. Resolution Carry out Cold Start: Isolate Controller power supply. Press and hold down "Enter" and "Exit" buttons. Keep "Enter" and " Exit" buttons depressed while restoring power. Display should show "Self Test" and "Initiating System Variables" Release "Enter" and "Exit" buttons. Controller may then be programmed in accordance with Data Sheet instructions.   Or, if the controller is non-recoverable, the DC1100 and DC1400 units are now obsolete. However, there are several 3rd party companies offering refurbished units, these can be found by using a browser and searching e.g. DC1100 repairs.    

Issue If the STR 350 plug-in is missing, then the STR 350/351 setup needs to be performed manually in NL220, LonMaker, TAC Vista Workstation, or TAC Menta. Product Line TAC Vista Environment TAC Vista 5.1.4, TAC Vista 5.1.5 Windows 7, Server 2008 Cause Not all plug-ins in the TAC ToolPack can run on Windows 7 or Windows 2008. Read details in TAC ToolPack plug-ins are not showing up. Resolution If the STR 350 plug-in is missing, then the STR 350/351 setup needs to be performed manually in NL220, LonMaker, TAC Vista Workstation, or TAC Menta. NL220 STR 350/351 setup steps are shown below: Use the STR 350 device template to create a new node on the channel. Note: the device template is located at C:\LonWorks\import\TAC\IO Modules (Default location) Double click on the STR 350/351 device and make necessary changes to any signal under “NVs” tab. TAC Workstation STR 350/351 setup steps are shown below: Expand the tree structure in the left panel. Select the desired signal to change in the right panel. If a STR 350/351 is connected to a programmable controller (Xenta 280/300/400), then the STR 350/351 can be added in the Menta file similar to an IO module. Setup steps are shown below: Under “Options/Device Specification” select “Add STR Module…" Under “Type” Select “STR350/351” and Under “Bit(s)”, choose the desired bit(s). Note: hover over each bit, there is a short description about the selected bit. If a STR 350/351 is connected to a Xenta Server (Xenta 7XX), then the STR 350/351 can be added in the Xbuilder project similar to an IO module. Setup steps are shown below: In Network panel,  under “LON", right click and select “Add IO Module->STR35X". Right click on the STR35X model just added, and select "Configure". A configuration pop up window will be displayed.  Make any desired changes. Note: Neuron ID can be manually typed in the Xbuilder or get from service pin in the Workstation. If choose to service pin, need to create and commission a LNS network in Workstation. Save and download the project. Below is a table of each bit in nciOption1 and nciOption2 and its brief description. nciOption1: Bit 0, 1: Fan type 00: No fan (Default) 10: On/Off fan 01: 2 speed fan 11: 3 speed fan Bit 2: Fan auto state 0: Not allowed (Default) 1: Allowed Bit 3: Fan off state 0: Not allowed (Default) 1: Allowed Bit 4: Fan speed 1 0: Not allowed (Default) 1: Allowed (On/Off fan type needs to be activated) Bit 5: Fan speed 2 0: Not allowed (Default) 1: Allowed (2 speed fan type needs to be activated) Bit 6: Fan speed 3 0: Not allowed (Default) 1: Allowed (3 speed fan type needs to be activated) Bit 7, 8 ,9: Not used   Bit 10: Temperature presentation 0: °C (Default) 1: °F Bit 11: Temp. normally displayed 0: Setpoint temperature (Default) 1: Room temperature Bit 12: Setpoint temp. presentation 0: Absolute temperature (Default) 1: Offset temperature Bit 13: Bypass button usage 0: Bypass (Default) 1: On/Off Bit 14: Not used   Bit 15: Supported protocols 0: Standard LonTalk protocol only 1: Standard LonTalk protocol and TAC proprietary protocol (Default) nciOption2: Bit 0, 1: Sunblind - Switch 1 00: On/Off (Default) 10: Up/Down 01: On/Off/Up/Down 11: Not used Bit 2, 3: Sunblind - Switch 2 00: On/Off (Default) 10: Up/Down 01: On/Off/Up/Down 11: Not used Bit 4: Light - Switch 1 0: Disable (Default) 1: Enable Bit 5: Light - Switch 2 0: Disable (Default) 1: Enable Bit 6, 7, 8: Local sensor 000: None (Default) 100: CO 2 010: RH 001: Occupancy Bit 9: CO 2 /RH value 0: Hidden (Default) 1: Display Bit 10-15: Not used