Building Automation Knowledge Base

Issue Error message "Unable to display events. To view or change, go to Text view on the Advanced tab." in a Schedule in Workstation. Product Line EcoStruxure Building Operation Environment Building Operation Workstation Cause The error message appears when attempting to view events with a duration of five minutes or less in the graphic view of Schedules in Workstation. Additionally, the message can also occur when the time between two events is five minutes or less.  The screenshot below shows an event with a duration of four minutes that causes the error message to be displayed. Resolution Two potential solutions are available to address this issue: Utilize Webstation: Webstation does not have the same limitations as Workstation. Users can leverage Webstation to view and edit events with a duration of five minutes or less, or where an event starts five minutes or less after another event ends. Switch to Text View: As indicated in the error message, users can switch to the Text view on the Advanced tab to list short-duration events. To do this, navigate to the Advanced tab (1), then click on the Text view button (2) to switch to text view.

Issue Problems adding i2 or b3 controllers to systems and causing the network to go down or devices to not learn on. Product Line Andover Continuum Environment i2 Controller b3 Controller Cause Duplicate ID's,  incorrect baud rates or faulty controller Resolution Infinet and BACnet field controllers have the capability to autobaud and auto correct duplicate ID's on a network. They do this by listening to the network on powerup and determining what Baud Rate and currently operating controller ID's are on the network. If an existing controller is on the network and the newly added controller has the same ID assigned, the new controller will zero out its own ID so as not to cause a network problem with duplicate ID's. Then learning or manually commissioning the controller will give it a unique ID. It is therefore critical that when adding a controller to a network, that the controller is connected to the network before the controller is powered up.  Failure to do so could cause network problems such as duplicate ID's or conflicting baud rates which could bring the network down. If the new controller causes these types of problems it is recommended to power down the suspect controller(s) and re-power them to eliminate these issues.  Run acctrace when the learn is being done and there will be an indication of what is happening.  Send a controller error log to PSS.   If nothing else works even with a clean database then replace the Master and if that works send the controller in to repair.

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 If TLS 1.0 is disabled on Microsoft Server 2016 you cannot connect to SQL Server 2016 database using Continuum database initialization. Product Line EcoStruxure Building Operation, Continuum Environment Continuum Cyberstation Microsoft SQL Server 2016 Microsoft Server 2016. Cause Microsoft no longer supports TLS 1.0 protocol and IT departments are disabling it. The current version of the ODBC driver (SQL Server) used with Continuum will not function correctly when TLS 1.0 is disabled on Windows Server 2016 in order to use TLS 1.2. A defect/hotifx QC#2290 has been issued for this issue. Resolution There is a hot fix for QC#2290 that needs to be applied to the cyberstation after the installation of the ODBC driver version 13. Use the following link to download the appropriate version of the ODBC driver for your version of the OS. Link to download ODBC driver version 13 https://www.microsoft.com/en-us/download/details.aspx?id=50420 This hotfix fixes the following defect 2290 = When TLS 1.0 is disabled on server 2016 ODBC does not connect to SQL database. Hotfix is attached below. Contact PSS for the hotfix for Cyberstation 2.03 Please note: The ODBC Driver 13 for SQL Server needs to be installed before the hotfix is applied Deprecation date   Steps to apply this hotfix: Create a ContinuumDB backup Shutdown Continuum if it is running Make a backup of OmsInst.exe in the Continuum folder Extract the OmsInst.exe from the hotfix zip file and copy the new file to the Continuum folder Do an update/initialized database Start Continuum

Issue An Enterprise Central has two Enterprise Servers, both connected to External Log storage as pictured below. How can the EC access trend logs in both External Log storage locations when it is only connected to one of them? Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Central Building Operation Enterprise Server Building Operation Automation Server Premium (AS-P) Cause It is only possible to specify a connection to one External Log storage location in the EC Resolution When a user needs to access trend data from a specific log located in, for example, an AS-P while the Workstation is connected to the EC, the following process occurs: The EC contacts the specified External Log storage for the log data using the trend log ID. If the trend log ID is not found in the specified External Log storage, the EC then contacts the Enterprise Server (ES) associated with the AS-P to request the log data. The ES connects to the External Log storage specified within it and retrieves the log data using the trend log ID. The ES delivers the log data to the EC, which in turn delivers it to the Workstation for access. This process ensures that the EC effectively manages connectivity to External Log storage systems and retrieves the required trend data for users.

Issue When using mstpcap.exe to capture, it automatically stops after 65535 packets. Similarly, when using Wireshark, it will stop capturing if the dissector encounters an issue. This article provides a solution to continuously capture BACnet MS/TP traffic in a ring buffer and store it as files. Product Line Andover Continuum, EcoStruxure Building Operation, TAC IA Series Environment Wireshark Any BACnet MSTP RS-485 network Cause Analyze BACnet traffic via capture files. Resolution Install Wireshark. Ensure TShark is checked when installing options.  Ensure Wireshark is installed with Npcap (default) or WinPCap has been installed by IA Series Workplace Tech. Install mstpcap.exe referencing BACnet MSTP Capture Application. Ensure that mstpcap.exe has been configured for the correct port and baud rate. Here is an example for Command Prompt and PowerShell: # Command Prompt cd "C:\Program Files\Wireshark\extcap" mstpcap.exe com3 38400 # PowerShell cd 'C:\Program Files\Wireshark\extcap' ./mstpcap.exe com3 38400 Run Tshark to determine the interface being used by mstpcap so that one can reference it by number. For this example, we are going to choose 9. COM3 (BACnet MS/TP on COM3). Please change the number below to the number of your interface.  Start Tshark capture by entering the following command, updating as needed. The commands below save Test01.pcap to the Username's desktop. Please store to a location that the user has access to write.  # Command Prompt cd "C:\Program Files\Wireshark" tshark.exe -i 9 -b duration:3600 -b files:72 -w "C:\Users\Username\Desktop\Desktop\Test01.pcap​"​ # PowerShell cd 'C:\Program Files\Wireshark' ./tshark.exe -i 9 -b duration:3600 -b files:72 -w 'C:\Users\Username\Desktop\Desktop\Test01.pcap​' Note: Change  -i 9  to the number of the interface on the capturing machine. Change  -b duration  to time in seconds (3600 is one hour). Change  -b files  to the number of files to cycle through (72 is 3 days of 1-hour captures, 3x24). Change  -w  to write to the location and filename you choose. Change  \Username\  to your Windows User, if you want to save to that user's Desktop Reference: tshark(1) Manual Page (wireshark.org)

Issue Does SHD2/SCD2 have galvanic isolation? Product Line EcoStruxure Building Operation Environment Building Operation SmartX Living Space Sensor Cause Galvanic isolation is a principle of isolating functional sections of electrical systems to prevent current flow; no direct conduction path is permitted. Resolution The SHD2XP2A/SCD2XPXAVX does not have galvanic isolation.

Issue ES is connected to a remote server via EWS; when loading a graphic in a web browser or workstation, the values take a long time to read. (a few minutes.) It makes no difference what the settings for polling are configured for. Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Enterprise Central Cause Every time the graphic is brought up, the ES needs to subscribe to all values from the external EWS server, this is the cause of the delay. Resolution Workaround Solution: Maintaining Active Subscriptions The recommended workaround solution involves maintaining active subscriptions. This can be achieved through the following methods: Persistent Graphic Display: Always keep the graphic displayed on a client. This is crucial as the subscriptions are terminated when the graphic object is closed. By keeping the graphic open, the subscriptions remain active. Watch View Creation: Create a watch view that includes the values displayed in the graphic. This ensures that the values are constantly monitored and updated. As long as a client subscribes to these values, the update process will be expedited when the graphic is launched. This is because the subscriptions remain active, and the values do not need to be re-initialized. However, if there are no active subscriptions to the values, all values must be set up each time the graphic is opened. This can potentially slow down the process. Therefore, maintaining active subscriptions is highly recommended for efficient operation.

Issue Customer request of a sample Plain English program to unlock a list of doors by toggling a switch. NOTES Sample program provided here as proof of concept only, and is not intended as a complete solution but rather as general guidelines, significant modifications maybe required to adapt the sample program to an acceptable solution per local site requirements. The sample program as written works with a "maintain position" toggle switch, if site is using a "momentary" switch then the program will need modifications. Resolution Sample PE Program in PE Editor   See attached text file   

  Issue The WebStation menu used to create new calendar dates and values is not visible. Product Line EcoStruxure Building Operation Environment Building Operation Workstation Building Operation Webstation Building Operation Enterprise Server Cause The panel used to display the calendar schedule is incorrectly configured Resolution In Workstation, right-click on Panel and go to Properties, go to Show Toolbars, and choose Yes.    Now when you log in to Webstation, you will see the toolbar including the menu on the top of the calendar in the panel.     

Issue When the BACnet Interface is created in Container Servers, the automatically generated Device Object ID aka Instance ID can be the same as another Container Server on the same container host. Product Line EcoStruxure Building Operation Environment Building Operation Edge Server Building Operation Enterprise Server for Linux Cause The algorithm used to pick BACnet Interface Device IDs in individual Automation Servers does not work for Container Servers since they share the same ethernet connection,. Resolution Perform tasks to ensure Instance IDs are unique. One can prevent the issue by ensuring uniqueness when adding the BACnet Interface  When adding Interface -> BACnet Interface, do NOT click Create or Create and Edit, but click Edit in Wizard.  Enter the following data BACnet Name Instance ID (ensuring unique ID to the entire BACnet system) Leave Network Type = IP network Network ID (this should be the same network ID as the IP network is attaching)  One can repair the issue and ensure uniqueness after creating the BACnet Interface. Changing the BACnet Device ID in an Automation Server to configure unique ID Repair Hosting a BACnet controller and IO Module  Fixing References in BACnet/IP Controllers 

Issue Getting an Error 1001 near the end of the EcoStruxure WebReports Installation Reports not functional from WebReports Product Line EcoStruxure Building Operation Environment Web Reports SQL 2008 R2 Windows Server 2008 Windows Server 2012 Cause This error is caused when the WebReports installer is unable to reach SQL Server Reporting Services to configure the WebReports Interface Resolution After a failed install of WebReports you will need to follow the general workflow:   Clean of the Pieces of the failed install. Use the uninstall process listed in the WebReports Reference Guide or Uninstall Process for Web Reports. Correct all possible causes of the failed install Verify that you can connect to the ES using http from the Reports Server PC Verify that you can connect to http://localhost/Reports_SQLInstanceName  Re-install WebReports. NOTE: You may be able to correct the issue without having to remove and re-install WebReports. Possible Issue: The Microsoft Reporting Service SQL databases are not registered Check through SQL Management Studio that the 2 databases "ReportServer$instance" and "ReportServer$instanceTempDB" are registered. If not, the SBO Web Reports installed have nowhere to place the report pack files. If they are not there, you need to add them through "Reporting Services Configuration Manager". Click "Database" and then "Change Database". Here you can chose to create new databases. Possible Issue: Insufficient User Access Log out of Windows and Log back in using a PC admin account. The account logged in for the installation should have full access to Windows and be a DB admin in the SQL Server. Set the User Account Control Settings to Never notify. Possible Issue: PC Configured as a Domain Server In the Server Manager, check that the IIS Role is configured and that there are no Domain Roles assigned to this PC Possible Issue: Another Application is using a Required SQL function Uninstall any application which use SQL on this PC. (The Enterprise Server does not Use SQL) As a Best Practice, the Reports Server should be installed on its own, dedicated PC. Possible Issue: Incorrect Version of SQL Server or Windows Server Check the Reports Server Specification Sheet for your build and verify that you are on the Correct Version of Windows and SQL. Possible Issue: Secure Connection Level set too high This issue typically also results in not being able to log into http://localhost/Reports_SQLExpress. Log into the Reporting Agent Configuration Manager Application Click on the Report Manager URL on the left-hand column Click on the HTTP URL This will give you the correct URL for your installation of SQL If this fails, browse to C:\ProgramFiles\Microsoft SQL Server\MSRS10_50.SQLEXPRESS\Reporting Services\ReportServer (this may vary based on SQL Installation)   Modify the CONFIG file "rsreportserver" Change the Secure ConnectionLevel to "0" Save the file and attempt to log into http://localhost/Reports_SQLExpress again. For more details on this property see: http://technet.microsoft.com/en-us/library/aa179559(v=sql.80).aspx Possible Issue: .NET Framework is not operating correctly. Download the correct version of .NET framework for your version of EBO (The correct required version can be found on WebHelp Reports Server under EcoStruxure Building Operation Software Requirements) Run the installer in "Repair" mode Possible Issue: The Windows account "appuser" is not created because the default password does not meet password policy requirements Temporarily disable password policy on the server and try reinstalling. For clarification of the use of 'appuser', refer to the following article, Report Server "appuser" clarification 

Issue There is a need for a single Compatibility Matrix that shows EBO, PME, Energy Expert and relevant software versions all in the same location.   Product Line EcoStruxure Building Operation, Other   Environment EcoStruxure Energy Expert (formerly Power Manager) ETL tool Cause Energy Expert version compatibility information is currently available but is stored in many different places such as release notes and online documentation, rather than one single matrix.   Resolution The full ETL for EBO compatibility matrix is shown in the following table. Energy Expert  PME EBO ETL Integration Utility .NET Framework Power Manager 1.0 7.2.3 1.6.1 3 1.0.14304.2 4.5 Power Manager 1.1 8 1.6.1  1.7.1 4.1 1.0.15306.1 4.5 Power Manager 1.2 8.1 1.6.1  1.7.1  1.8.1 4.3 2.1.16081.1 4.6 Power Manager 1.3 8.2 1.8.1 1.9.x  4.6 2.2.17056.2 4.6 Energy expert 2.0 9 2 5 3.0.18215.3 4.6 Energy expert 3.0 2020 3.0 3.1 6 3.1.19319.1 4.6 Not commercialized  - (n/a) 2021 3.2.3 6 Integrated - (n/a) 4.8 Not commercialised - (n/a) 2022 4.0.2/2022 6 Integrated - (n/a) 4.8 Not commercialised - (n/a) 2023 5.0/2023 6 Integrated - (n/a) 4.8   Great care must be taken when choosing the correct version of ETL to use when integrating Energy Expert and EBO, as there are actually two families of ETL in production.  One ETL designed and tested for PME use only and ETL for EBO designed and tested with an EBO Extract Task specifically for integrating the two systems.  (For example, a version of ETL 4.7 exists, but this is not ETL for EBO and therefore does NOT contain an EBO Extract Task, even though it is a valid version of ETL for the Power Community) New PME 2023 now offers EWS Client 1.2 which can be used to transfer data from EBO to PME instead of ETL.  The merits for and against using this new EWS Client rather than ETL are discussed at length in the PME 2023 System Guide

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 SP-C has a valid gateway specified and it's not receiving communications Product Line EcoStruxure Security Expert Environment Security Expert Controller firmware .1248 (or higher) Security Expert 4.0.128 (or higher) Security Expert Controller w/ USB port 2.08.582 (or higher) SX-ELV-HLI-TK license to enable the integration USB to Ethernet adaptor dongle TKE Controller (American) v2r0 (only supported version) Cause It is a known issue. SP-C sends a heartbeat message to TKE but it is not being sent/received as a broadcast message. The controller still sends a heartbeat message to TKE but it is not sending it as a broadcast message with a destination of FF:FF:FF:FF:FF:FF. The gateway being valid causes it to send a Unicast message to the gateway itself (eg router) which does not pass it on to the rest of the network. (This is a known issue and has been logged with engineers). Resolution The workaround is to enable the USB Eth NIC on the SP-C and use: - The onboard NIC to connect to the Security Expert Server that requires a valid gateway to be set - The USB to ethernet adaptor (USB NIC) to connect to the TKE Network where we would set any gateway to avoid this bug Note: The USB NIC can only be configured when using OTIS elevator HLI type. The USB NIC hardcodes the required OTIS IP info to the Onboard NIC for connection to Security Expert. To enable Web UI: 1. In Security Expert, Go to Sites|Controllers|Configuration Tab. 2. Scroll down and expand the Elevator HLI section. Set Elevator HLI type to choose OTIS 3. Return to the General Tab, Scroll down and expand the Commands section and enter OTISUseUSBForMainComms = true 4. Save changes and wait for the programming to be downloaded. 5. Power cycle the SP-C. 6. Go to SP-C Web UI. The USB Eth adaptor will have the original IP. Configure both IP adresses 7. Once The NICs are configured, change the Elevator HLI type back to Thyssen Krupp, choose Cable Network type 8. Click Save and restart the SP-C.

  Issue Performing an Enterprise Server upgrade preview from 3.2.3.59 to 5.0.3.117, the upgrade fails with the error "INET legacy interface no longer supported." message      Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Cause An existing folder in the Enterprise Server contained graphics underneath the INET interface. This folder was moved within the system, and the INET interface was deleted. However, the moved folder still had links to the INET interface, causing the upgrade to fail since this interface is not supported in Building Operation 2022 (v.4) and above.  Resolution Delete any references in the database linked to the INET Interface. Bindings Diagnostics provides a quick method for locating these unresolved references.   After deleting these objects and/or references, the upgrade will completed successfully.

Issue How to Mass Create Trend Logs and Extended Trend Logs Product Line EcoStruxure Building Operation Environment Building Operation Workstation Cause If you did not create Trend Logs at the same time as you created the points or values, it is possible to create several trend logs or extended trend logs at the same time. Resolution For this example, we assume all of the values are in the same folder. You can hold down SHIFT to select multiple adjacent objects, or CTRL+click to select non-adjacent values Mass Creation of Interval Trend Logs Select all of the Values you wish to add the same type of Log to Right Click and select New connected object>Trend Select the Log type and the settings you wish to use.  Note that the log name will be the values name with either a prefix or suffix defined by the user Be sure to Select a useful folder location, either same folder as each selected object, a different folder, relative to the selected object or a single folder for all created objects. Click Edit in wizard. Set the Interval Settings, if iterval log type is selected. Click Next, configure initial meter settings if required, click next tehn click create Mass Creation of Extended Trend Logs if required Select the group of Logs you wish to create Extended Trend Logs for Right Click and select New connected object>Extended Trend Log Enter the desired settings. Just as above, the Extended log will use the Log' name plus either a prefix or suffix Be sure to Enter an appropriate Location. Use a folder on the ES if you wish these logs to show up on the Reports Server (Report server is not supported in EBO 2022 and higher). Click Edit in Wizard, Configure the Extended Log as desired, then click create. Fore more information, refer to: Mass Creating Trend Logs and Mass Creating Extended Trend Logs

  Issue The customer has created an alarm, this alarm has an Attachment that displays a Graphic (Display on Alarm enabled). All the remote Workstations at this site show the graphic popup on alarm, except a single Workstation. That Workstation will display PDF Files 'On alarm', but not TGML graphics. Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Automation Server Premium Building Operation Workstation Cause Either, they at the same time had two monitors and placed the graphic attachment on the other monitor, and then the position was saved. Or by mistake managed to move the attachment out of the current monitor scope Resolution Remove WorkStation cache from both (User + Program data) :  User: C:\Users\*user-name*\AppData\Roaming\Schneider Electric EcoStruxure\Building Operation\WorkStation  Program data: C:\ProgramData\Schneider Electric EcoStruxure\Building Operation\WorkStation The alarm will now display the TGML graphic attachment

  Issue EBO 5.0 and all other revisions, In workstation When selecting `View history` of an alarm, we get columns more focused on alarms such as Alarm state, Alarm text,.. etc  But  in WebStation, we have “ View Events “ that shows columns that are more focused on object event history (including Value before, Value After, etc) rather than alarm history.       Product Line EcoStruxure Building Operation Environment Building Operation Workstation Building Operation Webstation Building Operation Automation Server Premium Cause Navigating to View Alarm history in webstation is different than in workstation Resolution Alarm is a subset of Event, so it is reasonable to see it is under 'Event viewer'. There is no such a thing called 'Alarm history record' in webstation.This is Function as Designed (FAD) If we click on any of the events, after opening it we can see full alarm details.

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 Services for assistance. Issue Log data is not being logged into SQL. The Reports Server indicates that the database is full.   This view will be shown when logging into the WebReports interface. If this chart is not shown, the PC is not running an Express edition of SQL. Product Line EcoStruxure Building Operation Environment Reports Server Cause In most instances, the data that quickly fills the SQL database are Events. Event data fills the SQL Database and prevents log data from passing to the Reports Server database. If the data has filled within a few days, this would indicate an issue, and contacting your local support is the best option here. The Process below allows the user to stop the reporting agent from passing specific information to the Reports Server. If the data files are due to the amount of data stored, then an upgrade to the Standard/Full version of SQL is recommended.   Resolution To verify that the Events table is the likely cause of the SQL filling up, there are Standard Reports in the later versions of SQL.  The below example uses SQL Server version 13.x and shows the "Disk Usage by Top Tables."   If the Standards Reports are not available, then use the following article Building Operation Reports SQL Database Full, for instructions on how to show the details for each table.     The Process below allows the user to stop the reporting agent from passing Event information to the SQL Database: Download the latest SBO Reports Agent Config tool from the community. Load the Tool onto the Reports Server PC. Stop the Reporting Agent Using the Tool Press F7 to get to the Advanced Agent Configuration Page Change the numEventRecordToRead property to 0. This will prevent future event data from being written to the Reports Server database. Press Ok Under the Maintenance tab of the tool - there are two options under Events  Delete future events, alarms, and trends  Delete events and alarms older than... Restart the Reporting Agent This will stop any further Events from being passed through to the SQL Database.  

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 Services for assistance. Issue SQL Database is full, or the partition the SQL is installed is full Product Line EcoStruxure Building Operation Environment Building Operation Report Server Cause If a site is using SQL Express 2008, the limit is 10 GB. If using the full version(s), it is unlimited. If the database or the partition where the Reports Server resides is full, here are some steps to reduce the SQL table volume and offer a short-term solution. Resolution Before continuing, make sure there is a good backup of the database. Using SQL Server Management Studio, highlight the StruxureWareReportsDB and select New Query Use the following Script in that Query: SELECT t.NAME AS TableName, s.Name AS SchemaName, p.rows AS RowCounts, SUM(a.total_pages) * 8 AS TotalSpaceKB, SUM(a.used_pages) * 8 AS UsedSpaceKB, (SUM(a.total_pages) - SUM(a.used_pages)) * 8 AS UnusedSpaceKB FROM sys.tables t INNER JOIN sys.indexes i ON t.OBJECT_ID = i.object_id INNER JOIN sys.partitions p ON i.object_id = p.OBJECT_ID AND i.index_id = p.index_id INNER JOIN sys.allocation_units a ON p.partition_id = a.container_id LEFT OUTER JOIN sys.schemas s ON t.schema_id = s.schema_id WHERE t.NAME NOT LIKE 'dt%' AND t.is_ms_shipped = 0 AND i.OBJECT_ID > 255 GROUP BY t.Name, s.Name, p.Rows ORDER BY t.Name Select Execute to run that Query as shown in the screen capture below: The Results show each of the tables and the size of those tables as shown in the screen capture below: Purely for example purposes, a script to reduce the number of Events would be delete from tbEvents where DATEDIFF(day, datetimestamp, getdate()) > 180 To gain back the space after deleting rows, right-click on StruxureWareReportsdb > Tasks > Shrink > Database

Issue In a life safety-related application, such as a fume hood, it is a requirement that the status of the end switch is not shared via peer-to-peer bindings. Instead, the end switch status must be hard-wired to all four controllers. What precautions should be taken to ensure that this will not cause issues. Product Line EcoStruxure Building Operation Environment Building Operation Room Controller (RPC) 24 V Cause Connecting multiple RP-C to the same dry contact.    Resolution Make sure to use individual transformers to each controller (i.e. one transformer to one controller power supply) to minimize the risk of short circuit.