Building Automation Knowledge Base

Issue Programming for the use of Smartware Technologies DUIC-5P-12v input multiplexer Product Line TAC IA Series, EcoStruxure Building Operation Environment Building Operation Multi-purpose Controller Building Operation Multi-purpose VAV Building Operation RP-V VAV Building Operation Room Controller I/A Series N4 Jace 8000/9000 I/A Series N4 Enterprise Server Building Operation Automation Server Premium Cause Define the application programming and configuration of the DUIC-5P-12V in various enviroments using SpaceLogic contollers Resolution The DUIC-5P-12V Card allows for conversion of a single universal input channel to accept up to five voltage free contacts of any mixture such as mercury wetted, Triac, etc., which may have inherently large and varying resistances. The DUIC-5P-12V on-board circuitry allows the controller inputs to have a consistent input reading, unaffected by long lead lengths, varying resistances, etc.  Smartware Technologies Documents includes programming for use in SpaceLogic devices under an AS-P in the form of a Function Block program. When SpaceLogic controllers are used in the Niagara Frameworks Jace 8000/9000 or hosted directly under a Niagara Frameworks Enterprise Server, the programming is done in a Visual Script Programming format utilizing the Schneider MPX modules in Workbench. The documentation addresses the original use for the I/A Series MNL and MNB contollers as well. NOTE:  The device requires half wave 5 -12 DC or 24 VAC only to prevent damage

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 hosting objects from EWS/Smart Connector, such as Security Expert, into EcoStruxure Building Operation (EBO), additional or mismatched object names can result in unresolved bindings and duplicate EWS IDs. Common symptoms include:  - Duplicate EWS IDs with different names - Unresolved or broken bindings - Binding loss after deleting containers   Duplicate EWS IDs with different names Unresolved or broken bindings     Product Line EcoStruxure Building Operation, EcoStruxure Security Expert. Environment EcoStruxure Building Operation Enterprise Server (ES) Security Expert Smart Connector Integration EcoStruxure Web Service (EWS) Cause Typical reasons for this to occur: Hosted object names do not match those in Security Expert. Deleting containers without proper renaming can cause binding loss. Resolution   Best Practices for Future Hosting Always rename the hosted object in EBO before rehosting from the hardware folder. This ensures that existing bindings are preserved. Avoid hosting the entire `SecurityExpertServer` container—only host changed or new objects. For Unbound or Irrelevant Objects: - If objects have no bindings, naming is not critical from an EBO perspective - Delete the container and rehost the object from the **Hardware folder**.   To Retain Existing Bindings  Identify the correct object name in the Hosted Containers folder  Copy the name to avoid typos. Delete the duplicate object with the correct name. Rename the existing EWS ID to match the copied name. Save the rename Verify bindings: Right-click the renamed object Select Delete Click Show References Confirm bindings are still valid. Click No to cancel deletion. Repeat this process for each object (inputs, outputs, doors, etc.) that has existing bindings.  

Issue The F3 Search function in EcoStruxure Building Operation (EBO) WorkStation does not return results for Notification File objects (e.g., .xlsx, .pdf, .txt), even when using wildcards.     Product Line EcoStruxure Building Operation Environment EcoStruxure Building Operation WorkStation Search Cause This behavior is functioning as designed (FAD). Notification files generated using the "Write to File" option are not stored in the EBO database. Therefore, they are not indexed and cannot be retrieved using the F3 search function. Resolution Although these files are not searchable within EBO, they are saved locally in a fixed directory: ...\db\notifications To assist users in locating these files:  Create a Hyperlink Object in EBO that points to the above folder. Users can then open the folder directly within WorkStation and use the operating system’s search functionality to locate specific files. Note: The notification file path is not configurable. For more information, refer to the official documentation in WebHelp: Accessing a Notification Written to a File

Issue Panel showing detector Calibration error. Product Line ESMI Fire Detection. Environment FFSULH1001. FFSULH1002. Cause When the contamination increases significantly and exceeds the sensitivity range for the smoke sensor, it is no longer able to perform calibration, causing a calibration error. Resolution Understanding the Calibration Process: The Esmi Ultima panel performs daily calibration and drift compensation for all addressable smoke sensors at 7 AM by default. Sensitivity and Contamination: Over time, dust and other contaminants can build up in the chamber of a smoke sensor, increasing its sensitivity. Illustration: Left Image: Clean sensor requiring 2.0% per foot of smoke to activate the fire alarm. Right Image: Contaminated sensor with increased sensitivity, requiring less smoke to reach the alarm threshold of 2.0% per foot. Trouble Condition: When the panel can no longer compensate for the contamination, it indicates a trouble condition. The Esmi Ultima panels can compensate for contamination build-up in addressable smoke detectors and addressable multi-criteria detectors. Daily calibration offsets any contamination, ensuring each smoke detector remains within its UL Listed sensitivity range. Recommended Action: Clean or replace the sensor with a new one of the same model. If you have a replacement in stock, replace it immediately.  

Issue Fail to apply CP or HF on AS Product Line EcoStruxure Building Operation Environment EcoStruxure Building Operation Workstation EcoStruxure Building Operation Automation Server (ASP/ASB) Cause The Automation Server is not installed next to the Power Supply. The requirement is stated in the Hardware Reference Guide, Position 1 is reserved for a power supply. Position 2 is reserved for an automation server. Resolution When the update process fails, please collect the DebugInformation. Next, check the System.log for the node ID. If the node ID is not  2 , it indicates that the AS is not installed at the correct address. In that case, the physical location of the AS needs to be corrected. Example of incorrect ID location Relevant Resource: Multiple Automation Servers on the same backplane

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 After making changes to object names in the system, outdated or incorrect names may still appear under the Hardware folder in EcoStruxure Web Services (EWS).     Product Line EcoStruxure Building Operation, EcoStruxure Security Expert. Environment EcoStruxure Building Operation Enterprise Server (ES) EcoStruxure Security Expert Smart Connector Integration EcoStruxure Web Service (EWS). Cause When significant changes are made to object names in the system, the Smart Connector may retain outdated data. If a standard Discovery does not update these names, the most effective solution is to clear the Smart Connector database and re-establish the connection.   Resolution To clear the outdated data from the Smart Connector:   Step 1: Access the Smart Connector Portal Open a browser and navigate to http://localhost:8082 (assuming Smart Connector is installed locally). Log in to the Smart Connector Portal. Step 2: Delete the Existing Processor Configuration Go to Configurations → Processor. Locate the Security Expert Discovery Processor. Click the Delete (bin icon) next to it. ⚠️ Do not delete other processors (e.g., Alarm Processor). Step 3: Delete the Existing EWS Server Navigate to the EWS Servers section. Locate the SecurityExpertServer. Click the Delete (bin icon) to remove it.   Step 4: Reconfigure the Processor and EWS Server Follow the instructions in Section 4.4 of the referenced document [1] to: Add a new Security Expert Discovery Processor Configure a new EWS Server Allow 10–15 minutes for the initial discovery process to complete. This will create a fresh snapshot of the current Security Expert database. Once the discovery is complete: Refresh the Hardware folder in EcoStruxure Building Operation. Rehost the new EWS objects as needed. Step 5: Verify Alarm Processor Configuration After re-adding the EWS Server, ensure the Alarm Processor is correctly configured to reference the new server. Refer to Section 4.5 of the same document [1] for detailed steps.   Reference [1] Refer to the official integration guide documentation for more information. Security Expert SmartConnector Version 1.1.0.8 - Installation & User Manual  

Warning Hazard of Electric Shock: Remove all power from all devices before removing any covers or doors of the system. Disconnect power at the device and at the power source. 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 Detector showing internal trouble. Product Line ESMI Fire Detection. Environment FFSULH2001. FFSULH2003. Cause If the analogue value of a detector measured by the panel is outside of the normal operating range (≤41 to ≥95) the panel will show “Internal Trouble” indicating that the detector is faulty and should be serviced. Resolution Replace the faulty detector.

Warning Hazard of Electric Shock: Remove all power from all devices before removing any covers or doors of the system. Disconnect power at the device and at the power source. 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. Caution While removing gateway cover: Open the gateway screws and delicately remove the top cover. Take extra care during this step, as the top cover is connected to the antenna cable via a thin wire. After opening the top cover, you will be able to see the top view of the board, please insert the active SIM card in the designated slot. Once the Sim Card is properly inserted, fix the screws back and ensure that the 4G&Wi-Fi Antenna is attached properly. If the antenna cable remains disconnected from the board, then the GSM will not work.   Issue If the flex server is not able to connect to the internet via the SIM card, Ethernet, or Wi-Fi, or is in a hanged state, a phone be used by the Flex server/Gateway for troubleshooting connectivity. Product Line EcoStruxure Building Activate Environment EcoStruxure Building Activate Flex Server EcoStruxure Building Activate Partner Portal Cause USB Tethering may be required at times during provisioning or troubleshooting when the flex server is not able to connect to the internet via the SIM card, Ethernet, or Wi-Fi, or is in a hanged state. Resolution If a a smartphone with data connectivity and a USB cable is available, USB tethering can be used to get a Flex server/Gateway online when a Wi-Fi or Ethernet connection is not established. It essentially turns a smartphone into an external modem for your Flex server/Gateway. This guide will cover both Android and iPhone, since the steps vary slightly. What you'll need: Your smartphone (Android or iPhone) with an active mobile data plan. A USB cable that connects the phone to a computer (the same one you use for charging usually works). A Flex server/Gateway. Part 1: General Preparations (For Both Android and iPhone) Ensure Mobile Data is ON: On the phone, go to quick settings (swipe down from the top of the screen) and make sure "Mobile Data" or "Cellular Data" is turned on. Alternatively, go to Settings > Network & internet (Android) or Settings > Cellular (iPhone) and confirm it's enabled. Important: If the phone has a limited data plan, be mindful of data usage while tethering, as Flex server applications can consume a lot more data than phone apps. Charge the Phone (or Keep it Plugged In): Tethering can drain the phone's battery quickly. It's best to have the phone charged sufficiently or keep it plugged into a power source while tethering. Find Your USB Cable: Make sure you have a working USB cable that connects the phone to the Flex server/Gateway. Ensure the USB cable used is a Data cable and not a charging cable. Part 2: USB Tethering with an Android Phone Video link for Demo (The exact wording of menus might vary slightly depending on the Android version and phone manufacturer, but the general path remains the same.) Connect the Phone to the Flex server/Gateway: Plug one end of the USB cable into the Android phone. Plug the other end of the USB cable into an available USB port on the Flex server/Gateway. Note: there are 2 USB ports in the Flex Server/Gateway you can connect to either port to establish USB Tethering. The Flex server/Gateway prioritizes usb0 (the top USB) interface by default for troubleshooting purpose. USB Ports   Allow USB Debugging (If Prompted): When you connect the phone, you might see a pop-up on your phone asking for "Allow USB debugging?" or similar. If you do, tap "Allow" or "OK." Access the Phone's Settings: Open the Settings app on the Android phone. Navigate to Network & Internet Settings: Look for an option like "Network & internet", "Connections", or "Wireless & networks." Tap on it. Find Hotspot & Tethering: Within the Network settings, you should see an option called "Hotspot & tethering" or just "Tethering." Tap on it. Enable USB Tethering: Inside the Hotspot & tethering menu, you will see a toggle switch labeled "USB tethering." Tap this switch to turn it ON. The switch should change color (e.g., green or blue) to indicate it's active. Check Your Flex server/Gateway is online from the Dashboard. The Gateway Status LED will be Solid Green.   LED pattern   To Disable USB Tethering (Android). Go back to Settings > Network & internet > Hotspot & tethering on the phone and turn OFF the "USB tethering" switch. Alternatively, unplug the USB cable from the phone or Flex server/Gateway. Part 3: USB Tethering with an iPhone Video link for Demo (The exact wording of menus might vary slightly depending on your iOS version.) Connect Your iPhone to Your Flex server/Gateway: Plug one end of the Lightning (or USB-C on newer iPhones) cable into the iPhone. Plug the other end of the USB cable into an available USB port on your Flex server/Gateway. Note: there are 2 USB ports in the Flex Server/Gateway you can connect to either port to establish USB Tethering. The Flex server/Gateway prioritizes usb0 (the top USB) interface by default for troubleshooting purpose.  USB Port for tethering   Trust This Device? (If Prompted): The first time you connect the iPhone to a new Flex server/Gateway, the iPhone will ask, "Trust This Device?". Tap "Trust" on the iPhone. You may need to enter the iPhone passcode to confirm. Access iPhone Settings: Open the Settings app on the iPhone. Navigate to Personal Hotspot: Scroll down and tap on "Personal Hotspot." Enable Personal Hotspot: You will see a toggle switch labelled "Allow Others to Join." Tap this switch to turn it ON. It will turn green to indicate it is ON. Important: You might see options for Wi-Fi Password or "USB Only." For USB tethering, you don't necessarily need to worry about the Wi-Fi password unless you also plan to use Wi-Fi hotspot. Check the Flex server/Gateway is online. The Gateway Status LED will be Solid Green. Gateway Status LED   Blink pattern for Internet connection   To Disable USB Tethering (iPhone): Go back to Settings > Personal Hotspot on the iPhone and turn OFF the "Allow Others to Join" switch. Alternatively, you can just unplug the USB cable from the iPhone or Flex server/Gateway Troubleshooting Tips: Restart everything: If it's not working, try restarting the phone and then the computer. Try a different USB port: Sometimes, a particular USB port on your Flex server/Gateway might be faulty. Try a different one. Try a different USB cable: Not all USB cables are created equal. Some are only for charging and don't support data transfer. Try a different cable if you have one. Disable VPN on the phone: If you're using a VPN on the phone, try disabling it before tethering, as it can sometimes interfere. Check data plan: Ensure you haven't run out of mobile data. Contact the mobile carrier: Some mobile carriers have restrictions on tethering or require a specific plan. If you've tried everything else, check with your carrier. By following these steps, you should be able to successfully set up USB tethering and get the Flex server/Gateway online using a smartphone's internet connection!