Building Automation Knowledge Base

Issue If a widescreen monitor is used, graphics will display properly in Vista, but if you open them for editing in Graphics Editor, they appear stretched horizontally. Conversely, if you create a graphic in Graphics editor that looks proper, it will appear to be squished horizontally in Vista, and the alignment of any text will be off. Environment Vista IV OGC Graphics Editor Cause The computer being used has a widescreen primary display. Resolution Resize the primary widescreen display to a resolution with a 4:3 aspect ratio, 800x600, 1024x768, etc. or, if a secondary display with normal aspect ratio is also connected, it must be set as the primary display.

Issue Integrated NPR Dial on a Xenta 527 Environment I/NET site with Integrated NPR Dial Cause Explanation of Integrated NPR Dial on a Xenta 527 Resolution Are you having an issue where you are setting up NPR Dial on a Xenta 527? Only the US Robotics V92 56K Faxmodem is supported. Do realize that this device cannot perform Auto Dial Auto Answer (AD/AA) functionality. To configure NPR Dial you will need to get the Xenta Modem Kit, part # 0-073-0916. These steps should point you in the right direction: -   Verify that you have the right strings for the modem. Create an I/NET Configuration profile for Integrated NPR Dial and make it active. Restart I/NET. Add site phone numbers (Edit > Host Computers > Phone Numbers.) Connect the necessary cables to the Xenta 527 unit and modem. You can get a full description from part number OFL-3972-001 with all the cables etc. Connect the adapter to the modem then the L1 cable from the modem to port A on the Xenta 527 unit. Query your modem, check the settings and baud rate then dial the site.

Issue Xenta 511/527 with Port Forwarding - Login allowed but after login page times out and page cannot be displayed. Product Line TAC Vista Environment Xenta 511 Xenta 527 Cause Firewall/router settings must be adjusted by the site administrator to accommodate the redirect. Resolution Tell the router/firewall administrator that the 511/527 redirects ports from https to http so you will need the firewall/router setup to accommodate this. If there is a delay in getting this done, the work-around is to type in the missing redirect address. For example your ports are https - :9443 and http - :9080. Login to the 511/527 https://xxx.xxx.xxx.xxx:9443/www/index/Slogin.html the 511/527 redirects you from https to http and it will not get the redirect with the "Button" and you will get http://xxx.xxx.xxx.xxx:9080/www/index/index.html After the last "/index" type in "Button" so the link looks like below http://xxx.xxx.xxx.xxx:9080/www/index/indexButton.html and type enter. You'll now be able to navigate as usual in the 511/527.

Issue XBuilder and Port Forwarding Product Line TAC INET, TAC Vista Environment I/NET or Vista site Cause Desire to know XBuilder and Port Forwarding Resolution A Xenta 511/527 can be downloaded: On the intranet using the actual 511/527 web address Remotely using the public IP address Using port forwarding by typing in the :9080 (or whatever ports are assigned) after the web address in the XBuilder project. You will have to change the http and https ports in the XBuilder project to the remote ports.

Issue Error message "The Parameter is incorrect" when clicking OK in TAC Vista Server Setup Emailing alarms from TAC Vista is not working Product Line TAC Vista Environment TAC Vista Server Setup Cause The text encoding method has not been selected. Resolution Open TAC Vista Server Setup Click on the Mail Tab Check if the Text encoding Field is empty. If it is, select an encoding from the dropdown. Unicode (UTF-8) is suggested in the US with an Exchange Mail server.

Issue Error message says "Can not initialize license" when logging in to TAC Vista Workstation. Environment Vista Workstation Cause The installation of the license server has been faulty in some way. Resolution Uninstall TAC Vista Server/Workstation Reinstall TAC Vista Server/Workstation

Issue I have a Window XP PC and cannot get the MSDE to load Environment Windows XP MSDE I/NET Seven Cause According to the Microsoft web site, the file and printer sharing has to be turned off to load Microsoft SQL. Resolution Turn off file and printer sharing. Once The I/NET software is loaded, re-activate the Shared objects.

Issue Dell PC will not allow the MSDE to load from I/NET Seven Environment There are (3) different computers from Dell: L100 Latitude D505 Latitude GX OptiPlex series desktop All were running Windows XP Pro and all had an installation of MSSQL installed already. Cause When I/NET is installed for the first time and MSDE begins to install it fails on the "renaming of the SQL folder" partly due to "Read Only" right to the folder SQL is installed in. The error message is has this reference in it about SQL: MSSQL$MICROSOFTBCM cannot be renamed. The install of I/NET stops at this point. You do not have the option to use "Add Remove Programs" to uninstall this previous install of SQL. Resolution Go to "Manage\Services and Applications\Services... to Stop and or Disable (3) current instances of SQL running. Right click on "MSSQLSERVER" and click on Properties, then click on the Startup type, then select "Disabled", click Apply and then repeat for MSSQLserverADHelper and SQLSERVERAGENT. Now close the Manage window and then begin the I/NET Seven install again. MSDE will install correctly as well as the rest of the I/NET Seven install.

Issue In the TAC Xenta 151-D, the nvoAlarmStatus handles the test of the dampers, but the translation of the status is not documented Environment TAC Xenta 151-D Cause nvoAlarmStatusis used to report the actual status of the fire damper tests. Resolution nvoAlarmStatus is a SNVT_state with the use of the following bits: nvoAlarmStatus.bit0 = 1   OBJECT1_CLOSE_TIME_TOO_LONG    nvoAlarmStatus.bit1 = 1   OBJECT1_CLOSE_TIME_TOO_SHORT   nvoAlarmStatus.bit2 = 1   OBJECT1_OPEN_TIME_TOO_LONG     nvoAlarmStatus.bit3 = 1   OBJECT1_OPEN_TIME_TOO_SHORT    nvoAlarmStatus.bit4 = 1   OBJECT2_CLOSE_TIME_TOO_LONG    nvoAlarmStatus.bit5 = 1   OBJECT2_CLOSE_TIME_TOO_SHORT   nvoAlarmStatus.bit6 = 1   OBJECT2_OPEN_TIME_TOO_LONG     nvoAlarmStatus.bit7 = 1   OBJECT2_OPEN_TIME_TOO_SHORT    nvoAlarmStatus.bit8 = 1   OBJECT1_SET_CLOSE_TIME_FAILED nvoAlarmStatus.bit9 = 1   OBJECT1_SET_SELFTEST_OK        nvoAlarmStatus.bit10 = 1  OBJECT1_SET_SELFTEST_FAILED    nvoAlarmStatus.bit11 = 1  OBJECT2_SET_CLOSE_TIME_FAILED nvoAlarmStatus.bit12 = 1  OBJECT2_SET_SELFTEST_OK        nvoAlarmStatus.bit13 = 1  OBJECT2_SET_SELFTEST_FAILED     

Issue How does the "Door Closed Timer" work in the I/NET Seven Door editor? Environment I/NET site with Access Control Cause Explaining the Door Closed Timer in the I/NET Seven Door editor Resolution Set the duration of the Door closed timer to a value from 0 to 25.5 seconds (0.1-second increments). This timer determines how long the door must remain closed (as sensed by the door sense switch) before an unauthorized door open condition will trigger a "forced door" message. Use this feature to help prevent false "forced door" messages that can sometimes occur when a door closes, but then bounces enough distance to trigger a temporary open condition at the door sense switch.

Issue Anti-passback and AIC defined on the same door not working correctly Product Line TAC INET Environment I/NET Seven prior to rev 2.11 Cause Before the release of I/NET Seven Rev 2.11 there was an issue with having APB and AIC on the same door. Basically the issue was the AIC function ran upon an entry into a zone, but it also ran the AIC function on the exit from the zone as well. This was an incorrect operation. Resolution In order to correct this function, a change was made in the AIC editor allowing the user to choose which reader (zone number) the AIC should run during a card read. Choose the entry reader (zone number) to have the AIC run only during an entry into that zone or choose the exit reader (zone number) to have the AIC run only during an exit from that zone. Door editor settings   On the right side of this window will be an entry zone of #3 and an exit zone of #1. This is a little confusing to people, in the Transaction table in AMT you will get a double transaction on an entry & exit card read. For example during a card read with the settings above on an entry. You will get “Exit from Zone 1 and entry into Zone 3”. This is why the setting above is seen this way. Zone lay out   As stated above the Transactions from an APB door will be this: Entry read—Exiting from Zone 1 and entering Zone 3 Exit read --- Exiting from Zone 3 and entering Zone 1 AIC Settings   In the AIC setting above the Zone listed is #1, in the case the AIC will run only during an entry card read based on the setting in the Door editor above. Now if you want the AIC to function only on the exit from Zone #3 then replace the #1 in the APB zone above with in this example #3. In this case the entry reader will only let you in the door (NO AIC functions) and upon the exit from Zone 3 the reader will open the door and also give the AIC functions.

Issue I/NET Anti-Passback (APB) rules. Product Line TAC INET Environment I/NET Cause Assistance with setting up Anti-Passback (APB). Resolution Note: Use of the Anti-passback option described below requires that a DPU have both an entry reader and an exit reader. An elevator DPU will support only an entry reader, and therefore, will not support anti-passback. Activate or deactivate the Anti-passback option. This option is not available if you have activated the Elevator option described in the previous step. Activate the Anti-passback option to prevent persons who have successfully gained access into an access-controlled area from passing their key/card back to another person desiring access. Refer to Implementing Anti-passback for more information. Note: The actual system response for both anti-passback and anti-tailgate (below) is controlled by the anti-passback scheme selected for the individual (see Individuals Parameter Editing). Activate or deactivate the Anti-tailgate option. This option is only available if you have activated the Anti-passback option described in the previous step. Activate the Anti-tailgate option to discourage users from following another person through an access-controlled door without reading their own keys/cards for access. Refer to Implementing Anti-tailgate for more information. If you activated the Anti-passback option in the previous step, the Entry Zone and Exit Zone parameters will become enabled. The valid range is 0–64. Enter an Entry Zone number. This is the number of the zone where the entry reader is located. Refer to Implementing Anti-passback for more information about entry and exit zones. Enter an Exit Zone number (0–63). This is the number of the zone where the exit reader is located. Leave this field blank if there is no exit reader. Refer to Implementing Anti-passback for more information about entry and exit zones. Note: If the Anti-tailgate option is enabled, any door between the secured area and the non-secured area must have the same zone number for both exit and entry. The non-secured area is any region not under access control, such as a lobby, public area, or the outdoors. Set the Anti-passback Reset Time (0 to 60 minutes). Any value higher than zero (default) will cause the anti-passback flag to be reset for each individual the specified number of minutes after the individual passes through the door. If an "APB Reset" action has been defined in the mode schedule of this door point, it will still be honored (i.e., the individual's anti-passback flag may be reset by the APB Reset action before the time specified in this field has expired). If you leave this parameter at the default value of zero, no timed reset of the anti-passback flag will occur. In this case, only an APB Reset action defined in the door's mode schedule will reset the anti-passback flag. Refer to Resetting the Anti-Passback Flag for more information. The purpose of the anti-passback function is to prevent persons who have successfully gained access into an access-controlled area from passing their key/card back to another person desiring access. Activate anti-passback for a particular door in the Door Extension editor. The system response depends on the anti-passback scheme selected in the Individual Parameters editor. The options are as follows: Hard (default) — access is denied, generates an alarm. Soft — access is granted, generates an alarm. Graced — access is granted, no alarm is generated. This effectively cancels anti-passback for the individual. Although the Anti-passback parameter (activated from the Door Extension editor) is used to enable anti-passback, implementing anti-passback also requires that you define access control zones (refer to Entry and Exit Zones, below). Note: Anti-passback requires that a DPU have both an entry reader and an exit reader. An elevator DPU will support only an entry reader, and therefore, will not support anti-passback. If you wish to have a more stringent control, you may also implement anti-tailgating.   Entry and Exit Zones Depending on the version of host software loaded on your workstation, I/NET supports either 32 or 64 zones (assigned from the Door Extension Editor). When anti-passback is enabled, the system will allow a user to be in only one zone at a time. When a user moves between zones (e.g., uses a key/card at an entry or exit reader), the system generates a zone exit message followed by a zone entry message, and broadcasts these messages to the other readers in the system. A user may enter a zone, but must use their key/card to exit the zone. If they do not (i.e., they leave a zone when another person uses their key/card), then I/NET will not allow them to re-enter any other zone using their key/card. Zones Example:   Zone Numbering Rules When populating the door editor, enter the zone number where the reader is physically located. Entry readers should be located on the exterior of a controlled zone. Exit readers should be located on the interior of a controlled zone. Exterior doors, in access control terms, are doors that lead from a non-controlled area into an access controlled area. These doors are not necessarily on the exterior of the building. The entry reader at an exterior door is physically located in an area that has no zone number (i.e., a non-controlled area). The zone number assigned to the entry reader of an exterior door should match the zone number assigned to the exit reader of that door. The example above shows a facility with three anti-passback zones that share doors. Using the example, the door leading from zone 1 to zone 3 has an entry reader physically located in zone 1. The zone number assigned to the entry reader is 1, even though this reader is used to gain access into zone 3. This door also has an exit reader that is physically located in zone 3. The zone number assigned to the exit reader is, therefore, 3. Each exterior door shown in the example has entry reader and exit reader zone numbers that match. This causes I/NET to generate only one zone entry or exit message after a valid read at an exterior door. This also makes it unnecessary to use a zone number for the exterior (non-controlled) area of the building.   The following two types of anti-passback are available: Soft anti-passback — The anti-passback flag is set when a key/card is successfully read, and a door sense switch is activated. This would occur when the door is opened. Hard anti-passback — The anti-passback flag is set when a key/card is successfully read at the entry reader. In this case, the anti-passback flag would be set even if the door were never opened. If anti-passback is enabled, hard or soft anti-passback is automatically selected by I/NET. The system looks at the Door Sense Switch parameter setting (this parameter is available from the Door Extension Editor). If a sense switch is defined (normally-open or normally-closed), the system uses soft anti-passback. If no sense switch is defined, the system uses hard anti-passback. Although the Anti-passback Type parameter (available from the Door Extension Editor) is used to enable anti-passback, implementing anti-passback requires that you define access control zones (refer to Entry and Exit Zones, below). Note: Anti-passback requires that a DPU have both an entry reader and an exit reader. An elevator DPU will support only an entry reader, and therefore, will not support anti-passback.   Additional Clarification: Anti-passback can be very complicated or simple depending on the site. Hopefully after looking at these documents, and reading this example, explains what the site setup could be. Let’s assume each door has an entrance and exit reader. This is required for anti-passback. Let’s also assume that all the readers are on the same Link (NPR). This is required for anti-passback. This example is a hallway with 32 rooms such as a hospital or school. Let’s set the hallway up as zone 1. Scenario 1: If you want the 32 rooms to have the same zone, set them all up as zone 2. This will allow the individuals to pass into any of the 32 rooms. Room 2 – Zone 2 Room 3 – Zone 2 Room 4 – Zone 2 and so on. Scenario 2: If you want to keep the individual(s) specific to their room and not all 32 rooms, you want to have different zones for each of the 32 rooms. Room 2 – Zone 2 Room 3 – Zone 3 Room 4 – Zone 4 and so on. There are other considerations, if the rooms have access to each other without scanning back into the hallway (zone 1). If there are exterior door from the hallway, it also would be zone 1.

Issue Is there a way in I/NET Seven to determine the Hexadecimal number of a prox card? Product Line TAC INET Environment I/NET site with Access Control Cause Determining the Hexadecimal number of a prox card Resolution Go into AMT and select "System" on the top task Bar. Choose the highlighted options. All you have to do in this window is the hit the "OK" button. This will set up an AMT screen called "No Filter" If the card you are seeking the Hex number IS NOT in the Individuals editor, and you read that card at any system reader it will give you the Hex number on the card under the “Message” area. The only other choice in getting this information is thru a RS232 device like the ones sold on RfIdeas.com.

Issue Running I/NET Seven as a Service and now my IDisc Wand will not function. Product Line TAC INET Environment I/NET site with IDisc Cause Running I/NET Seven as a Service and IDisc Wand will not function Resolution There are some changes within Windows that you have to do in order for the IDisc Wand to function. The attached link will explain how to do this. The Steps listed in "Red" are for the IDisc Wand changes. I7SrvsIdisc.doc

Issue How to set up Image Verification in an I/NET Seven system. Product Line TAC INET Environment I/NET site with Access Control Cause Setting up Image Verification in the I/NET Seven system Resolution The attached link will explain the proper way to set up the "Image Verification" feature of I/NET Seven. Image Verification setup.doc

Issue Memory requirements for converting access control to large numbers (Hex) Product Line TAC INET Environment I/NET Cause When using HEX card numbers the SLI will reserve memory for all required cards. Resolution The attached link will explain the memory requirements for the SLI using the Large (Hex) Number scheme. SLI Storage Capacity.doc

Issue Setting up an AIC (Access Initiated Control) to turn on an AHU or other systems Product Line TAC INET Environment Access Initiated Controls Event Sequence Cause Access Initiated Controls are used to fire a DO on any entry or exit event from the security system. This can be used to accomplish just about any sequence of events, but it most commonly used for after hours enabling of HVAC equipment upon badging in. Resolution Define all the points in the database. Then choose one as the AIC Trigger point and define an "Event Definition" on that point   This is how the "Event Definition" looks   Close out of the Controller Summary and Select Edit>Controller>Event Sequences Create a New event sequence.  Since the AIC Trigger is also an external point that starts the AHU you do not have to start that point. However, you have to stop that point. In my example here the AIC runs the points for 3600 seconds and stops the AHU followed 5 seconds later stopping each of the Floor Lights. If the AIC Trigger were an internal DO, you would need to also trigger the AHU S/S   Once you have programmed your Event Sequence, you can test it by manually triggering the DO point. When everything works correctly, select Edit>Controller>Access Initiated Control Create a new AIC You will notice the Trigger point is the AHU S/S (DO). This DO is triggered from a Reader Entry by a valid card   This is where you define which door reader the AIC is triggered from. If desired, you can have several doors such as all perimeter doors trigger the AIC.   This is where you select which person is allowed to trigger the AIC with their card read. In this example the only person allowed to trigger the AIC is Fred Flintstone. You can also select the "All individuals in Range" checkbox in the AIC editor to allow all individuals from a specific tenant to trigger this AIC.   Once you have created the AIC you can test your programming. Remember that the AIC piece is only supposed to trigger the DO and the event sequence will actually turn everything else off or on.

Issue How do I promote a Client PC in the I/NET Seven System? Product Line TAC INET Environment I/NET Seven site Cause How to promote a Client PC in the I/NET Seven System Resolution The attached link will explain the procedure of promoting a client PC within the I/NET Seven System. How to promote a Client PC.doc

Issue How to properly remove a Client PC from the I/NET Seven System Product Line TAC INET Environment I/NET Seven site Cause Steps to completely remove a Client PC from the I/NET Seven System Resolution Go into the IOServer Driver on the File Master PC Select the "Modify" for the active config. Look for the "Clients" Button in the middle of the window.   Click on the "Clients" button, this open another window   In the above window will list all of the clients in the Inet System. Since I only have one client in my system this is the way mine looks. Scroll down the list and highlight the PC you wish to remove from the File equalization list. You remove the PC by selecting the "Drop" button above. This will remove that PC from the File Masters list of PC to update. Go to the Actual PC you wish to remove. The go into that PC's IOServer Driver and Select the "Modify" button Demote the Client by either removing the File Masters computer name or its IP address in the "Filemaster name" box   Following all these steps above will remove this PC's Name/IP from the list of PC to scan during the File Equalization process.

Issue Alarm not received by Vista Workstation with a Xenta 511/527 present Environment TAC Vista Workstation Xenta 511, 527 Alarm queue Cause Vista Workstation or the Xenta 511/527 can act a the alarm master. If the Xenta 511/527 is set as an alarm master then it will intercept the alarm before it gets to Vista Server. Resolution To check whether this is happening, trigger an alarm in a Xenta controller and check the properties of the alarm object. If the status tab shows the Xenta Alarm Status as "Alarm" and the this alarm is not present in Vista Workstation then you should check the setting in the Xbuilder project.