Building Automation Knowledge Base

Issue Set up a two wire LTS80 Lini-Temp sensor on a UC Product Line TAC INET Environment UC microcontroller LTS80 Lini-Temp sensor Cause Conversion coefficients must be set to properly read temperatures. Resolution For Fahrenheit: M = 0.4235 B = 32.0 For Centigrade: M= 0.2353 B = 0.0 The sensor's white (WHT) wire goes to AI-X of the UC input, and the orange (ORN) wire goes to +15v of the UC input. Refer to TCON 069 for details.

Issue Direct substitute for the obsolete CSI Lini-Temp sensors Product Line TAC INET Environment I/NET Cause Need a part number to replace a discontinued part Resolution Yes, there is a direct substitute for the 2-wire and 3-wire versions of the old Lini-Temp sensors. The company is ACI (Automation Components Inc.). For this substitute, use the ACI/592-10K Series sensors attached. Their website is located at http://www.workaci.com/. If you are not sure what ACI Product matches the old CSI product, their Customer Service or Sales Engineers are knowledgeable in the CSI Product line. They will be glad to help you with your selection.  

Issue Set up a two-wire LTS80 Lini-Temp sensor on a 7718 PCU Product Line TAC INET Environment LTS80 Lini-Temp temperature sensor 7718 PCU Cause Lini-temp is a type of temperature sensor that is compatible with the I/NET product line. Resolution For Fahrenheit: m = 0.21978 b = -459.6 For Centigrade: m = 0.1221 b = -273.0 J31 to 15 VDC 10k ohm resistor in slot "A" Refer to TCON 106: 7718 PCU Installation Guide for details

Issue What purpose does Scan Interval serve on the point? Product Line TAC INET Environment All versions of I/NET software. Cause Understanding the Scan Interval on I/NET Points. Resolution The Scan Interval determines the length of time that elapses between scans. The controller scans the point based on the value set here (1-255 secs) and then updates the state/value on the screen. Common Concerns for Choosing Scan Intervals. The Scan rate determines how often the point display is updated in either the controller summary or a graphics page. The fastest the page will update is based on the Monitor refresh interval set in the Host Configuration Editor. The Scan interval determines when the calculation on a point is run. This means if the point has a 10-second scan interval, the calculation will only be run every 10 seconds. It is advisable to only use calculations that do not require running faster than that, as it can waste system resources. If you have a situation where logic requires an immediate response, use DDC or an event sequence. The Scan interval is used to determine when an indirect point goes OLD.  It will go old if the indirect point requests data from the global point and does not receive it after two scans.  Global and indirect points should typically have higher scan rate values.   The Scan Interval does not affect how often a global point broadcasts data. This is determined by the broadcast change in the counts setting or by a change of value for a discrete point. Higher values are usually better when dealing with scan intervals. This prevents hunting in DDC and the accumulation of old data. Whenever one point references another, these points should have identical scan rates. Problems have been reported on systems where the receiving point scans faster than the sending point. When dealing with points that send or receive data from outside of the physical device, consideration should be made to ensure all points on a given LAN segment are not broadcasting at the same time. The ideal solution is to use prime numbers for scan intervals on this type of point. For more information on Global and Indirect Points, see I/NET Global and Indirect Points Overview and Recommendations  

Issue I/NET Server (Remote Client Configuration) can not connect to I/NET network even though the workstations (other Hosts) can. All workstations (I/NET hosts) transactions are not updating, but alarms and messages are. Product Line TAC INET Environment I/NET Seven Remote Client Configuration Remote Desktop / Terminal Services Cause Unless the Remote Desktop is configured for a single user session, it's extremely likely that multiple instances of the INetIoSrv.exe will be established. This will cause issues with I/NET, such as described above. It is strongly recommended that an alternative method of remote connection be used. Resolution An alternative remote connection should be used. We recommend VNC, Ultra VNC, WinVNC, or a similar protocol. This will ensure that multiple user terminal sessions do not open. Remote Desktop can also be configured for single-user operation, but the above software packages are the preferred remote connection method. See the following external site on "How to force a single session Remote Desktop session per user." http://remotedesktoprdp.com/Force-Single-Session-Allow-Multiple-Sessions-Per-User.aspx  

Issue Configuring a Xenta 527/NPR - Combo Product Line TAC INET Environment I/NET site with a Xenta 527 End of Commercialization of TAC INET Building Management System Products Cause How to configure a Xenta 527/NPR - Combo Resolution When setting up a Xenta 527 NPR or Combo Unit for the first time, there are six basic steps to commissioning the Xenta 527/NPR-Combo. These steps are described below. Connect the Xenta 527/NPR-Combo to 24 VAC power. Refer to the TAC Xenta 527 Installation Instructions (0FL-3956). Connect a PC to the Xenta 527/NPR-Combo. Attach a serial cable from the computer’s COM port to the RS-232 B port on the front of the Xenta 527/NPR-Combo. Refer to TAC Xenta 511/527/911/913 Handbook (0-004-7870) for complete instructions. Set the Xenta 527/NPR-Combo's communication parameters. Start a Hyper Terminal Session on your PC. Once the cable is connected, it will display the 527's default information. Note: The factory default login/password is root/root, at the dsh> prompt, type inethost then enter. Now add your I/NET information for reference host, etc. Restart the unit, when the "dsh>" prompt appears, type setip then enter this command will let you set its IP address and other basic parameters. Note: Refer to TAC Xenta Server Manual - TAC Xenta 527/NPR-Combo Supplement (0-004-7682-1) Chapters 3 & 5 for instructions. Once completed restart the unit again. Connect the Xenta 527/NPR-Combo to the Ethernet. Attach the Xenta 527/NPR-Combo to the network at the necessary location. Refer to Chapter 4, “Connecting the Xenta 527/NPR-Combo to your Network. Now ping the unit through the cmd prompt on your PC to verify that communications is taking place on the Network. If necessary, load the Xenta 527/NPR-Combo’s software. Note: The Xenta 527/NPR-Combo is delivered from the factory with preloaded software. If you need to reload this software, you can download it from the EcoXpert website. Before installing downloaded software, review its release information to verify compatibility with your hardware. Configure the Xenta 527/NPR-Combo to communicate with I/NET. In order for the Xenta 527/NPR-Combo to communicate with I/NET devices from across an Ethernet, you must first define basic communication parameters. Tip: You can now access the I/O configuration editor by opening NP Routers. From the Netplus Router Summary, select the router, modify it, and print the configuration for your records or the customers. Once these steps are followed, your unit should be online, communicating to the Network, and seeing all your controllers at this site.

Issue There is currently no summary KB article for all the data collection available in EBO systems. Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Enterprise Central Building Operation Workstation Building Operation Webstation Building Operation Automation Server Premium Building Operation Automation Server Bundled Cause Identified the need to review data from EBO to analyze performance or issues. Resolution Purposes for Data Collection Provide visual information about the issue Screenshots (from Windows Snip & Sketch or other tools) Video Capture or Mobile Device Video Device LEDs, provide any information about them and when they change. Provide information about your configuration/installation Network devices, including routers, switches, and any configuration you can provide BMS Routers Site Topology, including all devices included in the communications path Provide server (EC/ES/AS) XBK backup Configuration only is smaller and useful when investigating configuration, bindings, and/or programming All Data is larger and recommended when need to see trends or events to help investigate the issue's timeline. Provide any information to replicate the issue. Provide as specific as possible steps used to create that outcome Provide VERSIONS of ALL software, hardware, and protocols involved If submit any captures or logs, perform the following: Provide any steps performed in EBO during the capture or log with the date & time, so these events can be matched.   Servers (EC/ES/AS) Collect logs from an Automation Server Collect logs from the Enterprise Server and Enterprise Central Backing Up EcoStruxure BMS Servers Manually  (Configuration Only or All Data) Server Fieldbus Protocols Infinet: Gathering Trace Log information for the Infinet bus in EBO Lon: (Video included) Analyze Lon communication using trace log in EBO Modbus: Capture a Modbus trace log in EBO/SBO   Software EBO Webstation Collect EBO Webstation browser logs EBO Workstation Collect EBO Workstation logs EBO Project Configuration Tool (PCT) Collect log files from Project Configuration Tool (PCT) Windows Review the Windows Event Logs. What specifically happens when an error occurs? Follow this KB article to view and save the Windows Events: Viewing, Saving, Sharing Windows Event Logs for Troubleshooting Purposes Wireshark For extended period capturing, use this article to set up a Ring Buffer in Wireshark. Wireshark capture ring buffer for continuous capturing Hardware b3/Infinet Controller Collect log from a b3 or Infinet controller BACnet/IP Controller Workstation method - BACnet/IP Controller Diagnostics Building Commission method - Viewing and Exporting Diagnostic Files (WebHelp) or Viewing Diagnostic Files (YouTube)   Protocols & Electrical Interfaces Ethernet Capture any ethernet traffic, including IP: Using WireShark to analyse communications on an Ethernet network Capture Loopback (127.0.0.1) traffic between applications and/or servers running on the same host OS: How to capture localhost traffic with Wireshark to help troubleshoot EWS communication issues Lon Using Loytec LPA with SpaceLogic Server AS-P RS-485 Fieldbuses include BACnet MS/TP, I/Net, Infinet, Modbus RTU BACnet MSTP Capture Application - Communities (se.com) aka mstpcap.exe BACnet - PicoScope Basics Picoscope Configuration for Modbus RTU capturing and decoding

Issue Pressing the Read Card button in the User object instantly crashes the Security Expert Client. Product Line EcoStruxure Security Expert Environment Security Expert Client 4.2.259.19 and earlier Cause There was an issue when attempting to assign new card details to a User by pressing the Read Card button on one of the Card Number slots will crash the client. Read Card Resolution This was fixed in Security Expert version 4.3. Other methods for adding new credentials to Users also include: Manually adding the Facility and Card Numbers to an available slot in the User object. Badging the card at a Card Reader and right-clicking the resulting access event in the Status Window and selecting to add to an existing or create a new User. Use the Data Sync Service to import Users, and changes to Users, from CSV files. See Mass importing User Photos into Security Expert using Data Sync Service for an indication of how the Data Sync Service is configured.

Issue Getting error "Failed to run: import-VM" when trying to install PCTv2 Product Line EcoStruxure Building Operation Environment Building Operation Project Configuration Tool (PCT) Cause Could install PCTv2 fine but the issue started when going back and forward between PCTv1 and PCTv2 so that might have caused the issue. Resolution Uninstall Hyper V in Windows Programs and Features and restart computer Delete everything in ProgramData\Microsoft\Windows\HyperV Install PCTv2 version 2.0.2.13 or later

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 Project Configuration Tool generates a 'failed get matching version' error when attempting to start an existing server Product Line EcoStruxure Building Operation Environment Project Configuration Tool (PCT) Cause The associated PCT server package files are not installed, cannot be accessed or are corrupt Resolution The "get matching version error" can occur when the associated server package files are not installed, cannot be accessed or are corrupt.  Try the following steps:   Check the associated PCT server package is installed, click manage packages (1) and check the Manage packages window (2)   Install the package if it is missing and then attempt to start the server If still unsuccessful, reinstall the server package and then attempt to start the server When installing the package if the error below occurs navigate to 'C:\ProgramData\Schneider Electric EcoStruxure\Building Operation\Project Configuration Tool\logs' and open the ConfigurePCT.log file to try and identify the problem                                                                                                  In the case the server package config file is corrupt navigate to the server packages folder at 'C:\ProgramData\Schneider Electric EcoStruxure\Building Operation\Project Configuration Tool\external\VM\cfg' and delete the associated *.cfg file.      Reinstall the server package and then attempt to start the server Additionally consult PCT error installing EBO package for further suggestions

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 How to uninstall PCT 2.0. Product Line EcoStruxure Building Operation Environment Project Configuration Tool. Cause The uninstalling instruction isn't documented. Resolution Launch Hyper-V. Shut Down PCT VM. After the VM is shut down, select Delete from the bottom right window. Select Delete if the confirmation window prompts. It may take some time depending on the VM size.   Go to the VM location selected during the PCT installation The default installation path is  "C:\ProgramData\Schneider Electric EcoStruxure\Building Operation\Project Configuration Tool 2.0"     Right-click on the pct folder then select Delete (This action will delete all the data in PCT including projects and servers created)    

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 During the installation of PCT 2 and 'Starting VM pct' step, one encounters the error: "Error: System.InvalidOperationException: Failed to run: Start-Vm -Name pct". Open Hyper-V Manager and confirm the 'pct' VM was created. Manually trying to start produces this error: Product Line EcoStruxure Building Operation Environment Project Configuration Tool 2.0 Cause Hyper-V is not set to start on boot automatically. Resolution DO NOT perform these instructions if PCT 1 is installed on the same OS. Contact Product Support for assistance. Launch Command Prompt as Administrator. Type: bcdedit /enum​  Ensure 'Hypervisorlaunchtype' is not 'Off' and set to 'Auto' by running the following command: bcdedit /set hypervisorlaunchtype auto​ Reboot the PC Rerun PCT 2 installer

Issue Does the part number, ENS-MOD license the Enterprise Network Server for both Modbus TCP master and slave functions? Product Line TAC IA Series Environment I/A Series G3 Enterprise Network Server Cause The Enterprise Network Server needs to function as a Modbus master or slave device.  ENS-MOD only licenses the Enterprise Network Server to function as a Modbus master device. It does not license it to operate as a Modbus slave device. Resolution ENS-MOD only licenses the Enterprise Network Server to function as a Modbus TCP master (client) device. As of 2013, the ENS can also be licensed as a Modbus TCP Server (slave) using the part number ENS-MOD-SL. 

Issue Configure REX button to be able to permanently lock or unlock a door if pressed for a set amount of seconds. Product Line EcoStruxure Security Expert Environment Security Expert Server Cause REX button does a momentary unlock then relatches the door. Would like to unlock or lock doors using the REX as determining factors are too dynamic to use a schedule. Resolution What is needed 2 Inputs (A & B) 4 Outputs (A, B, C, D, & E) 4 Programmable Functions (A, B, C, & D) 1 Dummy Area (Test Area) 2 Input Types (Input Triggers Output & Input Toggles Output) 1 Door with REX connected (Door X) Inputs Input A (REX Button) General Tab Control Output: Output A Areas and Input Types Tab Area: Test Area Input Type: Input Triggers Output Input B General Tab Control Output: Output E Areas and Input Types tab Area: Test Area Input Type: Input Toggles Output Input Types Input Triggers Output Options 1 Tab Generate Alarms checked Options 3 Tab Activate Input Control Output on Alarm checked Deactivate Input Control Output on Restore checked Input Toggles Output Options 1 Tab Generate Alarms checked Options 3 Tab Toggle Input Output State checked Outputs Output A, B, C, and E are just standard virtual outputs Output D General Tab Activation Time (seconds): the amount of time you want to hold the REX to activate the unlock/lock (I.E. 5 seconds would require you hold the REX button for 5 seconds) Programmable functions: Programmable Function A: Type: Ripple Output Output to trigger: Output A Stage 1: Output B Stage 2: Output C Inter Stage on Ripple Time: 5 Programmable Function B: Type: Logic Control Logic Function Mode: 7 Follow Logic And First Output to Check: Output A Second Output to Check: Output C Output to Control: Output D Programmable Function C: Type: Input follows Output Input follows Output: Input B Output to follow: Output D Programmable Function D: Type: Door Control Door Function Mode: 0 Follow and Test Output Door control Mode: 1 Latch Door unlock Output to Check: Output E Door to Control: Door X Make sure you right-click each programmable function and start them. Go to the Test Area and set it to Armed.

Issue Project Configuration Tool 2 can't be installed due to error "An error occurred trying to start process 'powershell' with working directory. The system cannot find the file specified." PowerShell can't also be started by Command Prompt, as shown in below screenshot, with error "'PowerShell' is not recognized as an internal or external command, operable program or batch file."   Product Line EcoStruxure Building Operation Environment Building Operation Project Configuration Tool (PCT) Cause Windows PowerShell path is not added to PATH environment variable, so it cannot be started by PCT installer.  Resolution Add PowerShell path to PATH environment variable by following below steps: Using Start menu, search for "Edit the system environment variables".                            Click on "Environment Variables".    Double click on "Path" variable located in the system variables list. Click New and add PowerShell path to the list then save the changes. %SYSTEMROOT%\System32\WindowsPowerShell\v1.0\     Try to start Power Shell in Command Prompt. If it can be started as shown in below screenshot, retry the PCT 2 installation.   

Issue Debugging SpaceLogic MP and RP controllers Modbus RTU Product Line EcoStruxure Building Operation Environment Building Operation Multi-purpose Controller Building Operation Multi-purpose VAV Building Operation Room Controller (RP-C) Building Operation RP-V VAV Building Operation EZLogic RP-C Building Operation EZLogic RP-V Cause There is no packet data can be logged or viewed for Modbus MP and RP controllers and RP controller has no transmit and receive LEDs for the Modbus and no packet data can be logged or viewed. Article Modbus in the MP and RP Controller Introduction provides information on the differences between the Automation Server and MP and RP controllers Modbus operations. Resolution There are a couple of options, but they involve using another device connected to the Modbus network to view the packets Use a PC based Modbus slave simulator Use an Automation Server set up as a Modbus RTU slave, the packets can be sent to the trace log then viewed in the usual way.  Note: A defect with v3.2.1 EBO means this solution cannot be used to monitor a Modbus RTU bus because the AS replies to all requests and may cause conflicts on the network. All versions 3.1.2 and earlier work fine, as well the EBO 2022 (v4.0.1) as detailed in the Known Issue Modbus Slave incorrect response Can use Picoscope to perform Serial Decoding for Modbus RTU as detailed in Picoscope Configuration for Modbus RTU capturing and decoding

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 Modbus RTU communication is not performing as expected, and there is a need to review electrical installation or request/response packets. Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Building Operation Multi-purpose Controller Building Operation Room Controller Building Operation EZLogic Room Controller Cause Picoscope hardware and software provide the ability to review the electrical waveforms and decode as Modbus RTU Resolution Ensure proper setup and connection of Picoscope probes Set the switch on probes to 1X Connect the probes using the color coding on each end to ensure the connection is as follows: Connect Probe A to TX/RX - Connect Probe B to TX/RX + Connect the probe black reference alligator clips to the cable shield drain wire. Ensure the drain wire is connected to EGND at one location. Connect the Picoscope to the PC, then open Picoscope software and choose the device connected. Set the Scope Use 1 ms/div for 38400 baud Follow this thread for more information since BACnet and Modbus are both RS-485 protocols. BACnet - PicoScope Basics - Schneider Electric Community  Select Channel A Set to +/- 5V Select Channel B and repeat the setting. One may change to +/- 10V if you encounter spikes above the 5V range (overvoltage warnings).  Add Math Channel Click the Math Channels icon Select A - B  Add Serial Decoding for Modbus RTU Click Serial decoding icon Select MODBUS RTU On Page 1 select Master A - B Change Baud Rate to known baud rate, usually 38.4 kBd Change Parity to known parity, usually NONE (1 Stop Bit) Leave the rest at default and click Next  On Page 2 Recommend leaving as default of HEX, knowing you will have to convert for Slave IDs over 09. Leave the rest at default and click Finish  Set Waveform Adjust thumbnail size to preference Leave Capture Time = On (default) Set Max Waveform to 2000 (example has 5000)  Start and stop capture and select Waveform as example Set Trigger Using a waveform, set the threshold voltage just above the blue line voltage. For example, the blue line is at 0.8V, and the threshold is set at 1.92V. Adjust based on your collected waveform(s) Set the Pre-Trigger 0% puts Yellow Diamond to the left and 100% puts Yellow Diamond to the right. The recommended setting is between 5% and 20% (for example, 20%).  Start capturing Set Serial Decoding for MODBUS RTU to show buffer The Current Buffer shows only the waveform on the screen.  All Buffers show everything.  NOTE: The Buffer Number column references the waveform number

Issue Since the Cloud Plugin cannot perform search operations on EBO, Building Advisor can only estimate the number of forced points using the event log and, for EBO versions above 3.2.1, the server archive.  Product Line EcoStruxure Building Advisor Environment BMS Health Cause 1. Incomplete Event Log: The event log may be incomplete if the maximum capacity is reached in EBO (events are rolling). When a customer connects their system, some historical events may be missed. 2. High Event Production: If a customer's system generates events at a higher rate than BA can process (currently, BA can ingest 100,000 events every 6 hours), some events may be overlooked, especially if there are many noisy events. 3. Understanding of Events: BA can only recognize forced and unforced events. BA will lose track of that point if an object's absolute path is updated or deleted instead of being unforced. 4. External Tools: BA cannot track it if an external tool forces a point without creating a corresponding forced/unforced event in EBO.   Limitations with EBO Versions 3.2.1 or higher: Building Advisor can resolve issues for each server by retrieving snapshots from the server archive. This method can address the abovementioned issues, except for point number 4. Additionally, Bacnet points forced via commands are unavailable in the server archive, meaning we cannot retrieve those values through the Cloud Plugin. Resolution Check the EBO Version, and If the customer's system is older than version 3.2.1, advise them to upgrade. Verify Server Archive, ensure the issue pertains to Bacnet points, and proceed to the next step. Ensure all servers associated with the mismatched forced items have an updated server archive. This will enable the Building Advisor (BA) to obtain the correct snapshots from the system. You can check this in the building's BA connectivity tab.  If the servers are updated, proceed to the next step. If they are not, ensure that server backups are created periodically. You can check this in the BA architecture tab under the backup section.  If a newer backup is present compared to the "Last Upload" in the server archive table, attempt to send it again. Refer to the instructions on how to send a new backup at the end of the file. If there isn’t a newer backup, create one and send it. Important: Please note that it may take one to two days for the Building Advisor (BA) to reflect the updates. If the object exists in EBO, retrieve the events from the relevant branch and filter for force-type events.  If the last event is unforced and BA is showing as forced, Force it and then unforce it one time. If it was a Bacnet point, try to force it from the basic tab.  Note: If you have multiple points, you can search using the appropriate criteria and perform all the force/unforce operations simultaneously.  If the object no longer exists in the path, you can create a replica of the object in the same path and perform the force/unforce operation. Ensure that events are created for your actions (see Step 5). If the point does not exist for manual override and you cannot set a new device in the path, please open a PSS case. Send a new backup using the following process: Navigate to ~/System/Modules/CloudPlugIn/Statistics/Services Add the Service type and Server name columns in the list view Locate the Service Type of SystemDiscovery, multi-select the server(s) affected, right-click, and select Execute task now If the issue is unresolved two days after uploading the updated SystemDiscovery files, please open a PSS case.

Issue What TAC Vista 5 license is needed to communicate with TAC 9000, TAC 6501, TAC 6505, TAC 6580 or TAC 6585?   Product Line TAC Vista Environment Vista Server Cause The communication module for these types of controllers are not included in the TAC Vista server license  Resolution You need a System 7 license

Issue Why do we get different settings when TAC Vista is running as a Service compare to started normally? Product Line TAC Vista Environment Vista Server Cause When TAC Vista is running as a Service, it is using "System user", and not the same user that is logged in. Resolution Verify that the system user have correct settings to be able to run TAC Vista as a Service. Under Region and Language, under the tab Administrative, you find Current language for non-Unicode programs, and also a button named Change system locale...