Building Automation Knowledge Base

Warning Electrostatic Discharge Required: Always discharge static electricity from your person by touching metal prior to handling any hardware. Failure to do so may result in damage to devices. Issue 7798C stops communicating after BIN file download Is the 7798C supported in the older versions of I/NET Seven (1.14 and below). How to reset the 7798C hardware (i.e. place into boot mode) if no communication is possible with the 7798C    Product Line TAC I/NET Environment I/NET Seven 1.14 and lower I/SITE LAN 7798C Cause I/NET revision 1.14 and lower does not support 7798C and can mistakenly be assumed by the I/NET Host software as a 7798B.  If a software restore is completed to the 7798C with these revisions, it disables the device from communicating via the Controller LAN and disables any communication via the serial port with the Hand Held Console (HHC) software.   Resolution If you have downloaded the incorrect BIN file (i.e. 7798) to the 7798C, the handheld console software will not work, and hence, the device can not be placed back into a boot state, allowing the correct BIN file to be restored to the 7798C.  If the serial port is still configured/enabled for direct connection via the onboard TAP, this is the easiest solution to try a software restore to blank out 7798C with the correct BIN file. If either of these options are not available, the following steps can be performed very carefully directly on the hardware: Very Important:  Make sure you turn OFF the power to the 7798C unit. If you fail to remove power, this process could damage the board.  If unsure, please contact Product Support On the top edge of the board is the EPROM, and just below are two RAM chips. Between the EPROM and the two RAM chips are two mustard-colored capacitors (Labeled C2 & C3) If you short across each Capacitor, one at a time, this will take the device to boot. If you still have issues with the device, sending the 7798C in for repair is recommended. Once the device is communicating again, the correct firmware can be restored to the 7798C. At this point, you should be using I/NET Seven revision 1.17 or above.

Issue How to identify what ports are being used on a PC. Product Line All product Lines. Environment Any Windows OS Cause Running multiple applications on the same PC without managing TCP/UDP port assignments can lead to conflicts. Resolution TCPView will help you identify all ports and services to each application. Download from Microsoft's website http://technet.microsoft.com/en-us/sysinternals/bb897437.aspx Detailed instructions are available at the site.

Issue The network card is not working on the PC.  Product Line Andover Continuum, EcoStruxure Access Expert, EcoStruxure Building Expert, EcoStruxure Building Operation, EcoStruxure Security Expert, Satchwell BAS & Sigma, Satchwell MicroNet, TAC IA Series TAC I/NET, TAC Vista Environment PC Network Interface Card Cause Require a method to test the network card. Resolution Assuming you have the correct protocols loaded:- Open up a command prompt and type ‘ipconfig’(1) then press enter to get a list of the available network cards. Find the specific network card by name (2) Record the IP Address (3) assigned to the card, e.g. 192.168.5.90 If the card is unplugged (4) connect a network cable and start back at step 1 If the network card does not appear in Device Manager check the drivers are correctly installed for the card and when installed correctly start back at step 1. If the network card still does not appear it could be disabled.  In Network Connections right click the adaptor and select Enable (5) and start back at step 1. After these steps if the network card still does not appear when running ipconfig it is most likely damaged. If/when an IP Address is successfully obtained open a Command Prompt and type ping followed by the IP Address of the card, for example ping 192.168.5.90 (1). A functioning card will respond with 4 successfully replies (2) and the associated statistics (3) As additional information a good first step would be to "ping 127.0.0.1". This will not test a network card but indicates that the TCP/IP protocol is installed and functioning on the host PC.

Issue Spare Addresses for use as internal points on an SCU 1284 dual address Product Line TAC INET Environment I/NET Access Control SCU1284 dual address mode Cause What are the ramifications of using the spare point addresses for internal points in an SCU 1284 Resolution Note! It's generally not recommended to use the available address on a subLAN. Addresses marked as "Internal" in the MCU configuration are reserved for internal software points. However, it's crucial to consider that doing so may limit the potential expansion of the subLAN to utilize these addresses in the future.   When a SCU1284 is set to dual channel, it only uses 12 inputs, 8 outputs, and 4 reader points.  Here is a list of all software points and their uses:   XX00 DI - XX03 DI Hardware Inputs used by doors XX04 DI - XX07 DI Spare Hardware Inputs XX08 DI & XX09 DI SCU tamper and power monitoring points XX00 DO - XX03 DO Hardware Outputs XX04 DO - XX07 DO Spare software only points XX08 DO & XX09 DO Reader Points YY00 DI - YY03 DI Hardware Inputs used by doors YY04 DI - YY09 DI Spare software only points YY00 DO - YY03 DO Hardware Outputs YY04 DO - YY07 DO Spare software only points YY08 DO & YY09 DO Reader Points   See the following documentation: TCON312-0910.book (schneider-electric.com)

Issue Can the serial port on the NetPlus Router (NPR) communicate at 9600 baud? Product Line TAC INET Environment NetPlus Router (NPR) 2000 Cause Configuration inquiry Resolution This specific configuration port is capable of transmitting data only at a rate of 19,200 baud.

Issue Sequence zero does not run when power is restored to the Micro Regulators (MR). The MRI is on a UPS in another part of the building and never loses power. Product Line TAC INET Environment MicroRegulator (MR) SubLAN devices MicroRegulator Interface (MRI) Controller LAN Interface Cause By design, sequences are stored in the MRI. Sub-LAN controllers do not store sequences. Resolution Sequence zero is designed to trigger the power restore event (Sequence 0) in the event of the Interface (MRI) power failure being restored, hence the MR will not trigger this sequence 0 in the MRI.  The action is correct.

Issue How do I set the Tap emulation for a Process Control Unit (PCU)? Product Line TAC INET Environment Process Control Unit (PCU) 7716/8 Process Control Unit (PCU) 7756 Cause Need to set TAP Emulation type on PCU  Resolution Using the HHC, press [Code], 90 [Enter] Press [Inc] or [Dec] through 7801, 7803, 7806 Tap emulation Press [Enter] to accept your choice 7801 for direct connection and Integrated dial operation 7806 for direct connect, integrated dial, and ADAA For additional details, please see the following documentation:  PCU 7718 TCON106-0910.book (schneider-electric.com) PCU 7756 TCON127-0910.book (schneider-electric.com)

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 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 How to set up a Mantrap Product Line TAC INET Environment I/NET Access Control Site Interlocked Doors Person Trap Anti-Passback (APB) Cause What is a mantrap? A mantrap is a security device that monitors and controls two or more interlocking doors to a small room that separates a non-secured area from a secured area. These interlocking doors allow only one door to be open at any time. What are interlocking doors? “Interlocking doors” is a security term used to describe how two or more doors are interfaced with each other and locked. Doors that are interlocked cannot be opened at the same time. Either door can be unlocked and opened as long as the other door is locked and closed and no other alarm condition exists. What types of locations require a mantrap? Mantraps are used at high-value or critical security areas where only authorized persons are allowed to enter. Typical areas include sensitive data processing areas, cash handling areas, critical research labs, security control rooms, and automated airline passenger entry portals. Why would my company consider a mantrap? Typically, security personnel are posted in high-security locations to control access into the area. An automatic mantrap used in this same location would control the access to the area, allowing security personnel resources to be available for other tasks. What is the difference between a mantrap and an interlocking door control system? Regarding controlling two doors within a vestibule, “mantrap” and “interlocking door controller” can be used interchangeably. Once the number of doors controlled by a single controller exceeds two, then the term interlocking door controller should be used. Resolution I/NET has three ways to do a mantrap: Event sequences and calculations -- limit to 5-7 SCUs per 7798C due to system loading Use a "standalone" third-party device that is wired to the door and is not attached to I/NET at all Use the interlock wiring diagram that uses relay logic to function. This is also part of the I/NET System. I/NET Seven allows configuring a door to have both an entry and an exit reader and uses the selection of Anti-pass back/Anti-tailgate to set up Zones or areas with stricter control over access. However, even with the Anti-pass back option set to Hard, which denies access to successive reads at the same reader, it does not prevent multiple persons from entering and exiting together, and it does not provide real-time accounting for the number of people in a Zone. Besides having a guard at the door, the usual method of implementing Zones does not prevent violations.   The example below presents some thoughts about improving the Zone's security in an I/NET Seven system. There needs to be a way to restrict the number of people gaining access to the door. There needs to be a way to keep up with how many people are in the Zone. One method to accomplish the first goal is to use a two-door egress system, as is often used in jails and similar security setups. For a medium security setup where the intent is not to prevent people from leaving, only one door needs a card reader. Such a design is illustrated below: Notes: Electric strike normally energized. Low walls or fences. The area should be small enough to limit how many people or things are in it at one time. Gate with normally de-energized bolt. The gate could swing both ways, so one would only have to push it to open it. It should have a spring to close it. The door “a” would have both an Entry and Exit reader, so an Anti-pass back/Anti-tailgate can be implemented. The strike on the door “a” would normally be energized and opened by a valid reader transaction.   The bolt on the gate would be normally de-energized, allowing the gate to open freely. When the strike on the door “a” is de-energized, the bolt on the gate would be energized, preventing the gate from opening. This is designed to allow only one person to simultaneously move into or out of the Zone.   An added level of security would be accomplished by mounting IR emitter/receiver pairs along the low wall or fence at regular intervals. A person would interrupt the light at a limited number of receivers, so if more than expected are interrupted, it would violate one person at a time, and necessary action could be taken.   If material needed to be moved through the door, the gated area could be made large enough to allow for a dolly or whatever might be needed. A different access level would be provided to those who are moving material, thus preventing the alarm for too many people going through the door.   This approach would restrict movement into and out of the Zone, and the example given in the AIC note could be implemented to allow real-time monitoring of occupancy levels in the Zone.   Design thoughts:   To calculate whether more than one person is in the gated area, sum the number of receivers that are detecting and compare it to a minimum, e.g., four of six must be detecting if only one person is in the area. If material is in the gated area, generate an alarm if an authorized card is not read. Use the alarm delay for the point to give an individual time to make a card read before sounding the alarm. The AIC scheme described in the AIC note would have to be duplicated for the material mover individuals to change the calculation of a person in the gated area. For material movers, the detection would be (sum of detectors < minimum), whereas for regular individuals, the detection would be (sum of detectors > minimum). Remember, the SLI connected to this door can have only 64 AIC’s and this door now has used 2 of them. Use an inter-card delay long enough to let the person exit the gated area before another card can be read. For personnel safety, there must be a way to de-energize the strike. One method would be to mount an emergency exit button located far enough away from the door so a single person could not reach it and a second emergency exit button on the outside of the Zone so someone could keep the strike de-energized until everyone is evacuated. Most codes probably require that all strikes be de-energized in case of smoke or similar emergency to provide another fail-safe.   Here is a pdf document which explains the setup using an SCU Click here to download third-party ManTrap information.

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 Initialization errors when starting I/NET Seven 2.42 or higher Error: "You must install an instance of SQL 2008R2 (64bit) before completing the INET install" Product Line TAC INET Environment I/NET Seven 2.42 Windows Server 2008 64-bit Windows 7 64-bit SQL 2008 64-bit Windows 8 Cause I/NET 64-bit requires specific installation process in order to function on a 64-bit PC Resolution Installing SQL Download SQL2008 R2 Express 64 bit (SQLEXPR_x64_ENU.exe) from this location: http://www.microsoft.com/en-us/download/details.aspx?id=30438 Run SQLEXPR_x64_ENU.exe In the left hand section, select Installation In the Right and section, select New SQL Server stand-alone installation of add features to an existing installation. At the "Setup Support Rules" screen select OK At the "Product Key" screen, select Next At the "License Terms" screen, check accept and select "Next" At the "Setup Support Files" screen, select Install At the "Setup Support Rules" screen, select Next At the "Feature Selection" screen select: Database Engine Services, SQL Server Replication, Management Tools - Basic (If Present) and SQL Client Connectivity SDK. Leave the Shared feature directory as default. At the "Instance Configuration" screen, select the Default instance option, accept the default Instance ID, accept the Instance root directory default settings and select next. At the "Disk Space Requirements" screen, select Next At the "Server Configuration" screen, under SQL Server Database Engine set the Account name to NT AUTHORITY/SYSTEM, leave the password field blanks, and set the startup type to automatic. Under SQL Server Browser Service, set the Startup Type to Automatic At the Database Engine Configuration screen, set the Authentication Mode to "Mixed Mode", Define a strong password (example: @sql2008), in the Specify SQL Server administrators section click "Add Current User". Select Next. At the "Error and Usage Reporting" screen, select Next At the "Installation Rules" screen, select Next At the "Ready to Install" screen, select Install At the Installation Progress screen, when the setup process is complete, select Next At the "Complete" screen, select Close. SQL Configuration: In the Windows Start Menu, launch the SQL Server Configuration Manager In the Left hand section of the window, highlight SQL Server Services Verify that SQL Server Browser and SQL Server are Running In the left hand section of the window, expand SQL Server Network Configuration and highlight Protocols for MSSQLSERVER Enable Named pipes and TCP/IP Close the SQL Server Configuration Manager Restart the PC Installing SQL Server 2005 Backward Compatibility On the I/NET 2.42 or higher installation CD, look in Support\SQLBCM_64Bit and launch the SQLServer2005_BC_x64.msi file Follow all the prompts on each screen and accept all defaults. Install I/NET Seven 2.42 or higher Install I/NET Seven 2.42 or higher using the installation CD Follow prompts and use defaults When prompted for the SQL password, select "Windows Authentication" Restart the PC Open I/NET Configuration through the start menu. Modify the default Config profile or create a new profile. Close I/NET Configuration Start I/NET NOTE: If error occurs during SQL installation stating invoke or begin invoke failed, follow instructions at this link: http://support.microsoft.com/kb/975055 UPDATE: SQL2008 SP1 prevents the invoke failed error. It can be installed with the same instructions as above. Download it at this link: http://www.microsoft.com/en-us/download/details.aspx?id=25052

Issue Opened the Individuals Editor, and nothing is listed in there. The Individual list editor is blank Product Line TAC INET Environment All versions of I/Net Seven Cause The Option Selection was used and not reverted back to the original setting that allows all individuals to show in this Editor. Resolution Open the Individuals Editor by selecting Edit>Access>Individuals. If there is more than one Tenant, select a valid Tenant.  Avoid selecting the All Tenant option. Select the Options button at the bottom of the Editor. In the Display field, from the drop-down, select Individual. In the options for all the fields, ensure it has an asterisk (*) and not a name or anything else. Click on the OK button, and now all the individuals for that Tenant will be displayed.

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

Issue Need to change from the Small Number Format (Card Number) to the Large Number Format (Facility Code + Card Number). Requirement for Security Expert Transitions with I/NET Hardware.   Badging card on SCU1284 Reader using Security Expert, the reader event displays "Format error RD xx Port x Error Number of Bits" From Security Expert Client Events Product Line TAC INET, EcoStruxure Security Expert Environment I/NET Seven Security Expert Transitions Cause The I/NET system is limited to a maximum number of access cards, 32,000 per Tenant.  If a larger number is required, then I/NET must be configured to use large card numbers.  The Large card number format described in the Resolution MUST be completed before transitioning from I/NET to Security Expert and utilizing the I/NET SCU hardware as detailed in the Transition Guide Security Expert - INet Access Control to Security Expert - Reference Guide. Resolution To convert I/NET to use the Large Card Number support, the following steps must be performed:  Conversion of Card Numbers (small) to Large Numbers Sort the Individuals list according to the Individual Number. Look in the Individuals Editor “Options” function to set this up. Look at the tenant editor to determine the Tenant Code/ Facility code of the cards. From this, use the circled items the Tenant Code (Facility Code) and the First Individual Number as the lowest possible card number in the next step.  Verify in the door editor that the cards in this system are in a known Weigand bit format.  In this case, we are using 26-bit. Attached are various Excel spreadsheets that can determine the Decimal number of the first card in the system (e.g., Card #970 Facility code 199) is the Decimal number 13042634, using a 26-bit Weigand Excel spreadsheet.  This number will become the Source number in the Key/Card Translation table. These include 26-bit 32-bit ABA115 format Create a Key/Card Translation table similar to that shown below in the I/NET Seven Access Control editor.  This table will be removed after running the provided SQL Script.  The Key/Card Translation must contain: Source - Decimal number calculated in Step 3 above (13042634) Target - First Individual number shown in the Tenant (970) Count - Number of Individuals as shown in the Tenant (10000) Tenant - Tenant number this translation refers to (1) If there are multiple Tenants, then this process MUST be repeated for each Tenant Tenant Editor and Key/Card Translation Editor Shut down I/NET completely and run the attached SQL Script. Then once the script runs then, restart I/NET and look in the Individual Parameters editor, as shown below. Start I/NET and delete the Key/Card Translation table create above. Open the Individual Parameters and verify a Hex number and the decimal number matching that from the Excel spreadsheet (Step 3) is seen in the Individual Editor Card section. NOTE: There may be multiple card entries here; the Last entry shown is that entered by the SQL Script.  It will depend on whether an existing Card entry was entered for the Individuals before running the SQL Script.  To have large numbers working on a site DipSw #7 has to be turned ON for the 7910/7920 DPUs. For the SCU1284 in the door editor, at the top center of that editor, there is a check box, "Card Translation," which has to be enabled for large numbers to work in the SCUs. An SLI “SAV” should then be done because that is where the Card numbers and Door settings are stored. Then perform an SLI restore. Followed by a DPU restore to all of the door controllers. NOTE: Steps 6d. and 6e. are NOT required when performing the transition to Security Expert as this information will be performed by the SP-C.   

Issue Incorrect settings in the BCX will prevent BACnet communication. Product Line Andover Continuum, TAC INET, TAC Vista Environment BACnet MSTP BACnet IP BCX Xenta 913 Cause Because the Xenta 913 has a limitation of 127 addresses, the default BACnet Address will most likely be out of range. Resolution The BCX4040 must be addressed properly to allow BACnet communication to the Xenta 913. The setting can be changed on the BCX's Controller Configuration page by accessing the controller via IP address to its web interface. On this page, you will see a setting for BACnet Network ID Comm2 which is the device's BACnet address. This number must be unique on the BACnet Network and must range from 0-127.   To Enable BACnet IP communication: Modify the BACnet Ethernet settings from the web interface. Set the BACnet Ethernet Enabled to Yes Set the BACnet Network ID Ethernet. This is the device's BACnet address. This number must be unique on the BACnet Network. The BACnet Device Id is by default the last 7 characters of the BCX serial number and must be unique to all devices in the Continuum network. Many people try to set the BACnet Device Id field to represent a BACnet address but this is not correct. This setting does not affect the Xenta 913 in any way.