Building Automation Knowledge Base

Issue What is the firmware version that supports EcoStruxure Web Services in SmartStruxure Lite MPM Controllers? Product Line EcoStruxure Building Expert, EcoStruxure Building Operation Environment SmartStruxure 1.3 and above SmartStruxure Lite 2.7 and above EcoStruxure Web Services Cause SmartStruxure Lite controllers have two variants of firmware depending on the sales channel: Schneider Electric Can2go Resolution EcoStruxure Web Services are only available in Schneider Electric firmware versions and full EWS support is planned for firmware version 2.7.0 SmartStruxure Lite shows offline in StruxureWare Building Operation

Issue Waveforms for PS, AS, and I/O modules Product Line EcoStruxure Building Operation Environment SmartStruxure Site Cause Loss of power and UPS for the StruxureWare Building Operation and SmartStruxure product lines. Should you design a site with Stepped Approximation or Pure Sine Wave? Resolution Concerning the UPS, and in particular the APC UPS 650, this is a good UPS, but the problem is that it would still interrupt the power for enough time to reset the AS. The AS has a 100mS capacity. AS Power supply interruption or failure has a bit more information would be beneficial to read through. A good UPS would be one that is Online or sometimes referred to as Double Online. This means that the power is not interrupted. The APC UPS line that has this is the SmartUPS and the base model is the old 1000XLI. This model may or may not be available in every country, but there would be a comparable model available. APC has been replacing the 1000XLI with various models, but all have the capability to go directly to battery, then back to power once the power is restored (assuming that there is a backup generator or the main power is restored) before the battery is pulled down. The Automation Server is powered from one or several PS-24V units. They have and peak voltage rectification on the input and the voltage waveform should not be an issue as long as the peak voltage is similar to that of a sine wave. If the input voltage is increasing with a very high dV/dt there may be high input current peaks. Those peaks may but not necessarily be reduced by the 230/24V transformer.   Key Concept: Look for a model with the Topology of Line Interactive and the Waveform Type of Sine wave. Picture is simply for example but not required:

Issue Echelon Node Utility with Loytec NIC-USB Network Interface Product Line EcoStruxure Building Operation, Satchwell MicroNet, Satchwell Sigma, TAC IA Series, TAC Vista Environment Microsoft Windows 7 32-bit Echelon Node Utility 2.04 Echelon OpenLDV 4.0 Loytec NIC-USB network interface Loytec NIC driver version 4.1.3 Cause There is a need to run Echelon Node Utility using Loytec network interfaces. Resolution The easiest way to accomplish this, is to use the NodeUtil Launcher. This program scans the registry for known interfaces. It was created by an active Community member. * Do take note Schneider Electric Product Support does not provide support for the NodeUtil Launcher - for support please write the developer of the tool. Below are two methods to manually achieve this if you don't want to use the tool. Here are 2 methods to run Node Utility using Loytec NIC-USB network interface. Method 1 involves accessing the Windows registry to check the path name of the Loytec network interface. We are not modifying any entries in the registry but as always, we should be careful when we access the Windows registry. Using Windows registry incorrectly can cause serious problems that may require you to reinstall Windows. Method 2 will configure the Loytec NIC-USB to use LON1. If you have used an Echelon LonWorks interface as LON1, you will need to detach it before you can use this method. Method 1 Run Loytec LConfig tool. With the Loytec NIC-USB network interface connected, go to the 'USB' tab and test the connectivity Run Windows registry editor (Start > Run > regedit). Navigate to the path HKEY_LOCAL_MACHINE\SOFTWARE\LonWorks\DeviceDrivers. The interfaces will be shown here. Look for the interface with '_LDV'. Run Windows Command Prompt and navigate to the Node Utility software directory (whichever directory you have put Node Utility) and run NodeUtil using the command nodeutil -D"". See example below. Method 2 Run Loytec LConfig tool. With the Loytec NIC-USB network interface connected, go to the 'USB' tab and test the connectivity. Click on the 'Advanced' button. Check the option 'LON1 Support for device' and select the appropriate device in the drop down list. You will need to reboot the computer for this to take effect. Once the computer has restarted, run Windows Command Prompt and navigate to the Node Utility software directory (whichever directory you have put Node Utility) and run NodeUtil. Node Utility should now run.

Issue Identify between the various dongles used by Vista 2k, Vista 4 and Vista 5 License systems. Product Line TAC Vista Environment Vista 3.3x (Vista 2000) Vista 4.x.x Vista 5.x.x Cause Licensing and dongle technology used by Schneider Electric Vista has changed as new revisions were released. The manufacturer of Vista dongles is Aladdin which causes the designs and colors to lead to confusion over which dongle works with which version of Vista. Resolution Visual inspection and some software tools can be used to differentiate between the various Vista dongles. The Dongle Reset Utility for Vista 4 can be used to determine whether the dongle is for End User or In House use. The getTACHLInfo.exe program which is installed with Vista 5 and the License Server can be used to determine whether a Vista 5 dongle is End User or In House. Vista 4 End User Dongle A Vista 4 End User dongle is only functional when an associated license file (PLF) is installed on a computer that was generated for the PSU ID of the dongle. This dongle can either be USB or LPT in size. If the dongle is LPT it is typically white in color. If the dongle is USB the color is typically blue. When viewing the dongle through the Dongle Reset Utility it will report the type of dongle as Enduser PSU and show the PSU ID. Vista 4 In House Dongle A Vista 4 In House dongle, commonly referred to as an Engineering Dongle, activates the Engineering license files which grants a branch or partner access to the majority of Vista licenses. This type of dongle is not intended for use on customer sites outside of commissioning and maintenance work. Custom licenses can be generated for In House dongles, but it is not common. This dongle can either be USB or LPT in size. If the dongle is LPT it is typically white in color. If the dongle is USB the color is typically blue. When viewing the dongle through the Dongle Reset Utility it will report the type of dongle as TAC Vista IV Inhouse PSU and show the PSU ID. Vista 5 End User Dongle part number 000857510 A Vista 5 End User dongle is only functional when an associated license file (LIC) is installed on a License Server that was generated for the Host ID of the dongle. Vista 5 End User dongles only come as USB dongles and are typically purple in color. When using the getTACHLInfo.exe command the dongle will indicate that it is Enduser and provide the dongle ID. Instructions can be found in Find a Vista 5 dongle ID. Vista 5 In House Dongle - Part Number - 000885000 A Vista 5 In House dongle, commonly referred to as Engineering or Maintenance dongle, grants a branch or partner access to the majority of Vista licenses. This type of dongle is not intended for use on customer sites outside of commissioning and maintenance work. Custom licenses can be generated for In House dongles, but it is not common. Vista 5 In House dongles only come as USB dongles and are typically black in color. When using the getTACHLInfo.exe command the dongle will indicate that it is Engineer and provide the dongle ID. Side by Side Comparison Dongles side by side for size comparison:

Issue String comparison in TGML script is not working. Product Line TAC Vista Environment TGML graphics editor 1.1.X Cause Javascript has a string class and a string literal. String literals are denoted by double or single quotation marks ("" or '') and it is important to compare "like" with "like". String literal: string1 = "Apples" String class: string1 = target.getAttribute("Name"); Resolution A deeper comparison is required in the example below. Instead of: name = target.getAttribute("Name"); tmp = target.getParentNode().getElementsByTagName("Ellipse").item(i).getAttribute("Name"); if (tmp==name) Use: if (tmp.equals(name)) An example is shown in the TGML graphic attached. Download graphic Also check out the JavaScript Essentials - Episode 3 - Value Types Quick-Help video on the Exchange.

Issue The MVB actuator is no longer available from Schneider Electric Replacing a Controlli S300 Actuator Product Line Field Devices Environment VMB valves MVB actuators S300 actuator Cause Only the actuator requires replacing but the MVB is no longer available from Schneider Electric. Resolution Note: The MVB actuators are still manufactured by Controlli, but not distributed by Schneider Electric. Use the AG52 valve linkage kit 880-0129-000. For the Controlli MVB22, MVB26 and MVB28 or S300 replace with the MV15B-230 actuator For the Controlli MVB46 replace with the MV15B-24 actuator For the Controlli MVB32, MVB52 and MVB56 replace with the M800 880-0310-030 actuator If a D36 auxiliary switch was fitted in the  the MVB actuator or if the auxiliary switch was used in the S300 actuator then the following auxiliary switch packs can be used: M800, use the 880-0104-000 kit or order the M800-S2 880-0311-030 actuator which includes 2 auxiliary switches. MV15B-24/230, use the 880-0469-000 kit. Note: if the valve also requires replacing see VSB, VSB..F, VMB, VMB..F Schneider Electric replacement valves.

Issue In TAC Vista 5.1.9 when trying to lock a license file to an end user dongle, the taclic vendor daemon starts briefly, but then stops again and you see the error "Invalid license key (inconsistent authentication code)" in the taclic.log file. Usually you only see that message if the license file has been tampered with. 8:48:28 (taclic) Invalid license key (inconsistent authentication code) 8:48:28 (taclic) ==>INCREMENT Menta.View taclic 5.1 permanent 1 ISSUER=TAC \ ISSUED=30-may-2014 BORROW NOTICE=3424672 \ SN=FID__47eba299_146164ca427__7ec5 SIGN="13DC 795D AF25 E8ED \ D6EG 7BAA 8495 2ED7 B4B0 F6E4 EDD8 C3C1 6EAE 2BF0 598D 0759 \ AE4A 3C9E 391C A6ED B313 9971 369A 349C 8671 E194 2E42 E2DC \ 8A9A 7905" Product Line TAC Vista Environment TAC Vista 5.1.9 License Server Cause An issue has been detected in TAC Vista 5.1.9 when locking a license file to an end user dongle. You see the error "Invalid license key (inconsistent authentication code)" in the taclic.log file. The error is located in the taclic.exe file. Resolution Contact PSS for a permanent hotfix for this issue, or download it from Exchange Download Center.  Work around 1: Lock the license to the MAC address of the PC Follow Rehosting a Vista 5 License on the FlexNet License Server to rehost a license file to a MAC address.  Work around 2: Use a previous version of the taclic.exe file Access a PC having a previous version of the license server installed Locate the file "taclic.exe" and copy it - it's normally located in the TAC Vista installation folder under "License Server" Stop the license server on the PC having TAC Vista 5.1.9 installed Rename the original taclic.exe file to taclic_11.12.exe Paste the "taclic.exe" file you copied into the folder Start the license again  In general when working with the license system on TAC Vista versions from 5.1.8 and above, this utility can come in handy: TACLicenseServer Settings.

Issue Where to find Continuum SQL schema and table details so a 3rd party can have access to the database. Product Line Andover Continuum Environment Continuum Cause Third party requires access to the database Resolution It is not recommended that third party systems directly access to the Continuum SQL database as the Cyberstation software expects full access to all tables at all times. Should a table be locked or inaccessible to Cyberstation it may cause problems or runtime errors. We do not publish any details on the database tables or a SQL schema as Continuum is used for Security applications it would undermine the security of the product. Also the database does not contain live data, this should always be read directly from the controllers. There are other alternatives that can be used. Use an existing open protocol XDriver e.g. Modbus IP or other open protocol BACnet IP or MS/TP link to the 3rd party system or controllers, could also be linked to StruxureWare Building Operation Export the required data from a Listview, Group or Report for use by a 3rd Party Create a Plain English program to regularly export data to a .CSV or .TXT file, see Automatically export logged data to .CSV files Commission the development of a new Xdriver or other integration; contact UK Technical Services department for a bespoke solution, paul.bates@schneider-electric.com

Issue How Permissions works in EBO Product Line EcoStruxure Building Operation Environment Building Operation Workstation Cause Software Permissions are used to control user activities in a software application. For example, permissions can be setup to manage the type of data and commands the user has permission to within a workspace, panel, or domain. Resolution EBO software permissions comprise path permissions and command permissions. Path Permission: Path permissions give a user or user account group basic permissions to the objects defined in a path. The permission level set on a path applies to all sub levels unless you set a new permission level for a sub level. Command Permission: To make the system even more flexible and useful, you can assign a user account group with special command permissions. Use the command permission to control exceptions from path permissions that allow or deny actions on specific commands. Command permissions will not restrict a user from specific properties of a given window. They function to remove items from Action or Right Click menus. EBO uses the following basic rules to interpret software permission priorities: The path permission settings of lower branches overrule the settings of higher branches within a user account group For example, a user account group has the Read permission to the path /Trend_Logs and Full Access permission to the subbranch /Trend_Charts. Users in the user account group have permission to modify the objects in the /Trend_Charts but can only view the objects in the superior /Trend_Logs. If the path /System has the permission level Read, and the subbranch /Alarms has the permission level Full Access, the users in the group have full access to the objects in the /Alarms path. The highest permission rule wins between user account groups. For example, if a user has inherited the permission to accept an alarm from one group, this overrules settings from other groups that deny the user the permission to acknowledge alarms. The software permissions for a single user account overrule the permissions of any inherited user account group permissions. The path permission rules also apply to the basic commands Create, Copy, Paste, Cut, Move, Rename, and Delete. For example, you only need the Read path permission level to copy an object but you need the Full Access path permission level to paste an object. See the table for more details.       Download Software Permission.pdf, the detailed guide about how permission works in EcoStruxure Building Operation (Formerly known as SmartStruxure) and how to make it work.  Check out the SmartStruxure Software Permissions Quick-Help video on the Exchange.

Issue Is there support for the C-Bus protocol in StruxureWare Building Operation? How can we integrate C-Bus into StruxureWare Building Operation? Product Line EcoStruxure Building Operation Environment StruxureWare Building Operation 1.0, 1.1 and 1.2. Cause Requirement to integrate C-Bus protocol into StruxureWare Building Operation, Automation Server or Enterprise Server. Clipsal C-Bus integrated service provide two gateways (BACnet / OPC), that may provide a suitable integration option. Resolution StruxureWare Building Operation does not directly support the C-Bus protocol at this point. Currently Schneider Electric Buildings integration with the C-Bus protocol is typically through the Xenta 913 (See Tip and tricks for communication between Xenta 913 and C-Bus on how this is achieved). When Interfacing the Xenta 913 to the Building Operation offerings you must create connection objects to and from the C-Bus objects via SNVTs, which need to be separately created within the Xenta 913 XBuilder project. Once these SNVTs are exposed, then the Xenta 913 can be added on the LonWorks network allowing the unit to be discovered as a LonWorks device (i.e. only acting as a third party LonWorks device). There are also two offerings provide by the Clipsal Integrated Services division that can be integrated with Building Operation, these are:   1. C-Bus BACnet Gateway (5000BACnet) The C-Bus BACnet Gateway is an embedded device that provides a field bridge between Clipsal C-Bus lighting control systems and the BACnet open protocol. The C-Bus BACnet Gateway provides 255 group addresses from a single application address. The C-Bus BACnet gateway supports the reading and writing of BACnet objects between C-Bus and BACnet and is supplied pre-configured from the (Clipsal) factory. Below is the link to detail of the C-Bus BACnet Gateway (5000BACnet) https://www.clipsal.com/Trade/Support/Software   2. C-Bus OPC Server For larger C-Bus systems (i.e. >255 group addresses) then the C-Bus OPC Server provides a gateway for C-Bus and the OPC Data Access protocols. Current releases of Building Operation does not support OPC, so you will require either an OPC to BACnet or OPC to LonWorks application which can be purchased through third party vendors. SCADA Engine is the preferred Clipsal BACnet OPC Client solution used. http://www.scadaengine.com/ Even though this solution is focused on BACnet, it may also be possible for a similar solution using LonWorks. Below is the link to detail of the C-Bus OPC Server https://www.clipsal.com/Trade/Support/Software There are additional requirements for each of these options that may need to be considered, it is best to discuss these directly with your regional Clipsal representative.

Issue The EcoStruxure Web Services Interface has been successfully setup in a Enterprise Server but cannot see the Vista objects / points in Workstation Product Line EcoStruxure Building Operation, TAC Vista Environment StruxureWare Building Operation 1.4.x TAC Vista SmartStruxure Interface TAC Vista 5 and above Cause The Web Services interface hosts the Vista objects in the System / Hardware / EcoStruxure Web Services / TAC Vista folder, these must be hosted to the Server to become visible within Workstation.  Resolution Once you have navigated to the System / Hardware / EcoStruxure Web Services / TAC Vista folder you will see the list of objects available associated with the TAC Vista user name setup in the TAC Vista SmartStruxure Interface. From the list of Vista objects select the required ones you wish to use within the Enterprise Server database. The right click on the selected folder and select the Host EWS Objects... option. The next option is to select the Vista EcoStruxure Web Service interface that will host these objects. The objects will now be visible within the Enterprise Server / Workstation.   For how to create Vista interface in SmartStruxure, refer to How to Create TAC Vista Interface to SmartStruxure. For additional details see Creating an EcoStruxure Web Service Object on the SBO WebHelp site. 

Issue IP address using DHCP Product Line EcoStruxure Building Operation Environment IP network Cause Bacnet or Modbus IP loses communication Resolution The AS or ES may be configured using DHCP (Dynamic Host Configuration Protocol), this is usually set up using "Device Manager" See Troubleshooting AS configuration issues with IP address. However many other systems use fixed IP address and use the IP address to specify the controller or server. Thus it is usually best to use fixed IP addresses for the Automation Server and Enterprise Server, especially if using Bacnet or Modbus over IP NOTE When the IP address of an AS is manually changed, the IP address of the Bacnet or Modbus IP interface needs also to be manually changed

Issue Continuum running under MS Windows 7, Vista or MS Windows Server 2008 (including R2) Access event viewers at workstations other than the primary access server do not show events. Alarms acknowledged at one CyberStation would remain unacknowledged in the other CyberStations.  Product Line Andover Continuum Environment CyberStation Microsoft Windows 7 Microsoft Windows Server 2008 Microsoft Windows Server 2008 R2 Cause Problem in Microsoft MSMQ component. MSMQ service might not send or receive messages after you restart a computer that is running Windows 7, Windows Server 2008 R2, Windows Vista or Windows Server 2008. This will cause any Continuum component that uses MSMQ (such as Alarms and Access Events) to fail. Microsoft has issued a hot fix for this MSMQ problem. Resolution Use the following command prompt test to verify the problem netstat -ano | findstr 1801 The command tests whether MSMQ is listening for messages. For example, Continuum WS 'A' is the primary access server (PAS) with an Event Viewer 'EV' up,  a second Continuum WS 'B'  is also displaying the same EV. If MSMQ is functioning normally you should see the following. 1. is the IP address of WS 'B' that has established a link to WS 'A'  2. is the IP address of WS 'A', the PAS in this case. 2560 is the listening MSMQ process PID  You can clearly see that there is a MSMQ process (2560) in WS 'B' LISTENING on port 1801 If there is no MSMQ process listening the output of the command will show the loopback or localhost IP address 127.0.0.1 and you have to install the following Microsoft hotfix: Package: ----------------------------------------------------------- ----------------------------------------------------------- See Microsoft KB Article Number: 2554746   ** In very rare occasions, removing MSMQ and adding MSMQ again to the PC is required. ** Once it is re-installed, please refer to Access event viewers running in a workstation other than the Primary Access Server stop displaying events to set the MSMQ CleanupInterval setting to one hour in the primary access server.

Issue The Automation Server is constantly using 100% CPU causing a slow operation Product Line EcoStruxure Building Operation Environment Automation Server Cause Check which process is taking the CPU. Cause 1: The cause was found to be a Function Block Program which was corrupt in some way. When trying to edit, open properties or do anything with this Function Block Program Workstation just hang. The root cause of the problem with the Function Block Program was never found. Cause 2: Some schedules have more than one entry for the same time stamp (likely if the process "CScanner" is taken the CPU) Resolution Solution 1: After deleting the particular Function Block Program (which took over 2 hours) the CPU usage was directly down to 20%. Another solution for an AS with the same symptoms: After downloading a new database to the automation server and then restoring a backup the CPU usage went down to normal levels.  Solution 2: Check all schedules for duplicate entries, especially around the time where the CPU goes to 100%. Also check out the SmartStruxure Quick Help - AS CPU and Memory Loading Quick-Help video on the Exchange.

Issue Does Sigma run on Windows 10? Product Line Satchwell Sigma Environment Sigma Windows 10 Cause Is Sigma 4.08 supported on windows 10? Resolution No version of Sigma is supported on a Windows 10 platform except: Sigma 4.08 can only be installed on Windows 10 when the software is used as a transition into EcoStruxure Building Operation ( EBO ) and used with the correct version of transition component. For full details of Sigma 4.08 versions, build numbers and operating systems supported, see What operating systems is Sigma 4.08 supported to run on?.

Issue How to use L-IP in Vista Classic network. Cannot service pin controllers under L-IP in Vista Classic network. Values in Classic network under multichannel L-IP are showing "Invalid Address" and "No such entity" Product Line TAC Vista Environment TAC Vista Workstation L-IP NIC852 Cause LOYTEC L-IP needs to be configured as a server and into the smart mode in order to be used in the Classic network. NIC852 needs to be used with LOYTEC L-IP in the Classic network. Resolution Configure L-IP as a web server (How to Configure Lonworks Network Interfaces to Communicate on the IP to a Loytec L-IP Router using the Echelon driver).   Configure L-IP into Smart mode. There are two ways to configure L-IP into smart mode.  Flip the DIP switch or using a serial cable (RS232). Flip the DIP switch to activate the smart mode. The dip switch is at the side of the L-IP next to the Ethernet port. L-IP DIP switch has seven switches.  By default, DIP switch 3 is down and the rest switches are up. Flip dip switch 2 down to activate the smart mode.   Use RS232 serial cable to activate the smart mode. Read more information in the LOYTEC L-IP User Manual Chapter 4.4.2.2   Configure NIC852 Open LConfig and go to NIC852 tab (Start/All Programs/LOYTEC Network Interface/LConfig). NOTE:  LOYTEC Network Interface package can be downloaded from LOYTEC website, called NIC-LOYTEC Network Interface Software X.X.X Make sure “Enable device” is checked Click on “CNIP Configuration”. Under “Device IP Address” use computer's address and use 1628 as Port number. Under “Conf. Server IP Addr.” Use L-IP’s IP  address and use 1629 as Port number.   Click “OK”. Click on “Test Device”, and should return the serial number   Add LIP as a LTA in Classic network. Right click on the Vista Server and choose “New->Device->Communication Port-LOYTEC” Name the LTA (for example: LIP).   Edit LIP in Classic network. Right Click on the LOYTEC L-IP (in this example the LIP LTA) just added and choose “Properties”. Under Communication Settings, click on the arrow and select the available NIC852.   Commission the LIP in Classic network. Right click on the LOYTEC L-IP just added (in this example the LIP LTA) and choose New > Device > LonWorks Network Name the network (for example: LNS Right click on the LonWorks Network just added (in this example the LNS network) and choose “Commission and Download” Select the LonWorks Network (in this example the LNS network) and click the “Start the Selected Operation” button (up-down arrow button on the top) Click “Continue” when asking for “Continue operation?” Operation successful message should be displayed.   Refresh (F5) the tree in the left panel in TAC Vista Workstation. The L-IP LTA (in this example the LIP LTA) and the LonWorks Network (in this example the LNS network) should turn green afterwards. Now the L-IP is ready to communicate in the TAC Classic network.

Issue How can System Alarms be disabled? Product Line EcoStruxure Building Operation Environment Building Operation Workstation Cause There are over 230 system alarms and at times they need to be turned off temporarily. There is no straight-forward method to gain access to the (intrinsic) system alarms, so an instruction on how to disable them is needed. Resolution You cannot stop system alarms from triggering. But if there are system alarms that trigger often, you might want to "turn these off". The way to do this is to disable the alarms, which would cause the alarms not to trigger again until they are enabled. An alarm has to trigger first in order for it to be disabled. To disable an alarm, right click on the alarm in the alarm list and choose Disable alarm. There is no menu or object to access the system alarms only. For a list of system alarms see What system alarms can occur in StruxureWare Building Operation?

Issue How do I run Continuum Analyzer and get a report Product Line Andover Continuum Environment Continuum 1.7 onwards Cause The Continuum Analyzer is designed to provide installers and troubleshooters with a point of reference for discovering problem areas within their installations.  The software is proactive in that it enables you to 'clean' orphaned and mismatched objects from the database, thereby recovering from a minimal amount of database corruption.  Continuum Analyzer also performs a system information check and provides full reporting on all aspects of the installation, as well as alerts regarding deficiencies. Resolution Always ensure the site database backed up before Continuum Analyzer is used to "Clean" the database. Go to - Start - All Programs - Continuum - Continuum Analyzer Type in User Name and Password (usually andover97 and (not disclosed due to public access)) for the Continuum DB or you can use the system admin user name and password. Click on the version "System Tests", then "Run Wizards" There should be zero failed. Then "Generate Report". To save click on top left disk icon and save as .html file If there are any failures, then ensure the database has been saved before a "Clean" is performed There was a bug in some Analyzer versions that caused a ghost alarm on the AlarmInfo test, also see Continuum Analyzer Failure for Continuum 1.92 & 1.93

Issue When trying to commission a controller into a LonWorks network in SmartStruxure you get a DST error. Product Line EcoStruxure Building Operation Environment WorkStation LonWorks Interface Cause The DST error occurs during the commissioning of the controller when the DST settings are attempted to be downloaded. Resolution TAC Xenta 280 and 300 series Controllers If the DST error occurs when commissioning a Xenta 280 or 300 series controller then check the label on the side of the controller. If there is no /N/P after the model number then it is not a network presentation controller and can not be commissioned in SmartStruxure. For more information see Xenta 280/300 without /N/P designation cannot communicate in a Network.

Issue Xenta Controllers can report "offline" status if they encounter bandwidth limitations Completion Event Failure warnings CRC Errors showing in controller properties Loytec Multi-port router/switch channel LED blinking fast red (traffic overload) Product Line TAC Vista Environment Lon Networks Vista Xenta LPA Loytec Protocol Analyzer Cause HMI Vista on-line/off-line presentation is based upon receipt of the heartbeat messages. Every TAC Xenta 280/300/401 controller is periodically sending a message to the other members of its TAC Xenta reporting (including the group master) that it is on-line. Proprietary "LACNet-IAm" and "LACNet-GroupIs" are sent every 15 seconds to HMI Vista. Without the HMI receiving these heartbeats, Vista will display the controller or group in an offline state. The TAC Xenta group is specified by the tag_0 and the TAC Group is specified by tag_1 bindings in LonMaker or NL220. Resolution Actions for reducing Bandwidth: TAC Xenta 100s Slow down the SendHeartBeat Check sensors etc that are affecting all bound nvo's Decrease traffic of SNVT group bindings. For large groups of bound controllers, use UNACKD/RPT instead of ACK service type. 3rd Party LonWorks devices Change update rates for nvo's. If possible, the product manual should show how. Decrease traffic of SNVT group bindings. For large groups of bound controllers, use UNACKD/RPT instead of ACK service type. TAC Xenta 280/300/401 TACNV and SNVTs Verify delta and period values make sense for the particular signal and application. Decrease traffic of SNVT group bindings. For large groups of bound controllers, use UNACKD/RPT instead of ACK service type. Increase the trend log time span (the total log time) if possible. Of course, this will increase the memory usage in the Xenta, but this will make TAC Vista to do the fetch more seldom and result in reduced traffic. TAC Xenta 280/300/401 + TAC Xenta I/O Modules If sensitive sensors (i.e. pressure sensors) are connected to I/O Modules, a high load of communication will be generated. Bandwidth issues may arise when 401s with many I/O Modules are each reading multiple sensitive sensors. Increase the Min Send Time for every I/O Module. Min Send Time is how often the I/O module is allowed to communicate with the TAC Xenta. This setting is located in Device Specification in Menta. Reduce Trend Log definitions in the controllers. If possible, try to have all your "high speed sensors" connected to one, or a few I/O modules, so it's only a few I/O modules sending a lot to the Xenta. LonWorks routers Implement L-Switch routers to reduce traffic on high bandwidth segments. Set router to Configured Mode, not Repeater Mode. Vista Server Trend Log Stagger Vista server Trend Log start times so that they do not all attempt to get fetched at once. See also Troubleshooting LON Network Communication More information can be found in Tool for LON / LPA Capture Traffic Analysis (login required) which discusses the LPA Analyzer Tool. This may be useful for interpreting the LP file data.