Building Automation Knowledge Base

Issue Sending the results of a Listview to a Report.   Product Line Andover Continuum   Environment CyberStation   Cause Available options are not commonly known   Resolution There are two ways to display the contents of a Listview in a Report.   The first method is to create a Report and set its data source to 'Listview'.  Then in the filter tab add the desired Listview as a filter. Please note that only ONE list view can be added. When the Report executes it populates data from the Listview object.   The second method is to create an HTML Report template Then the HTML Report in the Listview's Report Template field In this case the report can be invoked right from the Listview

Issue The Conversion Settings guideline is not documented. Product Line EcoStruxure Building Operation Environment Continuum Conversion Tool Infinet i2 BACnet B3 Cause Lack of information on "Conversion" column in Conversion Settings for B3 and I2 Resolution The Conversion column has the highest priority in the setting. If a formula exists then the setting below will not affect the Value.   Example The ElecValue is set to 10 for the following examples. 1. The Conversion field is empty, the ElecValue = 10 which corresponds to 100 on the Engineering scale. The Input Value = 100. 2. The Conversion field is set to ElecValue, and the ElecValue = 10. The Input Value = 10. 3. The Conversion field is set to ElecValue - 7. The Input Value = 3.  

Issue BACnet objects that are deleted from the BACnet side keep coming back. Product Line Andover Continuum Environment Cyberstation BACnet IP devices BACnet MSTP devices Cause Require to be able to find all the BACnet devices, delete the ones not required, and not have them reappear in Continuum Explorer. Resolution When BACnet is enabled, Cyberstation will automatically add devices into its database when it hears an “I-Am” message containing a Device Identifier it does not already know about. There is no way to disable this behavior without shutting BACnet off completely. I-Am messages are typically sent in response to Who-Is messages, but not always. Sometimes devices send I-Am messages when they start up for example.  Also, since I-Am’s are typically broadcast across the entire BACnet internetwork, the Cyberstation is likely to hear I-Am messages for lots of different reasons, like in response to Who-Is/I-Am sequences it’s not directly a part of.

Issue With Script Programs in Continuum we were able to check the variable time against an integer value. Like "if time>500 then...".  In StruxureWare Building Operation time is of the type datetime, no longer an integer. Product Line EcoStruxure Building Operation Environment Script Program Cause In StruxureWare Building Operation a datetime internally is now a 64 bit number, so dates can go beyond the year 2038 which was the top limit for Continuum.  Numbers in script for StruxureWare, like in Continuum are just floats ( 32 bits ) so when trying to map a 64 bit number ( the date ) into a float it is not going to work.  You will get very erroneous readings, therefore the ban. Resolution Here are some examples of the correct StruxureWare program: Remember that for the dates, you can only compare dates to dates, not dates to numbers… In general,   you CAN do the following:       compare dates to dates                ==>   if Date1 > Date2  then     add numbers to dates                   ==>    LaterDate = LastDate + 24*3600     subtract numbers from dates         ==>    EarlierDate = LastDate - 24*3600   you CANNOT do the following   compare dates to numbers                ==>   if Date1 > 500  then

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 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 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 Temperature Sensor Resistance Charts Product Line Andover Continuum, EcoStruxure Building Operation, Field Devices, Satchwell MicroNet, Satchwell Sigma, TAC IA Series, TAC INET, TAC Vista Environment Temperature Sensors Cause Temperature (°C) to Resistance Charts (ohms). Upgrading the site BMS, but retaining the existing sensors and the sensor resistance values are not known. Resolution The resistance of a sensor at a specific temperature can be downloaded below, there are a number of tables collated from different sources for a number of Schneider Electric sensors and other BMS suppliers.   In EBO, the thermistor selection in the IO module or controller does not represent the thermistor bead type, an example is the Continuum Type I in EBO, but the bead is a Type 3,. For further information regarding this see the KB article  Thermistor type selection in EBO.   The document All Sensors covers the following:   Satchwell DxT sensors are replaced by STR600, STP660, STD600, STO600 type T with shunt, and use the Satchwell T range chart Drayton DC1000, DC1100 30K6A1 is now known as STR600D, STP600D, STO600D Andover 10K4A1 TAC Inc. Vista 1.8KA1 I/A series 10K3A1 with 11K shunt INET 10K2A1 (10k Dale) BALCO 1000 ohm RTD   Older Satchwell ranges: Satchwell DW1204, DW1305, DWS1202 Satchwell DO Satchwell DD/DR Other manufacturers included: Allerton 3K3A1 Ambiflex 2012, Honeywell Aquatrol, Jel/Thorn, Trend, York 10K3A1 Schlumberger (air) 5K3A1 Schlumberger (immersion) 100K6A1 Automatrix, York, Sibe 10K4A1 Honeywell 20K6A Landis & Gyr PT100A, PT1000A   Further information regarding INET, IA, the document Thermistor Types Tables (Veris Industries) is available.  The 1k Balco resistance chart is also available.   Further information for the Continuum ACC Temp 10K Type 3 also known as 10K4A1, the document Thermistor Temp Resist Chart (Precon Thermistors) is available.   TC900 series TC900 RS-03 sensor chart   For I/A Series Controllers (MNL/MNB) Compatible sensors that have a built-in 11k shunt resistor include the TS-5711-850 TS-57011-850 TS-57031-850 TSMN-90110-850 Series Any sensor that matches resistance to temperature curve for a 10K Thermistor Type G (U.S. Sensor), Type 9 (Dale/Vishay) or Type III (ACI Series AH) can be used with the I/A Series MNL and I/A Series MNB series controllers, provided that a 11k ± 0.1% 1/8 watt resistor is wired in parallel with the sensor. The input has a range of -10 to 135 °F (-23.3 to 57.2 °C) with an accuracy of ±1% of span. Temperature / Resistance Reference Values Temperature Deg F (Deg C) Resistance Resistance Incl. 11k Shunt 32 (0) 25490 8,012 68 (20) 12,260 5,798 75 (25) 10,000 5,238 104 (40) 5,592 3,707 140 (60) 2,760 2,206 The full temperature/resistance table for the US Sensor 10K Thermistor R-T Curve Type G sensor. Please note that the controller may not be able to use the full temperature range shown in the table.  

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 At times the firmware and software on the Roam IO2 requires updating and instructions are needed Product Line Andover Continuum, EcoStruxure Building Operation Environment Roam IO2 Windows XP Windows 7 Windows Server 2003 Windows Server 2008 Windows Mobile Cause Instructions for upgrading the software and firmware are provided in the User's guide, but this article places them in an easy to find location Resolution The full instructions for installing and using the RoamIO2 software and hardware are in the User Guides: BACnet Service Tool User Guide + Software Infinet Service Tool User Guide + Software NOTE: The RoamIO2Appl2.000002.upd firmware firmware can only be updated from the BACnet service tool, the Infinet service tool does not have the update OS option.     Please see instructions for installing firmware and hardware for the RoamIO2 for an overview.  

Issue Looking in the controller error log, what does this error indicate and how do I troubleshoot it? 0x00006c0e 0x00002600 0x020a8536 0x00000000 0x00000000 error transmitting (LAN_ERR_TRANSMIT_ERROR) Product Line Andover Continuum Environment Continuum Controllers ControllerErrorLogTool error log report Cause This error can be the result of comms buffers being too full to transmit data to the LAN. Resolution Check the following: Check the scan rate of the controller to see if it is high. If high (above 1.0 scans/sec), stop programs to see which may be causing problems. Are there a lot of remote points being read or written from/to this controller? Try minimizing this traffic by limiting the number of points per program line, set COV Increment values, etc... If writing to 3rd party controllers, check how often your programs are doing this. Are they being sent each scan or only once when the value is required? Many BACnet writes per second can saturate the communications buffers and cause communications bottlenecks. Run a Wireshark capture by mirroring the controller's NIC card. This will show the traffic that is making it to the controller's NIC. See if there is traffic from 1 or more IP addresses that could be affecting the system and eliminate or reduce that traffic.

Warning COMPLEX PROCEDURE REQUIRED. The resolution of this article has many complex steps that may result in unforeseen results if not performed correctly. If you are at all unfamiliar with the requirements, please contact Product Support Services for assistance. Issue In some situations, when doing a learn on the CX/BCX controller, the learn process aborts and an error prompt pops up, "Can not learn this controller, it contains an unknown model number." Product Line Andover Continuum Environment Cyberstation CX/BCX I2/B3 Cause Learn process has been executed more than once and at least one has not completed. Some controllers that reside in the CX/BCX have not been cleared and have a duplicate infinetID with some controller in the database. Reloading the CX/BCX controller will indicate which controller has the duplicate InfinetID. Resolution It is recommended to create I2/B3 controllers manually (not by learn) to avoid this problem. If this problem happens: Open the BCX/CX controller and click "reset" Reload BCX/CX controller, from the distribution properties window to find out which controller has the duplicated InfinetID Go to the Continuum Explorer, right click the i2/B3 controller which has the duplicated InfinetID and then select "send to text file" Open the text file, change the infinetID for this controller to another number that does not exist in the database. Delete the i2/B3 controller which has the duplicated ID and import the text file. Reload the CX/BCX controller, there will be no more error. Do learn again on the commport of BCX/CX controller, that should execute successfully. For any other installation issues that also result in this error, please refer to Unknown model number error when learning I2/b3 device

Issue The object identifier of a BACnet device (device id) must be unique internetwork-wide, different vendors use different methods for calculating the device id default value. When integrating devices from different vendors sometimes it become necessary to change a device's default object id. Product Line Andover Continuum Environment bCX4040 b3s Third party BACnet devices Cause BACnet integration Resolution If the BACnet device is a Continuum device (bCX4040 or b3), Continuum provides a mechanism for changing the default device id. For a third party BACnet device, VTS can be used to write to the Object Identifier of the device in order to change the device id. Note that this will only work if the device manufacturer has made the object identifier for the device object writable. Click here to download VTS Click here to see the procedure to follow to set a third party device id using VTS.

Issue Some attributes used within Continuum PE programs on b3/i2 controllers are no longer appropriate with EBO Script programming Product Line EcoStruxure Building Operation Environment b3 Infinet Building Operation Server Script Programming Cause Some attributes used within Continuum PE programs on b3/i2 controllers are no longer appropriate or cannot be used with EBO Resolution An example of this would be the ElecValue attribute for an input or output. This can be used within the Conversion field of an input but cannot be used within a Script Program or Script Function. The Continuum example PE program for an STR502 or STR504 includes the line "If STR5xx ElecValue <= 0 then Return Upper" The correct result can be obtained within SmartStruxure by dropping the "ElecValue", so "If STR5xx <= 0 then Return Upper" Then ensure the STR5xx analog input is a Voltage type with no conversion configured. Note: The ElecValue keyword can still be used in the Conversion line of an Analog Inputs (e.g. for Counter input scaling). Some other Attributes not supported in Script Programming are: Size LogType

Issue Controller loses data following power failure or mains noise (from transients or spikes). Product Line Andover Continuum Environment All CX, ACX, i2, bCX, b3 controllers Cause Controllers are exposed to operating conditions outside their operating envelope and tested limits. This can cause them to reset, go offline or lose data. In extreme circumstances, poor installation can take controllers outside their operating envelope and cause damage requiring a repair. Resolution If a controller is setup on a bench with a clean power supply and the correct grounding, you will be able to turn off/ on the power and the controller will warm start every time. This test will confirm the controller is operating correctly, not faulty and that the software settings are correctly set for warm starting. Also that the RAM backup battery is connected and operating. If site resets, lockups, loss of memory or other corruption are seen on a site, then here are some of the installation issues to consider: Grounding - All controllers require a clean low impedance earth to sink all of the noise and emission energy a controller may be exposed to. The noise protection circuitry within a controller is designed to dissipate this energy down to earth, if this path is not low impedance the energy can cause a controller to reset or even be damaged permanently. Shared Ground - The earth cable to the Controller should not be shared with any other equipment that is a high inductive or capacitive load, these can generate noise spikes back into the controller. This includes motors (pumps/ fans etc) lighting circuits (capacitive loads), inverters (high frequency noise). Induced emissions - The controller should not be installed near any equipment that may induce excessive radiated emissions into the unit, the radiated emissions from Motors, inverters, radio & microwave equipment, lighting circuits, power wiring can all produce radiated emissions that could exceed the specified limits of the Controllers. By fitting the controllers into earthed metal enclosures you can minimize the external emissions by effectively creating a Faraday cage protecting the controllers circuitry. Power feed - The power requirements for every controller is defined in its datasheet with the defined tolerance, taking the power levels outside these limits can cause incorrect operation. Power spikes - Surges or spikes in power feeds or connection I/O cabling can cause controllers to reset, lose data or even become damaged. Fitting varistors to the power supplies and across any output loads can minimize the impact on the controller, See What Varistors should be used?. Shared Supply - The power feed to a controller should never be shared with other equipment that can generate electrical noise. Never use the same supply to power both controllers and field equipment like valve/ damper actuators in BMS systems or magnetic door locks in Access control, both actuators and the solenoids in Mag locks can generate large back EMF pulses into the controllers that can cause resets or even damage.. Fitting power filters or an external UPS on the controller can protect it from spikes on power up/ down, it is however always best to remove the noise spikes at source, so fit filters the generators, motors, contactors etc. It is also possible for the above issues to cause Infinet networks to Reconfig as well as other networking problems. Note: All controllers are approved and tested to the defined limits for FCC and CE induced and radiated emissions as detailed in the datasheets, for a controller to fail, restart or lose data it must be exposed to levels exceeding these specifications. They are not however power equipment and cannot be exposed to the noise levels power and industrial controls equipment is designed to withstand.

Issue What new features are planned for inclusion in future product releases? Product Line Andover Continuum, EcoStruxure Building Operation, Field Devices, Satchwell BAS & Sigma, Satchwell MicroNet, TAC IA Series, TAC INET, TAC Vista, EcoStruxure Access Expert, EcoStruxure Security Expert Environment All product ranges Cause Information required on future Product Marketing plans. Resolution This document is no longer published on the Download Center by Product Management. For further information on the future product planning please contact the Product Manager for the specific product in your region. Americas: Americas.EcoStruxureBuilding@schneider-electric.com EMEA: EMEA.EcoStruxureBuilding@schneider-electric.com Asia Pacific & India: AsiaPac.EcoStruxureBuilding@schneider-electric.com

Issue How to use the Telnet command to troubleshoot network connectivity and check for blocked network ports. Product Line TAC INET, TAC Vista, Andover Continuum, Satchwell MicroNet, Satchwell Sigma, TAC IA Series, Field Devices, EcoStruxure Building Operation, Other, Pelco, EcoStruxure Building Expert, Access Expert, Security Expert Environment TCP/IP Communication Command Prompt Telnet Command Cause Suspect certain network ports are blocked and need to verify Resolution Note:- Telnet operates using the TCP protocol. UDP connectivity cannot be tested using Telnet.     Open Windows Command Prompt Enter :telnet <address_of_remote_server> <port_number>" - telnet 192.168.1.2 443 Result if Port open: blank window with blinking cursor Result if Port closed: error message displayed similar to "Connecting To 192.168.1.2…Could not open connection to the host, on port xx: Connect failed" The example above test for connectivity against the remote server that has the IP address of 192.168.1.2 over port 443