Building Automation Knowledge Base

Issue How to set up extended logging. Product Line Andover Continuum Environment Continuum Cyberstation Extended Log Cause Configuration of extended logging. Resolution Sample configuration for extended logging. This example would create enough entries for a 24 hour period. Create an Infinity Numeric Select the logs tab Number of entries (96) Type will be LogInstantaneous (Stores the current value of this point at the beginning of every interval) Interval will be 15 minutes (15 minutes in a 24 hour period is 96 which is what we set for the Number of entries) By default the Workstations are setup for 5 minute checks to the controllers to see if there are extended logs to enter into the database. For more in-depth configuration of extended logging, please review Extended Logs in the Continuum Online help system.  For performance and load balancing please see Extended Logging gaps, performance and load balancing.

Issue Sporadic values in Vista or Vista Graphics show up as red X or "Invalid Value" Product Line TAC Vista Environment Vista Workstation Classic Environment Cause Vista is designed to only have one instance of Vista Server running per system.  If two Vista Servers are polling the same equipment, data will not be read correctly. Resolution Configure all machines as a Remote Workstation with the instructions below. The remote Workstation will be networked to the Vista Server you would like to remotely view. To allow for correct communication DCOM setting will also need to be set. See Helpful Vista Utilities - Configure DCOM instantly, Register ASP.NET for the utility to complete this process. Shut down all Vista programs, including Vista Server Start Vista Workstation You will see this log in screen: Click on "Options" to display this screen Change "[Local Server]" to the IP address of the machine with Vista Server running Enter your username and password and select OK 

Issue Downgrade SQL 2008 to SQL 2005 Restore from SQL 2008 to prior version. Product Line Andover Continuum, TAC INET, TAC Vista Environment SQL 2008 used by Building Management Software Cause Have database loaded on one machine using SQL 2008 and would like to move or change to SQL 2005 Resolution Golden Rule: A SQL 2008 database cannot be downgraded or restored to a SQL 2005 version. It is not possible to downgrade a database or a database backup. The SQL schema will not allow it.  For your current version of SQL: C:\Program Files\Microsoft SQL Server \80, \90, \100 Folders are the client tools. 80 = SQL Server 2000 90 = SQL Server 2005 100 = SQL Server 2008 How ever, it is not a rule. Since 2008 creates both 80, 90. The only way to find what versions are installed (besides regedit) is by the Sql Server Configuration manager.    For other SQL options related to I/NET, please visit SQL and version compatibility for Filemaster, Equalized Client, Remote Client, Limitations of SQL.

Issue IT departments want to install just the client software without attaching to the webclient server and want to know if there is a way to accomplish this. Product Line Andover Continuum Environment webClient Windows XP Windows Vista Windows 7 Windows Server 2003 Windows Server 2008 Cause Webclient deploys activex controls using several .cab file from the C:\program files\redist folder on the webclient server. These files must be delivered to the browser PCs with admin privileges on the client PC in order for webclient and webpinpoint to work. Here is a list of the .cab files and ActiveX controls that get installed AccWebUtils.cab - AccDotNetBootstrap Control, Crypto Class (Used for  regular webclient use) WebclientPinpointSetup.cab - PPBrowserMgr Control (WebPinpoint) WebclientVideo.cab - TACVideoControl.VideoControl (Viewing Video layouts) ** The other piece that doesn't get installed are the permissions for the caspol commands that must be set for zones in order to run schedules. See webClient schedules getting error 'request for permission of type' system.security.permissions or .net control error on Webclient reports related to webclient schedules and running the caspol commands 1.94 SP1 requires that Microsoft VC++ 2005 Redistributable SP1 x86 to be installed for webpinpoint, it prompts to install when accessing a graphic the first time Resolution There is no client side webClient PC installation. The method for delivering the necessary activex controls and files are triggered by the browser PCs access to the webclient server PC and then the files are delivered to the client.  Some IT departments use Microsoft  SMS or Active directory to deploy software in a locked down environment. To deploy webclient to these types of browser PCs, they would have to logon with Admin privileges to perform the one time install of these files. The only other method if the IT group has InstallShield or WISE package creation software would be to capture the browser PC installation and use the produced .msi file for client delivery. This is informational only and has not been tested by Schneider Electric.

Issue How to find a Vista 5 dongle ID if it has rubbed off of the dongle. Product Line TAC Vista Environment Vista 5 Windows Command Window Cause The Dongle ID is required for locking TAC Vista licenses to a site dongle. Normally, the dongle ID can be found on the side of a Vista 5 licensing dongle. However, on older dongles, this number can rub off.  It is still possible to extract the dongle ID using the GetTACHLInfo.exe dongle utility software. Resolution On the Start menu, click Run. In the Run dialog box, type cmd Click OK. In the dialog box, go to the folder C:\Program Files\Schneider Electric\License Server (as default) NOTE: for TAC Vista 5.1.3 and prior, go to the folder C:\Program Files\TAC\License Server. Use command "cd.." for going to the parent directory and command "cd folderPath" for going to a child directory. Can also view items in the current directory by typing "dir". In the dialog box, type GetTACHLInfo (or GetTACHLInfo.exe) and press Return. The dongle ID is listed after "TAC_HL_ID=". Read Find a Vista IV dongle ID (PSU ID) for how to find Vista IV dongle ID.

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

Issue Node reset messages are received at the Sigma server on a regular basis. Product Line Satchwell Sigma Environment Sigma software - all releases. Sigma firmware - all versions. Cause Messages designed to be sent to a server are being sent to a device node. Resolution The BAS 2800+ system allows Controllers and Terminals to have the same numbers allocated. In Sigma this is not possible as all device numbers are unique. Should a reference to a terminal accidently be left in a controller configuration, then the controller may send messages to this device number, the receiving controller will then reset. There are two ways to locate the source of the messages being sent to the resetting controller, they are: Use SigView to display all of the object data for a controller, and then search the data for the node number of the resetting controller. You will be looking for entries such as T(resetting node number). OR Disconnect the controller from the network, and then connect a laptop, configured with the controller IP Address, and running WireShark to record all network messages. Allow WireShark to run for a period greater than the time between controller node resets. Filter the WireShark messages to review only messages sent to the IP Address of the resetting node. Check what the source IP address of these messages is, and then use SigView to review this controllers data. A typical Wireshark display is shown below, in this case the trace is filtered on the "Source" IP Address. For more information on using WireShark, please review Using WireShark to analyse communications on an Ethernet network.

Issue Invalid or phantom Links, Hosts and IP's in Netcon.  This symptom exists when you penetrate Network Configuration and there are Links and NPRs that you have no clue as to who they are or where they came from. Product Line TAC INET Environment I/NET NPR-2000 Xenta 527 Cause This can happen is if a laptop was used to connect to the system from a different Network or from the outside. Once connected, its IP address and any link it shares are broadcasted to the other devices like PCs and NPR’s, thus populating the table with entries that do not belong or are non-existent for this location or system. It can also happen if you install an NPR/527 or replace  one with a unit that has been used elsewhere. If that use NPR/527 is being used as a reference host, it will infect the system with every IP address and Link in its routing tables. Resolution At this point there is no way to get it out of the tables except to Telnet into all devices, remove the IP tables and rebuild them from scratch. This may be a cumbersome process depending on the amount of devices that make up the system (PCs, Laptops and NPR’s). All of these would need to be set back to 0 reference host while the cleanup is being done. To get this cleaned up, follow the steps to start a Telnet session:   Go to Start > Run and type Telnet then hit Enter. Type open at the end of the prompt, hit the space bar and then put in the IP Address of the NPR/PC and hit Enter. A logon prompt will come up, type csi and hit enter Now type LA, this lists all the entries in the table. Type delall and hit enter. This clears out all the IP’s of the other devices. This would have to be done on all the devices. Once completed, start I/NET to verify that those are gone and then start referencing other PC’s, Laptops and NPR’s to get the system back online again. Note: The proper way to use a Service/Maintenance laptop that is used for multiple customer sites is to direct connect to the NPR to see the controllers of the other links that exist at the site. However, before starting I/NET on the service/maintenance PC, open Windows Explorer, C:\Program Files\Inet Seven and delete the XXX.dat files. These get rebuilt when I/O Server restarts, it also clears out all entries in the routing tables. See .DAT files.  You may also create a different configuration profile for each site. This will also keep the tables separate.

Issue Using STR-350 Bypass button as On/Off button in Classic Network Product Line TAC Vista Environment Vista STR-350 STR-351 Cause Sometimes on/off function is needed when using STR 350/351 to start or stop a device. Resolution Following the steps below to realize this function in Classic Network: Create a Menta file and Click "Add STR Module" in the Device Specification. In the Bits field of HVAC settings, change the value of the last 3 rd bits of the first line from "0" to "1". This bit is to switch the using Bypass button as on/off function on. Create an STRIN and STROUT module. Bind the STRIN to OccManCmd variable, while bind the STROUT to EffectOccup. Connect the STRIN to an real DO point to control the start/stop of device. But an calculation is needed because when the button is off, the value is 2 while the button is on, the value is 3 instead of simple 0/1. Also connect the STRIN to STROUT to make the output synchronize with the input, like the program below. You can also download the sample from here. For the application used in the LNS network, refer to the Using STR-350 Bypass button as On/Off button in LNS Network.

Issue I/A Series G3 weather service will not connect - error indicates java.net.SocketTimeoutException: connect timed out.  A browser on the same computer is able to access www.weather.gov without issue.  The application director output window displays the following ... WARNING [12:56:28 05-Dec-13 EST][weather] Updating forecast failed for Battle$20Creek java.net.SocketTimeoutException: connect timed out at java.net.PlainSocketImpl.socketConnect(Native Method) at java.net.PlainSocketImpl.doConnect(Unknown Source) at java.net.PlainSocketImpl.connectToAddress(Unknown Source) at java.net.PlainSocketImpl.connect(Unknown Source) at java.net.SocksSocketImpl.connect(Unknown Source) at java.net.Socket.connect(Unknown Source) at javax.baja.naming.BIpHost$SocketFactory.open(BIpHost.java:271) at javax.baja.naming.BIpHost$SocketFactory.open(BIpHost.java:264) at javax.baja.naming.BIpHost.openSocket(BIpHost.java:129) at javax.baja.net.HttpConnection.connect(HttpConnection.java:263) at javax.baja.net.HttpConnection.connect(HttpConnection.java:238) at com.tridium.weather.nws.NwsForecastReader.getFeed(NwsForecastReader.java:76) at com.tridium.weather.nws.NwsForecastReader.getFeed(NwsForecastReader.java:55) at com.tridium.weather.nws.NwsForecastReader.getForecast(NwsForecastReader.java:135) at com.tridium.weather.nws.BNwsWeatherProvider.updateReport(BNwsWeatherProvider.java:450) at javax.baja.weather.BWeatherReport.doUpdateWeatherReport(BWeatherReport.java:269) at auto.javax_baja_weather_BWeatherReport.invoke(AutoGenerated) at com.tridium.sys.schema.ComponentSlotMap.invoke(ComponentSlotMap.java:1357) at com.tridium.sys.engine.EngineUtil.doInvoke(EngineUtil.java:49) Product Line TAC IA Series Environment I/A Series G3 Enterprise Network Server ENC JACE Cause The connection timeout may be related to the proxy server.  By default, the weather service driver contacts the various weather.gov sites (alerts.weather.gov, graphical.weather.gov, etc.) directly as opposed to routing through the proxy server.  The connection times out as the proxy server is unable to route the request. I/A Series G3 (3.4 and higher) provides a service that can be added to the station.  The HttpProxyServer service is used to configure the station so that outbound web services know how to get through an outbound non-transparent proxy server.  The HttpProxyServer service located in the net module. Configure this service to the proxy server that will be routing. The user guide states the following. All services that make use of the bajax.baja.net.HttpConnection class will automatically roll over to using the proxy server once the HttpProxyService has been configured and enabled. The Weather Service is one of the services that is affected by this feature. Resolution Verify the updated weather modules are installed, see Weather information provided through the weather module in I/A Series G3 is no longer updating. weather-3.4.67.3 or higher weather-3.5.39.5 or higher weather-3.6.37.4 or higher To use this component: Open the net (Network API) module in the Workbench palette. Add the HttpProxyServer to the Services of the station. Configure the following properties in the Property Sheet view as required.     Status - This display only property displays the status of the Http Proxy Service. Fault Cause - This display only property provides an error message that indicates the reason for a fault. Enabled - This property has a true (enabled) and false (disabled) option. Server - This property provides a text field for entering the address of the proxy server you are connecting to. Port - This property is for specifying the port number for communicating with the proxy server. Exclusions - This text field allows you to designate addresses that are allowed to be contacted directly, therefore “excluding” them from having to be contacted through the proxy server. The default addresses in the field are typical addresses followed by a slash (/) and the subnet mask designation. Authentication Scheme - This property provides the following two options:      None - no authentication is required at the proxy server when this option is set.      Basic - basic authentication is required at the proxy server when this option is set. User - This is the login name to be used when authentication is set to Basic. Password - This is the password text that is to be used when authentication is set to Basic.

Issue Is there a template to help create the custom AccessFormat array? Product Line Andover Continuum Environment Creating a Custom Card, Access Format array for non standard Wiegand formats Cause As there is sometimes confusion on the way that the bits are counted from 0 or 1 and how to use a Plain English program to initialize the array an easy way to lay out the data would be useful. Resolution The attached Excel spreadsheet works as a template to enter the Access Format data. Click here to download Format Template.xls. Enter your required Wiegand format bit definition in the box at the top, then this will allow you to define the numbers to go in the AccessFormat array lower left, which automatically fills in the example program on the right. Also see: Setting up a custom Wiegand format access cardfor information on setting up an AccessFormat array. Determining Custom Card formats on Deciphering Custom Card formats. What is the range of Wiegand Card numbers and Site Codes I can use on Continuum? on maximum card numbers.

Issue TAC Vista SQL maintenance repeatedly fails. Not just once or twice, but on every attempt. Microsoft Management Studio View of error Vista Workstation view of error Environment TAC Vista 5.1.7 or newer. Cause The SQL maintenance feature was added to Vista in version 5.1.7, to regularly database defragment the database and prevent the follow-on effects of a fragmented database. This scheduled maintenance can fail for a number of reasons. Resolution Start by  taking a DSS writer server log using TACOS Tweak. Follow the steps below to do this. Goto the TAC Vista installation folder (C:\Program Files (x86)\Schneider Electric\TAC Vista 5.1.9 by default on 64-bit machines). Locate TacosTweak and double-click on it. Click on the "Category" drop-down box and select "DSS (Registry)". Locate the "DSS Server - Log Level" entry and increase the log level to "7" by entering the value in the value field and clicking the "Set" button. Locate the "DSS Server - Log file" entry and chose an appropriate path. Launch "TAC Vista Server Setup" and go to the SQL maintenance tab. Locate the "Run SQL Maintenance now" checkbox and check it. Click on "OK" or "Apply". Locate the DSS server log file and open it with a text viewer/editor. Search the log file for the following text "Maintenance Task - Starting" and check that the date time stamp is approximately when the "Run SQL Maintenance now" button was pressed. Examine the file carefully and follow the file line for line from this point until you reach "[ERROR] Fatal error : SQL Exception : Incorrect syntax near '('. NOTE: Contact Product Support Services if you are unable to interpret the log file or see another type of error than that described above. Once confirmed, launch Microsoft SQL Server Management Studio and follow the steps below: Locate the "taclogdata" database. Right-click on it and select "Properties"  Locate the "Options" tab and set the compatibilty level to SQL 2008 (or SQL 2005 if that is the installed version). Don't forget to set the DSS Server log level back to "5"!   A tool to simplify this process can be found here. Please note that this is not an official Schneider Electric utility.  

Issue How to place an order for more LNS credits to allow LNS plug-ins to work and to be able to commission more devices. Product Line TAC IA Series, TAC Vista Environment LonMaker NL220 LNS Cause There are two types of credits: Product specific credits like LonMaker and NL credits LNS credits   LNS LNS credits are assigned to the PC and when they reach zero, the LNS Server license goes into deficit mode. After 14 days the deficit mode will expire, at which time no LNS tools will be able to be used on that PC. To reverse the lockout, enough LNS credits must be ordered to cover the deficit and any additional nodes that need to be commissioned. Backing up, sharing, and restoring LNS databases can sometimes corrupt these LNS credits, which then prohibits you from launching any LNS plug-ins. For more help with corrupt LNS credits see Corrupted LNS Credits. LonMaker LonMaker credits are assigned to the PC. Both LNS and LonMaker credits are required, however when commissioning devices in LonMaker, LonMaker credits are consumed but LNS credits are not. Even though LNS credits are not consumed in LonMaker they are still necessary because certain LNS applications (i.e. TAC Vista System Plug-in) require them to operate. NL220 Each time a node is commissioned in NL220 it requires a NL credit and a LNS credit. NL credits are assigned to the NL220 dongle and can be used on other PCs in "MOVED" mode. LNS credits are also necessary in NL220 to operate certain LNS applications such as the TAC Vista System Plug-in.   To order more Echelon LonMaker credits see Ordering more Echelon LonMaker credits. To order more Newron NL220 credits see Ordering more Newron NL220 credits. Resolution To check the amount of LNS credits remaining on a PC go to Start > All Programs > Echelon LNS Utilities > LNS Server License Wizard and look for Credits Available.   To order more LNS credits: Go to Start > All Programs > Echelon LNS Utilities > LNS Server License Wizard In the box named Credit Order, type in how many credits to order, then click Next. Following the instructions at the top of the window, Click the Copy to Clipboard button to copy the PC key generated by LNS Server License Wizard. Click Cancel. Compose a new email and paste the PC key into the body of the email. Address the email to credits@echelon.com or your local Schneider Electric Buildings Business order department so they can place the order. Follow the instructions at the top of the email making sure to fill out all required fields. Once Echelon or the local Schneider Electric Buildings Business order department sends back an Application Key, go to Start > All Programs > Echelon LNS Utilities > LNS Server License Wizard. Click next and paste the application key into the field titled "Application Key". Click Finish.

Issue Effects of leap year with schedules and BMS Product Line Andover Continuum, TAC INET Environment I/NET Site Continuum Site Time, calendar, Gregorian Calendar Cause Leap year adjustment in calendar Resolution I/NET: I/NET will not be affected by Leap Year occurrence if DST and Time Sync is correct in the host computer. For Time Sync errors, please refer to Time Sync Error, Daylight Saving setup, please refer to Configuring Daylight Savings Time. Continuum: Continuum will not be affected by Leap Year occurrence to controllers or scheduling if the Cyberstation has the correct time. There have been no incidents in the past with regards to leap year. Leap year is no different than some months having 30 days, others having 31. More information on time sync of controllers check Time sync controllers to workstations. To sync Continuum to an external time clock read Synchronize Continuum system to external time clock.

Issue When opening LonMaker the LonMaker Menu list is not shown in Visio. Product Line TAC Vista Environment Echelon LonMaker 3.xx Microsoft Visio 2002, 2003, 2007, 2010 Microsoft Windows XP SP3 Cause Echelon LonMaker was not installed with Administrator rights or some of the default security settings have been changed. Resolution Older versions of Visio - Check the File Paths and Security Settings Open up Microsoft Visio on its own. Go to Start > Programs > Microsoft Office > Microsoft Visio. (Do not open up Visio by opening up the LonMaker project) Go to the Tools menu > Options and then select the Advanced tab. Click the File Paths button. (For LonMaker 3.1, go to Tools > Options > File Paths) In the Add-ons field make sure that the file path starts with DRIVE:\LONWORKS_PATH\LonMaker. The default path is C:\LonWorks\LonMaker. The path in the Templates and Stencils fields should DRIVE:\LONWORKS_PATH\LonMaker\Visio. The default is C:\LonWorks\LonMaker\Visio. The next setting to check is the Macro Security. Go to the Tools menu > Options > and then select the Security tab. Make sure that all of the below options are selected. Enable Microsoft Visual Basic for Applications Enable Microsoft Visual Basic for Applications project creation Load Microsoft Visual Basic for Applications projects from text Enable COM add-ins Enable Automation events   Newer versions of Visio - Check the File Paths and Security Settings Open up Microsoft Visio on its own. Go to Start > All Programs > Microsoft Office > Microsoft Visio. (Do not open up Visio by opening up the LonMaker project) Select "Options" on the left hand side of the window. Click on the "Advanced" section and scroll down to the bottom. Verify that the "Enable Automation events" box is checked. Click on "File Locations..." In the Add-ons field make sure that the file path starts with DRIVE:\LONWORKS_PATH\LonMaker. The default path is C:\LonWorks\LonMaker. The path in the Templates and Stencils fields should be DRIVE:\LONWORKS_PATH\LonMaker\Visio. The default is C:\LonWorks\LonMaker\Visio. Uninstall LonMaker and reinstall with the administrator account used to log into Windows. The following articles have information about another problem that can cause the same issue: Visio menu not displaying properly after installing Lonmaker 3.1 with Visio 2002  Visio will open but LonMaker menu is missing from the toolbar, the features are unavailable, or Error: "unable to launch visio with file lonworks.vst"  There are two other things you may try before uninstalling, that have solved the issue in some cases: Right-click any toolbar, Choose Customize > Toolbars tab, Choose the Menu Bar, Choose Reset Remove all registrations in the Tools menu, click Options, and then on the Advanced tab, click File Paths.

Issue Enabling XDriver on the first generation of controllers, 9200, 9400, 9940, 9900 including the enabling of TCP/IP Product Line Andover Continuum Environment Older Continuum sites Cause Connectivity to third Party devices using the old NCI or First Generation Controllers requires an updated file. Resolution For 1st generation controllers, a .upd file is needed to turn on the bit for the Comm port. There is 1 bit per port to enable X Driver then a second bit to enable IP X Driver support required for the Modbus TCP/IP driver. The same principle applies to the generation1, 9200, 9400 controllers.   These controllers have flash memory just for things like the Serial number, model num, & X Driver settings, even though the controllers have EEPROM's for the firmware   As far as loading these drivers using hyperterminal, apart from firmware, one can load the X Driver file/ code through hyperterminal if required, but easier to do through Cyber'.   These files which enable the Xdriver for the Comm port, and TCP/IP are available by filling out the Driver Request Form, then they will be emailed directly to the customer from the factory in U.S.   X Driver list (Search for 'Third Party Driver List') and Order Forms (Search for 'xdriver order form') are located on the Exchange Download site  Difference between first and second generation controllers, visit What is the difference between 1st and 2nd Generation X Drivers. For information on Physical Ports, visit What controller ports and physical standards are supported by the Modbus X Drivers?  For Second Generation Controllers, visit How to order a controller with or upgrade a controller to have XDriver support.

Issue When the Sigma client attempts to connect to the Sigma server it fails and reports an error "No Seats Available".  What is the maximum number of clients that can be connected to a server? Product Line Satchwell Sigma Environment Sigma version 4.08 Client connections Cause Sigma server is not licensed for the attempted client connection Resolution For a customers system check: 1.  The Sigma dongle is licensed for the number of clients to be connected.  From a working client see Help - About and the number of clients supported is shown in the brackets ().  The maximum allowed depends on the operating system where the OS itself limits the number of consecutive connections; Windows 2003/Windows 2008 server:  Maximum client connections is 10 Windows XP/ Windows 7:  Maximum client connections is 5 2. Run the file C:\Sigma\bin\Setupsvr.exe and check that if a local client (on the same PC as the Sigma server) that "My Computer" is ticked or for a remote client (not the same as the server PC) that the "My Computer" is un-ticked and the correct Sigma server IP Address is entered. 3. Also in the Setupsvr.exe for a remote client check that the HTTP Server Port is set the same as the Sigma server (default = 8080) 4. Close down another client to free up a seat 5. Purchase more licensed clients (seats) using ZSO_CLIENT-x (where x is the number of additional clients - max 5 for Windows XP/7 server and max 10 for Windows 2003/2008 server).  Must add the Dongle number to order.    For an engineers laptop (Local connection) running SigmaX check: 1. SigmaX 7.0.9 does not require an unlocking code, if your using an older version of SigmaX you will need to uninstall SigmaX and install SigmaX version 7.0.9. SigmaX 7.09 no longer unlocks Sigma (or BAS2800+). To unlock Sigma you will need to install the SBO (Verision 1.5, 1.6, 1.7, 1.8 or 1.9) or EBO license administrator (Version 2.0 or later) and unlock Sigma using the current EcoStruxure Building Operation Evaluation License. The evaluation license is available to download form the Schnieder Echange Extranet web site. Latest version of SigmaX download provides some information on the changes in SigmaX version 7.0.9 and provided a link were the software can be downloaded. 2. If the Ethernet connections have been enabled or disabled (i.e. laptop has been with IT or wireless switched off/on) then a new SigmaX code will most likely be required. 3. Run the file C:\Sigma\bin\Setupsvr.exe and check that "My Computer" is ticked.

Issue When using TAC Vista 5 Demo License and Site License at the same time, Vista returns “Your application was not able to obtain a license because the FLEXnet license server manager could not determine where to find the licensing data it needs. Please choose one of the following: Specify the License Server System Specify the License File Product Line TAC Vista Environment Vista 5.X.X with Site License and Demo License Cause Using Vista 5 Demo License concurrently with Site Licenses, or having an expired Demo License in the License File folder with Site License may cause Vista ignore the Site License or not fully read the Site License. Resolution Remove Demo License from the License File folder. Restart the computer. If the issue still exists, follow Switching from the Demo license to the site License in Vista 5.1.7 or older.

Issue Is it possible to configure Workstation so that certain users see certain alarm categories? Product Line EcoStruxure Building Operation Environment StruxureWare Building Operation Cause There may be a need to restrict access to certain alarms on a site, if for example a site is comprised of two or more buildings, it may be appropriate for users in Building 1 to only see alarms from Building 1, and not the others. Resolution To achieve this filtering a workspace, alarm view and user group must be configured. Start by creating an Alarm View object in Workstation. Edit the Alarm view and set an appropriate filter i.e. the alarm priority to be displayed. Next create a new Workspace. Ensure that an Alarms Pane is added and that the Initial Path property is set to the Alarm View created in step 1.  Create a new user group and add the Workspace created in step 3 to the group's Selected Workspaces. On the Software Permissions tab for the group, give the group Read permission for the Alarm View created in step 1. Add other appropriate permissions as required. Lastly, create a user a make them a member of the User Group created in step 5. Log in to workstation with the new user. You should then only be able to see the filtered alarms and the user should not be able to change the filter. Also check out the SmartStruxure Software Permissions Quick-Help video on the Exchange.

Issue Is it possible to see how many users are logged in to Webstation? Product Line TAC Vista Environment TAC Vista Webstation 5.1.X Cause The number of users logged into Webstation at one time is limited by the number of available licenses.  Need to have a way to monitor this resource. Resolution There is no built-in function in TAC Vista Webstation to see how many users are logged in at a certain time. The only way to see how many users are logged in at the same time is to use the License Server Webpage. There it is possible to see how many Webstation licenses are in use. To access the License Server webpage: Open a browser and type in localhost:8888 Open the "Dashboard" and click on "Concurrent" See also Using Lmtools in Windows Vista/7/Server 2008 for Windows Vista/7/Server 2008 OS.