Building Automation Knowledge Base

Issue When launching a Access Expert on a Premise install, an error "Unable to retrieve license. Please notify your Keep service provider" when trying to log on to the instance. Product Line Access Expert Environment Access Expert Wondows 7, SQL 2012 SQl 2014 Cause Keep does not have access to the database for license information. Resolution Install SQL Studio and give NT AUTHORITY\SYSTEM sysadmin rights. The following captures shows where to go to enable this in SQL. Connect to SQL, go to the Security Folder and expand it, select the Logins Folder and expand that then select the NT Authority When the tab opens select the Server Roles, then check the box for sysadmin.

Issue Installation question on XP module Environment Cause Installation question on XP module Resolution Yes. Modules can be connected to the bottom of the controller with the built-in expansion port connector or they may be connected remotely via a 3-foot (1 m) or 10-foot (3m) ribbon cable. A total of 10 feet of cable may be used for all Expansion Modules. Mounting and securing of the xP modules is provided through four mounting holes in the base plate.

Issue Error when starting Continuum 1.9: Cannot find acc video recording service. Environment Windows XP SP3 Continuum Cyberstation Cause As with many software installations, installing with anti-virus running will block some registrations and registry entries. Resolution Install Continuum with admin privileges Turn off anti-virus software Stop any firewalls during Continuum installation

Issue The maximum stat adjustment range that can be set using the Xenta 102-AX Plug-in is 10°C (17.98°F) or roughly 5°C (9°F) above and below the base setpoint. This limitation is applied to the 102-AX Plug-In, Operating Parameters, Stat Adjustment Range. Environment Xenta 102-AX Plug-in Cause The LNS Xenta 102-AX Plug-in limits the values that can be written to the stat adjustment range parameter. Resolution Write to the stat adjustment range variable through Vista Workstation.  There is no limitation applied to this value when the LNS Plug-in is not being used.  The point can be found in the Xenta 102-AX controller at VAV_Controller.nviSetpoint.SCPTmaxRnge. If the 102-AX Plug-In is accessed after the change, the plug-in will limit the value again resulting in 10°C (18°F) being written back into the 102-AX.

Issue Definition of number of nodes and points allowed using Modbus TCP/IP or RTU xdriver. Product Line Andover Continuum Environment Modbus Protocol Cause Definition of number of nodes and points allowed using Modbus TCP/IP or RTU xdriver according to the modbus protocol. Resolution The maximum number of nodes is 254. The address range for points is 1 through to 65535. The number of addresses is limited by the controller memory. We have had ~6000 points but please note the Modbus is a polled protocol so the more points you have the longer the poll rate.   Specific Modbus RTU Details Our Modbus RTU XDriver supports the node range from 0-255. According to the Modbus specification, the node range is from 0 – 255, with 0 being the master, 1-247 being the slaves, and 248-255 being reserved addresses. After 32 nodes (1 master + 31 slaves), you may need RS-485 repeaters to ensure proper communications. This depends on a number of different items, including if the RS485 transceivers are full or quarter load. You can find the Modbus serial standard at the link below for further details. http://www.modbus.org/docs/Modbus_over_serial_line_V1.pdf

Issue Integration to the Powerlogic PM800 power meter with the Xenta 500 \ Xenta 700 \ Xenta 900 and Modbus RTU Product Line TAC Vista Environment Xenta 511, 527, 701, 711, 721 (5.1.5 up) Xenta 731, 913 (all versions) XBuilder Powerlogic PM800 Power Meter Cause Disclaimer: This device template is intended to provide a starting point for an integrator, and is in no way written to be the mandatory points list for your integration effort. Product Support Services-Dallas has written this device template in an effort to give our customers a starting point and solid example of how to develop a device template for the above product. The integrator will be responsible for any additions or modifications to this device template. Please report any problems to PSS Dallas at product.support@buildings.schneider-electric.com Resolution Please us the following .dev file as a starting point and a guide to the integration. This .dev file contains a set list of registers that PSS assumed would be seen as critical and important to the integration process. If any other data is needed please see this supported document to make the necessary changes.     To use these files in Xbuilder please follow these steps: Extract the .dev file from the .zip file in the link above, and place it on your harddrive. In Xbuilder, right click on the Modbus Master device and chose Add Device Browse to the needed .dev file and choose Open. Rename the newly added device to a unique name within the Modbus Master network.

Issue Integration to the Powerlogic CM4000 power meter with the Xenta 500 \ Xenta 700 \ Xenta 900 and Modbus RTU Environment Xenta 511, 527, 701, 711, 721 (5.1.5 up) Xenta 731, 913 (all versions) XBuilder Powerlogic CM4000 Power Meter Cause Disclaimer: This device template is intended to provide a starting point for an integrator, and is in no way written to be the mandatory points list for your integration effort. Product Support Services-Dallas has written this device template in an effort to give our customers a starting point and solid example of how to develop a device template for the above product. The integrator will be responsible for any additions or modifications to this device template. Please report any problems to PSS Dallas at product.support@buildings.schneider-electric.com Resolution Please us the following .dev file as a starting point and a guide to the integration. This .dev file contains a set list of registers that PSS assumed would be seen as critical and important to the integration process. If any other data is needed please see this supported document to make the necessary changes.   To use these files in Xbuilder please follow these steps: Extract the .dev file from the .zip file in the link above, and place it on your harddrive. In Xbuilder, right click on the Modbus Master device and chose Add Device Browse to the needed .dev file and choose Open. Rename the newly added device to a unique name within the Modbus Master network.

Issue Integration to the Cummins ModLon 2 gateway with the Xenta 500 / Xenta 700 / Xenta 900 and Modbus RTU Product Line TAC Vista Environment Xenta 511, 527, 701, 711, 721 (5.1.5 up) Xenta 731, 913 (all versions) XBuilder Cummins ModLon 2 Gateway Cause Disclaimer: This device template is intended to provide a starting point for an integrator, and is in no way written to be the mandatory points list for your integration effort. Product Support Services-Dallas has written this device template in an effort to give our customers a starting point and solid example of how to develop a device template for the above product. The integrator will be responsible for any additions or modifications to this device template. Please report any problems to PSS Dallas at product.support@buildings.schneider-electric.com Resolution Please us the following .dev files as a starting point and a guide to the integration. This .dev file contains a set list of registers that PSS assumed would be seen as critical and important to the integration process. If any other data is needed please see this supported document to make the necessary changes. One generator: .dev file Two generators: .dev file   To use these files in Xbuilder please follow these steps: Extract the .dev file from the .zip file in the link above, and place it on your harddrive. In Xbuilder, right click on the Modbus Master device and chose Add Device Browse to the needed .dev file and choose Open. Rename the newly added device to a unique name within the Modbus Master network.

Issue In some situations, the STR-350 is needed to send an absolute setpoint to another device on the network, and the nviEffectiveStpt is needed to be able to raise or lower that setpoint over the network. When doing this, the nvoSetpoint will not mirror the set value in the nviEffectiveStpt.  Environment STR-350 v1.2 & v1.3 Cause If the nciSendHeartbeat is greater than 0, the stat will only use the adjusted value at the stat and will ignore a network value from the nvi.  Resolution Set the nciSendHeartbeat to 0 and any change on the nviEffectiveStpt will be reflected on the nvoSetpoint and as the current setpoint on the stat.

Warning Potential for Data Loss: The steps detailed in the resolution of this article may result in a loss of critical data if not performed properly. Before beginning these steps, make sure all important data is backed up in the event of data loss. If you are unsure or unfamiliar with any complex steps detailed in this article, please contact Product Support Services for assistance. Issue When doing a LonMaker resynchronization, the operation fails on a certain subsystem or when doing a commission on a controller in Lonmaker an error is displayed: Attempt to assign a neuron ID that is already in use by another device. (Subsystem: LNS, #102) Environment LonMaker 3.X Cause If re-commissioning or downloading and commissioning a controller in LonMaker fails or times out, this issue may crop up. LonMaker assigns the desired neuron ID to a temporary device while performing either of these commands, and if the operation fails, that temporary device will get stuck in the database with the same neuron ID as the controller the user was working on. A successful resynchronization will bring this "phantom device" to light where it can be deleted, but if it is the resynch that is failing, the steps below detail how to remove a neuron ID from a device in the LNS database so it can be deleted. Resolution Try to do a resynch command in LonMaker to get the temporary device to show itself on the Visio drawing. If this works, then the temporary device will show up with a randomly generated alpha numeric name on the same page as the controller you were trying the commission or download. After the resynch completes, delete the device from the page and repeat the commission or download. If the resynch operation fails with: Attempt to assign a neuron ID that is already in use by another device. (Subsystem: LNS, #102), continue. Because the temporary device is in the LNS database, but not on the LonMaker Visio drawing, manual manipulation of the LNS database is required to remove this object. This is done with the LNS Object Browser. First, shut down LonMaker, then click START and chose RUN in Windows and type lnsobjectbrowser and click ok. The Startup Preferences are shown. Set the Client/Server Communication to Don’t change and the Local Network Access to Engineering Mode and then click Ok. After choosing settings in the Startup Preferences menu, the LNS Object Browser is displayed. Press F8 to take the object browser out of read only mode. Browse to the following: ObjectServer/Networks/Your_Network_Name/Systems/ Your_Network_Name/Subsystems/All/AppDevices. Note: Double-click to open each object. Within the APPDevices menu you will see the temporary device with the large alpha-numeric name. Double-click this device to get its properties in the right hand window. Double-click on the NeuronId line in the properties pane of this device and manually set the Neuron Id to 000000000000 (12 zeros) and click Ok. Exit out of the LNS Object Browser and re-open the LonMaker database. Perform another resynchronization of the database, and the suspect temporary device should now show up on the LonMaker drawing. Then, delete that device and re-attempt your work on the original controller.

Issue Test and air balance procedure for balancing airflow Product Line TAC Vista, EcoStruxure Building Operation Environment Building Operation Automation Server Premium  TAC Xenta 102-AX  TAC Xenta 102-AX Plug-in Cause Each 102-AX controller must be calibrated on-site to report accurate airflow readings.  The LNS Plug-in provides this functionality, but it may not be immediately clear what the correct procedure is to perform a valid calibration. Resolution Check the firmware version of your 102-AX controllers in the plug-in, Node Configuration tab. It will be shown under Program Revision. If it's anything earlier than 2.1.6 then the calibration won't work properly. The airflow setpoint changes but the damper does not modulate to maintain setpoint in the calibration mode. Your options in that situation are to manually manipulate the damper to maintain airflow setpoint in order to facilitate calibration or upgrade the controllers firmware. Also verify that the box is set to "Pressure Independent" mode on the Unit Parameters tab.  Pressure dependent boxes do not use airflow sensors, and therefore cannot be calibrated. To balance the 102-AX in Building Operation version 1.4 or higher where the LNS plug-in is no longer provided, review the article TAC Xenta 102-AX TGML plug-in for Building Operation To calibrate airflow using the 102-AX LNS plug-in:  Go to the Node Configuration Tab. Select "Set Default m & b." This is a good idea before each calibration attempt since incorrect calibration values can make it more difficult to perform a valid calibration. (NOTE: The m & b values can be viewed under the Airflow Parameters Tab of the 102AX LNS plug-in...m = Velocity Pressure Gain & b = Velocity Pressure Offset) Select "Start Calibration." At this point the airflow setpoint should go to the minimum. You can check the Cooling Minimum airflow setpoint on the Airflow Parameters tab. The damper now modulates to maintain the minimum cooling flow setpoint. Watch the VAV Reading (Low) and wait for it to hit the minimum flow setpoint and level out. If the airflow is fluctuating a lot, it could be that the low setpoint is below the threshold the box can confidently supply. Or it could be bad placement of the flow sensor in a turbulent area of the duct. It can affect your calibration greatly if the value is fluctuating too much. A relatively level reading will provide a good calibration. When it levels out, measure the actual airflow with a highly accurate magnehelic hood. Enter the actual value into Reference (Low) and select "Continue." The damper now modulates to maintain the maximum cooling flow setpoint. Watch the VAV Reading (High) and wait for it to hit the maximum flow setpoint and level out. When it levels out, measure the actual airflow with a highly accurate magnehelic hood. Enter the actual value into Reference (High) and select "Finish." The new calibrated m & b values are shown. The gain (m) is shown in the format of multiplier/divisor. Divide the values to get a decimal format of the gain. The closer to 1 this value is, the less calibration was required. actually gains of 2 or more indicate probable airflow reading problems. It may be advisable to reset factory calibration values and try the calibration again. The box should now be displaying values very close to actual measured readings. Test the low and high flow during normal operation using the Status Tab, Right click on the Space Temp and override the space temperature to a value equal to or greater than the Occupied Cooling Setpoint plus half the Cooling Band to drive the airflow setpoint to the cooling maximum airflow setpoint (you can find the Occupied Cooling Setpoint and Cooling Band on the Operating Tab).  With the space temperature already in override, left click the Space Temp to change the space temperature without taking it out of override, and set the space temperature to the Occupied Cooling Setpoint minus half the Cooling Band to drive the airflow setpoint to the cooling minimum airflow setpoint.  With the space temperature in override, right clicking it will take it out of override.

Issue BACnet values drop out occasionally BACnet devices update slowly, or miss updates Xenta Server must be power cycled to restore communication Environment Xenta 913 BACnet Cause BACnet physical layer best known practices were not followed. Resolution The following must be verified on your installation. The physical BACnet layer must be wired as specified to have the wire grounded at each BACnet card and at the 913. The physical layer must be terminated with end of line terminators of the type specified in the documentation. It is recommended a BACnet segment should not exceed more than 15 per segment. It is recommended BACnet cards must be sequentially addressed leaving the 913 as Master node address 1. The 913 Xbuilder project and BACnet cards must reflect a "max master" setting of the last master address on the BACnet segment. A default baud rate of 38.4k may be attempted but it is safe to slow the network to 19.2k if you experience communication issues.

Issue A stand-alone Xenta programmable controller can have an application downloaded into it using a serial cable and Menta. However, if that base unit has additional Xenta 400 I/O modules associated with it, they will never recognize and associate with their base controller. Product Line TAC Vista Environment Stand-Alone Xenta Programmables Xenta 280, 281, 282, 283, 300, 301, 302, 401, 401:B Xenta 400 I/O Modules Menta Cause A direct download of a Menta application does not download any network description information along with it (.ndb file) -- it is application only.  The controller can be downloaded via System Plug-in, which places the .ndb file into the controllers, but this requires the creation of a "dummy" network.  lontool32 offers a quick work around for truly stand-alone controllers. Resolution It is best to use the most current system program for this method as older versions may not work. Note: While Menta allows for configuration of the communications port from COM1 to COM9, lontool32 can only communicate on COM1. Follow the instructions in Reassigning a USB Serial Adaptor to a desired COM port to force the hardware to COM1. Then launch the Menta Setup tool from the Start Menu (Start >All Programs > Schneider Electric > TAC Tools X.X.X > Menta Setup) and set the Com Port to 1. Using Menta, create and download your .MTA file to the Xenta programmable using the direct connect method. This connection will also be used for lontool32 downloads. After Downloading, ensure Menta is "offline" to allow lontool32 an active connection on COM1. Open the lontool32 program which is located in your Menta program folder (e.g. C:\Program Files\Schneider Electric\TAC Menta 5.X.X\lontool32.exe) In lontool32, select the add button to add group, then select add node to add Base Unit. Double click on the Base unit to edit the node in the Network Configuration window. Select the Upload button to retrieve the Device and associated  I/O information. You will see this information populate the "database" column and associated I/O will populate the "I/O Modules" window below. *If the upload button remains grayed out, Ensure the Menta connection is "Offline" or follow the instructions here Reassigning a USB Serial Adaptor to a desired COM port to force the hardware to COM1. Also, check in the TAC Menta Setup program to verify that the Com Port is set to 1. Edit each I/O module by right clicking and selecting "Edit I/O". Use the "Service Pin" button to set the Neuron ID .  Enter the Subnet and a unique Node address in the appropriate text boxes. Repeat this procedure for every base unit in the network. If the network will contain more than one Base Unit, one must be designated as master by selecting the "master" check box in the Network Configuration window. When all the I/O has been updated, Select the "Download" button to generate and send the .NDB file to the base unit. Your I/O Modules should now be online which can be verified by the status light now oscillating every second vs. flashing quickly. If the Subnet Node information populates to a 0, you must type a subnet address and unique Node address for each unit on the network.  

Issue When update Vista database through System Plug-in got error message saying “Update Vista database failed”. Open Workstation, in the alarm window, there is error message saying “unable to request license”. Environment CIRCON Network Integrator or other LNS network builder, customer license file Vista 5 Cause Vista cannot recognize the LNS server license. This happens when you use some LNS network builder besides LonMaker or NL-220, and you are using a purchased license file instead of a demo license file or an engineering dongle. Resolution If you get the “Update Vista database failed” error message in system plug in. Make sure you have done the group binding or redo the group binding. If the issue still exists, check the system plug-in output window and see if there is any error message before the “update vista database failed” message. If not, open TAC Vista Workstation and check the alarm window. If you see the error message says “unable to request license”, this means TAC Vista server cannot file the LNS server license. The TAC Vista demo license or an engineering dongle has a full version of all licenses which includes the LNS server license. You will see a line below in your demo license file: FEATURE Vista.Server.LNS taclic 5.1 31-oct-2010 uncounted HOSTID=DEMO However, the purchased customer license file does not have “Vista.Server.LNS” license included. The solution to this issue is either rebuilding the LNS network in LonMaker or NL-220, or purchasing an engineering dongle or using the demo license file.

Issue In Vista / Menta 5.1.4  it is possible to have illegal characters such as spaces or - in the program specification name of a Menta file. This will cause this $.mta file to fail when transferring to the Vista DB inside of the system plug-in. It will also cause a Xenta controller to never come online if installed in a Vista Classic DB.  Environment TAC Menta 5.1.4 Cause When leaving the program specification blank in a 5.1.4 Menta file, it will automatically be filled in with the name of the entire Menta file when it is saved for the first time. So if you do not fill in the program specification and name/save the Menta file "AHU-1," the program specification will be filled in with AHU-1. This "-" in the AHU-1 is not a legal character and will not be accepted within the Vista DB or the system plug-in.  Resolution When creating a Menta file for the first time, always remember to set the program specification to a name and without any illegal characters (maximum 12 characters). Once you are in the program specification name editor, it will let you know if you have entered proper syntax. 

Issue Incorrect settings in the BCX will prevent BACnet communication. Product Line Andover Continuum, TAC INET, TAC Vista Environment BACnet MSTP BACnet IP BCX Xenta 913 Cause Because the Xenta 913 has a limitation of 127 addresses, the default BACnet Address will most likely be out of range. Resolution The BCX4040 must be addressed properly to allow BACnet communication to the Xenta 913. The setting can be changed on the BCX's Controller Configuration page by accessing the controller via IP address to its web interface. On this page, you will see a setting for BACnet Network ID Comm2 which is the device's BACnet address. This number must be unique on the BACnet Network and must range from 0-127.   To Enable BACnet IP communication: Modify the BACnet Ethernet settings from the web interface. Set the BACnet Ethernet Enabled to Yes Set the BACnet Network ID Ethernet. This is the device's BACnet address. This number must be unique on the BACnet Network. The BACnet Device Id is by default the last 7 characters of the BCX serial number and must be unique to all devices in the Continuum network. Many people try to set the BACnet Device Id field to represent a BACnet address but this is not correct. This setting does not affect the Xenta 913 in any way.

Issue Remote Serial Port  Driver, RSPD, is not working. Environment Windows 7 Windows 2008 Cause Security in OS . Resolution Install and start the program as administrator. Right click on the program and select run as administrator.

Issue OPC Server setup for TAC Vista will not save the information when you change the user type from Windows account to TAC Vista account. Product Line TAC Vista Environment TAC Vista OPC Server 1.6.1 Cause This is a known issue that requires a specific reinstall procedure. Resolution Install version 1.6.0 of OPC Server Change to TAC Vista login in the TAC OPC setup Uninstall it Install 1.6.1 again. For more OPC Server issues please Vista OPC Server Installation and Known Issues.

Issue How many histories can be created in a station and how many records are allowed per history? Environment I/A Series G3 ENC, ENS or SoftJace CComTrolCCWEBor CES Cause Technical product information update. Resolution Regardless of platform type, histories are stored under the station's file system (file:^history/). Stations running on a PC-based system (Enterprise Server or SoftJACE) store the histories in subdirectories using segmented files; this provides improved search capabilities over a flat file system. Stations running on a QNX-based system (ENC) store all of the stations histories in a single compressed file (history.zip). A running station opens the history.zip file in the ENC's ram disk space, the histories are compressed and saved to flash whenever the station is saved. Opening the history.zip file to the ram disk eliminates the need to write to the flash drive each time a record is added to the history file.   When the station needs to write a record to a history, it opens the specific history into the running station (either from the file system if PC-based, or from the ram disk if QNX-based). The open history does contribute to the heap.used of the station. The history service has one property 'max open time' (default 5 minutes) which causes the station to close the history from the running station heap if no records have been written to the history for a time period exceeding the 'max open time'.   Each history extension which is added to the station does add slightly to the station resources because the extension is represented in the bog file. When the history is first enabled, the station creates the history file. The initial file includes a 1600 byte header (defines the configuration parameters) and a single page file of 4096 byte size. When triggered by either the collection interval or COV/COS, a record is added to the page file. When the page file becomes full, additional page files are created based on the capacity configuration of the history. History Record Size by Point Type Point Type bytes/record boolean 13 enum 16 single precision numeric 16 double precision numeric 20 string variable length * *NOTE: A single 'string' record cannot exceed one page (4096 bytes)   Since histories count as file descriptors, there is a physical limitation on the number of histories allowed in a QNX-based ENC station. It is recommended not to exceed 800 histories, given the file descriptor limit of 1000. Note: The platform services view of the QNX-based JACE station includes a property to modify the size of the ram disk within defined limitations. Note that the alarm database is also maintained in the same ram disk space. Exercise caution when modifying the default ram disk size; note that allocating additional memory to the ram disk will limit the memory available for other functions by the QNX OS. Reducing the ram disk size too much could result in history or alarm records not being stored properly and erratic station behavior.

Issue The local time inside a Xenta programmable unit is dependent upon server time, time zone, and daylight savings time settings.  Incorrect DST settings result in incorrect times in the controller which causes problems from incorrect start times on HVAC equipment, to incorrect alarm time stamps in alarm queues. Product Line TAC Vista Environment Xenta Programmables version prior to 3.74 Xenta 280, 281, 282, 283, 300, 301, 302, 401, 401:B Cause In 2007, most of the United States and Canada changed when DST is observed to the second Sunday in March to the first Sunday in November.  Because it had never changed prior to that, programmable controllers retained the old settings (first Sunday in April to last Sunday in October). Resolution The issue was resolved with the release of firmware MOT version 3.74.  Upgrading your controllers to 3.74 is a viable solution, however not always cost effective.  There are two ways to work around the issue. Note: For information on how to download firmware to Xenta programmable devices using the Download Wizard please see Download an .MOT file into a Xenta Programmable controller. Configure TAC Xenta Central DST Settings Refer to the TAC Vista Technical Manual Chapter 19.6 In the folders pane, right-click the folder where you want to place the time event object. Point to New, point to Object, and then click Time Event – Object. Type the name. Open the time event object. On the General tab, type a description. On the Time Event Settings tab, set a suitable repeat interval, for example, first Monday in each week. Click OK. In the folders pane, right-click the folder where you want to place the Central Daylight Settings – Xenta object. Point to New, point to Object, and then click Central Daylight Settings – Xenta. Type the name. Open the Central Daylight Settings – Xenta object. Two options are available. You can use Windows start and end times for the daylight saving time or specify your own start and end times. If you want to specify your own start and end times: Clear the Use Windows settings check box. In the Daylight saving starts box, set the start time for the daylight saving time. In the Daylight saving ends box, set the end time for the daylight saving time. In the Update schedule box, browse to the time event object that triggers the push to the TAC Xenta devices. Click Select. Click OK. Note: You must select Manual DST Mode and Central DST for each controller in the system for a global change to take effect. Manually set DST Settings for each controller The DST Xenta object is not available in all versions of Vista.  If that is not an option, DST settings on each controller can be manually set for the start day and stop day.  Unfortunately, time settings do not allow for designations of "first Sunday" or "last Sunday," only calendar dates.  So each controller will have to be edited each year to maintain correct time settings. In order to facilitate this, this utility:  ODXentaTimezoneChanger was created.  It must be used each year to update the settings, but it will allow you to change all time settings on all controllers in a Vista database simultaneously, greatly reducing the time it takes to correct a system. NOTE: If the Lonworks network has not been properly commissioned & downloaded the tree will not properly communicate with the Vista Server. Check your network tree for asterisks to see if any downloads are required.