Issue What are the specifications for using a synchronous (Hayes) external modem in relation to I/NET Dial Applications? Product Line TAC INET Environment Synchronous (Hayes) external modem I/NET Dial Applications Cause Dial up I/NET applications Resolution See TCON101, TCON213, TCON226 and TCON298 for more details PC, modem, and phone line must be connected and “ON”. To program a modem, the modem must be direct connected to the PC Connect the modem to an analog phone line only. Remember the host needs a 78041 or a 78051 tap (not Embedded 4x) Warning! Using a non-analog line will damage the modem!   Make sure the correct modem driver is installed. Add the modem hardware in Windows Control Panel In the “Phone And Modem Options” editor, go to the “Modems” tab Remove any profiles of modems that are not currently connected to the INET comm port. If you are running Windows 2000, the “Microsoft H.323 TAPI Service Provider” should be the telephony provider highlighted under the “Advanced” tab, in the Phone And Modem Options Editor of Windows 2K Control Panel. From the “Modems” tab, go to Properties / Diagnostics / and Query Modem. Go to Modems / Properties / General, and set the Maximum Port Speed at 9600. Close Windows Control Panel   View the modem’s Active and Stored settings: Type “ATE1” to place echo to “On” mode “AT&V” followed by the “Enter” key displays the settings the modem is using and the NOVRAM settings in profile “&Y0” and  &Y1 If the settings need to be changed then continue Recommend “AT&F” to reset the modem to factory defaults. The Host and Site modems use the same settings. Both modems should be as follows: Active Profile: B1 B16 B30 B41 B52 B60 B70 B75 B80 E1 L2 M1 N0 P Q0 V0 W0 X4 Y0 &A0 &B1 &C1 &D3 &G0 &K3 &L0 &Q1 &R0 &S1 &T4 &U0 &X0 &Y0               S00:001 S02:043 S03:013 S04:010 S05:008 S06:002 S07:060 S08:002 S09:006 S10:014 S11:095 S12:050 S25:005 S26:001 S36:001 S37:009 S38:020 S46:002 S48:007   Suggest you store the settings in both profiles of the modem’s NOVRAM. “&W0” stores to “&Y0” “&W1” stores to “&Y1”   TAPs : EPROM(s) and BIN files need to be synchronous and INET rev compatible   After following the preceding steps for the remote site’s modem: Connect the modem to the Tap (or emulated Tap) and Analog Phone Line Power-up the modem Press the controller’s reset button or cycle the Tap’s power Do NOT cycle the modem’s power The “RD” and “SD” should flash after several seconds have past After about 30 seconds the  “MR”, “AA”, and “TR” lights should be “On”   Using I/NET, Dial the site. Make sure the host can: Dial out (you can here the dial tone) Handshake with the remote Modem Maintain its connection to the remote modem (Neither modem inadvertently terminates call) See the Controller(s) on the LAN Actually connect to the controller(s) View points in the summary screens Warning! Using a non-analog line will damage the modem! For Asynchronous ADAA, click here

Issue What are 7806 Site Taps? Environment I/NET site Cause What are 7806 Site Taps? Resolution These series of Taps connect one or more controller LANs to a workstation through a companion 7804/78041, or to a host LAN through a 7805/78051 Tap using a Direct Distance Dial telephone network. (Refer to TCON 101, Model 7806 Site (LAN) Taps).

Issue What are 7805 Link Taps? Environment I/NET site Cause What are 7805 Link Taps? Resolution This series of Taps connect a workstation to controller LAN Taps (Site Taps) through a Direct Distance Dial (DDD) telephone network. They communicate to a companion model in the 7806 Taps, which forms the connection from a workstation to the remote controller LAN. (Refer to TCON 101, Model 7805 Link Taps.)

Issue What are 7804 Host Taps? Environment I/NET site Cause What are 7804 Host Taps? Resolution This series of Taps connect a workstation to controller LAN Taps (Site Taps) through a Direct Distance Dial (DDD) telephone network. They communicate to a companion model in the 7806 Taps, which forms the connection from a workstation to the remote controller LAN. (Refer to TCON 101 Model 7804 Host Taps.)

Issue What amount of memory is used for DPU Resident Individuals in the DPU\SCU controller? Product Line TAC I/NET Environment I/NET Seven - Access control DPU7910A, DPU7920, DPU7920 w/DPU48K, and SCU1284 Cause Need to understand the memory allocation and implications of using DPU Resident settings with both the DPU or SCU hardware devices. Resolution To set the Individual as DPU Resident the DPU Res. checkbox needs to be checked in the Individuals editor as shown below (red box) shown below.     In the table below from TCON300 05/17 Chapter 9-14 shows the memory allocation for a 7910A DPU or DPU7920   If you have a selection of between 6000 to 12000 Resident User Individuals (i.e. set as DPU Resident) in the system you can ONLY have between 3262 to 2887 Cached users respectively stored within a properly communicating system.  If the DPU is offline to the Sub LAN Interface (SLI) these cached users will be reduced as the requirement for the DPU storage capacity will need to store 'offline' messages as shown under the "Messages" column.     In the table below from TCON300 05/17 Chapter 9-15  shows the memory allocation for a SCU1284 DPU or DPU7920 w/DPU48K   If you have a selection of between 6000 to 12000 Resident Users Individuals (i.e. set as DPU Resident) in the system you can have the full quota of 48,000 Cache Users respectively stored within a properly communicating system.  Unlike the DPU7910 or 7920 if the DPU is offline to the Sub LAN Interface (SLI) there is no change to these cached users and there is more 'offline' message storage as shown under the "Messages" column. For further information on DPU Caching and memory management read from Chapter 9-11 in TCON300-05/17

Issue What LAN is at the top of the I/NET structure? Product Line TAC INET Environment I/NET Site Cause What LAN is at the top of the I/NET structure? Resolution The Ethernet LAN is at the top of the I/NET structure and can be used to connect multiple host workstations, via TCP/IP (TCON 209, 1-3). Refer to Explain and define I/NET Ethernet, C-LAN, and Sub-LAN communication for further information.

Issue What HHC cable do I need to connect to a Unitary Controller (UC) SubLAN port? Environment I/NET Hand Held Console (HHC) Cause Can not locate documentation to indicate which cable is required. Resolution The part number is 606014-0011. It is a six foot (or 1.8 m) coiled, black modular cable. Refer to TCON 073 for more details. HHC or Hand Held Controller is also called the HC7410 Note for iPortal users:  The above Part Number in iPortal is displayed in the Description / Part Name .  iPortal uses the following part number for this product: 01-0100-492-01

Issue What HHC (Hand Held Console) cable do I need to connect to a DCU, UCI, or PCU? Product Line TAC INET Environment I/NET HC7410 HHC (Handheld Console) Cause Can not locate documentation to indicate which cable is required. Resolution Original HHC: The part number is 602135-0003. It is a six foot (or 1.8 m) coiled, silver modular cable. Refer to the appropriate controller TCON for more details.   HHC (Hand Held Console) is also called the HC7410. Refer to TCON 073 for more details. Updated USB HHC: This is the replacement for the HHC. TCON318 has more information. The HHC-USB-IF cable allows you to connect the hand-held console (HHC) port of a TAC I/NET device to the USB port of a PC. You can then use the HHC emulator running on the PC to configure the I/NET device’s controller LAN address, tap emulation, baud rate settings, monitor and control points, and perform the other typical local maintenance functions supported by the earlier HC7410 console product. The HHC-USB-IF cable can be used with the model 7716, 7718, 7756, 7780, 7790A, 7700, 7740, and 7750 Distributed Control Units (DCUs), and the model 7760 UCI

Issue Some security software will report that there are vulnerabilities for SSL of Xenta Server. Some vulnerabilities look like: SSL Server allow anonymous authentication vulnerability SSL Server allow Cleartext communication vulnerability  Weak encryption model Environment Vista I/NET Cause This is how Xenta Server designed to work. Resolution There is a security enhancement for Xenta Server in Xenta 5.1.9. Update the firmware to Xenta 5.1.9 will fix these vulnerabilities. You can download Xenta 5.1.9 from Buildings Download Center.

Issue On a 7718 controller, why do none of the discrete outputs provide 24vdc when energized? Product Line TAC INET Environment I/NET site Cause Using the 7718 controller, why do none of the discrete outputs provide 24vdc when energized Resolution Verify that fuse F9 is not open. (TCON106)

Issue Using an End-User Dongle to license XBuilder or Menta when Vista Server is not installed Environment Vista 5.1.7 and older XBuilder Windows XP Menta Cause License may not be able to install due to previous license file conflicts. Resolution Install or re-install the TAC License Program found on Exchange Select Start>All Programs>Schneider Electric>TAC Tools>LMTools (or Start>All Programs>TAC>TAC Tools>LMTools Click on the Start/Stop/Reread Tab Click on "Start Server" Click on "ReRead License File" Close LMTools and Start XBuilder If the option is available, it is preferred to host the license to a MAC address instead of a dongle ID.

Issue Using I/NET2000, Can a site change a filemaster setting? Environment I/NET2000 Cause Using I/NET2000, can a site change a filemaster setting? Resolution Not, without difficulty. Setting a pc as a filemaster makes irreversible changes in software. We, in tech support have not found a way to reverse them, short of uninstalling Inet, deleting the root directory, and removing registry entries. Then reload Inet software. See pages 1-12 through 1-14 of TCON 237, Technical Reference Guide for a discussion of filemaster functioning.

Issue Using I/NET Audible Alarms with Remote Clients No audible alarms with Remote Client configuration Product Line TAC INET Environment I/NET Seven Software 2.42 and newer I/NET Remote Client or Remote Client with I/O Server Cause The functionality was changed with the following TrackRecord 5940 fix in I/NET 2.42: Alarms in a Remote Client do not get an audible alarm Only clients configured as "Remote Client w/IO" are capable of routing alarms/events to the server. The masking on clients configured as "Remote Client" will not cause alarms/events to be routed to the server. On these clients, you can use the masking to get audible alarms with no danger of getting duplicate alarms.   Resolution To receive and activate audible alarms on a Remote Client, set the Distribution Group and Masking of the alarm point within AMT.   Note: This setting is only the case for I/NET 2.42 and above.  If this is setting is made in earlier versions of I/NET, it will cause alarms / events / trends to be routed to the server and possibly can cause duplicate events / trends to be sent to the server.  The following information is noted in TCON300: "Limitations to TAC I/NET Seven on Remote Clients   Remote clients configured as “Remote client w/IO” have access to TAC I/NET Seven’s full functionality. Remote clients configured as "Remote client" do not have access to the following areas of TAC I/NET Seven features:   Network functions                 Automatic DPU restore                 Archiving                 Dial after edit   Additionally, for any client configured as a “Remote client”, the mask settings in the AMT Configuration editor and Host Configuration editor are ignored. Only the mask settings on the server or on the client configured as “Remote client w/IO” will control what messages are received in AMT and what data is stored for trends. You can, however, use unique filter settings at each remote client to control what AMT messages are displayed." "Limitations to TAC I/NET Seven on Remote Clients" Remote clients configured as “Remote client w/IO” have access to TAC I/NET Seven’s full functionality. Remote clients configured as "Remote client" do not have access to the following areas of TAC I/NET Seven features: Network function Automatic DPU restore Archiving Dial after edit Additionally, for any client configured as a “Remote client”, the mask settings in the AMT Configuration editor and Host Configuration editor are ignored. Only the mask settings on the server or on the client configured as “Remote client w/IO” will control what messages are received in AMT and what data is stored for trends. You can, however, use unique filter settings at each remote client to control what AMT messages are displayed."  

Issue Understanding how to check the firmware version of the USB-485-I/NET adapter and upgrade it to the latest version. Product Line TAC I/NET, EcoStruxure Building Operation Environment Building Operation I/NET USB-485 I/F Building Operation Automation Server Building Operation Automation Server Premium Cause If the firmware version of an I/Net USB interface is at an older firmware version then it may need to be updated. Please check the Exchange website for the latest firmware version Note: If the USB adapter is not at least at firmware version 1.02 then the system may experience communication issues in which I/Net values are not updating in EcoStruxure Building Operation or Automation Servers may be dropping offline.  In some cases, the Enterprise Server can lock up due to the older firmware in the I/Net USB adapter. Resolution To download the latest "USB-485-Inet Firmware Update Utility" click here. To Verify the Current Adapter Firmware Version in EBO 2.0 and Higher Right click the I/Net Interface is the System Tree of WorkStation and choose Properties. Down towards the bottom of the Basic tab you will find the Firmware Version.   To Verify the Current Adapter Firmware Version in SBO 1.9 and Lower Connect the USB Interface to a laptop with the USB cable that is attached to the AS-P. Do not hold the pushbutton in on the USB Interface. Run the firmware executable. Press Enter. It will display: "Found USB Device on COMX" and will display the hardware version, software version, and the firmware date. It will then say, "Press Enter to begin the upgrade.  Note: Pressing Enter here will only repeat the hardware and firmware versions. The process to Upgrade the Adapter Firmware Note: If the I/Net USB adapter is already plugged into the laptop from checking the firmware version as described above, then to start the upgrade process USB cable will need to be unplugged from the laptop. Then follow the steps below. While holding down the pushbutton of the I/Net USB adapter, unplug the adapter's USB cable from the AS/AS-P and plug it into your laptop. After it is plugged into the laptop, release the pushbutton.  You will see that the LEDs on the interface are not flashing. On the laptop, run the firmware executable. After the command window opens, press Enter to start the update process. It should display "Unprogrammed device located" followed by "Device programmed successfully". Next, it will say "Found USB Device on COMX" and show the hardware version, firmware version, and the firmware date. Press Esc to close the command window.  The firmware upgrade is now complete. Note: Some laptops will not recognize the USB Interface and will not assign it a Com port.  If this is the case you will still be able to upgrade the firmware.  But instead of giving the Com port the and the firmware version after the upgrade is complete, it will show "Unable to find USB Device".   Also, you would not be able to check the firmware version prior to upgrading as mentioned above.  To correct this you must install the 7801 Tap.inf driver.  Click here to download the 7801 Tap.inf drivers. To install the 7801 Tap.inf drivers: Connect the USB Interface to a laptop with the USB cable that is attached to the AS-P. Go into Device Manager and find the I/Net USB Interface.  It will have an error because of no driver. Right-click on it and choose to Update Driver Software... Select Browse my computer for driver software and browse to the 7801 Tap.inf file. Then follow the instructions above.

Issue Unable to link External Point to a global point Environment I/NET Cause Global points can only be linked to indirect points Resolution Create an indirect point on the same controller as the external point you wish to reference.  Configure that point as an Indirect point and enter the I/NET address of the Global point.  Add a calculation to the external point that makes it equal to the Indirect point. Ensure that your Global point has the correct global setting.  Refer to TCON 300, I/NET Seven Technical Reference Guide, page 6-10 for more information.

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 Is I/NET capable of translating “large” key/card numbers (i.e., numbers greater than 24,000) directly to a lower number? Environment I/NET site with access control Cause I/NET capable of translating “large” key/card numbers (i.e., numbers greater than 24,000) directly to a lower number? Resolution The I/NET system is capable of translating “large” key/card numbers (i.e., numbers greater than 24,000) directly to a lower number, without the use of the Key/Card Translation table. However, this functionality requires that the SLI and DPU binary loads are I/NET 2000 revision 2.x or I/NET Seven revision 1.x (or later) compatible, and that DIP switch 7 at the DPU is ON. For DPUs with earlier firmware versions, the use of the Key/Card Translation table is still required when key/card numbers are greater than 24,000. Refer to TCON300 for more details.

Issue Transferring an I/NET Seven system from one PC to another Product Line TAC I/NET  Environment I/NET Seven Site Cause Customer needs to transfer I/NET between two computers Resolution Perform the following steps: Install I/NET Seven on the new PC. Using DBCreate.exe, create a backup of the I/NET database. Copy the backup to the new PC and restore it using DBCreate. If the database needs to be upgraded it will prompt you.  Proceed with the upgrade.  Copy the save files, graphic pages, archives, any custom reports, custom symbols, and custom BIN files (ICI bin files) to the new PC using the same directory path as the previous PC to guarantee that graphic links will still work. The following are default paths for these files assuming it was not an upgrade from I/NET 2000. If it was an upgrade from I/NET 2000 please consult TCON298 the Getting Started guide which includes I/NET 2000 paths. Default location for Archives: C:\Program Files\INET Seven\Arch\ Default location for BIN Files: C:\Program Files\INET Seven\Data\ Default location for Reports: C:\Program Files\INET Seven\Reports\ Default location for Save Files: C:\Program Files\INET Seven\Sav\ Default location for Bin Files: C:\Program Files\INET Seven\Data\ Default location for Graphics: C:\Program Files\INET Seven\ Take a screen capture or write down the active configuration profile in I/NET configuration and manually fill this information into I/NET configuration on the new PC and make it the active configuration profile. Transfer the communication medium to the new PC (serial cable or Ethernet cable) and if communicating via NPR’s set the IP address of the new PC to match that of the old PC and remove the old PC from the network to avoid IP address conflict. Start up I/NET, login, and edit the Host Computer->Network Configuration to verify that the PC is communicating with the controllers.

Issue Why are transactions/messages showing up in double, triple, etc in I/NET Product Line TAC INET Environment I/Net revisions 2.xx Cause The table linking for each of the reports and establishing a link between RptIndividualHistorz.TenantNdx and the RptCards.TenantNDX Resolution In versions of I/NET when using the I/NET client as a remote client, you must uncheck all the Host Masks on each remote client, otherwise, the Messages and transactions show up multiple times. If not using a Remote Client, the following solution may help you. Refer to the TCON301.

Issue Does I/NET Seven provide Time and Attendance functionality Environment I/NET Seven 2.xx and above Third Party Time and Attendance solution Cause Possible alternatives to Customers wanting to use or interface Time and Attendance solutions with I/NET. Resolution I/NET does not have a separate Time and Attendance ‘module’. There are three possible options which may provide a suitable alternative to your requirements: SevenReports: I/NET’s SevenReports provides a standard report called “Transactions Attendance”.  The report compares the time stamp for an individual and calculates the time within zones defined in I/NET.  I/NET doors must be configured with entry and exit readers and have defined Zones (i.e. Anti-pass back must be enabled).  It could be as simple as a single zone for the entire site or multiple zones if this is required. This report shows EACH transaction received, therefore if you badge multiple times on the entry or exit readers the system calculates the time difference from the last badge. This must be taken into account by any system when calculating the total time within the “Zone”. Automatic Report Generation (Export of SevenReports to CSV): Using the same report as mentioned above, I/NET is capable of automatically exporting this document to a CSV file. This can be scheduled to run as required for any third party system to use. Third Party Access to InetDb SQL database This option allows third party SQL connections to query the I/NET SQL Database (Read only access), utilizing a predefined login or the INetThirdParty login.  The third party software or application would query data from the InetDb SQL database. For further information and configuration of these features are all available in the same document, TCON301 – Database Connectivity and Reporting.