Building Automation Knowledge Base

Issue Common card vendors, types and formats commonly used by Continuum Product Line Andover Continuum Environment Continuum HID Indala Corporate 1000 Cause There is a wide range of card formats available. It's necessary to understand the most commonly used options for Continuum. Resolution Credential Card Format H50932 - Schneider Corporate 1000(35) Format A10202 - Andover 37-bit Wiegand Format 4041X (ASP-ANDINF) - Andover 37-bit Indala Format 40045 (ASP-CSI) - CSI Indala Format Indala Reader Format (FP3511A, FP3521A) 10723 (ASP-ANDINF-1L) - Andover 37-bit Indala Format 1009X (ASP-CSI-2L) - CSI Indala Format 10022 (ASP 26-bit Wiegand-1L) - 26-bit Indala Format HID MultiCLASS Reader (9xx Series) 4041X (ASP-ANDINF) - Andover 37-bit Indalat Format For additional  information on other HID formats, see the following article: Which HID card formats are supported by Continuum?

Issue Find New BACnet Device fails to find BACnet devices Product Line Andover Continuum Environment Continuum CyberStation Cause Third Party BACnet software may interfere with the CyberStation Bacnet Find process. NOTE: There are other reasons that bacnet devices may not be found not covered within this document. See: Cannot find new BACnet devices. Could not learn in a new 3rd Party BACnet device Bacnet 3rd party controller will not respond to Find New Bacnet Devices (Who-Is/I-Am) Resolution Stop the BACnet service in Administrative Tools\ Services. One example would be Cimetrics service Bacstac Protocol Once the BACnet devices have been found the BACnet service can be restarted, although it may be best to uninstall any non-Continuum bacnet software from a CyberStation

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 When logging into Xenta server using Internet Explorer 8 a certificate error is displayed as displayed below: When logging into the web server of a Xenta controller using Internet Explorer 8 an error message is shown stating that there is a problem with the website's security certificate. The error reads: There is a problem with this website's security certificate. The security certificate presented by this website was issued for a different website's address. Security certificate problems may indicate an attempt to fool you or intercept any data you send to the server. We recommend that you close this webpage and do not continue to this website. Click here to close this webpage. Continue to this website (not recommended). More information How to install a self signed certificate. Product Line Satchwell MicroNet, TAC INET, TAC Vista Environment Internet Explorer 8 Xenta 511, Xenta 527, Xenta 555, Xenta 701, Xenta 711, Xenta 721, Xenta 731, Xenta 913 SSL Cause The default certificate in the Xenta web server is a self-signed certificate. Since the certificate is not issued by a recognized Certificate Authority the web browser (in this case Internet Explorer 😎 cannot validate the authenticity of the certificate and suggests that the user not continue to the website each time the user tries to access it. Resolution Click "Continue to Website" to continue to the screen shown below. Click on "Certificate Error" which is found on the right side of the address bar at the top. A dialog similar to the one below will open. Click "View certificates". The certificate dialog will appear. Click "Install Certificate." The Certificate Import Wizard will open. Click Next. Allow Windows to automatically select where to store the certificate. Proceed to Finish the Certificate Import Wizard. A notification appears indicating that the certificate was imported successfully. Restart Internet Explorer for the change to take effect. Note: The certificate will need to be installed in each client computer that accesses the Xenta server but once this complete it does not need to be done again. The exception to this is if the web address of the Xenta server is changed or if Internet Explorer is uninstalled then reinstalled. The alternative is that a certificate issued by a Certificate Authority (CA) may be purchased. These certificates are pre-installed into the web browser and will automatically prevent certificate errors from occurring on all client computers that access the web server. Note that these can be quite expensive and unless the Xenta web server is being hosted on the internet they are not necessary. See "This Connection is Untrusted" certificate error when logging in to a Xenta Server using Firefox for information on installing certificates into Firefox. Update: Starting in September 2014, all major browsers will be disabling 1024-bit roots within their trusted roots stores. Any SSL certificates chained to a 1024-bit root will no longer work on any browsers that takes this action or one that relies on another's root store (the self-signed certificate is 1024-bit). This means that you will still get the security warning even if you have installed the self-signed certificate.

Issue What is the difference between a Numeric Input, Numeric Output and Numeric Public within a script program. Is using a Numeric Public a less efficient choice (as opposed to using a Numeric Input or Numeric Output) that will generate negative overhead in the AS? Product Line EcoStruxure Building Operation Environment Building Operation Automation Server (AS, AS-P or AS-B) Building Operation Workstation b3 and Infinet controllers Cause Want to determine best practices when choosing numeric types during script programming. Resolution Numeric Input is a read only numeric (from the point of view of the script program) that accepts a binding. Numeric Output is a write only numeric (from the point of view of the script program) that accepts a binding. Numeric Public is both read and write (from the point of view of the script program). Numeric Public also accepts a binding. (A Numeric Public can be bound to both a Graphic and a Value Object to allow overriding of values from a Graphic. See SBO Script Public.zip for an example) When choosing the numeric type in a script program there is no overhead cost difference between using one of these numeric types vs the others. Also check out the Script Programming - Writing the Script Program Quick-Help video on the Exchange. NOTE b3 and Infinet Controller scripts do not support "Numeric Public", but "Numeric Output", in these controller scripts, can be used in a similar way to "Numeric Public" The Bound value is read by the script as well as being written to.

Issue OPC Server with third party and alternatives Product Line Andover Continuum, TAC INET Environment System requiring third party connectivity Cause OPC Server to communicate between hardware and the iBMS (intelligent Building Management System). Resolution The OPC server is a software program that converts hardware communication protocol into the OPC protocol. The OPC client software is any program that needs to connect to the hardware. The OPC client uses the OPC server to get data from or send commands to the hardware. OPC Client Servers are used to communicate between BACnet IP interfaces and iBMS (intelligent Building Management System) programs such as TAC I/NET or Andover Continuum. There is also no Continuum OPC Client software to use for a direct OPC link. The best way to integrate from 3rd party EIB or OPC protocols is using BACnet IP on Continuum; there are third party interfaces and gateways that will convert to BACnet/IP and others that go from OPC Client/ Server to BACnet/IP. I/NET OPC For I/NET a great solution is to install a Xenta 913 controller which gives the capability to go with Modbus or BACnet/IP to third party solutions. The I/NET to Xenta 913 allows communication with Continuum BCX, StruxureWare AS-B, and other 3rd Party solutions. Continuum OPC Standard 3rd party gateways are established to communicate between the protocols such as BACnet and Modbus. Andover Continuum has an OPC Server available here. The hardware requirements are Windows NT 4.0 or Win2K. If wanting to run on XP or newer operating systems, please be aware that no testing has not been done with these OS. For more info on the OPC and XDriver, please see OPC Server Integration. Only one instance of the OPC server on a computer. Each system would need a separate PC with license key to connect to the individual systems and host controllers. The Andover Controls OPC server must be running a separate 3rd Party OPC client computer and cannot be on the same computer as CyberStation. From there it is configured to retrieve point values from a the suggested dedicated Infinity (CX) Controller. It is suggested to install a OPC gateway Infinity Controller since this controller will constantly be busy with OPC traffic. Therefore it is the separate third party vendor computer which requires the ACC OPC Server security key, not Cyberstation security key. Both USB and parallel port keys are available. If no choice is available for OS, one alternative is to check on 3rd party OPC servers like Kepware and Matrikon. Note: For Continuum, determine which one of your controllers will become the “Primary Controller” The Server requires that you designate one external Andover Controls Infinity or Continuum controller located on the same network as its “Primary Controller.” This controller must have had the network taught to it prior to selection. (This is done through the “Teach” function in the workstation.) The Server gets its information about the network through this controller. This suggested single controller is designated as the interface through which all point access is obtained. Controller Type Select the type of network where the controller is located. For a NetController, b4920, CX9702 or upgraded Infinity controllers that can be connected to a Continuum network you would select “Continuum”. For older Infinity controllers, select Infinity. Works with any IP level controller. There is no limit on the quantity, but rather it depends on how you tune.

Issue Check Windows Add/Remove programs and see if MSXML 6 SP2 is installed.  Installation of MSXML 6 Service Pack 2 (KB954459) failed because a higher version already exists on the machine. To proceed, uninstall the higher version and then run MSXML 6 Service Pack 2 (KB954459) Setup again. Product Line Andover Continuum Environment XP SP3 SQL Express 2005 XML Cause When SQL Server Setup tries to install MSXML 6.0 SP2, it detects that the version of MSXML 6.0 that is described in Knowledge Base article 954459 is already installed on the computer. Therefore, the validation process indicates that the current version of MSXML 6.0 should not be replaced. This stops the installation of both MSXML 6.0 and SQL Server 2005. Resolution See Microsoft's Support KB article for more information. MS offers a work around to this issue in their KB article as follows: Download MSMXL fix from the following Microsoft website: http://download.microsoft.com/download/E/3/F/E3F51FFB-505D-480E-9F67-0DD3A9680DEE/MSXMLFix.EXE Extract the fix, and then copy the MSXML6.MSP file and the MSXML_FIX.VBS file to the same folder. Run cscript MSXML_FIX.VBS. Once the fix is run, try installing SQL Express again. For alternative solutions see Failed to create or configure database on SQL Server! ([17] SQL Server does not exist or access denied.) and Error when installing SQL 2005 Express on a machine that had previously had MSDE installed

Issue Xenta Programmable Device is Offline in Vista, but Online in LonMaker. For LonWorks Devices refer to LonWorks Device is Offline in Vista but Online in LonMaker or NL220. Product Line TAC Vista Environment LonMaker, NL220 Vista Workstation Xenta programmable controllers Xenta 280, 281, 282, 283, 300, 301, 302, 401, 401:B Cause In an LNS system, Xenta programmable controllers have different methods of communication to the LNS server and the Vista server.  Communication with the LNS server indicates the wiring is connected, the neuron ID is set correctly, but does not guarantee communication with the Vista server.  An online condition for Vista is dependent on Xenta Group bindings and network description files in the device and the Xenta Group Master being online. Resolution Ensure that Vista Workstation is in Operating Mode vs. Engineering Mode. Refresh the Folders View - Highlight the root directory "TAC Vista" press "F5" or click the refresh icon. Ensure the device is physically Online in LonMaker even though the drawing displays as green. Check the status by right clicking on the device, select Properties. Commission Status should say "Current", and State should say "Online". Alternatively, right click on the device and select Manage / Test.  The state should read "configured online" if the device is online in LonMaker. Make sure that your Master Device in the corresponding Xenta Group in the System Plug-in is online. If the Master Device is online and displaying values, it is always necessary to download the application and parameters to the Xenta group after adding a new device. The entire Xenta Group must know there is a new device for proper communication to occur.  Download the applications and parameters to the entire group in the TAC System Plug-In. If all the above is true and there is still no data then use Verifying Xenta Group Bindings in an LNS system to verify that the Xenta Group Bindings are correct. If not, in the Vista system plug-in, click on the LNS Network tab choose Create Group Bindings and click Yes on the Resynchronize drawing to database (Fix-up Drawing). Ensure the Xenta Group name is less than 20 characters without any spaces. Note: Channel names can contain spaces (NL220) but still must stay under the 20 character limit. 

Issue Can the current revision of I/NET Seven Software CD key be used to install older revisions of I/NET Seven Software.  Site has a revision of I/NET installed older than the current release version and additional Site or Seat License is required for the site. Upgrade or revision changes. Product Line TAC INET Environment TAC I/NET Seven Cause Additional License Seats requested by site\customer. Resolution Only current revisions of I/NET seats are available for purchase. Current revision of I/NET Seven Software CD keys are backward compatible within the same major revision release (i.e. 2.40 CD keys are compatible with any 2.XX revision.) Every computer which has I/NET installed must have a I/NET CD regardless if the site is HVAC, Security or both. At a site which has a StandAlone with I/NET, it must have a Site License. If I make that a FileMaster and add one Equalized Client, a SEAT license must be purchased for that Equalized Client. If I add another Equalized Client(s) or perhaps Remote Client(s) additional SEAT licenses must be purchased for those.  The license key is registered to the site, see I/NET CD Key and software revision for more information. When looked up, it reveals how many licenses (Site or Seat) have been purchased for that site. After the initial purchase, any I/NET PC upgrade uses Part Number INETSEVEN24U If upgrading Site computer use Part Number INETSEVEN24U If upgrading File Master use Part Number INETSEVEN24U If upgrading Equalized Client computer use Part Number INETSEVEN24U If upgrading Remote Client computer use Part Number INETSEVEN24U If there is a separate database for a site, let's say they open a new building with INET install with a different db, then an additional Site license is required which would be a new license key. For the latest version information check Software and Firmware compatibility matrix for older versions of the traditional product lines   Upgrade orders can be placed using the following part number: P/N: INETSEVEN24U TAC I/NET Seven Software CD TAC I/NET Seven Getting Started - TCON298 Software License Agreements TAC I/NET Seven Software Box New software orders can be placed using the following part numbers: SEVENMAXR - HVAC & Security site license, w/ CD SEVENHVACR - HVAC only site license, w/ CD SEVENSECR - Security only site license, w/ CD SEVENADDHVAC - Add HVAC, site license only SEVENADDSEC - Add Security, site license only SEVENSEATR - HVAC & Security license for 1 workstation, w/ CD, site license required SEVENSEAT3 - HVAC & Security license for 3 workstations, w/ 3 CDs, site license required SEVENSEAT5 - HVAC & Security license for 5 workstations, w/ 5 CDs, site license required SEVENMANUAL - Manual set, 3 volumes. No CD   Example: The site is currently at I/NET Seven Software Revision 2.14 and requires the purchase of additional seat licenses. The newly purchased seat licenses are the current I/NET Seven Software Revision 2.47. Two options available: 1) Use the newly purchased I/NET Seven Software revision 2.47 seat licenses to install the I/NET Seven Software revision 2.14. Upgrade the sites original licenses from I/NET Seven Software revision 2.14 to 2.47 Older revision I/NET Seven Software can be obtained from either the original CD Media or can be downloaded from EcoBuilding Download Center. Example 2: A site has an existing Host File Master, and Five(5) SEAT licenses(Equalized Client or Remote Client). To upgrade, they would purchase six(6) INETSEVEN24U part numbers which is for each of those workstations. To add an additional I/NET workstation, they would purchase a SEVENSEAT, which is the additional SEAT license.  

Issue Replacement I/NET Controller NICAD Battery info., I/Net Batteries Product Line TAC INET Environment All I/NET controllers Cause Controller battery has failed, because the battery on the controller is over 5 years old   Resolution The 3 pin version Battery is used for the NPR2000 and the DPU48K (MIP Board) -- part number 3/V80H-SLF (Note this battery has to be order from an outside Vendor and not Schneider Electric). Click here to view a PDF on this part. The 7910, 7920, 7930 7780 & 7940 use the 2 pin version -- part number 3/V80H-LPC (Note this battery has to be ordered from an outside Vendor and not Schneider Electric). Click here to view a PDF on this part. The battery used on the 7700, 7716, 7718, 7728, 7720, 7928, 7793, 7798B, & 7798C (and like controllers) is the Dallas/INET part number 801288-07. This also can be ordered from the Rockford order entry using 01-2100-545 (Old CSI P/N 801288-07). This battery also has an outside Vendor source from Power-Sonic P/N - PCBM-3.6 Click here to view a PDF on this part. For battery testing process see How to test the NiCAD Battery on a Controller

Issue Power cycling the SE8000 room controller will cause the settings to revert to default. This requires reconfiguring each of the parameters once again. Product Line EcoStruxure Building Expert Environment Multi Purpose Manager Automation Server SE8xxx Room controller SE8000 Series SER8300, SE8300, SE8350 Ex. Viconics branding VT8000 Series Cause This has to do with BACnet priority; if the configuration was not written with the appropriate priority, the Room controller will overwrite the parameters upon a power cycle and set them to default. Resolution There are a few ways to prevent the SE8000 from reverting to its default settings after a power cycle: Configuring each Room Controller locally by navigating to the configuration menu. (Centralized and Standalone system) Using a LUA4RC script (Centralized and Standalone system) Writing to points with a specific priority via the BACnet front-end (Centralized system) NOTE: Since Zigbee does not have any command prioritization mechanisms, setting the parameters from an MPM via Zigbee will not be retained after a power cycle and is strongly not recommended. All three methods can be used to configure a Room Controller prior to or after its installation. Configuration prior to installation can save a lot of time for the technician on site.     1 - Configuration on SE8000 (Local) Changing the parameters on the SE8000 locally will permanently save the settings and will also allow the user to change the parameters settings locally (e.g. Occupied cooling setpoint). This however can be time consuming.   2 - Configuration via LUA4RC This method is especially useful in standalone applications with no BACnet front end. If there are many parameters that need to be adjusted, it will be quicker to upload the script to each of the Room controllers rather than navigate to each parameter manually. By default, when you assign a value to a BACnet point, the write priority will be priority 16 Example: ME.MV6 = 2 --Set "Network Units" to Imperial (blocked by using priority 16, not user-adjustable) To write to another priority, an array is used Example: ME.MV4_PV[3] = 1            --Language will be blocked by user, room controller and bacnet front-end. Will be saved to memory and will stay after a power cycle NOTE: To release this priority, you can set it to nil (example: ME.AV25_PV[8] = nil). To access the relinquish default, priority 17 can be used Example: ME.MV10_PV[17] = 1    --Set "Occupancy Command" to "Local Occupancy"; here it is mandatory to have (_PV[17]) because thermostat must be able to toggle between "Occupied" and "Unoccupied" temperature Use the script below as a template for your LUA4RC script (remove comments to use less memory) if not init then ME.MV6 = 2           --"Network Units" ME.MV10_PV[17] = 1  --"Occupancy Command"  ME.AV46_PV[17] = 3   --"Standby Temperature Differential" ME.MV5 = 2           -- "Time Format" ME.AV67_PV[17] = 4   --Standby Time ME.AV68_PV[17] = 12  --Unoccupied Time ME.MV46_PV[17] = 3   --UI 16 Configuration ME.MV4_PV[3] = 1     --Language --Add all required configuration parameters init = true end   3 - Configuration Via BACnet: SE8000 parameters can be configured via the BACnet front end by using the following priorities: Priority 2 or 3: Using these priorities will permanently save the setting on the SE8000 and will not allow the user to change the settings locally. Relinquish default: This will allow the user to change the value locally on the SE8000. This is typically used with setpoints NOTE: using Priority 16 will not allow the user to change the value locally on the SE8000, however, the SE8000 will revert to value to default upon a power cycle. Another effective method is to push the configuration to multiple SE8000s across the network using a lua script. See Bulk Lua4RC upload via BACnet (Mass upload).

Issue What is the process to replace a CX9400 with a CX9680 NC2? Product Line Andover Continuum Environment Upgrading a CX9200, CX9400 Eclipse, CX9900, CX9940 to a NCII Netcontroller. CMX9924. Model Number, Type change. Cause Where can I get the process to upgrade my obsolete CX controller. Resolution Cyberstation V1.74 SP2 or above is required to support the upgrading process of a CX9200, CX9900 and CX9940 up to a Netcontroller 2. The upgrade process for this is detailed in Appendix B or the NetController II Operating and Technical Reference Guide. For the CX9400 Eclipse controller they require a minimum of V1.91 to support the upgrade. For the older versions of Cyberstation that do not support direct upgrading of a model number, you will need to bring the Netcontroller II on line as a new controller, then in offline editing copy /paste (or Drag /Drop) all objects over to the Netcontroller II. Then go online and fully reload the Netcontroller II and any connected Infinet controllers. The old controller can then be deleted from the system. The objects could also be copied over using edited ASCII dump files if you prefer that method, but either way you may still have to re-animate your Pinpoint graphics unless you upgrade to a version that supports the Netcontroller II replacement. NOTE ACC-LON RS-485 and ACC-LON FTT-10A protocol options A CX9900 may be labeled CPU-8M and a CX9940 labeled CPU-4M. Later CX99 models may have FT added, eg. CPU-8M-FT When replacing a CX9900 or CX9940 it is vital to know if it requires an RS485 or FTT10 IOU module port (if this port is being used) as this CANNOT be modified on site. See article titled No response from I/O module when learning in an IOU This process cannot be used to upgrade the CMX9924 controllers.  The available range of Netcontroller II controllers available has recently been reduced, see PA-00535 "Andover Continuum Offer Optimization"

Issue Making a cable / adapter by using the cable guide as a reference can be confusing. Product Line TAC Vista Environment Vista Menta Download Wizard Cause Without knowing to use a Ribbon (Rollover) Cable, or the correct pins of RJ45 and DB9, it can be difficult to build this cable and adaptor. Resolution Note: Pay particular attention to the pins numbers, this view is the inside of the adapter! This is the pinout to be used in conjunction with a "ribbon" type cable. A Ribbon (Rollover) Cable has inverse ends. For example, Pin 1 of one RJ45 will be Pin 8 at the other end, Pin 2 will be 7, Pin 3 will be 6 and etc..                                    Here is a Diagram which highlights the path of TxD RxD and GND from the PC to the Xenta Controller. Use and Ohm meter to check the continuity of connections. If you are having communication problems, please see Verifying Serial Port Communications with loopback test   for further troubleshooting tips.                Alternatively, a cut ethernet cable can be wired to a DB9. DO NOT use an Ethernet Cable with the above adapter. 1. Use a standard 586B RJ45 ethernet cable pictured below.                2. Connect RJ45 jack to a DB9F according to the following diagram.

Issue Site experiencing comm issues on the Infinet or MSTP bus. Controller error logs show many 1465 (Cyclical Redundancy Check) errors. Product Line Andover Continuum Environment Infinet MSTP b3 i2 Controller error log Cause CRC errors are check sum errors. Before a packet is sent, the sending controller calculates a checksum based on the packets contents. This checksum is then appended to the packet. When the packet is delivered, the receiving controller calculates it's own checksum based on the packets contents. If the check sums do not equal, this indicates that somewhere in the delivery process the packet has been altered, usually due to bad cable or connections, controller grounding, or a bad controller transceiver. For additional information on troubleshooting the infinet or mstp bus, see Infinet and MSTP bus troubleshooting. Resolution CRC errors usually indicate poor signal integrity on the physical bus. Infiltration of "noise" on the comm cable due to the presence of high voltage conductors, radio transmissions, etc. In some cases a failed transceiver may be involved but this is generally not the case. Poor controller grounding can also contribute to this issue. Generally CRC errors call for using a scope to assess the signal integrity on a bus.

Issue The FlexNet console shows the following error Vendor daemon down: taclic No such feature or vendor does not exist: taclic Product Line EcoStruxure Building Operation Environment License Server FlexNet TACLIC Cause The taclic vendor daemon which serves the SmartStruxure licenses is down. This indicates that the vendor daemon either does not exist, or that another application using the same vendor daemon executable is present on the PC. You can run one or more FlexNet license servers with different vendor daemons, but a given vendor daemon can only be run once at a time on the PC. The SmartStruxure Building Operation vendor daemon is called taclic.exe. This can be seen as a process in the Windows Task Manager. Resolution 1. Make the SmartStruxure license server is properly installed 2. Follow SmartStruxure license and TAC Vista license on the same PC if both TAC Vista and SmartStruxure Building Operation is installed on the same PC.

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 Interfacing M-Bus meters to Modbus. Product Line Andover Continuum, EcoStruxure Building Operation, Field Devices, Satchwell Sigma Environment Sigma IC3-Modbus Mbus Modbus Kampstrup Heat Meter Multical 601 Cause Multical 601 M-Bus meters are required to be interfaced with the BMS. Resolution A M-Bus/Modbus converter (RS-485, RS-232 or TCP) and configuration software are required. The converter  and software are available from SyxthSense or similar suppliers. Using the converter and software setup the M-Bus/Modbus system without the BMS system connected. The M-Bus/Modbus converter will automatically assign the M-Bus registers as Modbus registers. From the software note the tables and registers used. Create the Modbus registers as required for the BMS system used. For Sigma - Create the gateway.txt, connect and configure the IC3-Modbus. A sample of the gateway.txt can be downloaded here: MultiCal Modbus Gateway.zip. For further M-Bus information see M-Bus Protocol Information. 

Issue When using the Modbus RTU X Driver on RS-485 what cable type should be used and what maximum distance would it give? Product Line Andover Continuum, EcoStruxure Building Operation Environment Modbus RS-485 XDriver. bCX1, NC2 AS Cause Recommended cable type required. Resolution The Modbus RTU is a standard RS-485 network and you can use the same networking rules as per the Infinet network. As long as the baud rates are set the same you can even use an Infilink 200 or a B Link to act as a repeater. Unless the Third Party device manufacturer specifies different requirements the Belden 9182 or a similar cable that matches the Infinet specification would be suitable, again as per Infinet rules this would typically allow a maximum end to end distance of 1200 Meters. Also check out the SmartStruxure-RS485-Network Installation Quick-Help video on the Exchange.

Issue What is the latest specification For a Continuum PC Product Line Andover Continuum Environment Cyberstation SQL Server Cause Computer specification required. Resolution The PC specifications for a version does not change from the time of release, so there is no "Latest Specification" as such. For all versions the hardware requirements are defined in the installation guide (Installation.PDF) on the software CD, or in the downloaded zip file from The Exchange Download Center for the version to be used. This document will contain the minimum and recommended specification required for that Cyberstation version on a typical site, if any other software is to be installed on the computer or the computer is to be heavily loaded; the requirements should be increased accordingly. The same RAM and Processor requirements will also apply to the SQL Server on a typical LAN system. You also need to check the Software and Firmware compatibility matrix for older versions of the traditional product lines for details on the compatible operating system requirements for the version to be used. For a V2.01 system the recommended hardware for servers and workstations are: Intel 8 Cores, 2 GHz or better 8Gb RAM 30Gb Available HDD space (NTFS Partition) CD ROM Drive Video resolution: 1024 x 768 pixels Parallel or USB port For larger systems and where there will be a lot of Extended logging or Alarming, the Hard drive, RAM size and processor speed should be increased.  

Issue How do I change the Baud Rate of a field bus (either Infinet or Bacnet MSTP) if there is either an Infilink or B-link on the network? Product Line Andover Continuum, EcoStruxure Building Operation Environment Infinet BACnet Cause The Infilink and B-link must have their baud rate set manually. Resolution All Infinet or Bacnet B3 controllers autobaud on initial startup or when the fieldbus commport is changed from the parent controller's commport editor. The Infilink and B-link must have their baud rate set manually. The proper procedure to change the fieldbus baud rate is to first go to the commport editor and change the fieldbus baud rate. At this point a message is sent to all field bus controllers to change their baud rate. They will all change immediately, however the Infilink and B-link have not yet changed, so the bus will now be in a confused state and there will be offline issues. The next step is to go to the Infilink or B-link repeater and manually change the baud rate to the new setting. At this point the network should work normally, however if the procedure is not followed there may be network issues where you have some controllers that are running at different baud rates causing the network to be totally shut down. If this is the case the way to resolve the issue is to make sure the Infilink or B-link repeater is set to the desired baud rate and power down or reset those controllers on the network so that they will all synch up to the correct Baud Rate upon power up. ** Changing many controllers A method that may help when needing to change the baud rate of many controllers is to bypass the b-link Connect segment 1 of the b-link directly to the BCX comm port and change the baud rate Reconnect the B-link and verify the controllers are now online, repeat the baud change if necessary. Repeat this process for each segment You may still have some isolated controllers that need to be powered off/on. Related: BACnet bCX MSTP network loses communication when a b-Link is added or removed