Building Automation Knowledge Base

Issue I/A Series G3 Niagara network points in fault and indicate Subscribed error:invalid permissions. Environment I/A Series G3 (all versions) Cause The credentials being used by the connection does not have the correct permissions to access the data. Resolution Verify username / password and associated permissions related to station to station fox connections.  Modify the associated permissions on the server side or use another set of credentials that have permissions.

Issue Schneider Electric domain firewall policy Product Line Satchwell BAS & Sigma Environment Engineer's laptops Cause Schneider computer/domain updates include McAfee firewall updates. It has been seen on some laptops with a fully working Sigma system, after a  Schneider policy update, the Sigma client fails to connect to the server.   Resolution Access to the firewall setting, on most Schneider Electric engineer's  laptops is not possible. Disabling the McAfee firewall should allow Sigma to load. Locate and, with a right mouse click, select the McAfee Icon  (found on the taskbar near the clock). From the list provided select "Quick Settings" Then select "Enable Firewall Timed Groups", You will need to enter a reason. The firewall will be disabled for a one hour period. 

Issue The LON network is experiencing high bandwidth utilization identified by problems with commissioning devices and intermittent communication loss. Product Line EcoStruxure Building Operation Environment Building Operation LON devices Cause There can be many causes for high bandwidth utilization, including configuring change of value trend logs directly to points on the LON devices without using the local node. This causes Building Operation to poll the values constantly to see if there has been a change which in turns impacts the communication. Another cause can be graphics pages with a very large number of points. Even pages with many hidden layers will poll every point including the hidden layer points. It is important to bind any values coming into the Automation Server through the Local Node. Another cause can be the lack of proper LON interface configurations such as Bandwidth Throttling. Resolution The best option is to modify the Change of value logs to the type Interval logs. If it is a graphic causing the issue, then reduce the points on the graphics page. If these options are not suitable then using the local node option described below will help in reducing the bandwidth. Utilize the Local Node Create a Local Node underneath the LonWorks Network in the Enterprise or Automation Server. Create a SNVT underneath the Local Node that matches the one you want to log or bind. Make a SNVT binding from the Device to the SNVT created under the Local Node that triggers on change. For more information on Lon interface configuration settings, see LonWorks Interface Properties – Advanced Tab.

Issue What web browsers are compatible with Sigma Web ActiveX interface Product Line Satchwell Sigma Environment Sigma 4.3 and later Cause Later versions of Internet Explorer do not display the Sigma ActiveX web pages. Resolution Sigma 4.3 introduced the ActiveX web client, this interface is only compatible with Microsoft Internet Explorer. The table below details the versions of Internet Explorer that are compatible with the various Sigma Web ActiveX releases. Operating System/Sigma Version 4.08 4.07 4.06 4.05 4.04 4.03 Microsoft ® Windows 2000         IE6 IE7 IE6 IE7 Microsoft ®Windows XP IE7 IE8 IE7 IE8 IE7 IE8 IE6 SP3 IE7 IE8 IE6 IE7 IE6 IE7 Microsoft ® Windows Server 2003 IE7 IE8 IE7 IE8 IE7 IE8 IE6 SP3 IE7 IE8 IE6 IE7 IE6 IE7 Microsoft ® Windows 7 IE8 IE9 IE8 IE8 IE8     Microsoft ® Server 2008 N/A N/A N/A N/A     Later versions of Internet Explorer than those listed above may be supported in Compatibility View

Issue During SQL install portion of Continuum installation the following error message is received. "SQL Express is not installed properly. Please contact technical support representative." Product Line Andover Continuum Environment Continuum Cyberstation (All Versions) Microsoft SQL Express (Version dependent upon Continuum version) Cause Bit Locker has been installed on the system to which Continuum Cyberstation is being installed. Bit Locker enforces specific password requirements across all Microsoft Windows products. Find the SQL installation log at C:\Program Files (x86)\Microsoft SQL Server\110\Setup Bootstrap\Log\20190627_092341\Summary_WTUSLVSE076617L_20190627_092341.txt *NOTE* The parent folder of the log will include the date and time of the installation. The log file name format will be Summary_(your computer name)_date_time.txt At the bottom of the log, you will see an Exception summary which gives full detail of what the error is: "Exception summary: The following is an exception stack listing the exceptions in outermost to innermost order Inner exceptions are being indented Exception type: Microsoft.SqlServer.Chainer.Infrastructure.InputSettingValidationException Message: The specified sa password does not meet strong password requirements. For more information about strong password requirements, see "Database Engine Configuration - Account Provisioning" in Setup Help or in SQL Server 2012 Books Online. HResult : 0x84b40000 FacilityCode : 1204 (4b4) ErrorCode : 0 (0000) Data: SQL.Setup.FailureCategory = InputSettingValidationFailure DisableWatson = true Stack: at Microsoft.SqlServer.Chainer.Infrastructure.InputSettingService.LogAllValidationErrorsAndThrowFirstOne(ValidationState vs) at Microsoft.SqlServer.Configuration.SetupExtension.ValidateFeatureSettingsAction.ExecuteAction(String actionId) at Microsoft.SqlServer.Chainer.Infrastructure.Action.Execute(String actionId, TextWriter errorStream) at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionHelper(TextWriter statusStream, ISequencedAction actionToRun, ServiceContainer context) Inner exception type: Microsoft.SqlServer.Configuration.SqlEngine.ValidationException Message: The specified sa password does not meet strong password requirements. For more information about strong password requirements, see "Database Engine Configuration - Account Provisioning" in Setup Help or in SQL Server 2012 Books Online. HResult : 0x851a0013 FacilityCode : 1306 (51a) ErrorCode : 19 (0013)" Resolution Update or use password for new database that meets the minimum standards of: 8 Characters 1 Capital letter 1 Numerical character 1 Special character (!,@,#...) 1 Lowercase letter This will allow SQL Server to be installed

Issue When reviewing events from Doors or Users, the below error is shown. The communication object, System.ServiceModel.Channels.ServiceChannel, cannot be used for communication because it is in the Faulted state. Error - The communication object Product Line EcoStruxure Security Expert Environment Security Expert Server Security Expert Client Workstations SP-C Controllers. Cause Firewall and/or Port settings are incorrectly configured. Certain ports must be opened to enable communication between the server, client workstations, and controllers. Resolution Check the Firewall to ensure that all required ports are open between the Security Expert Server, Security Expert Client Workstations and the SP-C Controllers. Refer to the IP Networking Ports section in the SX-SRVR Security Expert - Networking Guide for Administrators - Reference Guide for details on required ports.

Issue The status of a Forced BACnet value is not reflected in a Graphic or the Watch Window. Product Line EcoStruxure Building Operation Environment Enterprise Server (ES) Automation Server (AS) Cause This is functioning as designed. It was designed so that the "Forced" status for BACnet values would not be displayed in graphics or the watch window. Resolution It was designed so that the "Forced" status for BACnet values would not be displayed in graphics or the watch window. For a workaround using a PE Script program to show the forced icon for a BACnet value see How to show the forced icon for a BACnet value in a Graphic. In EBO version 3.0.1 and later this issue only occurs on internal BACnet points, points which are located in the Application folder under the BACnet interface for the SmartX server.

Issue BACnet bCX schedules cannot be edited without an error. Product Line Andover Continuum Environment Continuun bCX4040 Schedule Firmare v4.500082 Cause Following an upgrade to firmware v4.500082 the  Schedule end date year 2038 now enforced and schedule cannot be modified if the end (effective) date is beyond this Resolution For all schedules newly created or otherwise, the end (effective) date needs to be set to 2038 or earlier see Script Programs in Continuum compared to StruxureWare Building Operation and using floats (32 bits) and 64 bit numbers If the date is set after 2038 then an error is seen when trying to edit the schedule "An error code was returned from a BACnet operation, but the reason could not be determined."   Creating a new schedule with a date > 2038 can also give the error: " Error setting attribute 'DeviceID' An error code was returned from s BACnet operation , but the reason could not be determined " Defect was corrected in v4.500083

Issue How can I add a SmartStruxure Automation Server to TAC Vista using BACnet/IP and what is needed Product Line TAC Vista, EcoStruxure Building Operation Environment TAC Vista Xenta 913 Automation Server Cause Building Operation versions earlier than 3.2 are not FDA 21 Part 11 approved, In instances where the version is lower than 3.2 it can be achieved by using  TAC Vista as a front end, and having Automation Servers as field controllers. In Building Operation version 3.2 and later an optional Regulated Industries Compliance Pack is available that can be used without the need for  TAC Vista as a front end. Resolution 1. Create a BACnet interface in Automation Server. 2. Create BACnet points in the "Application" folder 3. Browse the Automation Server with a BACnet browser (Here is a free tool) 4. Note the instance id's of the points 5. In TAC Vista, create a Xenta 913 6. Edit the Xenta 913 7. Create a "BACnet IP Client" interface and give it the IP address of the Automation Server 8. Create a BACnet device template containing the points you need - refer to the id's previously discovered 9. Add the device template to the "BACnet IP Client" interface in XBuilder 10. Save and download the project 11. Now you get the live values from the Automation Server in TAC Vista

Issue The Xenta 913 supports several different BACnet object types but does not support all object types. Product Line TAC INET, TAC Vista Environment Xenta 913 BACnet Vista I/NET Cause The Xenta 913 is only a gateway device and is not native BACnet and thus does not support all BACnet object types. Resolution The BACnet specification outlines 49 different object types. Objects include physical points, processes and even internal operations. Most BACnet devices, including BACnet certified devices, do not support all of the object types since some of the object types are particular to specific industries and several are not commonly used. The Xenta 913 controller supports the following object types: Analog Input Analog Output Analog Value Binary Input Binary Output Binary Value Multi-state Input Multi-state Output Multi-state Value The following BACnet object types are unsupported by the Xenta 913: Access Credential Access Door Access Point Access Rights Access User Access Zone Accumulator Averaging Bit String Value Calendar Character String Value Command Credential Data Input Date Pattern Value Date Value Date Time Pattern Value Date Time Value Device Event Enrollment Event Log File Global Group Group Integer Value Large Analog Value Life Safety Point Life Safety Zone Load Control Loop Network Security Notification Class Octet String Value Positive Integer Value Program Pulse Converter Schedule Structured-View Time Pattern Value Time Value Trend Log Trend Log Multiple           Note that there is some confusion among object types. For example, while it is possible to have a Life Safety point that is a binary output, this is not the same thing as the standard Binary Output object type and the two points are not interoperable.

Issue When attempting to login to the hosted instance, the below error is received indicating that the user is already logged in. Product Line EcoStruxure Access Expert Environment V2 Hosted Instance Cause There are two things that can cause this- A user can only be logged into a single instance at any given time. The user may currently be logged into a different instance. The user did not correctly log out of the instance they are attempting to access, and therefore is still logged in.  Resolution Take the following steps to resolve each of the two causes: Ensure that the user is not logged into any other instances. When closing out the web browser it is necessary to log the user out, as opposed to just closing the web browser. Failure to log out prior to closing the browser will result in this error.

Issue webClient schedules getting error 'request for permission of type' system.security.permissions Product Line Andover Continuum Environment webClient Cause Require to run the Caspol commands. Resolution Run the Caspol commands, here is a batch file that runs these commands without typing them in. Click Here to download the batch file   Rename the caspolwebclient.txt to .bat Run the batch file at each WS that needs to access webclient schedules. Below are the actual commands: The following command will add FullTrust to the Internet_Zone in DotNet 2.0: C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\caspol.exe -m -addgroup Internet_Zone -zone InterNet FullTrust -name FullTrust The following command will add FullTrust to the Trusted_Zone in DotNet 2.0: C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\caspol.exe -m -addgroup Trusted_Zone -zone Trusted FullTrust -name FullTrust This will result in output like: The operation you are performing will alter security policy. Are you sure you want to perform this operation? (yes/no) Then select Y and you should see: Added union code group with "-zone" membership condition to the Machine level. Success In some configurations, you may need to add the IIS computer into Internet Explorer as a trusted site for each browser. Internet Explorer > Internet Options > Security > Click trusted Sites > Click Sites Type in http://yourservername/webclient and click Add (Ex. http://tacweb/webclient) Deselect the checkbox for Require server verification (https:) for all sites in this zone. Click OK and Ok Close Internet Explorer and access webclient See Removal of MS KB2858725 Dot Net 4.5.1 causes issues with Web Servers IIS Functions if this is for 1.94 SP1 - Uninstalling KB2858725 * It may be necessary to give specific permissions in the registry if you are seeing system.permissions.UIPermission, mscorlib Make a backup of the From Windows, Start> Run> Regedt32.exe Expand the hives(folders) to HKEY_CLASSES_ROOT\CLSID\{00B01B2E-B1FE-33A6-AD40-57DE8358DC7D}\InprocServer32\2.0.0.0 Right Click on 2.0.0.0 and select export, name the file and save. (This file can be used to restore the original settings of this branch)  Right click on this folder again and select permissions, select Users and add Full Control See below for snapshots

Issue SmartStruxure integration to StruxureWare Data Center Expert via EcoStruxure WebServices Environment StruxureWare Building Operation EcoStruxure Web Services StruxureWare Data Center Expert 7.2.0 Cause There is a need to have StruxureWare Building Operation pass data to StruxureWare Data Center Expert using EcoStruxure Web Services. StruxureWare Building Operation Web Services is capable of both 'Serve' and 'Consume' functionality. However, StruxureWare Data Center Expert (version 7.2.0) is only capable of Web Services 'Serve' function. Resolution Use Modbus TCP instead of EcoStruxure Web Services if StruxureWare Data Center Expert is required to read from StruxureWare Building Operation. 

  Issue Using active directory with Change Control  feature does not authenticate when signing  Product Line EcoStruxure Building Operation Environment Building Operation release 3.1 and above Building Operation Enterprise Central  Building Operation Enterprise Server Building Operation SmartX Controllers Cause The interaction of Active Directory and Change Control is not clearly defined in the documentation when both are in use.  Although Active Directory within Building Operation Domains can use both the Fully Qualified Domain Name (FQDN) and Netbios Windows Domain names it is recommended that only the Netbios Domain name be used if Change Control is implemented. Refer to EBO Known Issues & Solution topic  Change Control and Windows Active Directory not authenticating - Communities (se.com)  for updates.   Resolution When using Active Directory with Change Control only add the Windows Netbios name to the Building Operation Windows domain name entry:   Using the Full DNS Domain Name (examples include - apa.gad.schneider-electric.com ; pss.apa.local etc.) although these will allow user accounts to log on to servers it currently does not work when used to authenticate change control.    The easiest way to identify which domain name to use is to open WorkStation and refer to the name shown next to:  Log on as:    Secondly when authenticating change control actions with active directory user accounts, irrespective of the Default Building Operation Domain selected, the user account name must be prefixed with the Windows Domain Name 

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

Issue Re-addressing I/A Series BACnet controllers on an existing BACnet MS/TP installation Environment I/A Series R2 BACnet integration to I/A Series Micronet BACnet Controllers Cause There are gaps in BACnet MS/TP addressing which needs to be fixed. Gaps in addressing add delays in communications. Addressing should begin with node 0 (zero) and progress through all nodes, without any gaps, for each separate MS/TP network. Refer to the I/A Series MicroNet BACnet Wiring, Networking, and Best Practices Guide (F-27360-7). Resolution The procedure to change the addresses of the MNB controllers involves the following steps. Changing the physical DIP switch address on the MNB controllers. Making sure the MAC Address of the BACnet shadow device object in the I/A Series R2 UNC reflects the change. Changing the Max Master property in each MNB controller using WorkPlace Pro. Alternatively, you can change the Max Master property using the WorkPlace Commissioning Tool. 1. Changing the physical DIP switch address on the MNB controllers Have a piece of paper ready to note down the physical DIP switch address before and after the change. DIP switch addressing should be sequential starting from ‘0’ with no gaps in between. However, the physical location of the device does not matter. For example, if we have 30 MNB controllers on the BACnet MS/TP network, the addresses should be from 0 to 29 but they do not have to be in order physically. As an example, the first MS/TP device could have an address of '0' while the second MS/TP device on the wire can have an address of '10'. The MNB-1000 should be address ‘0’ if it is the first MS/TP device. If the first MS/TP device is an UNC, the UNC should be address '0' (set in WorkPlace Pro). Use Table–2.3 to calculate the DIP switch value for physical addressing. Take, for example, that the address must be set to 16. To do so, you would set switch number 5 (value=16) to ON. If the address is to be set to 43, instead, you would set switches 1, 2, 4, and 6 to ON (value=1+2+8+32=43). The controller should reset itself about 10 seconds after the change and the new address will be in effect. 2. Check / change the MAC Address of the BACnet shadow device object in the UNC using WorkPlace Pro. After changing the physical DIP switch of the device, we will need to make sure that they change has been reflected in the corresponding BACnet shadow object device in the UNC. Using WorkPlace Pro, open the UNC station. Go to the Properties of the MNB shadow device object and go to the ‘Config’ tab. Make sure that the 'MAC Address' field is showing the new address (in HEX) of the controller. 3. Changing the Max Master property in each MNB controller using WorkPlace Pro. Each MNB controller under a particular BACnet MS/TP trunk needs to have their ‘Max Master’ setting changed. Set ‘Max Master’ to 1 or 2 higher than the highest address on the MS/TP network. If the highest addressed device is DIP switch value 50, set the Max Master to 51 or 52. In WorkPlace Pro, open the UNC station. Go to the Properties of the MNB shadow device object and go to the ‘Engineering’ tab. Change the ‘maxMaster’ to a value that is 2 higher than the highest addresses device. Click ‘Apply’.

Issue Installing and Configuring Email Service Accounts in Niagara G3 Environment Niagara G3 Cause The need for a quick reference guide Resolution The following document can be found at Niagara-Central.com as well.

Issue Uninstall Process for Web Reports Product Line EcoStruxure Building Operation Environment SmartStruxure Web Reports Server StruxureWare for Building Operation Web Reports Server Cause After a re-install of webreports, certain features will not function if the original version was not completely removed. Resolution To uninstall WebReports: In Windows Control Panel, point to Programs and then select Uninstall a Program. Right-click StruxureWare Report Pack Installer and then click Uninstall. Right-click StruxureWare Reporting Agent and then click Uninstall. Right-click StruxureWare Reports Installation and then click Uninstall. Right-click StruxureWare WebReports and then click Uninstall. Right-click StruxureWare WebReports Service and then click Uninstall. In your Web browser, type the URL for SQL Server Reporting Services Report Manager. If you have installed SQL Server 2008 R2 Express, the URL is http://localhost/reports_sqlexpress Click Details View. Select the folders that contain the WebReports reports including Data Sources. Click Delete. Click OK. Click Close. Open Microsoft SQL Server Management Studio (type SQL in the Start menu Search box). Expand the Databases folder. Right-click StruxureWareReportsDB and then click Delete. In the Delete Object window, select StruxureWareReportsDB. Select Close existing connections. Click OK. Open Internet Information Services (IIS) Manager (type IIS in the Start menu Search box). In the Connections pane, expand Sites, expand Default Web Site, and then expand SchneiderElectric. Delete each virtual directory in the specified order: - Right-click WebReportsService and then click Remove. - Right-click WebReports and then click Remove. - Right-click SchneiderElectric and then click Remove. - In the Connections pane, select Application Pools. Right-click SchneiderElectric.WebReportsAppPool and then click Remove. Right-click SchneiderElectric.WebReportsServiceAppPool and then click Remove. Exit Internet Information Services (IIS) Manager. In SQL Server Reporting Services Report Manager (see previous steps), click Folder Settings. Select the NT AUTHORITY\IUSR check box and the [PC NAME] \appuser check box, and then click Delete. Exit SQL Server Reporting Services Report Manager. In Windows Control Panel, select System and Security, then select Administrative Tools. In Computer Management, expand Local Users and Groups and then select Users. Right-click appuser and click Delete, then follow any further prompts to complete the deletion. In Microsoft SQL Server Management Studio, expand Security and then expand Logins. Right-click the appuser account and then click Delete. In the Delete Object window, select appuser. Click OK. Click OK again. Right-click NT AUTHORITY\IUSR and delete it in the same way as you deleted the previous (appuser) account. Right-click [PC NAME] \appuser and delete it in the same way as you deleted the previous (appuser) account. Exit SQL Server Management Studio. In Windows Explorer, expand Program Files (x86) and then expand Schneider Electric. Right-click StruxureWare Reports Installation and then click Delete. Right-click StruxureWareReports and click Delete, then follow any further prompts to complete deletion.

Issue The nvoEffectSetPt is different than the nviSetPoint The nvoEffectSetPt is different than the cooling or heating setpoint (SCPTsetPnts) Product Line EcoStruxure Building Operation, TAC Vista Environment Xenta 102-AX Cause The nvoEffectSetPt is calculated according to nviSetPoint, cooling or heating setpoints (SCPTsetPnts), nviStPointOffset, and thermostat offset. Resolution The nvoEffectSetPt is a SNVT network output in Xenta 102-AX and represents the current effective setpoint that the controller is utilizing in its control loop. nvoEffectSetPt can be configured to display in two different manners: Actual and Normalized. (As defined bynciVAVselctcCntl.oP.ESS (UCPTvavSelection)) Actual nvoEffectSetPt displays the setpoint that corresponds to the currently active application mode of the controller (occupied cooling, unoccupied cooling, standby cooling, occupied heating, unoccupied heating, and standby heating). Normalized nvoEffectSetPt displays the average of the cooling and heating setpoints for the currently active occupancy mode (occupied, unoccupied, standby). NOTE: Whether nvoEffectSetPt is set to Actual or Normalized only affects how the effective setpoint is displayed and does not affect how the application operates. The 102-AX application utilizes the setpoint that corresponds to the currently active mode (occupied cooling setpoint, etc.). In addition, the thermostat adjustment of the setpoint will not appear in any SNVT in Xenta 102-AX controller. This offset is captured in the Xenta 102-AX's memory, and although it is not displayed, it is utilized into the nvoEffectSetPt calculation. Also note that the below scenarios only apply to the occupied and standby modes since the unoccupied setpoints are unaffected by nviStPointOffset, nviSetPoint or by the thermostat offset. Scenario 1: nviSetpoint is unused 1.1 Actual nvoEffectSetPt calculation: In this scenario, the nvoEffectSetPt is the sum of one(1) of the four setpoints (occupied cooling, standby cooling, occupied heating and standby heating) plus the offsets (nviStPointOffset and thermostat offset). 1.2 Normalized nvoEffectSetPt calculation: In this scenario, the nvoEffectSetPt is the average of heating and cooling setpoints ( 1/2(Occupied Cooling Setpoint + Occupied Heating Setpoint) or 1/2(Standby Cooling Setpoint + Standby Heating Setpoint) ) plus the offsets (nviStPointOffset and thermostat offset).   Scenario 2: nviSetpoint is used 2.1 Actual nvoEffectSetPt calculation: In cooling mode, the nvoEffectSetPt is the nviSetPoint plus half of the difference between cooling and heating setpoints ( 1/2(Occupied Cooling Setpoint -Occupied Heating Setpoint) or 1/2(Standby Cooling Setpoint - Standby Heating Setpoint) ),  plus the offsets (nviStPointOffset and thermostat offset). In heating mode, the nvoEffectSetPt is the nviSetPoint minus half of the difference between cooling and heating setpoints ( 1/2(Occupied Cooling Setpoint - Occupied Heating Setpoint) or 1/2(Standby Cooling Setpoint - Standby Heating Setpoint) ), then plus the offsets (nviStPointOffset and thermostat offset). 2.2 Normalized nvoEffectSetPt calculation In this scenario, whether the application is in the cooling mode or the heating mode, the nvoEffectiveSetPt is the sum of the nviSetPoint and the offsets (nviStPointOffset and thermostat Offset). Therefore, when nviSetPoint is used and nvoEffectSetPt is to Normalized, the actual heating and cooling SCPT setpoints do not matter; only the difference between them is significant. For example, setting occupied cooling and heating setpoints to be 75°F (24°C) and 65 °F (18°C) will give the same resulting nvoEffectiveSetPt as setting occupied cooling and heating to be 45°F (7°C) and 35°F (1°C).   Example Occupied Cooling = 72°F (22°C), Occupied Heating = 68°F (20°C), nviSetPoint = 75°F (24°C), assuming the nviStPointOffset and thermostat offset are zero. nvoEffectSetPt in Occupied Cooling or Heating Mode   Scenario 1.1 Scenario 1.2 Scenario 2.1 Scenario 2.2 Cooling Mode 72°F (22°C) 70°F (21°C) 77°F (25°C) 75°F (24°C) Heating Mode 68°F (20°C) 70°F (21°C) 73°F (23°C) 75°F (24°C)

Issue Personnel.csv file fails to import into Continuum No error message is shown Product Line Andover Continuum Environment Continuum access control Keywords: CSV, Import, cardholder, personnel Cause CSV file gets modified by MS excel such that the import fails During the process of manually changing and saving a personnel.csv file within MS excel, a number of commas are added to the first line (corresponding to the number of column fields in the CSV) Resolution Use notepad or similar to delete commas before importing into Continuum as Microsoft Excel does not show up any trailing commas This will NOT import correctly Personnel,,,,, Name,FirstName,LastName,CardNumber,CardType,SiteCode Smith_Fred,Fred,Smith,10,Infinity_37,3701 This will import correctly Personnel Name,FirstName,LastName,CardNumber,CardType,SiteCode Smith_Fred,Fred,Smith,10,Infinity_37,3701 For more information on CSV imports Click Here For an example .csv file for testing Click Here Note: If importing X Driver points using a .csv file the comm port attribute "Port" must always be defined before the X Driver parameters Param1, Param2 etc. The Port must contain the full path e.g. "Network1\CXName\Comm1" Example X Driver Numeric: InfinityNumeric Name,Alias,Format,Description,Port,Param1,Param2,Param3,Param4 XDRPoint1,XDRPoint1,##,First X Driver Point,Network1\CX1\comm4,1,3,10001,1