Building Automation Knowledge Base

Issue Existing SIM-MTECH communicates with a McQuay OPM (Open Protocol Master) and McQuay controllers under it. Can an AS-P replace the SIM-MTECH? Product Line TAC IA Series, EcoStruxure Building Operation Environment I/A Series NW8000 GCM/SIM-MTECH (McQuay OPM) Building Operation Automation Server Premium Cause Replacing obsolete NW8000 GCM/SIM-MTECH with currently supported EBO AS-P Resolution The GCM/SIM-MTECH data base can be converted as a normal GCM through the Transition Tool on the Schenider Electric Exchange TAC I/A Series Transition Portal.  The blocks specifically associated with the OPM integration will not be converted. A third-party hardware device can be used that will allow the AS-P to communicate through the OPM to the McQuay controllers. This will be accomplished by BACNet or Modbus protocol to the AS-P depending on the third parties device selected.  Refer to these 2 documents and websites.  NOTE: These are third party devices and have not been tested or approved by Schneider Electric Product Support. FS-8700-80 McQuay MicroTech Open Protocol Mcquay Gateways

Issue What will happen with the EBO license when used with cloned Virtual Machines in a fail-over scenario to another host? Product Line EcoStruxure Building Operation. Environment Building Operation Enterprise Server Cause Even if the Virtual Machines are "cloned" the licensing will show as "Damaged" Since Virtual Machines don't have unique hardware and the software images can be identical, another identifier called UMN3 (Unique Machine Number 3) is provided by the Virtual Machine. This is, as the name indicates, unique for each Virtual Machine. Without this feature, it could be possible to cheat the licensing system and run many instances of software without a license being purchased for each instance.   See the following technical description of the virtual machine image identifier (VMID) that provides the UMN3   A hash of the universally unique ID (UUID or SMBIOS3) that the hypervisor issues whenever a virtual machine is created or cloned. SMBIOS is commonly virtualized by hypervisor providers such as VMware and Microsoft. In addition, virtualization management systems such as VMware’s VMotion ensure that all virtual machines being managed have a unique SMBIOS value. Resolution If Virtual machines are being utilized to provide a fail-over or "hot swap" of the EBO Server then licenses need to be purchased for each Virtual Machine, just as if two physical computers were used. Each Virtual Machine will require its own License Server installation and have the required licenses activated.

Issue The SmartX server has a "?" under the server name field and shows the error "SSL certificate validation failed!" as the server state in Device Administrator. In some instances, this may cause a failure to upgrade of the SmartX Server displaying these symptoms.  Product Line EcoStruxure Building Operation Environment Building Operation Device Administrator Building Operation Automation Server Premium Building Operation Automation Server Bundled Building Operation Automation Server Cause The SmartX Server is added into Device Administrator over HTTPS 443 but does not have a valid SSL certificate installed. Resolution Change the connection from HTTPS 443 to HTTP 80 This can be done by clicking into the server settings (click on the "?") Select "Edit Connection"   Change the EBO Server Protocol from HTTPS to HTTP  Create a trusted chain between Device Administrator and the problem SmartX Server using a self-signed certificate by following this workflow

Issue Would like to monitor and control points and alarms from an ESMI Fire Detection Panel in EBO. Product Line EcoStruxure Buildning Operation Environment Building Operation Automation Server Premium (AS-P) ESMI Fire Detection Panel Cause The integration between ESMI Fire Detection Panel and EBO enables the user to visualize and operate ESMI Fire detection systems effectively from graphics in EBO. Resolution The interface between the ESMI Fire panels and EcoStruxure Building Operation (EBO) is handled by the AS EN54 FIRE SmartDriver. The event and command information is sent/received by the Fire panel using RS-485 communication to/from the AS-P using the SmartDriver.   This resolution is in three steps: Enable communication via RS485 (INFO protocol in Fire panel) Use the AS EN 54 Fire Configurator to create the layout for EBO Install/configure the SmartDriver and create the Fire graphics in the AS-P   Step 1 - Enable communication via RS485 (INFO protocol in Fire panel) This video shows how to enable communication from an ESMI Fire panel and an AS-P over RS485. This is a prerequisite for using the Fire SmartDriver in the AS-P.     Step 2 - Use the AS EN 54 Fire Configurator to create the layout for EBO This video will give you a quick introduction to the AS EN54 Fire Configurator. The AS EN54 Fire Configurator is a Windows application that imports floor plans and configuration files to create the EBO interface, devices, points, alarms and graphics.     Step 3 - Install/configure the SmartDriver and create the Fire graphics in the AS-P This video shows how to connect an EBO SmartX Server to an Esmi Sense Fire detection panel (FDP). And how to create and edit the Fire graphics in the EBO SmartX Server, The fire graphics provide the user interface to visualize and operate Esmi Fire detection systems.  

Issue What are the rules governing the BACnet device Instance ID in EBO and how to change it if required. Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Automation Server (all) SmartX IP Controllers BACnet Cause The BACnet device Instance ID must be unique within a BACnet  system. There may be a need to find out or change the device Instance ID to ensure there are not duplicates.  Resolution When a BACnet Interface is added to an SmartX server, AS or ES , the Server will become a BACnet device and it will have an Instance ID (automatically generated or manually assigned).  To check an ES or AS BACnet device instance ID go to the properties of the BACnet Interface and then the Advanced tab. The device instance ID is defined as the Object ID. To check other  BACnet device, SmartX controller or 3rd party BACnet device, go to the properties of the BACnet Device and then the Advanced tab. The device instance ID once again is defined as the Object ID.  No 2 BACnet devices in any system may have the same Instance ID/Object ID. The valid range of Instance Numbers for a BACnet device is 0 to 4194302.   Change BACnet Device ID: You can change BACnet device IDs for SmartX Server or Controller when there is a conflict with another BACnet device, move controller or in those situations where you need to change the originally selected value for some local or site-specific reason. In EBO V3.2.3 or higher (except V3.3), it is possible to change BACnet Device ID of an SmartX server (ES, AS-P or AS-B), as explained in: Changing the BACnet Device ID in a SmartX Server To change SmartX IP Controller BACnet device ID, follow: Changing a BACnet/IP Device ID

Issue Need to manage car park usage based on the company associated with each vehicle. Product Line EcoStruxure Security Expert Environment Security Expert Controller (SP-C) Cause Area counting can be configured to count the users with a defined access level who are present in the area. In a shared car parking application, this can be used to limit the number of parking slots assigned for each company. Resolution The below steps are based on AN 278 Security Expert - Access Level Area Counting - Integration Guide Navigate to Users | Access Level and create an access level for each company and take note of the database ID for each access level.   Navigate to Automation | Data Values and create the following data values for each company: Counter data value: This will be used to store the current car count for each company, take note of the database ID for Counter data value.   Setpoint data value: This will allow the operator to define the maxim number of parking areas assigned for each company. Ensure that the Preset Power Up and Preset Value options are selected.   Assign these data values to variables, which allow data values to be monitored via a floor plan or status page. Navigate to Automation |Variables and create one variable for each Data Value record.  Enable area counting:  Navigate to Programming | Areas and select the relevant area to enable area counting in.  Select the Options 1 tab.  In the Reporting Options section, enable the Enable User Counting option.  Click Save. Set The Max User Count to define the maximum number of users that the system will allow to occupy an area. Navigate to Programming | Areas and select the area to configure. Select the Configuration tab. In the Setup section, enter the maximum area occupancy in the Max User Count field. Click Save. Important: The Max User Count cannot be left at zero for area counting. If occupancy restriction is not required, an unrealistically high value should be set to implement area counting without restricting access. The CountOnAccess function needs to be defined for the parking area, using the counter data values that will record the count and the access levels that will determine which users will be counted. Navigate to Programming | Areas and select the area to be configured. Select the Configuration tab. Scroll down and enter the following command into the Commands field: CountOnAccess=W[X,Y,Z]where:  W refers to the Database ID of the relevant Counter data value and,  X, Y, Z refer to the Database IDs of the included access levels Up to 16 comma-separated access levels can be included in each command. Up to four commands can be applied to each area. Each command must begin on a new line. Virtual outputs are required for the system to be used on the programmable functions. The number of virtual outputs depends on the number of companies.  Navigate Expanders | Output Expanders and add a new output expander (16 outputs). Ensure that the Virtual Module option is selected and the module address is set to a high number (e.g. 32). Navigate to Programming | Outputs and assign appropriate names to the new virtual outputs, as below screenshot.  One programmable function for each company is required to compare the current car count with a setpoint.  Navigate to Automation | Programmable Functions and create one function for each company with the following settings; Type: Value Compare. Out to Enable This Function: Function Enable. Activate Output when Below Set Point: Company X Under the Limit. Analog Input Data Variable Register: Company X Data counter. Set Point Data Value: Company X Data Setpoint. Where X is the company number. One Schedule is required for each company to enable or disable access based on programmable function output. Navigate to Sites | Schedules and create one Schedule for each company that is valid at all times (i.e. from 00:00 to 00:00, for all days of the week and ignoring holidays). Select the Options tab and select a Qualify Output: the schedule should be valid when the Company X under the limit output is On.  Navigate to Users | Access Levels, in the Configuration tab of each company access level assign the relevant schedule in the Operating Schedule field, or in the Doors tab you can apply the Schedule to specific doors, ex. park gate. Create Status Page or Floor Plan to monitor the system. In the below example, the user from the company will not be allowed access because his company has used all assigned parking slots.   

Issue Could not start the TAC Xenta 102-AX LonWorks PlugIn, due to an Error message. Product Line EcoStruxure Building Operation. Environment EcoStruxure Building Operation Workstation. TAC Xenta 102 AX Cause EcoStruxure Building Operation does not support online PlugIns, as LNS is running in the background, without any communication port.. If selecting to Synchronize (Upload or Download) you will get an error message. Resolution Select "Skip" synchronize.

Issue While using a demo license, the system is unable to connect to the Building Advisor Cloud Product Line EcoStruxure Building Advisor Environment Building Operation Enterprise Central 3.0 or later Building Operation Enterprise Server 3.0 or later Building Operation Automation Server Premium 3.0 or later Building Operation Building Advisor Portal Cause The Demo License of EBO does not contain the Cloud Connectivity feature. If the original system was registered in 2.0 and running on a demo license, once it is upgraded to 3.0 the Cloud connectivity will be lost. Resolution Enterprise Server and Enterprise Central Customers using an Enterprise Server or Enterprise Central must install a valid license to connect to the Building Adviser Cloud.   AS-P and AS-B Cloud Connectivity is only supported in versions 3.0.x or later. When running in a Stand-Alone configuration, the AS-P and AS-B do not require a separate license for Cloud Connectivity.

Issue Having trouble configurating EcoStruxure Building Operation to connect to the Building Advisor Portal. Product Line EcoStruxure Building Advisor Environment Building Operation Automation Server Premium Building Operation Enterprise Central Building Operation Enterprise Server Building Operation Building Advisor Portal Cause There are multiple server configurations that you can have to connect to the Building Advisor Portal Resolution The following are the most common configurations.   Stand-alone AS-P and AS-B SmartX servers  REQUIREMENTS: EBO version 3.0 or higher. Automation Servers with EBO 2.x do not support the Cloud Connectivity feature. Servers are connected directly to the EBO cloud provided these servers are running    ES/AS configuration REQUIREMENTS: EBO version 2.0 or higher. The ES is responsible for the communication and data transfer with the Building Advisor cloud on behalf of the downstream SmartX servers and requires    EC/ES/AS configuration,  REQUIREMENTS: Each server requires EBO version 2.0 or above. The EC is responsible for communication and data transfer with the Building Advisor cloud only for itself.  Cloud-connect settings only are needed on EC & get cloned to each ES.  Each ES is responsible for communication and data transfer with the Building Advisor cloud for itself and the downstream SmartX servers. 

Issue The site is having cloud connectivity issues and R&D requires the trace log to see the communication. The trace logging for the cloud plugin (/System/Modules/Trace/Loggers/nsp/nsp.pin/nsp.pin.Cloud) has been enabled and set to Trace, and there are no records of nsp.pin.Cloud referenced within the trace log. Product Line EcoStruxure Building Advisor, EcoStruxure Building Operation Environment EcoStruxure Building Advisor Building Operation Automation Server Premium v3.0.x or later Cause By default, the cloud plugin does not report on the trace log. Enabling trace log reporting for  nsp.pin.Cloud  is a high-level procedure that requires Product Supports intervention. Resolution Please contact PSS to help resolve this issue

Issue The Sigma Client reports a "HTTP connection failed" error" when an attempt is made to start it. Product Line Satchwell Sigma Environment Satchwell Sigma release 4.05 and later Cause When the Sigma Client is started, attempts are made to make a connection to the Sigma Server, this connection fails and the Client cannot be started. Resolution There are a number of reasons why this error might occur, suggestions are listed below. 1.  Windows XP operating system - ensure that service pack 3 has been installed, and that all the Windows updates have been applied. 2. Windows 7 operating system - only Ultimate and Professional are supported. 3. Sigma Client/Server software must be installed by a Windows user with "Admin" privileges. 4. Windows Firewall must either have been switched off, or has "Exceptions" configured as explained in the Sigma 4.05 SP1 release note. 5. Check that the "SigmaSVR" service has been started. If this service cannot be seen, then this is an indication that the Sigma software has not been install by an "Admin" user, and the software must be reinstalled. 6. Corruption of the Windows "User" files has taken place. Create a new Windows user with "Admin" privileges. Log on to Windows as the new user and test the Sigma Client again. 7. If using a VMware image try rebooting the image. 8. SMART is being used and has a modem connected to the PC for uploading data. Ensure that the modem is fully functional. If not, the HTTP error can be caused. This was seen at Sigma: R4   Release 3.44.14. and Smart Task Manager  3.0.2.20. Added 26-07-2012 9. This may be because a proxy server is being used, eg on school networks. Log on to your PC computer with an administrator account. Open the "Start" menu and click on "Control Panel." Double-click on the icon labeled "Internet Options." Go to the "Connections" tab at the top of the window and then click on "LAN Settings." Make sure the box next to "Bypass proxy server for local addresses" is checked. Hit "OK" twice to confirm the new proxy port settings. Make sure the box next to "Bypass proxy server for local addresses" is checked. Hit "OK" twice to confirm the new proxy port settings. Added 25-09-2012. 10. This issue was reported from a School where Sigma 4.05 SP1 had been operating correctly for several weeks. The issue was traced to the Anti-virus software Sophos, which had received an update prior to the failure. Sophos had quarantined two Sigma dll files. To correct this issue both Sophos and Sigma were uninstalled. A later version of Sophos was installed, and then Sigma was reinstalled, this corrected the problem. Added 01-08-2013 11 - Sigma software installed when connected to a wireless network. The Sigma client will only connect to the server when the wireless connection is made. Uninstall Sigma, disable the wireless, enable the network card, and then reinstall the Sigma software. Added 03-10-2013 12. DELL PC, with firewalls and antivirus disabled and no wireless card fitted. There may be a service or an application running in the background as part of the vendors Windows platform makeup.Restore the same version of Windows, but without (where possible) any of the Vendors applications. Re-install Sigma. Added 16-05-2014 13. Check the port number in c:\sigma\bin\setupsvr.exe, the default is 8080. Added 19-05-2014 14. Flexera license software has been reported as a cause for receiving this error. Flexera license software uses port 8080, (IMADMIN.EXE). Stop Flexera and retry Sigma. Changing Sigma from port 8080 to 8081 could also provide a solution. Added 27-08-2014 15. The SBO PCS (StruxureWare Building Operation Project Configuration Server) also uses port 8080.This needs to be stopped or will conflict with Sigma and produce the HTTP error. Added 02-09-2014 16. Make sure any data is backed up from the installed Sigma system. Uninstall Sigma using Add/remove programs (Win XP) or Programs and features (Win 7). Wait for the Sigma un-install process has completely finish. Delete or rename the C:\Sigma folder to.......for example Sigma1. Re-install Sigma by using a right mouse click on the "SigmaSetup.exe" file and select  A new clean Sigma folder will be created during the install. Once completed reboot the computer. Check the SIgma server is running and run up SIgma. Added 01-10-22014 17. The HTTP error can also caused if the computer name contains extended ASCII or Unicode. For example a computer named "P á st" may fail, if the computer name is changed to "Past" this may correct the HTTP problem. Added 23-11-2021 18. On SE laptops, the McAfee firewall has been updated: Go to McAfee (under hidden icons) > right click 'Quick Settings' > 'Enable Firewall Timed Groups'. This will provide a 1 hour window to run Sigma, in the McAfee pop up window. add a reason e.g. Sigma.

Issue How to change the IP address of the Automation Server and ensure proper communication. Product Line EcoStruxure Building Operation Environment Enterprise Server Automation Server Building Operation Device Administrator Building Operation Workstation Cause At times the IP address information for an Automation Server must be changed after being added to an Enterprise Server to accommodate changes in IP network design, correction of incorrect data, or any other reason. Changing the IP address needs to be done in the proper method to avoid artifacts and confusion after the change. Resolution To avoid complications, follow this process to modify the IP address of an Automation Server that is already communicating with an Enterprise Server. In the Building Operation Device Administrator connect the AS controller via USB or IP.  WebHelp Topic Connect to SmartX Servers Right-click on the AS and select Network Settings Modify the IP address settings to the new values Additionally, this can be changed through PuTTY with the "setip" command. Power Cycle the Automation Server (If a power cycle is not completed the AS will still have invalid data for network settings despite the physical network interface running with the new settings) Start Building Operation Workstation and log in to the Enterprise Server Select the Enterprise Server and open the Communication Tab Highlight the Automation Server that needs to be changed and modify the address field for the IP address of the device. (The Communications settings tab is enabled by selecting the Show/Hide tick icon). Click the Save button The Enterprise Server should now automatically establish communication with the AS, but if you want to speed this process you can right-click the Enterprise Server and select the "Advanced\Repair Server Communication" option. IMPORTANT: As of 1.41 if the IP address is changed on a server that is configured with a BACnet interface, the IP address and possibly the broadcast address of the IP Network under the BACnet interface must be updated manually. (see below)

Issue Checking operation of CSC. Product Line Field Devices Environment CSC5252 CSC5352 Cause The operation of the CSC compensator explanation. Resolution The operation of a compensator is to adjust the system flow temperature, in relation to changes in the outside air temperature. The system flow temperature can be further adjusted by the addition of a room temperature sensor, which will provide room influence. The CSC 5252/5352 controller is programmed with a complete set of "Default" settings, these settings will allow the controller to operate as soon as its powered up. Although the controller has a complete range of adjustable settings, accessed through the "Fine Tune Mode", for a basic installation the "Quick Set Mode" can be used. The screen shot below explains how to enter the Quick Set Mode and the settings available. Controller data sheet Controller User guide   Compensated Flow Temperature Set-point: The compensated flow temperature set-point is automatically adjusted based on a ratio for set-point adjustments against the outside temperature changes. A consistent ratio across the entire outside temperature range, may not provide suitable control. For example: with radiator type systems, radiators are less efficient at lower water flow temperatures and need to be provided with a higher temperature to compensate for this initially. The “Set compensator ratio 1”and the “Set Ratio 2” settings provide the ratio of the change to the flow temperature set-point for changes in the outside air temperature, the ratio used is based on the “Set Change-over Value”, with the compensated slope starting from the “Set Flow Origin”. The “Set Flow Temperature Set-up Value” and “Set Night Set Back Value” provide a constant adjustment of the flow temperature set-point to a given building control requirement. The default settings would give a resultant flow temperature as shown follows:     The CSC5352 Calculator presents these settings in a graphical and listed format, making it easier to visually confirm the effects any changes to these settings would make.    

Issue In EBO there is no build in way to view b3 array element value. In Continuum there is a command line that allows printing array elements by specifying the array index. Product Line EcoStruxure Building Operation Environment Building Operation ASP, ASB, AS b3 BACnet devices Infinet i2 device Cause The Infinet i2 device object array values can be viewed as WebHelp. This option is not available with b3 BACnet controllers. Resolution A workaround is to use a Script program to expose the array element value. See Sample Script Program to expose b3 array element value.

Issue When adding Server Packages to a new PCT install, the installation process does not complete.    Product Line Project Configuration Tool Environment Building Operation Project Configuration Tool (PCT) Cause Some security policy is interfering with the PCT installation process. The VirtualBoxDisclamer.log shows the following error     Could not add PCTService to BUILTIN\Administrators.   The lack of the PCTService could be responsible for a range of issues including the failure to install Server Packages. Resolution To learn what is preventing the creation of the PCTService, try manually adding the user to the Administrators group to see what errors might be presented.  Open Windows event log and look for errors that occurred during the same timeframe noted above. 

Issue Poor communications between AS-P and Deep Sea Electronics (DSE) generator and switchgear modbus RTU slaves. Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Premium (AS-P) Cause When upgrading from an AS to AS-P, poor Modbus communication is seen between the AS-P and DSE slave device. The communications when using the AS was seen to be good. Using an AS-P, poor communication is seen between the AS-P and the DSE slave device. Resolution Firstly, on the AS-P, ensure the release is v3.2.3.8000 to improve the modbus RTU polling. Then if the issue still persists, make the adjustments to the DSE device as below. If the AS-P cannot be taken to v3.2.3.8000 then continue with the adjustments to the DSE device.   On the DSE Modbus slave, there are additional parameters as well as the baud rate, parity and stop bits. Access to these parameters is by using the DSE software tool. The additional parameter is the Inter-Frame delay. Change the Inter-Frame delay from 0ms to 1ms.

Issue It is not possible to select a "Trend 10K3A1" Thermistor when configuring a central or onboard IO input point. Product Line EcoStruxure Building Operation Environment Building Operation WorkStation Building Operation Automation Server (AS-P) Central IO Building operation Automation Server Bundled (AS-B) Onboard IO Cause The specific thermistor type is not available to be selected. Resolution Configure an input as a resistive Input with reliability level, electrical scale and engineering scale set to: Upper/Top: 0 Lower/Bottom: 587628 Then use a Function Block 10K3A1-Ohm-To-C sample  program or Script program to convert from resistance to °C. NOTE Satchwell and Trend both use 10k3A1 Thermistors but the shunt resistance used within it will vary.

Issue Unable to connect Enterprise Server or Enterprise Central to the Building Advisor Cloud Portal  Product Line EcoStruxure Building Advisor, EcoStruxure Building Operation Environment Building Operation Building Advisor Portal Building Operation Enterprise Server Building Operation Enterprise Central Cause There are some Operating System Requirements that need to be checked and enforced. Resolution Incompatible versions lead to missing trust certificates that could hinder the connection to Azure cloud services.  The table below provides a compatibility matrix of EBO versions and supported Windows OS that is necessary for the cloud-connectivity to work reliably.         The SmartX servers also require TLS1.2 to be enabled to communicate with the BA cloud properly. Automation servers (AS-P/AS-B) have TLS1.2 enabled by default. Check that the Windows OS running Enterprise Server has TLS1.2 is enabled by following the steps in this link: How to Check if TLS1.2 is Enabled  

Issue What alternative are available for accessing Continuum WebClient from browsers other than Internet Explorer? Product Line Andover Continuum Environment Continuum WebClient Server Cause While Internet Explorer is the only officially supported browser for Continuum WebClient, Microsoft has announced that support for Internet Explorer will end in June 2022.   When accessing WebClient sites using Microsoft Edge in Internet Explorer mode. WebClient server returns an error, indicating that Internet Explorer is needed to access WebClient. Resolution It is possible to access WebClient using Microsoft Edge in Internet Explorer Mode   The method of specifying Internet Explorer Mode for a site’s webClient URL will depend on how the customer treats the configuration of Edge – either settings at the individual Edge level or via group policy settings.

Issue Creating an Extended Trend Log for b3 (Infinet) Point and Value Logs Product Line EcoStruxure Building Operation Environment b3 BACnet Controller Infinet Controller Building Operation Automation Server, AS, ASP, ASB Cause Using an extended trend log to store log records for long periods of time. The extended trend log is often saved on a higher-level server with more storage capacity. This extra storage capacity enables the server to store more records before overwriting the old ones. For more information, see WebHelp. Configure extended trend logs for b3 BACnet and Infinet devices the same way as configuring extended trend logs in other Building Operation devices. There is one difference, however. do not use smart logs when configuring extended trend logs in b3 BACnet devices. Instead of using smart logs, use the Maximum Transfer Interval property to specify the transfer interval. Resolution In Listview, select the b3/Infinet Object (point or value), click Properties/Advanced Multiply the "Log records" by the "Log interval" to calculate the maximum transfer interval. The "maximum transfer interval" is the frequency at which the extended trend log will transfer log records from the b3/Infinet Object before any entries in the b3/Infinet controller log are overwritten Right click the object, choose New then "Extended Trend Log" In the Create Object box, set Smart Log to False, Set the "Maximum transfer interval" to less than that calculated above (2) Click Create