Building Automation Knowledge Base

Issue When a specific application request exceeds the standard capability of I/NET it is sometimes possible to use XBuilder to expand possible applications. Product Line TAC INET, TAC Vista Environment I/NET XBuilder I/NET Host Tool Cause When a specific application request exceeds the standard capability of I/NET it is sometimes possible to use XBuilder to expand possible applications. Resolution This is a sample access control application to demonstrate the possibility. Minimum requirements for this are :Xenta 527 Web Server. If you wish to use Menta Programming, use a Xenta 731 or Xenta 913. Application: Customer Requests an Audible Buzzer be triggered when a door is forced open, but not shut off until the alarm has been acknowledged. Create a DO point to controller your buzzer/light/alarm indicator (buzzer DO) Create an internal AO point to function as a translator (logic AO) Add a Calc to the buzzer DO: ~(P0=C0) where P0 is the logic AO and C0 is 80 Perform a Station save In XBuilder, create a project for the 527 Web Server Insert or re-insert the I/NET network Add a connection object Drag the Flags attribute of the Doors DO point to the "from" part of the connection object Drag the Value attribute of the logic AO point to the "to part of the connection object Generate the Project and Send to Target. The response time of the buzzer coming on or going off is dependent on the Scan interval of the buzzer DO.  The reason it works is that the flag attribute of the Door point will equal exactly 80 if you have an alarm flag and the point is still in alarm (the alarm has a value of 64 and unack has a value of 16 totaling 80. See Decoding the I/NET signal "flags" attribute for more information). The door point will stay in alarm until it is acknowledged so this will stay at 80 until someone acknowledges the alarm, or puts the point in Manual/Test.  The Buzzer will not activate if the point is in Manual or Test The above solution will trigger off any alarm specified from the door editor (Door Open To Long, Door Forced, Bad Card read, etc).  Turn off the other possible alarms, or create an addition internal point labeled Door Forced.  The Door DO point can trigger an event sequence based on Forced door to control the additional point. If you do this the calc will need to be modified to ~((P0=C0)|(P0=C1)|(P0=C2))  C0=16 C1-64 C2=80. This will allow for the buzzer to be on until the point has been acknowledged and return to normal

Issue Documentation on the MSC-P-1500 Series Microsmart controller. Environment Microsmart controller MSC-P-1500 Cause Obsolete controller Resolution Click here to view the installation instructions on the MSC-P1500.

Issue Unknown meaning of object status numbers and descriptions Product Line Andover Continuum Environment Continuum Cyberstation Cause Continuum uses object status numbers and descriptions for diagnostics.  A list of these enumerations is required. Resolution See file Stsvc.txt in the Continuum directory In Continuum Versions 1.5 and higher, a new database attribute exists. This new attribute is "ObjectStatus". When the value of an object in the Continuum system is greater than zero, then an indicator icon is placed on that object in the explorer view. This indicator icon is also placed on the parent object and subsequent parent objects as applicable. This indicator icon will reveal the reason it has been placed on the object when you place your mouse over the indicator icon. This ObjectStatus attribute value is a bitwise type of attribute. ObjectStatus values and their descriptions: 0   - No mouseover, display normal 1   - Requires a Save from Controller (Parent) 2   - Requires a Save from Controller (Child) 4   - Requires a Flash Backup 8   - Object must be reloaded 16  - Object has been offline edited 32  - Object has been offline created 64  - Flash backup disabled 128 - OS update fail Combination values will display more than one description.  For example, 144 would display OS Update Fail and Object Has Been Offline Edited

Issue Workplace Commissioning Tool is showing a yellow triangle with red exclamation point on an MNB-1000 controller icon. Environment WorkPlace Commissioning Tool version 5.x.x MNB-1000 controller Cause The yellow triangle icon indicates that there is a firmware or Remote I/O Status issue on the RIO bus of that MNB-1000 controller. Resolution There are three ICON overlay symbols that can be displayed over the device icon in the WorkPlace Commissioning Tool.  These symbols are defined in the Device Icons table of Chapter 1 of the I/A Series MicroNet Commissioning Tool manual, F-27358.  Further information regarding the reason for the display of the Remote I/O Warning (yellow triangle with exclamation point) is found in Table 6.1 of that manual.  This document is installed along with the WorkPlace Tech Tool software package and can be accessed from the Help menu of the Commissioning Tool. Any R-I/O module status except Communicating OnLine is reported with the warning symbol being displayed overlaying the MNB-1000 device icon.

Issue Presented with a message saying the activation was completed but "The license file could not be found". The license was then not activated. Product Line EcoStruxure Security Expert Environment Security Expert License Activation Cause This is a credential issue. What happens during a license update is that the license is downloaded to ..\ProgramData\Schneider Electric\SecurityExpert\License folder and is then loaded from that location. If the current Windows user doesn't have the correct permissions to write or read from that folder then the process will fail and we will get the error message Resolution Go to the C:\ProgramData\Schneider Electric\SecurityExpert\License location and right-click on the folder white space and select properties.  This will bring up the properties window of the folder "License" shown in the screenshot below.  Go to the Security tab and ensure that the SYSTEM and Users accounts have  the same permissions set as what is shown in the screenshot below (specifically read and write permissions).

Issue Request to exit motion sensor seems to be causing nuisance alarms. Environment CyberStation, ACX family, AC1 family, REX motion sensor  Cause Even though the exit request variable is "On" in the door object, if the door opens and closes more than once, a forced entry alarm is created. This causes issues when the REX motion never turns off and multiple users exit the door. Resolution In Continuum controller firmware once the door is closed and locked a change of state of the REX input is required to keep the alarm shunted. To simulate this, trigger the REX motion detector and then open the door while it is unlocked. The door relocks 1 second after opening. If the door REX signal goes OFF and then ON again, the door unlocks. If, while the door is unlocked, the REX signal goes OFF and ON and OFF and ON the door can be opened and closed with no forced entry OR it can remain open and no door ajar will occur. The same is true if you do not check 'unlock on exit request' - it's just harder to test because you cannot watch the REX signal as easy as the unlock output. The key to avoiding the nuisance forced entry alarms is to let the REX motion sensor cycle quickly - have it turn on and then off after 1/2 to 1 second. The forced entry alarm will be shunted until the door relocks. Then if there is still motion at the sensor the REX will come on again and the controller will continue to shunt the alarm.

Issue Will a certain badge printer, signature pad or capture device work with Continuum? Product Line Andover Continuum Environment CyberStation Cause Certain badge printers. signature pad and cameras that have been tested and approved by ImageWare are supported. Resolution Note: ImageWare is a third party add on for Continuum, all support on compatibility questions should be directed to ImageWare at the following ImageWare Support Link. Please check the EPISuite compatible hardware list to verify whether a badge printer, signature or capture device has been tested by ImageWare. See also current device driver download page. Update as of August 2015 direct from ImageWare Systems EPI Builder Updates NEW QR Code barcode plug-in ImageWare has recently built a plug-in that provides the ability to create QR Code barcodes within EPI 6.x Designer. If you are interested in testing out this update, please let me know and I will provide you with a link for download. Camera Hardware Compatibility List: Canon cameras EOS Rebel XS, EOS Rebel T3, EOS Rebel T5 and EOS Rebel T5i Tested on Windows 7 (32-bit & 64-bit) and Windows 8.1 (64-bit) Requires IWS custom software plug-in to provide direct control and image capture from the client workstation to the camera. Plug-in is licensed and sold per client workstation. Videology cameras 1.3 MP USB Color Box Camera Tested on Windows 7 (32-bit) Camera can be used out of the box with its TWAIN driver (TWAIN data source SFT-10011 REV2.1.18). No additional IWS software plug-in is needed. 5 MP USB 2.0 Camera with Synchronized Flash and Auto Focus (24C708AF) Tested on Windows 7 (32-bit & 64-bit) Test PENDING for Windows 8.1 Camera can be used out of the box with its TWAIN driver (TWAIN driver version 2.1.22). No additional IWS software plug-in is needed. Sony camera (PENDING IWS custom plug-in release) EVI-D70 Pan/Tilt/Zoom Color NTSC Video Camera Tested on Windows 7 (32-bit & 64-bit) and Windows 8.1 (64-bit) IWS custom software plug-in provides direct control and image capture from the client workstation to the camera. Plug-in is licensed and sold per client workstation. Camera requires the dPict Aexeon LT video capture card hardware to be installed within the client workstation. Webcams EPI Builder works with most Webcams with compatible TWAIN drivers. IWS has worked with both the Logitech HD Pro Webcam C910 and C920 camera models. Most webcams can be used out of the box with its TWAIN driver. No additional IWS software plug-in is needed. Signature Pad Hardware Compatibility List: ePad-Ink Signature Pad VP9805 Tested on Windows 7 (32-bit and 64-bit) and 8.1 (64-bit) Requires IWS custom software plug-in to provide direct control and image capture from the client workstation to the device. Plug-in is licensed and sold per client workstation. Topaz SigPlus Signature Pad -L-460-HSB, T-LBK460-HSB-R and T-S571-HSB Tested on Windows 7 (32-bit and 64-bit) Requires IWS custom software plug-in to provide direct control and image capture from the client workstation to the device. Plug-in is licensed and sold per client workstation. NOTES EPI Builder typically supports the generic TWAIN driver, as well as Video For Windows (VFW). Furthermore, EPI also indirectly supports the WIA drivers, which Windows ports internally to the TWAIN driver. Each device manufacturer will provide drivers of some or all of these types with an implementation of their own specific functions. WIA is supported under certain circumstances. In each case the functions that will be present depend on the Manufacturer's implementation of these drivers. If you would like to internally evaluate any IWS EPI capture plug-in, please let me know and I will supply you with a 30 day evaluation license. Printer Hardware Compatibility List: Below are some of the current printers which we have received in house for testing.  Datacard SR300 Tested on Windows 7 Tested Mag encoder Digital Identification EDIsecure DCP360+ Tested on Windows 7 Fargo DTC 4500e Tested on Windows 7 and 8.1 Tested Mag encoder Fargo HDP 5000 Tested on Windows 7 Tested Mag encoder Magicard Rio Pro Duo Tested on Windows 7 and 8.1 Tested Mag encoder Matica Technologies XID 8300 Tested on Windows 7 Tested Mag encoder NiSCA PR-C101 Tested on Windows 7 Tested Mag encoder Zebra ZXP Series 7 Tested on Windows 8.1 (Windows 7 testing is pending) Tested Mag encoder Zebra ZXP Series 8 Tested on Windows 7 and 8.1 Tested Mag encoder IDP SMART-50L M N Tested on Windows 7 and 8.1 Tested Mag encoder POINTMAN USA  Test PENDING for October 2015 NOTE: We have tested other printers on Windows XP and they may be supported in Windows 7 and 8.1 depending on the available drivers. Also, other printer make/models are being used with the EPI software, but we only list printers that we've received in house for testing. If you are interested in having IWS test a specific make/model printer, please let us know and we will try to work with you and the manufacturer to obtain a demo printer in house to run through compatibility testing.

Issue How is the mac address (ethernet id) of the Continuum master controllers calculated? Product Line Andover Continuum Environment bCX CX9200 CX9400 CX9900 CX9600 CX9702 CX9680 ACX5720 ACX5740 Cause Mac address must be unique. Resolution The controller mac address is assigned at the factory. The first three numbers (0:40:11) are fixed and represent the manufacturer, the next three numbers ar5e the unit's serial number converted to hex. Example: Manufacturer = 0:40:11 SN = 557746 which converted to hex = 882b2 Mac address = Manufacturer + SN ~ 0:40:11:8:82:b2   Windows calculator has a programmer mode that can be used to convert from decimal to hex.

Issue What is the maximum binding count per graphic when polling OPC tags? Product Line TAC Vista   Environment Vista Server Vista OPC Server Cause There is no limit to the number of OPC tags, but performance may be affected when a large number of binding are used. Resolution The load on the Vista server should be considered. E.g. datatypes and the update period: Does an outside air temperature tag need to be updated every 10 seconds or is 10 minutes maybe more appropriate? Can binary signals be combined into a single register?

Issue AMT Event Messages Environment I/NET Seven AMT Cause AMT messages are used to diagnose certain system problems. This table can be used to interpret data when an alarm comes in, or needs to be acknowledged, the user can easily reference what is going on. This table was taken from TCON300.  This TCON is updated regularly, so to view the version which works best with your release of I/NET, select START>All Programs>I/NET>Technical Reference Guide. Look on page 3-26. Resolution Note: Most AMT Message "Event Types" are appended with the I/NET Users initials as defined in the Host Passwords.  It is also possible to see the "root" user name appear here, this is when you are using a Xenta Server that is controlling points in the I/NET system.  For example you may see the term "Control root" under the Event Type column.  This indicates that the associate I/NET point has been control by a Xenta Server.   Use this table to interpret AMT messages  

Issue Definition clarifications for Thermistor Type in Technical Reference Guide for StruxureWare Building Operation Environment StruxureWare Building Operation site with Thermistor temp sensors Cause In the image below of the technical reference guide for StruxureWare Building Operation on page 3164 the accuracy of the supported thermistors seems to be difficult to decipher or at least very hard to figure out what accuracy goes to what thermistor type. The issue is the input specifications does not clearly separate the Thermistor type (Continuum, I/NET, etc) with the accuracy. If there was a line or something to separate the accuracy definitions from each other that would help. What defines one set of values from the next? The ending of the parenthesis defines the end of the information for each sensor type, but this is not clear.  Resolution A defect has been recorded and it has been requested that in the next release of the Technical Reference Guide for StruxureWare Building Operation, this be corrected and offer clarification as to the accuracy with a Hard Return. The lines are actually separated by the end of the parenthesis, but this is difficult to decipher.  

Issue Compatible GSM Modem for use with the I/A Series G3 SMS Driver Environment I/A Series G3 Cause An externally purchased GSM modem is required to be used for sending out alarms in an I/A Series G3 system via the G3 SMS driver. Resolution The SMS driver has been tested with Siemens MC35 GSM modem. Technically the driver should work with any GSM modem providing the GSM standard has been implemented properly by the manufacturer. Product Support have tested the Siemens MC35 equivalent modems from Cinterion with the G3 SMS driver (https://www.gemalto.com/m2m). The Cinterion devices, MC35i and MC55i have been used on several sites with no issues reported.

Issue When installing Loytec NIC software the USB driver installation fails. Installing USB Drivers Failed LOYTEC NIC Driver Installer Error Installing USB Drivers: Could not pre-install Drivers Environment Windows Server 2003 setup on a domain. Cause The admin rights of the user is causing driver installation failure Resolution Even though you are logged on as a domain administrator the installation process fails at the USB driver stage. If you run the installation process by right mouse click on the exe file and then select run as. Then select the local administrator account the USB drivers will be installed correctly. Here are the screen captures of this process  

Issue Cannot login with Admin level Continuum user.  Password either lost or restricted by Object Level Security. Environment Continuum CyberStation WebClient Cause Admin level user password has been changed and/or forgotten. Object Level Security is inhibiting access to Continuum Users. Resolution Contact Schneider Continuum Product Support Services to arrange to have database sent in for repair.  The cost of this repair varies depending on the nature of the problem.

Issue Converting the entries from an MPX controller error log can be useful when there has been a software revision change. Product Line EcoStruxure Building Operation Environment EBO MPX Cause There may be an entry in an MPX error log that shows as follows: 25 I 2018-07-02 10:07:36.56 0x00006409 0x20000015 0x80018a15 0x10000134 0x18061101 Software revision change Resolution The ability to extract the firmware revision numbers from the controller error log is useful especially if you do not have the device report. Take a look at the last 2 numbers of the following line: 25 I 2018-07-02 10:07:36.56 0x00006409 0x20000015 0x80018a15 0x10000134 0x18061101 Software revision change 0x10000134  == 1.00.01.00134  (please disregard the missing 01) 0x18061101 == 2018 06 11 (ignore the trailing 01 in the hex number)

Issue Receiving "Deny Entry Sched." (Schedule) transaction message for all individuals on a single Interface (SLI). Receiving "Deny Entry Sel." (Select) transaction message for all individuals on a single Interface (SLI). Product Line TAC INET Environment I/NET Seven Traditional Elevator Control Cause In traditional elevator control, the Reader (Door Point) must have a schedule assigned for the Group / Individual to allow access to the Lift (reader) itself. Then in Floor Maps you can allocate access to the individual Floor Points. In the floor mapping you must also remember to allocate the associated floor points otherwise the Individual is not Scheduled to have access to the floor (Hence a Deny Entry Sched message is received). Recommendation is to migrate sites to Extended Elevator Control which makes this process much simpler. For details of this refer to Extended Elevator control (Step by step instructions). Resolution Under Access Elevators check that the Floor mapping is correctly set for each Floor DO point. If no DO 's are selected for that particular Tenant Schedule, the individual will receive a Denied Entry Sched when attempting to gain access to the floor. Deny Entry Sel (Selection) is received when the Elevator Reader is not selected for the Tenant / Group or Tenant / Individual. A schedule (Group or Personnel) must exists on the reader (door ) point for the Group or Individual in question. A list of all Event messages, and their descriptions, received in AMT is available in AMT Event message definitions.

Issue Receiving message that KB2919355 must be installed when installing SQL Server 2016 on Windows Server 2012R2 Product Line Andover Continuum, EcoStruxure Building Operation, TAC Vista Environment Microsoft SQL Server 2016 Windows Server 2012R2 Cause To Install SQL 2016 on Windows Server 2012R2 you must have KB2919355 installed. Resolution To install KB2919355 you must first install KB2919442.  Once this patch is installed then you will need to install KB2919355.  After this patch is installed you will need to restart the server.  After the reboot you should be able to restart the SQL server install and complete it. Links for the required patches Download Windows update KB2919442 Download Windows update KB2919355

Issue Communications from CyberStation to controller is flaky, controller goes offline during reload or while an object is under edit. Controller can be pinged consistently and access via the configuration web page works fine. Opening/editing objects randomly result in communication timeout errors. Environment CyberStation All CXs Cause Controller is online with two Continuum databases at the same time. Example: In a LAN system  with the controller is configured in the SQL server DB, a lap top running stand alone Continuum is connected to perform some troubleshooting, the controller exists in the SA database residing in the lap top. Resolution The controller MUST only be online with one ContinuumDB. Close Continuum on the machine that is looking at the second database.

Issue The delay on and delay off functions do not work correctly inside of the 700 Menta alarm block. Instead of delaying the signal for the configured amount of time, the signal is delayed for a random amount of time before being passed on or turned off. Environment Vista XBuilder Menta Xenta Server 701, 711, 721 and 731 Cause Documented defect in 700 Menta alarm block. This defect has been confirmed in XBuilder 5.1.5 through 5.1.7. Resolution This 700 Menta issue has been corrected in XBuilder 5.1.8. If using a version of XBuilder 5.1.5 through 5.1.7 the following workaround can be used. Leave the delay on and delay off settings in the alarm block at zero. Add a delay block in front of the alarm block. Set the desired delay on and delay off values in the delay block.

Issue Does TreeTech version 3.1 & 3.2 support all block types in all types of GCMs and LCMs? Product Line TAC IA Series Environment TreeTech version 3.1 or 3.2 GCM-84xxx GCM-86xxx SIM-xxxxx LNC GIM-2100 LCM-8xxxx Cause Block types supported are not listed in the Tree-Tech Engineering Guide document, F-26640 Resolution The following table lists the sub-devices supported by TreeTech 3.1 or 3.2 for each Network 8000 device type. GCM (rev 4.x & 5.x) ASDGCM (rev 4.x & 5.x) GIM-2100 / SIM-GCM (All rev)  LCM (rev 4.x)  LCM (rev 4.x)  MICROZONE-II  LCM (rev. 5.x)  LCM (rev 5.x)  PEM    MICROZONE-II  LIM    PEM      LIM   The following table lists the block types supported by each device family.  GCM 4.X ASD-GCM 4.X GCM 5.X ASD-GCM 5.X GIM-2100 SIM-GCM LCM 4.X/5.X AI AIPLC ALARM AO AOPLC APT BTUH CALEN COS CURVE DAILY DCC DEGDA DELAY DI DIPLC DO DOPLC DPT EDL EMS ENTHL FLOW HILO HOLI LIMIT LOGIC LOOP MATH MOMEN MTR MZHP1 MZONE MZRT1 MZSAT MZST1 OSS POLL PULSE PWM RAMP RESET RLCM RNET SEQ SGCM SLECT SNET SYS TOTAL TREND TSTAT VVBOX WEEK   ALARM AO APT BTUH CALEN COS CURVE DAILY DCC DEGDA DELAY DO DPT EDL EMS ENTHL FLO2 FLOW HILO HOLI LIM LIMIT LOGIC LOOP MATH MOMEN MTR OSS PEM1 POLL PWM RAMP RESET RLCM RNET SEQ SGCM SGRP SGRP2 SLECT SNET SYS TOTAL TREND TSTAT WEEK ZONE2   AI AIPLC ALARM AO AOPLC APT BTUH CALEN COS CURVE DAILY DCC DEGDA DELAY DI DIPLC DO DOPLC DPT EDL EMS ENTHL FLOW HILO HOLI LABEL LIMIT LOGIC LOOP MATH MOMEN MTR MZHP1 MZONE MZRT1 MZSAT MZST1 NIM NSCHD OSS POLL PULSE PWM RAMP RESET RLCM RNET SEQ SGCM SLECT SNET SYS TOTAL TREND TSTAT VVBOX WEEK   ALARM AO APT BTUH CALEN COS CURVE DAILY DCC DEGDA DELAY DO DPT EDL EMS ENTHL FLO2 FLOW HILO HOLI LABEL LIM LIMIT LOGIC LOOP MATH MN MNFLO MOMEN MTR NIM NSCHD OSS PEM1 POLL PWM RAMP RESET RLCM RNET SEQ SGCM SGRP2 SLECT SNET SYS TOTAL TREND TSTAT WEEK Z2HSC Z2SCH ZONE2   ALARM AO APT BTUH CALEN COS CURVE DAILY DCC DEGDA DELAY DO DPT EDL EMS ENTHL FLO2 FLOW HILO HOLI LIM LIMIT LOGIC LOOP MATH MOMEN MTR OSS PEM1 POLL PWM RAMP RAV21 RDS21 RDV21 RESET RNET SEQ SGRP2 SLECT SNET SYS TOTAL TREND TSTAT WAV21 WDV21 WEEK ZONE2   ALARM AO APT BTUH CALEN CNTR1 CNTR2 COS CURVE DAILY DCC DEGDA DELAY DO DPT EDL EMS ENTHL FLO2 FLOW HILO HOLI LABEL LIM LIMIT LLLB1 LOGIC LOOP LWC1 MATH MN MNFLO MOMEN MTR NIM NSCHD OPM1 OSS PEM1 POLL PWM RAMP RECP1 RESET RMA1 RNET ROOF1 SEQ SGRP2 SIM SLECT SNET SYS TOTAL TREND TSTAT UNTV1 WEEK WMA1 WSHP1 Z2HSC Z2SCH ZONE2 AI ALARM AO APT BTUH CALEN COS CURVE DAILY DCC DEGDA DELAY DI DO DPT EDL EMS ENTHL FLOW HILO HOLI LABEL LIMIT LOGIC LOOP MATH MOMEN MTR NSCHD OSS POLL PULSE PWM RAMP RESET RGCM SEQ SLCM SLECT SYS TOTAL TREND TSTAT WEEK   NOTE 1: Refer to the table at the beginning of chapter 4 of the GCM/LCM Programmer's Manual, F-23120, for more information on what object types are supported in specific versions or types of controllers. NOTE 2: The block types listed for the "GIM-2100 / SIM-GCM:" encompass the blocks supported by all the devices of the group.  You will be able to create any block type listed however, an error will be displayed when you attempt to download an unsupported block type into a specific controller in the GIM-2100 / SIM-GCM family.  Please refer to the controller manual (LNC, SIM-York, SIM-Trane, SIM-CCN, SIM-MTech or GIM-2100) for information on the block types supported by that controller type. The following ASD device blocks are supported by TreeTech. MICROZONE II PEM LIM AO DO EMS HOLI LOOP OSS RESET RGRP SCHED SEQ UI UTIL WINDO AO AS AT AV DI DO EMS LOOP RESET RGRP SEQ UTIL WINDO EMSA EMSD HOLI OVI RGRP RO SCHED UTIL WINDA WINDD