Building Automation Knowledge Base

Notice NOTICE 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 for assistance. Issue Want to access door with 'Card only' or 'PIN only' not both of them.   Product Line TAC INET Environment I/NET Seven Access Cause I/NET has two door mode schedules, Secure, the default setting, which provides access via card number or Secure with PIN, which requires card entry AND a PIN entry.   In this case it is possible to use either card or PIN to gain access if using specialized readers that support a Wiegand PIN output. Resolution It is possible to achieve this provided the PIN output from your card reader supports one of the supported card types of I/NET (i.e. 26-bit, 32-bit Wiegand etc) you can assign a "card number" (PIN) for each individual. The PIN pad will output the entered PIN in Wiegand format and I/NET will then treat it as a normal card entry. Once the PIN pad / card reader has been configured you simply enter this into the Individual editor as the card number card and it acts exactly the same as swiping a card. What this means is that the Individual can use either their card or PIN to gain access (if entered in this fashion). So provided you have a suitable reader / pin pad (such as the P-640 Patagonia Proximity Reader from Keypad Farpointe Data, Inc (www.farpointedata.com))- here are the steps to configure this to work: In the Door editor set the reader type to Wiegand 26-bit (or other) Configure the PIN Type to 26-bit The Door mode is either left blank (Secure mode) or configured as 'Secure' Configure your Tenant (Refer to note below regarding Large Card number usage) Add your individual; The individual will have to have two card numbers associated to them: The number associated to the card, The number associated with the PIN number - what not to get confused with is that this PIN number is NOT the PIN number associated (or shown) in the Individual editor. Large Card number usage: How to calculate the "card number" if using Large Card Numbers: The following two Excel spreadsheet calculators; 26-bit and 32-bit can be used calculate you the large card number. Enter the details (Facility Code / Card number) and the calculator produces the large card number in both decimal and hexadecimal. For example if you use Facility Code 26 and card number 255, the results would be 1704191 (Decimal) and 001A00FF (Hexadecimal). Alternatively I/NET also displays this 'large card' number in the Message column if added to the Transaction window - you can use this also to ensure you have everything wired and configured correctly. How to calculate the "card number" if using the Facility Code / Card number: Once the reader has been programmed with the facility code and this number entered into the Tenant Code of the Tenant editor. The PIN number assigned to the individual then becomes the 'card number’. So for the same example used above, the Facility Code used is 26 and card number 255, the Tenant editor will have the Tenant code configured as 26 and the Individual number (ID) of 255 is used - so no card number is entered into I/NET. This ties the card number to the Individual ID. This is important and the major difference between using large card numbers and facility codes.

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 DSS error occurs while importing users into Security Expert Product Line EcoStruxure Security Expert Environment Continuum Transition Tool I/NET Transition Tool Data Sync Service Cause The Data Sync Service settings file contains a mapping for a credential named “User ID” but cannot find the User ID credential type. The User ID credential was not created before starting the Data Sync Service.  It is important to determine if the site is using user PINs and whether they are all unique before selecting the following option in the transition tools.   By default, SX does not allow duplicate PINs. A unique PIN is a requirement for signing into intrusion keypads with only a PIN number. Resolution Option 1: The site does not have user PINs in the legacy database or PINs are unique. Stop the data sync and transition services Uncheck the 'Allow PIN Duplication' option Click the 'Create Data Sync Service Settings File' button below   Delete the export history of Users   Start both Data Sync and Continuum Database Transitions services. (All users will get exported again) Option 2: The site uses PIN numbers and there may be duplicates. Keep the “Allow PIN Duplication” option checked In Security Expert, Go to Global | Sites| Site Defaults Tab Scroll down and expand the Site security enhancement section Enable the top 3 checkboxes (Require dual credential...; Auto Populate User ID... and Allow PIN duplication)   Click Save.

Issue Mobile or Cellular companies may require the modem's IMEI number to issue a SIM card for the device. Product Line EcoStruxure Security Expert Environment Security Expert SP-4G-USB Cellular Modem Cause The IMEI number is not displayed on the device labelling. Resolution The IMEI number is printed on the label on a chip inside the SP-4G-USB module. IMEI number This can be seen when looking up close through the slots in the module case and looking down through the top of the module. IMEI through bottom vent Use a phone camera to take a photo of this label so the number can be properly identified. IMEI through bottom vent

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 Services for assistance. Issue What is the procedure for replacing a CX9200, CX9400 or 99xx with a BCX9640 Environment BCX9640 CX9200 CX9400 CX99xx Convert Conversion Cause While Continuum Versions 1.91 and higher have a direct procedure for upgrading a CX9200, CX9400 or 99xx to a CX9680, no such option exists for converting a controller to a BCX9640 controller.  Resolution There is no quick and easy way to replace a 9200 (9400 or 9900) with a BCX9640.  In order to do this it will be necessary to bring the BCX9640 online as a new controller (with a new ACCID) and copy the contents of the 9200 (9400, 99xx) into the BCX9640.   Do not copy the System Variables from the 9200, 9400 or 99xx into the replacement controller. As always a backup of the Continuum database should be made prior to making any such changes to the system. External point references, point references on graphics and alarm links would have to be checked and repaired where they have been lost.  Other controllers that referenced points in the original 9200 (9400 or 99xx) will have to be corrected so that they point toward the corresponding object in the new BCX9640.  A full recommissioning of the controller may be required.  Once the conversion is complete the original controller object would be deleted from the system. While importing a text dump of the (9200, 9400 or 99xx) is another approach, this can be a messy process that requires the dump file to be manipulated.  This can lead to more substantial problems if done incorrectly.

Issue Continuum runs very slowly. Taking up to two minutes to first startup. Generally opening up Continuum Explorer and any other objects are seen to be slower than normal as well. Product Line Andover Continuum Environment Continuum v1.94 and above Cause There was no Security Key connected and Continuum was running in Demo mode.  This symptom can also be caused by a missing or corrupt driver for the Security key, see Re-install of Continuum system and security key is not being recognized for details on re-installing the Security Key driver. Resolution Install valid Security Key and restart Continuum. Note: Want to know what features are supported in Demo mode? See How do we run Continuum in Demo mode and what features are available?

  Issue PCT v1.3.3.75 fail to start SmartX server in versions 1.8.x and 1.9.x Product Line EcoStruxure Building Operation Environment Building Operation Project Configuration Tool (PCT) Cause Defect, user can create SmartX server v1.8.x and 1.9.x but the servers can't start properly. Resolution Uninstall PCT v1.3.3.75 Install PCT v1.3.2.110 (Download), (Client Installer) Install server packages 1.8.x and 1.9.x

Issue An attempt to flash the firmware in the controller results in error, "The UPREV code could not communicate with the specified controller." Product Line Andover Continuum Environment bCX CX9680 ACX5720 ACX5740 Cause Uprev operation attempted using the wrong flash file. Resolution Re-try the operation using the flash file that matches the model number in the controller. Note that regardless of what the model number reads from the InfinityController editor in CyberStation, the verification is done at the controller level. Do not go by what you see in the CyberStation as this user configured field could have been entered incorrectly. Verify the model number from the controller's web page configuration.

Warning Potential for Data Loss: The steps detailed in the resolution of this article may result in a loss of critical data if not performed properly. Before beginning these steps, make sure all important data is backed up in the event of data loss. If you are unsure or unfamiliar with any complex steps detailed in this article, please contact Product Support for assistance. Issue Project Configuration Tool generates a 'failed get matching version' error when attempting to start an existing server Product Line EcoStruxure Building Operation Environment Project Configuration Tool (PCT) Cause The associated PCT server package files are not installed, cannot be accessed or are corrupt Resolution The "get matching version error" can occur when the associated server package files are not installed, cannot be accessed or are corrupt.  Try the following steps:   Check the associated PCT server package is installed, click manage packages (1) and check the Manage packages window (2)   Install the package if it is missing and then attempt to start the server If still unsuccessful, reinstall the server package and then attempt to start the server When installing the package if the error below occurs navigate to 'C:\ProgramData\Schneider Electric EcoStruxure\Building Operation\Project Configuration Tool\logs' and open the ConfigurePCT.log file to try and identify the problem                                                                                                  In the case the server package config file is corrupt navigate to the server packages folder at 'C:\ProgramData\Schneider Electric EcoStruxure\Building Operation\Project Configuration Tool\external\VM\cfg' and delete the associated *.cfg file.      Reinstall the server package and then attempt to start the server Additionally consult PCT error installing EBO package for further suggestions

Issue What process do the bCX and b3 controllers use to automatically establish their communication bus speed. Product Line Andover Continuum Environment bCX b3 Auto Baud MSTP Cause Having issues with b3 controllers selecting the wrong bus speed. Resolution The process by which the b3 controllers establish their communication speed is as follows. When the b3 controllers power up, they listen to the network for 2.5 seconds If they hear communication at their last known Baud rate, they start talking when they hear the poll for master. If they hear no communication after 2.5 seconds, they start their own poll for master at their last known Baud Rate. If they hear garbled communication during the 2.5 second listen mode, they begin hunting different Baud Rates while listening until they have synced to the Baud Rate they are listening to. Then they join the token passing when they receive the Poll for Master. Note:  There was a issue with the autobaud process in earlier versions of the b3 and BCX40xx controllers which would cause them to set the communication speed incorrectly.  This issue was corrected in the following firmware versions. BCX40xx ==> 4.500053 b3xxx      ==> 4.500064 b-3xxx-V ==> 4.501064

Issue Is it possible to connect a number of Vista servers to the same SQL server instance? Environment TAC Vista 5.1.X in a multi server environment. Cause Customers with larger sites may wish to collect the log data from TAC Vista on one SQL server for ease of maintenance and security reasons.  Resolution There are a couple of conditions to observe when doing this: Each Vista server must have it's own database (ie. taclogdata1, taclogdata2, taclogdata3 etc). The SQL server machine must be able to handle the increased load. There must be sufficient space for all the databases. A maintenance plan must be put in place - regular defragmentations and rebuilds (See White Paper - SQL Server Best Practices).

Issue Can SLPSXC2 CO2 sensor calibration be used with both methods (ABC standard and Fresh Air process) at the same time? Product Line Field Devices. Environment Building Operation SmartX Living Space Sensor. Cause SLPSXC2 CO2 can be calibrated using two different methods. Automatic Baseline Calibration(ABC) The ABC algorithm constantly keeps track of the sensor’s lowest reading over a pre-configured time interval and slowly corrects for any long-term drift detected when compared to the expected fresh air value of 400 ppm. ABC calibration is enabled/disabled through coil 4 (invoke = enable ABC). Manual Calibration Coil 11 triggers the manual calibration (FRC 400ppm) => this will tell the sensor that the current level of CO2 should be interpreted as 400ppm. When setting this register to 1, it automatically goes back to 0 a couple of seconds later. Setting Coil 11 to value 1 is the same as pressing the calibration button. Resolution The both methods of calibration can be used simultaneously since one method is for correcting drift over time (1 week intervals), the other is a manually executed reset.   The only error would come if the unit was exposed to high CO2 concentrations at night, inducing abnormal averages. If ABC is disabled, manual calibration would need to be performed more frequently.

Issue Can the Execution Precedence determine the priority of a program binding to a value? Environment SBO Function Block and Script programs Cause Clarification on the function of Execution Precedence is required. Resolution In both Function Block and Script programs there is an attribute called Execution Precedence, this can be set in the program "Properties", Basic tab. For a Function Block program:    For a Script Program: Execution Precedence determines the order that the programs will be run, the lowest numbers will be run first. In the 2 screenshots above the Function block program (Value 1) will be run before the Script program (Value 20). This can be used for applications where a calculation is done to generate a value, that is then used in a second program e.g. Calculation of a compensated setpoint, that is then used in a PID control program as the reference value. The PID program must have a higher Execution Precedence than the setpoint calculation. Execution Precedence does not affect priority. If the outputs of 2 programs are bound to a single value, both programs will be trying to control the value and give an indeterminate result.   To combine the outputs of 2 programs the programmer must use the appropriate logic to determine how the 2 signals should be combined for the application. So for Binary values use one of the logical operators: AND, OR, XOR etc, For Analog values combine the 2 results with Max, Min, Average etc as required.

Issue DBCreate backup access denied using Windows Server 2008 R2 Standard & Microsoft SQL 2008 R2 'Cannot open backup device ' C:\Users\Administrator\Desktop\20120919'. Operating System Error 5( Access is denied). [Microsoft][ODBC SQL Server Driver] [SQL Server] BACKUP DATABASE is terminating abnormally' Product Line TAC INET Environment I/NET loaded on Windows Server 2008 R2 Standard & Microsoft SQL 2008 R2 Cause The cause is insufficient rights to perform this function based upon a local policy of not allowing users to see the 'C' drive. Resolution Although when Using a Network Administrator account or Administrator for the local machine, you cannot open backup to either the local machine 'C' drive or a network share, you should be able to backup to a thumb drive.  Go to local disk properties - security tab Users do not have permissions to modify or write to the 'C' drive. Windows UAC may over ride the administrator permissions. Check your permissions and make sure you have rights to a folder and perform the backup. Refer to How to Troubleshoot on DBCreate for more issues about DBCreate.  

Issue By default, you are not allowed to shut down/restart the TACLIC/TAC License server when logging in to the Flexnet license admin web application from another PC than local. Product Line TAC Vista  Environment TAC Vista versions 5.1.8 and higher, using the web-based TACLIC tool.  Cause A remote shutdown/restart is required when adding/removing/editing license files in the License Files folder. Resolution The following steps should be done on the PC where the license server is located: In the "server.xml" file located in the "conf" catalogue (...\License Server\conf), edit the following string from " stopServerRemoteAllowed="false" "  to  " stopServerRemoteAllowed="true" " Then save the file and restart the license server.   The setting can also easily be changed using the tool called "TACLicenseServer Settings."

Issue 37-bit cards not working correctly even though a Credential Type has been configured correctly for Infinity37 cards (as seen below), the site code and/or card number read does not match what is printed on the card or the expected value. Parity errors could also be seen if the card is not truly of the Infinity37 format. Product Line Security Expert Environment Security Expert Server Security Expert Controller Cause Various cards have 37-bit data lengths but different formats; some guidance is needed on how to differentiate the ACC Infinity37 cards.  Resolution There are two pieces of data that can be used to verify if a 37-bit card is ACC Infinity27 format.   ACC Infinity 37 card format includes a Manufacturer's Code field; the field is 4 bits long, starting on the second bit and ending on the fifth bit. The Manufacturer's Code field always has a value of 4, the first bit of the card is used for the ODD parity, so the first 5 bits of ALL ACC Infinity37 cards ALWAYS look like P0100.... If we see a raw bitstream of a 37-bit card like the one in the screen capture below, we can immediately determine that even though the card has 37 bits, it is NOT an Infinity37 card since bits 2,3,4 and 5 do not add up to a value of 4 See https://community.se.com/t5/Building-Automation-Knowledge/How-to-display-RAW-bit-data-stream-of-Wiegand-card-in-Security/ta-p/390720  We can not assume that because a 37-bit card has  0100 on bits 2-5 it is 100% evidence that the card is indeed an Infinity37 card since that pattern (0100) could be present on the card as part of a different field (i.e., Site Code) on a different 37-bit card format. The second piece of data that could help determine if the card is true of the Infinity37 format is the parity bits, Infinity37 card format has a somewhat unique interlaced parity scheme. If parity errors are seen when cards are presented to the reader, this should be taken as an indication that the 37-bit card might not be Infinity37 card format. The attached zip file contains an Excel sheet that can be used to calculate the parity bits of an ACC Infinity37 card by entering the raw bitstream of the card; if the calculated values for both parity bits (bits 1 and 37) do not match what the card has, then the card is NOT an Infinity37 card format.    

Issue How to create i2xxx and b3xxx controllers from a CSV dump file. Environment Continuum i2xxx Controllers b3xxx Controllers Cause In this scenario they wanted to create the beginning of a site database from CSV dump files before deploying on site.  Resolution It seems that when creating an i2 or b3 object, the path is also required when defining the comm port. Make sure to add the path to the Port field and this should allow the controller object to be created. See the original CSV I exported below, how it was modified, and then imported back in successfully. Original Export to CSV InfinityInfinetCtlr Name,InfinetId,Port,DeviceId,SerialNum,Alias,CntrlType i2_850,32,Comm1,Network1\ACX11_10th,11111,i2_850,i2920 Modified Import CSV InfinityInfinetCtlr Name,InfinetId,Port,DeviceId,SerialNum,Alias,CntrlType i2_920,32,Network1\ACX11_10th\Comm1,Network1\ACX11_10th,11111,i2_920,i2920 Now, this import does complain about the CntrlType in the distribution Properties window but does create the controller and sets the type correctly. If you don't want any errors you can remove the CntrType attribute and the controller object will still be created but will default to a 240 controller. See below. Import CSV without CntrlType InfinityInfinetCtlr Name,InfinetId,Port,DeviceId,SerialNum,Alias i2_920,32,Network1\ACX11_10th\Comm1,Network1\ACX11_10th,11111,i2_920   This can then be changed to whatever controller you require through the controller Device object dialog.  

Issue Loading or upgrading new firmware into a 102-AX VAV controller that resides under a Jace controller Environment Jace Vista Xenta 102-AX Firmware Cause Updating firmware in a 102-AX VAV controller that has previously been commissioned into an existing network Resolution Please click here to see a step by step procedure document on the recommended procedure for this task.

Issue In a Niagara G3 station, whenever someone logs into the graphics (with any web browser), the following error appears in the application director output: javax.baja.xml.XException: Root element must be "nav" [line 3]  at javax.baja.nav.NavFileDecoder.err(NavFileDecoder.java)  at javax.baja.nav.NavFileDecoder.decodeDocument(NavFileDecoder.java)  at javax.baja.nav.NavFileDecoder.decodeDocument(NavFileDecoder.java)  at javax.baja.nav.NavFileDecoder.load(NavFileDecoder.java)  at javax.baja.nav.NavFileDecoder.load(NavFileDecoder.java)  at javax.baja.user.BUser.getHomePage(BUser.java)  at com.tridium.fox.sys.user.BUserChannel.fetchPrefs(BUserChannel.java)  at com.tridium.fox.sys.user.BUserChannel.process(BUserChannel.java)  at com.tridium.fox.sys.BFoxConnection.process(BFoxConnection.java)  at com.tridium.fox.session.SessionDispatcher.dispatch(SessionDispatcher.java)  at com.tridium.fox.session.SessionDispatcher.run(SessionDispatcher.java)  at java.lang.Thread.run(Unknown Source) Product Line TAC IA Series Environment Niagara G3 Cause The G3 user account has the nav file property pointed to a file that is not a nav file. Resolution Correct the nav file property setting.

Issue When a Bacnet alarm from BACnet controller (BCX and b3 controller) is acknowledged,  alarm recipient Continuum WS sends out Change-Of-Bitstring packet to the 3rd party BACnet Operator Workstation (BOWS) when the 3rd party BOWS is registered as one of the recipients in the EventNotification of the alarm. Environment Continuum WS. BCX. B4920. B3 controllers.. Cause This packet shows some proprietary behavior of Cyberstation we refer to as the "workstation to workstation ack", that happens in addition to the normal workstation to controller acknowledgement. Cyberstation uses the information in the Recipient List of the NotificationClass object of the original alarm to determine which other devices receive the original alarm, and therefore, should receive the proprietary alarm ack. Resolution As a workaround is as below: From the existing EventNotification, remove all the 3rd party devices from its recipient list. Create a new EventEnrollment & EventNofitication for the same alarming point, and add only the 3rd party devices to its recipient list.

Issue A Log Processing Trend Log created in an EBO server and connected to an Extended Trend Log will not transfer any records even if the Force Transfer command is executed. Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Automation Server Premium Building Operation Automation Server Bundled Cause Log processing trend log records are not saved to database, so they will not be transferred to Extended Trend logs. Resolution In the Basic Properties of the Log Processing Trend Log, set "Persist data" to True to store trend data in the database. This will enable the records to be transferred to the connected Extended trend Log.