Building Automation Knowledge Base

Issue S-E Forta M700 Actuator unable to be mounted on S-E VGS211F Valve Body . Environment S-E Forta M700 Actuator mounted on S-E VGS211F Valve Body  Cause S-E Forta M700 Actuator unable to be mounted on S-E VGS211F Valve Body due to absence of S-E VGS211F Valve Body Spindle Adaptor. Resolution 1.  Install S-E VGS211F Valve Body Spindle Adaptor prior to installation of S-E Forta M700 Actuator. The S-E VGS211F Valve Body is supplied with a Valve Spindle Adaptor. The Adaptor is illustrated in the S-E Forta M700 Installation Instruction (OFL – 4340 – 001). It is particularly important to ensure that this Adaptor is fitted to the Valve Spindle, as its absence will prevent the M700 Actuator from being mechanically connected to the Valve Body Spindle.

Issue Using an EP1501 as a controller and unable to add reader one. Product Line Access Expert Environment Access Expert Server 2012R2 and above Cause Using an EP1501 as a controller as well as a card reader controller. Resolution To resolve the issue, please follow the steps listed: Wire the RS-485 bus to reader port 1, Clock and Data Wire the reader being used on port 2 When programming the reader on the device, it needs to be added as Reader 1 The Door Address needs to be set as 0 as well

Issue Is it possible to replace a Xenta 400A I/O module in a LonMaker based project without a program download? Environment LonMaker Xenta 421A, 422A, 451A, 452A I/O Modules Cause There is an option in the system plug in that decides how the addressing of the I/O module is handled. If the checkbox "Xenta I/O modules commissioned with LNS" is checked (this is called preconfigured in the old NDB tool and in XBuilder), the Xenta starts communicating to the I/O module using the subnet node address it has been given by the network tool (Lonmaker).  If the Checkbox is not checked, the Xenta will communicate with the I/O module on the neuron ID first to give the module the address that it thinks it should have. Resolution If the checkbox "Xenta I/O modules commissioned with LNS" is checked in the System Plug-In, and you replace the module in LonMaker, you do not have to download the Xenta. If the checkbox is not checked (the I/O module does not need to be commissioned in LonMaker), you have to download the controller or you can add the I/O module using the OP.

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.  

Issue How to Rehost an NL220 Dongle to another PC. Product Line TAC Vista Environment NL220 License Transfer Cause Once an NL220 licensing dongle has been locked to a PC, it cannot be hosted to another computer without Newron's involvement. If you use it on another PC, it will be in "MOVED" mode which allows you to do all engineering tasks except for ordering more credits. Resolution You need to "free" the dongle in order to be able to Rehost it on a new computer. Download the NLDongleUtility from Newron Systems here. A login is required, but it is free to register. Make sure the dongle is plugged into a USB port of the PC Launch the NLDongleUtility by going to Start > Programs > NLSuite > NLDongleUtility > NLDongleUtility At the bottom of the screen is a button that says "Free." Click this button. This generates a code in the green tinted window. Use the "Copy" button to copy the code. Paste this code into a "free request" email addressed to fr-newron-credits@abb.com They will reply with an update key that will unlock the dongle and you will then be able to host it on the new computer. When the software key is sent back from Newron Systems re-open the NLdongle Utility click the Free button at the bottom of the program. Paste the Free Key sent from Newron Systems in the Free Key section and click the "Free" button. Open NL220 and confirm the dongle transfer.

Issue Continuum Add-On Software products and support contacts Environment Continuum Continuum Reports Suite Continuum Archiver/Archivers Continuum Elevator Control Continuum Bioscrypt Integration Video Monitor For Third Party Video Systems Continuum Guard Tour Center of Excellence (COE) Cause Continuum Add-On Software products and support contacts information. Resolution Please forward Continuum Add-on Software support requests to COE.Support@buildings.schneider-electric.com The Reports Suite software can be downloaded here: https://ecobuilding.schneider-electric.com/search?documentUUID=e040ce9b-7114-4cbc-b9cc-bcde73a6d64e&title=Continuum%20Reports%20for%20CyberStation%20v1.81%20and%20v1.82%20Add-on%20Software Internal note: In bFO the Care Team to which PSS will De-Escalate case is the NAM_BLD_COE_ADV Care Team.

Issue Xenta group bindings are used for group communication between Xenta group masters and members.  They also transmit TAC Network Variables between two programmable controllers.  Redoing group bindings is a common troubleshooting technique to address issues with these functions.  However, it can often be time consuming, especially if using LonMaker which requires the Visio drawing to be resynchronized.  Verifying that the Xenta group bindings in the device's address table are correct prior to redoing them can save time on an unnecessary troubleshooting step. Product Line TAC Vista Environment Vista programmable controllers LonMaker, NL220 Cause Checking to see if the group bindings need to be redone instead of always using it as a standard troubleshooting technique can save time. Resolution To access the Device Address Table of an application device in LonMaker: Right-click on the controller in LonMaker and go to Properties. Go to the Address table tab. Look at the first two entries (0 and 1) and note the value in the ID column. Go to another controller in the same group and compare the values in the ID column. Every controller on a network should share the same ID in row 0. Every controller in a group should share the same ID in row 1. If the group bindings are correct, there is no need to redo group bindings.   To access the Device Address Table of an application device in NL220: Select the application device in the tree Press Ctrl+A keys or right click on it and select the option Network\Network tables ... in its context menu Select the tab Addresses    The grid contains one line for each entry in the address table. Index = The index of the address entry MT = Yes if the entry is reserved for message tags connection Type = Type of the entry, Unbound (Not used or "free"), Turnaround, Subnet/Node, Broadcast, Group Size = Size of the group (zero for a large group) and Used only if Type is Group Domain = Domain index (0/1) Mb/Node = Member if Type is Group (not used for a huge group), Node id if Type is Subnet/Node or Unused Repeat timer = Value of the repeat timer  Retries = Retries count Rcv timer = Value of the receive timer  Tx timer = Value of the transmit timer  Gp/Subnet  = Group id if Type is Group, Subnet id if Type is Subnet/Node or Unused   Refresh will refresh the table.

Issue Since both products -- Xenta programmables and the UNC 520 -- speak LON protocol, there is some assumption that integration should be seamless.  In the case of ASCs, this is true, but Xenta programmable controllers use some forms of proprietary communication that can complicate the integration. Product Line TAC IA Series, TAC Vista Environment Xenta programmables Xenta 280, 281, 282, 283, 300, 301, 302, 401, 401:B UNC-520 Niagara Tridium Cause Xenta programmables use proprietary communications for three main purposes: To communicate their online status between group members and group masters To communicate between a base unit and associated I/O modules To pass proprietary TAC Network Variables between two programmable controllers In a UNC-520, the first function would be taken over by the new network manager (Local Lon Device).  However, the second two must use Group Bindings set through a Vista compatible network management tool like LonMaker or NL220.  If the controllers are commissioned into the UNC-520, that communication will be broken and I/O modules will go offline and no network variables will pass. Resolution  It is possible to engineer a TAC Vista network as usual, using an LNS management tool to create group bindings to facilitate proprietary communications.  A UNC-520, set to non-network management mode could then be implemented on top. However, any attempt to commission the devices into the UNC-520 network will break that proprietary communication.  To prevent this scenario from occurring, the simplest method is: Do not use proprietary TAC Network Variables to pass data between controllers. Use only SNVTs which will be available to a third party LON network manager like the UNC-520 Make no SNVT bindings in a temporary LonMaker or NL220 database.  Let the UNC-520 handle all network management duties. Do not define Xenta I/O modules in the Menta Device Specification. Use only Xenta 421A, 422A, 451A and 452A I/O modules.  These have the capability to act as stand-alone LON nodes. Define the modules as LON nodes, configure them using Configuring inputs on Xenta 421A or 451A when using the controller as a stand alone Lonworks node. Bind to the inputs and outputs of the I/O modules in the UNC-520.

Issue When attempting LonWorks communications in WorkPlace Tech, the following error message is seen. "Failed to get communications type, using LonWorks as default" Environment WorkPlace Tech 5.7.x Echelon U10 USB LON Network Interface (part number ECH-75010) – TP/FT-10 Channel Cause WorkPlace Tech LonWorks communications is not properly initialised.   Resolution Re-initialise WorkPlace Tech LonWorks communications. In WorkPlace Tech, go to 'Tools' > 'Configure Communication'. Change the communications type to 'BACnet' and click 'OK'. Open up 'Configure Communication' again and change the communications type back to 'LonWorks'. This should re-initialise the LonWorks communications.

Issue After setting up an SSC controller, it does not come online even after multiple Resets and putting it into DFU Mode. Product Line Access Expert Environment Access Expert Windows Server 2012 Cause The device was previously set up, maybe at the office. Now, when taken out to site, it shows that it already exists on another instance. Resolution Open up the initial instance that it was set up on Right click and Delete the device Open up the new instance that it will be current on If already created, then communication should start automatically Once online, program accordingly

Issue Problems upgrading/installing SQL server. The SQL Server System Configuration Checker cannot be executed due to WMI configuration on the machine XXXXXXX Error:2147749896 (0x80041008). "Not clustered or the cluster is up and online” check fails. Note: In the screen shot above the clustering check was passed. Environment TAC Vista 5.X.X SQL Server 2000/2005/2008 all versions; upgrades and new installations. Cause The WMI (Windows Management Instrumentation) Control is a tool that enables you to configure WMI settings. Inadequate access permission will mean that the user is unable to access the WMI service. Resolution If one of these messages appears or other problems are encountered during installation or upgrading of an SQL server, follow the steps below: 1. Check the WMI settings Go to My Computer – either in the start-menu or go directly to the desktop icon if running windows in classic mode – and right-click on it. Select Manage. In the hierarchical tree in the pane to the left, expand Services and Applications. Locate WMI Control and right-click on it. Select Properties from the context-menu. If the message “Failed to initialize all required WMI classes” is displayed (see screenshot below) read on… 2. Change/check the DCOM settings Open the start-menu, click on Run and type “dcomcnfg”. The Component Services console should open. Expand Component Services and then expand the Computers folder. Select and right-click on My Computer. Select Properties. In the dialogue window that opens up select the COM Security tab. Under Launch and Activation Permissions select Edit Default. Check under Groups or user names to see if the group Everyone has been added. If not select Add, type in "everyone" and then click on Check names. Once the name is confirmed, click on OK. Ensure that the permissions Local Launch, Local Activation and Remote Activation are allowed for the group Everyone. Repeat the above steps for Launch and Activation Permissions but select Edit Limits.   Click on OK again to close the My Computer Properties window and then close Component Services.     3. Recheck the WMI Settings       Go back to the Computer Management console described earlier and locate WMI control under Services and Applications. Right-click on it and select properties. If all the steps have been followed the message should read "Successfully connected to local computer." After this it should be possible to upgrade/install SQL server.

Issue The user logged into Windows doesn't have permissions to the folder that contains the Continuum.mnu file,  the file is set to read only or the path in the continuum.mnu is incorrect. Product Line Andover Continuum Environment Continuum Windows XP Windows Vista Windows 7 Windows Server 2003 Windows Server 2008 Cause Permissions are restricted to the Continuum.mnu file or the path in it is incorrect. Resolution One of the follow solutions will resolve this: Click to download an edited default path Continuum.mnu and Menu.bmp  (links for the default path C:\Program Files (x86)\Continuum) Copy these files to each workstation that has an incorrect path Manually edit the file yourself if you have a path that is other than (C:\Program Files (x86)\Continuum) Grant permissions to the folder. The folder that contains the Continuum.mnu can be located by editing the Cyberstation in Continuum Explorer. WS Edit> Preferences tab> The file name of the main menu  Ex. c:\program files\continuum\userprofile\continuum.mnu Right click on Continuum.mnu and select properties. Deselect Read Only if it is selected. Change the path to the Continuum.mnu file to a folder that you have access to and copy the continuum.mnu to it. Ex. c:\program files\continuum\continuum.mnu While in edit mode, right click on each of the buttons and select Properties Use the browse button to select the correct x86 path (C:\Program Files (x86)\Continuum) Repeat this for each of the buttons and then save the Continuum.mnu file Copy these files to each workstation that has an incorrect path Also see Continuum.mnu file with C:\program files (x86) on 64 bit PCs points to C:\program Files and shows a blank screen.

Issue Satchwell "AL..S" series Spring Return Linear Actuator requires replacement. Product Line Field Devices Environment Satchwell “AL..S” series Spring Return Linear Actuator installed on Satchwell MJF, MZ, MZF, VJF, VSF, VZ or VZF series Plug and Seat Valve Body.  Cause Obsolescence of Satchwell “AL..S” series Spring Return Linear Actuator. Resolution Replace Satchwell ALMS Actuator with S-E M700 Actuator. The S-E M700 Actuator may be used to replace an existing Satchwell ALMS Actuator. It should be noted however that the S-E M700 Actuator is suitable for use with 24 volt power supplies only, while the Satchwell ALMS Actuator is a mains voltage device. The S-E M700 Actuator has an average power consumption of 30 VA and the use of an independent 230 / 24 volt Transformer rated 50 VA is recommended.  S-E Transformer Type TR60 (341-3060-000)   Replacement of Satchwell ALXS Actuator with S-E M700 Actuator. The S-E M700 Actuator may be used to replace an existing Satchwell ALXS Actuator. It should be noted however that where an existing Satchwell ALXS Actuator has been connected to a Satchwell Climatronic Controller via an independent Transformer, it is probable that the Transformer will have been rated to provide the level of power required by a single ALXS Actuator (23VA) In such circumstances the existing independent Transformer may also require replacement by another independent Transformer, rated to provide the greater level of power required by a single S-E M700 Actuator (50VA) S-E Transformer Type TR60 (341-3060-000)   Replacement of Satchwell ALES Actuator with S-E M700 Actuator. The S-E M700 Actuator may be used to replace an existing Satchwell ALES Actuator. It should be noted however that where an existing Satchwell ALES Actuator has been connected to a Satchwell Climatronic Controller via an independent Transformer, it is probable that the Transformer will have been rated to provide the level of power required by a single ALES Actuator (26VA) In such circumstances the existing independent Transformer may also require replacement by another independent Transformer, rated to provide the greater level of power required by a single S-E M700 Actuator (50VA) S-E Transformer Type TR60 (341-3060-000)   Please check the latest catalog for current equipment.

Issue Animations, gifs, updating values, hover overs or mouse event scripts work in Workstation but do not work in Webstation. Product Line TAC Vista Environment Vista Webstation TGML graphics   Dynamic values       Cause Various reasons can cause TGML graphics to not function the same in TAC Vista Webstation as in Workstation. Typical reasons can be: Using "Static TGML viewer" vs. "Dynamic TGML viewer". Under Static view, all animations are prohibited. Using unsupported script functions can cause animation to not work in Webstation. Sizes and the number of animated .GIF images used on a single TGML graphic page. Resolution Check if the Webstation is running under Dynamics view. Go to Start->All Programs->Schneider Electric->TAC Vista Web Applications -> Vista Web Setting. (For Vista 5.1.3 or prior, go to Start->All Programs->TAC->TAC Vista Web Applications -> Vista Web Setting instead.) Click on "Graphics/TGML Views" in the left panel. Make sure the TGML View is either “AutoDetect” or “Dynamics” in the right panel.  If it is “Static”, click on the drop down manual and choose a different display viewer.   Check if using any unsupported Java script. Please reference Vista Webstation unsupported TGML functions for more information.   If a TGML graphic page contains many animated GIF images, it can cause the animation on that graphic page to run slow, discontinuously, or not run at all.  The amount of animated GIF images that can be put on one single TGML graphic page various case by case. Therefore, the best way to test it is deleting all animated GIF images and add them back on one by one.

Issue How to change the default SMTP port in Vista 5.1.5 running on 64-bit operating systems Environment Window 7 64-bit Windows 2008 server 64-bit Vista 5.1.5 Cause The registry key that allows the SMTP port to be changed is located in a different folder when running 64-bit operating systems. Resolution Open the registry editor. Start\run and then type regedit Go to HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\TAC AB\TAC Vista\5.1.5\SMTP and locate the entry named Port. Double click on this entry and change it to the desired port number. Click OK. (The Wow6432Node folder is a folder that contains information about 32-bit applications being run on 64-bit operating systems).

Issue Document of Conformity (DoC) for Sigma controllers Environment Sigma DoCs UNC 632 696 796 DNN3 CE04 CE05 CE06 2004/108/EC The Electromagnetic Compatibility Directive 2006/95/EC   The Low Voltage Directive EN 61326-1:2006 EN 61000-6-1:2007 EN 55022:2006+A1:2007 EN60730-1:2000+A2:2008 EN60950-1:2006 (ed.2) +A11:2009 Cause Certificates of Conformity Resolution Signed copies of the Documents of Conformity are available on The Exchange

Issue Field Bus controller shows its version number as 0.000000. Learn controllers from comm port is very slow and fails when reloading the controller. Updating the firmware will not fix this problem. Product Line Andover Continuum Environment Cyberstation 1.74 above i2 controllers B3 controllers Cause There are many reasons that will cause the i2 and B3 controllers show their version number as 0.0000000 Wireless network enabled or Multi-Network card enabled on the machine. Database snatched from Flash RAM after power-cycle does not match to the Continuum Database Some controllers with special firmware (Such as B38XX-V with 4.501043) have points referenced by other controllers, this will make the source controller buffer to be full after more than 20 hours Unknown application software installed on the CyberStation PC B-Link fault will also cause this problem Resolution Exit Continuum CyberStation, then ensure only a single network card is enabled Fix the problem caused by database mismatching: Create a new database and bring the master controller online, Do learn from the commport and bring the field controllers online Click the "Reset" button on the Runtime tag after opening the controller editor. Do database initialization and connect the original database to see if the version number is correct or not. If not, skip to item 4. If yes, do SendToController and then BackUpToFlash Update the controllers to the latest version. Rebuild the CyberStation PC. Only have the Windows operating system and Continuum CyberStation installed. Skip over B-Link and connect Field bus to BCX1 comm2 directly to verify B-LINK has some fault, and then replace it with new one, if required

Issue When attempting to Discover devices on the Niagara Network getting the following message: java.net.socketException can't assign requested address. Environment G3 (Niagara) ENC Cause The address in the default gateway of the ENC is invalid. Resolution Under the station Platform open TCP/IP Configuration and enter the proper gateway address in the "IPv4 Gateway" field.

Issue Is there a wiring diagram available for the HOA BACnet Series Digital Output Override Cards for IA BACnet Controllers? Environment IA, MNB-300, MNB-1000, MNB-1000-15, BCS-HOA-3-BACNET, BCS-HOA-4-BACNET Cause Is there a wiring diagram available for the HOA BACnet Series Digital Output Override Cards for IA BACnet Controllers? Resolution A wiring diagram on the HOA card can be viewed in the attached document.

Issue Where can older versions of Cyberstation software be downloaded from? Product Line Andover Continuum Environment CyberStation Cause Older version of Cyberstation software archived to FTP site. Resolution Log on to FTP server ftp://ftp.andovercontrols.com/ Customer UserName: andoverrep Password : andoverrep   Older CyberStation versions are found in the CyberStation_Revisions directory.