Building Automation Knowledge Base

Issue Which actuators are suitable for VG311F? Environment VG311F Venta Forta M700 MG900SR M800 M1500 MV15B M3000 Cause Which actuator to choose for MV15B Resolution The following actuators are, depending on application requirements, suitable for use with the VG311F valve: M700, MG900SR, M800, M1500, MV15B, M3000 For more information on the valve / actuator selection, please see the valve data sheet here. For more details on each actuators, please see their data sheets respectively. They are available for download from the Extranet or public website.

Issue Internal counter stops counting. Product Line EcoStruxure Building Operation Environment Script Function Block Counter 167777216 Cause When this script is used it stops counting at 16777216. Numeric Output CountOut   Main: CountOut = 16777100 goto Counter Counter: CountOut = CountOut + 1   Resolution This issue was identified in the early days of Continuum and is regarded as a limitation, not a defect. Explanation - Internally the Script handles all numbers as IEEE754 single precision floats, which means that 16777216 is handled as 1.6777216E7. Adding 1 to 16777216 is unrecognizable in that representation. Using an IEEE754 converter at https://www.h-schmidt.net/FloatConverter/IEEE754.html, one can see that 16777216 and 16777217 have the same binary representation. The point at which the counter will stop, will depend upon the value being added each time, so adding 0.9 will count to a different number than adding 1. The counting range can be extended by two or more variables as shown below. Numeric Output CountOut Numeric CountOut1 Numeric CountOut2   Main: CountOut1 = 16777100 goto Counter1   Counter1: CountOut1 = CountOut1 + 1 CountOut = CountOut1 if CountOut1 = 16777216 then goto Counter2   Counter2: CountOut2 = CountOut2 + 1 CountOut = CountOut1 + CountOut2  

Issue There are a couple of part numbers available for the expansion module cables, which ones are for which devices? Environment xP modules Cause Not sure which cables are for which xP modules. Descriptions and documentation on iPortal is inadequate. Resolution There are three xP module cables available: The 01-0100-484 cable is a replacement for the xP-Display module cable and this is meant to be for the xP-Display only, not for any of the other xP I/O modules. The xP I/O modules such as xPDO4 require either the xP-Mod-Cable-3 or xP-Mod-Cable-10. Be aware that you will only be able to extend the xP network for a maximum of 10Ft. See this iPortal datasheet or on Exchange Extranet for details.

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 Not sure how to configure sending emails to multiple recipients when an Input or Area goes into alarm. Product Line Security Expert Environment Security Expert SP-C-WEB Cause Correct formatting must be used when sending alarms to multiple email recipients. Resolution Separate each address with a semi-colon and surround the entire string with double quotes, see examples below.   Security Expert Navigate to Events | Actions, create a new Send E-mail Action and add your multiple addresses to the E-mail Address field. "address1@email.com;address2@email.com" Email Addresses The email address field is limited to a maximum of 128 characters. All email addresses must be within this 128 character limit to be sent correctly. SP-C-WEB To add multiple recipient addresses, navigate to Programming | Areas or Programming | Inputs. For an Area, select the Configuration tab and add a recipient email address to the command window and use the format:email:"address1@email.com;address2@email.com" For an Input, navigate to the Commands window for your selected input and use the format: email:"address1@email.com;address2@email.com"

Issue When upgrading an IMI Video system to the newer Datacard (ID Works) system, are there any files or utilities needed besides the ID Works software? Product Line TAC INET Environment I/NET Seven IMI Video system Datacard ID Works Cause Converting the IMI Video Badging system to Datacard system Resolution There are 3 files that you need. Click Convert.zip to download them. Also, INET Application Guide AG-2002-01.pdf has additional information on this process. When converting the IMI Video Badging system to Datacard system, the first step in the IMI system to begin the convert process is to re-index the database files before attempting to batch export the data. If you have multiple tenants you must perform this procedure for each tenant. ID Works ODBC String. Type the string as you see it including the case: UPDATE ACP001 SET FIELD16 = 'C:\Photo\' + cardnumber + '.JPG' Make sure the case and spaces are just like the above to avoid any problems. Make the path anything you like, but remember the C: string cannot exceed 50 characters.

Issue Controlli S300 Actuator Environment Controlli S300 Actuator Cause Controlli S300 Actuator terminal details. Resolution L=Neutral L'=230Vac B=Close signal from thermostat or control device R=230V to thermostat or control device V=Open signal from thermostat or control device To test: Place a wire link between R and B, the valve actuator will close, place a wire link between R and V, the valve actuator will open. If a auxiliary switch kit D22 is fitted, this can be used to signal the boiler/pump to start if the installation was a domestic. For the actuator datasheet click here.

Issue Ensure a version of TLS is disabled using OpenSSL Product Line EcoStruxure Building Operation Environment Enterprise Central Enterprise Server Automation Server Cause Need to verify TLS is disabled on an EBO server in case of incorrect text entry Resolution It is possible to check which TLS protocols are set to be disabled using WorkStation Control Panel's Security Settings or in the Device Administrator SSL Security Settings tab. If the version required is not disabled then consult Disabling TLS and SSH. Once the protocol is set to disabled follow the steps below to verify using OpenSSL Open a command prompt and change directory to the OpenSSL folder. If OpenSSL is not available consult OpenSSL installed with EBO or install OpenSSL as mentioned in Ensuring the SSL Host Certificate and key file are a matching pair To check if TLS is disabled enter the command openssl s_client -connect 'server address':'port'-'TLS version'.  For example if the server IP address is 192.168.5.95 and using port 443:- openssl s_client -connect 192.168.5.95:443 -tls1    openssl s_client -connect 192.168.5.95:443 -tls1_1 openssl s_client -connect 192.168.5.95:443 -tls1_2 openssl s_client -connect 192.168.5.95:443 -tls1_3 If an error is returned (1) and no certificates are available (2) then the TLS version is Disabled. If a certificate chain (3) and certificate details (4) are returned the TLS version is Enabled. The image illustrates only the start of the returned information, more will be available.   For additional information search "OpenSSL s_client" using an online web browser.  The s_client command can be used to test TLS server connectivity, TLS/SSL version support, check cipher suites, and verify server certificates.  

Warning Electrostatic Discharge Required: Always discharge static electricity from your person by touching metal prior to handling any hardware. Failure to do so may result in damage to devices. Issue Introducing a previously commissioned Continuum IOU module such as an AC-1 to an Access Expert or Security Expert site can cause communication issues in the LON bus due to duplicated node id. Product Line Andover Continuum, EcoStruxure Security Expert, EcoStruxure Access Expert Environment Continuum AC-1 Continuum Net Controller Continuum Net Controller II Access Expert Controller Security Expert Controller Cause When IOU modules are commissioned in a Continuum system, the Net Controller assigns each module a Node ID, this is in addition to the LON Module ID that is unique to each module hardware, the purpose of the Node ID, is to decouple the identifier used by Continuum for communication from the specific piece of hardware, this in order to facilitate the replacement of a failed module without the need to change its Continuum identifier. The module stores the Node ID in nonvolatile memory so that it persists across power loss. If a Continuum IOU module is introduced to a LON network (Security Expert SP-AC1 or Access Expert AX-SSC) without clearing its Node ID, there is a risk of creating a duplicate Node ID condition that will prevent the LON network from operating properly. IMPORTANT This should not be an issue during the normal transition of Continuum site to Security Expert or Access Expert, as all the modules on the running LON bus should have unique Node IDs, this is only a problem when adding a module, or replacing a module with one that has been used before. Resolution In order to signal its presence on the LON network, each module will transmit on resetting its status network variable. If upon receiving this message, the Net Controller determines that the module is NOT in its local database, the controller will decommission the module by setting its Node ID to zero. Before introducing a Continuum IOU module that has been previously commissioned to the LON network of an SP-AC1 or SX-SSC controller, decommission the IOU module using the steps below: Attach the module to an empty Net Controller that is powered down with its battery removed. For a Net Controller II, in order to be absolutely sure that the Net Controller has an empty database, you may need to clear its backup in flash from a browser or by the use of the reset IP switch. See LL on how to use the controller's reset IP switch to clear its flash backup https://community.se.com/t5/Building-Automation-Knowledge/How-to-clear-the-controller-flash-backup-from-the-hardware-using/ta-p/5877 Power up the Net Controller Once the CPU led on the Net Controller starts blinking, press the 'Reset' button on the IOU module. Wait 30 seconds to make sure the decommissioning process has completed. Power down the Net Controller Remove the IOU module

Issue MFC errors when starting or running Cyberstation or Webclient Product Line Andover Continuum Environment Windows XP Windows Vista Windows 7 Windows Server 2003 Windows Server 2008 Windows 10 Windows Server 2012 Cause Microsoft Function Class (MFC) errors are typically caused by missing, damaged or altered files that an application is looking for and is having problems using. Resolution There can be a number of reason why MFC errors are being received. Here are a few causes related to Cyberstation startup. Check the Continuum compatibility matrix. If you are using a version of Windows Operating System that has not been qualified for a specific version (i.e. Windows XP SP2 with 1.93) then this can cause MFC errors. Viruses and Malware can also affect MFC files. Be sure to run both types of scans on Cyberstation, but this should be done after the Cyberstation or Webclient PC has been installed. If these types of products are active during an install, they can flag some of the files that would normally get installed as suspect and cause problems with the operation of Cyberstation even if it appeared that the installation was successful. Removing Continuum, rebooting, running scans and then disabling the active scans at the time of the Cyberstation install will often resolve these issues. Windows XP, Vista and Windows7 have restore points that you can sometimes go back to in order to restore to a point earlier where the MFC errors were not happening. As a last resort, you may need to reformat the hard drive on the PC, reinstall the Windows Operating System including the appropriate service packs and hotfixes and then install Cyberstation or Webclient. Links to other MFC related articles: MFC errors on Continuum startup after moving a database to another PC MFC error on Continuum startup or Continuum won't start on HP PC Running a listview is giving a MFC error

Issue Replacing battery Product Line Satchwell Micronet Environment Panel Wall mounted Controller mounted Cause Obsolescence Resolution Updated June 2019 The MicroNet 50 series range MN350, 450, 550, 650 LCD and Touchscreen have been withdrawn from sale. The IAC 420, 600 and Touchscreen have now also been withdrawn from sale. No direct replacement is offered. Further information on these changes can be found in PA-00495 - Notice of Withdrawal - Satchwell Sigma and PA-00528 - End of Commercialization - Satchwell Sigma. ---------------------------------------------------------------------------------------------------------------------------------------------------------- Battery part number Type LS14500 The battery is available from RS Components

Issue Need to bring Continuum system into SmartStruxure. Product Line EcoStruxure Building Operation Environment StruxureWare Building Operation v1.3, Continuum v1.94 system with BACnet bCX and b3 devices Cause b3 devices under the bCX become BACnet devices as if they were 3rd party BACnet devices. Resolution Test Environment: Cyberstation 1.94, SmartStruxure 1.3 Released, (1) AS-B, (2) bCX4040, one bCX hosting (2) B3 devices. Do BACnet discovery from SmartStruxure. Both bCX's and the b3 devices can be seen From the Hardware\BACnet devices folder, multi-select both bCXs and drag them into the BACnet Interface\IP Network. Upload their BACnet objects to SmartStruxure. From the Hardware\BACnet devices folder, multi-select both B3 controllers and copy/paste them into the BACnet Interface\IP Network. The B3 devices are hosted as, and look like, generic BACnet devices. Once the two B3s have been copied to the IP Network, an upload to SmartStruxure can be done. BACnet Digital Values and BACnet Analog Values on the b3 devices can be seen updating on a SmartStruxure listview. Note: Currently in SmartStruxure v1.3 there is no method to multi-select and host B3 Devices, within an MS/TP network. This functionality is part of the Continuum Migration project (a future version). Also check out the b3 VAV Quick Start Video on the Exchange.

Issue Field Bus controller shows its version number as 0.000000. Learn controllers from comm port is very slow and fails when reloading the controller. Updating the firmware will not fix this problem. Product Line Andover Continuum Environment Cyberstation 1.74 above i2 controllers B3 controllers Cause There are many reasons that will cause the i2 and B3 controllers show their version number as 0.0000000 Wireless network enabled or Multi-Network card enabled on the machine. Database snatched from Flash RAM after power-cycle does not match to the Continuum Database Some controllers with special firmware (Such as B38XX-V with 4.501043) have points referenced by other controllers, this will make the source controller buffer to be full after more than 20 hours Unknown application software installed on the CyberStation PC B-Link fault will also cause this problem Resolution Exit Continuum CyberStation, then ensure only a single network card is enabled Fix the problem caused by database mismatching: Create a new database and bring the master controller online, Do learn from the commport and bring the field controllers online Click the "Reset" button on the Runtime tag after opening the controller editor. Do database initialization and connect the original database to see if the version number is correct or not. If not, skip to item 4. If yes, do SendToController and then BackUpToFlash Update the controllers to the latest version. Rebuild the CyberStation PC. Only have the Windows operating system and Continuum CyberStation installed. Skip over B-Link and connect Field bus to BCX1 comm2 directly to verify B-LINK has some fault, and then replace it with new one, if required

Issue StruxureWare Building Operation AS status data Environment StruxureWare Building Operation AS Automation Server Cause AS Information program such as CpuUsage, MemUsage, ProductID, Partnumber, Serial, SWversion, and much more. Resolution The attached file can be imported into a AS (with any or the releases 1.1.x  through the current release 1.5.x). It will create two graphics that supply a wealth of operational information. Screenshots are shown below:   After import into your AS, look for System View folder. Open to view the two ProgramInfo and SystemInfo tabs. Please note that you can also see the CPU% and memory usage of the AS by using Building Operation Workstation, highlight the AS, go to the Properties tab and in Basic, the stats are listed.

Issue Are examples available to show how to write Plain English programs and create points for a Modbus RTU X Driver linked to Schneider Electric Power meters? Environment Modbus RTU X Driver Schneider Electric PM800 Power meters. Cause How can Modbus RTU X-Driver programs be written to poll for the data in a 3rd party Modbus device? Resolution The attached example show how to use the modbus RTU x-driver to read 4 16 bit data values from the PM800 meter, then using plain english to get the values to output to a single infinity numeric the total Power reading in kWH/mWH/gWH depending on the scaling factor of the meter. Create 4 Numerics reading the four registers that are used to store the data. Registers, 1716, 1717, 1718, 1719 are used in the PM800 Then create another numeric and via PE do the following calculation Energy Calc = (Register 4 x 1000000000000) + (Register 3 x 100000000) + (Register 2 x 10000) + Register 1. This will give you the value in wH. Then use a multiplier to give you the final reading in kWH etc.

Issue Public values, inputs and outputs of a Menta object defined in a Xenta 700 XBuilder project are displaying their values in Workstation as [Invalid Address]. When the value is double- clicked, the following error appears: Error in property Value. Read operation failed. Product Line TAC Vista Environment Vista Workstation Xenta Servers Xenta 701, 711, 721, 731 XBuilder Menta Cause The Menta object is not connected to a task. Therefore the Menta application is not being executed. Resolution In XBuilder, generate the project. Check the output window Generate tab for a warning that states "This Menta Object is not connected to a task" Double click the warning. The offending Menta object is highlighted. Drag and drop the Menta object into a Control Task folder in the Network Pane > TAC_Xenta_7xx > Control Tasks Regenerate and send the project to target. Menta object values should now report valid values.

Issue Opening an MTA file in Menta causes an "The device type is not supported" error message. Environment Menta 5.x.x XBuilder 5.x.x Cause The Menta file is for a Xenta 700 controller and cannot be opened in stand alone Menta which only supports the Xenta 280, 300, and 400 series of programmable controllers. Resolution Import the MTA file into an Xbuilder project's Menta Library in order to edit or view the MTA file.

Issue Maximum number of expansion modules and doors per controller Environment SP-C Security Expert Security Expert Controller SP-RDM2 Security Expert Security Expert Door Expansion Module Cause Documentation states that one SP-C supports up to 128 doors but this is dependent on the communications.  Resolution The current recommendation from Product Management is a maximum of 24 to 34 doors per SP-C. This equates to about 10 to 17 reader expansion modules.  

Issue SEC-TE (TE2) smart terminal controller / SED-0 (DA2) smart wireless actuator will not come online in an MPM controller. Product Line EcoStruxure Building Expert, Field Devices Environment SmartStruxure Lite Multi-Purpose Manager Smart Controllers Cause The Zigbee network configuration parameters in the MPM have been entered incorrectly. Resolution The application version of the SEC-TE/SED-0 must be determined before proceeding forward. Sticker on device should read V13 or V14. To check/modify the current settings, navigate to the "ZigBee Configuration" object (ZBC) under the MPM. For Application Version 13: Stack profile should be set to "Custom" and Security profile should be set to "None." For Application Version 14: Stack profile should be set to "ZigBee Pro" and Security profile should be set to "Home Automation."

Issue A floating-point value is displayed incorrectly in a TGML graphic. The presentation field appears to show random numbers. The example shows how the value 11.60 is represented in a TGML graphic. 11.60 is actually stored as 11.600000381469727. In format presentation mode: In none presentation mode: The last 6 digits of the stored floating-point value are seen! Product Line TAC Vista Environment TAC Vista 5.1.X TGML editor 5.1.X A presentation text bound to a floating-point value. Cause Vista uses the PC's default settings for number of decimals, when presenting values in TGML graphics. Resolution To resolve the issue, either set the format property to "Presentation" for the binding object or change the PC's settings to view fewer decimal places eg. 2.