Issue How to set the IP address of a Xenta 5/7/9xx through serial communication. Product Line Satchwell MicroNet, TAC INET, TAC Vista Environment Xenta Servers Xenta 511, 527, 555, 701, 711, 721, 731, 913 Cause If the IP address of a Xenta 5/7/9xx is not known initially, then no configuration can be done through the IP interface. The IP address must be set through serial communication. Resolution IP setup for a Xenta server (Xenta 5/7/9xx) through serial communication for step-by-step instructions for this process.

Issue How to set the IP address of a Xenta 5/7/9xx through serial communication. Product Line Satchwell MicroNet, TAC INET, TAC Vista Environment Xenta Servers Xenta 511, 527, 555, 701, 711, 721, 731, 913 Cause If the IP address of a Xenta 5/7/9xx is not known initially, then no configuration can be done through the IP interface. The IP address must be set through serial communication. If the device is new out of the box, or has attempted recovery after a format command, please see Default IP address following Xenta Server "format" command is different than from factory for the known default IP addressing. Resolution Preparation: You need to have an RS-232 serial cable (TAC Xenta Programming Serial Kit 0-073-0920-0). Plug the RS-232 cable in to the RS-232 B port. The RS-232 B port is the second left port at the front. Then connect the other end to the computer. Configuration steps: Go to Start > All Programs > Accessories > Communications > HyperTerminal, and open the HyperTerminal. In Connection Description Windows, type any name you like in the Name box. Click OK. In the Connect to window, choose the correct COM port that the RS-232 cable is using. If you do not know which COM port it is using. Go to your computer device manager. (Right click on “My computer” icon, and choose “Manage”. Then under “System Tools”, choose “Device Manager”. Find “Ports (COM & LPT)” and expend it Find the COM port number that is used by the RS-232 cable. Click OK. In the COM Properties window, type 9600 for “Bits per second”, 8 for “Data bits”, “Parity” is None, “Stop bits” is 1, and “Flow control” is None. Click OK. Options: you can save this setting for future use. Click on File Menu and Save. Press ENTER to activate the command prompt. Default username and password is both “root”. Type “root” and press ENTER for both the username and password. Type “setip” and press ENTER. Type the appropriate information for DHCP, IP-address, Subnet mask, Default gateway, DNS, Website name, Domain name, and Host name. Type “yes” for “Do you want to restart the IP interface”. Quit HyperTerminal when the restart is finished. See [Video] Setting the IP address of a Xenta 5/7/9xx through serial communication to watch a video of this process.

Issue The Xenta 7xx from factory it has the default IP address 192.168.255.2, which also is stated in the manual. But when you run the “format” command on a Xenta 7XX, you will get IP address 172.22.1.5. Product Line Satchwell MicroNet, TAC INET, TAC Vista Environment Xenta Servers Xenta 511, 527, 527 NPR, 555, 701, 711, 721, 731, 901, 911, 913 Cause The format command will wipe all memory from the Xenta Server. Its IP address will need to be reset, system program will need to be reloaded, and XBuilder project will need to be redownloaded. Resolution The Xenta from factory has the default IP address 192.168.255.2 subnet mask 255.255.255.0 After the “format” command it will have IP address 172.22.1.5 subnet mask 255.255.255.0 See IP setup for a Xenta server (Xenta 5/7/9xx) through serial communication for instructions on setting the IP address to the desired address.

Issue Separate a 7792 or 7793 into two 7798C Split SAV files  Product Line TAC INET Environment I/NET Seven 779x Controllers Cause Need to replace a 7792 or 7793 which has two station addresses and replace with two 7798C Controllers which have one station address Resolution To split the required SAV Files: Download and Extract the attached SAV_Split_EXE.zip Make a backup of the I/NET Seven system using DBCreate. Perform Station Save to all the required controllers Copy the SAV files that need to be split to the same location where the ZIP file was extracted too in step 1. Run the SAV_Splt.exe The commands are showing the Sav_Splt.txt file contained within the ZIP file and shown below Purpose: Use this tool to create two 7798 SAV files from a dual-station 7793 SAV file. Syntax: Sav_Split.exe (with no parameters will check all save files in the current directory and split 2 station 7793s.) Sav_Split.exe LLSS (where LL = Link and SS = Station) Result: The resulting files will be named DCULLSS-0.SAV and DCULLSS-1.SAV. Rename these files appropriately to match the link and station of the 7798 into which each will be loaded. Example: SavSplit.exe 0906 Results: DCU0906-0.SAV and DCU0906-1.SAV     Finally check the split files using the "Work Offline" mode within I/NET Workstation. Any issues or additional questions please raise a case with your local support   For SAV file upgrade information see How to upgrade bin and SAV files in I/NET controllers.

Issue AMT has stopped receiving data AMT is not receiving data A new link added to a system, is not sending messages or transactions Product Line TAC INET Environment I/NET Cause AMT can stop receiving data for several reasons. Connection between Remote Client with I/O and SQL is broken AMT is Paused Communication to the device is not functioning AMT Masking is not set correctly Host Masking is not set correctly Point Masking is not set correctly Door Editor Masking is not Set The software has frozen I/NET has reached its maximum online event size and FIFO is not working (very rare) Other Resolution Connection between Remote Client with I/O and SQL PC is broken. Check that no other I/NET PCs are connected to the SQL database. This may include an instance of I/NET installed on the SQL PC Restart the I/Net Remote Client with I/O to re-establish the connection with the SQL Server Wait several minutes for data to update. If this fails, ensure that there are no firewalls or communication failures between the 2 PCs. If using I/NET v2.42 there have been instances where this version does not pass events to the SQL Server.  This is fixed in v2.43 or greater. AMT is paused Right-click anywhere in an open Alarm/Transaction/Message window The bottom choice is either "Pause" or "Resume" If it is "Resume" click on that and AMT function will be restored Communication to the device is not functioning Minimize AMT and open I/NET Connect to the controller Select Summary>Controller If you see values and get no error messages this is not the issue If you cannot see values or get a "No Entries in Database" error, determine why communication is down AMT Masking is not set correctly In AMT Select Edit>Configuration Note the current settings, take a screen shot and save it if possible For troubleshooting purposes, select all of the check boxes under "Messages/Alarm" Restart the I/O server In I/NET trigger a point to go into alarm or send a message Check AMT for successful delivery Host Masking is not set correctly (TCP/IP only) Right-click on the I/O server and select Configure Modify the Active Profile On the bottom of the screen click on "Host Masks" Select any NPR or 527 Note the current settings Check all boxes Click okay Repeat 4-7 for all NPR or 527 devices Restart the I/O server In I/NET trigger a point to go into alarm or send a message Check AMT for successful delivery Point Masking not set correctly Connect to a controller that you expect to receive messages from Select Edit>Controller>Resident I/O Modify a point you expect to receive messages from Ensure that the appropriate Mask bits are set Ensure that there is a priority set for both Messages and Alarms Click okay Go to the controller summary and attempt to trigger a message or alarm Door Editor Masking is not Set Connect to a controller that you expect to receive messages from Select Edit>Controller>Doors Modify a door you expect to receive messages from Ensure that the appropriate Mask bits are set Ensure that there is a priority set for both Transactions and Alarms Click okay Attempt to trigger a message or alarm The software has frozen Restart the I/O server If this does not work restart the computer I/NET has reached its maximum online event size and FIFO is not working (very rare) Right Click on the I/O server and select Archive Configuration Enable Archiving if it is not enabled Increase the size of the maximum online events Restart the I/O server Trigger an Alarm or Event in I/NET Verify AMT  Other troubleshooting steps Force a Lan to reconfigure by changing the station address of the Xenta 527, then changing it back If AMT still will not function Repeat the above processes using an Event window with no filter.  It is possible messages are being received, just not to the open Window Close all open AMT windows Select System>New>Event Window Click Okay This opens an Event Window which will display all data coming into AMT Repeat the above troubleshooting processes The Controller LAN is having communication issues Cycle power on one of the Controllers on the Controller Lan to force a Lan Reconfigure Other solutions for this issue have been documented in these articles: No door transactions coming into AMT: Quick Poll is not enabled.  Typically applies to older sites. Transactions not Updating AMT Window using direct connect: For Direct Connect systems No Transactions or controller Events in AMT: Reliable Tap AMT messages stop after re-installing I/NET: Applies to recently upgraded sites.

Issue If an application hangs or crashes, Windows systems are sluggish or have problems, or new software fails to install properly one of the first places to look for information on what may be happening is the Windows Event Log. Product Support personnel may ask to see a copy of the Windows Event Log. Product Line TAC INET, TAC Vista, Andover Continuum, Satchwell MicroNet, Satchwell Sigma, TAC IA Series, Field Devices, EcoStruxure Building Operation, Other, EcoStruxure Building Expert, Access Expert, Security Expert Environment Windows Operating System Cause If an application hangs or crashes, Windows systems are sluggish or have problems, or new software fails to install properly one of the first places to look for information on what may be happening is the Windows Event Log. Resolution   Open the Event viewer by one of the ways below: Start Event Viewer by pressing Windows key + R to open the Run dialog box and type eventvwr. Right-Click on "This PC" and select "Manage" then navigate to Computer Management (Local) > System Tools > Event Viewer. Select the type of logs the need to be exported. Application, Security, and System logs in the Windows Logs and Schneider Electric Security Expert logs under Applications and Services Logs (for Security Expert cases) are required.  For each log, view recent messages then click the "Action" menu and select "Save All Events As". Enter the log name, include the log type (Application, Security, or System) in the log name, and location the click "Save". For non-English Windows, make sure to select English (United States) in "Display information" then click OK. 

Issue "Software file not found: 7797**.bin" when downloading bin on a 7797 ICI Product Line TAC INET Environment I/NET site with 7797 Cause Error Message in software file not found: 7797**.bin when downloading bin on the 7797 ICI Resolution The reason the Software Restore command is looking for a 7797**.bin file during the download is due to one of two reasons. The ICI has not been configured in the Edit->Controller->Configuration screen to specify the ICI type. Example: 12 for BacNet, 15 for Modbus. Copy corresponding bin file under /Support/Bin/ in the installation CD of I/NET to the Data directory. The download should be OK now.

Issue There is only 1 input available, but the end-user wants more than 1 sensor to be connected, where the reading will be averaged. Product Line EcoStruxure Building Operation, EcoStruxure Building Expert Environment Building Operation Workstation Building Operation Automation Server SSL SE8000 Cause The wrong sensor type or incorrect wiring might have been used. Resolution 4 resistive sensors of the same type are required. Depending on scenario, 2 sensors may have to be fitted adjacent to each other, or fit 2 sensors into 1 sensor housing to achieve the correct number of zones to be monitored. For wiring follow the drawing below:

Issue User Definable Buttons and Tools Product Line TAC INET Environment I/NET Seven site Cause How to make user-defined buttons that will allow the user to set up shortcuts for reports and events Resolution Configuring User Buttons I/NET now has the ability to add a User-defined button that will allow the user to set up shortcuts to reports and events. I/NET displays this editor when you select Tools Define Buttons from the main menu. Use this editor to create up to 16 user-defined buttons. Configure user buttons as follows: Highlight one of the 16 user button entries from the list and select Modify. The system displays the User Tool Configuration editor. If the desired tool has already been configured, highlight it in the list and select OK. The User Tool Configuration editor closes and the selected tool is added to the user button. Skip the following step and proceed with step 4. If the desired tool has not already been configured, configure the user tool now (refer to User Tool Configuration). Then highlight the user tool and select OK. The User Tool Configuration editor closes and the selected tool is added to the user button. Select OK to accept these settings. The button is now available when you select Tools from the main menu. Configuring User Tools I/NET displays this editor when you select Tools Define Buttons from the main menu, or when you highlight a button entry in the User Button Configuration editor and select Modify. Use this editor to define tools that you can assign to any of 16 user-defined buttons, or that you can activate from live graphic pages. Two kinds of tools are available: Event – Use this tool to execute an event sequence defined in a controller. Shortcut – Use this tool to launch another application, open a file, visit a website, etc. Options The following options are available in the User Tool Configuration editor: Add – Use this option to create a new tool. The system displays the User Tool Type dialog. Delete – Delete a tool by choosing a tool from the list and selecting Delete. The system prompts you to confirm the delete request. Select Yes to delete the selected tool or select No to cancel the Delete request. Modify – Use this option to modify an existing tool. Highlight a tool in the list and select Modify. The system displays the User Tool Type dialog. Copy – Use this option to create a new tool by copying the selected tool. The system displays the User Tool Type dialog.

Issue How to find a card number in a transaction when Large Card numbers are used? It seems that no card number is shown in the transaction window and Deny Entry Tenant event message is seen in the transaction window Product Line TAC INET Environment I/NET Seven  Access Control  Cause The column containing the card number doesn't show in the transaction window by default, this must be added which will show the raw card number.  This is true ONLY when the card is NOT programmed into the database, the event message will say Deny Entry Tenant. Resolution With the Transaction window open, right-click and select "Window Options". Double click the Message column from right to left to make it visible in the transaction window. - Location is not important  With this column now displayed the raw 'large' card is shown in the transaction window.

Issue Receive the following error message within I/NET:  Default system page: File does not exist! Environment I/NET Seven all revisions Cause Under the Host Configuration Editor there is a setting for the Default system page.  The path and filename in this section must be correct. One or more points on a graphics page have the check box for Automatic page and / or Home Page options checked in their property settings when added to a graphics page.  (See boxed section below):   I/NET generates the above error when the alarm is triggered and this setting has been checked.  The other instance that generates the error is when selecting the Home Page option from within AMT, either by right-clicking on the point in alarm or using the Home Page icon .  The error is generated because the original graphics page has now been moved, renamed or deleted from its original state when these points were added to the graphics page.  This causes I/NET not to find the graphics page and hence display the error. Resolution  To remove this error check the following two possible causes: A.  Host Computer Configuration - Default page setting incorrect: Ensure that the Host Configuration is pointing to the correct path / filename for the default graphics page.  This is achieved as follows: Log in to I/NET Go to Edit > Host Computer > Configuration Within the Host Computer Configuration editor check within the Monitor section that the Default system page (as shown below) is valid.  If not use the browse button [...] to locate the default page you wish to use. Select the correct page, click Open then click OK to close the editor. Log out and back in to check that the correct page opens. B.   Home Page / Automatic Page display references are invalid: The resolution for this can be done in two ways:  1. Modification of Home Page references Note this method can not be used if the page has been deleted.  If you know or have some knowledge of which pages have been changed, then you can modify the path by editing a file as follows:  Locate the I/NET Seven Data folder, by default this is located in "C:\INET Seven Data\Data"  This folder should contain a file called: HOMEDIR Using a text editor open this file and carefully locate the relocated path and modify these entries (Note their may be multiple entries of the same graphics page). Save the file and confirm the Home Page or Automatic Page display option now works. If this does not work then the only solution is to recreate all the home page references as described in the below procedure.  2. Recreating all references to Home Page points: If the page names are not known or the graphic page has been deleted then the above process may assist to locate other graphic pages which have Home Page references, making this process somewhat shorter.  This method will correct the error by re-creating all links to the Home Page / Automatic Page display used within your I/NET system. The steps for this are as follows: Locate the I/NET Seven Data data folder, by default this is located in "C:\INET Seven Data\Data" This folder should contain two files called: HOMEDIR HOMEPAGE Delete these two files Now edit each page via the Graphics Editor and save each page.  The saving process will recreate the references to these pages back into the above file names. Note: If the graphics pages with references are known then you only need to visit those graphics pages; if not then all graphic pages will need to be edited / saved to ensure all references are re-created. Test its operation to confirm this process has functioned as expected. If the problem still persists then please email Product Support with the Graphics, SAV files along with the HOMEDIR & HOMEPAGE files mentioned above.

Issue Is there a way to use points in I/NET Seven to calculate the "Heat Index"? Product Line TAC INET Environment I/NET Cause Desire to use Heat Index information Resolution You can determine the "Heat Index" within I/NET Seven. The only External points required are the following: Outside Air Temperature sensor Outside Air Relative Humidity sensor Please see the attached Word doc that shows the Calculations involved: 

Issue Need to capture steps taken to reproduce a problem or a solution Product Line Andover Continuum, EcoStruxure Building Expert, EcoStruxure Building Operation, Field Devices, OTHER, Satchwell MicroNet, Satchwell Sigma, TAC IA Series, TAC INET, TAC Vista Environment Windows 7 Windows 10 Windows Server 2008, 2012, 2016 Cause A series of screen captures will help to demonstrate the steps needed to reproduce a problem or a solution. You can use this tool to capture the steps you take as a problem occurs and send the output to someone so they can see a screenshot of each step. Resolution In Windows click on the Start menu button  Type "PSR" Windows 7Windows 7 Windows 10, 2012, 2016Windows 10, 2012, 2016 Open the Problem Steps Recorder Windows 7Windows 7 Windows 10. 2012, 2016Windows 10. 2012, 2016 Click Start Perform the desired tasks Click Stop Choose a location to save the file output The .zip file will contain a .mht file which can be opened in a web browser The screenshots will appear in order  This will be followed by a detailed output of keystrokes and mouse movements. For additional information please refer to Microsoft webpage on this topic: Record steps to reproduce a problem 

Issue What is the purpose of the battery/coin clip on some of the I/NET Hardware Product Line TAC INET Environment TAC INET Hardware  7718, 7716, 7798C  Cause The initial development path plan was to include an additional feature to allow communication with Dallas Semiconductor ID tag/coin, similar to that used with the I/NET Access Control I/DISC.  This development was never implemented Resolution This battery/coin tag serves no active purpose or functionality

Issue Number of individuals that a controller can have based on the firmware revision. Adding individuals to a system that has more than 24,000 users and is not working. Product Line TAC INET Environment I/NET Seven DPU 7910 DPU 7920 with or without 48K MIP Card SCU1284 Cause Although TAC I/NET supports up to 32,000 individuals per tenant, the model type and revision date of a tenant’s door controllers will ultimately determine how many individuals will be supported Resolution I/NET Supports up to 32,000 individuals per tenant based on the model type and revision date of the tenant's door controllers determines how many individuals it will support. The following table shows the capacity of the various door controllers. Firmware Revision Door Controller Maximum Number of Individuals Maximum number per Tenant 2.1X and earlier DPU 7910, DPU 7920 Up to 24,000 per door 24,000 2.2X to 3.23 DPU 7910, DPU 7920 w/o 48K MIP Up to 48,000 per controller. 24,000 DPU 7920 with 48K MIP, SCU 1284 Up to 48,000 per door 1 3.24 and later DPU 7920 with 48K MIP, SCU 1284 Up to 64,000 per door 1 32,000 1 Typically, the total number of individuals for a selected door cannot exceed 32,000. However, if one of the two doors controlled by a DPU is not being used (that is, no individuals are assigned to the door), you can assign up to 64,000 individuals to the door that is being used. This also requires the use of more than one tenant since no single tenant can have more than 32,000 individuals.

Issue What track is used for ABA data? Environment ABA Magnetic stripe cards and readers. Cause Card format information required. Resolution ABA data is usually stored on Track 2 and requires a track 2 reader to decode the data. ABA Magnetic Stripe Format.

Issue Programming an 8-Bit HID or Indala Prox/Pin Pad reader Environment I/Net Site with Access Control Cause There is a requirement to supply an 8-Bit Prox/Pin Pad reader at a site. How do I program this reader? Resolution Attached is a PDF File that guides you through the setup if this type of reader in an I/Net Seven system. Click here to download.

Issue Site Access Control lockdown for the entire complex. But, also allow certain cards to override certain doors during an emergency situation. Environment I/NET site with access control Cause There is a requirement to lockdown an entire complex with a single toggle switch, but allow First Responders access to certain locked doors in the building. Resolution  There are two different Demo programs for this process One Link program (Download One Link Zip file): MCI -- 7798 DPU – SCU1284 (2 addresses) A maintained switch SPDT   Two or more Links program (Download Two Link  Zip file) MCI – 7798 Link1 MCI – 7793 Link2 – Channel “B” SCU1284 (2address) Link1 SCU1284 (2address) Link2 – On second channel A maintained switch SPDT Each of the above zip files have the following inside: Note: This would be restored to your test bench, and then configuration implemented into a production site.

Issue How to set up ID Works 6.5 in Windows 7 64-bit. Product Line TAC INET Environment ID Works version 6.5 I/Net Seven rev 2.4X SQL2008 R2 (Full) SQL2008 R2 Express Cause Normally this is needed for an upgrade or a new install of ID Works and I/Net Seven on a new Windows 7 64-bit PC. Resolution See ID Works Win7 64-bit Setup.pdf for step by step instructions for setup.

Issue When opening I/NET on a secondary monitor, and open the point control window of I/NET summary for a digital output, the drop list for the point doesn't work. Nothing is shown in the drop list. Product Line EcoStruxure Building Operation,TAC INET Environment I/NET SmartStruxure Cause There is a 3rd party system dll file out of date for I/NET. Resolution There is a 3rd party system dll file under the folder C:\Program Files\INET Seven\Program Files (Program Files (x86)) if for a 64 bit Operation System called SftBx32.dll. Click here to download the new dll file and extract it. Close I/NET IO Server and SmartStruxure Enterprise Server Copy this new dll file and replace the old one under that path. Start I/NET and SmartStruxure again, and it should work now.