Building Automation Knowledge Base

Warning Potential for Data Loss: The steps detailed in the resolution of this article may result in a loss of critical data if not performed properly. Before beginning these steps, make sure all important data is backed up in the event of data loss. If you are unsure or unfamiliar with any complex steps detailed in this article, please contact Product Support for assistance. Issue Need to move PCT storage file to another location Product Line EcoStruxure Building Operation Environment Project Configuration Tool Cause The hard drive where the storage file resides may be full, or the space may be allocated for another purpose Resolution It's suggested to create a backup before proceeding, follow How to backup PCT 2.0 data to create a backup.   Open Hyper-V Manager Select "pct" under Virtual Machines then click "Move..." from the right-hand side menu Move "pct" Wizard Window will pop-out, click Next Select "Move all of the virtual machine's data to a single location" then click Next Select the NEW location for PCT then click Next. Check if the location is correct, then click Finish. Hyper-V will initial the process Once the Status shows the progress finishes. Click "Shut Down" from the right-hand side menu for "pct" image   Click "Stop Service" from the right hand side menu to stop Hyper-V as we need to modify the file location for PCT settings file   Open Windows Explorer and go to C:\ProgramData\Schneider Electric EcoStruxure\Building Operation\Project Configuration Tool Open the "settings" file Replace the old folder location with the new one then Save the file (I changed the folder from 'C:\ProgramData\Schneider Electric EcoStruxure\Building Operation\Project Configuration Tool' folder to 'D:\PSS\PCT 2 storage' Before modification After modification Go back to Hyper-V then click Start Service   Select "pct" then Click Start   Wait for a couple of minutes for the VM to start Go to https://192.168.10.2/ in a browser and PCT will start with all the existing projects

Warning Potential for Data Loss: The steps detailed in the resolution of this article may result in a loss of critical data if not performed properly. Before beginning these steps, make sure all important data is backed up in the event of data loss. If you are unsure or unfamiliar with any complex steps detailed in this article, please contact Product Support for assistance. Issue Need to create PCT backup Product Line EcoStruxure Building Operation Environment Project Configuration Tool Cause Users need to backup all PCT data to prevent data loss or corruption. Resolution Since PCT 2.0 virtual machine resides in Hyper-V., the process is the same as backup any VM in Hyper-V Manager. Open Hyper-V Manager: Launch the Hyper-V Manager application on your server. Select the VM: Navigate to the virtual machine you want to back up in the left pane. Right-click and choose "Export": Right-click on the VM and select "Export" from the context menu. Choose a destination: Select the folder where you want to save the exported VM files. Start the export process: Click "Export" to begin the backup process. The "Export" process will create a "pct" folder from the folder in step 4. The 3 folders under "pct" folder are the backup for PCT 2.0 with projects and server packages installed.      

Issue At the completion of the download of a WorkPlace Tech application into an LON controller, the following error window is displayed: Product Line TAC IA Series Environment WorkPlace Tech Tool release 5.x.x I/A Series MNL Controller application file Cause A default nci constant is out of range for its variable type. Resolution Verify that all nci values are valid for the SNVT type, re-compile and re-download the application. The most frequent issue that causes this error is an invalid text string value for a nciLocation SNVT.

Issue How to use an LTS80 (Lini-Temp) sensor on a 7716 as a two-circuit.  Product Line TAC INET Environment I/NET Site Cause How to use an LTS80 (Lini-Temp) sensor on a 7716 as a two-circuit.  Resolution Place a 10K ohm,1/8 watt resistor in the corresponding resistor "A" position. Jumper J22 to 15V For Fahrenheit, M = 0.21978, B = -459.6 For Celsius, M = 0.12210, B = -273.0 Using the first input on TB1 as an example, place the white lead of the sensor on terminal 1, place the orange on terminal 3 (+V)

Issue Can I use an LTS80 Lini-Temp sensor on an MR or ASC? Product Line TAC INET Environment MR ASC LTS80 Lini-Temp sensor Cause MRs and ASCs were not designed to use the Lini-Temp. Resolution This is not recommended. The accuracy is not good.

Issue Set up a two-wire LTS80 Lini-Temp sensor on a 7728 PCU Product Line TAC INET Environment LTS80 Lini-Temp temperature sensor 7728 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 10k ohm resistor in slot "A" Refer to TCON 114: Model 7728 Series I/SITE I/O Controllers Installation Guide for details.

Issue Set up a two-wire LTS80 Lini-Temp sensor on a 7700 DCU Product Line TAC INET Environment 7700 DCU LTS80 Lini-Temp sensor Cause Conversion coefficients must be set to read temperatures properly. Resolution For Fahrenheit: M = 0.17582 B = -279.4 For Centigrade: M= 0.09768 B = -173.0 Refer to TCON 095 for Resistor(s) 41-55 to clip (suggest you clip only one side)

Issue Set up a two-wire LTS80 Lini-Temp sensor on a 7716 PCU Product Line TAC INET Environment LTS80 Lini-Temp temperature sensor 7716 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 J22 to 15 VDC 10k ohm resistor in slot "A" Refer to TCON 096: 7716 PCU Installation Guide for details

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