Building Automation Knowledge Base

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 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 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 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 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 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 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 Xenta 102-ES Flow Calibration Plug-In Error An error message is generated that reads: Balancing Error Errors occurred during balancing and values for nciBoxScale, nciNomFlow and nciBoxOffset and values have been reset. This can be caused by air flow not being stable during the balancing process, or due to incorrectly measured values. Returned values were: nciBoxScale = XXX, nciNomFlow = XXX, nciBoxOffset = XXX. You should try doing the balancing process again.   Product Line TAC Vista Environment Xenta 102-ES Plug-In Cause If the Lonmaker plug-in for the Xenta 102-ES gets a negative result on nciBoxOffset during calibration, the "Apply" button can be hit and all works fine. However if the plug-in is closed and then re-opened, the flow page will show values that do not match what was calibrated to. Resolution Do not make any adjustments or changes after the device has been calibrated.   You should hit cancel if you go to the flow page after a box has been calibrated and not Apply. If you do hit the "Apply" button, it corrupts the data in the device and you will need to re-calibrate. Also if you want to check flow values on a box after a calibration has been done, do so in Vista or in the LonMaker Browser, not through the plug in flow page.

Issue Sunrise/Sunset Settings on a PCU Product Line TAC INET Environment I/NET PCU Sunrise/Sunset Time Schedule Cause Are you using Sunrise/Sunset settings on a PCU to control lights and they are turning on and not off when they should? There could be several things that would cause this not to function properly: Do you have the correct Latitude/Longitude and Zone Settings? Are you using a 0-Stop for Sunrise and 1-Start for Sunset? Are you using the correct Control Descriptions for Time Schedules? The TS in the PCU sends a 0 command (first of the pair) to the control point for the Start action and a 1 command (second of the pair) for the Stop action. If the Control Description pairs in your application are set to send a 0 (de-energize) command as a Start then simply switch the Sunrise action to be a Start and sunset to Stop. Resolution There are a couple of workarounds to this issue depending on the way the relays are terminated and the settings for the first of the pair in Control Descriptions. Using the Sunrise/Sunset settings, a third start command for 1 minute after midnight (12:01 AM) sends a re-enforce command to the controller. Use actual times instead of sunrise/sunset as long as the times used are well after both the Sunrise /Sunset settings have elapsed. Verify the correct latitude and longitude are set. Here is a website to check the exact location: www.airnav.com. Additional information on the Airnav site and a new work around.

Issue Wiring an STR-202 slide stat and override into a Xenta 102-AX Product Line TAC Vista Environment STR-202 Xenta 102-AX Cause The STR-202 wiring guide does not explicitly describe jumping together pins 14 and 15 of the STR and landing them both on U4 of the 102-AX. Resolution Pins 14 and 15 of the STR-202 must be jumpered together. This output is then connected to input U4 of the 102-AX. Be sure to set the hardware configuration to "Slide Stat" in the hardware configuration tab of the 102-AX plug-in.

Issue Search for all inputs and outputs in a system that are forced by operator Find IOs that are set in manual override Product Line TAC Vista Environment TAC Vista Workstation Cause Need to find all Inputs/outputs that are set to Forced by operator (manual override). Resolution In Workstation, right click on the Lonworks object and select search. In type of devices or objects select Analog/Digital input and/or Analog/Digital outputs.     Select property value 'Forced by operator' and Select equal to 1.     (To be able to set the property value 'Forced by operator' specify Analog/Digital input and/or Analog/Digital outputs, not just Points in 'type of devices or objects'.)

Issue The cooling and heating will not work on the Xenta 121 FC/HP even though the terminal load is building. Product Line TAC Vista Environment ZBuilder Xenta 121 FC/HP Cause The default setting for both the Xenta 121 Fan Coil and Heat Pump is to have no fan feedback. If the fan interlock options are selected then the heating and cooling will not work on the Xenta 121. The controller sees the absence of the fan feedback as a fan failure, therefore locking out the heating and cooling.   Resolution If fan feedback is not required then the primary heating, secondary heating, and cooling interlock need to be unchecked. You can access these options by launching ZBuilder, click the Configuration tab, and go to Control > Fan > Interlock.   If fan feedback is required then this feature needs to be activated. Launch ZBuilder, click the Configuration tab, and go to Control > Fan > Feedback. Here you can check to activate fan feedback and choose whether it is a hardwired point.   Once the configurations have been set, go to the I/O Setup tab where you can see that "Fan proof" has been added to a DI point. You can click and drag the "Fan proof" point to any available input.  

Issue 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. Product Line TAC INET Environment Access Initiated Control Cause I/NET Seven allows configuring a door to have both an entry and an exit reader and uses the selection of Anti-passback/Anti-tailgate to set up Zones or areas with stricter control over access. However, even with the Anti-passback 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. Other than having a guard at the door the usual method of implementing Zones does not prevent violations. The example below presents some thoughts about how to improve the security of the Zone in an INET Seven system. Resolution 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 of the doors needs to have 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 Anti-pass back/Anti-tailgate can be implemented. The strike on door "a" would be normally energized and be 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 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 move into or out of the Zone at one time. 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 be a violation of 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 to get out of 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 would not be able to 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 so that would provide another fail-safe.

Issue Performing database maintenance with Vista 4.5.0 Product Line TAC Vista Environment Vista 4.5.0 SQL Server Cause It is necessary to perform backups for two reasons, first to be able to recover the system in the event of a fatal error and second to be able to manage the size of the database. Resolution Vista has a means of backing up databases on a Vista Server.  It is necessary to perform backups for two reasons, first to be able to recover the system in the event of a fatal error and second to be able to manage the size of the database.  The Vista database probably won’t grow very much after the initial engineering activity but the event and trend log database grows as events are received in Vista.  In many installations maintaining an archive of event data is required so that is another reason for backing up the database.  This paper presents a way to accomplish the backing up of the Event and Trend database and creating an archive file. Before the backup process can be implemented it is first necessary to have a good estimate of the Event and Trend Log traffic anticipated for the installation.  In the Vista 4.3.0 Technical Product Information (TPI), Ref No: C88-1-D43, there is section entitled Strategies for Calculating and Controlling Database Size.  On page 5 the method for determining database size is explained and used in the following example: Right clicking on the $Backup_LDB object in the Server View brings up this dialog.   Note that this example has an Event and Trend database that has reached 1121 (MB) in size.  The default Size Alarm Limit is shown to be 1640 and if the database grows past that size, Vista may not operate reliably. The TPI states on page 4 that events contain on average 2Kb of data.  Combining that value with the expected traffic provides a reasonable estimate of the database expansion rate.  If the installation traffic estimate is 4000 Events and Trend samples per day, the database expands at the rate of 8Mb per day.  If the installation traffic estimate is 10,000, the database expands at the rate of 20Mb per day. A conservative approach would limit the size of the active database to half of the alarm limit.  That means the backup process must be done so that the size does not get to 820Mb.  At 10000 Events and Trend samples per day that value would be reached every 41 days.  Vista is designed to allow Event driven backup operations and the closest choice it offers to the 41 days is once a month so that is what will be chosen. The configuration of backup is done in Vista Workstation by opening the Properties of the Workstation object in the tree.  The first step is to select a location for the backup files to be saved.  In the example shown below it is the folder outlined in red.   The “Max number of files” limits the number of backups that are retained by Vista on the hard drive.  The number chosen here was two (2).  The procedure that is described further down will actually move backup files to new directories which could be a network drive or a CD/DVD rom.  (The latter option requires operator action so it might not be the most desirable especially since backups are usually done at off times when an operator might not be available)  Next the event that is to trigger the backup must be defined.  The configuration of when the backup is done is set on the Log Backup tab of the Vista Server Properties dialog.  In the example shown below the backup is scheduled to occur on the first of every month at 12:40AM. The selection of Event object is made from the options made available by the browse button.     The browse selection brings up the Select dialog from which the selection of Event type and properties is done.  In the following example the selection is Monthly.   Right clicking on the $Event_LDB object opens the properties dialog box to configure the Event_Month object.  The final configuration option is what to do with older records.  Vista will remove Events from the database if you so desire.  The removal does not shrink the database but does make space available for new events to be written without expanding the size of the database.  This is the key to keeping the database from exceeding the Alarm Limit. The Event Log tab provides a way to delete old records from the database.  In the example shown below records older than 30 Days will be deleted after the backup that was done be the Event_Month object has been completed.  This means that each month the backup should have the most recent 30 days of Events and Trend samples.   The final step that can be taken is to also copy the backup file to a server that is backed up or to a CD/DVD Rom. This operation creates an archive in which Event and Trend data is stored.  Windows task scheduler can be used to run a cmd at some time after the backup operation was scheduled.  For the above example schedule it to run a 1:00am on 1 st of each month.  If backing up to a network drive create a folder such as shown below.  J:\Engineering\Vista Event Log BU.  In order for the task scheduler to run it is necessary to setup a user account on the pc that is not related to any actual user.  I added a user to the User group named, vista xcopy dbmgr.  This will be the user account used by the task scheduler.  The Vista backup folder must have modify/write permissions for this user and the folder into which the backup is going to be copied must have Full control.   The command line for this example is shown below: C:\WINDOWS\SYSTEM32\xcopy.exe "C:\Program Files\TAC\TAC Vista 4.5.0\Db2\$bkp" "J:\Vista Event Log BU" /M The Windows task scheduler is configured in the Control Panel, Scheduled Tasks as shown below:   In the Run as: box enter the name of the new User created described above: vista (xcopy dbmgr) Schedule the task to run on the first of each month at 1:00AM.   The backup files can be restored to a Vista Server that is not performing actual site monitoring.  This method is only way the “archived” event and trend data can be viewed as of Vista revision 4.5.0.

Issue What is the proper way to enter data in ID Works and print a badge? Product Line OTHER, TAC INET Environment ID Works I/NET Seven Cause Enter data properly to avoid losing data or having to redo personnel entry. Resolution Log into the ID Works Program Default user name is lowercase admin Default password is lowercase admin Choose the badge project for the card you are going to print. If you do not see the Project in the window area, select the "More Projects" button to see the complete list of projects. Once you choose the project, a window will pop up for you to log into the ID Works Project. You have a choice on how to log in. You can either choose to check the box next to "Use Trusted Connection" or under the "INetThirdParty" Login ID the password is lower case passinetdb3p. Typically, select the “Trusted Connection” option. This is a view of the Sample project that is on the I/NET Seven CD under the "Support" file folder on the CD. Next fill in all the information listed on the Production Form including taking the photo. Now that you have filled in all the info and took the picture, it is time to print the badge. On the Bottom ICON Task Bar, the second ICON in going from left to right is the "Print ICON." Before you actually print the badge, make sure the Blank cards that are in the printer magazine are the correct ones. Once you verify that the correct blanks are in the printer, and then depress the Printer ICON with the mouse. Printing the badge will also save the information in the I/NET Seven system and the ID Works system. There is NO need to save the info first, and then print the badge. Now that you still have the information in the Production Form on the Screen, DO NOT choose the RED X on the Top ICON Task Bar to clear the page. If by accident you do choose the RED X, you will get the following pop up window. DO NOT CHOOSE the YES BUTTON, if you do, you WILL DELETE ALL THE INFORMATION AND PHOTO you just entered in the I/NET Seven System and the ID Works system. If you find yourself in this situation, you NEED TO CHOOSE the NO BUTTON, doing this choice WILL NOT DESTROY ANY DATA. In order to refresh the project, go to the Top Task Bar and choose the "FILE" option. In the drop down list choose the "Close Project" option. Then select a new Project for the next badge, this process will open a new clean Production Form to fill out.

Issue Setting up an Integral DVR in I/NET Seven Product Line TAC INET Environment I/NET Integral DVR CCTV Cause Installation Resolution Please use the following link: I/NET Seven to a DVR Configuration.doc

Issue Need to remotely determine the MAC Address for an NPR or PC. Product Line TAC INET Environment I/NET Site Cause How to remotely determine the MAC Address for an NPR or PC. Resolution Please see use the following link: MacAddress from remote.doc

Issue How do I setup the Custom Pin Numbers In I/NET Seven Product Line TAC INET Environment I/NET Seven site Cause How to setup Custom Pin Numbers in I/NET Seven. Resolution Please use the following link: Custom Pin Numbers.doc

Issue Cannot get to some of the pages defined in a Xenta OP Tree. They pop back up to the submenu. Alternatively, attempts to generate the Menta file or Xenta OP Tree result in the following error:   Conversion to BIN file OP Configuration tool working, please wait... Error in opdoc.tmp near line: 2224, symbol: 'NOF_LPag036Pg02_C': Symbol table full. Product Line TAC Vista Environment Xenta programmable controllers Xenta 280, 281, 282, 283, 300, 301, 302, 401, 401:B Menta OP Tree Cause The maximum number of pages allowed in the TAC Xenta OP tree is limited to 255. A sub menu is not included in this limit, but every status page should be counted. Resolution Check if the 255 page limit has been exceeded: Open the file OPDOC.SPT after generating the OP tree. (This file is normally located in C:\Program Files\TAC\Menta\Temp). Search for the first occasion of "EOFF". This value should be below 512 (This value adds up with 1 for each page and starts at 256. 256+255=511) If the size limitations have been exceeded, the size of the tree must be reduced in order to generate the OP Tree.

Issue It is possible to make connections to the output side of a DO or AO in Menta Product Line TAC Vista Environment Menta Cause Connecting to the back end of an AO or DO ensures that the value being used by the Menta application is always in sync with the value in the Vista Workstation/OP. Any AO or DO could be put in forced-by-operator mode, and if the Menta application does not use this down the line, the desired results may not occur. Resolution You can click on the right side of the output block and connect it to other blocks.