Building Automation Knowledge Base

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 Living Space Sensore goes offline after upgrading SmartX Controller firmware from 2.0x to 3.01 or later Product Line EcoStruxure Building Operation Environment Building Operation Room Controller (RPC) v3.01 or later Building Operation SmartX Living Space Sensor Cause Living Space Sensor RJ-45 connector is plugged into Room Bus port on RPC. Resolution Move RJ-45 connector from Room Bus port to Sensor Bus port.

Issue Can an export file from one version of EcoStruxure Building Operation(EBO) be imported to another version of EBO?  Product Line EcoStruxure Building Operation Environment Building Operation Workstation Cause Export files are in general NOT backward compatible. A Script or Function Block Program that is exported from for example version 3.1.x is NOT guaranteed to import successfully into an earlier release Resolution Starting in version 3.0.x, import files exported from a later release than where they are imported will be denied. An export file from 3.1.x cannot be imported in 3.0.x. An export file from 3.0.x can however still be imported in 2.0.x, but it's not recommended, and it may fail to import successfully. In version, 3.1.x import files exported from versions older than version 1.3, will be denied. Starting in version 3.2.x, import files exported from versions older than 1.8.x will be denied.

Issue What happens when a device that SmartStruxure has COV subscriptions with goes OFFLINE for a while and then comes back ONLINE? Environment ES AS BACnet devices Cause Documentation Resolution QUESTION: What is the limit on number of COV subscription AS/ES support. ANSWER: There is no hard limits in the AS/ES for number of COV subscription, the server is limited only by resources. QUESTION: How often does the Automation Server subscribe (sends the subscription requests) for the very first time to the other devices? ANSWER: When the subscriptions are first established they are sent immediately to the devices, for example when you save a PE script program any COV created as a result of compiling the program are sent immediately to the device. QUESTION: In the case that the other device (the gateway) restarts or goes OFFLINE, how does the Automation Server handle the sending of the re-subscription requests? ANSWER: If a renewal fails due to device offline, it will be retried every minute indefinitely until it succeeds or the subscription is canceled. So if the device goes offline for a while some of the re-subscriptions will fail and will be re-tried once a minute, when the device is back, within a minute all the failed re-subscriptions will be sent again. QUESTION: Can the COVSubscriptionLifetime and the COVTimerPeriod  be set in the AS? or is it only in the ES ANSWER: They can be set in both the ES and the AS by editing the server.properties file in versions of SBO prior to 1.8.1 In SBO 1.8.1 and above, the settings can be accessed from the BACnet interface manager. QUESTION: Where is the server.properties file located in the server file system? ANSWER: AS: /opt/tac/etc (1.4.1 and below) AS: /opt/sbo/etc (1.5.0 and above) /opt/tac/db (1.4)   /var/sbo/db (1.5) /opt/tac/db (1.4)   /var/sbo/db (1.5) /opt/tac/db (1.4)   /var/sbo/db (1.5) ES:  "C:\Program Files\Schneider Electric StruxureWare\Building Operation 1.x\Enterprise Server\etc\  

Issue Windows crashes after performing a Doc to Dif conversion Environment I/NET Site Cause Why does Windows crash after performing a Doc to Dif conversion? Resolution Do not define more than 164 cells per conversion.

Issue When proportional 0-10Vdc type valve actuators are used with a SE8000 room controller, the actuators behavior is inconsistent. Environment SE8300 SE8350 SE8600 SE8600 Cause Some valve actuators e.g. wax filled (thermic type) have a high input impedance e.g. 100 Kohms. When connected to a SE8000 room controller, the actuators operation may be sluggish or may never operate. The SE8000 has a maximum output of 5mA when set to proportional control, using actuators with high impedance, the SE8000 room controller fails to recognise there is an actuator and does not drive it. Resolution A burden resistor can be fitted to draw some current from the SE8000 room controller because the actuator's impedance is too large. The burden resistor needs to be large enough not to affect normal use, but small enough to draw a current from the SE8000 room controller. Using ohms law: Valve actuator @ 100 Kohm SE8000 UO output is 5 mA, maximum Vdc output is 10 Vdc. Minimum size of burden resistor: 10 Vdc/5 mA = 2 Kohm. It may be necessary to increase the size of the burden resistor e.g. 10Kohm. The burden resistor is then installed between the signal ground and the signal, either at the controller or the actuator end. Test the actuators for correct operation.

Issue TAC Vista database export/import. Description texts are missing when the .zip file is imported. Product Line TAC Vista Environment TAC Vista Server TAC Vista Workstation Export/Import Cause Changes to the object description text fields made in TAC Vista Workstation are not automatically saved in the .mta file. Resolution To make sure that the description texts will be included in a database export (physical structure only): Edit the Xenta application with text description fields added or modified through Workstation. Save the Xenta application to the database. If you do this, the description text will be written in the .mta file and will be included in a database export.

Issue Switching from the Demo license to the Entitled License in Vista 5 Product Line TAC Vista Environment TAC Vista 5.X.X Cause In most cases the license will begin to work just fine after starting Vista and selecting "Use License Server" upon startup. For unknown reasons, Vista may need to be forced to ask you for a License File Or License Server option when Vista is first started after the license is switched. Resolution Unlike the Demo license, the site license must be placed in C:\Program Files\TAC\License Files (or C:\Program Files\Schneider Electric\License Files for TAC Vista 5.1.4 and above) and accessed via the License Server. It is imperative that the license file retains the .lic file extension, which importing to certain Windows environments may append a .txt extension to the filename The easiest way to force TAC software to use a License server versus pointing directly to the Demo License is to modify a registry setting of the Flexnet Licensing Software.   Start the Registry Editor from the Command prompt (type "regedit" in the start menu run box) and navigate to HKEY_LOCAL_MACHINE>SOFTWARE>FLEXlm License Manager.  Modify the TACLIC_LICENSE_FILE string and delete the Value data. By leaving this key empty, the next time you start any TAC software you will be prompted to "Specify the License Server System" or "Specify the License File".  Start a TAC Software package that requires a license.  Select "Specify the License Server System" and enter the computer name preceded by an "@" symbol. If the License Server resides on the local machine, "@localhost" can also be used. Note: In more recent versions of License Server, the "@" symbol is optional. If in doubt, putting it in will work with all versions. If the changes were successful, the registry entries should appear as follows (in a typical installation). If registry settings are different that the ones below, please contact Product Support Services.   If the above changes were performed but the License fails to read,  in some cases the License Server system will not work properly until rebooting the PC. If unable to read the license use LMtools utility located in the TAC Tools to troubleshoot the issue. If additional assistance is needed for using LMtools, watch the video overview published in Vista 5 Macrovision/Flexnet Licensing: Lmtools diagnostic utility overview. For help with Vista versions >5.1.7, see License troubleshooting in Vista 5.1.8 or greater

Issue What is valve authority? Product Line Field Devices Environment Any valve Cause Information on Valve Authority to obtain good control. Resolution Valve Authority = (Pressure drop across fully open control valve) / (pressure drop across the remainder of the circuit) + (pressure drop across fully open valve) In other words, valve authority within a system indicates how much of the system's total pressure drop comes from the control valve. It is common practice to consider the range between .2 to .5 as "acceptable" authority for proportional valve.

Issue Vista Server can read values on a LON device, but when this same device is used in an Xbuilder project for a Xenta Server no values can be read. Product Line TAC Vista Environment FT-10 LON Network Xenta Server Xenta 511, 527, 701, 711, 721, 731, 913 Cause The XIF file of the LON Device does not conform to LonMark standards for self documentation. Vista Server can recover from this and assumes all SNVTs are from the default function block, but XBuilder cannot. On the third line of each variable declaration is the self documentation: 1: VAR nvo01Value 2 0 0 0 2: 0 1 63 1 0 1 0 1 0 1 0 0 0 3: "@1|2 The correct format is to show the functional block number and the member number separated by either a | or # character. Improperly formatted self documentation include the following: "nvo01Value - Does not define the function block or member number. "@_1|_1 - Uses _1 which is not a valid number. "&3.4@0,20000-MP580 - Uses a - (dash) which is not valid It can also be because SNVTs from devices are bound directly to Menta programs in a Xenta 7XX. If the procedure below doesn't solve the issue, refer to Graphic values not updating in a network that includes a Xenta 7XX. Resolution The XIF file must be edited to correct the self documentation. Right click on the controller in Vista Workstation and open the properties window. On the XIF file tab find the file name of the XIF file. Open this file from the $thisfil directory in the Vista database folder. Modify the XIF by manually correcting these invalid lines of self documentation. It is recommended to use the default function block (0) and start with member index 50 to ensure no overlap. Increment the member number for each SNVT. "@0|50 "@0|51 .... Once the XIF file has been updated save it under a new name in the $thisfil directory. In the device properties browse to the new XIF file. Log out of workstation. Log in to workstation. Insert the LON network into Xbuilder. Generate the project and send to the device.

Issue Attempting to commission a controller in an LNS environment results in the following error: Cannot communicate with the device. (Subsystem:  NS, #26) Environment LonMaker, NL220 Cause An NS, #26 error indicates a complete failure to communicate.  Most often this will be the result of physical layer problems.  In some situations it maybe due to a failed controller. Resolution Check the obvious physical layer connections: Is the cable plugged into the laptop to connect to FT-10?  Is the router between the computer and device being commissioned online and communicating?  Are the wires terminated properly at the controller?  Is the controller powered? Are there end of line terminators fitted? Inspect the controller: Are the LEDs blinking as designed? Are you able to receive a service pin from the device? Does an MOT or NXE need to be reloaded to the device? Typical troubleshooting techniques will usually resolve an NS, #26 error once it is understood to be a complete lack of communication at the physical layer.

Issue Personnel.csv file fails to import into Continuum No error message is shown Product Line Andover Continuum Environment Continuum access control Keywords: CSV, Import, cardholder, personnel Cause CSV file gets modified by MS excel such that the import fails During the process of manually changing and saving a personnel.csv file within MS excel, a number of commas are added to the first line (corresponding to the number of column fields in the CSV) Resolution Use notepad or similar to delete commas before importing into Continuum as Microsoft Excel does not show up any trailing commas This will NOT import correctly Personnel,,,,, Name,FirstName,LastName,CardNumber,CardType,SiteCode Smith_Fred,Fred,Smith,10,Infinity_37,3701 This will import correctly Personnel Name,FirstName,LastName,CardNumber,CardType,SiteCode Smith_Fred,Fred,Smith,10,Infinity_37,3701 For more information on CSV imports Click Here For an example .csv file for testing Click Here Note: If importing X Driver points using a .csv file the comm port attribute "Port" must always be defined before the X Driver parameters Param1, Param2 etc. The Port must contain the full path e.g. "Network1\CXName\Comm1" Example X Driver Numeric: InfinityNumeric Name,Alias,Format,Description,Port,Param1,Param2,Param3,Param4 XDRPoint1,XDRPoint1,##,First X Driver Point,Network1\CX1\comm4,1,3,10001,1

Issue Using a 4-20 mA sensor on a Xenta 451A or 452A Product Line TAC Vista Environment Xenta 451A Xenta 452A Cause There is only enough power onboard a Xenta 451A or 452A for one 4-20mA.  Resolution Wire each sensor, using an external power supply for cases where there is more than 1 4-20mA sensor. Create an AI in the Menta file Bind the object to the 451A Select the correct Terminal Ref Choose the 4..20mA sensor If using this device as a stand alone LON module chose the 4-20 mA option for the nci NOTE: only Xenta devices ending in "A" have truly Universal Inputs.  For complete details on input configuration, see Configuring inputs on Xenta 421A or Xenta 451A when using the controller as a stand alone Lonworks node.

Issue Alarm queue in the Vista Workstation states "No license for LonWorks communication" Product Line TAC Vista Environment Vista Workstation Cause The simplest cause of the issue, and the one that should probably be checked first, is that the license for LonWorks communication was not present at the time the server was started.  Oftentimes, this is due to starting server, realizing the engineering or end user dongle was not plugged in (or license server was not started) and then plugging it in.  The server will not actively poll for this license, it must be present at startup. Resolution Stop the Vista Server Ensure the license dongle is plugged in, or the license file is activated and installed on the license server. Restart the Vista Server Related Articles: "No license for LonWorks communication" with TAC Vista Server LE "No license for LonWorks communication" error when using a non LE dongle "No license for LonWorks communication" - LonMaker Recovery Folder "No license for LonWorks communication" error message in Classic Network "No license for LonWorks communication" Error in Windows 2008 Server X64 TACOS startup delay utility

Issue Although all the cameras connected to Pelco Endura SM5000 system manager can be found by the video server, when using "Video Administrator" to try to assign alarm points to cameras, sometimes cameras cannot display properly,  such as "1-192.168.5.10"(SM5000 IP Address),  or return "not found' and get an error message such as "Camera or Video server maybe offline....". Environment Windows XP SP3 Cyberstation 1.92, Cyberstation 1.93 Pelco Endura SM5000 system manager Cause It is an Endura configuration problem. A camera should be added into a group. In and Endura system, there is a default group, if no additional group is created. Normally, cameras should be added into this default group. However, in some situation, some cameras will not be automatically added into that default group. In this situation, those cameras do not belong to any group; therefore, those cameras will not display properly in the camera's field drop down menu and cannot be selected. Resolution Create one or more groups in Endura system. Add the desired cameras into the groups created in step 1. Learn cameras again from the video server. Reopen the video administrator and add points to cameras.

Issue Satchwell RM3601 mains voltage Light Duty Actuator split phase capacitor motor rating is 24 volts. Environment Satchwell RM3601 mains voltage Light Duty Actuator mounted on Satchwell MB Rotary Shoe Valve Body.. Satchwell RM 3601 mains voltage Light Duty Actuator mounted on Satchwell MB Rotary Shoe Valve Body.. Cause Satchwell RM3601 mains voltage and XRM3201 24 volt Light Duty Actuator both utilise a 24 volt rated split phase capacitor motor. A dropper resistor installed across the RM3601 input terminals during manufacture is designed to enable this Light Duty Actuator to be utilised in mains voltage applications. Resolution The presence of a 24 volt split phase capacitor motor within a RM3601 mains voltage Light Duty Actuator should not lead an installer to believe that the Actuator has been manufactured incorrectly.. A dropper resistor installed across the RM3601 input terminals during manufacture is designed to enable this Light Duty Actuator to be utilised in mains voltage applications.   Please check the latest catalog for current equipment.  

Issue LON communications not working and error in Application Director: Error initializing LonNetwork javax.baja.LonWorks.LonException: Unable to initialize local lon port {Lon1} Environment G3, ENC, niagara Cause Typically this indicates a hardware issue with the neuron in the ENC. Resolution Open the platform for the ENC and use the Commissioning Wizard to commission the ENC again and see it if recovers.  If error remains the unit must be replaced.

Issue When using a USB to RS-232 adapter and an MN-CIM, cannot connect to MicroNet 2000 controllers. Receive an ERROR = -510. The problem has also been seen on laptops with an integral serial port. Environment Laptop computer running the MN-CI or MN-FLO-BAL software tools,  any version MN-CIM Controller interface Module Cause One cause of ERROR = -510 is that the serial port or USB to RS-232 adapter does not supply enough power to the "port-powered" MN-CIM. When the CI software is running, but not communicating on the U-LINK, it requires only 12 mA at 5 VDC. To communicate on the U-LINK, the MN-CIM requires 14 mA at 5 VDC from the DTR control line of the port.  Some computers have a mechanism to sense the increased current draw and shut down the DTR line. This loss of power causes the MN-CIM to reset, and after 3 attempts to communicate the MN-CI software issues the ERROR= -510 message. Resolution See Technical Bulletin 01-104 for information  on the Patton Electronics power supply adapter, model 3PMF9-BC.

Issue Upgrade Xenta I/O modules Environment Xenta 421A, Xenta 422A, Xenta 420A Xenta 411, Xenta 412 Xenta 491/492 Xenta 451A, 452A, 450A Xenta 471 Cause It is not very common to upgrade I/O modules. If it must be done, they are upgraded the same as any other LonWorks device without a host processor. Resolution Right click on the target file to store the file locally on the hard drive. To be able to download the NXE-file, you need both the NXE and the according XIF-file for the specific device. In LonMaker, select Replace or Commission, depending if the device are already in the database or not. If the XIF-file already exist in the database, select the correct Device Template. In the next dialog, select Load application image. Browse to find the directory for the NXE-file. Change File of type to NXE. Browse to find the directory for the XIF-file. Select Next to decide about source for CP values. Select Next, if you do a Replace, you could select the Neuron ID manually, and the old Neuron ID will already be in the dialog. Select Finish to download the new NXE-file into the device.

Issue Satchwell Sigma integration to BACnet Environment Satchwell Sigma IC-GEN-DDE PolarSoft BACdoor DDE Server Cause There is a need to integrate BACnet devices / system into Sigma. Resolution Refer to Product Information Bulletin 02.07.05-3 - BACnet I/O server for IC-GEN-DDE for details on the integration. Other than purchasing the IC-GEN from Schneider Electric, you will also need to purchase the BACdoor DDE Server from PolarSoft. Purchasing information can be found here.