Building Automation Knowledge Base

Issue How to setup and use the Plain English Alarm function?   Product Line Andover Continuum   Environment PEAlmFunction, PERtnFunction CyberStation Alarm Workstation PE function Cause Manual configuration is required to create the Plain English alarm function and set certain registry keys.   Resolution As a function of Continuum CyberStation Alarm Engine, user written Plain English functions are automatically invoked at a workstation when an alarm occurs when an alarm is acknowledged when a return-to-normal condition occurs. The user optionally specifies the names of those functions in the Windows registry, and they will be called appropriately. Registry keys used for calling Plain English Alarm function PEAlmFunction : The name of the user-defined PE Alarm Function. (Ex. “AlmProcess”) PERtnfunction : The name of the user-defined PE Return-to-Normal Function. (Ex. ”AlmProcess”) Example of the Plain English Alarm function is as follows: Arg 1 A ' Network AliasName(16) Arg 2 B ' Controller AliasName(16) Arg 3 C ' Infinet Controller AliasName(16) Arg 4 D ' Object name(32) Arg 5 E ' Object AliasName(16) Arg 6 F ' Object Description(32) Arg 7 G ' Object Value(Numeric) Arg 8 H ' Alarm State(3) ALM,RTN,ACK Arg 9 I ' Graphic Object AliasName(16) Arg 10 J ' Alarm Enrollment Alarm Message(String) Arg 11 K ' Alarm Enrollment AliasName(16) Arg 12 L ' EventNotification AliasName(16) Arg 13 M ' EventNotification Priority (Numeric 1~255) Arg 14 N ' TimeStamp(16) Arg 15 O 'Logging Flag (1~255) ' String 1 Q String 80 AlmDir, Fnam File AlmF ' If M < 100 then AlmDir = "C:\" Q = chr(96) Fnam = NumToStr(random(Second)) OpenFile(AlmDir ; Fnam ; ".alm", WriteOnly, AlmF) Print L ;", " ; K ; ", " ; A , B , C , D , ", " ; G to AlmF CloseFile(AlmF) Endif Return Success Create the following registry keys in HKEY_LOCAL_MACHINE\SOFTWARE\Andover Controls \Continuum\Settings: PEAckFunction (REG_SZ) PEAlmFunction (REG_SZ) PERtnFunction (REG_SZ) PEMaxBufferedAlarms (REG_DWORD) PEPopAlarm (REG_DWORD) Set PEAlmFunction to “AlmProcess” Set PERtnFunction to “RtnProcess” Restart Continuum. Create PE programs in the workstation called AlmProcess, and RtnProcess with source code similar to the example function. Files will be created in the specified directory containing the alarm and return to normal information.

Issue A new Automation Server won't load in Device Administrator versions earlier than EBO 2022. A "Failed to process USB connection event for DevicePath:\\?" error is shown when adding the device.   Product Line EcoStruxure Building Operation Environment Building Operation Automation Server AS-P with Secure Boot Building Operation Automation Server AS-B Scalable Cause Secure Boot/Scalable Automation Server hardware is not supported in EBO versions prior to EBO 2022. Resolution It is not possible to install EBO versions prior to EBO 2022 in Secure Boot/Scalable Automation Server hardware. Verify the Automation Server part number to ensure it is a non-scalable/non-secure boot version. Refer to the Part Number and Hardware and Software Matrix for a list of parts numbers and their associated EBO version compatibility.

Issue Opening and running a Seven Report that uses the Calendar to define the date range feature for data after entering the values, and nothing happens. It does not pull up any data. Business Objects error is seen in the Calendar picker.  Product Line TAC INET Environment I/NET Seven revision 2.31 and higher. Seven Reports (Crystal Reports) Cause Crystal Reports has not been set up correctly on the host PC. An additional file has to be installed to handle scripts in Seven Reports. This file can be found under >Support>Sevenreport/CR_XI/PostCRSetup on the INET CD.  A read me is also located there to assist with the installation procedure: Resolution To resolve this issue, the following steps need to be implemented: Close I/NET and I/O Server Open up Windows Explorer and select the original CD Open up the Support Folder and expand it Select the CR-XI folder and run the SetupCrystalReportsXI.exe Once completed, go back into the folder again and run the Post CRSetup.exe Once this is completed, restart I/Net and I/O Servers again Open up Seven Reports again and run the associated report

Issue When using Microsoft Vista and IE 8, the calendar picker pops up a window but does not show the calendar. Product Line TAC INET Environment I/NET Seven 2.40 Microsoft Vista Internet Explorer 8 Cause Security of Internet Explorer Resolution Go to the Internet Options, Security Tab, and disable the protected mode for the Internet.

Issue Crystal Reports with I/NET 2.41 and higher Design tab is no longer available (missing) within SevenReports. Can no longer edit Crystal (Seven) Reports Product Line TAC INET Environment SevenReports (Crystal Reports) with I/NET 2.41 and higher Cause I/NET will no longer have the "Crystal Reports" Modify and Design license after May 2012. After 2.41 you must buy a separate CD for this function. Upgrades are not affected by this change. Any SAP Crystal Reports licenses used at existing installations will remain active after an upgrade. Resolution RDC version will no longer be supplied on the I/Net CD.   The NON_RDC version will still allow reports to be Viewed and Printed, as always. Modifying a "Canned" report or designing a "New" report will be impossible unless the new RDC version is installed.   This removal of the Crystal report function will start with I/Net Seven rev 2.41A and beyond.   To receive the Crystal Reports application files and license certificate, the SEVEN-REPORTS-RDC part will need to be ordered in addition to the standard I/NET SEVEN software part for each workstation requiring SAP Crystal Reports. Refer to Unable to install the RDC version for additional information and a copy of the necessary software for upgrading and installing this software.   Upgrades (from I/NET Seven Version 2.21 and above) are unaffected by this change. Any SAP Crystal Reports licenses in use at existing installations will still be active after an upgrade as long as you perform an upgrade of the existing I/NET installation.  If you perform a clean install, so you have uninstalled the previous version of I/NET, you will lose this licensing.      

Issue Unable to install the RDR version of the software.  Unable to find the RDC version of Seven Reports Product Line TAC INET Environment I/NET version 2.40 and above. Cause The Seven Report file gets installed automatically for the NORDC and blocks the RDC install. Resolution To resolve this, the Seven Reports NORDC has to be removed, and the RDC has to be installed. To accomplish this, the following steps should be followed. Open up the Add/Remove Programs Go to Seven Reports NORDC and select Uninstall Now explore the RDC CD and find the SetupCrystalReportsXI_RDC.exe file Download the attached 7zip file Run the PostCRSetup.exe Once completed, open up Seven Reports, and the ability to Modify reports should be available.

Issue A BACnet Schedule is working but not changing the point it is controlling   Product Line Andover Continuum   Environment CyberStation Schedules BACnet command priority Cause A BACnet Schedule will by default, write to a BACnet point at a certain command priority level.  However if that BACnet point is also being commanded by a higher command priority then the present value of the point will not change according to the Schedule.   Resolution Example: A BACnet Binary value is created and the operator wishes to set the value to Off. If the value is set by a Manual Operator then by default this will command the point to Off at command priority 10. If a Schedule is then created and the point is attached to that Schedule, because a Schedule's default priority is 16, at the configured time, when the Schedule tries to change the point to On it can only command that point at command priority 16 The point itself always obeys the highest command priority which in this case is command priority 10 so the value stays Off.   To correct the above scenario there are two main options: Edit the Command Priority Tab of the BACnet Point and perform a Relinquish at command priority 10 to clear out that command, at which point the BACnet object will then defer to the next highest command priority (which in this case would be command priority 16) Edit the Schedule and change the command priority on the Schedule configuration page to an appropriately higher priority such as command priority 10.     NB. In cases where a point is written to at the same command priority as another object then the point will be controlled by whichever object wrote last...

Issue The reconfiguration of the log database (run from TAC Vista Server Setup) times out. Configuring the settings, for the first time after upgrading Vista, on the SQL server tab of TAC Vista Server Setup an then clicking on apply makes the following message appear: "Log database found but needs to be reconfigured. Reconfigure Log database?". After clicking yes the reconfiguring process starts, but times out. The message states the following:  Lock request time out period exceeded. (Microsoft SQL Server, Error: 1222) Environment TAC Vista 5.1.X SQL server  Cause The SQL server is busy. When a reconfigure of the database layout (or schema) is done, all connections to the database must be stopped to prevent corruption of data. If a number of applications/clients are trying to write data to the database, the request to lock the database will time out. Resolution Close the open connections to the database and try again. Generally speaking this shouldn't occur with just Vista running. It is when 3rd party clients access the SQL data directly that this problem can occur. To help identify the problem, the Activity monitor in SQL server management studio can be used.

Issue Automation Server CPU Specifications Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Building Operation Automation Server Premium Building Operation Automation Server Basic Cause Automation Server Family CPU specifications are required for projects requirements and specifications. Resolution There are three Automation Server models, each with unique CPU specifications:   Automation Server (AS): The Automation Server (AS) has been withdrawn from sale. CPU: ATMEL AT91RM9200, ARM9 core microcontroller. Processor: ARM920T. CPU Clock Speed: 160 MHz. Automation Server Premium (AS-P): CPU: STMicroelectronics SPEAr1380, ARM Cortex-A9 dual-core microcontroller. Processor: ARM Cortex-A9. CPU Clock Speed: 500 MHz. Automation Server Bundled (AS-B): CPU: STMicroelectronics SPEAr320S, ARM926 core microcontroller. Processor: ARM926. CPU Clock Speed: 333 MHz.

Issue Can not save the Diagnostic Files from IP Controller using Building Commission Share button Product Line EcoStruxure Building Operation Environment Building Commission Cause By default, the only apps you can share are Mail and OneNote for Windows. Neither allows you to save a file to the Windows File System. Resolution Install Clipboard by Justin Chase via MS Store or link.  In Building Commission, navigate to the controller -> Device Settings -> Diagnostics Files Select either Device Report, Error Log, or Crash Report Click Share icon in the upper right corner.  Select Clipboard icon.  Click Copy button  Right-click Paste on the desktop or in File Explorer folder.

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 upgrading EcoStruxure Building Operation to version 2.0 or newer, the existing Power Manager software should also be upgraded to EcoStruxure Energy Expert to maintain compatibility Product Line EcoStruxure Building Operation EcoStruxure Energy Expert Environment Power Monitoring Expert (PME) Power Manager Cause The proper procedure is required when upgrading from older versions of Power Manager to the latest Energy Expert version. Guidance and best practices are needed for upgrading a PME server from PME 7.2 to PME 9.0. Resolution A Power Manager 1.0 site should be taken to 1.1 first, then upgraded to Energy Expert 2.0 Below are the recommendations for a side-by-side upgrade from PME 7.2 to PME 9.0: On the old server: Run the PME_8.2.iso file to do an in-place upgrade from PME 7.2.3 to PME 8.2 After completing that upgrade, the system will default to using a PME 8.2 trial license Install and run the PME 8.2 CM 2.1.0 Tool which will perform necessary actions for the side-by-side upgrade; we will use it to create a .zip file containing configuration components such as reports, dashboards, diagrams, users, devices, etc. Transfer this .zip file from the CM Tool to the new server On the new server: Run the PME_8.2.iso file to install PME 8.2 (this can be done while the above steps are performed on the old server) After transferring the .zip file from the old server, install and run the PME 8.2 CM 2.1.0 Tool on the new server and have it load the archived data from the .zip file into the program, and then write it to the system (essentially performing a PME 8.2 server to server migration) After that finishes, we can run the PME_9.0.iso file to upgrade from PME 8.2 to PME 9.0 After PME 9.0 is installed, we can activate the PME 9.0 license(s) in the Floating License Manager using the activation ID(s) that were already acquired, then remove the PME 9.0 trial license using License Manager (different from Floating License Manager) Running into issues with the install? Receiving error messages related to PME? Check out the Technical FAQ for a solution to your problem.  Links to relevant documentation and files: Where can I find documentation for Power Monitoring Expert 8.2 (PME 8.2)? Where can I download Power Monitoring Expert 8.2 installation files? Where can I find documentation for Power Monitoring Expert 9.0 (PME 9.0)? Where can I download Power Monitoring Expert 9 installation file? PME 8.2 CM Tool Exchange Community post  PME 9.0 CM Tool Exchange Community link  

Issue Satchwell AR Series 7 Rotary Actuator requires replacement Product Line Field Devices Environment Satchwell AR Series 7 Rotary Actuators installed on Air Dampers, Satchwell MB Series or MBF Series Rotary Shoe Valve Bodies. Actuator types :- ARE ARM ARX ARMS Cause Obsolescence of Satchwell AR Series 7 Rotary Actuators Resolution Replace Satchwell AR Series 7 Rotary Actuators with appropriate Schneider Electric MD Series Rotary Actuators and wire as follows :- Satchwell AR Series 7 Rotary Actuators installed on Air Dampers. ARE ARE Series 7 Wire Number 2 = MD20A-24 Wire Number 2 ARE Series 7 Wire Number 3 = MD20A-24 Wire Number 3 ARE Series 7 Wire Number 1 = MD20A-24 Wire Number 1 ARE Series 7 Wire Number 5 = MD20A-24 Wire Number 5 ARX ARX Series 7 Wire Number 3 = MD20B-24 Wire Number 3 ARX Series 7 Wire Number 2 = MD20B-24 Wire Number 2 ARX Series 7 Wire Number 1 = MD20B-24 Wire Number 1 ARM ARM Series 7 Wire Number 3 = MD20B-230 Wire Number 3 ARM Series 7 Wire Number 2 = MD20B-230 Wire Number 2 ARM Series 7 Wire Number 1 = MD20B-230 Wire Number 1 ARM Series 7 Wire EARTH = MD20B-230 NO EARTH REQUIRED ARMS ARMS Series 76021Term 3 (Open) = MD10SR-TS Blue G ARMS Series 7602 Term 2 (L1) = MD10SR-TS Not used *1 ARMS Series 7602 Term 1 (N) = MD10SR-TS Brown GO ARMS Series 7602 Wire EARTH = MD10SR-TS NO EARTH REQUIRED ARMS Series 7603 Wire Number 2 = MD10SR-T Blue G ARMS Series 7603 Wire Number 1 = MD10SR-T Brown GO ARMS Series 7604 Wire Number 2 = MD10SR-TS Blue G ARMS Series 7604 Wire Number 1 = MD10SR-TS Brown GO *1 Disconnect from the supply, label, and make safe at the supply and actuator.   N.B. Should the Satchwell AR Series 7 Actuator (not applicable to ARMS) include a wired Auxiliary Switch then the following Accessory should also be wired on the Schneider Electric MD Actuator as follows:- MD – S1 One independent SPDT 1 mA…3(0.5) A, 250 V AC Auxiliary Switch AR COMMON Wire Number S1 = MD-S1 COMMON Wire Number S1 AR N/O contact Wire Number S3 = MD-S1 N/O contact Wire Number S3 AR N/C contact Wire Number S2 = MD-S1 N/C contact Wire Number S2 MD – S2 Two independent SPDT 1 mA…3(0.5) A, 250 V AC Auxiliary Switches AR COMMON Wire Number S1 = MD-S2 COMMON Wire Number S1 AR N/O contact Wire Number S3 = MD-S2 N/O contact Wire Number S3 AR N/C contact Wire Number S2 = MD-S2 N/C contact Wire Number S2 AR COMMON Wire Number S4 = MD-S2 COMMON Wire Number S4 AR N/O contact Wire Number S6 = MD-S2 N/O contact Wire Number S6 AR N/C contact Wire Number S5 = MD-S2 N/C contact Wire Number S5   Satchwell AR Series 7 Rotary Actuators installed on Satchwell MB Series Screwed Rotary Shoe Valve Bodies. ARE ARE Series 7 Wire Number 2 = MD10A-24 Wire Number 2 ARE Series 7 Wire Number 3 = MD10A-24 Wire Number 3 ARE Series 7 Wire Number 1 = MD10A-24 Wire Number 1 ARE Series 7 Wire Number 5 = MD10A-24 Wire Number 5 ARX ARX Series 7 Wire Number 3 = MD10B-24 Wire Number 3 ARX Series 7 Wire Number 2 = MD10B-24 Wire Number 2 ARX Series 7 Wire Number 1 = MD10B-24 Wire Number 1 ARM ARM Series 7 Wire Number 3 = MD10B-230 Wire Number 3 ARM Series 7 Wire Number 2 = MD10B-230 Wire Number 2 ARM Series 7 Wire Number 1 = MD10B-230 Wire Number 1 ARM Series 7 Wire EARTH = MD10B-230 NO EARTH REQUIRED N.B. Should the Satchwell AR 7 Series Actuator include a wired Auxiliary Switch then the following Accessory should also be wired on the Schneider Electric MD Actuator as follows :- MD – S1 One independent SPDT 1 mA…3(0.5) A, 250 V AC Auxiliary Switch AR COMMON Wire Number S1 = MD-S1 COMMON Wire Number S1 AR N/O contact Wire Number S3 = MD-S1 N/O contact Wire Number S3 AR N/C contact Wire Number S2 = MD-S1 N/C contact Wire Number S2 MD – S2 Two independent SPDT 1 mA…3(0.5) A, 250 V AC Auxiliary Switches AR COMMON Wire Number S1 = MD-S2 COMMON Wire Number S1 AR N/O contact Wire Number S3 = MD-S2 N/O contact Wire Number S3 AR N/C contact Wire Number S2 = MD-S2 N/C contact Wire Number S2 AR COMMON Wire Number S4 = MD-S2 COMMON Wire Number S4 AR N/O contact Wire Number S6 = MD-S2 N/O contact Wire Number S6 AR N/C contact Wire Number S5 = MD-S2 N/C contact Wire Number S5   Satchwell AR Series 7 Rotary Actuators installed on Satchwell MBF Series Flanged Rotary Shoe Valve Bodies ARE ARE Series 7 Wire Number 2 = MD20A-24 Wire Number 2 ARE Series 7 Wire Number 3 = MD20A-24 Wire Number 3 ARE Series 7 Wire Number 1 = MD20A-24 Wire Number 1 ARE Series 7 Wire Number 5 = MD20A-24 Wire Number 5 ARX ARX Series 7 Wire Number 3 = MD20B-24 Wire Number 3 ARX Series 7 Wire Number 2 = MD20B-24 Wire Number 2 ARX Series 7 Wire Number 1 = MD20B-24 Wire Number 1 ARM ARM Series 7 Wire Number 3 = MD20B-230 Wire Number 3 ARM Series 7 Wire Number 2 = MD20B-230 Wire Number 2 ARM Series 7 Wire Number 1 = MD20B-230 Wire Number 1 ARM Series 7 Wire EARTH = MD20B-230 NO EARTH REQUIRED N.B. Should the Satchwell AR Series 7 Actuator include a wired Auxiliary Switch then the following Accessory should also be wired on the Schneider Electric MD Actuator as follows :- MD – S1 One independent SPDT 1 mA…3(0.5) A, 250 V AC Auxiliary Switch AR COMMON Wire Number S1 = MD-S1 COMMON Wire Number S1 AR N/O contact Wire Number S3 = MD-S1 N/O contact Wire Number S3 AR N/C contact Wire Number S2 = MD-S1 N/C contact Wire Number S2 MD – S2 Two independent SPDT 1 mA…3(0.5) A, 250 V AC Auxiliary Switches AR COMMON Wire Number S1 = MD-S2 COMMON Wire Number S1 AR N/O contact Wire Number S3 = MD-S2 N/O contact Wire Number S3 AR N/C contact Wire Number S2 = MD-S2 N/C contact Wire Number S2 AR COMMON Wire Number S4 = MD-S2 COMMON Wire Number S4 AR N/O contact Wire Number S6 = MD-S2 N/O contact Wire Number S6 AR N/C contact Wire Number S5 = MD-S2 N/C contact Wire Number S5   Product Information. For details of AR Series 7 ARM ARX ARE please see here For details of AR Series 7602 and 7603 please see here. For details of the MD10 SR Damper Actuator please see here. For details of MD10A please see here For details of MD10B please see here For details of MD20A please see here For details of MD20B please see here For details of MD-S1 please see here For details of MD-S2 please see here

Issue Is there a recommended  repeater for BACnet MSTP networks?   Product Line TAC I/A Series   Environment R2 G3 (Niagara) MNB-1000 Cause MSTP repeaters may be required to extend trunk length or provide isolation in the smoke purge application.   Resolution Consider B-Links which were actually used on the MSTP trunk during UL 864 testing. B-LINK-AC-S (AC powered)    B-LINK-DC-S (DC powered)   B-LINK-F-DC-S (Fiber Repeater) 

Issue The Runtime tab of an Infinet controller editor shows the maximum number of 255 for both the Infinet Error Count (InfinetErrCount) and Reconfigs.  What is the command to reset them to 0? Product Line Andover Continuum Environment Infinet controller NetController (CX9200, CX9400, Cx9702, CX99xx) NetController II (CX9680) bCX9640 Cause Having an unstable Infinet can cause both Infinet errors and Reconfigs to occur.  An engineer may want to reset the Infinet Error Count (InfinetErrCount) and Reconfigs to 0 and check how fast they both reoccur. Resolution Either execute the command from the Command Line of Continuum Explorer or create an InfinityProgram in the CX controller to reset them as below: *   Set Comm2 Reconfigs = 0 *   Set InfnetCtrlName InfinetErrCount = 0                NB  Make sure the whole path is specified!!

Issue When starting Continuum version 1.94 (64-bit OS), the main screen is blank.   Product Line Andover Continuum   Environment CyberStation 1.94 (64-bit OS) WebClient 1.94 (64-bit OS) Cause When Continuum is installed on a 64-bit OS, the Main.bmp file is stored in: C:\Program Files (x86)\Continuum\UserProfile  However the application is looking for the file in C:\Program Files\Continuum\UserProfile.   Resolution Configure the Main Menu to search for the Main.bmp file in the correct directory: In the "blank" Main menu, right-click in the white space, and select Edit Right click in the white space again, and select Page Properties In the Background File field, press the "..." button.  In the "Open" window, navigate to the  C:\Program Files (x86)\Continuum\UserProfile directory Select the Main.bmp file.  Press Open Click OK on the Page Edit window In the Edit window, press the Run Page button (looks like a Lightning Bolt) to close the Edit window Re-start Continuum (if necessary)

Issue Due to a variety of reasons it is sometimes necessary to add an offset to the value obtained from a sensor to achieve the required accuracy. For example, a temperature sensor may be reading off by 0.5 degree as compared to a calibrated high accuracy temperature measuring device used as a standard. Product Line Andover Continuum, EcoStruxure Building Operation Environment All CX controller All i2 devices All b3 devices Cause Sensor tolerance. Resolution Add an algorithm in the conversion field of the input objects to adjust the value by the necessary offset. In the example here the conversion entered could be: Elecvalue + 0.5 or Elecvalue + TempSensorOffset where TempSensorOffset is an InfinityNumeric point that has been set to the amount of offset to apply.  While this example uses a very simple conversion algorithm, the input’s conversion can be thought of as a one line PE program that can use PE system functions. Elecvalue + Maximum(TempSensorOffset, 1.5)   Note: For inputs that use automatic conversion e.g. voltage inputs and InfinityFunction is required, see How to add a calibration factor or offset value to an input using automatic scaling for details.

Issue How to add a calibration factor or offset value to an input using automatic scaling. Product Line Andover Continuum Environment Continuum Universal Input Cause If using the Conversion field to offset the ElecValue on an input that is using an automatic scale, the resulting value will not be calculated properly. Resolution For this to function with an input using an automatic scale we need to setup an InfinityFunction to do the scaling for us and then add/subtract our offset from this result.   1. Create a new InfinityFunction in the controller called “IPConvert” 2. Paste the below code (between the lines) into the function and save it. ======== 'This InfinityFunction must be called from the conversion line of the input 'This InfinityFunction will allow an offset to be applied to a universal input 'Example Conversion line in the Input - IPConvert(EngScaleTop, ElecScaleTop, EngScaleBot, ElecScaleBot, -1) Arg 1 EngTop 'Engineering Units -  Top of Scale Arg 2 VltTop 'Voltage -  Top of Scale Arg 3 EngBot 'Engineering Units -  Bottom of Scale Arg 4 VltBot 'Voltage - Bottom of Scale Arg 5 Offset 'Amount to Offset returned value Numeric Slope, C Slope = ((EngTop - EngBot) / (VltTop - VltBot)) C = EngBot + (Slope * (minimum(VltTop, maximum(ElecValue, VltBot)) - VltBot)) Return C + Offset ========== 3. Go to your inputs on that controller that need to use this function. 4. confirm that the auto conversion fields have been set to the scale range you require. 5. type the below into the conversion field, replacing the “-0” at the end with whatever offset is required. IPConvert(EngScaleTop, ElecScaleTop, EngScaleBot, ElecScaleBot, -0)

Issue What is the best method for calibrating a thermistor? Product Line Andover Continuum Environment All CX controller All i2 devices All b3 devices Input Temperature sensors Thermistors Cause There is no documentation that details how to calibrate a Continuum sensor. Resolution There is no requirement to calibrate a Continuum Thermistor sensor, Thermistors are factory trimmed to provide an accurate temperature / resistance curve to within the tolerances defined in the datasheet. One exception to this could be if the connecting cable was of excessive length to add additional impedance to the circuit, in this situation the input point conversion line could be used to subtract an offset: Enter "ElecValue - x" where x is a factor to compensate for the cable impedance. See How to add an offset to a sensor reading for further information

Issue License Administrator fails install with an "Uninstall failed, installer cannot continue" error Product Line EcoStruxure Building Operation Environment Building Operation License Administrator Cause Building Operation uses Flexera (Revenera) Software Technology for licensing. Other Schneider-Electric products may also use this technology for their licensing. Resolution Check to see if the site has other software programs/products using the Flexera (Revenera) Software Technology. Other Schneider Electric offers such as Unity Pro - IEC Programming Software for Modicon PAC, Power Monitoring Expert & TAC Vista as well as third party programs also use Flexera (Revenera) for their licensing. During installation of the Building Operation License Administrator the dialog below is shown: The default behavior of the Building Operation License Administrator installation program is to install both Building Operation License Administrator and a new local license server instance. If the default behavior is accepted, the installation program will attempt to uninstall any previously installed local license servers. If the Building Operation License Administrator installation program  does not have sufficient access rights to uninstall the license server previously installed by another product a "Failed to install Building Operation License Administrator" error will occur.   Multiple products can share a single Flexnet License server instance. If there is an existing Flexnet install then the License Server checkbox should be unchecked during installation of the Building Operation License Administrator This leaves the existing local license server installed by the other product intact, while still allowing Building Operation License Administrator to run. The license server used by Building Operation License Administrator can easily be changed by the user on the License Server Address tab in Building Operation License Administrator, if necessary.  

Issue Using a USB - serial lead to SDCU a controller. Product Line Satchwell Sigma Environment Satchwell Sigma Controllers SDCU Cause My Laptop does not have a serial port.  Can a  USB - serial lead be used to SDCU a controller. Resolution A USB - serial RS232 can be used. Plug the lead in to the laptop. For 1st time use, install the driver that comes with the lead. Goto My Computer > View System Information > Hardware > Device Manager > Ports and check the port number assigned (this may change each time the lead is plugged). Use the SDCU lead and plug this between the USB - serial lead and the controller. Open SDCU utility and set the port to that seen in item 3. Configure controller. Pinouts for the SDCU cable is as follows: