Building Automation Knowledge Base

Issue Will public signals in TAC Xenta show up in Echelon Lonmaker? Will AI, DI, AO, DO, PVR, PVI, PVB blocks show up in Echelon Lonmaker?  Product Line TAC Vista Environment TAC Menta LonMaker or NL220 Xenta 30x, 401, 28x Cause Public signal are proprietary and can only be viewed from Schneider Electric products such as TAC Vista Workstation or EcoStruxure Building Operation. Resolution The answer to both questions is no. Only SNVTs are displayed in Echelon Lonmaker, and the SNVTs have to be added in TAC Menta and then downloaded to the TAC Xenta devices.

Issue "No license for LonWorks communication" Error when starting Workstation. Product Line TAC Vista Environment Windows 2008 Server X64 TAC Vista 5.1.5 Cause Windows Server is member of a domain. Configure the TAC Vista Server to run as a service, with a local user set as administrator to logon. Results in "No license for LonWorks communication" when starting Workstation. If starting the service with a domain user or local system, it works.  Resolution Windows Security Policy This may have something to do with UAC (User Account Control) in Windows. The user that launches TAC Vista was already as a local administrator, but it seems that a log out with the user, log in with a local user, and log back in with a domain user is necessary for some policies to be set. Licensing Registry The Vista licensing requires registry information on where to find a license file. This registry key is found in the following location: HKEY_CURRENT_USER\Software\FLEXlm License Manager\TACLIC_LICENSE_FILE If the user has not been logged in and configured to run Vista software, this key might be missing or misconfigured. Ensure that it has a proper value by launching Vista Workstation or running the TAC License Setup. Log in with the user that will run the TACOS service and run the License Server Setup application to ensure the correct file path is defined in the Registry.   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" in Vista Workstation TACOS startup delay utility

Issue 5.1.5 is now packaged into two different spanned archives because of how large the installer files have become. At this point there is a 300 MB file limit on exchange online and the 5.1.5 installer package is now 336 MB, hence the reason the installation package had to be split into two archives. Because the installation package is a spanned archive it will need to be opened with WinZip or a compatible archive program. In these instructions we will be downloading and installing WinRar to open the installation archives. Note 1: WinRar is technically not free software, but it does allow its demo license to extend on past the demo period. It is at the customer’s discretion on what legal and compatible archiving software they chose to use. Note 2: The built in zip archive program in Windows 7 will open this spanned archives without fail. Product Line TAC Vista Environment Vista 5.1.5 software download on any operating system older than Windows 7 Cause File limit set on exchange online and the built in .Zip extractors in older operating systems do not have the capabilities to open these spanned archives. Resolution Create a folder on your local C: drive and name it 5.1.5 To download and install WinRar please visit http://www.rarlabs.com/download.htm and find the appropriate version. If you would like to use Winzip instead, please visit http://www.winzip.com/win/en/downwz.htm to download and install the appropriate version Navigate to exchange online at Download Center login, and click the links Product > TAC Vista > Vista Software > TAC Vista 5.1.5 > Downloads Click the file named TAC Vista Server 5.1.5 with Workstation (File 1 of 2) and save. Save the file to the 5.1.5 folder created in step 1. Click the file named TAC Vista Server 5.1.5 with Workstation (File 2 of 2) and save. Save the file to the 5.1.5 folder created in step 1. Allow the downloads to finish and navigate to the location of the 5.1.5 folder. Right click on the file named TACVistaServer515.zip and select Open With > WinRar archiver WinRar should open the archive file and you can now double click and run the TACVistaServer515.exe file within it. This exe file will access the other file (TACVistaServer515.z01) within the 5.1.5 folder automatically during the install process.

Issue Using the Pocket Terminal 32 utility to set the UNC532 default gateway via the command GW 10.130.10.253 and then set the node configuration using the SDCU.  Communications from the Sigma server to the controller failed.  On checking the default gateway it had changed to 10.130.10.240. Environment Sigma (All versions) SDCU PocketTerminal32 Cause Using SDCU to write the controller node configuration wrongly changes the previously set default gateway IP address. Resolution Configure the controller first using SDCU and then set the default gateway IP address using Pocket Terminal 32.  Similarly, if any changes are made by SDCU then the default gateway IP address must be re-entered.  The SDCU utilities is available for download.

Issue How to convert a B4-920 to a BCX4040 Environment BACnet B4-920 BCX4040 CyberStation Cause How to convert a B4-920 to a BCX4040 Resolution ASCII export the B4-920 then modify the dump file to change from the B4-920 to the BCX4040.  Delete the B4920 from both the Continuum view and the BACnet view in Continuum Explorer. Import the converted dump file into the system.   Reload the new BCX and all it's child objects.  Execute a Find New BACnet Device to pull all the devices back into the BACnet view.  Execute a Send to DB on the BACnet side to pull all the objects in. NOTE:   Another option if you are running version 1.90 CyberStation or greater is to change the model number through the controller editor in Continuum Explorer.

Issue Does a single controller (2nd generation controllers such as NC2 and bCX) support two(2) Modbus TCP/IP xDrivers on two(2) different comm ports?    Product Line Andover Continuum Environment Modbus TCP/IP XDriver NC2 (CX9680) bCX4040 Cause Need to have Modbus TCP/IP interface with 3rd party devices for both Server mode (Slave mode) and Client mode (Master mode).  Resolution You can have only one Modbus TCP/IP XDriver on a Controller(NC2 or bCX).  In order to have Modbus TCP/IP XDriver for both Server mode and Client mode, there should be two different CX controllers, and  different mode of Modbus TCP/IP XDriver should be installed and configured on different controller.   Note: This also includes any IP XDrivers. You can only enable one IP XDriver per Controller. (Ex. You can not enable a BACnet IP XDriver on one comm port and a Modbus IP XDriver on another, you would need two Controllers for this - one IP XDriver on each)

Issue Seeing “Fail to get the next controller step 2 – 0” in the Download Server Diagnostics Window (or similar message) when attempting to download to controller. Product Line EcoStruxure Security Expert Environment Security Expert Cause There is a problem with the encryption between the client and controller. It's possible only one end of the connection is encrypted and the controller may have been defaulted. You can tell this by looking in the Event Server Diagnostic Window which will usually show entries similar to "Encrypted Packet Received". Resolution Remove encryption by selecting Disable Controller Encryption and attempt to download the controller.

Issue ARCNET Cable Requirements. Product Line Satchwell Sigma Environment Sigma 4.05 and earlier versions V53 and ARM7 Processor Boards Cause Sigma ARCNET Network cabling advice. Resolution The following Sigma Cabling Guide should be followed when installing an ARCNET network for Sigma:  Sigma Cabling Guide 2.2 Network biasing and earthing arrangements will be required and further information about cabling can be found in the following guides: For V53 Processor Boards (UNC496, 596, UNC532, DNN and IC integration controllers): Sigma Configuration Guide - Chapter 26a For ARM7 Processor Boards (UNC696, 796 & UNC632): Sigma Configuration Guide - Chapter 32; Sigma Configuration Guide - Chapter 31 For ARM7 Processor Boards (DNN3 Decentralised Network Node): Sigma Configuration Guide - Chapter 33 For ARM7 Processor Boards (IC3 Integration Controller): Sigma Configuration Guide - Chapter 34

Issue 1. What is the specification (spec) for a Sigma PC?  2. Do I need to use Windows XP SP3 with Sigma? Product Line Satchwell Sigma Environment Sigma Software Cause Minimum requirements for a Sigma PC. Resolution The highest PC specification should always be sought.   See the Download Center for the release note appertaining to the Sigma version in use. The release note will detail the minimum PC required and Windows version no. that can be used. For EBO transitions and Windows 10 compatibility, see the KB article Sigma and Windows 10 compatibility.

Issue Trying to install CyberStation 1.9x.  It completes but then pops up 6 errors saying "Access denied" Environment CyberStation 1.9x Cause Microsoft hotfix KB942288-V3 is installed or files are not getting registered Resolution Verify that you are installing Cyberstation with Admin rights Uninstall MS hotfix KB942288-V3 .  To do this see below. Click on Start then settings then select Control Panel from the Windows menu.  Double click Add/Remove programs. In Add/Remove programs make sure the "Show Updates" checkbox on the top of the window is selected. Scroll through the list of installed item and find the Microsoft update named "KB942288-V3" Select the update and then click the "Remove" button. Once complete shut down and restart the PC and reinstall CyberStation. Note: If KB942288-V3 was slipstreamed into the image that was used to install XP SP3 then you will not see this in Add/Remove programs Please use the link below to download a batch file to register some of the files that aren't getting registered. Copy it into c:\Program Files\Continuum, unzip the text file. Open the file and "Save As" a batch file and then run it. AccessDeniedRegisterFiles191.zip

Issue Satchwell ALX series Linear Actuator requires replacement. Environment Satchwell ALX series Linear Actuator installed on Satchwell MJF, MZ, MZF, VJF, VSF, VZ or VZF series Plug and Seat Valve Body. Cause Obsolescence of Satchwell ALX series Linear Actuator. Resolution Replace Satchwell ALX series Linear Actuator with MV15B-24 Linear Actuator and Linkage Kit :-  ALX = MV15B-24 + L7SV (880-0662-000). Note: this part no. is for both actuator and linkage kit.  N.B.  Should the Satchwell ALX series Actuator include a wired Auxiliary Switch then the following Accessory should also be installed on the MV15B-24 Actuator as appropriate :-  S2 – MV15B = Two independent 250 volt 10 amp / 3 amp rated SPDT Auxiliary End Point Switches.    Particular care should be taken when selecting an S-E Forta MV15B-24 Actuator to replace an existing Satchwell ALX series Actuator. The S-E MV15B-24 Actuator may be used to replace an existing Satchwell ALX series Actuator but it should be noted that where an existing Satchwell ALX series Actuator has been connected directly to a Satchwell Controller, an independent Transformer rated to provide the greater level of power required by a single S-E MV15B -24 Actuator (12VA) will also be required. (e.g. S-E Transformer Type TR32)  Where an existing Satchwell ALX series Actuator has been connected via an independent Transformer, it is possible that the Transformer may have been rated to provide the level of power required by a single ALX series Actuator (3.5VA) only. 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 MV15B-24 Actuator (12VA) (e.g. S-E Transformer Type TR32)

Issue Opening and running a Seven Report that uses the Calendar to define the date range feature for data after entering the values, and nothing happens. It does not pull up any data. Business Objects error is seen in the Calendar picker.  Product Line TAC INET Environment I/NET Seven revision 2.31 and higher. Seven Reports (Crystal Reports) Cause Crystal Reports has not been set up correctly on the host PC. An additional file has to be installed to handle scripts in Seven Reports. This file can be found under >Support>Sevenreport/CR_XI/PostCRSetup on the INET CD.  A read me is also located there to assist with the installation procedure: Resolution To resolve this issue, the following steps need to be implemented: Close I/NET and I/O Server Open up Windows Explorer and select the original CD Open up the Support Folder and expand it Select the CR-XI folder and run the SetupCrystalReportsXI.exe Once completed, go back into the folder again and run the Post CRSetup.exe Once this is completed, restart I/Net and I/O Servers again Open up Seven Reports again and run the associated report

Issue It is not possible to extract a Menta file directly from a Xenta programmable. If a backup of the Menta file, or a backup of the Vista database is not available, there is no way to extract the program from the controller. "File object contain no actual MTA file" when trying to open a Menta file. Product Line TAC Vista Environment Xenta Programmable Xenta 280, 281, 282, 283, 300, 301, 302, 401, 401:B Menta Cause Going out to a job site without a database backup, or a backup of the Menta applications (.MTA), leaves no way to view the Menta that is running in a Xenta programmable controller. Resolution Options are: Find a backup of the .MTA Menta application that has been downloaded previously into the controller. Find a backup of the Vista database.  Menta files are stored in the Vista database for each programmable controller. To extract a Menta file from a Vista database, the preferred method is described in Get all MTA files saved from a Vista Database. To extract the files one at a time, right-click on the controller and select Edit. Connecting to a live controller, it is possible to view all public values inside the controller and to extract a .COD code file.  Unfortunately, these cannot be used to create a .MTA to view the logic.

Issue The text on the prog object does change but the graphic does not show the same change. Environment Sigma all versions BAS all versions Cause Controller only update server graphics when the object changes state or exceeds the set tolerance.  If prog objects are written with the same condition but different texts in the return statements then the correct text may not be displayed until the whole graphic is updated.  For example 10 If P0|1 on then return true "Object 1 on" 20 if P0|2 on then return true "Object 2 on" 30 if p0|3 on then return true "Object 3 On" Resolution Write the programmable object to that will change state to update the graphic.  This may well have to be a dedicated object for the graphic.  For example using a time statement to check for a change; 10 if not time left then goto 50 20 If P0|1 on then return true "Object 1 on" 30 if P0|2 on then return true "Object 2 on" 40 if p0|3 on then return true "Object 3 on" 50 set timer 10 60 If P0|1 on then return false "Object 1 on" 70 if P0|2 on then return false "Object 2 on" 80 if p0|3 on then return false "Object 3 on"

Issue There is a compatibility issue between Revision 2 MNL controllers and S-Link sensors. This incompatibility is noticed when a later production S-Link sensor is connected to an older Revision 2 controller. When the sensor is connected to the controller, 88.8 appears on the sensor’s display window along with all of the other LCD icons. The display never recovers from this mode, which makes the sensor non-functional. Product Line TAC IA Series Environment MN-Sx sensors MNL-10Rx1 and MNL-20Rx1, where x denotes profile type (F, H, R) MNL-V1RV1, MNL-V2RV1, MNL-V3RV1 Cause New MN-Sx production S-Link sensor firmware is not compatible with older Revision 2 MNL controllers. Resolution Newer model S-Link sensors have been released to address this issue. The new part numbers are MN-S1-2, MN-S2-2, MN-S3-2, MN-S4-2, and MN-S5-2. The MN-Sx-2 model line was designed and verified to work with older Revision 2 controllers.  Reference TPA-RKFD-09-0028-00 for more details. Please note that the new MN-Sx-2 S-Link sensors are only for use with older Revision 2 controllers.

Issue There are a number of object tabs that support the functionality of exporting to a CSV file. Can this CSV file then be used as a template and imported into another site? Product Line EcoStruxure Security Expert Environment Security Expert Cause Not sure how to import objects from CSV as a database creation tool. Resolution The export options are so you can export the required records to a file as part of site documentation, administration etc. There is no way to import anything other than users using a CSV file. A database backup that is already configured can be restored to a new system to be used as a site template. Another option for using the same configuration is the Copy Controller Feature. If you want to have multiple sites within a single Security Expert Server, take a bank for example where each branch is a separate site in the one server but configured pretty much the same, you could utilize the Copy Controller feature to copy all the programming from the template controller to a new one. Please note that although this feature currently exists within Security Expert it is currently being worked on by our engineers to improve its functionality.

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 After upgrading, it now asks for the security key when launching Continuum. Product Line Andover Continuum Environment Continuum Cause Continuum stand-alone is not working in Demo mode after upgrading. Resolution Completely uninstall Continuum and re-install using the following steps. Warning: Incorrectly editing the registry may severely damage your system. At the very least, you should back up your current settings and any valued data on the computer before making changes to the registry. Go to Control Panel > Add or Remove Programs. Remove Continuum. Reboot the PC. Remove EPI Builder Run-Time. Reboot the PC. Remove Sentinel System Driver Installer if installed. Reboot the PC. Remove the Continuum entries in the registry using Regedit. Start > Run > regedit Browse to HKEY_LOCAL_MACHINE\SOFTWARE\Andover Controls. Select the "Andover Controls" key, right-click and select "Export" to backup the reg key. Select the "Andover Controls" key, right-click and select "Delete" to delete the reg key. Reboot PC. Install Continuum without a security key attached to the PC.  You should now be able to start Continuum in stand-alone demo mode.

Issue In MNB-1000 with firmware Revision 1.50E, the Router Table can be viewed and /or reset without resetting the Plant Controller. This allows users to clear table entries that could cause router problems, without needing to reset the MNB-1000. Product Line TAC IA Series Environment I/A Series MNB-1000 (Plant Controller) with firmware Revision 1.50E, or later. WorkPlace Tech Tool, Commissioning Tool (WPT CT) version 5.7.7 and later Cause Product enhancement. Resolution To view or reset the Router Table, choose from the following procedures, depending on the version of firmware: For MNB-1000 with Revision 1.50E, use a web browser to access the Plant Controller to view or clear its Routing Table. Click here to see the Release Notes for Revision 1.50E, for more details. For MNB-1000 with Revision 1.510, use the WorkPlace Tech Tool Commissioning Tool, version 5.7.7.  Go to the Device Properties, Diagnostics Tab, and Router Table Information button. Click here to see the Release Notes for WPT 5.7.7, for further details.

Issue After installing the Niagara AX Serial Tunnel client, the service fails to start and Windows displays the following error: Could not start the NiagaraAX Serial Tunnel service on the Local Computer. Error 1068: The dependency service or group failed to start. Product Line TAC IA Series Environment I/A Series G3 ENC I/A Series G3 Enterprise Server Microsoft Windows operating systems (any) Cause The selected, virtual COM port is in use by another application or is in conflict with another service running on the Windows host computer. Resolution Modify the COM port used by the Serial Tunnel Client. On the Windows host, go to Control Panel and double-click Niagara AX Serial Tunneling. Change the Serial Port to another selection that is not being used by other applications or services and click OK (see below). Reboot the computer

Issue An IC GEN OPC to communicate with an OPC server using OPC XML -DA. Product Line Satchwell Sigma Environment IC GEN OPC OPC XML-DA OPC DA Cause The IC GEN OPC does not support OPC XML-DA and only supports OPC DA. Resolution A third party gateway produced by Advosol enables the IC GEN OPC DA client to access third party OPC XML - DA servers.  Click here for details. The IC GEN OPC gateway.txt will still need to reference the third party OPC XML-DA server for example; Item0=4^ IndigoVision^ 192.168.246.95^ Fromlv.analysis.motionalarm1^ 0      Where 'IndigoVision' is a OPC XML-DA  third party server.