Building Automation Knowledge Base

Issue Customer database server crashed with no backup. Customer needs to re-create the access control database. What data can be recovered from the acx781's? Product Line Andover Continuum Environment Netcontroller ACX781 Hyperterminal Terminal mode Cause Customer database server crashed with no backup. Customer needs to re-create the access control database. What data can be recovered from the acx781's.? Resolution Using terminal mode into the NetController the customer can dump out from the controllers all the doors, numerics, inputs, outputs and PE code. The personnel records are not retrievable, however, as they are not stored in text format in the controller.

Issue With no CyberStation or network controller available, need to load application programs into controller. Product Line Andover Continuum Environment RoamIO2 Cause This item is not in the documentation. Resolution The RoamIO2 does not have the ability to load a dump file into a controller.

Issue The programs Run Times are running fast. Product Line Andover Continuum Environment Continuum 1.82 BCX-4040 Cause Internal Programming corruption Resolution Verify the System variable time on the controller Reload the controller

Issue An error may pop up when using Bosch RPS configuration software indicating there is an issue with the hardware key. The Bosch Panel is offline in Access Expert Product Line EcoStruxure Access Expert Environment Access Expert Hosted V3 Bosch Panel using RPS (Remote Programming Software) SafeNet USB Driver Cause The USB hardware key may not be installed or the driver needs to be updated or repaired Resolution Note: This solution assumes that the Bosch panel has been online in Access Expert before.   While working with a Bosch panel to integrate with Access Expert, the RPS software is used to configure the Bosch panel. An error may pop up indicating there is an issue with the USB security dongle that is inserted into the PC to connect to the Bosch Panel using RPS. This error typically pops up when trying to login with RPS and making the connection to the panel in RPS. "Invalid or missing Hardware Key" Steps: 1. Check to make sure that the USB dongle is inserted into the PC RPS is installed on 2. Install, repair or update the Sentinel Driver in Windows Programs and Features  Navigate to Windows Programs and Features Right Click on the Sentinel Driver Select Repair       Clicked through Next and Install Prompted to restart the PC       Note: Before restarting the PC, Exit RPS, Stop and Exit Docker, Exit Access Expert and then Restart the PC. Once the restart is completed, restart RPS and connect the Bosch panel, there should not be an error with the hardware key. Restart Docker and Access Expert. The panel should show online in Access Expert.                Additional external reference from Bosch: https://community.boschsecurity.com/t5/Security-Intrusion/How-to-correct-the-Invalid-or-Missing-Hardware-Key-message-from/ta-p/2858

Issue In the download center there are up to four files for the same version of the IOU modules firmware, how do I know which is the right file for my IOU module? Product Line Andover Continuum Environment Continuum IOU Module Cause The Neuron chip used in the Continuum IOU modules can support two different transceivers which are FTT-10A and RS-485, each type requires a different FW file. Additionally, the IOU module originally used a Motorola Neuron Chip ***, in 2001 the Motorola Neuron chip had to be replaced with a Toshiba chip when Motorola ceased production of their Neuron chips. A 3rd chip was used after, the Cypress chip. *** The AC-1 Plus, VT-1, Infistat, and LC-1 were not affected by the chip change as they did not use the Motorola Neuron chip. So you will only find 2 FW files for the same version and model these modules. Resolution 1. When up revving Continuum IOU modules first determine if the module is FTT-10A or RS-485. To determine the type lift the door cover of the IOU module and check the model written on the label. FT appended at the end of the model is for FTT-10A, RS-485 will either have 485 appended or only the model name with nothing appended at the end. If the door cover is missing then remove the inner cover and take a look at the label on the chip itself. The picture below shows an AC1-Plus FTT-10A module indicated by the FT on the label. If the label is missing you can easily identify FTT versus 485 by removing the upper part of the enclosure and inspecting the components populated in the communication section of the circuit. On the Net Controller itself (99xx or 9680) there will be an ECHELON FT component similar to the one in the picture below located in the upper right corner of the board, the Net Controller's cover will need to be removed to see the component.  2. Verify which Neuron chip (Motorola or Toshiba) is installed in the IOU module. 3. Get the appropriate FW file from the download center. R&D had to recompile for the Toshiba chip. The 20 version is the same as the 10 version and the 21 version is the same as the 11 version. Download the IO module firmware Note:  Version 10,11 are the Motorola processors  Version 20 is the Toshiba processor  Version 21 is the Cypress processor

Issue Unable to Request License in Vista 5.1 using a "Vista 5" license. Product Line TAC Vista Environment Vista Server Cause Upgrade from Vista 5.0 to 5.1 Resolution Unlike previous Vista 4 Software, upgrading from 5.0 to 5.1 is not a free upgrade. You must purchase a Vista 5.1 license or upgrade license. Also if the site has a maintenance agreement the license will be provided through that agreement.

Issue As soon as a user logs in to Workstation, there is a bandwidth usage above 50%. When logged out, it goes down to 10%. When logged in to Webstation, there are no changes to the bandwidth usage; it stay at 10%. Product Line EcoStruxure Building Operation Environment Building Operation Workstation Cause There are a lot of signals in the Watch Window. The system continuously asks for the watched values as long as the user is logged in. The system stops asking for the watched values when the user is logged out. Resolution Remove values from the Watch Window when they are no longer needed.

Issue Schedules are not unlocking or locking doors according to the dates and times specified by the scheduled events Product Line EcoStruxure Security Expert Environment EcoStruxure Security Expert Cause The Security Expert system has a number of variables that schedules take into consideration when determining control of doors and if one of these isn't configured correctly, it will affect proper schedule function and control. Resolution 1. Verify that the schedule has the appropriate dates and times set 2. Check Holiday Groups and ensure that any calendar actions created to repeat each year have the same start and end date. Having different start and end dates with a repeat can cause the action to span long periods which can affect scheduled operations.    

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 Continuum i2 and b3 field devices use the same hardware. With the exception of their -V models and the bCX (bCX9640/bCX4040) controller, they were not designed to have their firmware swapped from Infinet to BACnet (or BACnet to Infinet) in the field. Product Line Andover Continuum, EcoStruxure Building Operation Environment Continuum i2 Controllers (except -V) Continuum b3 Controller (except -V) Cause With the exception of the -V controllers, the devices were not designed to have their protocol (Infinet/BACnet) swapped in the field, however, due to changes in market needs R&D is now providing a method to allow the protocol to be changed in the field. Resolution IMPORTANT: If a RoamIO2 is available, it can be used to do the conversion without the need to have Continuum Cyberstation and Continuum controllers. https://community.se.com/t5/Building-Automation-Knowledge/Conversion-of-Continuum-devices-from-i2-to-b3-and-vice-versa-in/ta-p/448337    To convert i2 field devices into b3 BACnet (or vice-versa) from CyberStation Contact PSS and request the conversion files for the specific model(s) you wish to convert. Follow the procedure detailed below or as per the attached document. To swap the firmware of any non -V i2 device from one protocol to the other (in this case, from Infinet to BACnet b3), you use the following procedure.  For more information, see section 1.3 “Converting Infinet i2 Field Devices to BACnet b3 Devices from CyberStation” below. NOTE: This procedure was developed by Schneider Electric’s R&D and tested in the Product Support Services (PSS) lab.   Before starting the procedure, you need the following items: An I2 device(s) to be converted. A Continuum CyberStation with i2 device(s) configured and online. A special, conversion b3 upgrade file for the appropriate device model as provided by PSS A b3 bootloader file for the appropriate device model, provided by PSS Physical access to the device.  You need this to push its Restart switch or to access the switch or breaker where you can shut off power to the device to force a restart. A bCX4040 controller configured in CyberStation xP Expansion I/O Note If the device to be converted from i2 to b3 has any expansion modules attached, make sure the modules do not exceed the power capacity of the expansion port (180 mA), it has been observed that the b3 devices adhere more strictly to the 180 mA limit than the i2 devices, resulting in loss of operation on IO channels located on the Expansion Port if the power limit is exceeded.  See attached xP Expansion IO Datasheet for information on power consumption of each xP IO module.   1.2 Preparing the Field Bus for the i2 to b3 Device Conversion To ensure a smooth conversion, it is necessary that you reduce the traffic on the field bus as much as possible in order to provide the necessary bandwidth to the upgrade operations required for the conversion. Before starting the process with the conversion file, be sure to follow these instructions.    To prepare the field bus for the i2 to b3 device conversion Disable all the programs in all the devices residing in the field bus. Close all Continuum Workstations except the one performing the upgrade. In the Workstation performing the upgrade, close all graphics, List views, and anything else that could be polling data from the field bus. Make sure MS/TP field bus is on same baud rate as Infinet field bus, mainly 19.2K 1.3 Converting i2 Field Devices into b3 BACnet from CyberStation You can convert Infinet i2 field devices into b3 BACnet field devices by swapping the firmware of any non -V model i2 device. IMPORTANT: When using this procedure, be aware of the following guidelines: It applies ONLY to the firmware or communication protocol (Infinet or BACnet) of the device. It does not convert the control application in the device. Following conversion, the device’s memory is cleared, so you need to configure a new control application. It may result in a loss of critical data if not performed properly. Before beginning, ensure that all important data is backed up in the event of data loss or the device losing its application and becoming non-operational.  For more information, see section 1.1 “Introduction” above. To convert i2 field devices into b3 BACnet from CyberStation Contact PSS and request the conversion files for the specific model(s) you wish to convert. You will be provided with an application file (namely, i2920toB3920B4.500077.upd) and a boot loader file (namely, B3920BootB4.500077.upd). From CyberStation, edit the i2 device and record its Serial Number and Infinet id. Consult the General tab to locate this information. From the Runtime tab, perform a Reset to clear the device’s database. Upgrade the i2 device using the application file provided by PSS. Once the upgrade is complete, the i2 device stays Offline since its communication protocol has now been swapped from Infinet to BACnet. Disconnect the device from the Infinet field bus of its host master controller (for example, a CX9680 or a bCX9640). Connect it to the bCX4040 MS/TP field bus. (MAKE SURE MS/TP FIELD BUS IS RUNNING AT SAME BAUD AS INFINET FIELD BUS DEVICE WAS ON, NAMELY 19.2K BAUD) In the bCX4040, configure a b3 device using the appropriate model as well the Serial Number and ID recorded previously. NOTE: You will need to provide BACnet Device ID. Typically, it will be the same as the Serial Number. You can also use a Learn to bring the device online under the bCX4040 and automatically assign the model, id etc.  Refer to this Knowledge Base article on using the serial number for the Device ID.  Remember here to set the Comm Port for comm2. Restart the device either by power cycling or using the restart button. The device will come online under the bCX4040 as a b3 device. Perform an Update b3 OS operation to send the appropriate b3 boot loader file provided by PSS. Go to the Runtime tab, and reset the device once the update is finished. Once the device reboots and comes back online, you can confirm it has the right boot loader by looking at the device from the BACnet side. The screenshots that follow display the before and after results of the i2 to b3 conversion process. Before: After: NOTE 1 If Continuum system is not available it is also possible to convert i2 to b3 using RoamIO and EBO server using the following steps Disconnect device from field bus and connect RoamIO directly to i2 device. Use InfinetServiceTool to send the application conversion file to the i2 device. After the uprev operation is done disconnect RoamIO and cycle power to the i2 device Connect converted device (now a b3) to MSTP of AS-P or other EBO server that supports BACnet MSTP Perform a b3 learn operation to bring the device online Right click the b3 device and proveed to 'Device->Update firmware...' Navigate to appropriate boot loader file for the b3 model After uprev of boot loader is complete, cycle power to the b3 device. NOTE 2 Similar steps can be used to convert b3 device to i2 device. Make sure to use the V2 version of the b3 to i2 conversion files as it was found the original set of b3 to i2 conversion files did not work in some cases. Please note that once a b3 device has been converted to i2 using this procedure the device will ONLY accept conversion uprev files, attempt to uprev using regular uprev file will result in the following error:   This Uprev file does not match this type of controller. This applies to b3 to i2 conversion only, it does not apply to i2 to b3 conversion.

Issue In WorkPlace Tech 5.7.2, some selections in the menu bar at the top of the screen are missing (i.e Project and Application selections) Product Line TAC IA Series Environment WorkPlace Tech 5.7.2 Cause Disable COM add-ins on the Security tab. Resolution Click on "Tools" in the menu bar Click on "Visio Options." The Options screen appears. Click on the Security tab and un-check "Enable COM add-ins".

Issue After converting from .vsd to .vsdx Workplace Tech application, monitor tags sometimes do not work. Product Line TAC IA Series Environment Workplace Tech  Cause The application must be closed and reopened. A new monitor tag from the stencil needs to be added to the drawing Resolution Add the application to a project Monitor the application. If the monitor tags do not function, close the application and re-open it. If the drawing has been converted from .vsd to ,vsdx, add a new monitor tag from the stencil and try the monitor operation again.

Issue After uploading a Workplace Tech application from an MNL controller, Workplace Tech attempted to generate the application drawing, but aborted with an error message. Product Line TAC IA Series Environment Workplace Tech Cause The issue is related to the drawing information portion of the hex file. One or more object names, entered by the user, are longer than 31 characters in length. Although the WorkPlace Tech Tool 4.0 Engineering Guide states that long object names (over 32 characters) are permitted, it seems that 31 characters is the limit with all MNL controllers. Resolution When performing the above task with Workplace Tech 4.0.4 (running on Visio 2002 sp2), the error message is: "Error code -2032465748 Code meaning: Unknown error 0x86db98acs". When performing the above task with Workplace Tech 5.6 (running on Visio 2003 sp2), the error message is: "An unknown error was encountered while the application was generating the drawing." Workplace Tech 5.7.2 works around the naming error by truncating the first long-named object to 31 characters followed by naming the remaining objects as obj1, obj2, etc. It completes the conversion without error. Use Workplace Tech 5.7.2 to generate the application and compile it. Then take the complied hex file and use it with Workplace Tech 4.0.4 to generate an application drawing.

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