Building Automation Knowledge Base

Warning Potential for Data Loss: The steps detailed in the resolution of this article may result in a loss of critical data if not performed properly. Before beginning these steps, make sure all important data is backed up in the event of data loss. If you are unsure or unfamiliar with any complex steps detailed in this article, please contact Product Support for assistance. Issue Need to backup or share the project with another user. Product Line EcoStruxure Building Operation Environment Building Operation Project Configuration Tool (PCT)  Cause One way of sharing a project is to move it and another way is to Export the project. Resolution Move the project Stop all servers in each project and stop all projects. Close PCT application. Copy the “projects” folder from the PCT storage location and paste it to another storage location (suggested by WebHelp topic Move a Project) OR backup all servers through Workstation. Default PCT Project Folder Locations Versions prior to PCT 1.2 C:\ProgramData\Schneider Electric StruxureWare\Building Operation\Project Configuration Tool\storagemodule\projects PCT 1.2 or higher C:\ProgramData\Schneider Electric EcoStruxure\Building Operation\Project Configuration Tool\storagemodule\projects Default PCT Template Folder Locations Versions prior to PCT 1.2 C:\ProgramData\Schneider Electric StruxureWare\Building Operation\Project Configuration Tool\templates PCT 1.2 or higher C:\ProgramData\Schneider Electric EcoStruxure\Building Operation\Project Configuration Tool\templates   Export the project In Project Configuration Tool, in the Project view, select the project you want to export. On the Header toolbar, click the Export project button or right-click on the project and select "Export". On the Export selected project(s) dialog box, in the Folder box, browse to the folder on your hard drive where you want to save the exported project. Click OK. TIP: You can select multiple projects and export all of them at once. Note: In order to be more future proof, there is a new export/import format of PCT projects starting in PCT v1.3.2 with exports having an extension of '.pct_export'.  Projects exported at an earlier version have an extension of '.ppb' and they must be converted to '.pct_export' files before import into PCT v1.3.2.    Please refer to point 2.1 in the release notes.   Also prior to PCT v1.3.2 the project had to be stopped before export was possible.  In PCT v1.3.2 the project has to be running before it can be exported.    

Issue How to add b3 devices to EcoStruxure. Product Line EcoStruxure Building Operation Environment Building Operation Workstation b3 BACnet Cause List the methods of adding b3 devices to EcoStruxure Building Operation Resolution The following information can be found in the EcoStruxure Building Operation - Technical Reference Guide. Use the guide relevant to the release of EBO installed.   Discovering b3 BACnet Devices with the Device Discovery View Using the Device Discovery view to search deployed Automation Servers for b3 BACnet devices. For more information, see section "b3 BACnet Device Overview". To discover b3 BACnet devices with the Device Discovery view In WorkStation, click the Device Discovery view. In the System Tree pane, click the Automation Server to be searched. In Select device type, click on BACnet devices. Select the b3 BACnet device you want in the Device result pane. Map a device by dragging that device from the Device result area and dropping it in the System Tree pane. When prompted, copy the device only or copy the device and all of its children.   Learning b3 BACnet Devices b3 BACnet devices van be learned and to automatically assign the node IDs and initiate communication with devices on the MS/TP network. Tip: It is possible to learn b3 devices when the b3 devices and the Automation Server functioning as the BACnet interface are connected and online. If the b3 devices are not physically connected to the network, it is also possible to manually create and configure the devices offline in Workstation. For more information, see section  "b3 BACnet Devices. To learn b3 BACnet devices In WorkStation, in the System Tree pane, select the MSTP Network In WorkStation, on the Actions menu, click b3 devices and Learn When the b3 BACnet devices are learned, click Close If necessary, perform a download operation to eliminate any old points and programs stored on the b3 BACnet device.

Issue Unable to gain access to Building Expert Product Line EcoStruxure Building Expert Environment SmartStruxure Lite Multi Purpose Manager MPM-GW MPM-UN MPM-VA Cause The admin password has been changed and the user has lost the password Resolution For MPM with firmware 2.14 and earlier: Send the MPM 'default.db' file to Product Support.  From a web browser, you can save the default.db file to the local drive by typing the address http://[ip_address]/root/default.db (replace [ip_address] with the actual IP address of the MPM, or 10.50.80.2 if bootloader is used) For MPM with firmware 2.15 and later: Send the MPM Node ID or MAC Address to Product Support. Refer to the document StruxureWare Building Expert Password Recovery When Accessing MPM - Reference Guide for the procedure to obtain the MPM Node ID or MAC Address.

Issue On a SmartStruxure workstation PC how can the Menta communication port be changed. Environment SmartStruxure 1.5 Cause The Menta setup application is not added in the start menu. This exe is located in the StruxureWare install files and can be run to change the communication port for a direct RS232 connection This file is located in the following directories 64bit systems C:\Program Files (X86)\Schneider Electric StruxureWare\Buildings Operation 1.5\Workstation\Menta Setup.exe 32 bit system C:\Program Files\Schneider Electric StruxureWare\Buildings Operation 1.5\Workstation\Menta Setup.exe Resolution Run the Menta Setup.exe and add the communication port that Menta will use. For the first time the other settings must be entered as detailed in this image.

Issue WebClient Pre-Installation Requirements for Server 2016 are not included in the 2.03 webClient installation guide Product Line Andover Continuum Environment Windows Server 2016 Continuum webClient Server 2.03 Cause The Pre-Installation requirement steps provided in the webClient planning and installation guide do not show all the steps needed to install webClient successfully Resolution This material is intended as a supplement to the webClient Planning and Installation Guide   Installing IIS on Windows Server 2016 For Windows Server 2016, install IIS on the designated web.Client application server (LAN systems) or the standalone CyberStation/web.Client workstation (standalone system). 1. Start the Server Manager by clicking on the Administrative Tools menu. 2. In the Server Manager, click Add Roles and Features. 3. In the Add Roles and Features Wizard, Before You Begin tab, click Next. 4. In Installation Type, select Role-based or feature-based installation. 5. Click Next and then select a server or virtual hard disk on which to install roles and features. 6. In Server Selection, click Select a server from the server pool. 7. Click Next and select one or more roles to install on the selected server. 8. In Select Server Roles, please select the items from the following snapshots carefully Note: In previous Windows Server instructions from the webClient pre-installation guide, a reference was made to select Application Server. This option is selected and installed by default in Windows Server 2016. No selection for Application Server is offered.   Once these Pre-Installation steps have been performed the webClient Server is ready for Chapter 4 - Installing web.client on the IIS PC (Found in the webClient planning and installation guide.pdf)

Issue TGML Graphic worked without error in EcoStruxure Building Operation 2.0 WebStation. After an upgrade to 3.0, WebStation displays one of the following errors on page load: Script error in DocumentLoadEvent (Component_Name) Refused to evaluate a string as JavaScript because 'unsafe-eval' is not an allowed source of script in the following Content Security Policy directive: "script-src 'self' blob: 'unsafe-inline'". Do you want to continue running this script? This site says... Script error in DocumentLoadEvent (Component_Name) Blocked by Content Security Policy Do you want to continue running this script? Script error in DocumentLoadEvent (Component_Name) call to eval() blocked by CSP Do you want to continue running this script? Product Line EcoStruxure Building Operation Environment Building Operation 3.0 TGML Graphics Cause A new security setting in 3.0 disallows eval() statements by default in TGML JavaScripts presented in WebStation. An eval() statement executes a string of characters as code, which can open security vulnerabilities if enabled, something akin to a SQL injection or cross-site scripting attack. If graphics were created in earlier versions and relied on eval() to execute dynamic code, the user will be notified upon opening the graphic in 3.0 WebStation. Resolution Any graphics relying on eval() to execute dynamic code should have their JavaScript functions rewritten to avoid use of eval(). This is the preferred approach with respect to cyber-security. Work-Around It is possible, but not recommended, to disable the new security check in WebStation TGML graphics. Within WorkStation open the Control Panel Go to Security Settings Check the box for "Enable WebStation to use unsafe string evaluated JavaScript methods like 'eval' For more information, see Web Help article: Enabling WebStation to Use Unsafe JavaScript Methods. For the latest solution to this issue please refer to: Cannot Open Graphics in WebStation 

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 In an MP-V controller, Box flow is reading air flow when the VAV damper is closed Product Line EcoStruxure Building Operation Environment Building Operation Multi-purpose VAV FW v2.00.01.00016 Building Operation Workstation (Version 2.0.x or later) Cause Confinguring the MP-V Box Flow Zero Point WebHelp article in Building Management System WebHelp is missing steps needed for MP-V with firmware version 2.00.01.00016. Resolution In addition to the procedure described in Configuring the MP-V Box Flow Zero Point, two additional steps are required to zero the Box flow on an MP-V using firmware version 2.00.01.00016. Under Flow Balance Data... The Box Measured maximum flow must be an appropriate value based on the box size.  The Hood Measured maximum flow must be an appropriate value based on the box size. Once the procedure in WebHelp is followed and these to settings are configured, the Box Flow will read zero when the Velocity Pressure is below the Minimum value setting in Velocity Pressure properties.   If the Box Flow is still a non-zero value: While the damper is closed, put in an offset value to counter the Box Flow Make sure that the minimum value setting is a small positive value ex/ 0.002

Issue TimescaleDB Installation Errors - ERROR: could not get 'pg_config --pkglibdir' : exec: "pg_config": executable file not found in %PATH% - ERROR: could not get 'pg_config --pkglindir' : exit status 1 Product Line EcoStruxure Building Operation Environment EcoStruxure Building Operation 3.x External Log Storage TimescaleDB (third party)  Cause Missing environment variable paths in Windows is detailed in section 9.4.4 PostgreSQL and TimescaleDB Installation in the EcoStruxure Building Operation 3.0.1 Release Notes. Assistance in how to add these variables is described below. Resolution Using the EBO External Log Storage Installer tool available on the Community, there is no need to make any manual configuration, as the tool executes the installation without the need for e.g. environment variables. Alternatively, you can manually set these as detailed below: You can either view a video showing how it is done:  or follow the instruction below view, add and modify the environment variables from the Control Panel as follows:  In the Control Panel select System and Security Select System Select Advanced system settings Select Environment Variables. In System variables, highlight Path and click Edit. For the error - ERROR: could not get 'pg_config --pkglibdir' : exec: "pg_config": executable file not found in %PATH% Add the New path 'C:\Program Files\PostgreSQL\11\bin' to the environment variable. For the error -ERROR: could not get 'pg_config --pkglindir' : exit status 1 Add the New path 'C:\Program Files\PostgreSQL\11\lib' to the environment variable. You should see something similar to the following after TimescaleDB has been successfully installed.

Issue When browsing back and forth between Floor Plans the background image is not showing. This appears to be random with some background images showing up correctly with others not displaying the image. Product Line EcoStruxure Security Expert Environment Security Expert Client Security Expert Floor Plans Cause The Floor Plan background image sizes are too large. These must be close to the Width and Height size of the background canvas so that fewer resources are needed during image resizing. For example, where background images are approximately 9921x7016 pixels and been displayed on a canvas sized 1587x1122 will most likely display this issue. Resolution Use image editing software, such as Microsoft Paint, to resize and save the background images to a size closer to the Floor Plans canvas Width and Height. Floor Plan Canvas Size In the above example, the images were resized to 1920x1358 (maintaining the aspect ratio) which was much closer to the canvas size resulting in fewer resources being required to resize the images when viewing Floor Plans.

Issue Configuring Security Expert Readers Product Line EcoStruxure Security Expert Environment Security Expert Smart Card Readers Cause Security Expert Smart Card Readers have options such as Mifare Reading Mode, LED colors, etc. that can be configured. How the readers are configured will depend on the reader's firmware. Resolution The method used to configure a Security Expert Smart Card Reader depends on the firmware version it is using. There is no way to visually determine the firmware version. To identify what firmware the reader was shipped with from the factory refer to Knowledge Base article Identifying Security Expert Smart Card Readers Firmware. 1. Smart Card Readers with firmware below build 200 - (I.e. 1.04.64) These are older readers which were configured with a serial terminal program by connecting to the reader using a USB-RS485 converter. Please refer to the 'Installer Programming' section of the attached Smart Card Reader Installation Manual - Feb 2017. This has been replaced by a newer version of the manual on Exchange which no longer includes this information. 2. Smart Card Readers with firmware build 200 or above (I.e. 1.04.229) These newer readers do not have a serial interface and will require a configuration card to change reader options. The configuration card (SX-ISO-CONFIG) is ordered from Schneider Electric, see the Security Expert Credentials Order Form for details.

Issue Application Director output window and LON proxy point indicates fault: java.lang.ClassCastException: javax.baja.sys.BDouble ERROR [14:56:22 20-Aug-14 EDT][lon1] Could not decode nv update data Misc9:nvoSpaceTemp java.lang.ClassCastException: javax.baja.sys.BDouble    at javax.baja.lonworks.londata.LonFacetsUtil.makeLonQualifiers(LonFacetsUtil.java)    at javax.baja.lonworks.londata.LonFacetsUtil.getQualifiers(LonFacetsUtil.java)    at javax.baja.lonworks.londata.BLonData.primitiveFromInputStream(BLonData.java)    at javax.baja.lonworks.londata.BLonData.fromInputStream(BLonData.java)    at javax.baja.lonworks.londata.BLonData.fromNetBytes(BLonData.java)    at javax.baja.lonworks.BNetworkVariable.receiveUpdate(BNetworkVariable.java)    at com.tridium.lonworks.NvManager.receiveLonMessage(NvManager.java)    at com.tridium.lonworks.loncomm.NLonComm.routeToNvListener(NLonComm.java)    at com.tridium.lonworks.loncomm.NLonComm.receiveLonMessage(NLonComm.java)    at com.tridium.lonworks.loncomm.NLonLinkLayer$AppBufferReceive.run(NLonLinkLayer.java)    at java.lang.Thread.run(Unknown Source) Environment I/A Series G3 (all versions) Cause This error is related to a mismatch between the lonworks module running on the ENC/JACE versus the version being used within the Workbench modules folder.  A different version of Workbench and/or lonworks module is being used to engineer the ENC/JACE. Resolution Review the versions between the Workbench and ENC/JACE and match the versions.

Issue When deploying Automation Server or Enterprise Server from Workstation for Projects under PCS, it will fail. The error shown in the Progress view window is "The live server is not empty." Product Line EcoStruxure Building Operation Environment SmartStruxure Project Configuration Server Workstation for Projects Enterprise Server (ES) Automation Server (AS) Cause A project can only be deployed to a server when the server has an empty database and not has been part of a multi-server system. A server is considered empty when it does not contain any user-created objects, such as programs and graphics. Resolution The server database can be emptied in different ways depending on if it is an Automation Server or an Enterprise Server: Reinstall the Enterprise Server. Upgrade the Automation Server with a new database. For more detail about how to deploy AS or ES, refer to Offline Engineering with Project Configuration Server (PCS).

Issue Collecting String data from third party BACnet systems where they do not support BACnet String Objects Product Line EcoStruxure Building Operation Environment Third Party BACnet systems Continuum Text/Strings Datetime Cause BACnet String and Date (characterstring-value and datetime-value) objects are not included in some BACnet systems eg. Continuum. Continuum supports these objects types in a proprietary manor but not as BACnet objects, therefore these values cannot be simply collected by EBO Resolution A simple method of collecting text strings from Continuum is to convert each character to its ASCII equivalent number, then pass these values via BACnet Analog Values, then convert back to a string in EBO The simplistic PE program below shows conversion of the first 8 characters of "String8Character" Object to 8 Analog Values "StringChr01-08", these are collected by EBO The Script Program below converts the Analog Values back to a Text String  

Issue What type(s) of 125 kHz proximity cards are supported by Security Expert Card Readers? How to configure Secure Expert to read an Indala card (125 kHz)? Product Line EcoStruxure Security Expert Environment Security Expert Smart Card Reader Cause Card readers work by modulating the electromagnetic wave in different ways to resolve between 1s and 0s. There are several different ways to bring card data across 125 kHz; ASK, FSK and PSK. ASK : Amplitude Shift Keying FSK : Frequency Shift Keying PSK : Phase Shift Keying Since the technology used is determined at the hardware level,  a reader would need to have the hardware to read a specific type. Security Expert 125 kHz readers make use of FSK only, which means that e.g. Indala cards (125 kHz PSK technology) will not work with them. Resolution Use FSK technology 125 kHz cards with Security Expert Smart Card Readers.

Warning Potential for Data Loss: The steps detailed in the resolution of this article may result in a loss of critical data if not performed properly. Before beginning these steps, make sure all important data is backed up in the event of data loss. If you are unsure or unfamiliar with any complex steps detailed in this article, please contact Product Support for assistance. Issue When trying to add a SmartX server to an ES, or when trying to rename an ES, you see the following error message: "All subserver must be online at least once before adding" Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server (version 2.0 or later) Cause This issue is caused by a mismatch between the content in the folders called MountPoints and Versions in the ES database folder. Resolution Before doing this make sure you have a good backup of the ES database. Identify and delete the files in the ES database folder called Versions which don't have representation in the ES database folder called MountPoints. The files have the same GUID-name in both folders, but not the same content, so you cannot copy paste between the folders. It requires a manual comparison. Procedure to identify files to remove (for version 2.0): 1. Check files in C:\ProgramData\Schneider Electric EcoStruxure\Building Operation 2.0\Enterprise Server\db\System\MountPoints 2. Check files in C:\ProgramData\Schneider Electric EcoStruxure\Building Operation 2.0\Enterprise Server\db\System\Versions 3. In Versions only remove the files which don't have a representation in MountPoints. Comparing the files in MountPoints (1) to the ones in Versions (2 & 3). Here they are identical and all is OK.

Issue The first time a TGML graphic is opened after logging in through Workstation it takes a long time (approximately 30 seconds) before the graphic is shown Product Line TAC Vista Environment Windows Domain TAC Vista .NET Framework Cause This is usually only an issue when the PC has either no or a bad internet connection or is located behind a proxy server. The reason this is happening, is because an application using e.g. signed .NET Framework dll files will check for certificate revocation each time it's launched. That can only be done if the PC has internet connection. If the PC can't connect to Microsoft's server to get the newest list of revoked certificates, the application will appear to hang until a given timeout is reached. The default timeout is 35 (15+20) seconds. For a deep explanation of certificate revocation check and the base of this article, read this article. Resolution There are two solutions that can be implemented. The first is mandatory and the second is optional. The first solution solves the slow TGML opening issue, while the second seems to have a positive overall performance impact but doesn't solve the slow TGML opening issue. A third solution is to get internet connection for the PC, but that is usually not an option. Solution 1 : Lowering the timeout 1. Open the "Local Group Policy Editor" by typing "gpedit.msc" (no quotes) in "Start"->"Search programs and files..." 2. Navigate to "Local Computer Policy"->"Computer Configuration"->"Windows Settings"->Security Settings"->"Public Key Policies" 3. Open the object to the right called "Certificate Path Validation Settings" 4. In the tab "Network Retrieval" check "Define these policy settings" and write 1 in both retrieval timeout settings 5. Click "Apply" and "OK" and close "Local Group Policy Editor"   Solution 2 : Manually installing the newest certificate lists 1. Download the newest CRL updates from a PC with internet connection http://crl.microsoft.com/pki/crl/products/CodeSignPCA.crl http://crl.microsoft.com/pki/crl/products/CodeSignPCA2.crl 2. Copy the two files to the PC having the issue 3. Open a command prompt and navigate to the folder where the files are located 4. Install the CRL files using the following commands CertUtil -AddStore CA CodeSignPCA.crl CertUtil -AddStore CA CodeSignPCA2.crl

Issue Require method on how to Arm and Disarm an Area by Triple Badging at the Door. Product Line EcoStruxure Security Expert Environment Security Expert Cause Require Door to be controlled by a Schedule but also to allow a valid User to override the Schedule with three consecutive valid badges. Resolution Required Objects virtual Output - Flag to control area status (v_TB_AreaArmedFlag) Area - Area to control (TB_Inside_Area) Programmable Function - Arms Area when virtual output ON (TB_Inside_Area_Arm_PF) Programmable Function - Disarms Area when virtual output OFF (TB_Inside_Area_Disarm_PF) Schedule - Operating hours of Area (TB_Schedule) Door - Door to control Area status (TB_Entrance_Door) Configuration Create virtual Output v_TB_AreaArmedFlag. Set Module Type to Output (PX) and Module Address and Module Output channel to ones that do not exist. virtual Output On the Reader Expander > Reader 1 tab - Set Reader 1 Arming Mode to Toggle Function Output on 3 Reads Set Reader 1 Function Output to v_TB_AreaArmedFlag Reader Expander - Configuration Under Reader Options section set Allow Reading Opened/Unlocked. Under Misc Options section set Allow Access When Area Armed Reader Expander - Misc Options On the Doors > General tab - Set Area Inside Door to to TB_Inside_Area - Set Unlock Schedule to Never Door - General On the Options tab under Door Options 2 section  - Set Door Lock Follows Inside Area Door - Options On the Area > Configuration tab under Schedule set Arm/Disarm Schedule to TB_Schedule Set Disarm Area When Schedule Starts Set Arm Area When Schedule Ends Area - General On Outputs tab set Armed Output to v_TB_AreaArmedFlag Area - Outputs Go to Automation > Programmable Functions and create TB_Inside_Area_Arm_PF - Set Type to Area Control - Set Mode to Normal Programmable Function - Arm - General Under Area Control tab - Set Area Function to 2 - Area Arms on Output Turning On - Set Output To Check to v_TB_AreaArmedFlag - Set Area To Control to TB_Inside_Area - Save changes - Right-click TB_Inside_Area_Arm_PF function and select Start Programmable Function - Arm - Area Control Go to Automation > Programmable Functions and create TB_Inside_Area_Disarm_PF - Set Type to Area Control - Set Mode to Normal Under Area Control tab - Set Area Function to 5 - Area Disarms on Output Turning Off - Set Output To Check to v_TB_AreaArmedFlag - Set Area To Control to TB_Inside_Area - Save changes Right-click TB_Inside_Area_Disarm_PF function and select Start Programmable Function - Disarm - Area Control

Issue How to set up PWM output in ZBuilder for TAC Xenta 121/122 devices. Product Line TAC Vista Environment Xenta 121 Xenta 122 ZBuilder Cause To be able to set up the PWM function for outputs, you need to understand each entry in the settings windows. Resolution   Activate at % TL The PWM output control starts when Terminal Load reaches this value. Fully active at % TL The PWM output control is fully active when Terminal Load reaches this value. Min control signal % The PWM output will not send out lower percentage of full stroke. Max control signal % The PWM output output will not send out higher percentage of full stroke. Period seconds The time for one full PWM period. This period will be cyclically repeated. Pulse change if change ≥ % Applicable only for actuators giving a position directly proportional to the pulse width and not dependent of cyclic updates (PWM with US terminology). This means the output will only activate when the Terminal Load has changed more than the set value, since last activation. Normally closed The TRIAC output is connected to ground (activated) when Terminal Load is zero, and the PWM output is not active. When the PWM output activates, the TRIAC output will not be connected to ground. Normally open The TRIAC output is open, not connected to ground, when Terminal Load is zero, and the PWM output is not active. When the PWM output activates, the TRIAC output will be connected to ground.