Building Automation Knowledge Base

Issue Values sent from a 102-AX via SNVT bindings are not making it to the receiving controller. Viewing the outbound SNVT on the 102-AX shows a value, but the inbound SNVT on another controller is invalid or a default value. Product Line TAC Vista, EcoStruxure Building Operation Environment Xenta 102-AX LNS SNVT bindings LonMaker NL220 Cause The Node Configuration parameters are set with a send heartbeat of 0 seconds, which tells the controller to never send an update on the output SNVT.  All 102-AXs come with a default send heartbeat of 0 seconds, so for them to function in an LNS network where they must send data to another controller, the send heartbeat must be set to something greater than 0 seconds. Resolution Open the Xenta 102-AX device Plug-in Go to the Node Configuration Tab Set the Node Minimum Send Time (SCPTminSendTime) to a non-zero value. The range is 0-6553.4 seconds. nvoSpaceTemp nvoStatOccBtn nvoSetPtOffset nvoLocalOccLatch nvoEmergCmd nvoUnitStatus nvoBoxFlow nvoTerminalLoad nvoEffectSetPt nvoFlowControlPt nvoOccpncyStatus Set the Node Send Heartbeat (SCPTmaxSendTime) to a non-zero value. The range is 0-6553.4 seconds. nvoAirFlow nvoAuxTemp1 nvoAuxTemp2 nvoUnvInput1 nvoUnvInput2 nvoUnvInput3 nvoUnvInput4 nvoCO2sensor nvoFanLoad nvoHeat1Load nvoHeat2Load nvoMotorPositn nvoActualValue nvoOAirFlowRatio nvoAirPressure It is typical to set the Node Minimum Send Time and the Node Send Heartbeat to 60 seconds and the Node Receive Heartbeat to 0 seconds.  

Issue How to find a dongle ID (PSU ID) if it has rubbed off of the dongle. Product Line TAC Vista Environment Vista IV TAC Dongle Utility Cause The dongle ID (PSU ID) can be found printed on the side of a Vista IV licensing dongle. However, on older dongles, this number can rub off. It is still possible to extract the dongle ID using the TAC Dongle Utility. Resolution Download the TAC Dongle Utility Install TAC Dongle Utility and run the program. Start > Programs > T A C > TAC Tools > TAC DongleUtil Plug in a valid Vista IV end user dongle. Hit Refresh on the Dongle Utility PSU ID is displayed. This is the ID required to add new licensing to an existing dongle. ReadFind a Vista 5 dongle ID for how to find a Vista 5 dongle ID.

Issue Plug-in 'TACZBuilderPlugIn.Application' launch failure. Unspecified error Product Line TAC Vista Environment LonMaker 3.X TAC ZBuilder Plug-in Cause An unspecified error in the launching of the TAC ZBuilder Plug-in is either caused by a faulty installation or registration of the plug-in. Resolution Check under Start > Settings > Control Panel > Add or Remove Programs. Look for TAC ToolPack 5.X.X. Make sure the version number 5.X.X matches the current Vista installation. If it does not, uninstall the current version of the ToolPack and install the correct version. If it is the correct version, proceed. Check the plug-in registration. In LonMaker go to LonMaker > Network Properties > Plug-in Registration. Look for TAC Vista System Plug-In (Version 5.X.X) Make sure the version number 5.X.X matches the current Vista installation. If it does not, unregister the current version of the Plug-in and register the correct version. If everything appears to be installed and registered correctly, but the error persists, uninstall and reinstall the correct ToolPack. Reboot the PC, reregister the plug-in, and try to launch it again.

Issue   The requested information is not available from the device. (Subsystem: NS, #28) Product Line TAC Vista Environment LonMaker 3.2 (Turbo) Cause The requested information is not available from an application node. For example, transceiver status, SI/SD data, and the network variable names are not always stored in the node. This error is a known issue with LonMaker 3.2 (Turbo). Resolution Navigate to http://www.echelon.com/support A username and password are required to access the download section, but it is free to register. Download LonMaker Turbo Service Pack 2 Install LonMaker Turbo Service Pack 2.

Issue The Echelon LonTalk PCC-10 PCMCIA Network Adapter will not work with a Dell E6410 laptop. Product Line Satchwell MicroNet, Satchwell Sigma, TAC IA Series, TAC Vista Environment Echelon LonTalk PCC-10 PCMCIA Network Adapter Dell E6410 laptop Cause Dell E6400 Chipset Resolution To correct this, an entry needs to be added into the Windows registry. Option 1 Download a Windows registry import file from The Exchange. Navigate through Products > Satchwell > Sigma or MicroNet > Downloads > Hot Fix (Or you can download the file here RegedittoaddPCMCIACard.zip). Once downloaded, double click the file and the entry will automatically be added. Reboot the computer before the entry is read. Option 2 Manually add the entry into your registry. Use caution when making changes to the Windows registry. Mistakes can be fatal to the operating system. To manually add the entry, carry out the following: Go to Start > Run and use “regedit” to open the Windows registry. Navigate through to HKEY_LOCAL_MACHINE\SYSTEM\ CurrentControlSet Services Pcmcia Parameters Add a new DWORD entry called “IrqRouteToPciController” Modify the new entry and give it a hexadecimal value of 8 Reboot the computer before the entry is read. If option 1 or 2 do not resolve the issue, it may be necessary to perform the following:  Option 3 Open the registry editor. Go to the registry entry HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{68EE3401-D4CA-11D3-8DBB-0060082936F2} or HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{68EE3401-D4CA-11D3-8DBB-0060082936F2}\0000 and look for the key name "PcmciaExclusiveIrq". Delete the key name "PcmciaExclusiveIrq" (If it exists). You may need to reboot the PC. Further information may be available in the Echelon Knowledge Base on the Echelon website. This information can be found in Solution: KB763. For more information, please refer to TPA-SACH-10-0009.00 - LON PCC-10 PCMCIA Card with Dell E6410 Laptop

Issue Epibuilder Dynamic Text fields are not displaying in a badge layout or Errors related to EpiBuilder or EPIDesigner Product Line Andover Continuum Environment EpiBuilder Badge Layout Cyberstation Cause Install didn't make the connection properly or badging wasn't enabled during the initial Continuum installation or Windows permission restrictions  Resolution From Make Edit badge in Continuum, Open Badge layout in EpiBuilder (If you have a problem opening Badge Layout see Note #2 below) View Options> Data Fields Select Use the data fields defined in a database If nothing is there, click the Other Database button Select Use an ODBC database Select the Data Source button Select System DSN tab and then select EPISDK then OK Click the Select button add the path to SDKNoDB.mdb (C:\Program Files\Continuum\EpiBuilder\Data) Click Open, Click OK All fields should now be available or the error should no longer happen on startup If receiving: ** Error Opening EpiDesigner Configuration Database error when selecting MakeEdit Badge,    Note #1: Permissions can affect the configuration of the Data Sources. If some options aren't configurable or have been changed from the default like buffers are not set to 2047 then try the configuration with increased permissions. Start>run odbc32.exe and check that the System DSN had EPISDK, If not, add it and then follow the instructions able to set the SDKNoDB.mdb  If the site is utilizing hard drive encryption on the hard drive.  Move the sdknodb.mdb to an unencrypted network share to correct the errors after updating the episdk datasource.  Note #2:  If you cannot perform step #1 from above check the following: On a 32 bit system run the following command from either the run window:  odbcad32.exe and check that the User DSN has an EPISDK entry with the datasource set to SDKNoDB.mdb .  The file should be located at the following path: C:\Program Files (x86)\Continuum\EPIBuilder\Data\ On a 64 bit system run the following command from either the run/search window:  C:\Windows\SysWOW64\odbc32.exe and check that the User DSN has an EPISDK  entry with the datasource set to SDKNoDB.mdb . The file should be located at the following path: C:\Program Files (x86)\Continuum\EPIBuilder\Data\

Issue Error displayed: Enhanced Alarm Delivery "There appears to be a problem with the configuration of this system. Please check to make sure that you have correctly installed MSMQ. The system will now shutdown."   Product Line Andover Continuum Environment Windows OS Cause The issue is that MSMQ is not installed on the machine or the installation is corrupted. MSMQ is a windows component that needs to be installed for enhanced alarm delivery. Resolution Install MSMQ from the Windows Control Panel > Add/Remove programs or Add/Remove Windows Components Reinstall Continuum NOTE: There have been instances where uninstalling MSMQ from Add/Remove Windows Components then allowing Continuum to install MSMQ resulted in a successful installation of the MSMQ.

Issue The xif file needs to be uploaded without LNS Management Tool All the devices on the LonWorks network needs to be searched The device mode or state needs to be changed Product Line TAC Vista Environment LonWorks Network Cause A LonWorks network test and diagnostic tool are needed. Resolution NodeUtil is a Windows console application that can be used with Echelon’s family of network interfaces (including the PCLTA-20, PCLTA-21, PCC-10, i.LON® 10, i.LON 100, i.LON 600, Loytec Devices, SmartServer, SLTA-10, U10, and U20 network interfaces) to diagnose and configure LonWorks® network interfaces, routers, and devices. NodeUtil is a test and diagnostic tool - it is not a network management tool.  It will not assign destination addresses or bind network variables. Nor will it format LonMark® interoperable device information. This tool can be used in the following conditions: The xif file needs to be uploaded without LNS Management Tool All the devices on the LonWorks network needs to be searched The device mode or state needs to be changed Other network test and diagnostic need This software can be downloaded at http://www.echelon.com/support/downloads/detail.aspx?partNum=153-0373-01A The username and password are needed. This site is opened to the public for registration, so everyone can obtain it. Once you are logged in by default "Recommended Downloads" will be selected. Select "Development Tools" instead to locate the NodeUtil software.

Issue After changing a controller's IP settings, it does not come online and cannot be accessed via its web interface. The controller can be accessed via its web interface by temporarily defaulting the IP address. Still, changes to its IP settings cannot be saved and are instead met with the following "Invalid Port" errors. Invalid Port – Module UDP Port Invalid Port – Touch Screen UDP Port Product Line Security Expert Environment Security Expert Controllers (SP-C, SP-ACX, SP-AC1, SP-C-WEB) Cause The controller's HTTP Port has been set to 0. If this field is set to no value, this is converted to an invalid 0 value, the controller will no longer be accessible via the web interface and will require defaulting the IP address to connect. Resolution Change the HTTP Port to a valid value. The default HTTP Port is 80, but it should be changed to another available port for increased security.

Issue Error when commissioning a Xenta 5/7/9xx indicates an out-dated or mismatched XIF (device template). Program IDs do not match. There is an incorrect or out-of-date program version. (Subsystem: NS, #38) on a Xenta 5/7/9xx LON device   If this error occurs on any other device besides a Xenta 5/7/9xx, please reference Program IDs do not match. There is an incorrect or out-of-date program version. (Subsystem: NS, #38) for resolution. Product Line TAC Vista Environment LonMaker 3.X Xenta Servers Xenta 511, 527, 701, 711, 721, 731, 913 XBuilder Cause The Program ID inside the controller does not match the Program ID specified for that controller inside the LNS environment resulting in a Program ID mismatch. Program IDs are unique identifiers created for use in device templates and are based on the XIF. Resolution Resolve the Program ID mismatch by making the Program ID in the controller match that in the LNS environment. Download the controller using XBuilder. Send project to target. Generate the latest XIF for the XBuilder project. In the Network Pane, right-click on the root (TAC_Xenta_511 in this example) Select Generate XIF File   Find the new XIF that has been generated in the XBuilder Project directory: targetimage\configdb\lon\TAC_Xenta_511.xif Default XBuilder locations XBuilder 5.1.3 and prior: C:\Documents and Settings\All Users\Application Data\TAC\TAC XBuilder Projects XBuilder 5.1.4 and later: C:\Documents and Settings\All Users\Application Data\Schneider Electric\TAC XBuilder Projects Windows 7: C:\ProgramData\Schneider Electric\TAC XBuilder Projects A good practice is to view details of the folder to confirm the time stamp of the XIF file. It should match the time that the file was generated in XBuilder. This file will be selected later, so another good practice is to rename the file to something more meaningful -- the name does not matter. "WebServer.xif" may be easier to find later and confirm it is the correct file. It is also perfectly acceptable to move this file to a new location -- Device Files of your overall project, for example. That can also help in later steps, especially if the default XBuilder Project location is used. In LonMaker, right-click on the device, and choose "Replace" (Not in System Plug-In)   Browse to the newly generated XIF file. Give the new device template a name. Select Finish. Commission the Xenta 5/7/9xx into the network. The Program IDs now match and the error is cleared.

Issue What is Remote Client with I/O in the Workstation Type in the I/O Server? Product Line TAC INET Environment I/Net Seven version 2.4x with need for Remote Client configuration using a Remote SQL Server. Equalization, FileMaster, File Master, Equalized Client, Remote Client, Equalize, FM, EQ, RC, MSDE, Express, Full SQL, SQL, TCP/IP, Connection Cause Remote Client changes with I/Net Seven version 2.4x  Resolution The new option of Remote Client with I/O for the Workstation Type begins with 2.4x version of I/Net Seven. This option is for a SQL Server which is not located on the Filemaster or Standalone but rather a separate Server. The Remote Client with I/O must be running for other standard Remote Clients to get the features such as AMT, Trends, and Network Functions. Network Functions can be found in I/Net on the pull down menu Edit/Host Computer/Network Functions. The configuration is in the I/O Server under the current profile and can be found in the Workstation Options.  HINT: Exit the I/O Server (and I/net) and select Start/Programs/I/Net/I/Net Configuration to be able to setup the Remote Client. Remote Client is not show unless you exit I/O Server. Clicking the link below will open a pdf document which will show how the communication should be setup if selecting Remote Client with I/O. I/Net version 2.4x Remote Client with I/O Clicking the link below will open a pdf document which will show how the communication should be setup if selecting Filemaster, Equalized Client, or Remote Client. I/Net version 2.4x Filemaster, Equalized Client, or Remote Client Suggestions for further info: To install the SQL, go to Installing I/NET Seven on a 64-bit operating system. For more on how to set up that Remote Client with I/O to use that SQL database, see Unable to connect Remote Client to Standalone Server. 

Issue Troubleshooting 2-Output PWM on a Xenta 102-AX Floating actuator for heating applications (hot water valve) Product Line TAC Vista Environment Xenta 102-AX PWM_2 floating hot water valve actuator Cause Multiple causes legitimately keep the hot water valve two-out floating control from stroking. Resolution The Xenta 102-AX controller supports auxiliary heat with two outputs. Both outputs can be utilized in a 2-output pulse width modulated (PWM) signal for control of floating actuators. This document suggests troubleshooting techniques to help narrow down the cause of improper operation of these hot water valve outputs. Start with Universal Output #2 On the Status tab of the 102-AX Plug-in, each of the universal outputs are listed under the “Network Bound Inputs” column. In the 102-AX Plug-in version 5.1.4, this column has been erroneously omitted. Download TAC Toolpack version 5.1.4 Hotfix 72 from the Buildings Business Extranet to resolve the issue. The output that represents the 2-output PWM is Universal Output #2 only. Even though output #3 is involved in the process, only #2 in the Plug-in represents the actuator position. The first thing to do is override the output to three different positions: 0, 50 and 100%. Cycling between three different values ensures the actuator is actively stroking. Forcing the valve to 100% will cause the open signal to energize for the full stroke time (throttling range) of the actuator, after which it will be de-energized. Wiring problems discovered after this time period has elapsed would require the output to be forced to 0% and then back to 100% to energize the open signal for the full stroke time again.   Figure 1. Network Bound Inputs If the valve strokes correctly, then the unit parameters, wiring, and actuator are all correctly configured. Skip directly to the chapter entitled “Overriding the Output Successfully Stroked the Actuator.” If the valve did not successfully stroke, proceed to the next chapter where three possible problems are addressed. Overriding the Output Failed to Stroke the Actuator There are three main reasons why overriding the output would fail to stroke the actuator. Unit Parameters The Unit Parameters tab of the 102-AX Plug-in is where Universal Outputs #2 and #3 are configured to work in tandem to accomplish 2-Output PWM control of a floating actuator. Heat 1 configures both outputs when OUTPUT_PWM_2 is selected. There is no need to configure Heat 2. Changes to Heat 2 will have no effect on the heating operation.   Figure 2. Heat 1 Unit Parameters Make sure the output type is set for OUTPUT_PWM_2. The stroke time should match the manufacturer’s documented stroke time of the actuator. Delay on start and stop are dictated by user preference or customer specifications. Normal Stroke should be set for normally closed. Wiring Check the wiring of the actuator to the 102-AX. It should be wired as follows: Point Label Terminal Actuator Universal Output #2 V2 15 OPEN Universal Output #3 V3 16 CLOSE Ground G0 13 COM Actuator The last step to troubleshoot an issue with the actuator not moving is to test the actuator itself. This can be done by jumping out the open or close leg of the actuator to 24Vac power. If the actuator still does not move then it is faulty and should be replaced. Overriding the Output Successfully Stroked the Actuator If overriding the output causes the valve to move accordingly, then the configuration of the output and the physical configuration are all correct. The 102-AX controller logic is not calling for the valve to open. There are a number of reasons why this might be occurring. The Basics The 102-AX must be in a heating mode to open the valve (cooling mode will close the actuator). It may be displaying either HVAC_HEAT or HVAC_MRNG_WARMUP. The space temperature must be below the effective setpoint to be in heat mode and will generate a negative terminal load down to -100%. The terminal load will equal the heating valve position. Check that the heating/cooling setpoints and heating/cooling bands are set such that no overlap in the two modes occurs. Heating/cooling bands must be greater than 0°. Hardware Configuration If the 102-AX is not configured for a sufficient number of stages of heat, it will not cycle the valve. If there is no fan, then only one stage of heat needs to be defined. However, if a fan is defined, then there needs to be at least two stages of heat, because the fan is considered the first stage.   Figure 3. Fan Type and Heat Stage If the heating valve is to be utilized in morning warm up mode (when the duct inlet temperature indicates that the air handling unit is providing central plant heat), then the hardware configuration must state that supplemental heat is allowed during warm up.   Figure 4. Enable Heat on Warm Up If a supply temperature sensor is wired to Universal Input #1, it could be that it is sending the VAV into morning warm up mode when the heat is enabled, and thus, disabling the heat. If this is the case, there are two options. Universal Input #3 can be used instead and set as an outside air temperature. Alternatively, Universal Input #1 can be configured as "None."   Figure 5. Input 1 Selection Setting Input 1 Selection to "None" will not disable the reading of the sensor. UnivIn1_Sense.nvoAuxTemp1 will continue to report the duct supply temperature. Setting it to "None" disables the signal from affecting the internal logic – preventing the 102-AX from entering morning warm up mode. Note: If the VAV is already in morning warm up mode when the input is set to "None," the box will remain in morning warm up mode. Override the input temperature to something below room temperature prior to changing the input selection. Application Mode The SNVT input VAV_Controller.nviApplicMode can allow a supervisory controller to override the current mode of the VAV. Upon receipt of a new application mode, the 102-AX will encounter a brief synchronization period where the terminal load is held to 0%. If the SNVT is being sent from a data manager, and the period on the output SNVT in Menta is set to 60 seconds, then the 102-AX will zero out the terminal load every 60 seconds, preventing proper operation. Set the SNVT output to a period of 0 seconds, and it will only write a new value on change and allow proper external control of the mode. Airflow Setpoint The Warm up Maximum airflow setpoint must be greater than or equal to the Heating Minimum airflow setpoint.  If this is not the case, then the airflow setpoint will default to the unoccupied flow setpoint (typically 0 CFM) any time the VAV is in heat mode, and the heating output will not be utilized.  This can be easily overlooked in applications where Warm up Mode is not being used, but this one parameter must still be set. This is fixed in the Xenta 102-AX firmware v2.18.   Figure 6. Airflow Setpoint Actual Airflow In order for the heating outputs to be energized, the airflow must be at least 80% of the minimum heating airflow setpoint. This is hard coded into the controller and cannot be disabled. The only way to remove the interlock is to set the minimum heating airflow setpoint to 0 CFM; however, in this situation, the VAV will close the damper in an attempt to provide 0 CFM of airflow. The heating will modulate without any airflow at that point.   Figure 7. VAV Status not providing 80% Airflow Check on the VAV Status tab of the 102-AX plug-in to compare the airflow to the airflow setpoint. If the box cannot provide the necessary 80% of setpoint or there is no airflow available during the commissioning stage, lowering the airflow setpoint can allow checkout to continue. This 80% airflow requirement is looking at the on-board flow sensor of the Xenta 102-AX. If the flow value is coming from another controller on the network via the nviBoxFlow SNVT, the heat will be disabled. The nviBoxFlow input will override flow values for damper control, but heating outputs will ignore it. In this situation, setting the pressure offset (UCPToffsetPress) to 1” will bypass the limitation. This will be fixed in the Xenta 102-AX firmware v2.18. Wrap Up If everything is configured properly physically and in the 102-AX Plug-in, then the box should be stroking the valve to maintain the space temperature setpoint. Disclaimer The information contained in this document is subject to change without notice. It is also subject to change with versions of TAC Xenta 102-AX. If further assistance is required, or if you would like to add to steps suggested here, call or email Schneider Electric Product Support.

Issue After installation of G3 Workbench version 3.4.57 or 3.5.25, the Software Manager on the Localhost may display that the sun-jre-win-x86 VM module is out of date: Environment Niagara G3 version 3.4.57 or 3.5.25 Sun JRE VM Module Cause While this is not a fatal error condition, the module can be updated. NOTE: if the installed version is 3.5.25, replace path references to "3.4.57" in the paths with "3.5.25" Resolution Shut down Workbench Open Windows Explorer, and navigate to the C:\niagara\niagara-3.4.57 directory Rename the jre folder to jre.old Now, navigate to the C:\niagara\niagara-3.4.57\sw\1.6.0.20 directory. Using WinZip, open the sun-jre-win-x86.dist file (or the sun-jre-win-x64.dist file if using the 64-bit version of Workbench). Select all of the folders in the archive, and extract them to the C:\niagara\niagara-3.4.57 directory (see below). Make sure that the “Use folder names” (or equivalent) box is checked. After the extraction, a new jre folder is created. Run the Platform Daemon (Start > Programs > Enterprise Network Server 3.4.57 > Install Platform Daemon) Open Workbench, and then open the Software Manager in the Platform. The Sun VM will now show "Up to Date"  

Issue   PARSER_CODE_ERROR Error in COD file - Error:15 When directly downloading a Menta file a Parser Code Error is displayed. This is a Parser Error that is alerting you to the fact that there is a problem with your Code. An error in the Menta file is stopping it from downloading successfully. Product Line TAC Vista Environment Menta Xenta programmable controllers Xenta 280, 281, 282, 283, 300, 301, 302, 401, 401:B Cause Direct downloading a Menta file (via the RS-232 port, a serial cable, and Online Simulation Mode) can bring to light Parsing Errors that are not reported by the System Plug-in. These errors will result in unsuccessful download attempts without any indication of the failure. To find them, direct download the Menta file. The download gets to where it is parsing the file before it fails:  There are three known reasons why the parsing of a Menta file will fail with Error Code 15. With some careful investigation of the error the cause can be determined, although checking all known causes is not prohibitively time consuming. Either the Menta application is too large, contains SmartStruxure Function Block following a cut-and-paste of code, or the file has corrupted public values indicated by the values being shown in scientific notation. Resolution First, determine the source of the error. Three known issues are discussed below: Corrupted public values show in scientific notation The Error:15 window attempts to show the user where in the Menta code the error is occurring. Without a fairly intimate knowledge of the inner workings of Menta, this can be less than helpful. However, if scientific notation in a PVR is causing the error, the error window will show this. The first line states: PVR     3,Z4 R1.0762e-042 This is showing that a PVR in the Menta program has a value of 1.0762e-042. It may take some searching, but you will need to locate the PVR in the Menta file that has this corrupted value and change it back to something valid. Also check public constants in the file to make sure they are not corrupted.   SmartStruxure Function Blocks in TAC Menta application This error also appears if there are any SmartStruxure specific Function blocks in the application. RO, BO, RI, BI, TSCHI, ERROR, II, IO, PI, PO Check the if any of the blocks are in the COD file (in the error window), find the blocks and replace/remove them.   Menta Application is too large The only other option is that the Menta application is too large. So if the Error:15 window comes up and does not indicate scientific notation in any of the values, it has to be that the file didn't fit inside the controller. Check the memory in Menta under Options > Memory Usage. You want to see free space in all categories. If there are any negative numbers then that portion of the application is too large. Bear in mind that this is a simple estimation by Menta as to the memory needed. Trend logs, OP tree, network description files and the Menta application all need to be stored in the controller, so sometimes a very low, albeit positive, number can indicate problems as well. Try cutting down on trend logs or OP trees to free up space if the application cannot be reduced.

Issue   Invalid database version. (Subsystem: LNS, #81)[DB #-2038] Environment LonMaker 3.1 Cause A computer running LNS version 3.2 or higher (sometimes called LNS Turbo) can open any LNS database. If the database being opened is LNS version 3.1 or earlier, the database will be upgraded. This process is irreversible. Once the database is upgraded, earlier versions of LNS can no longer open it. The opposite is not true. If a computer running LNS version 3.1 attempts to open a 3.2 database, this error will appear. Resolution The LNS version must be at 3.2 or later to open a 3.2 database. Either upgrade the LNS version on the PC attempting to open the database, or revert to an earlier version of the database before it was upgraded (if possible). To upgrade your LNS version to 3.2: Navigate to http://echelon.com/support/downloads. You will need an Echelon ID and password. It is free to create a New User Account if you do not already have one. In the drop-down menu, select Search for software in the Network Tools category. Before you install LonMaker Integration Tool 3.1 Service Pack 3 Update 3, you must have already installed LonMaker Integration Tool 3.2 Service Pack 3 Update 1. Download both Update 1 and Update 3, or just Update 3 depending on the situation. Note: If you upgrade to LNS Turbo, you will no longer be able to restore databases from a non-Turbo LNS PC. There is backwards compatibility with old databases, but no "forward" compatibility for older PCs to open newer networks.

Issue Power to devices are Full Wave or Half Wave. Device is connected to 24VAC and begins to smoke because the voltage power input from transformer is not wired correctly. Product Line TAC INET, TAC Vista Environment Devices such as a Xenta Router or a controller which is powered by an external 24VAC transformer. Cause Devices such as a Xenta Router or control board is connected to 24VAC and begins to smoke because the power input from transformer is not correct. Resolution Download Full Wave Half Wave.pdf which illustrates the transformer to device wiring configuration. PoE is not supported for any of the Ethernet ports on I/NET devices.  

Issue Modbus device is offline in Vista. Product Line TAC Vista Environment TAC Vista Xenta 511 Xenta 913 Xenta 700 Cause The Modbus device online check has to read at least one variable for the device to come online in Vista. If you only write values to the Modbus device, it will appear offline.  Resolution As a workaround, you may create a dummy variable that you read from in Xbuilder

Issue How to increase the number of Modbus registers the Xenta server polls in a single request? Product Line TAC Vista Environment XBuilder Xenta 511 Xenta 913 Xenta 701 Xenta 711 Xenta 721 Xenta 731 Cause This feature is not well documented in the Xenta 700 documentation, though it is mentioned in the TAC Xenta Server – Gateway, Technical Manual (Xenta 913). Resolution In XBuilder, selected the Modbus device in the network view. Under Link->Max Range Size you will see the current setting, the default is 20 which most devices support. Change the number to the desired value between 1-100. Note that the value must be supported by the device! Download the project to the device to commit changes.  

Issue ES connect to 3rd party BACnet devices in StruxureWare Building Operation Product Line EcoStruxure Building Operation Environment StruxureWare Building Operation site with Enterprise Server. Connection to BACnet devices such as ACX. Cause Desire to use ES rather than AS Resolution As of StruxureWare Building Operation 1.1 the ACX with BACnet I/P xDriver with the ES, we can see the points, load them into the BACnet interface, and view them in tgml. The BACnet IP xDriver and User Guide is available on The Exchange Download Center. The following screen captures are from the ACX where a simple Infinity Numeric is setup called ACXdevice:   Next the xDriver for the ACX is loaded and setup as Server with the following settings: (Note the IP Address references the IP of the ACX controller)   Next a simple Numeric is setup called BacTest1 with the following settings: (Note the IP Address is left blank)   Next another Numeric is created called CocaCola1 with the following settings:   Next from the Enterprise Server, a 'Find New BACnet devices' is done to find the ACX and the two Numerics created:  

Issue What is the SubLAN and what is the C-LAN in regards to Ethernet and termination resistor information? Explanation of termination resistor, RS-485, baud rate, token passing, and polling method. Is the Host LAN above or below the Ethernet LAN? Product Line TAC INET Environment I/NET Seven Network with integration of the FOI or Fiber Optic Interface  Cause How the Fiber Optic Interface (FOI) fits into an I/NET site. Resolution When defining the network in I/NET, the chart below helps to explain which components communicate to others. This is a simple explanation on where the various I/NET components are located in an I/NET Seven Network. C-LAN & Sub-LAN and the integration of Fiber Optic or FOI. The FOI Spec sheet is available here, as well as TCON087. Click the image below to download as a PDF document.