Building Automation Knowledge Base

Issue Menta module names disappear when exporting a Xenta from Vista version 5.1.8 and importing it to Vista version 5.1.7  Environment TAC Vista 5.1.7 and 5.1.8 Cause Changes is made in the export/import function in TAC Vista 5.1.8 which will cause problems to import a export file from TAC Vista 5.1.8  in to TAC Vista 5.1.7. Resolution To be sure that the export/import function should work only export and import between Vista systems of the same version. 

Issue Diagnosis of a full Vista database shows that trend log storage size the culprit. Environment Vista trend logs SQL database Cause Excessive trend logging can quickly fill a database. Resolution This search will show both Xenta trend logs declared in Workstation/Menta and Vista Server logs. Search for ‘Type of devices or objects: Logical objects – Files – Trend Logs – Trend Log Vista’ Set Property Value – Status – Equal to ‘On’ Deselect the ‘interrupt if more than 1000 results’ if large Db with need for many logs. Once search populates right click on any result, Additional Property Value – Log space. This will add a column showing this setting in seconds.  Sort column to identify any trends that are set to store more than the desired amount of values and could be causing issues.  Note: 604800 sec = 1 week

Issue Extended Trend Logs Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Automation Server Premium (AS-P) Building Operation Automation Server Bundled (AS-B) Cause When configuring extended logging in the BACnet application folder, these objects are not available when performing a device discovery from the AS or ES. Prepare one AS with a BACnet point Create a trend log on the BACnet point Create an Extended log for that BACnet trend log From a second AS, the BACnet objects are available after a Device Discovery except for the Extended log object. StruxureWare Building Operation online help for “Configuring Extended Logging for a BACnet Trend Log” states:    ***Key Concept: Extended trend logs are not BACnet objects. These are StruxureWare Building Operation exclusive. The term "BACnet Extended Trend Log" does not exist and is a misnomer. Resolution The main reason is that extended logs are not defined in the BACnet standard; they are proprietary to EcoStruxure.  Everything that is proprietary to EcoStruxure Building Operation is not exposed to BACnet including graphics, script & function block programs and central IO points are not directly exposed, but have to be bound to BACnet I/O objects. The extended log serves the purpose of expanding a log on a larger capacity server.  A trend log on an AS would be more appropriate to extend on an ES. If you have a trend log in an external BACnet device (like a b3 or a 3rd party device/system) then you would want an extended log in the AS, to collect from that device (and then maybe a larger extended trend on a parent ES). If there is a local BACnet trend log in an AS (in the BACnet interface application folder) that is required to be larger, consider increasing the buffer size property of the one log that is needed (the default size of 10 may be too small, and increasing to 1000 up to 5000 (extended log size) may be an option). That would be most interoperable with other (3rd party) BACnet clients that need access to the trend log data.

Issue Clarification on how to wire Form A and Form K Triac outputs on i285-V / b3865-V controllers. Environment i2865-V b3865-V i2866-V b3866-V i2865-V-S b3865-V-S i2866-V-S b3866-V-S Cause Had issues in the past with blown Triac outputs due to wiring, need to confirm how they are properly wired for Form A and Form K Triac outputs. Resolution As per 30-3001-810 i2 b3 865-866 Controller Installation Instructions (see page 5), you can configure your Triac so they switch the 24VAC (hot) or the GND (ground), but all Triac outputs must be configured the same. The difference between the Form A and the Form K is that the Form A is two digital outputs using a single triac each while the Form K is a single tristate output using both physical triacs for the one (logical) output. The Form A Triac outputs can be configured as either a hot or ground switch but the Form K must be configured as a ground switch (TRIAC REF tied to GND, Load to 24VAC).

Issue At times the firmware and software on the Roam IO2 requires updating and instructions are needed Product Line Andover Continuum, EcoStruxure Building Operation Environment Roam IO2 Windows XP Windows 7 Windows Server 2003 Windows Server 2008 Windows Mobile Cause Instructions for upgrading the software and firmware are provided in the User's guide, but this article places them in an easy to find location Resolution The full instructions for installing and using the RoamIO2 software and hardware are in the User Guides: BACnet Service Tool User Guide + Software Infinet Service Tool User Guide + Software NOTE: The RoamIO2Appl2.000002.upd firmware firmware can only be updated from the BACnet service tool, the Infinet service tool does not have the update OS option.     Please see instructions for installing firmware and hardware for the RoamIO2 for an overview.  

Issue Setting up, using, and troubleshooting Windows Active Directory with Building Operation Workstation and WebStation. Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation WebStation Windows Active Directory Windows Server Cause When integrating EcoStruxure with Windows Active Directory, NO user accounts need to be created in EcoStruxure, all that needs to be done is map the EcoStruxure User Account Group(s) with the Windows group(s) that will be used.  You can map Windows Active Directory groups to Building Operation user account groups if Building Operation runs on a network that uses this directory to manage users and user account groups. A Building Operation user account group that includes a Windows account group can also be a member of another Building Operation user account group. Mapping Windows Active Directory account groups to Building Operation user account groups has advantages both for administrators and operators. Administrators can manage the user accounts in the Windows Active Directory, rather than managing the accounts in two places. Any changes are instantly implemented to the mapped Building Operation user account group. Operations only have to remember the Windows login. Once logged in to a Windows user account that is mapped to a Building Operation account, the user is authenticated to access WorkStation without having to log in a second time. Note: The Building Operation domain used to map the Windows Active Directory user account groups must be a member of the Windows domain where the Active Directory is located. Windows Active Directory account groups can only be mapped on servers that are based upon Microsoft Windows operating system. Automation Servers, cannot map Windows Active Directory groups. For example, the Windows Active Directory user account groups Main Admin and Main User are mapped to the Building Operation user account groups Administrators and External Users. The External Users user account group is a member of the Operator user account group. The Administrators account group, which is a member of the External Users, inherits access to the Operation workspace. The user will then log into Windows on the PC where the WorkStation is installed. When logging into EcoStruxure Workstation the authentication is automatically done from the Windows user account. Resolution NOTE: Active Directory association cannot be achieved using the inbuilt Local Domain Create a new EBO Domain and associate it with your active windows Domain. NOTE: It is best to only use the Domain (Netbios) name (as shown above) when adding the Windows Domain name to this property.  Using the full DNS Domain name, for example, eur.gad.schneider-electric.com will cause issues when utilizing other features that require active directory authentication.  One example where this has been identified is with Change Control.   Create an EBO Domain Group within that new Domain and associate it with the Windows Domain Group in which the Windows Active Directory user(s) reside. Log in using Windows Username, Password, and Domain rather than EBO credentials. When logged on to the Enterprise Server PC as a Domain User it is also possible to select the "Log on as" box. See WebHelp: How to Create and Configure a Domain Conceptual Information on Windows Active Directory User Groups How to Create User Account Groups Troubleshooting Windows Active Directory with Workstation Log in Error: Wrong user name or password If the EcoStruxure Building Operation Domain has the same name as the Windows Active Directory domain name, it will expect the user account to exist locally in the Building Operation domain. Log in Error: "User account not associated with a group. Contact your Administrator." Verify that the Windows user is a part of the Windows group configured in the Building Operation Group settings. In order to identify every group that the current windows user belongs to, run the command: whoami /groups Once the Windows user has been confirmed as a member of the configured Windows group, try changing the Log On as credentials for the Enterprise Server service. The default user that is used when installed is the "Local System account". The Windows account used to run the Enterprise Server service needs "read access" to all places (e.g. OUs) in the Active Directory where user groups potentially involved in an EBO Windows log-on can be found. Note: By default, all domain users in an Active Directory have read access to Active Directory "Users and Computers" objects so it is the sites that have restricted this in some way that may face issues. You do not need to use “domain admin” type accounts for this as they are granted way too much authority in general. An account that has read access to sufficient parts of the AD while having only normal local user privileges on the machine where the Enterprise Server is running will suffice. From the Windows Start menu, launch Computer Management. In Computer Management go to Services and Application > Services. Find Building Operation X.X Enterprise Server, select it and Stop the service. Right-click on Building Operation X.X Enterprise Server and go to Properties. Select the Log On tab. Under Log On as select "This account". Enter a Windows user login that has sufficient Windows rights for the Enterprise Server to log on as. Click OK and then start the service again. Log in to Workstation again using Active Directory. Troubleshooting Windows Active Directory with WebStation From version 1.5.0 and up, using Windows Domain accounts is supported in WebStation. However, the following must be done in order to log in. Must use HTTPS. Must enter your Windows username and password. Must enter the domain as the Windows domain as defined within Building Operation.  See below: An example log-on format is shown below when using the above configuration when using WebStation:    Alternatively, if the following is configured in Building Operation: WebStation log-on will look as follows:  Download a TVDA for Single Sign-On Instructions

Issue When trying to open a report, you get an error message like below: Msg=DDL creation failed ex=Error creating DropDownddlTopCount The request failed with HTTP status 503: Service Unavailable Ex=ButtonRunReport The request failed with HTTP status 503: Service Unavailable   Product Line EcoStruxure Building Operation Environment Reports server Cause Cause 1: The Report Server Service is not started To check if this is the cause, open the report manager. If you get the error below, continue to resolution 1.   Cause 2: The Report Server Service takes too long to generate the report and thus times out The root cause should also be investigated. It can be a slow network connection, fragmented SQL database, antivirus software or memory limitation that is slowing the request to compile a report down. Resolution Resolution 1 Open "Reporting Services Configuration Manager" Start the server   Resolution 2 Increase the timeout for the report service Open Report Manager Click "Site Settings" Change the Report Timeout. Default is 1800 which is 30 seconds.   Check that the memory usage for the SQL server is not limited (Microsoft's How to: Set a Fixed Amount of Memory (SQL Server Management Studio)) Open SQL Management Studio Open the properties for the SQL Server Click "Memory" and check that the value is default (2147483647)   Reindex and defragment the SQL database e.g. using SBO Reports Agent Config.

Issue How long has an Automation Server been running since the last power cycle or reboot? Environment Automation Server SmartStruxure Device Administrator Cause The uptime of an Automation Server indicates how long the server has been operational since the last power cycle or system reboot. This is not currently visible in the StruxureWare Building Operation Workstation, but it is available through the Console interface in Building Operation Device Administrator. By monitoring the uptime of the device this can be a valuable diagnostic tool to determine if power loss occurred, crashes in Automation Server occurred, or other situations that might have resulted in a reboot and what time this occurred. Resolution In the Building Operation Device Administrator connect to an Automation Server (IP or USB) and select the "Open Console" option. Once logged into the Console issue the "uptime" command in the prompt. The uptime will be listed in Days, Hours, and Minutes as visible below: admin@AS-B-RKFDMW:~> uptime  14:18:20 up 1 day,  1:01, load average: 1.26, 1.16, 1.06   If you are using Report Server, this information is also available using SQL Server Management Studio from the Report Server PC. Enter the following query and the "Runtime" column will provide the current uptime for the specified ES or AS. SELECT Top (1) CAST(CURRENT_TIMESTAMP - DateTimeStamp AS Time) AS 'Runtime' ,DateDiff(Day, DateTimeStamp, CURRENT_TIMESTAMP) AS 'Days Up' ,DateDiff(HOUR, DateTimeStamp, CURRENT_TIMESTAMP) AS 'Hours Up' ,DateDiff(MINUTE, DateTimeStamp, CURRENT_TIMESTAMP) AS 'Minutes Up' ,DateDiff(SECOND, DateTimeStamp, CURRENT_TIMESTAMP) AS 'Seconds Up' ,[DateTimeStamp] ,[TYPE] ,[OriginatedServer] ,[OriginatedDevice] ,[SystemEventId] FROM [StruxureWareReportsDB].[dbo].[tbEvents] WHERE SystemEventId = 'Server initialized' AND OriginatedServer = '/Server 1' ORDER BY DateTimeStamp Desc   NOTE: Change the WHERE statement "OriginatedServer = '/Server 1'" so that '/Server 1' become '/yourServerName'

Issue Which Continuum versions support an NC2(9680)? Procedure for replacing a CX99xx with a CX9680 Product Line Andover Continuum Environment CX9940 CX9900 NetController 2 NCII CX9680 Cause Netcontroller II (CX9680) is supported in Continuum versions 1.80 and higher Resolution Upgrade the site to Continuum 1.80 or higher for NC2 support   Procedure for converting an NetController1 (NC1/99xx) to a NetcontrollerII (NC2/9680) To convert a NetController to a NetController II, perform the following steps:   Back up your SQL Server database. See the Andover Continuum CyberStation Installation Guide, 30- 3001-720, and Microsoft® SQL server documentation. From the Continuum Explorer, use the right-click popup menu for this controller, and select Send to Text File. This drops the controller object’s data into a text file. For various ways to customize this operation, whereby you can save the controller’s child objects, please see the Send to Database Options in the CyberStation online help. Update your workstation with a version of CyberStation that supports the newer NetController models. These models are supported by CyberStation Version 1.8 and higher. Physically remove the old NetController, and mount/connect your NetController II. When you configure and commission the NetController II, use the same controller name, network IP address, and network ID. This is performed via the controller’s embedded web commissioning pages and via the General tab and the Network tab of the CyberStation’s Infinity Controller editor. Switch to CyberStation offline editing mode in the InfinityController editor. On the General tab, from the Controller Type dropdown menu, change the model number to 9680 or 9681, depending on which NetController II you are installing. Make sure you actually want to replace the NetController. When you attempt to change the controller model, Cyberstation displays a few warning messages: Cyberstation warns that a model change is irreversible. Cyberstation warns that, if an XDriver is used with this controller, not all XDrivers are supported by the new model. If you proceed, the XDriver links are left in place regardless of the availability of a replacement Xdriver. XDrivers on NetController II — In general, Xdrivers that are available on the bCX1 model 9640 are also supported on the NetController II. For example, supported NetController II XDrivers include, but are not limited to, the following: Filter XdTest Modbus TCP Modbus RTU XDrivers built for the previous-generation NetControllers will not run on the NetController II. What is an XDriver? An XDriver is special, customized software that your site purchases separately from TAC. The XDriver software allows your controller to connect to and communicate with a special piece of third-party equipment needed at your site. In the CyberStation CommPort editor, you must configure a controller comm port for this special device that the XDriver software enables. * When you leave the InfintyController editor, go back to online editing mode. If necessary, provide an updated XDriver file compatible with your NetController II. CyberStation prompts you to do this. Note: You can specify an XDriver on the General tab of the CommPort editor. Specify XDriver for the Default Mode, and use the browse button in the XDriver File Name field to search for and specify the path of the XDriver. Determine whether this NetController II has network security. If so, configure network security for this controller. Note: Network Security is supported only in NetController II model 9680, as well as ACX controllers 5720 and 5740. Restore (reload) data from your database into the new controller. From CyberStation’s Continuum Explorer, use the Object dropdown menu or right-click the object popup menu for this controller object, and select Send to Controller. Back up to flash. In Continuum Explorer, right-click over this controller, and from the container popup menu, select Backup to Flash. This saves the controller’s RAM configuration to its flash memory, in accordance with the attribute value that is set for the ACCRestartMode system variable.

Issue Need to Export a Trend log file without using Reports Server Product Line EcoStruxure Building Operation Environment SmartStruxure Workstation Cause Customer needs a log file, but does not have Report Server Resolution In Workstation, right click on a Trend and create a new Trend Log List View Once the List populates, click on the Icon showing a green arrow labeled .csv Save the file to an appropriate location. If this is a frequent action, save the Trend Log List View Please Note that this feature is not available in WebStation  At v2.0 WebStation introduced the option to export to Excel, creating an XLSX file, this can be opened in Excel and saved as a CSV if required (this option is not available if WebStation is directly logged on to the AS/P/B)

Issue SE7300 series BACnet controller does not come online in StruxureWare Building Operation if the communications address is greater then 127. Product Line EcoStruxure Building Expert, EcoStruxure Building Operation, Field Devices Environment StruxureWare Building Operation BACnet Cause The communications Address of SE7300 series BACnet controller can be set between 0 to 254. In StruxureWare Building Operation the highest address can be set only up to 127. Resolution Set the communication address less than or equal to 127 for SE7300 series BACnet controllers. Please refer to the Default Device ID / Device Instance of SE7000 series BACnet controllers to know the default Device ID / Device Instance of SE7000 series BACnet controllers.

Issue Send an SMS text message when an alarm occurs. Product Line EcoStruxure Building Operation Environment Alarming SMS Text Cause Sending an SMS Text message in response to an alarm condition will allow the responsible personnel to react immediately, even if they are not currently at the workstation. Resolution EcoStruxure Building Operation does not support direct SMS texting. One workaround is to use an Email to SMS Test service provider that handles conversion of emails to SMS, as emails are easily created in EcoStruxure Building Operation.   If direct SMS functionality is required there are work arounds with 3rd party programs such as SysManSMS via file output options (see Using Sysman alert server with StruxureWare Building Operation). Note that this third party products such as this are not supported or tested by Schneider Electric.

Issue Is the Continuum Cyberstation a B-OWS (BACnet Operator Workstation)? Product Line Andover Continuum Environment Continuum Cyberstation BACnet Cause Can't find reference to Continuum Cyberstation being defined as a B-OWS. Resolution The Continuum Cyberstation is a B-OWS and complies with ANSI/ASHRAE standard 135-2004.  However, the Continuum Cyberstation has not been BTL tested, please see the Schneider Electric BTL Listing of Tested Products.    The following selection is taken from the Andover Continuum Family of User Interfaces document describing Continuum's Cyberstation capabilities. Native BACnet B-OWS CyberStation communicates with the BACnet devices using BACnet/IP in strict accordance with ANSI/ASHRAE standard 135-2004 and is designed to function as a BACnet Operator Workstation (B-OWS) and BACnet Broadcast Management Device (BBMD). The CyberStation can communicate to all Andover Continuum BACnet Devices as well as any third party BACnet Device on the BACnet network.

Issue Does the Automation Server support network authentication via Radius Server (IEEE 802.1X)? Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Cause AS supports network authentication via Radius Server (IEEE 802.1X)? Resolution RADIUS and IEEE 802.1X are not the same thing, although they can be used together. Remote Authentication Dial In User Service (RADIUS) is a networking protocol that provides centralized Authentication, Authorization, and Accounting (AAA) management for computers to connect and use a network service. RADIUS is a client/server protocol that runs in the application layer, using UDP as transport.   The RADIUS server is usually a background process running on a UNIX or Microsoft Windows server. RADIUS serves three functions: to authenticate users or devices before granting them access to a network, to authorize those users or devices for certain network services and to account for usage of those services.  IEEE 802.1X is an IEEE Standard for port-based Network Access Control (PNAC). It is part of the IEEE 802.1 group of networking protocols. It provides an authentication mechanism to devices wishing to attach to a LAN or WLAN. It is a mechanism used in (mostly) switches and wireless access-points to allow or block devices to access the network (or granularly allow access to parts of it).   For example, if you have a network port in a meeting room, you can enable 802.1x on the switch port and configure it in such a way that when an employee connects they have access to the entire network, but if a guest connects (with a temporary password) they can only reach the Internet and if a passer-by is tempted to try his luck, they cannot access anything at all. Does IEEE 802.1X also use RADIUS as it's underlying authentication mechanism? Yes and no. IEEE 802.1x uses Extensible Authentication Protocol (EAP), the drawing below shows that for wired 802.1x: EAP over LAN (EAPoL) is used between the Supplicant (software on a computer) and the Authenticator (switch). EAP is then usually tunneled over Radius between the Authenticator and the Authentication Server, but it can also be done over Diameter (the successor to Radius). For wireless, it is similar in the sense that there is also no Radius between the supplicant and the authenticator, only between the authenticator and the Authentication Server (to tunnel the EAP). From EBO 2022 the AS-P and AS-B can be configured as supplicants on a network protected by IEEE 802.1X security. See the IEEE 802.1X Security Webhelp topic for further details.   Note: MPx/RPx do not support 802.1x network authentication, see the SpaceLogic controllers MPx/RPx do not support 802.1x network authentication Knowledge Base article  for further details.    

Issue An AS has failed and there is no backup. Can the SD card from the broken AS be used in a new AS Product Line EcoStruxure Building Operation Environment Automation Server Cause AS has failed without any backup and there is a need to get the information to the new AS Resolution The SD card in each AS is encoded for that specific AS. The information on the SD card can only be read by that AS. AS's are now replaced by the AS-P, however if an AS can be obtained, then a backup can be recovered as follows:   It is possible to put the SD card from the damaged AS into a non damaged AS and do a backup. Then the backup can be restored into a new AS-P. The AS-P does not use a SD card. Important note: The version of the bad AS / SD card needs to match the donor AS used to make the backup. To remove the memory card push the metal retainer in towards the centre of the PCB The metal retainer will disengage its locking catches The metal retainer is hinged and can then be opened The memory card can then be lifted out for replacement Replacement is the reverse of the removal process.

Issue VSB valves have been substituted by the Schneider Electric V211T valve VSB..F valves have been substituted by the Schneider Electric V211 valve VMB valves have been substituted by the Schneider Electric V311T valve VMB..F valves have been substituted by the Schneider Electric V311 valve Product Line Field Device Environment VMB VSB Cause The existing actuator is not compatible with the replacement valve as it is a different type. Resolution Schneider Electric  are no longer supplying VSB and VMB valves. They are replaced by a Schneider Electric Venta valve. Note: VSB and VMB valves are still manufactured by Controlli. VSB 2 ports are replaced by the V211T, VSB..F is replaced by the V211. VMB 3 ports are replaced by the V311T, VMB..F is replaced by the V311. The existing actuator will no longer fit on the new valve and needs to be replaced as well. If the actuator was a Controlli MVB22, MVB26 or MVB28, then replace with MV15B-230 actuator. If the actuator was a Controlli MVB46, then replace with MV15B-24 actuator. If the actuator was a Controlli MVB36, MVB52 or MVB56 then replace with M800 actuator. For compatibility: V211, V211T, V311 and V311T Venta valves are directly compatible with the Forta range of actuators e.g. M310, M400, M800, M1500, M3000, M700, MG900 and the MV15B-24/230 and no linkage kits are required.

Issue Wire colour coding for the SPP110 Product Line Field Devices Environment SPP110: 004702020 004702040 004702060 004702080 004702100 004702120 004702140 Cause Wire colour coding SPP110 required. Resolution Due to supply problems, between week 23 to week 32, there was a change to the sensor's cable and the wire colours. This was implemented by the manufacturer without Schneider Electric's knowledge. So no product announcement was produced.                      Original       Week 23 to Week 32 No. Function Colour                Colour 1     Y            Brown                Green 2    GO         Black                  White 3    G            Red                    Brown   Standard                                                                                           Week 23 to Week 32   Refer to the SPP110 Pressure Transmitter Wet Media Specification Sheet for more information.   The SPP110 installation sheet showing the standard wire colouring is available here The SPP110 installation sheet showing the wire colouring is attached.

Issue Is there a limit to the number of S-Cables which can be used when connecting additional rows of I/O modules? Environment S-Cables I/O modules Rows extending Cause SmartStruxure is being installed into an existing building and the current controllers are split into several rows. Resolution A maximum of 5 cables can be used on an IO back plane. You can serially connect up to 2 S-cables in a row to extend the length. This information was located in StruxureWare Building Operation Help – Installation Instructions - Terminal Base TB-PS-W1

Issue Will J-Bus operate with Modbus RTU devices on the same bus? Product Line EcoStruxure Building Operation  Environment Building Operation Automation Server Building Operation Automation Server Premium Building Operation Automation Server Bundled Cause Compatibility of J Bus required. Resolution The J Bus protocol is supported by the Autimation Server, it runs on an RS485 network and uses a subset of the Modbus RTU protocol function codes. The J Bus devices addressing usually has an offset of 1 compared to the Modbus RTU standard, to apply this offset select "J-Bus Mode" = Yes in the Modbus Master Network Properties.   Verify that the devices to be used have a standard RS485 electrical connection and do not require any special electrical biasing, also ensure that all units connected on the bus have a unique ID/ address number. If this is the case then you should be able to connect both Modbus RTU and J Bus devices on the same Automation Server port connection but in the Modbus Master Network select the J Bus Mode setting to No. In J-Bus mode, the Automation Server will automatically reduce the polled register addresses by one, so if the AS is set to Modbus mode, you may need to manually set the register addresses of any J-Bus devices by minus one. With J Bus as with Modbus sometimes the point addressing needs to be offset by +1 or -1, but check with the 3rd party device supplier/ documentation to determine its specific point addressing requirements.  

Issue Workstation displays power in Btu/s when VA is required. Product Line EcoStruxure Building Operation Environment Workstation Cause The units displayed in Workstation are based on the Regional and Language Options settings in Windows Control Panel as talked about in Metric vs. English (Imperial) Operating System. Resolution The Unit Conversion Exception tool can be used as a solution for this issue. This is located in the Domain portion of Workstation's Control Panel. For more information on the Unit Conversion Exception see Unit Conversion Exceptions feature or the Online help located here. In the situation where VA has been set as the power unit but Btu/s is still displayed, the unit conversion shown below will resolve the issue. Note: If your desired value units have a prefix, then this needs to be done in the Unit Conversion Exception as well (kVA). Note: WebStation (as of v1.3 SP1) does not use the Windows OS setting because the AS does not currently have localization - it uses only the International System of Units (SI) - not the Imperial or US units.