Building Automation Knowledge Base

Issue How are the bits allocated in a 26bit Wiegand card format? Environment Access control peripherals data format Cause Although this is an openly published data format, sometimes the actual data bit format is required. Resolution The Wiegand 26 bit format consists of 24 bits of data and 2 Parity bits (Odd and Even) The 24 data bits are split between 8 bits for the Site code and 16 bits for the card number. Giving a card number range of 1 to 65535, and a site code range of 1 to 255. A spreadsheet defining the format can be downloaded here.

Issue Need information on securing a building automation system. Environment Best practices Cause End user has requested assistance for their IT department to secure the building automation system. Resolution Click here to get a copy of Best_Practices_for_Securing_an+IBMS_WP.pdf,  a white paper written by Schneider' Electric's Buildings BU IT Security Group. This also located on the Download Center here

Issue Access Control Spec for Tender Offer which usually comes from the Product Marketing Division Environment I/NET Site with Access Control Cause Bidding a job and requests for Access Control Spec or Specification Requests for: General Requirements Site Construction Door Locking Hardware Conveying Equipment / Elevator Controls Electrical Power Communications Video Surveillance Security Management System (SMS) specified For the Access/Security Control Contractor. Typically the SMS provides and explanation and integration for:   • Integrated Access Control • Alarm Monitoring • Integrated Digital Video Management • Interactive Alarm/Facility Graphics Display • Wireless Alarm and Video Transmission • Associated Access Control and Alarm Equipment Control • Multiple Language Operation • Multiple Tenant Operation • Access Initiated and Event Initiated Control  • Elevator Control • Workstation and associated equipment General Requirements Site Construction Door Locking Hardware Conveying Equipment / Elevator Controls Electrical Power Communications Video Surveillance Resolution I/NET Seven Access Control Specification (Available in a MSWord format)  

Issue Guard Tour for I/NET Environment I/NET site with Access Control Cause Is there a Guard Tour configuration or is there add-on software for Guard Tour with I/NET Access Control Resolution I/NET really does not have a Guard Tour add-on. It does not have a Guard Tour setting with the Access Control functionality.    What I would suggest however, is that you can run a report on an individual card, and this report could have the times at which the card was used. This could for example be the Guard card, and show that at specific times the Guard used the card. This also would apply to a Group such as Guards. I/NET does not have a Guard Tour add-on. It does not have a Guard Tour setting with the Access Control functionality.   However, a site can run a report on an individual card(s), and this report could have the times at which the card was used. This could for example be the Guard card, and show that at specific times the Guard used the card. This also would apply to a Group such as Guards.   Please find two custom reports for using with the above suggested scenario.  Custom Reports.zip which contains two reports: TAC_TransactionsIndividuals_dateIndivID_001.rpt TAC_TransIndiv_Date_IndivID_GroupName.rpt  

Issue Archiving and database size with FIFO not working Product Line TAC INET Environment I/NET site Cause dbo.Events keeps growing and presumably is not in FIFO mode (First In First Out) Resolution Note: Autogrowth is not used with TAC I/NET Seven or TAC Andover Continuum The size of the InetDB can be set through Microsoft SQL Server Management Tool:   By selecting the InetDB database properties you can set the Autogrowth setting via the Files page.  Under the Autogrowth column select the browse button as shown:   The Change Autogrowth setting by either disabling the Autogrowth check box or you can set Autogrowth to a Maximum File Size as shown:     The Autogrowth value now shows this setting is restricted to setting define in step 2.   Disabling Autogrowth allows the events to be removed from the table when the total size of the SQL database reaches the limitation set in the properties of the db. The table dbo.Events has all the current events and it should be the biggest. The dbo.currenteventdetail table keeps up with the current max events and the current minimum events. Lets say it is around a million (1,000,000) events and so the first event in this table would be 01 and the last would be the 1000000. If items are removed from the other table, the dbo.Events, then this other table, the dbo.currenteventdetails is off. This means we run the risk of losing those events that are not correctly numbered. Manually removing items from one table can have an impact on other tables and how this data is kept and archived. About archiving and shrinking the db, this is a function of SQL. SQL goes into a FIFO mode, which means First In, First Out. This keeps the db from getting to large. The archived records are designated as archived in the db and even though they are still (secretly) in the db, they will be out as soon as the db is over the capacity amount and the amount designated in the db.currenteventdetail table is the guide for what is current. The thing that keeps the db from getting to large is the archive is setup correctly and old data is archived. It is still available via Reports, but considered not technically in the db. That is what shrinks the db and keeps it from getting over size.    Note: Autogrowth is not used with TAC I/NET Seven or TAC Andover Continuum

Issue How do you get the Modbus register list and communication values from a ICP7188 (SP7040) project. Have extracted files from ICP7188 (blue turtle) want to upgrade this to a Xenta 731 or 913, how can I read the current register configuration from this device. Environment ICP 7188 Cause Want to replace a ICP7188 "blue turtle" device with a Xenta 731 or 913 and need to now what the current Modbus configuration / registers are in the ICP7188 device. Resolution To retrieve the Modbus values from the ICP7188 (SP7040) project you will need two text files Cfg9100.txt and MAP9000.txt. from the original project. and the following files contained in this ZIP file SP7040. Note:  If you need to extract these files you can follow the instructions in the "ILink Commissioning Guide" PDF which is contained within the above ZIP file.  If you don't have the LinkTerm application detailed in this document you can download and install it from here. N.B: After extracting this LinkTerm.zip file there are two files with the extension '.rename', ISDEL and SETUP.  Both these extension must be renamed to '.EXE' and then you can follow the instructions is the above mentioned guide. After extracting the SP7040 ZIP file to a drive on your PC along with the two text files into the directory proceed with the following steps: 1. Open the TGT9100.xls file. Make sure you have Macros enabled in Excel. 2. Then select the Device Editor button.   3. This will move you to the System Device summary with a message indicating there is a mismatch of the configuration files. Select Yes too load the configuration files   This will populate the Table from the txt files copied earlier. 4. Now you can select the + button next to the Type heading 5. Then select the + button next to the Type heading to show the Modbus values for that device.   6. To view the communication setup select the + button next to the System heading as seen in the step 4 image.

Issue How to troubleshoot UDP IOServer can not communicate with Xenta Environment Xenta Server Ethernet Communication (UDP) Cause INET communicate with Xenta Server via UDP but sometimes another process are occupying the default port Resolution Refer to this guide

Issue Alternatives to the FOI1 and FOI2 product which is discontinued and possible replacement using the Westermo ODW-730-F2 Environment Site using a Fiber Optic Interface on LAN (CLAN) or SCU Network (SubLAN) Cause Discontinuation of the FOI1 and FOI2 products which have been available for a number of years. Resolution The ODW appears to provide a very cost effective and versatile fiber optic interface for RS485 networks. The ODW is one of only a few RS485/Fiber interfaces that provide the redundant fiber network capability. Some notable features on the ODW-730-F2 include – -Dual Fiber Bus Configuration or Dual Fiber Redundant Ring Configuration -Local status contact output indicates fiber fault detection -LED indication of Local fiber fault condition (FL L) CH1 and CH2 LEDs indicate if failure is on incoming or outgoing fiber -LED indication of Remote fiber fault condition (FL R) Here the LED indicates when there a fault anywhere in the system. A summary of controller status points monitoring the Local fault detection would be reviewed to identify location of a fault. Current system operation is probably operating on the basis of the redundant ring. A second fiber fault will disable the ring system. In a bus configuration, you currently have lost some portion of the system communications. -Supports Asynchronous (SubLAN) and Synchronous (CLAN) protocols In the case of the synchronous CLAN interface, it is not reconstructing RS485 data quality. Any accumulated distortion on the copper cable segment is passed on to the data through the fiber and will arrive at the other fiber drops in the same condition, although amplitude will be replenished. You must insure you do not exceed copper cable distances and maintain compliance with recommended grade of cable while avoiding stubs and the distortion they produce. -Alternate Fiber Interface Options are supported two receptacles for plug-in fiber transceiver module purchased separately The lowest cost and most common interface is the MLC2. Each of the ODWs in this evaluation were configured with 2 of the MLC2 modules - MLC2 Multimode 62.5/125um or 50/125um 2km Fiber Length - SLC20 Singlemode 9/125um 20km Fiber Length - SLC120 Singlemode 9/125um 120km Fiber Length The ODW also supports the option of bidirectional fiber interface modules. These are more expensive options and currently used infrequently and are not discussed/evaluated here. -Powered by 24VAC (48-62hz), or 12 to 48VDC (supporting redundant DC) Power input is isolated from RS485 and Status port signals -RS485 port is isolated from power AND local ground The RS485 will take on the ground reference of the incoming RS485 signals. An oscilloscope examination of the RS485 data pins with no connection to other RS485 devices will show AC voltage on the RS485 pins (leakage to isolated circuit). A scope should only be examined with the RS485 port connected to the CLAN or SubLAN. Please find the attached pdf ODW FOI EVAL 120824.pdf for review. It proceeds through a sequence of differing configurations with the synchronous controller LAN and the asynchronous SubLAN.

Issue Demand Control Information Product Line TAC INET Environment I/NET Seven Cause Most issues with demand control will come from improper setup or lack of understanding of demand control processes. Resolution TCON 300 Technical Reference Guide is the best location for version specific information on  Demand Control.  Click here for the demand control sections of TCON 300 from version 2.43

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.

Issue I need to re-order IDisc Parts for a system Environment Any Windows OS and I/NET Software Cause I need to find the replacement Part Numbers for the Old I/Disc Systems Resolution The I/Disc (silver Disc) and the Plastic Fobs are not available on the Iportal Outside Vendor for the I/Disc Reader and the I/Disc (silver disc) and other accessories Outside Vendor for the I/Disc Wand  Third party vendor website with iButton

Issue Code-Guard Pin Pad Reader Programming in I/Net Seven Product Line TAC INET Environment Any Windows OS Version and Any I/Net Seven Version Cause I need to program a "Scramble" Pin Pad Reader made by Code-Guard Resolution Here is a link  to programming the Code-Guard Pin Pad Reader in I/Net

Issue Table needed for linearizing a 10K thermistors for an I/Net 7756 (lower board) Product Line TAC INET Environment 7756 (lower board) Cause Thermistors require the use of a look up table to linearize the data. Resolution Thermistor Inputs on a PCU 7756 (lower board) Enter the Temperature data in °C (First Column - 31 entries) Enter the corresponding resistance data in Ohms (Second column - 31 entries) Enter the dissipation constant in milliwatts per °C: 2 Low Temperature : -22.11°F (-30.06°C) High Temperature: 247.92°F (119.95°C) Point Value in °F: M=0.00412; b=-22.1138 Point Value in °C: M=0.00228913; b=--30.0632065 Look Up Table: °C Ohms Current Self Htg Adj °C Adj °F VDC Counts Adj Cts 120 389 0.000481 0.045052 119.95 247.92 0.187217 1227 65535 100 680 0.000468 0.074521 99.93 211.87 0.318352 2086 56785 90 917 0.000458 0.096177 89.90 193.83 0.419987 2752 52407 80 1258 0.000444 0.12407 79.88 175.78 0.558714 3662 48027 70 1753 0.000425 0.158633 69.84 157.71 0.745767 4887 43643 60 2489 0.0004 0.199471 59.80 139.64 0.996477 6530 39257 55 3045 0.000383 0.223671 54.78 130.60 1.167114 7646 37062 50 3602 0.000368 0.243359 49.76 121.56 1.32407 8677 34869 45 4368 0.000348 0.264484 44.74 112.52 1.520045 9962 32676 40 5326 0.000326 0.283435 39.72 103.49 1.73757 11387 30483 35 6691 0.0003 0.300218 34.70 94.46 2.004374 13136 28292 30 8056 0.000277 0.308878 29.69 85.44 2.230837 14620 26104 28 8777 0.000266 0.311174 27.69 81.84 2.337168 15317 25229 26 9572 0.000255 0.312351 25.69 78.24 2.44533 16025 24355 25 10000 0.00025 0.3125 24.69 76.44 2.5 16384 23918 24 10450 0.000244 0.312349 23.69 74.64 2.555012 16744 23481 22 11420 0.000233 0.311127 21.69 71.04 2.665733 17470 22608 20 12490 0.000222 0.308669 19.69 67.44 2.77679 18198 21735 18 13680 0.000211 0.304953 17.70 63.85 2.888514 18930 20863 16 15000 0.0002 0.3 15.70 60.26 3 19661 19992 14 16470 0.000189 0.29383 13.71 56.67 3.111069 20388 19121 12 18090 0.000178 0.286579 11.71 53.08 3.220007 21102 18250 10 19900 0.000167 0.278241 9.72 49.50 3.327759 21808 17380 8 21920 0.000157 0.268921 7.73 45.92 3.433584 22502 16510 6 24180 0.000146 0.258715 5.74 42.33 3.537156 23181 15641 0 32660 0.000117 0.224329 -0.22 31.60 3.827942 25086 13035 -4 36200 0.000108 0.211999 -4.21 24.42 3.917749 25675 11293 -10 55340 0.0000765 0.162028 -10.16 13.71 4.234772 27753 8694 -14 69000 0.0000633 0.138199 -14.14 6.55 4.367089 28620 6957 -20 97130 0.0000467 0.105789 -20.11 -4.19 4.533277 29709 4350 -30 177200 0.0000267 0.063207 -30.06 -22.11 4.732906 31017 0 This spreadsheet is for a thermistor rated at 10,000 ohms at 25°C. Install a 10K Ohm Resistor in the "B" terminal (consult the TCON for the controller you are using for details) This look up table program is based on using 31 entries The data points do not have to be evenly spaced Click here to download this in pdf format. For the look up table to the 7716, 7718, 7728 and a 7756 (upper board), see 10k Thermistor Look Up Tables for a 7716, 7718, 7728 and a 7756 (upper board).

Issue Key/card numbers Largenumber Hexadecimal Decimal   Environment I/NET keycards Cause Converting Hexadecimal to Decimal and vice versa Resolution See the attached document for a clearer understanding of the formats conversion: Hexadecimal/decimal

Issue The Actuator is responding as though it is receiving a continuous signal from the ASC. Environment I/NET software all versions I/NET ASC controllers Cause The triac device on these ASCs have a bleed voltage value even though the signal is in the Off mode. Thus causing the motor to drive to one end of the stroke and stop. Resolution See Tech Tip No. G075 which describes a procedure to correct this issue.

Issue Documentation for architectural design for illustration, explanation, sales presentations, or other medium Environment Schneider Electric office, partner office, or other site needing documentation Cause Inability to find literature and need to explain, illustrate, or define issues. Please find the links below for each of the product lines. Resolution Continuum: download architectural Flyer:  pdf   jpg  INET: download  architectural Flyer Vista:  download architectural flyer pdf   jpg  I/NET and Vista together pdf

Issue My computer has USB ports, but it does not have serial or com ports. Can I use USB ports? Environment For I/NET, Host computer that either Direct Connects (cable 072) or you need to connect to a controller such as a 7798C (cable 082) Continuum, Vista, Sigma, I/A Series, Pelco, DVR, DS, Com Port, Com, PTZ Control, Serial Port, Comm, Comm Port Cause USB to Com has issues downloading or communicating with system. Resolution The generic drivers which came with your USB to Com adapter do not allow two-way communication.  Prolific driver often helps resolve this issue. Download driver HERE or for the latest driver use link below: http://www.prolific.com.tw/US/CustomerLogin.aspx    you will need to logon as GUEST  

Issue Integrate a Datacard (ID Works) Video Badging system together with an existing I/NET Seven system. Environment I/NET Seven ID Works Video Badging software version 6.5 All Windows version that are supported in the current I/NET Version of 2.42 and below Cause I/NET Seven and ID Works need to work as an integrated system. Resolution The attached White paper defines the necessary steps required to modify the ID Works to operate in the I/NET system. Note: if using 64bit OS such as Windows 7, a patch is required which makes ID Works 64bit. It is available from the 3rd party vendor. http://www.datacard.com/id-software-support-and-upgrades/id-works-identification-software

Issue Clarification on dip switch six and station addressing for the SCU1200, SCU1280, or SCU1284 Product Line TAC INET Environment I/NET Seven with Access Control using an SCU SCU1200, SCU1280, or SCU1284 Cause Clarification on SCU and dip switch settings being open, enabled for dual or single station addressing (2 or 4 doors) Resolution If the Device Type is SCU1200, SCU1280, or SCU1284: set the Number of points to either 1 or 2. Choose 1 if the SCU is configured to operate in the “single-address” mode (DIP switch S1-6 = OFF). Choose 2 if the SCU is configured to operate in the “double-address” mode (DIP switch S1-6 = ON). In order to control more than two doors, the SCU1284 must be configured to operate in the double-address mode. Though the TCON312 shows the dip switches for 1-6, there is still a bit of clarity which can be provided on how that looks on an actual SCU. The example from the TCON is shown here: And this is a photo below of an SCU which is setup as 0101 with dual addressing since Dip Switch 6 is in Dual Address mode shown in the picture below. When penetrating down to it using Edit, Host Computer, Network Configuration, SCU 1284 is shown with 2 Points with door addresses: 010108 Door1 010109 Door2 010208 Door3 010209 Door4 After checking MCU Configuration, I added the points in the Network configuration. The main point here is that Dip Switch 6 is up on the Open side of the Switch bar shown in red which is the dual point and 4 door configuration.   Note: Concerning the numbering scheme for addressing the SCU, it is important to number your SCUs with an address then skip the next number so in the event you dual addressing for four doors, the second address is available. Don't use addresses 28, 29,30, and 31 as those are reserved for the Remote Arming Terminal.  Overlooking this can result in future headaches of moving SCUs around in the addressing scheme which is never recommended. Example for a site containing 4 SCU door controllers: SCUa address 2, SCUb Address 4, SCUc Address 6, SCUd Address 8.  Another example configuration: One reader inputs to READER1 and READER2? Here is that wiring example. In order to use more than the first eight inputs on the SCU, you must configure the SCU as a double-address controller. When you enable the double-address mode (DIP switch S1-6 = ON), inputs 1 through 8 are monitored on the selected subLAN address (i.e., the primary address) and inputs 9 through 12 are monitored on the next consecutive subLAN address (i.e., the secondary address). The input points are defined in the I/NET host using two separate SCU controller assignments, the first providing eight input point definitions and the second providing 4 input point definitions. The SCU’s outputs are also divided across two LAN addresses when the SCU is operating in the double-address mode. The first four outputs are assigned to bit offsets 00 through 03 on the SCU’s primary address. The last four outputs are assigned to bit offsets 00 through 03 on the SCU’s secondary address.

Issue Conversion process for taking small numbers in I/NET Seven to Large numbers in I/NET Seven Environment I/NET Seven rev 1.12 and above Cause The card number of the Prox cards are larger than 24000 Resolution Sort the Individuals list according to the Individual Number. Find out the lowest number in the list. In this example number 1 is the lowest card number.   Look at the tenant editor to determine the Tenant Code/Facility code of the cards.   Go into the Door Editor and verify the Bit Format of the Cards. In this case it is a standard 26-Bit Format.   Verify in the door editor that the cards in this system are 26-Bit Wiegand. Then use the attached Excel spreadsheet (This is a ZIP File) to determine the Decimal number of the first card in the system (Card #1 Facility code 199) is 13041665. This number will become the source number in the Key card table.   Create a Key card table like below, using the Source # that was determined in Step #3 above. Please note the Target # must be equal to the value of the Lowest Individual Number.   Next unzip the supplied Windows SQL Script (BigCardConvert.exe). Please note that the SQL Script will ask for a Username and Password. These are the Username and Password used for the SQL in the DbCreate Editor. Once unzipped, double click the “EXE” file and this will convert all the existing card numbers into “Hex” numbers. After this process has completed, verify that the cards did in fact convert OK. Look at the lowest individual number the (“Source” card used the “Hex” and “Decimal” numbers) will be the same values determined in the Excel spread sheet. After verifying that all is OK, then delete the “Card Key Translation” table created to do this process.