Building Automation Knowledge Base

Issue The EWS interface in the SBO system tree shows as online but when browsing to the hardware folder all that shows up is the class folders, no objects are loaded.   When reviewing the settings in Security Expert EWS Manager.exe a prompt showing "Please set the password" is shown before loading the main configuration window.   You can then see that the Operator Password field is blank and that subsequent attempts to set this and save seem to work but when closing and re-opening the Configuration Manager that the password is not saved. Product Line EcoStruxure Building Operation, Security Expert Environment Security Expert Cause The current language for non-Unicode programs is set to a value other than English. In one specific case this was set to Chinese (Simplified,PRC). Resolution In the Region and Language settings for Windows go to the Administrative tab and select Change system locale... Set this to English, save and reboot the machine. The Operator Password should now be able to be set in the EWS Configuration Manager and EWS connection established.

Issue Unable to configure universal input from the thermostat Product Line EcoStruxure Building Expert Environment SE8000 Cause Universal inputs aren’t configurable at the thermostat Resolution There are two ways to configure inputs on SE8000; More often is via a BACnet front end and secondly is via a Lua script. The input shall be configured to Priority 3. SE8000 INPUTS: •       UI16 fixed as binary input •       UI17 fixed as binary input •       UI19 configurable as temperature sensor, binary input or 0 -10 VDC input •       UI20 configurable as temperature sensor •       UI22 configurable as temperature sensor •       UI23 configurable as temperature sensor •       UI24 configurable as temperature sensor, binary input or 0 -10 VDC input   For example UI19 configuration: UI19 LUA AnalogValue:202 ; this point is to write a Lua via Bacnet for UI19. LUA:  if not init then ME.MV6 = 2 -- set network units to imperial ME.MV145 = 2 -- room temp local ME.AV25_Desc = "UI19 TEMP" -- UI19 Present Value ME.AV26_Desc = "UI20 TEMP" -- UI20 Present Value ME.MV140 = 1 -- UI19 thermistor ME.MV141 = 1 -- UI20 thermistor init = true end ME.AV25 = ME.AV104 ME.AV26 = ME.AV105 ME.AV100_PV[16] = (ME.AV104 + ME.AV105) / 2 -- average UI20 remote sensor and UI19 remote sensor

Issue Where to go to download the Access Expert Device Administrator application. Product Line Access Expert Environment Server 2012 SQL 2012 and above Premise Install V2 Hosted V2 Applet V3 Cause There is no documentation on where to go to download the Device Administrator and how to program the SSC to communicate with the selected application. Resolution The following steps describe where to go and download the software and how to use it to program an SSC: Go to the EcoBuilding Exchange In the search field type Device Administrator Select the Access Expert Device Administrator and download to any location Browse to location and double click execute to run and install the program Accept Agreement and click next to continue installation Click Next to start installing the software Select the location where the file will be installed Successfully loaded software To complete installation, click on Finish Connect the device to a network switch that is open to the internet and launch the application by opening Access Expert device Administrator from the Schneider Electric group in All Programs Launch the application  Right click on the usb line or click on the green arrow to the top left to upgrade the software Once upgraded successfully, Right click again on the line and select properties then select the Ethernet 1 ConfigurationTab Select applicable choice whether it is DHCP or Static addressing being used and click on OK. Once the device comes back Online, select the DIP Switches Tab and check the box for Default User Using the IP address given from step number 13, open up IE and browse to that address Once opened, configure the SSC per Setting up an SSC (System Security Controller), EP1501 and EP1502 Mercury Controllers.

Issue Security Expert database size increasing rapidly and getting large. SecurityExpert Database size From the screen capture below, it can be seen that the Security Expert transaction log file SecurityExpert.ldf has increased to a large size. SecurityExpert database log file Product Line EcoStruxure Security Expert Environment Security Expert Microsoft SQL Server Cause The Recovery model of the Security Expert database is set to FULL and the database has not been maintained. When using the Full recovery model, regular backups of the transaction log should be performed to prevent the transaction log file size from growing out of proportion to the database size.   New user databases are created with the same recovery model as the model database. The default recovery model for the model database depends on the edition of SQL Server you have installed. Editions targeted at test and development environments (SQL Server Express) set the recovery model of the model database to SIMPLE. Other editions set the recovery model of the model database to FULL. Resolution For Security Expert, it is recommended that the Recovery model be set to the default of SIMPLE.   You can reduce the size of the logs and also prevent them from getting too large again by changing the recovery model of the database from FULL to SIMPLE. The databases are then shrunk to free up drive space.   Refer to the following steps: Take a backup of both the SecurityExpert and SecurityExpertEvents databases and store them in a safe location Change the Recovery Model of the SecurityExpert database from Full to Simple in SQL Server Management Studio. To do this, right click on the SecurityExpert database and go to its properties. Select 'Options'. Change the Recovery Model setting to Simple. Recovery Model Simple Right click on the SecurityExpert database and select Tasks > Shrink > Files Shrink In the Shrink File - Security Expert window, change the File type to Log. Shrink File Type Log Click OK Repeat steps 2-5 for the SecurityExpertEvents database   It is recommended that regular scheduled backups be configured when using the SIMPLE recovery model. In SIMPLE recovery mode, changes since the most recent backup are unprotected.

Issue Modbus device in hand does not have a pre-configured widget in the device list of Building Expert. A script is required to communicate with the device Product Line EcoStruxure Building Expert Environment SmartStruxure Lite Multi-Purpose Manager Any modbus device Cause Pre-configured widget not available in the device list of Building Expert Resolution The MPM can only be a Modbus Master; meaning it can request information from other slave modbus devices, or write to them. Terminals A and B on the MPM correspond to modbus terminals (Serial +) and (Serial -) respectively. When using a script to communicate with modbus devices, the "Enable" box in the ModBus configuration object (MOD1) must be disabled to allow the MPM to communicate with the devices using a script. The modbus port should then be closed (in case it was left open) and re-opened using the following functions ******************************************************** @@@ Lua.modbus.close       (Description and example here) ******************************************************** @@@ Lua.modbus.open        (Description and example here) ********************************************************     The following are the standard modbus functions and their corresponding Lua functions used in the MPM Modbus Function Code Lua Function in MPM Function Code 01 modbus.coil_read Function Code 02 modbus.di_read Function Code 03 modbus.hr_read (16-bit) Function Code 04 modbus.in_read Function Code 05 N/A Function Code 15 modbus.coil_write Function Code 06 modbus.hr_write   The following are the 8 different modbus functions that can be used to read/write to registers from/to modbus devices ******************************************************** @@@ Lua.modbus.coil_read     (Description and example here) This function is equivalent to : [Function Code 01 (01 HEX)] ******************************************************** @@@ Lua.modbus.coil_write    (Description and example here) This function is equivalent to : [Function Code 15 (0F HEX)] ******************************************************** @@@ Lua.modbus.di_read      (Description and example here)   This function is equivalent to : [Function Code 02 (02 HEX)] ******************************************************** @@@ Lua.modbus.hr_read       (Description and example here) This function is equivalent to : [Function Code 03 (03 HEX)] ******************************************************** @@@ Lua.modbus.hr_write      (Description and example here) This function is equivalent to : [Function Code 06 (06 HEX)] ******************************************************** @@@ Lua.modbus.in_read      (Description and example here) This function is equivalent to : [Function Code 04 (04 HEX)] ******************************************************** @@@ Lua.modbus.fp_read     (Description and example here) ******************************************************** @@@ Lua.modbus.fp_write    (Description and example here) ******************************************************** To read a floating-point (32-bit) value, the fp_read() function can be used. (Download script) To read an unsigned long (32-bit) value the hr_read() function can be used, however, some data manipulation is required (Download script) To read a floating-point (64-bit) value, the hr_read() function can be used. (Download script)   Modbus errors can be found here

Issue After downloading a hotfix for Device Administrator, it is not possible to install a new database onto an Automation Server **. **Note, for this article "Automation Server" will be used as a general term. This applies to all Smart-X controllers (Automation Server, AS-P, and AS-B). Product Line EcoStruxure Building Operation Environment AS, AS-P, AS-B  SBO Device Administrator Cause When the Device Administrator hotfix is downloaded to the machine, it replaces the "Full-Installer" version that was already installed. The new hotfix version does not include the necessary firmware to push down onto the Automation Server. This can be misleading because Device Administrator still indicates the base firmware version is present, as shown below. Resolution A full installer (such as 1.8.1.87 or 1.9.1.95) of Device Administrator must first be installed on the machine and used to install the base firmware onto the Automation Server. Then the hotfix version may be downloaded to the PC and used to apply the hotfix to the Automation Server.  **Note - In some instances a hotfix can be a full installer, which will allow for the download of a new database. Such hotfixes will be released either as a full installer or as a maintenance build. The release notes for the particular hotfixes will indicate their full installer build. 

Warning Potential for Data Loss: The steps detailed in the resolution of this article may result in a loss of critical data if not performed properly. Before beginning these steps, make sure all important data is backed up in the event of data loss. If you are unsure or unfamiliar with any complex steps detailed in this article, please contact Product Support Services for assistance. Issue Software installation problems with Windows 7 OS and above Configuration problems also known as UAC / User Account Control These problems occur when you receive an error message stating that you do not have the correct administrative rights to continue. Product Line Andover Continuum, EcoStruxure Building Expert, EcoStruxure Building Operation, Satchwell MicroNet, Satchwell Sigma, TAC INET, TAC Vista Environment Windows 7 Windows 8 8.1 Windows 10 Server 2012 Cause Windows 7 and above user administrator privilege settings (UAC) Resolution The solution to this issue is to turn off the user admin settings before the software is installed by following these instructions: Go to Start > Control Panel. Set the view to "small icons" to show all Control Panel icons Click on "User Accounts." Make sure that the account used for installing the software is a full admin user. On this page, click on "Change User Account Control settings", a slider bar that starts with "Never notify" up to "Always notify" by default will be set to "Notify me only when programs try to make changes to my computer" Set it to "Never notify." This will disable all the admin blocks that pop up in installing and configuring software Once set, restart the PC and then continue with your software installation and configuration Once all is installed and working, the feature may be turned back on if required. Additional requirements for Windows server 2012 and Windows 10. Please note: this process may open the "Windows 10 Firewall up" For Windows Server 2012 and Windows 10, additional steps are required to disable User Account Control. Although the slider bar can be set to “Never Notify”, the User Account Control does not disable completely. The User Account Control can be disabled for any user by setting the system registry value “EnableLUA” to zero in the system registry under the registry key “HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\policies\system”. A Windows registration file has been included in the Continuum 2.01 release in order to expedite these additional steps. Or the attached file EnableLUA.zip can be used, unzip and execute.  Supplement: Using the right click "run as administrator" instead of this is not the same. The right click will only run that .exe as an administrator and not the whole install/configuration package, i.e. SQL2005 manager will fail to run if you do not do as instructed above. You will always get an error stating that you do not have permission to run this program.  Alternate Windows 10 Admin. to User privilege for I/Net Seven:   Go to this path: C:\Program Files (x86)\ Inet Seven 1) Rename and move to a new folder these files.       A) INetIoSrv.exe.manifest       B) INetW.exe.manifest       C) If there is a file equalization client, then there is INetEqzMerge.exe.manifest to do this change on as well.  2) Change the DbCreate by doing this:       Another problem for non-admin users will be logging into and using DbCreate. A work-around for that would be to create a new login into the SQL database that could be shared among all DbCreate users and would provide the necessary rights.       Alternate Windows 7 Admin to User privilege for I/Net Seven:  See the attached Document and Manifest Files  

Issue The Project Configuration Tool is installed as a Server. A project can be created but when it should be saved, an error says, "Failed to open project," and "Failed to start VM." Product Line EcoStruxure Building Operation Environment PCT version 1.1.1 Cause When PCT is installed as a server PCT, and a project is opened, the computer running PCT must have a connection to the DHCP server in the network. Resolution Make sure that the computer running PCT has a good connection to the DHCP server in the network.

Issue Controllers may leave their network and join another if a nearby network has an identical "Extended network ID", "Channel" or "PAN ID" Product Line EcoStruxure Building Expert Environment SmartStruxure Lite Multi-Purpose Manager SE8xxx Room controller SE8000 Series SER8300, SE8300, SE8350 Ex. Viconics branding VT8000 Series Cause Conflict in zigbee networks (Same "Channel", same "PAN ID" or Same "Extended Network ID") Resolution Before deployment, and in order to ensure having a reliable ZigBee network, one has to be aware of the best practices and the limitations of RF signals. Here are some key points to be considered Network Conflicts: Always change your Extended Network ID from the factory default. The best thing is to use a naming convention that makes sense. One suggestion would be to use "SSLLITxx," where "xx" is replaced by the floor the network is on. For example, floor 5 would be "SSLLIT05." If you have multiple networks on the same floor, adding a letter code helps denote them. For example, if there were 2 networks on floor 5, "SSLLI05A" and "SSLLI05B" can be used. Note: In Firmware 2.20.1, the ZigBee Extended Network ID parameter is set by default to a unique string based on the serial number of the MPM. This will eliminate the possibility of having duplicate Extended ID's in a new deployment. For existing installations, the Extended Network ID will remain unchanged if upgrading from a previous version.   Alternating Channels: Alternating channels between network will minimize interference ensure stability. For example, for a 5-story building, alternate between channels 20, 25, 20, 25, 20. Tx Power Upgrade: The default value for "Tx Power" is 5dBm which was designed in order to meet various regulations in certain countries (Europe). However, the "Tx Power" can be increased to 18dBm in other regions of the world (North America) to boost the transmission power of the MPM.   Interference: There are different types of interference when a wireless signal travels through a given space: Physical objects: The number of walls the wireless signal can pass through is determined by the density of the materials used in a building's construction. Concrete and steel walls are difficult for a signal to pass through. These structures will weaken or at times completely prevent wireless signals. Also, the presence of individuals or water will diminish the signal due to the water's ability to absorb the signal. 2.4Ghz Frequency Interference: Cordless Phone - operates on the same frequency as the ZigBee and can cause a significant decrease in performance. Microwave Oven - operates by emitting a very high power signal in the 2.4GHz band. Often emits a very "dirty" signal across the entire 2.4GHz band. Wireless Routers - Wireless Wi-Fi Networks that share the same channel will have a negative effect on ZigBee network performance. Distance: To ensure reliable communications, a suitable distance between two devices has to be calculated before installation. The distance depends on three factors; transmitter power, sensitivity of the receiver and the propagation path loss. The latter is dependent on the number of walls/physical objects obstructing the signal. Locations: The physical location where a router or coordinator is placed also has an impact on the signal. Place the devices in higher ground to reduce the impact of physical objects. Route Redundancy: It is critical that the signal has multiple routes to hop from one device to the other, from one edge of the network to the opposite edge. (See example in images below)

Issue Need the UL Listings for Xenta Product Line Product Line TAC IA Series, TAC INET, TAC Vista Environment Xenta Cause UL Listings for Xenta Product Line Resolution Go to Exchange Online and log in Search for "TAC Vista UL Listings" (Example, Click Here) You can find more information in Xenta Hardware UL 864 Listing.

Issue In some projects there is demand for importing a large number of individuals from an existing spreadsheet for individual information at one time. Product Line TAC INET Environment I/NET Seven Revision 2.xx and higher Microsoft SQL Server Management Studio Express Cause In some cases the customers have a spreadsheet or database of employees and/or users which they want to quickly import into their I/NET Seven Access control database. Resolution The whole process is to import the data from the excel file to the IDWorksView table of SQL database of I/NET. The steps below needs to be followed: Prepare the Microsoft SQL Server Management Studio Express. Click here to down this tool for version 2005 free of charge. If for version 2008, click here to download. Then install this tool. Download the individual spreadsheet Excel template and SQL script here. Save to the C:\. Ensure that the Tenant, Group have been added in I/NET already. Also ensure that all the card numbers in the spreadsheet don't conflict the ones already in I/NET. Enter the individual information into this template. If there are photos for individuals, the folder of the photos also need to be entered. Open the Microsoft SQL Server Management Studio Express and connect to the database. Find the InetDb database, and open the SQL script just downloaded from the File menu. Click Execute to run the script. Then if without any problems, the successful result will be shown in the output message window. The next step is to get the imported data downloaded to the controllers. For each SLI perform a station SAV and station restore – it may take some time for all this information to be downloaded to the DPUs and may fail in some instances.  You may also notice the system slow up for some time (hours) until all of this information has been successfully downloaded to the controllers.  It may also be necessary to force the data into the DPU by performing staggered DPU Restores on specific doors that are experiencing incorrect functionality.  There is also a method that download the imported data without any operation in I/NET software by a function called Automatic DPU Restore. Refer to Automatic DPU Restore and Individuals added via Datacard ID Works are not getting access to doors for detailed information about how to set Automatic DPU Restore in I/NET. This is the method using SQL Server Management Studio Express. The Microsoft Access can also be used to do the importing work. Refer to How to import a large number of Individuals into an I/NET Access Control database for detailed information.

Warning Potential for Data Loss: The steps detailed in the resolution of this article may result in a loss of critical data if not performed properly. Before beginning these steps, make sure all important data is backed up in the event of data loss. If you are unsure or unfamiliar with any complex steps detailed in this article, please contact Product Support Services for assistance. Issue Want to be able to import a list of individuals quickly without having to retype all the details from a spreadsheet or text file again into I/NET Product Line TAC INET Environment I/NET Seven Revision 2.xx and higher Microsoft Access 2003 Microsoft Access 2007 Cause Customers usually have a spreadsheet or database of employees and / or users which they want to quickly import into their I/NET Seven Access control database.  The process below describes how to do this along with its limitations. Resolution Process to import Individuals via the IDWorksView table using Microsoft Access 2003 / 2007 The import process will NOT update any existing data; it will only add new entries and leave existing entries as they were.  So this is typically a process used for a new installation.  If you are attempting to import into an existing Access control database with individuals then it is strongly recommended to backup your I/NET SQL database. It is also strongly recommended you test this in an ‘offline’ state, that is, it is not connected to any physical controllers until you are comfortable that the process provides the desired results. The same limitations that apply with ID Works (Refer to TCON 301 Chapter 5) apply to this import process. TAC I/NET Seven (not just I/O Server) must be running on the server specified in TAC I/NET Seven’s ODBC data source in order for records created or modified from ID Works to be downloaded to affected DPUs. ID Works does not allow you to add or modify multiple cards for a single individual. ID Works does not allow you to remove a card from an individual without deleting the individual record. You cannot disable an individual’s card without disabling the individual. You cannot create a new group or a new tenant.  All Tenant and Group information must already exist in I/NET You cannot make an individual’s record be DPU resident. You cannot assign a decimal card number to an individual. You cannot set an individual’s APB scheme (that is, hard, soft, or graced anti-pass back). You cannot assign a PIN to an individual. The steps to import are as follows: Download ZIP file containing necessary files here. If you are using Microsoft Access 2007 use the following files Format customer data into the Excel template (dbo_IdWorksView.xlt in the ZIP file) or provide this to the customer to complete the Employee details.  Pay attention to required data shown in the comments for each title cell. Open db1.mdb file in the ZIP file using Microsoft Access 2003 /  idworks.accdb if using Microsoft Access 2007. Double click (open) the table dbo_IdWorksView to establish the connection to I/NET on the respective machine.  You may be prompted for login details – you must use the ‘sa’ login and password installed on the PC. If successful you should see any individuals that already exist in the database (unless blank).  Close the table. If you are using Microsoft Access 2007 Click Here to view the changes for steps 6 though to 8. Right–click in any of the white space and select Import (or go to File>Get External Data>Import) Browse to the location of the Excel Spreadsheet, saved in step 2, containing the data to be imported.  Be sure to change the File Type to *.xls otherwise you will not find the file.  Select the file. Import wizard should appear, now select the following options within the import wizard: Select the Check box “First row contains column headings..” Select Next Select “In an Existing Table” and select the table from the drop down list – there should only be one there. dbo_IdWorksView. Select Next. Select Finish. Be patient – the process can take a few minutes based on the number of entries that you are trying to import.  Once imported you should receive a message indicating that the import was completed.  Select OK. If you have images referenced in your import file, be sure that the Images are in place before modifying ANY individual in I/NET.  Otherwise the image path will be deleted.  The next step is to get the imported data downloaded to the controllers. For each SLI perform a station SAV and station restore – it may take some time for all this information to be downloaded to the DPUs and may fail in some instances.  You may also notice the system slow up for some time (hours) until all of this information has been successfully downloaded to the controllers.  It may also be necessary to force the data into the DPU by performing staggered DPU Restores on specific doors that are experiencing incorrect functionality. There is also a way to realize this function using Microsoft SQL Server Management Studio Express instead of Microsoft Access. See How to Import a Large Number of Individuals from Excel to I/NET SQL Database at One Time for more information. 

Issue When viewing graphics in Enterprise Server values are flashing in and out. Product Line TAC IA Series Environment R2 Niagara Cause When viewing the UNC's workspace editor, the values are ok, but in the Enterprise Server links are active and inactive. Resolution The Enterprise Server stations have to be configured with different ports to run simultaneously. Please consult Two stations running concurrently on a Niagara R2 computer or stop second station from running.

Issue Using a card reader to Unlock and Secure a Building Product Line TAC INET Environment I/NET Seven 7798 Cause Site requests the ability to have a user card in at the beginning of the day locking the door and card out at the end of the day unlocking the building Resolution Create and AIC triggered from the card reader to start an event sequence as outlined in Using AIC to trigger an event sequence The AIC should trigger an event sequence (sequence1) Line 1 of sequence1 should be skip if 0, looking to see if the door is lock and skipping to sequence2 Line 2 of sequence1 should be skip if non-0, looking to see if the door is unlocked ad skipping to sequence3 Sequence 2 should unlock the door(s) Sequence 3 should lock the door(s) You may need to change the delays until you get an acceptable response. Ideally Line 1 of sequence 1 should be delayed long enough for the door to return to lock after the reader entry. As an option you could have sequence 1 check the status of the door. A badge read when the door is closed unlocks the door(s). A badge read when the door is open locks the door(s).

Issue Direction of data transfers between Xenta Servers is important in versions 5.1.4 and later.  Stable communication over TCP/IP, UDP requires management of the data flow.  In XBuilder 5.1.6 and later, it will give an error on any connection objects not created using this standard: "It is not allowed to connect a signal to an output that results in a write over the IP network." Product Line TAC Vista Environment Xenta Servers v 5.1.4 and later XBuilder Cause Properly managing data flow will cause the TAC Xenta Server to poll for data, rather than accept an asynchronous write command. This will result in a more stable TCP/IP connection. Resolution See TAC Vista 5.1.5 Release Notes for more information. When importing another TAC XBuilder project to the current TAC XBuilder project in order to create data point transmission between two TAC Xenta Servers, make sure to import the data producing project into the consuming project. In the above example, because Xenta Server A is sending the Outside Air Temperature point to Xenta Server B, it is Xenta Server B's XBuilder project that should be edited.   In XBuilder, right-click on IP Backbone under the Network pane Select New > Other Projects Network In this example, Browse the sending project, Xenta Server A, into the receiving project, Xenta Server B Bind all data using connection objects into the receiving project's network. If bi-directional data flow is desired, the same steps must be performed on Xenta Server A's XBuilder project. The proper way to connect signals in this scenario can be found in Polling data over IP from the System pane of a 700 project.

Issue Set up a two wire LTS80 Lini-Temp sensor on a 7756 PCU on the lower board Product Line TAC INET Environment LTS80 Lini-Temp temperature sensor 7756 PCU lower board Cause Lini-temp is a type of temperature sensor that is compatible with the I/NET product line. Resolution For Fahrenheit: M = 0.0274669 B = -459.8 10k ohm resistor in slot "A" Remember, the lower board has a different resolution than the upper board. See Set up a two wire LTS80 Lini-Temp sensor on a 7756 PCU on the upper board for details on the upper board. Refer to TCON 127: 7756 PCU Installation Guide for details

Issue Standard Output Window displays the following error:  Java.net.socketexception.reset Product Line TAC IA Series Environment R2 Niagara Cause The IP network has two NIC cards assigned the same address.  This results in a  Duplicate IP Resolution Use WireShark to Find the duplicate IP and re-assign a new ip to the server or UNC IP. For more detail see Using WireShark to analyse communications on an Ethernet network. 

Issue How to identify the Firmware / Software Version of an Xenta Controller Product Line TAC Vista Environment Firmware/Software Version of Xenta Controllers LonMaker Vista Cause The Firmware/Software Version of a Xenta Controller can be used for troubleshooting issues on site, or determining if an upgrade is required. Resolution The Application Specific Controller version Open LonMaker Right Click on the ASC and choose properties Select the Self-documentation tab Firmware/Software Version should appear in the bottom window The Programmable Controller version Open Vista Right Click on the Programmable Controller and choose properties Expand the window if necessary to expose the Information tab Select the Information tab Firmware/Software Version should appear as Software Version Please see Xenta Software current versions as of 10/2012 for most current released Xenta Software versions

Issue Different Continuum products are approved to different approval standards and where are copies of these certificates held? Product Line Andover Continuum Environment All Hardware products: Standards listings to UL, BTL C-Tick, CE Cause Copies of the approval certificate or clarification on the different standards are required. Resolution The Agency listings each controller is approved against are defined on the datasheet, for more information see How do I get the part numbers and datasheets for Continuum products?. An example of the approvals for the bCX1 controllers are: UL/CUL 916, UL 864 9th Edition, FCC CFR 47 Part 15, ICES-003, EN55022, AS/NZS 3548, Class A, VCCI, EN61000-6-1, CE   All of the Regulatory Compliance documents including: UL, CUL, ISO,  European CE Certificates, Australia/ New Zealand  C-Tick Certificates and WSP Cert can be downloaded from The Exchange Download Center -  Regulatory Compliance   Confirmation of BACnet testing can be seen at the BTL website: http://www.bacnetinternational.net/btl/ European Standards - Continuum has been tested to the following as part of the 89/336/EEC Electromagnetic Compatibility Directive and over the years the standards have changed. Emissions -Continuum is tested against EN55022-Class A This is the emission standard for Information Technology equipment and another emission standard is the EN50081-1 but this is a generic emission level and less stringent than the IT standard that Continuum complies with. Immunity - These standards have changed over the years, older controllers were tested against the International IEC1000-4 and we state the specific levels our controllers are tested against, then when it was released in 2000 we used the EN50082-1 standard which replaced the IEC standard in Europe. But newer controllers have now been tested against the EN61000-6-2  standard that have since replaced the other immunity standards.    There is also the EN60730-1 standard that Continuum is approved to, this defines the standard controls specifications it can perform. These standards are required for us to apply the CE marking to our products.

Issue Unable to relay Email not working Product Line TAC Vista Environment Vista SMTP Cause If an error "Unable to relay" is returned, this is most likely because authentication is not sent to the SMTP server. Resolution Go to Vista Server settings At the email tab set proper authentication (TAC Vista Technical Manual Chapter 3.3 explain this more in detail) You may need to consult with the IT department on site For more information on troubleshooting sending emails from a Vista server, see Troubleshooting Sending Emails from a Vista Server.