Building Automation Knowledge Base

Issue Complexity of SQL and which version is compatible  Product Line TAC INET Environment TAC I/NET Seven and congruent Windows Operating System. File Master, Filemaster, EqualizedClient, Compatibility, SQL, SQL 2008, Full SQL, SQL 2005, SQL2008, SQL2005, SQL Express, Express SQL, MSDE, 2.31, 2.40, 2.40a, 2.41, Server, XP, Windows 7, 7, 32-bit, 64-bit, Microsoft SQL, Service Pack, SP Cause Filemaster and either Equalized Client or Remote Client is desired. Problem is to know which versions of SQL are compatible. Resolution Below is a handy chart designed to help in determining what versions of SQL are compatible in I/NET Seven. Pertains to MSDE, SQL Express, SQL 2000, 2005, 2008. File Equalization Chart       Note: 1. Do not mix versions of SQL server among equalized or client/server workstations in your TAC I/NET Seven system. Ensure that the edition of SQL server installed on each workstation used in a client/server or equalized setting are based on the same version of Microsoft SQL, either 2000, 2005, 2008, or 2008 2. It is strongly recommended that you defragment the PC’s hard drives on a regular basis. Severely fragmented hard drives can cause poor system performance and in some cases can introduce data errors. 3. The use of any edition of Microsoft SQL Server 2005, 2008, or 2008 R2 will require that the PC have at least 2 GB of RAM. 4. No Express edition of Microsoft SQL Server can be used on a TAC I/NET Seven filemaster. Golden Rule: You cannot move the db or downgrade from I/NET db SQL 2008 to I/NET db SQL 2005, see Downgrade SQL 2008 to SQL 2005, What version is used? 

Issue Step-by-step instructions for calibrating airflow on a Xenta 102-AX (or I/NET MR-VAV-AX) using the M/STAT. Test and air balance procedure for balancing airflow Product Line EcoStruxure Building Operation, TAC INET, TAC Vista Environment Xenta 102-AX MR-VAV-AX M/STAT Cause The preferred method for calibrating airflow in Xenta 102-AX or MR-VAV-AX is through the plug-in.  However, this is not always an option, especially when the responsibility for calibrating is given to a third party test and balance company.  Pocket references exist for navigating through the M/STAT menu, but there aren't clear step-by-step instructions to tell exactly how to perform the calibration. Resolution Click here to download this document in Microsoft Word format Connect M/STAT Plug the M/STAT into the jack on the thermostat. The initial display shows the set temperature.   Enter Password Press the Service button. This prompts you to enter the service mode password. Default password is 183. Use the +/- keys to set each digit and the enter key to submit. If the password is incorrect, the display will blink. Airflow Parameters If the password is correct, the first menu option – Unit Parameters (UP) – is displayed. Hit the select button down twice until Airflow Parameters (AP) is displayed. Press enter. Cooling Low Flow Setpoint The first option is Cooling Low Flow Setpoint (CLF). Press enter to view the setpoint (divided by 1000). Record this value. Press the service key to escape out of the menu. Cooling High Flow Setpoint Navigate to Cooling High Flow Setpoint (CHF). Press enter to view the value (divided by 1000). Record this value. Press the service key to escape out of the menu. Reset Factory Calibration Navigate to Factory Calibration Settings (FCS) and press enter. Use the change keys to display “YES” and press the enter key. This will set the box back to default settings. This is a good idea to do prior to every calibration. Press the service key to escape out of the menu. Calibrate Low Airflow Navigate to Calibrate Low Airflow (CPL). Press enter and the current airflow is displayed. Wait for the airflow to reach the CLF and level out. Once the value is steady at setpoint, press the enter key only once. The display does not change. Enter Actual Low Airflow Measure the actual airflow. Use the change keys to set the display value to the measured value. Press the enter key. Choose One or Two-Point Now Calibrate High Airflow (CPH) is displayed. If one-point (offset only) calibration is desired, press the service key to escape out of this mode and calibration is complete. If two-point (gain and offset) calibration is desired, press enter to continue to the next step. Calibrate High Airflow The current airflow is displayed again. Wait for it to rise to meet the CHF and level out. Once the value is steady at setpoint, press the enter key only once. The display does not change. Enter Actual High Airflow Measure the actual airflow. Use the change keys to set the display value to the measured value. Press the enter key. CPH is displayed again, this time as a general menu item. Escape Service Mode Press the service key to escape out of the menu. If you are finished configuring the box, escape all the way back out of the service menu before disconnecting the M/STAT. Disconnecting in configuration mode can leave the stat displaying “00” or other incorrect numbers.

Issue What is Remote Client with I/O in the Workstation Type in the I/O Server? Product Line TAC INET Environment I/Net Seven version 2.4x with need for Remote Client configuration using a Remote SQL Server. Equalization, FileMaster, File Master, Equalized Client, Remote Client, Equalize, FM, EQ, RC, MSDE, Express, Full SQL, SQL, TCP/IP, Connection Cause Remote Client changes with I/Net Seven version 2.4x  Resolution The new option of Remote Client with I/O for the Workstation Type begins with 2.4x version of I/Net Seven. This option is for a SQL Server which is not located on the Filemaster or Standalone but rather a separate Server. The Remote Client with I/O must be running for other standard Remote Clients to get the features such as AMT, Trends, and Network Functions. Network Functions can be found in I/Net on the pull down menu Edit/Host Computer/Network Functions. The configuration is in the I/O Server under the current profile and can be found in the Workstation Options.  HINT: Exit the I/O Server (and I/net) and select Start/Programs/I/Net/I/Net Configuration to be able to setup the Remote Client. Remote Client is not show unless you exit I/O Server. Clicking the link below will open a pdf document which will show how the communication should be setup if selecting Remote Client with I/O. I/Net version 2.4x Remote Client with I/O Clicking the link below will open a pdf document which will show how the communication should be setup if selecting Filemaster, Equalized Client, or Remote Client. I/Net version 2.4x Filemaster, Equalized Client, or Remote Client Suggestions for further info: To install the SQL, go to Installing I/NET Seven on a 64-bit operating system. For more on how to set up that Remote Client with I/O to use that SQL database, see Unable to connect Remote Client to Standalone Server. 

Issue Power to devices are Full Wave or Half Wave. Device is connected to 24VAC and begins to smoke because the voltage power input from transformer is not wired correctly. Product Line TAC INET, TAC Vista Environment Devices such as a Xenta Router or a controller which is powered by an external 24VAC transformer. Cause Devices such as a Xenta Router or control board is connected to 24VAC and begins to smoke because the power input from transformer is not correct. Resolution Download Full Wave Half Wave.pdf which illustrates the transformer to device wiring configuration. PoE is not supported for any of the Ethernet ports on I/NET devices.  

Issue What is the SubLAN and what is the C-LAN in regards to Ethernet and termination resistor information? Explanation of termination resistor, RS-485, baud rate, token passing, and polling method. Is the Host LAN above or below the Ethernet LAN? Product Line TAC INET Environment I/NET Seven Network with integration of the FOI or Fiber Optic Interface  Cause How the Fiber Optic Interface (FOI) fits into an I/NET site. Resolution When defining the network in I/NET, the chart below helps to explain which components communicate to others. This is a simple explanation on where the various I/NET components are located in an I/NET Seven Network. C-LAN & Sub-LAN and the integration of Fiber Optic or FOI. The FOI Spec sheet is available here, as well as TCON087. Click the image below to download as a PDF document.  

Issue Troubleshooting sending email alarms from a Xenta Server. Product Line TAC INET, TAC Vista Environment Xenta Server Xenta 511, 511:B, 527, 701, 711, 721 and 731 XBuilder SMTP Server Cause There are many reasons why an emailed alarm from a Xenta Server wouldn't reach the desired destination inbox. This document walks through the most common settings and networking issues and how to overcome them. Resolution Some Xenta Servers can be configured to send out alarms via email – 511, 511:B, 527, 701, 711, 721 and 731. Typically, following the instructions found in the TAC Vista Xenta Server – Web Server Technical Manual will result in successful delivery of email alarms. However, there are some factors that can hinder these email messages. This document is intended to address a few of the most common troubleshooting techniques to resolve these problems. The Basics The first step to getting Xenta alarms to email out is to properly configure the XBuilder project. Reference Chapter 5.2 Configuring the TAC Xenta Server for Email Forwarding in the TAC Vista Xenta Server – Web Server Technical Manual. Enter the address of the Simple Mail Transfer Protocol (SMTP) server as well as the authentication information (if any). If no SMTP server or login information has been provided, contact an IT professional at the customer's site to obtain this information. Alternately, for testing and demo purposes, Schneider Electric's SMTP server can be used – smtpservice.buildings.schneider-electric.com (port 25 or port 2525). If using Schneider Electric's SMTP server, set the Authentication to "TAC." Once the Xenta Server is correctly configured, set up Alarm Receivers in the XBuilder project. The steps for this can be found in Chapter 4.3 Configuring Receiver Groups in the TAC Vista Xenta Server – Web Server Technical Manual. Consider configuring the Alarm Receiver to email a distribution list as opposed to individual email addresses. Then the distribution list can be edited and maintained by the IT staff without ever having to access XBuilder projects or Xenta Servers. If everything is set up correctly, test the email capability by logging into the web interface of the Xenta Server and navigating to Utilities > Tools > Communication Tests. Enter a test email destination and hit "Test" as shown in Figure 1.  Figure 1. Test Send E-mail Message If the email arrives as expected, then the SMTP settings are all correct. A final test of the alarm receivers and alarm properties can be accomplished by forcing an alarm condition. If the email does not arrive as expected, check the following possible errors, or proceed directly to the next section of this document titled "Check SMTP Connectivity." Could not send the e-mail, error in mail configuration If this error results from sending a test email, then the settings in XBuilder need to be revisited and verified. Failed deliver e-mail, connection couldn't be established, check e-mail address If the test results in this error, proceed to the next section of this document titled "Check SMTP Server Connectivity." Check SMTP Server Connectivity In order to use an SMTP server, a connection must be established. In this example, the provided SMTP server is "smtp.ACME.com." Xenta Servers have a built in test function for determining the status of some of the defined devices. Log into the web interface and navigate to Utilities > Tools > Communication Tests.  Figure 2. Communication Tests From this screen, the connection between the Xenta Server and any of the defined gateways and servers can be verified. Select the radio button for Mail server 1 (SMTP) and hit test. Some possible results of the test are: ‘Mail server 1 (SMTP)’ is on-line If the mail server is online, but the test email still is not delivered, then the cause is most likely the authentication credentials of the Xenta Server. Check with an IT professional to verify the login account name and password that have been provided. Check that it has been correctly entered as described in the section of this document titled "Check SMTP Server Settings." If all of this is set up correctly and verified, proceed to the section of the document titled "Xenta Server Indicates No Errors." ‘Mail server 1 (SMTP)’ is off-line If the mail server is offline, then no communication exists. Make sure the SMTP server settings are correct. Refer to the section of this document titled "Check SMTP Server Settings." Also check the TCP/IP settings as described in the section of this document titled "Check TCP/IP Settings." If the SMTP server is outside the network, ensure that the default gateway is defined and test its availability with a communication test as shown in Figure 2. Lastly, connect to the network using a laptop and attempt to ping the SMTP server. If it is unavailable, contact an IT professional for assistance. C:\>ping smtp.ACME.com Pinging smtp.ACME.com [10.10.10.10] with 32 bytes of data: Request timed out. Request timed out. Request timed out. Request timed out. Ping statistics for 10.10.10.10: Packets: Sent = 4, Received = 0, Lost = 4 (100% loss), Figure 3. Failed Ping Example C:\>ping smtp.ACME.com Pinging smtp.ACME.com [10.10.10.10] with 32 bytes of data: Reply from 10.10.10.10: bytes=32 time=1ms TTL=64 Reply from 10.10.10.10: bytes=32 time=1ms TTL=64 Reply from 10.10.10.10: bytes=32 time=1ms TTL=64 Reply from 10.10.10.10: bytes=32 time=1ms TTL=64 Ping statistics for 10.10.10.10: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 1ms, Maximum = 1ms, Average = 1ms Figure 4. Successful Ping Example In Figure 4, the ping has returned four successful results. This will confirm that cables are connected properly, IP addresses are set, and any necessary gateway routers are communicating. It does not indicate ultimate success in connecting to the SMTP server. To check connectivity with the SMTP server, use a simple telnet command on port 25 (or the specified port) from a command prompt. C:\>telnet smtp.ACME.com 25 Connecting To smtp.ACME.com... Figure 5. Telnet command. If there is an error connecting, you will see this: C:\>telnet smtp.ACME.com 25 Connecting To smtp.ACME.com...Could not open connection to the host, on port 25: Connect failed Figure 6. Failed Telnet Command. If the connection succeeds, the command prompt will clear and show a new line beginning with 220. Type the word "helo" and press enter. The SMTP server should again respond but this time with a line starting with 250. Exit the telnet session by typing "quit" and pressing enter. 220 smtp.ACME.com ESMTP helo 250 smtp.ACME.com quit 221 smtp.ACME.com Connection to the host lost. C:\> Figure 7. Successful Telnet Session. If a connection can successfully be established through telnet, then the ports are open and SMTP messages should be successfully received from the Xenta Server. That does not guarantee they will be relayed by the SMTP server, so if emails are still not being delivered, continue troubleshooting with the next section titled "Xenta Server Indicates No Errors." Command not found If a telnet attempt results in the command prompt error "command not found" it is most likely because telnet is not enabled. In newer operating systems (Windows Vista/Windows 7) this feature is not enabled by default. To enable telnet: Go to Start > Control Panel > Programs and Features On the left side, select Turn Windows features on or off Scroll down to Telnet Client and check the box (see Figure 8 below)  Figure 8. Enable Telnet Client. Failed convert dns-name into ip-number If using DNS names for the SMTP server instead of IP addresses, a DNS server must be defined. A DNS server is responsible for resolving DNS names to IP addresses. Make sure the DNS server is online with a communication test as shown in Figure 2. To bypass any problems with DNS, enter the SMTP server IP address instead. This can be obtained by pinging the server as shown in Figure 3. Check SMTP Server Settings The SMTP settings can be viewed and changed either in the XBuilder project, or live via the server's web interface. If you are troubleshooting live on a site, it is probably faster and easier to use the web interface. If settings are changed live, be sure to update the XBuilder project at some point to avoid the settings being erased by a download. Navigate in the web interface to Configuration > Network > SMTP.  Figure 9. SMTP Settings The fields shown in Figure 9 for "Outgoing mail server port" are not available in XBuilder/System Program versions prior to 5.1.3. In versions 5.1.2 and below, it is not possible to alter the default SMTP port. It is hard-coded at 25. The Primary SMTP will be provided by the site's IT staff. If authentication is required, then an account name and password must be provided by the IT staff. If the SMTP server is available, but no emails are being sent out, the authentication parameters need to be checked. Any further investigation at that point will require contacting an IT professional for assistance. Refer to the section of this document titled "Xenta Server Indicates No Errors" for some troubleshooting questions to pose. Also refer to "Contacting an IT Professional" for documents to use to facilitate these conversations. If no SMTP server has been provided, then Schneider Electric's SMTP server can be used. To use Schneider Electric's SMTP server for testing or temporary purposes, enter "smtpservice.buildings.schneider-electric.com" into the outgoing mail server. Mail server ports 25 and 2525 are available. Authentication is set to "TAC." This does not require an account name or password. This method is only recommended for testing purposes. Schneider Electric makes no guarantees as to the availability of the SMTP server. To ensure the email alarms are being delivered as promised, use an SMTP server with some guarantee of up time. Even if an SMTP server has been provided, consider defining Schneider Electric's SMTP server as a secondary server. It is not always a viable solution due to some network security settings and availability, but may increase the overall success rate of your email delivery by providing some redundancy. Check TCP/IP Settings The TCP/IP settings can be viewed and changed either in the XBuilder project, or live via the server's web interface. If you are troubleshooting live on a site, it is probably faster and easier to use the web interface. If settings are changed live, be sure to update the XBuilder project at some point to avoid the settings being erased by a download. Navigate in the web interface to Configuration > Network > TCP/IP.  Figure 10. TCP/IP Settings The most important items to check on this screen are Default gateway and DNS server. If the default gateway is not properly defined, then external SMTP servers will be unavailable. If the DNS server is not properly defined, then SMTP servers defined by DNS names will be unresolved. Either enter a valid DNS server, or manually resolve the IP address by pinging the server as shown in Figure 3. If using Schneider Electric's SMTP server, DNS must be defined. Xenta Server Indicates No Errors If the test email was sent, but not received, and no errors were recorded, the focus should now shift to troubleshooting the SMTP server itself. Assistance from an IT professional will be helpful at this stage. Things to check include: Check the incoming/outgoing messages from the SMTP server. See if the messages from the Xenta Server are arriving but not being sent out. Many companies will set up an "allowed" list that will only pass emails from recognized IP addresses, and all else is filtered as spam. Make sure the Xenta Server's IP address is listed on the acceptable list. Ask what port the SMTP communication is using. Port 25 is typically used for SMTP communication, but some companies will change this for security purposes. Request that port 25 be opened for SMTP communication from the Vista Server. If this is not an option, the port can be changed in XBuilder/System Program versions 5.1.3 and later. See the section of this document titled "Changing the default SMTP Port" for instructions. Xenta Servers are hard-coded to use UTF-7 encoding. They require this encoding to support Swedish characters. UTF-8 is the most common encoding in America and Europe. Some networks may filter UTF-7 messages as spam. While this is not readily configurable, it can be manually changed by editing some files. Use an FTP program (Internet Explorer) to connect to the Xenta you are trying to change and download the \sys\langstring.cfg file. Edit the file and modify the following lines to replace all instances of 7 with an 8: ALARM_CODE_1= =?utf-7?Q? ALARM_CODE_3=charset=UNICODE-1-1-UTF-7 Upload the edited file back to the Xenta device and then cycle the power. The device will now use UTF-8 character encoding which is more commonly used in the United States. Remember that reloading the system program will erase these changes. Some companies will block all POP messages on the network. This will disable the ability to use external SMTP servers. Make sure POP messages are allowed or that the SMTP server is internal to the network. If you are trying to use an SMTP server of a different ISP than the one Vista Server is connected to, this will most likely be blocked by the SMTP server. This is known as mail relaying – something spammers can and will abuse. Changing the default SMTP Port Changing the default SMTP port is not available in XBuilder/System Program versions prior to 5.1.3. In versions 5.1.2 and before, the only options are to request for the IT department to allow use of port 25, or upgrade to version 5.1.3 or later. If you are using XBuilder/System Program version 5.1.3 or later, adjusting the default SMTP Port can be done through the web interface as shown in Figure 9. It can also be adjusted in XBuilder as shown in Figure 6.  Figure 11. Changing the SMTP Port in XBuilder Contacting an IT Professional If you need help contacting the customer's IT department to gather and share the correct data, use the document attached in Appendix A: IT Request for Information. A completed example is shown in Appendix B: Sample IT Request for Information. Disclaimer The information contained in this document is subject to change without notice. It is also subject to change with versions of TAC Xenta Servers. If further assistance is required, please Call or email Schneider Electric Product Support Appendix A: IT Request for Information The TAC building automation system installed on your site has the capability to email facilities personnel in certain situations. Typically, this is used to alert the proper channels of equipment failure or security breaches detected by the automation system. TAC Xenta Servers use standard Simple Mail Transfer Protocol (SMTP) for these messages. An SMTP server must be provided in order for these messages to be delivered. The following document was created to facilitate the sharing/gathering of necessary information between IT and the installation contractor. Information for the Installation Contractor from IT SMTP messages must be sent with the following details: SMTP server address (DNS or IP):   Authentication required (choose one): Yes No Account name (if applicable):   Password (if applicable):   To distribution list (if any):   Required UDP Port:   Information for IT from the Installation Contractor SMTP messages will be sent with the following details: To distribution list (or email addresses):   Unit e-mail address:   From IP address:   Desired UDP port:   Appendix B: Sample IT Request for Information The TAC building automation system installed on your site has the capability to email facilities personnel in certain situations. Typically, this is used to alert the proper channels of equipment failure or security breaches detected by the automation system. TAC Xenta Servers use standard Simple Mail Transfer Protocol (SMTP) for these messages. An SMTP server must be provided in order for these messages to be delivered. The following document was created to facilitate the sharing/gathering of necessary information between IT and the installation contractor. Information for the Installation Contractor from IT SMTP messages must be sent with the following details: SMTP server address (DNS or IP): smtp.ACME.com Authentication required (choose one): Yes No Account name (if applicable): emailuser Password (if applicable): password123 To distribution list (if any): facilities_staff@thebuilding.com Required UDP Port: 25 Information for IT from the Installation Contractor SMTP messages will be sent with the following details: To distribution list (or email addresses): facilities_staff@thebuilding.com Unit e-mail address: xenta@server.com From IP address: 10.10.10.20 Desired UDP port: 25

Issue Seven Reports Error "CRPaige library CRPaig80.DLL cannot be found". Product Line TAC INET Environment I/NET site with Windows OS Cause Missing CRPaig80.DLL error message Resolution CRPaig80.DLL can be found on the original I/NET Seven installation CD (cd-drive:\program files\inet seven). Copy CRPaig80.DLL to the root I/NET Seven folder (c:\program files\inet seven). Click Here to download a zipped copy of the CRPaig80.DLL

Issue Can the Xenta 913 be used as a NPR in I/NET? Will the Xenta 913 transfer (via Connection Objects) from one I/NET link to another? Product Line TAC INET Environment I/NET Seven Xenta 913 Cause Although the Xenta 913 appears in the I/NET network configuration and parameters appears the same as a NPR not all functions are possible.  Refer to the resolution to below for supported communications: Resolution Even though the 913 has some basic NPR functionality to I/NET it does not function 100% as a NPR like the 527 or 731 does. The 913 will not pass any AMT information to a host, nor will it pass global indirect points from link to link. It is recommended to only use the 527 or 731 as an NPR to an I/NET system.   Click the picture above to open this image in PDF format. It should also be noted that provided the Xenta 913 is connected on the TCPIP network it is possible to create connection objects across I/NET links.  The Xenta must be part of the I/NET network, that is add the reference host to the Xenta 913 configuration then all links will be available to the device.

Issue How do the 7793 and 7798 handle retries?  Improving I/NET sublan communications Excessive MCU Lost messages in AMT Command Error messages in AMT Product Line TAC INET Environment I/NET sublan 7793, 7798 Cause If there are issues on the physical layer of the network, this will effect the reliability of I/NET communications. However, these risks can be lessened with some best practices. Resolution Best Practices and Troubleshooting measures to improve sublan communications: Ground the 24V line coming into MRs and ASCs Connect ground to the earth ground terminal of DPUs and SCUs. Bond the shield of the LAN cable all the way through the network, not landing it on any controller anywhere and then tie it to earth ground in one location. (see diagram)   SubLAN Communication Explained: The first packet to any sublan device goes out on the primary channel, terminals 1 and 2 of the sublan connector on the 93/98. If the device doesn't respond in time, a second packet is sent out on the alternate channel, terminals 4 and 5. If there is still no reply, a third packet goes out on the primary Finally, if there is still no reply, that device is marked as lost which generates an "MCU Lost" message. Optional Configuration for only using Terminals 1 and 2:  If you are using only Terminals 1 and 2 you could be missing 33% of it's retry capacity. If you follow wiring guides and best practices the device will answer on the first packet every time, however if you have not followed the guide all it takes is a little noise to make the retries necessary. If you are unable to use a loop configuration, or want to avoid the extra potential for noise and EMI, in stall a jumper on the sublan connector from terminal 1 to 4 and from terminal 2 to 5 The allows you to get the extra retry, without the extra cable This will also function if you have some controllers on channel A and some on Channel B The SLI doesn’t have to be at the end of line on sublan communication  

Issue Sunrise/Sunset does function correctly in I/NET Seven rev 2.16 Sunrise/Sunset workaround in I/NET Seven 2.16 Product Line TAC INET Environment I/NET Seven rev 2.16 Cause Currently there are some issues with Sunrise and Sunset working correctly in I/NET Seven rev 2.16. The follow steps are given as a work around to solve these issues. Resolution There are two different ways to make this work correctly: Add some starts between the Sunrise and Sunset. It is important that these starts do not have any days of the week defined.   Use a Cycle between the Sunrise and Sunset. It is important that this Cycle does not have any days of the week defined.  

Issue After upgrade of Xbuilder or opening a project built on another computer generating the project causes a "File not found:" error message.   Product Line Satchwell MicroNet, TAC INET, TAC Vista Environment XBuilder Cause Find the alarm or event page that is causing this problem and view the reference field to identify the cause of the problem.   XBuilder was upgraded and the xmle files from the previous version are no longer present. XBuilder installation directory was on a different drive on the computer the project was last used on. Resolution In Xbuilder, right click on all the Alarm and Event pages, select Change reference, and browse in the new path to the referenced file.  

Issue 3 State Event Sequence to control certain Access Control Doors Product Line TAC INET Environment I/NET site Cause Three State control requirement Resolution   When using the Door Points ("08" & "09") with event sequences, the following actions will occur: A “Start” command is equal to the “Secure Mode” of the door A “Stop” command is equal to the “Unlock Mode” of the door A “Lock Door” command is equal to the “Lock Mode” of the door

Issue How do I properly acknowledge and purge a "Force Door" alarm in AMT. Product Line TAC INET Environment I/NET Access Control Cause The return to normal condition (Door Normal) "Message Type" must have the same "Message Type" as the alarm cause (Forced Door).  This is the same condition as for DOTL (Door Open Too Long) alarms.  For I/NET to clear both these alarms. the Message Types must match within the Door editor. Resolution You have to properly configure the Door editor before you can properly remove this from AMT. In order to acknowledge and purge a "Force Door" alarm you must have the "Force Door" entry set to "Alarm." The "Door Normal" should also be set to "Alarm."  

Issue Can I use the Xenta 527 on an old I/NET 2000 system? Product Line TAC INET Environment I/NET 2000 Cause Adding a Xenta 527 to an I/NET 2000 network. Resolution Yes you can, provided you set the Xenta 527 up to be compatible with I/NET 2000.   With the Xenta programming cable (P/N 3-781-0128-0) inserted in port "B" of the Xenta 527, go into Windows Hyper-Terminal and make the following changes for the Xenta 527 to operate in an Inet 2000 program.     Please be aware that I/NET 2000 is no longer a supported product and this mode should be used at your own risk.  

Issue USB Prox enrollment reader for I/NET Seven Environment I/NET Seven Cause I/NET supports the use on an Enrollment reader via the Hosts PC Serial port, most PC's no longer have serial ports.  One solution is to use a USB supported reader which can be sourced by the supplier listed in the resolution  Resolution The USB enrollment reader is made by RF Ideas. It is very easy to program for use in the I/NET Seven System. After you program certain steps it becomes a "Plug and Play" device at the job site. To set up this USB reader please consult this whitepaper.

Issue The "Transactions Individual" report in Seven Reports does not sort the transactions by Date and Time. Product Line TAC INET Environment I/NET Seven Seven Reports Cause The "Transactions Individual" report is not sorted by Date and Time Resolution The "Transactions Individual" report is not sorted by Date and Time for a reason. I was determined by TAC, that the customer needs to design the method by which they want this report to be presented. This White Paper will define how to go about setting the Sort process by the Date and Time Option. Start Seven Reports and open the “Transactions Individuals” report Once the report is fully developed on the screen. Choose the “Design” tab In any of the blank white area do a “Right Mouse” Click In the “Popup” window selects the “Report” Option In the next “Popup” window selects the “Sort Records…” Option In the next “Popup” window you need scroll the left window unit you find the “RptEvents.DateTime” Option. Then Select the “Add” button the place the “RptEvent.DateTime” Option in the right window. After you do Step 6 this is what you will see in the right window You need to highlight the “RptEvent.DateTime” function. Then select either “Ascending” or “Descending” sort order.  In the “Ascending Mode” the “Oldest Date” is on the top of the list and the most “Recent Date” is at the bottom of the list.  In the “Descending Mode” the most “Recent Date” is on the top of the list and the “Oldest Date” is at the bottom of the list. I selected the “Descending” Mode as the way I wanted to sort the Date and Times. You also need to select the “OK” button to finish the setup process. You need to close out of this report. Select “Yes” button to save the changes you made in the “Canned” report. Remember to rename you newly created report to something other than the Original “Canned” report name.

Issue   Error message: "Failed to run DcuXml.exe" when importing I/NET .sav files into XBuilder Product Line TAC INET, TAC Vista Environment XBuilder 1.6.0 Cause When XBuilder imports I/NET save files, it does a simple batch of all of the save files for the import process. It creates a path for the import into XBuilder. A typical path might look like this: C:\TAC XBuilder Projects\MyProjectName\Files\INET\dcu0102,dcu0103,dcu0104 This example shows the import of 3 I/NET save files with a character length of 72 for the batch process. This process is limited to 2048 characters. Importing 15-20 save files will cause a crash.   Resolution To squeeze a few more save files into XBuilder, shrink that path as much as possible. For example: Rename the default "TAC XBuilder Projects" folder to something shorter. Rename the project to something shorter. Move .sav files to another location, even temporarily to the C:\ drive root to eliminate extra path data. Example:  C:\XBPrj\MyPrj\Files\INET\dcu0102.sav.  This path shrinks the directory at the front end to allow for more save files on the backend.

Issue Importing I/NET 2000 Graphics into I/NET Seven Product Line TAC INET Environment I/NET Seven Cause Have you upgraded from I/NET 2000 to I/NET Seven and the graphics at the site has either stopped working, don’t come up with the correct back ground or bitmaps and the size is all wrong? Resolution There are a few things that you need to verify after the upgrade. Verify that the path for both symbols and bitmaps that was used in I/Net 2000 is the same for I/NET Seven. If this is not done then the pages when opened in I/Net Seven would come up with a blank background or without a bitmap and or symbols. To find the original path (if unknown): Open the Graphics Editor Select File> Open to edit the graphics page  Select View > Page Properties In the Backdrop area (shown below) is the original path of the background bitmap.   If you only have a few graphics then you can edit and modify this for each of the graphic pages  Alternatively make sure all the bitmaps used are still located in the path defined here. All folders with Bitmaps and Symbols are all the same, even if you have to create a new I/Net 2000 folder on the new PC. If you were using 800 X 600 on the original pages, then you’d have to change the resolution on the new PC to the same. If this is not done, then the pages will show smaller and the points would be distorted.

Issue There is a possible corruption of the SQL Database and the DCUxxxx.sav files when upgrading I/NET Seven from Rev 1.xx to I/NET Seven rev 2.13 and above Product Line TAC INET Environment I/NET site 1.xx Cause Corruption of the SQL Database and the DCUxxxx.sav files Resolution If you do a fresh install of Inet Seven 2.13 and above and restore an Inet Seven rev 1.xx SQL DB. There is a possibility of having the SQL Database and the DCUxxxx.sav files getting corrupt if you do not properly save the NETCON file. The example below is an Inet Seven rev 1.06 SQL database that was restored to a fresh install of Inet Seven rev 2.14. This is what the NETCON file looks like; if you do a station restore at this point you will corrupt the system. Look at step 2 for the correct way to handle this. Taking the above example and changing it to look like the one below will prevent the corruption from occurring in the Inet Database and DCUxxxx.sav files. Please NOTE this issue will be corrected in Inet Seven rev 2.16 and above. Note: Remember while you are in the NETCON editor; penetrate each station in the MCU summary page. Edit and Save each DPU entry so that the “Type” is correct DPU type (7910, or 7920). Also, save the revision of something close, such as 3.03 or 3.04 for the 7910 & 7920. Make sure that there are no “*”, “Blank spaces” or “0.00” displayed when you are done. Also make sure you “SAVE” NETCON all the way down to the door level.

Issue I/NET Message Masking Product Line TAC INET Environment I/NET site pre 2.13 Cause Message Masking with Rev. 2.13 and prior Resolution In Rev 2.13 a new configuration option was introduced, Server/Remote Client. The Server should be set to mask for all Links’ messages and AMT similarly set. If this configuration is chosen, it will be necessary to use filters in AMT if it is desired to display only selected link messages on a host. In Rev 2.12 and earlier versions, the message masking for the links could be set so a host would receive messages from only selected links. AMT on those hosts with masking similarly set would therefore display messages from only those links. An example of using masks to route messages for File master//Equalized Clients is shown on link below. There are three links and three hosts. It is desired that Host 1 see messages and interact with controllers only on Link 1. Host 2 will handle Link 2 and Host 3 will handle Link 3. Link 1 controllers can use Group 1 bits 1 and 8, Link 2 controllers use Group 2 bits 1 and 8, and Link controllers use Group 3 bits 1 and 8. Host 1 will then set Group 1 bits 1 and 8 for link 1. Host 2 will set Group 2 bits 1 and 8. Host 3 will set Group 3 bits 1 and 8 (these masks are arbitrary and were chosen for illustration only). AMT masking is set the same for these hosts. File master/Equalized Client Server/Remote Client In the Server/Remote Client configuration all messages are routed to the Server (Host 1). AMT can then be configured on a host to show messages from only selected links using the filter option in AMT. To display messages from only Link 1 on the Server (Host 1) set up a filter to select messages from just Link 1 as shown in the linked document below: The Start address has to be an address before the start of the link desired in order to show all messages for the link. In this example it is assumed there are no devices on the link 00. If there were, set the Start to the highest possible address that is not used, e.g. 00633109. Message Masking