Building Automation Knowledge Base

Issue Windows update KB4519976 causes all Xenta servers to go offline in TAC Vista every few minutes. Product Line TAC Vista Environment TAC Vista Server Microsoft Windows 7 or Microsoft Windows 2008 Server Xenta 500 Xenta 700 Xenta 900 Cause After the Windows update, KB4519976 is installed, the SSL handshake behavior is changed. This affects TAC Vista and its communication with the TAC Xenta server. Resolution There are two workarounds available at the moment. Solution 1: Uninstall Windows update KB4519976 Solution 2: Turn off SSL for the communication between TAC Vista and the TAC Xenta server using the registry setting shown below. This means that only the login will be encrypted when TAC Vista is communicating with the TAC Xenta servers. Run the utility TacosTweak.exe, located in the program folder where TAC Vista is installed. Set "Only use SSL for login to TAC Xenta Servers(5xx/7xx)" to 1 to run the communication between TAC Vista and TAC Xenta servers without SSL. Restart the TAC Vista server for the changes to take effect.

Issue Satchwell VEU 2-port Unit Control Valve is obsolete. Environment Satchwell VEU 2-port Unit Control Valve installations Cause Satchwell VEU 2-port Unit Control Valve requires replacement due to failure. Resolution Satchwell VEU 2-port Unit Control Valve may be replaced by Schneider Electric VZ219 series Unit Control Valve, although dimensional differences may apply. It should be noted that VZ219 series Unit Control Valves are available in both Flat Face and Compression fitting specifications. The latest issue of the Schneider Electric Valves and Actuators Catalogue should therefore be consulted in order to determine the availability of the particular size / kv / fitting combination required. It should also be noted that any Actuator installed on the Satchwell VEU 2-port Unit Control Valve will not be compatible with the replacement Schneider Electric VZ219 2-port Unit Control Valve and that a Schneider Electric MZ20 series Actuator of the appropriate operating voltage / signal type will also be required.

Issue Additional information for creating Lonworks networks in ES, not covered by the StruxureWare Technical Guide. Product Line EcoStruxure Building Operation Environment StruxureWare Building Operation 1.3 SP1 Cause Additional information for creating Lonworks networks in ES, not covered by the StruxureWare Technical Guide. Resolution Setup of the NIC852 network interface for the ES is covered in the StruxureWare Building Operation Technical Reference Guide, chapter 37.9 L-IP router setup is covered in the StruxureWare Building Operation Technical Reference Guide, chapter 37.10   Here are some additional points not covered in the Reference Guide: To use the NIC852 as a network interface for the ES, you must configure the Loytec LConfig software to run as a service.  See Not able to get Service pin from LON devices connected with Loytec NIC from ES for more details. The L-IPs must be used in Smart Switch mode in StruxureWare.  There are two Smart Switch modes: 1.  Smart Switch Mode 2.  Smart Switch mode with No Subnet Broadcast Flooding. Only use the first of these modes.  This should be the default, out of the box.  See the L-IP User Manual for details of the DIP switch positions for each mode. The ES version 1.3 can host up to 100 Xenta devices + 100 LON devices in total. These can be divided across 5 logical networks (different domains). It is possible to have multiple L-IPs in the same network if needed - but the limit of 100+100 is per ES, not per network or L-IP. Loytec recommend that in Smart Switch mode an IP channel should have no more than 10 L-IPs and packet rates no more than 500 packets/s. If additional Xenta/LON devices are needed you can add them to one or more AS, below the ES. Observe the standard Lonworks guidelines when creating your network topology e.g. maximum number of devices per network segment, maximum length of runs for the chosen cable type.  Group your devices so that network traffic across channels is minimized. StruxureWare is unaware of your physical network topology - it just sees it as one big channel.  It will reserve a different subnet for each Xenta group you create, starting at subnet 253, but each Lonworks device you create will just be assigned the next available subnet/node address, starting at subnet 254 node 1.  This means that devices with the same subnet address will most likely appear on multiple physical channels. The Loytec L-IP in Smart Switch Mode can still provide effective routing in this situation as it builds its routing table based on the physical location of subnet/node addresses, not just subnets.  Other manufacturers' routers, even in learning mode, may not be so forgiving.

Issue Metasys® N2 Integration to SBO Product Line EcoStruxure Building Operation Environment Struxureware Building Operation Metasys N2 Cause This Quick Start Guide will assist the Schneider Electric branch or dealer installation team with the basic steps to bring the virtual BACnet devices emulated by the S4 Open: BACnet-N2 Router into the SmartStruxure environment as part of a Johnson Controls Metasys® N2 integration into SBO. This document is not intended to be a full tutorial or user manual for either the S4 Open: BACnet N2 Router or the SmartStruxure system. Refer to the manufacturer’s documentation for each of these systems for detailed information. S4 documentation, the complete Device Template library, and support utilities can be found on the support CD delivered with your S4 Open appliance. Please contact the S4 group for any questions on this process.  Resolution Step 1:   Follow the installation instructions provided with the S4 Open: BACnet-N2 Router to discover and publish the N2 devices in the Metasys® installation to BACnet IP. All operations in SmartStruxure will be against these emulated BACnet IP devices each representing the underlying N2 device. Investigate before you integrate! Validate the N2 bus to make sure that it is electrically in spec and that all N2 devices are working properly before starting the integration process. Assign a unique BACnet virtual network number to each S4 Open: BACnet-N2 Router. N2 devices connected to this S4 Open appliance are published as emulated BACnet IP devices under that network. The Configure Wizard in the S4 Open Management Console will assist you with generating a unique BACnet Device ID for each N2 device. Point instance numbers are included as attributes in our Device Templates for all application-specific controllers. Either of these can be manually overridden in the S4 Open Management Console to meet unique requirements. The S4 Metasys® Configuration File Conversion Utility can be downloaded from the S4 Group web site and will assist you in creating custom Device Templates for DX-9100 devices or application-specific controllers. You will need the corresponding .DMO or .PRN files as input to this utility. A detailed understanding of Metasys® N2 devices, the Metasys® system, and the associated configuration and commissioning utilities are necessary to support successful integrations. If you don’t have this expertise in-house, The S4 Group can recommend a consultant to assist you. NOTE: We highly recommend that you attend a two-day S4 Boot Camp to make sure that you have all the skills necessary to install and configure the S4 Open: BACnet-N2 Router. Step 2: Bring up the SmartStruxure BACnet discovery tab and select BACnet devices. In this example, you can see that the S4 Open BACnet-N2 Router was defined in Network 1 and the N2 devices are in Network 122. The other device in Network 1 in this example is a JCI NAE. The best practice is to assign the S4 Open: BACnet-N2 Router to the BACnet network that you are using as your BACnet backbone. As with any BACnet device, the BACnet-N2 Router must be assigned a unique BACnet device ID. Step 3: Expand the navigation pane to expose the BACnet Interface / IP Network folder. Then select and drag the N2 devices from the Device Discovery tab to the IP Network folder. SmartStruxure will tell you that an Upload is required. Respond OK. Step 4: Navigate to the IP Network folder, select the properties page for each device, and request an Upload operation. This will bring the device properties and point list for each N2 device into SmartStruxure. SmartStruxure will respond with the following confirmation as each upload is completed. Step 5: When the Upload process is completed for all N2 devices and the S4 Open: BACnet-N2 Router, you can continue your SmartStruxure installation process as you would for any BACnet device. Note that there will be no points published under the S4 Open: BACnet-N2 Router itself but you will be able to confirm the Operational Status of the system from SmartStruxure. The Schneider Electric support organization will supply pre-sales engineering support and first-level technical support for the Metasys® N2 to SBO integration solution. The S4 Group will be available to provide 2nd level support to these integration projects.  

Issue Connected to a remote site network via WorkPlace Tech and a VPN connection, but unable to see the sites BACnet devices. No I/A Series MNB-1000s, or any 3rd Party BACnet devices, are found in Workplace Tech or the Commissioning Tool. Product Line TAC I/A Series Environment MNB-1000 WorkPlace Tech (all versions) Cause The VPN does place the connecting WorkPlace Tech PC on the site network, but the BACnet/IP (MNB-1000 and 3rd Party) devices are on a different subnet then the subnet assigned to the WorkPlace Tech PC. Resolution When BACnet/IP devices are on different subnets, BBMD must be used in order for the BACnet/IP devices to communicate across IP subnets. Only one BACnet/IP device can be enabled as BBMD per subnet.   Setup the MNB-1000 as a BBMD device using the Commissioning Tool Open Device Properties of the MNB-1000 controller and select the IP tab. For Device Type select BBMD and save change. Setup WorkPlace Tech to connect to the BBMD device Select Tool from the WPT Select Configure Communication… Select BACnet and click on Change Select IP and click next Select Access a remote internetwork. For Host BBMD Address, enter the IP address of the MNB-1000 which was setup as a BBMD device. Click the Finish button to save changes. You should now be able to see and connect to the I/A Series and 3rd Party BACnet devices using WorkPlace Tech.

Issue Warning - Platform running low on RAM disk space (Niagara G3 Release 3.2.5 and higher) Environment I/A Series G3 (typically embedded ENC/JACE platforms) Cause Low disk warning for history RAM disk A station fault will be generated if the free disk space on the history / alarm RAM disk falls below the minimum percentage specified on the PlatformServices property sheet. Resolution During station startup,  /niagara/bin/ramdisk.sh is invoked to create the RAM disk partition.   The RAM disk is named /aram0 and symbolic links are created from /alarm -> /aram0/alarm /history -> /aram0/history.  After the RAM disk is created it is populated with the contents of the alarm.zip and history.zip files.  During a station save or shutdown, the alarm and history files on the RAM disk are zipped and stored under the station directory in alarm/alarm.zip and history/history.zip.  If this fault occurs, users should take one or more of the following actions to prevent history/alarm data from being lost: Reduce number of histories that you are collecting Reduce number of records in each history Increase history RAM disk system (requires reboot). Action 3, above, will reduce the available system memory and should only be taken if there is sufficient free system memory.  Rather than writing history and alarm records directly to persistent storage, a Niagara G3 station stores history and alarm records in a RAM disk. This approach reduces the number and frequency of writes to flash.  Be careful not to increase too much otherwise you risk consuming all the available JACE free RAM causing the niagarad to crash.  Review the free system memory and make sure to leave a buffer of at least 1 MB of free RAM.  The RAM disk size is stored in /niagara/lib/platform.bog and can be adjusted using Services -> Platform Services. After reducing the number of histories, etc. the RAM disk will still indicate a low warning message until the unused histories are removed from the history storage.  Delete the unused histories using the Database Maintenance view on the history component view within the station.

Issue When trying to log on to an ES or AS using HTTPS, you get "No connection to server" or it takes a long time. Using HTTP it works fine. Version 1.6.0 and below you get "No connection to server" Version 1.6.1 and above you get in but it takes an extra 25 seconds compared to normal Product Line EcoStruxure Building Operation Environment Enterprise Server Automation Server Workstation Cause The most common reason for this is that the port used for HTTPS is changed in the Software Administrator, and not added in Workstation when logging on. For a solution to that, please check Workstation Log on failure due to unidentified port. A more rare reason for this has been identified on sites with strict network policies or no connection to the internet. The reason this is happening is because an application using SSL or TLS (e.g. OpenSSL) is regularly checking for certificate revocation. That can normally only be done if the PC has internet connection. If the PC can't connect to Microsoft's server to get the newest list of revoked certificates, the application will appear to hang or fail to use SSL. For a deep explanation of certificate revocation check and the base of this article, read Citrix' article: Slow Web Interface\MMC console? CRL explained. The issue can be confirmed using Fiddler. Here is an example on how to identify the issue.: Another way to check it, is to enter the URL used to retrieve the list on the PC having the issue: http://ctldl.windowsupdate.com/msdownload/update/v3/static/trustedr/en/authrootstl.cab?baa88d4bbbfc38e4 When trying to access that URL from a PC having this issue, you should get "HTTP Error 502 Bad gateway". Resolution Download the newest CRL updates from a PC with internet connection http://crl.microsoft.com/pki/crl/products/CodeSignPCA.crl http://crl.microsoft.com/pki/crl/products/CodeSignPCA2.crl Copy the two files to the PC having the issue Open a command prompt and navigate to the folder where the files are located Install the CRL files using the following commands CertUtil -AddStore CA CodeSignPCA.crl CertUtil -AddStore CA CodeSignPCA2.crl

Issue How to setup OSDP Readers on Access Expert Product Line Access Expert Environment Access Expert Hosted Software Access Expert Premise Software Cause Clear recommendations and instructions needed for the process Resolution OSDP Readers with Access Expert Overview OSDP stands for Open Supervised Device Protocol. It is the replacement of the older clock and data style and Weigand protocols that have been used across the industry for many years.OSDP is based upon an industry-standard from SIA (Security Industry Association) and has various levels.  The original version was called OSDPv1 which was followed by OSDPv2 then Secured Channel Communications was added to OSDPv2. This document will address how to add an OSDPv2 and/or OSDPv2 Secured Channel reader to an Access Expert system. As we move more into a data secured and encrypted environment, it is recommended that all deployments be installed based upon OSDPv2 at a minimum.  More information on OSDP can be found at https://www.securityindustry.org/industry-standards/open-supervised-device-protocol/. When compared to Weigand, OSDP offers various technological advancements with the increased level of security being one of the key benefits associated with OSDPv2 Secured Channel. More Security: OSDP v2 with Secure Channel protects readers against hacking using AES-128 encryption and OSDP constantly monitors wiring to protect against tampering. OSDP helps overcome the growing threat of “man in the middle” attack. More Functionality: OSDP uses fewer wires, allows for multi-drop installation, supervises connections to indicate reader malfunctions, and can disable the reader automatically when removed from the wall. Bidirectional communication: OSDP supports bidirectional communication. This means that the reader configuration can be set at the software and then sent to the reader via the intelligent controller More Interoperability: Using OSDP enables communication among different manufacturers' devices. More Consistency:  Not only does OSDP provide a concise set of commonly used commands and responses, but it also eliminates guesswork since encryption and authentication are predefined. Ease of Use: Low cost of implementation on an embedded device and simplification of the encryption and authentication process. Most readers come with both Weigand and OSDP support already available. Reader Wiring & Prerequisites Prerequisites: Readers wired for OSDP Readers that support OSDP HID Mobile Reader Manager App (iTunes or Google Play) HID Reader configured for OSDP and addressed It is possible to deploy OSDP readers on Access Expert without using the HID Reader Manager App provided you are not “stacking” readers on the same controller port.Stacking is a process of putting multiple readers on the same controller and the same port. If stacking is being used, the HID Reader Manager App will be required to set the 2 nd readers' address. As an example: Application Need Reader Port 1 Reader Port 2 Parking Garage The project will have 2 Parking gates where each will have dual readers Reader 1 on Port 1 is set to address 0 Reader 2 on Port 1 is set to address 1 Reader 1 on Port 1 is set to address 0 Reader 2 on Port 1 is set to address 1 When deploying OSDP, the reader and port address designation for each reader port will default to address 0. This means you can deploy a system without using the HID Reader Manager App provide only a single reader is being used per controller port. Note that the AX-MR62e supports a total of 4 OSDP readers but only has a single reader port. This means the HID Reader Manager App is needed to set the addresses accordingly for readers 2 through 4.   OSDP wiring is different from what most installers are accustom to. Rather than Weigand which takes 6 wires to the reader, OSDP is an RS-485 connection where 2 wires are used for data, and 2 are used for power as noted in the images below. These pictures show an HID R900 reader is connected to an AX-MR52-S3 controller for OSDP. The same wiring method is used when deploying OSDPv2 Secured Channel.  No additional wiring is needed for the reader to pick up additional signals such as Reader Tamper alarms.   Adding OSDP Readers to Access Expert To Add an OSDP Reader to your Access Expert system: Open the desired downstream controller or right-click the downstream and select Add OSDP Reader. Click “Add OSDP Reader”. Enter the Reader Display Name. Select the Address.  This field will default to 0 or 1and represents the controller port. Complete the Reader Information for the other fields similar to how a traditional Weigand Reader is configured. Click "Save & Close".   Take note of the Addressing being used on your system. The address is the Controllers Port address while OSDP Address is the Readers address and will vary when Stacking is being used. At this point, the OSDP reader is added to the Access Expert system without Secured Channel being enabled. Leaving the Assurance Profile to None and using the Default Baud Rate settings will leave the reader connected to the system without using the Secured Channel. It is recommended to set up as default first then enable Secured Channel.  OSDP readers have many of the same fields as a Weigand reader so the setup processes will be similar. Assurance Profile: This is used only by PIV class cards for FIPS deployments. Use Default: Using the default sets the Baud Rate to 9600, the address to 0, and does not use a secure channel. Use Secure Channel: To leverage the extra security that comes from OSDP readers, it is best practice to turn on a secure channel. Baud Rate: Because OSDP readers have bi-directional communication, the downstream and the reader need to be using the same rate of the communication (baud rate). Make sure this is set according to the reader's needs. It is recommended that 9600 be used for OSDPv2 and that Auto Negotiate be used for OSDPv2 Secured Channel. OSDP Address: Multiple OSDP readers can be connected to the same reader port on a controller. As an example, the MR-62E supports a total of 4 Readers on the controller but nly has one reader port.  When this is done, each reader on that port needs a unique address and is set in the HID Reader Manager App. Setting up OSDPv2 Secure Channel The reader must first be configured as an OSDP reader in Access Expert to be successfully configured for Secure Channel communications. Right Click the Reader and select View Live Monitoring. This will allow you to monitor the reader communications as you enable Secured Channel.   Check the "Use Secure Channel" option. Set baud rate to auto-negotiate. Click "Save" The reader will show as offline in the hardware tree. From the Reader setup page, Click Actions then Select Start Linking mode. The linking mode is automatic, and the process can be monitored from the Live Monitoring page. The reader will negotiate the secure communication with the controller and come online. With Secure Mode, if the Reader Tamper is in alarm, the reader will not process any card reads by design. How to - Remove Secure Channel on an OSDP reader At some point, you may need to remove an OSDP reader which has been connected to a system via Secured Channel. Uncheck Secure Channel. Click "Save". From the "Actions" drop-down menu, select "Send OSDP Command". Select the Manufacturer. Choose "Set Install Mode". Click "Execute". The LED on the reader should blink green once completed Note: The 'Send OSDP Command' modal has several OSDP Command options so make sure you are selecting the correct manufacturer and command. How to - Know if a reader is in Secure Channel There will be an event indicating the reader mode changed to card only after the start linking mode command. As the reader comes on/offline, you will notice an event/message that says “OSDP Secured Channel for, Reader Name, is Enabled but not Online or Encrypted” and “OSDP Secure Channel for, Reader Name, is Online and Encrypted.”

Issue The built in logs for troubleshooting communications from SmartStruxure ES/AS to SmartStruxure ES/AS remove the need for network captures for SmartStruxure communications. However, SmartStruxure to BACnet continues to be ideal for traditional means of network captures. The most common capture method is Wireshark when dealing with BACnet device to BACnet device communication. Product Line EcoStruxure Building Operation Environment SmartStruxure BACnet ES AS Cause The need to troubleshoot communications issues from device to device whether this is ES to AS or vice versa. The need to troubleshoot BACnet communications Resolution Network captures are beneficial in troubleshooting the following cases: Connection issues between SmartStruxure client and AS/ES. If customers complain their client cannot connect to an AS/ES, a capture run from the client PC can be very useful. However, SmartStruxure uses TCP/HTTP and the payload is not easy to decode. There are no Wireshark decoders to help out, but the good news is that there is in communication logging built in to SmartStruxure that can replace the need for network captures. (See Error logs from the Enterprise Server for ES and see Error logs from an Automation Server and Enterprise Server for AS) Communication Status problems between servers and controllers (for example BACnet controllers). The location of where the captures is taken can be very important. The best place to capture is at a switch directly connected to the controller. This may be difficult because it will require putting a “dumb” hub between the switch and the controller or finding a port mirroring switch. When you are not receiving BACnet alarms when expected. When you are not receiving COV notifications when expected When a trendlog is trending external point To evaluate the health of a network. ARP broadcast traffic can flood networks and can create connectivity problems on BACnet/IP networks. If this is the case then a customer can take action by segmenting their BMS to a VLAN. Performance problems on graphics where a large number of the point displayed are BACnet MS/TP bus performance is poor or MS/TP device is offline Using a USB RS-485 adapter can permit the capture of packets on an MS/TP bus. Wireshark can then be used to decode the packet captures. This can show token passing problems as well as traffic loads. Also check out the BACnet-Capturing MS/TP Traffic Quick-Help video on the Exchange.

Issue Double clicking a .tgmlcomponentarchive file should automatically add the Component Archive to the Editor's component libraries. Sometimes it does not work and instead shows the following windows: TAC Vista Server Please wait while Windows configures TAC Vista Server Gathering required information... TAC Vista Server The feature you are trying to use is on a network resource that is unavailable. Click OK to try again, or enter an alternate path to a folder containing the installation package 'TAC Vista Server.msi' in the box below. TAC Vista Server Error 1706.No valid source could be found for product TAC Vista Server. The Windows Installer cannot continue. Product Line TAC Vista Environment TGML Graphics Editor Cause There are five libraries that are included by default with every installation of the editor. They are: TAC Vista Symbols (EN) ISO Symbols DIN Symbols (EN) My Components Basic Controls If any of these libraries are removed by navigating to C:\Documents and Settings\All Users\Application Data\TAC Graphics Editor\Components and deleting the folder, attempts to add new libraries will fail. Resolution Navigate to the Buildings Business Extranet Go to Products > TAC Vista > Vista Software Click on the correct version of TAC Vista in the left-hand column. Choose Downloads Download the TAC Graphic Editor 1.1.X. Double click to install The directories are restored. Do not delete them.

Issue Need to change from the Small Number Format (Card Number) to the Large Number Format (Facility Code + Card Number). Requirement for Security Expert Transitions with I/NET Hardware.   Badging card on SCU1284 Reader using Security Expert, the reader event displays "Format error RD xx Port x Error Number of Bits" From Security Expert Client Events Product Line TAC INET, EcoStruxure Security Expert Environment I/NET Seven Security Expert Transitions Cause The I/NET system is limited to a maximum number of access cards, 32,000 per Tenant.  If a larger number is required, then I/NET must be configured to use large card numbers.  The Large card number format described in the Resolution MUST be completed before transitioning from I/NET to Security Expert and utilizing the I/NET SCU hardware as detailed in the Transition Guide Security Expert - INet Access Control to Security Expert - Reference Guide. Resolution To convert I/NET to use the Large Card Number support, the following steps must be performed:  Conversion of Card Numbers (small) to Large Numbers Sort the Individuals list according to the Individual Number. Look in the Individuals Editor “Options” function to set this up. Look at the tenant editor to determine the Tenant Code/ Facility code of the cards. From this, use the circled items the Tenant Code (Facility Code) and the First Individual Number as the lowest possible card number in the next step.  Verify in the door editor that the cards in this system are in a known Wiegand bit format.  In this case, we are using 26-bit. Attached are various Excel spreadsheets that can determine the Decimal number of the first card in the system (e.g., Card #970 Facility code 199) is the Decimal number 13042634, using a 26-bit Wiegand Excel spreadsheet.  This number will become the Source number in the Key/Card Translation table. These include 26-bit 32-bit ABA115 format Create a Key/Card Translation table similar to that shown below in the I/NET Seven Access Control editor.  This table will be removed after running the provided SQL Script.  The Key/Card Translation must contain: Source - Decimal number calculated in Step 3 above (13042634) Target - First Individual number shown in the Tenant (970) Count - Number of Individuals as shown in the Tenant (10000) Tenant - Tenant number this translation refers to (1) If there are multiple Tenants, then this process MUST be repeated for each Tenant Tenant Editor and Key/Card Translation Editor Shut down I/NET completely and run the attached SQL Script. Then once the script runs then, restart I/NET and look in the Individual Parameters editor, as shown below. Start I/NET and delete the Key/Card Translation table create above. Open the Individual Parameters and verify a Hex number and the decimal number matching that from the Excel spreadsheet (Step 3) is seen in the Individual Editor Card section. NOTE: There may be multiple card entries here; the Last entry shown is that entered by the SQL Script.  It will depend on whether an existing Card entry was entered for the Individuals before running the SQL Script.  To have large numbers working on a site DipSw #7 has to be turned ON for the 7910/7920 DPUs. For the SCU1284 in the door editor, at the top center of that editor, there is a check box, "Card Translation," which has to be enabled for large numbers to work in the SCUs. An SLI “SAV” should then be done because that is where the Card numbers and Door settings are stored. Then perform an SLI restore. Followed by a DPU restore to all of the door controllers. NOTE: Steps 6d. and 6e. are NOT required when performing the transition to Security Expert as this information will be performed by the SP-C.   

Issue Concurrent user IIS limit Webstation user limit Simultaneous request execution limit Concurrent connection limit of 10 Environment TAC Vista Windows Webstation IIS Cause Many questions about webstation are how many concurrent user that can connect to the webserver, while the webserver itself do not have any limits except the license used ----------------------------------------------------------------------------------- 0-008-8270-1      "Vista 5.1 Web station 1 CAL - One concurrent user license for Web station 5" 0-008-8271-1      "Vista 5.1 Web station 3 CAL - Three concurrent user licenses for Web station 5" 0-008-8272-1      "Vista 5.1 Web station 6 CAL- Six concurrent user licenses for Web station 5" 0-008-8273-1      "Vista 5.1 Web station 12 CAL- Twelve concurrent user licenses for Web station 5" 0-008-8274-1      "Vista 5.1 Web station Unlimited- License for unlimited users for Web station 5" ----------------------------------------------------------------------------------- The operating system and/or the IIS do have a limit, not on user connected but connection made to the application. While using Windows XP this error occurs when 10 connections are met "403.9's  (Access Forbidden: Too many users are connected Internet Information Services).  " This is not really handled by IIS but the TCPIP.SYS that is set to a limit of 10 connection. Windows 7 (SP2) introduced a new way to handle the connection, so when the 10 connections are met, the following connections are queued so you will not see any error messages but it can take a while for the page to load. There is a timeout parameter in IIS. Windows server edition's do not have any limits so always use a windows server for webserver. NOTE: Webstation takes 1 connection and each TGML open takes 1 connection so if you use 1 webstation and have 5 TGML open you are already using 6 connection. Resolution Below is a list for the limits on respective Operating system   Windows Server 2008 R2 (IIS v7.5)     Server:   Server OS = No Limits        Windows 7 (IIS v7.5) 2     Starter:   No IIS Home Basic:   No IIS Home Premium:   simultaneous request execution limit of 3, allows multiple sites Business:   simultaneous request execution limit of 10, allows multiple sites Enterprise:   simultaneous request execution limit of 10, allows multiple sites Ultimate:   simultaneous request execution limit of 10, allows multiple sites        Windows Server 2008 (IIS v7.0)     Server:   Server OS = No Limits        Windows Vista (IIS v7.0) 2     Starter:   No IIS Home Basic:   No IIS Home Premium:   simultaneous request execution limit of 3, allows multiple sites Business:   simultaneous request execution limit of 10, allows multiple sites Enterprise:   simultaneous request execution limit of 10, allows multiple sites Ultimate:   simultaneous request execution limit of 10, allows multiple sites        Windows 2003 (IIS v6.0)     Server:   Server OS = No Limits WHS:   Server OS = No Limits 1        Windows XP (IIS v5.1)     Home:   No IIS Professional:   concurrent connection limit of 10, allows only one site        Windows 2000 (IIS v5.0)     Professional:   concurrent connection limit of 10, allows only one site Server:   Server OS = No Limits        Windows NT 4 w/ SP3 (IIS v4.0)     Workstation:   No IIS, PWS installs as part of the NT Option Pack Server:   Server OS = No Limits, IIS installs as part of the NT Option Pack

Issue Users are getting two possible errors when trying to open WebReports page Error #1 - "The Web Site URL for Reports is not configured. Please contact the administrator" Error #2 -  "The webpage cannot be found" can also be generated. Product Line EcoStruxure Building Operation Environment Web Reports Cause These Errors can occur when the link to the Reports Server is not correct.  This is usually caused by having the Enterprise Server and Report Server on the same PC It should be noted that having both the Enterprise and Report Server's on the same PC is not recommended.   The reason the Workstation can not access the Web site / Web service URL's is because the Report Manager points to the "Localhost".  When you try to use a Workstation that is not local to the Report Server it can not locate this URL, hence the error.   This issue is not seen if when installing the Report Server on a different machine to the Enterprise Server as designed. Resolution Even though the Enterprise Server is local to the Report Server if access required by any other Workstation or WebStation you must enter the IP or PC Name of the Report Server within the Report Manager's Web site URL.  In this instance changing only the Web site URL will rectify the problem but it is recommended to change both the Web site and Web Service URL settings. This will allow any remote Workstation / Browser to find the Report Server. In workstation, Browse, to the System folder Click on System>Report Manager Set the Web site URL to http://localhost/SchneiderElectric/WebReports/Login.aspx Set the Web Service URL to http://localhost/SchneiderElectric/WebReportsService If the Enterprise Server resides on a different PC than the Reports Server, change "localhost" to the Report Server computer name or IP address After making this change WebReports should display correctly:

Issue What is the difference between the XIF and NXE files in any LON controller? Environment LNS LON Controllers NL220 LonMaker Cause There are different files related to a LON device. The XIF and NXE files have completely different purposes. Resolution The XIF is a text-based file that defines the device’s network image to a network management tool (e.g. Niagara, LonMaker, etc.). The XIF along with files termed device resource files (DRFs) are used by the management tools to work with the LON device. Device resource files provide definitions especially when the manufacturer has not used standard SNVT types. When requesting a shadow object from Tridium, the XIF file must be provided as a minimum. If the manufacturer has defined their own variable types, the associated set of device resource files must also be provided. The only other alternative would be to use a dynamic device and hope that the device’s manufacturer implemented the files within the device correctly. When a dynamic device is commissioned, Niagara will upload the XIF from the device and attempt to create an object from the file’s definitions. The NXE is an abbreviation for (Neuron Executable file). Some devices allow the user to download an NXE or new application image file that changes the operation and / or network interface of the target device. New or different application firmware can be downloaded to the Neuron. This is the way some manufacturers upgrade their devices and / or the network interface portion of the device. If the LON device can support an NXE, this would have to be provided by the device’s manufacturer.

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 What address to use to email/SMS alarms from a SmartStruxure Server, Xenta controller, or Vista to a cell phone Product Line Andover Continuum, EcoStruxure Building Operation, TAC INET, TAC Vista Environment Xenta Servers Xenta 511, 527, 701, 711, 721, 731, 913 Vista Server Automation Server Enterprise Server Email, SMS, Text Alarms Cause Vista and SmartStruxure are only capable of sending out SMTP email alarms; however, it can accomplish a "paging" or SMS functionality by sending emails to mobile providers' default email addresses. Resolution For the following services use: T-Mobile 0123456789@tmomail.net Virgin Mobile 0123456789@vmobl.com Cingular 0123456789@cingularme.com Sprint 0123456789@messaging.sprintpcs.com Verizon 0123456789@vtext.com Nextel 0123456789@messaging.nextel.com AT&T 0123456789@txt.att.net 0123456789 = the 10 digit cell phone number When setting up the "From" email address in the Server Setup, it needs to have an @xyz.com for example, at the end of the from address to allow the text message to go through. Note that these addresses could change and you should consult your service provider for details.

Issue A new Automation Server won't load in Device Administrator versions earlier than EBO 2022. A "Failed to process USB connection event for DevicePath:\\?" error is shown when adding the device.   Product Line EcoStruxure Building Operation Environment Building Operation Automation Server AS-P with Secure Boot Building Operation Automation Server AS-B Scalable Cause Secure Boot/Scalable Automation Server hardware is not supported in EBO versions prior to EBO 2022. Resolution It is not possible to install EBO versions prior to EBO 2022 in Secure Boot/Scalable Automation Server hardware. Verify the Automation Server part number to ensure it is a non-scalable/non-secure boot version. Refer to the Part Number and Hardware and Software Matrix for a list of parts numbers and their associated EBO version compatibility.

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 What is the maximum number of trend logs in a SmartX IP Controller? What is the maximum number of trend log records in a SmartX IP Controller? Product Line EcoStruxure Building Operation Environment Building Operation Multi-purpose Controller Cause SmartX IP controller free object system memory is shared between objects and data in your application. There are no specific limits on the number of objects and/or trend logs that you can create. Several factors impact memory consumption: Every object added consumes a fixed amount of memory Memory is shared between objects and data. Adjustments to description fields or trend log buffer sizes will also impact the amount of memory consumed. Different controllers have different amounts of memory to start from. RPC controllers have roughly half of the memory of an MPC. Changes to EBO 3.X will also change the memory consumption, so upgrading your system may skew the memory consumption larger than it was in previous versions. Resolution After adding trend logs to the device consult the Free object system memory entry in the device report since this will help determine how much free memory is available. Trend log buffers are pre-allocated on creation of the trend object. The other place to find how much free memory the device have is in the device property page. This value can be put in a watch window, trended, or even bound to a low-limit alarm.     If the amount of free memory drops below 50 Kbytes, that is critically low available memory. A better target is to try to preserve 50% of available memory. Based on empirical testing, estimates of memory available inside a blank controller are: MP-C: 1890 Kbytes MP-V: 1780 Kbytes RP-C: 1115 Kbytes It is important to not overload the controller because the remaining memory can also be used for COV subscriptions (the last line in the table above). If there is no memory available, then opening a graphic which creates COV subscriptions could overrun memory or operate very slowly