Building Automation Knowledge Base

Issue Xenta programmable controllers can communicate to each other using TAC Network Variables (TANV). These are defined in the Menta programming and travel on Xenta Group Bindings in the LNS environment. If data is failing to update in the receiving controller, there are a few troubleshooting techniques that can help. Product Line TAC Vista Environment Xenta programmable controllers Xenta 280, 281, 282, 283, 300, 301, 302, 401, 401:B Menta LonMaker/NL220 Cause TAC Network Variable communication can be compromised for four reasons: Network path not defined correctly in the Menta file Network path name is too long Group Bindings not done correctly in LonMaker/NL220 Controller's network output capacity has been exceeded Resolution Verify the Network Path If the network variable has been populated by browsing Menta files on the hard drive, or was entered manually, it can be the cause of the problem. Even visual inspection of the network path is not 100% reliable -- a lowercase "l" and an uppercase "I" appear the same, for example. The only way to be certain the path is correct is to browse it in through the Vista database. Open the Menta file from the Vista database. Right-click on the receiving controller and select Edit. Editing a Menta file directly from the hard drive of a computer does not give you the same network browsing options and can lead to incorrectly mapped network variables. Double click the network variable AI block and go to the Bind dialogue. Next to the Network Address text field is a browse button ("..."). Click it to open the network browse window. This tree structure should be the same as the folder view in Vista Workstation. Navigate to the sending controller's public signal and click okay. Download the application to the controller. Verify that the Network Path Name is not too long If the network variable path name, or the Network Address, is too long then this will cause a problem.The network variable path name, if the point is in a module, looks like ControllerName\ModuleName\PointName. If it is not in a module then it will have the Program Specification name instead of a module name. So it would look like ControllerName\ProgramSpecificationName\PointName.  If the ModuleName\PointName or ProgramSpecificationName\PointName part of the path is longer than 33 characters, counting the "\", then it will not work. Verify Group Bindings are correct Refer to Verifying Xenta Group Bindings in an LNS system for the procedure on verifying group bindings. If the group bindings are not correct, redo group bindings and download the sending and receiving controllers. Calculate the total output of the controller Depending on the controller type, there are different limits on the network variable outputs.  This includes both SNVTs and TANVs.  If together, they exceed the capacity, there will be spotty updates and random signals that don't make it to the receiving controller.  Unfortunately, there is no easy way to count the TANVs. In the Menta file of the sending controller, go to Options > Memory Usage... > Advanced... Make note of the TACNV/SNVT Out Free number.  Each SNVT output defined in the Menta file consumes one of these outputs and decreases the number of Free signals available for use with a TANV. The only way to count the number of network variable outputs is to know each receiving controller that is pointing back to the sending controller with a TANV.  Unlike with SNVTs, EACH signal in EACH receiving controller consumes one of these available outputs.  If the output limit has been exceeded, the communication will suffer. Reduce the number of network variables coming from one controller by "cascading" signals.

Issue Network 8000 Ethernet networks experiencing the following symptoms should be upgraded: GCM panels reporting repeated off-line / on-line messages NIM lock-ups requiring power cycling to recover Loss of global data sharing with Network 8000 (RNET and SNET transmissions fail) Product Line TAC IA Series Environment Network 8000 GCM Ethernet NIM, part number GCM-ETH-001 Network 8000 GCM-86000 Series controller (GCM-86120, GCM-86110, LNC-100, SIM-CCN, SIM-MTECH, SIM-YORK, SIM-TRANE) 802.3U Ethernet (100 Mbps) or 802.3z gigabit Ethernet (1000 Mbps) backbone network Cause Ethernet NIM performance was enhanced in revision 11.2T. Resolution Upgrade all NIMs on the network to firmware revision 11.2T, with the single exception of any with revision 11.2P firmware. Click here to see Announcement 01-105 for more details. For details on the REVISED Flash clear procedure, see the NIM Networking and Configuration Guide, F-25955-4, Chapter 2, section titled "Special NIM Address Switch Functions". Click here to see the procedure. Please reference Verifying the current firmware revision of a Network 8000 GCM and if an upgrade kit is available regarding Network 8000 firmware, including current revisions and upgrade kit part numbers.

Issue Get "Error: Device type specified in MTA file is not what TAC Vista expected, Info: Download Application and Parameters"  when downloading to a Xenta controller from TAC Vista. Environment TAC Vista TAC Xenta 30x, 28x, 401 Cause The type of controller that you specify in the device specification in the Menta application have the be to exact type you are downloading to. So either there is a mismatch or there is another controller on the network with the address you are using. Resolution Right click and Edit the controller in TAC Vista Workstation. Log in to view the Menta application Check in Options > Device Specification that it is the right type. If not, change to the right type.

Issue Cannot commission an IC3 LON controller in LonMaker. It has become applicationless and the red service LED is flashing or is permanently lit.  Product Line Satchwell Sigma Environment Satchwell Sigma Controller IC3 IC LON FTT-10 NodeUtil Cause The Echelon chip has become 'locked' and requires resetting.  This can be caused by corrupted controller files, very high LON traffic (> 50% Bandwidth), or the controller has started from "start-up mode" or cold start.   Resolution The Echelon chip can be reset using NodeUtil.exe  .  This is a DOS-based program that can be loaded onto a laptop with an FTT-10 Echelon adaptor. A clean working set of controller files will be downloaded to the device. In the case of a flashing red LED - Download 'clean' files to the controller Start NodeUtil on the laptop and plug LON cable into the controller Reset controller (via onboard reset button) Activate the plug-in LON card service pin and the Neuron Id should appear on the laptop. Note: If further controller resets and service pin activations fail to generate the service pin echo then discard the plug-in card and replace with a new one. From the NodeUtil menu select 'R' and enter the Node Id number Confirm the reset of 3150 Node The service LED should stop flashing and the controller should now be 'Configured' that is not 'applicationless' In the red LED is permanently lit - Download 'clean' files to the controller, the Echelon chip will become locked again. Repeat the reset procedure using NodeUtil.exe, this will allow the controller to work, but the plug-in card will need to be replaced. Example of NodeUtil process; NODEUTIL> (H)elp with commands A -- (A)dd node to list. D -- Set the (D)omain of the network interface. E -- (E)xit this application and return to DOS. F -- (F)ind nodes in the current domain. G -- (G)o to node menu............. H -- (H)elp with commands. L -- Display node (L)ist. M -- Change node (M)ode or state. O -- Redirect (O)utput to a file. P -- Send a service (P)in message. R -- (R)eboot 3150 node. S -- Report node (S)tatus and statistics. T -- (T)ransceiver parameters. V -- Control (V)erbose modes. W -- (W)ink a node. Z -- Shell out to DOS. NODEUTIL> Received an ID message from node 2. Program ID is ICLON1a NODEUTIL> Received an ID message from node 2. NODEUTIL> (R)eboot 3150 node Enter node id for reboot (0-2) [2] :2 *** Neuron 3150: Rebooting will reset comm. params, node state on-chip EEPROM variables and buffer configuration Are you sure you really want to do this? (Y/[N]): Successfully rebooted node NODEUTIL> A second solution has been provided by a customer and could be considered if the above suggestions does not provide a solution. Alternative reset procedure provided by a customer is as follows: - 1. Removed the IC LON from both the LON and the Sigma network. 2. I used SCDU tool to re-node the ICLON to a random IP address, which I believe cleared the database and the files etc. 3. I removed the power form the ICLON and then removed the LON daughterboard card from the ICLON mainboard. 4. Re-instated power and re-installed the LON daughterboard card. 5. Connected with NODE Utility as per the product data-sheet below. And cleared the LON comms buffers as the suggested method. 6. Checked that the red constant service light ceased from the constant illumination. And witnessed that the Green LON heartbeat LED was operational. 7. Re-Node the ICLON to the original IP and check operation. * The Sigma IC-LON plug-in card can be purchased using the part number S-LON. The S-LON has been discontinued as of 29th December 2017 and it is now in the service period (limited quantities available for purchase). Refer to PA-00528 for details.

Issue What is the pin configuration for Modbus RTU when using a 9 pin comm port on a BCX controller. Environment BCX Modbus RTU Cause Connecting a BCX or CX controller to a Modbus RTU device. Resolution RS232 connection for a 9 pin BCX comm port.   BCX Comm 1 (9 Pin)            RJ 45 Connector @ Modbus device Pin 1 CXD        -->                 Pin 1 DTR Pin 7 RTS        -->                 Pin 2 CTS  Pin 4 DTR        -->                 Pin 3 CXD Pin 8 CTS        -->                 Pin 4 RTS Pin 5 GND       -->                 Pin 5 GND Pin 3 TD           -->                 Pin 6 RD Pin 6 DSR        -->                 Pin 7 DSR Pin 2 RD           -->                 Pin 8 TD        

Issue With Script Programs in Continuum we were able to check the variable time against an integer value. Like "if time>500 then...".  In StruxureWare Building Operation time is of the type datetime, no longer an integer. Product Line EcoStruxure Building Operation Environment Script Program Cause In StruxureWare Building Operation a datetime internally is now a 64 bit number, so dates can go beyond the year 2038 which was the top limit for Continuum.  Numbers in script for StruxureWare, like in Continuum are just floats ( 32 bits ) so when trying to map a 64 bit number ( the date ) into a float it is not going to work.  You will get very erroneous readings, therefore the ban. Resolution Here are some examples of the correct StruxureWare program: Remember that for the dates, you can only compare dates to dates, not dates to numbers… In general,   you CAN do the following:       compare dates to dates                ==>   if Date1 > Date2  then     add numbers to dates                   ==>    LaterDate = LastDate + 24*3600     subtract numbers from dates         ==>    EarlierDate = LastDate - 24*3600   you CANNOT do the following   compare dates to numbers                ==>   if Date1 > 500  then

Issue  Interstation links between UNC and Enterprise Server are not functioning. Product Line TAC IA Series Environment Windows 7 Windows Vista Windows XP Niagara R2 Cause Windows Firewall is enabled by default on desktop operating systems post Windows XP SP1. The Windows Firewall must be configured to allow unsolicited messages such as alarms and inter-station links from UNC's to be received by the Enterprise Server. Resolution WINDOWS FIREWALL OVERVIEW Windows Firewall is a “state-full packet filter” firewall by default. This means that all TCP packets trying to enter a system with the Windows Firewall enabled will be discarded unless those packets are responses to queries from that system, or if the packet is destined for a port that has an exception create for it. In other words, unless an exception is created, or the Windows Firewall is disabled a valid message such as an alarm or an inter-station link from a UNC will be blocked by the Windows Firewall and won’t be received by the Enterprise Server. Windows Firewall allows for exceptions to be created for particular ports and from particular ranges of IP addresses. For example, one could create a rule that accepts unsolicited packets on port 25, but only from the range of addresses from 192.168.0.1 through 192.168.0.254. There are two kinds of exceptions: program exceptions and port exceptions. A program exception is where the Windows Firewall is instructed to open ports that a certain program needs for unsolicited communications. This is the preferred method since Windows Firewall is only open while the program is waiting to receive the connection. In contrast, a port exception is the Windows Firewalls' way of acting like a port-filtering router. In other words, Windows Firewall can be configured to let in any traffic on a particular port whether it's solicited or not. Creating a Program Exception Windows XP Open Windows Firewall from the Control Panel and from the exceptions tab click "Add Program..." Click the browse button Navigate to the c:\Niagara\Version\Nre\Bin folder. Select the file “nre.exe” adding it to the list of programs. To specify which TCP/IP devices can use the port, click Change Scope and select one of the following To allow connections from any device, including those on the Internet, select “Any computer (including those on the Internet)”, and then click OK. (This is the default and least secure option) To allow connections from your local subnet only, select “My network (subnet) only”, and then click OK. (This is more secure than the previous option but will still allow a malicious attack from a PC on the network) To define a custom list, select “Custom list”, and then type a list of IP addresses separated by commas. (This is the most secure option) Click OK. The program will appear selected on the Exceptions tab under Programs and Services. Click OK to finish. Windows 7 Open Windows Firewall from the Control panel then select Advanced Settings: Right click Inbound Rules and select New Rule Select program and click Next. Click the Browse button Navigate to the c:\Niagara\Version\Nre\Bin folder. Select the file “nre.exe” and click Open to add it to the list of programs. Click next. Select Allow the connection and click next Select the Network profiles that the rule applies to and click next Domain The domain profile applies to a network when a domain controller is detected for the domain to which the local computer is joined. If you select this box, then the rule applies to network traffic passing through a network adapter connected to this network. Private The private profile applies to a network when it is marked private by the computer administrator and it is not a domain network. Newly detected networks are not marked private by default. A network should be marked private only when there is some kind of security device, such as a network address translator or perimeter firewall, between the computer and the Internet. The private profile settings should be more restrictive than the domain profile settings. Public The public profile applies to a network when the computer is connected directly to a public network, such as one available in airports and coffee shops. The public profile settings should be the most restrictive because the computer is connected to a public network where the security cannot be as tightly controlled as it is in an IT environment. Name the exception and click Finish Creating a Port Exception Windows XP Open Windows Firewall from the Control Panel and from the exceptions tab click "Add Port..." In the Port number field type 80 Select TCP. Type a short name for the port To specify which TCP/IP devices can use the port, click Change Scope and select one of the following. To allow connections from any device, including those on the Internet, select “Any computer (including those on the Internet)”, and then click OK. (This is the default and least secure option) To allow connections from your local subnet only, select “My network (subnet) only”, and then click OK. (This is more secure than the previous option but will still allow a malicious attack from a PC on the network) To define a custom list, select “Custom list”, and then type a list of IP addresses separated by commas. (This is the most secure option) Click OK twice. The Port will appear, selected, on the Exceptions tab, under Programs and Services. Repeat the procedure to add an exception for port 3011 Click OK to finish. Windows 7 Open Windows Firewall from the Control panel then select Advanced Settings: Select  Connection Security Rules: From right side menu, select “New  Rule” Select Rule Type then select Custom then click Next: Select “Protocol and Ports” then select the TCP protocol type, specify required ports, then click Next. This screen capture     shows the configuration for the I/A Series (Niagara) R2 required ports: On the “When does this rule apply screen, click Next, leaving all three areas checked. On the next screen, name the rule “Niagara 80, 3011 TCP” and click “Finish”. Repeat steps 3 through 7, above, selecting UDP instead of TCP.  All other entries are the same except in step 7 the rule name will be UDP instead of TCP. After completing step 8, the Connection Security Rules will be displayed in the center section of the program window.  You should see the following two rules:  

Issue Using a repeater to extend ACC LON bus. Environment CX9900 CX9940 CX9680 IOU Modules Cause Infilink repeater is designed for the Infinet field bus. Resolution The Infilink repeaters CAN NOT be used to extend ACC LON.

Issue Previously purchased WorkPlace Tech software is being moved from one computer to another. What proof of purchase is required for the software so that the purchase of a new copy is not required? How can they prove that they purchased the original copy if the original purchase order and invoice or license request form with unlock code cannot be located? Product Line TAC IA Series Environment WorkPlace Tech 5.x.x NOTE: Old installation must be of same major release (release 5) as the new copy being installed. If the old system has release 4 of the WorkPlace Tech software, the new computer will need to be running Windows XP and the release 4 version of the WorkPlace Tech software will have to be installed on the new computer. Cause Software needs to be migrated to a different computer. This could be due to an upgrade in hardware. Resolution The preferred proof of purchase is a copy of the license request form that shows the customer information, license requested, license unlock code, and the original sales order number. Depending on when or how the license for the existing copy of the WorkPlace Tech Tool software was ordered, this document may have been received by fax or email. If this information is available, a copy can be emailed along with the new license request form (requesting the same product license as the original) to IASeries.license@schneider-electric.com. Note that in some cases the new product code may vary slightly from the original. For example, the original license may have been for WP-TECH-52 and the new one for WP-TECH-58 or WP-TECH-50 -- these licenses are all equivalent. The WIB licensing team will verify the submitted information and if complete/correct, generate the new license unlock code. If the old computer is still functional, the License Diagnostic program can be used to generate a proof of purchase for the software installed on the computer. Use the following procedure to locate the proper version of the program and to generate the license diagnostic text file. NOTE: If the old computer has WorkPlace Tech release 4.0.0, skip step 2 in the following procedure. Open the Windows Explorer (My Computer icon) Search for the file "WPTLDiag.exe" in the Program Files folder of the C:\ drive (or drive where the program files have been installed). If found, skip to step 4, below. Search for the file "WIBSLicenseDiag.exe" in the Program Files folder of the C:\ drive (or the drive where the program files have been installed). Right-Click on the file found in step 2 or 3 and select "Open". This will cause the license diagnostic program to run. When the program opens its display, select Save from under the File menu and save the "WIB License Diagnostic.txt" file. On the new computer run the "Purchase WorkPlace Tech Software" or "Purchase WIBs Software" from the icon on the desktop and fill out the Field Office & Shipping information sections using the information for your office. The "End Customer Information" must match the information from the old system. In the Package List, the same product should be selected as was licensed on the old system. In some cases, the part number may be slightly different, for example, the old system may have been licensed for WP-TECH-53U and on the new system, the product code may be WP-TECH-50U. These license product codes are equivalent. Add the selected package part number to the order list, click the [Accept Order] button and output the order form to a file. Click the [Done] button to exit the purchase screen and click [Done] to exit the Purchase program. Email the saved license diagnostic form and the saved order form to Product Support Services for verification. Product Support Services will verify the information and if correct, forward the information to IASeries.license@schneider-electric.com for processing. They will email the unlock code back to the requesting office. Follow the normal procedures to install the unlock code.

Issue When configuring a SmartConnector, the custom assembly cannot be seen in the Add Processor Configuration tab.   Product Line EcoStruxure Building Operation Environment Microsoft Windows Server 2012 and newer, Windows 10 Cause Microsoft Windows Server Unsigned or unknown certificates Some files need to be "unblocked" after download in order to avoid security warnings from tools like Visual Studio about potentially unsafe content.   This is because the dll’s for the custom processor have been downloaded from an internet based source.   Otherwise, all the required dll’s for the solution may not be available in the service installation directory (normally “C:\Program Files (x86)\Schneider Electric\SmartConnector”). This information can be seen in the SmartConnector log file. SmartConnector will log an error when going to the point of adding a new processor if it can’t find a reference. It will point to the assembly which is missing. Microsoft Windows 10 The service needs to be restarted once the dlls for the custom processor have been added in the service installation directory. (“C:\Program Files (x86)\Schneider Electric\SmartConnector”) Resolution Microsoft Windows Server range To "unblock" a file, Right-click it in Windows Explorer Choose Properties from the context menu Click the Unblock button in the lower right-hand corner of the resulting dialog Hit OK or Apply Important: ZIP files should be "unblocked" before their contents are extracted. Note: Depending on the security policy level on the system, you may need to perform the same action for the DDLs once uncompressed. Microsoft Windows 10 To restart the service by Opening the service windows Select the SmartconnectorService entry Either click on the Restart button, or Stop then start

Issue Outside dimensions of the enclosure for the MNB-1000? Part Number MNB-1000-ENC. Environment Plant Controller, MNB-1000 Enclosure for the Plant Controller, MNB-1000-ENC Cause Need to determine mounting clearances. Resolution Outside dimensions are 12" wide x 11 1/4" high x 2 5/8" deep. See the figure below, from the MNB-1000 Installation Instructions, F-27347-3. (Figure 3, p.3.)   Click here for a link to F-27347.

Issue In Niagara G3, a BACnet proxy point was initially added to the database as Read only; how can it be change to a BACnet Writable proxy point? Environment Niagara G3 all versions Cause BACnet proxy point type (read only. writable, etc.) is selected when the proxy point is first added to the database. The BACnet Proxy Point was initially discovered and added to the database as Read Only Proxy Point. Resolution Unfortunately, once the BACnet Proxy Point is added to the database its Type value can not be changed. The Proxy Point will have to be deleted, rediscovered and re-added to the database. This time when adding the Proxy Point to the database, make sure to select writable for Type.

Issue What are the proper steps for inputting people in the Datacard ID Works Program? Product Line TAC INET Environment I/NET Seven Datacard ID Works Video Badging software Cause A new user or personnel needs to be added to the access control system. Resolution Logging into the ID Works Program The default user name is lower case admin The user password is also lower case admin   Choose the badge project for the card you are going to print. If you do not see the Project in the window area, select the "More Projects" button to see the complete list of projects.   Once you choose the project, a window will pop up for you to log into the ID Works Project.   You have a choice on how to log in. You can either choose to check the box next to "Use Trusted Connection" or under the "INetThirdParty" Login ID the password is lower case passinetdb3p. Typical process is to select the "Trusted Connection" option.   Select a New Production Form to fill out   Fill in all the information listed on the Production Form including taking the photo.   Print the badge. On the top ICON line the second one in going from left to right is the "Print" icon. Before printing the badge, make sure the Blank cards in the printer magazine are the correct ones, then click the Print icon. Printing the badge will also save the information in the I/NET Seven system and the ID Works system.  There is NO need to save the info first, and then print the badge.   With the Production Form on the Screen, DO NOT choose the RED X (X) on the icon task bar to clear the page. See Step #9 for further information on this matter.   If by accident, the RED X (X) button is clicked, the following window pops up. If "Yes" is clicked, all of the information and photos entered in the previous steps will be deleted from the I/NET Seven System and ID Works system. If this pop up is encountered, be sure to choose "No."   In order to refresh the project, go to the top task bar and choose the "Record" option. In the drop down list choose the “New” option. Then select a new Project for the next badge, this process will open a new clean Production Form to fill out.

Issue In Function Block Editor, it is possible to define units for function blocks, and these units can only be set to basic units. There is no way to add a metric prefix to the unit. For example W or Wh can be used, but it is not possible to define kW, MW or kWh, MWh. Unit configuration in Function Block Editor v. 1.8 Product Line EcoStruxure Building Operation Environment Building Operation Workstation version 1.8 or earlier Cause Metric prefixes are not implemented for function blocks in Building Operation version 1.8 or earlier. Resolution Upgrade EcoStruxure Building Operation to version 1.9 or later. When editing a function block In Function Block Editor click Select unit and choose unit and Prefix. Function block with prefix in v. 3.0

Issue Is it possible to just install the IA Commissioning Tool (WPCT) or IA Flow Balance Tool without having to install WorkPlace Tech? Product Line TAC IA Series Environment I/A Series WorkPlace Tech I/A Series WorkPlace Tech Commissioning Tool I/A Series WorkPlace Tech Flow Balance Tool Cause  WorkplaceTech is not required on the PC but the operator needs to use the WPCT and or Flow Balancing Tool. Resolution It is possible to install the WPCT and/or the IA Flow Balancing software without having to install WorkPlace Tech.  At the time of the WorkPlace Tech installation, there are three options to select from: WorkPlace Tech Flow Balance Tool Workplace Tech Commissioning Tool WorkPlace Tech 5.x. WorkPlace Tech Flow Balancing Tool is preselected.  It cannot be deselected – it must be installed.  You can choose to install the WorkPlace Commissioning Tool by selecting it. If WorkPlace Tech is not needed then do not select the box next to it. WorkPlace Tech will not be installed during the installation process.

Issue Security Expert PSU has Fault Icon lit and Status Light Flashing Red Every 3 Seconds indicating an issue with PSU Addressing Product Line EcoStruxure Security Expert Environment Security Expert PSU Cause The module address 254 is the default value which all modules are shipped with and is outside the range the controller can accept. This must therefore be changed during commissioning. See Page 41 of the Operator Reference Manual for details. There is an overall limit of 250 modules that can be connected to a single controller with the following limit on each type of module: Keypad Modules: 200 Input Expanders: 248 Reader Expanders: 64 Output Expanders: 32 The module addressing is defined per module type not by the position of that module on the network. You could have all modules at the same address as long as they are all different types. Example: With the following modules we could have all modules be set to use address 1: 1 x Controller 1 x Keypad 1 x Reader Expander (In this case onboard Reader) 1 x Analogue Expander (PSU) Resolution 1. Right Click on the SP-C Controller and select Module Addressing. Change the Address of the Analog Expander (PSU) from its default value of 254 in this case to a value of 1. 2. Then Update all Modules. 3. Select the Analog Expander (PSU) in the System and also change its Physical Address to also be 1. Save the changes. 4. The PSU should now come online and the Fault Icon on the PSU will no longer be lit.

Issue Customer has requested and received the Unlock code for WorkPlace Tech 5.7.7 and does not know where to enter it in WorkPlace Tech. Environment WorkPlace Tech Tool version 5.7.x or 5.8 Cause Needs to enter an unlock code for WorkPlace Tech Tool software. Resolution This process is documented in the section "Installing Unlock Codes" of chapter 5 of the WIBS Installation and Configuration Guide, document, F-26641 and is summarized here.  The installation instructions can be downloaded from the Publication Zone on iPortal (https://iportal2.schneider-electric.com/). Run "Purchase Workplace Tech Software" icon on computer desktop (See below if the ICON has been removed). Click "Unlock" Click on license to be unlocked. Enter unlock code in appropriate field on form Click [Generate License] Click [Done] to exit the Unlock window Click [Done] to exit "Purchase..." program. If the  "Purchase Workplace Tech Software" icon has been removed from the desktop, and WPT 5.7.x or 5.8.x was the first version ever loaded on the computer, the program will be found at: C:\Program Files\WorkPlace Tech\Licensing\Core\WPTLPurchase.exe After opening the program continue with step 2, above.

Issue Looking for actuator with position feedback signal for V321 (V292, V222) DN125-DN150 since M22/M50 does not provide this option. Environment V222 DN125 V222DN150 V292 DN125 V292 DN150 V321 DN125 V321 DN150 M22 M50 Cause Actuator with positioning feedback signal for DN125 - DN150 valves Resolution There are currently no suitable actuators available that gives the Forta features on the M22/M50 actuators. Also, there is no linkage kit that would make the Forta series actuators fit on the DN125 and DN150 size valves, due to its different design.

Issue Configured Loytec LConfig application as a service but still do not get communication from the LonWorks Network. Not able to get Service pin from LON devices connected with Loytec NIC from Enterprise Server Product Line EcoStruxure Building Operation Environment Enterprise Server 1.1 Loytec NIC852 (LConfig Tool) Windows 7 Cause LConfig tool version is too old. The LConfig tool, even if set to start as a service, also still needs to start before the Enterprise Server (ES), otherwise the Enterprise Server fails to establish its connection with the LonWorks interface. For information on how to set LConfig to run as a service refer to Not able to get Service pin from LON devices connected with Loytec NIC from ES. Resolution To rectify the cause 1, click here to verify if the LConfig version is the most recent one. If not please download the most recent NIC - LOYTEC Network Interface Software. To rectify the cause 2, you must set the Loytec (LConfig) application service to be a dependency of the Enterprise Server (ES), to do this follow these instructions: Using RegEdit (or similar) edit the Registry Key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\StruxureWare 1.1 Enterprise Server NOTE: For SmartStruxure version 1.3 and above, go to path: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\Building Operation 1.3 Enterprise Server Locate and edit the DependOnService string Add the text LoytecSrv (service name for the LConfig application). Close the editor and reboot the PC Note: When running the LConfig as a service the LConfig Tool is not available from the System Tray and must be started from the program shortcut, located under Start > Programs> LOYTEC Network Interfaces> LConfig As a quick visual check, to see if configured correctly, you can perform a LonWorks Device Discovery on your Enterprise Server, this will show the NIC which has been defined with a red box (see image below). If these are all blue then you will not be able to receive any communications from your devices. Also remember if using the Loytec LIP devices that these should be configured in Smart Mode.

Issue Where to find the documents for KNX System Integration with TAC Vista Product Line TAC Vista Environment KNX Protocol (LON) TAC Vista 5.x.x Cause When KNX Lighting system (LON) want to Integrate with TAC Vista system, It requires a Gateway to connect from KNX Protocols to TAC Vista. Resolution Download the KNX documents from the below link: Product Announcement - Field Devices Europe New 3rd Party Gateway between LON and KNX Learn more about LON-KNX Gateway