Building Automation Knowledge Base

Issue What code do I use on the HHC to set the Tap emulation? Environment Handheld Console Cause Setup Tap emulation. Resolution To set up Tap emulation: Press code 90 Press [ENTER] Press the [INC] or [DEC] to toggle through 78010, 78035 or 78061 Tap emulation. To set the baud rate for Tap emulation: Press code 91 Press [ENTER] Press the [INC] or [DEC] to toggle through the available PC port baud rates. The baud rate is typically 9600 if connected to a host PC. Refer to the appropriate controller TCON for more information.

Issue What considerations should be given to I/NET SEVEN and ID Works during the setup procedures? Environment I/NET Seven DataCard ID Works Cause Some best practices when considering implementing DataCard ID Works during setup with I/NET Seven.  Resolution Consider the following suggestions as you configure your ID Works project for use with I/NET Seven: Keep Image Path Short When you create a project that will be accessed from PC’s across a network, keep the image paths as short as possible. Long images paths accessed across the network can slow the performance of your Video Badging system.   Define a "UNC" Image Path In a network, the Universal Naming Convention (UNC) is a way to identify a shared file without having to specify (or know) the storage device on which it resides. This type of path will allow ID Works users at different machines across the network to successfully retrieve image files. Please refer to the DbCreate chapter in the I/NET Seven “Getting Started” guide for more information about UNC paths.   Store a Project's Images at a Single Location An ID Works project does not allow you to store images in multiple locations. Therefore, if you assign images to individuals from within I/NET Seven, ensure that each image is stored at the single location used by the ID Works project.   Rules for Multiple Image Location If the site requires multiple Image locations. It requires an ID Works Project defined for each image location. Note these Projects can be of the same design, however, the file name of the project must be different.

Issue What considerations should be given to I/NET Seven Promotion? Environment I/NET Seven Cause When Promoting or Demoting a File Master or Workstation you have to wait for the process to finish before closing out of the I/NET system. Below is a description of the area of the process that might cause you this problem. Resolution Between the next to last "I/NET Seven Balloon" is displayed and the final "Balloon" is displayed is a long pause without any appearance of any "Balloons." Do not stop or close out of the I/NET Seven system; wait at least for 5 minutes to make sure the last "Balloon" is displayed. The File Master Icon, on the bottom task bar, should turn a cyan blue and then back to gray. This is a good signal that the SQL is finished updating.

Issue Specification for using a USRobotics modem with dial application Environment I/NET site Cause What are the specification for using a USRobotics modem with dial application? Resolution Warning! Using a non-analog line will damage the modem! INET Dial Applications using US Robotics (External Modems) See TCON 101, TCON 213 , TCON 226 and TCON 298 for more details If the modem has dip switches, set them as follows: 1,5,6, and 7 up 2,3,4, and 8 down If the modem does not have dip switches, don’t worry about it! PC, modem, and phone line must be connected and "ON" Connect the modem to an analog phone line only. Warning! Using a non-analog line will damage the modem! (Contact USR) http://www.usr.com/products/analog/p-56k-menu.asp Make sure the correct modem driver is installed. Don’t use “Standard Modem”. Set the hyper-terminal session “Baud” as specified in the following instructions (See the sections titled: “Remote Site Settings” and “Host Settings”) View the modem’s Active and Stored settings: "ATI4" followed by the Enter key displays the settings the modem is using "ATI5" followed by the Enter key displays the settings stored in NOVRAM If the settings need to be changed then continue Recommend "AT&F" to reset the modem to factory defaults. See the sections titled: “Remote Site Settings” and “Host Settings” Suggest you store the settings in both profiles of the modem’s NOVRAM. "&W0" stores to "&Y0" "&W1" stores to "&Y1" Help Commands for US Robotics are: AT&$ ATS$ AT$ 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 "AA," TR" and "CS" lights should be "On" Using INET, Dial the site. Make sure the host can: Dial out (you can hear the dial tone) Handshake with the remote Modem Maintain its connection to the remote modem (Neither modem automatically terminates call) See the Controller(s) on the LAN • Actually connect to the controller(s) View points in the summary screens   Remote Site Settings: DIAL=TONE B0 E0 F1 M1 Q0 V1 X0 Y0 BAUD=9600 PARITY=N WORDLEN=8  &A0 &B1 &C1 &D2 &G0 &H0 &I0 &K0 &M0 &N6 &P0 &R2 &S0 &T5 &U6 &Y1  S00=001 S01=000 S02=043 S03=013 S04=010 S05=008 S06=002 S07=060 S08=002 S09=006 S10=014 S11=070 S12=050 S13=000 S15=000 S19=000 S21=010 S22=017 S23=019 S25=005 S27=000 S28=008 S29=020 S30=000 S31=120 S32=002 S33=000 S34=000 S35=000 S36=014 S38=000 S39=000 S40=001 S41=000 S42=000 For "Integrated NPR Dial," the following settings need to be changed in the modem connect to the NPR: Hyper-terminal Session, BAUD=9600, change to 19200 Change "&N6" to "&N10" Change "&U6" to "&U10" All other variables remain the same as shown For 78051 Taps, use the “Remote Site Settings” and set up procedure.   Host Settings (This is the modem used at the workstation): DIAL=TONE B0 E0 F0 M1 Q0 V0 X0 Y0 BAUD=9600 PARITY=N WORDLEN=8 &A0 &B1 &C1 &D2 &G0 &H0 &I0 &K0 &M4 &N0 &P0 &R1 &S0 &T5 &U0 &Y0 S00=001 S01=000 S02=043 S03=013 S04=010 S05=008 S06=002 S07=060 S08=002 S09=006 S10=014 S11=070 S12=050 S13=000 S15=000 S19=000 S21=010 S22=017 S23=019 S25=005 S27=000 S28=008 S29=020 S30=000 S31=120 S32=002 S33=000 S34=000 S35=000 S36=014 S38=000 S39=000 S40=001 S41=000 S42=000 For "Integrated NPR Dial," the following settings need to be changed in the modem connected to the PC or Workstation: Hyper-terminal Session, recommend BAUD=9600, change to 19200 All other variables remain the same as shown For Taps, use the "Remote Site Settings".; Do not use the "Host Settings"

Issue Alert - New Worm: W32.Slammer UPDATED: January 27, 2003 SEVERITY: CRITICAL Go to the following Microsoft https://docs.microsoft.com/en-us/security-updates/securitybulletins/2002/ms02-039 web site for more information. Customers who have followed previously issued instructions and already installed Microsoft Security Bulletin MSO2-061 and the patch associated with Q317748 do not need to install the new patch in order to prevent the W32.Slammer worm from infecting their machines. Customers who have not yet taken those preventative measures should follow the directions provided in this alert to patch their machines against the vulnerability exploited by the W32.Slammer worm. Environment PRODUCTS AFFECTED: SQL Server 2000 RTM, SQL Server 2000 SP1, SQL Server 2000 SP2, and Microsoft SQL Desktop Engine Version (MSDE) 2000 Cause WHAT IS IT? The PSS Security Response Team (Microsoft) is issuing this alert to inform customers about the W32.Slammer worm, which is currently spreading in the wild. You are not at risk unless you are running one of the above listed products. Customers are advised to review this information and take the appropriate action for their environments. This alert is primarily focused at business customers. IMPACT OF ATTACK: Denial of Service TECHNICAL DETAILS: W32.Slammer is a memory resident worm that propagates via UDP Port 1434 and exploits a vulnerability in SQL Server systems that have not applied the patch released by Microsoft Security Bulletin MSO2-039. This bulletin was first available on July 24, 2002. This worm is designed to propagate, but does not appear to contain any additional payload. Customers can detect if they have Microsoft SQL Desktop Engine (MSDE) 2000 installed by using the following instructions: Right-click on the My Computer icon Select Manage Double-Click on Services and Applications Double-Click Services If MSSQLSERVER is in the list of services, the default instance of MSDE is installed on their machines. Other Instances may exist, if they do they will be listed as MSSQL$**** (where stars indicate the name of the instance). Resolution RECOVERY: Instructions for Removal of W32.Slammer from infected Microsoft SQL Server 2000 Servers or Microsoft SQL Desktop Edition (MSDE 2000) Set the SQL Server Service to Manual. Reboot the infected machine. If you are running Windows NT 4.0 Server Service Pack 6a install the patch referenced in Microsoft Knowledgebase Q258437. The Microsoft Knowledge Base can be found at http://support.microsoft.com. Install the security patch associated with Microsoft Security Bulletin MS02-061. Please note that the Microsoft Security Bulletin MS02-061 patch has been re-released to include the functionality previously only available through Q317748. Users who install this updated patch do not need to install Q317748. Users can verify installation of this patch by verifying the following files are at version 8.00.568: ssmslpcn.dll dbmslpcn.dll Set the SQL Server Service to Automatic.

Issue Routers / i.Lons configured as repeaters pass everything and consume bandwidth causing throughput / slowness issues in your system. Environment LON physical layer L-IP routers Cause The cause of throughput/slowness issues in a network might be that it is bogged down with needless communication. Resolution Configure router ports as "Repeater" to avoid channel conflicts during the construction phase of a project. After all of the nodes are commissioned, configure all routers as configured routers so that they only pass what is necessary upstream. This is especially important if using i.Lon 1000s, 600s, or Loytec L-IP routers as they will pass that unneeded data onto the ethernet.

Issue Multiple LNS databases under i.Lons or Loytec L-IPs which use the same ethernet network and the same domain ID can cause communication failures. Routers stop communicating in random order until some user intervention is taken. Environment LNS LonMaker, NL220 Cause It seems that packets intended for the Operator Unit/Host PC (or from it to other routers) will be received by the other routers and passed down to their Lon networks. This may cause unexpected or duplicated messages to be generated and put back on the ethernet to be received by who knows which device. Resolution Configure all of the networks under multiple i.Lons or L-IPs as a single LNS database If that is not an option, ensure that each LNS network has a unique domain ID.

Issue In Vista Workstation 4.20 or 4.21, when using full screen mode (F11), if all windows are closed, a gray screen is displayed. Environment Vista Workstation 4.2.0 or 4.2.1 Cause Closing all windows results in an empty display, but it is still taking up the whole screen. Resolution The only way to exit full screen mode is to use the ESC key.

Issue Creating I/NET Seven User Group Environment All I/NET Seven systems Cause During routine I/NET Seven Host PC software installation, the Windows operating system group "Everyone" provides access to the I/NET Directory under "Program Files." This configuration works efficiently for most installations operating over an isolated Ethernet network. However, this configuration grants access to all users and may concern IT administrators tasked with protecting and managing company assets, data and employees. To eliminate this security concern, IT administrators typically create special groups and policies to manage data and restrict access across their Ethernet networks. If this is a concern in your installation, you may create an "InetUsers" Group to restrict access. Resolution Please see Customer Advisory CA-2004-03. To create an "InetUsers" Group to which system users may be assigned, follow the steps outlined in this section. Creating such a group allows you to install I/NET Seven Host PC software on an Ethernet network while conforming to IT policies regarding restricted data access. "Local Users and Groups" is a tool used for managing such access and is available on the following operating systems: Windows 2000 Professional Windows XP Professional Member Servers running Windows 2000 Server A local user or group is an account that can be granted rights and permissions from your computer. Domain or global users and groups are managed by your network administrator. You can add local users, global users, and global groups to local groups. However, you cannot add local users and groups to global groups. "Local Users and Groups" is an important security feature, because you can limit the ability of users and groups to perform certain actions by assigning rights and permissions. "Right" authorizes a user to perform certain actions on a computer, such as backing up files and folders or shutting down a computer. "Permission" is a rule associated with an object (usually a file, folder or printer) and it regulates which users can have access to the object and in what manner. "Local Users and Groups" is not available on domain controllers. Use "Active Directory Users and Computers" to manage global users and groups.   "InetUsers" Group Setup Creating a Group You need to perform the following procedure in order to create an I/NET users group. Then, assign individuals to the I/NET users group in Windows. This will restrict access to I/NET directory to members of that group. By following this procedure, you will be maintaining the “Local Administrative” rights required for I/NET Seven to operate while remaining in compliance with IT policies. If you do not have I/NET running as a “Local Administrative” right on your PC, parts of the program will fail or not function correctly. Note: You must log on with Administrative rights on the local machine to perform the following steps. To create a new local group: Open Computer Management (right click My Computer and select Manage). In the console tree, click Groups. Click Action, and then click New Group. In Group Name, type a name for the new group. We recommend “InetUsers.” In Description, type a description of the new group. Click Create, and then click Close. Notes: To add one or more users to a new group, click Add following Step 5. A local group name cannot be identical to any other group or user name on the computer being administered. It can contain up to 256 lowercase characters except for the following: " / \ [ ] : ; | = , + * ? < > A group name cannot consist solely of periods (.) or spaces.   Assigning the Group to I/NET Open Windows Explorer o My Computer o Select the drive that I/NET Seven is on o Program files o InetSeven Right click InetSeven and select Properties. Select the Security tab. Select the ADD button. Choose the Location button in Windows XP – Choose Look in button for Windows 2000. Scroll until you find the Computer Name of the PC; highlight this PC Name. Then choose OK –Win XP only. In the white box, type the InetUser group name and OK. Highlight the InetUser group in the upper window. Give the group Full Control in the Permissions for Administrators window view. Select Apply and then OK. Close out of Windows Explorer.   Regedt32.exe access Go to the bottom task bar and choose Start. Select the Run option. Type Regedt32 Select OK. Choose HKEY_LOCAL_MACHINE Choose Software. Select CSI-Control Systems International and highlight. On the top task bar, select the Security tab. Choose Permissions. Select the ADD button. Choose the Look In button, making sure the location is the Computer Name of your PC. Scroll to find the InetUsers group. Select the ADD button and then OK. With the InetUsers group highlighted, give the group Full Control permissions. Choose the Apply button. Choose the OK button. Go to the top Task bar and choose Registry, then Exit. After you have completed these steps, close Windows and log off as Administrator. Log on as a User, and then launch I/NET Seven.   Recommendation Review this advisory with individuals responsible for purchasing, installing or maintaining I/NET Seven systems. For more information, contact your Schneider Electric representative.

Issue Creating custom Multi-state Text definitions Environment Vista 4.2x Workstation Cause "Value-Multi-state" objects in Vista have a property called Multi-state Text which provides the definitions to enumerated signals. This is similar to the paired text in a "Value-Binary" signal. However you cannot add a new entry in the Vista 4.2x workstation. Resolution To add a new entry to the drop down list: Navigate to C:\Program Files\TAC\TAC Vista\ Find the old workstation program tamain.exe Use the object selection dialog to select the Object Type filter of "Multi-state Definition" Add a new definition by following the naming convention of the existing definitions. Once you have added the definition, edit the object and enter the text values in the “MSTXTS” field separated by comma in the order that match the enumerated signal. Example: OFF, ON SECR, UNLK, LOCK

Issue Modifying protection status of Vista 4.2x database objects Environment Vista Workstation 4.2.X Cause Vista allows you to enable protection of database objects which restricts your ability to change the object or delete it. Protected database objects are displayed with grey text and unprotected objects are displayed in black text. While the majority of protected objects are those created by the system there are times when a user has elected to make an object protected. Resolution The method used to enable protection is: Right click on the object and selecting "Authority" Inside the "Authority" dialog box is a check box labeled "Protected database object" Check this box and select OK. You will see no change in the Vista Workstation. To make the change go into effect, refresh the display by pressing F5 or right clicking and selecting "Refresh"

Issue US Robotics 56k V92/V90 Modem Settings (Non - NPR Dial) Environment I/NET site with need for Modem Cause What are the US Robotics 56k V92/V90 Modem Settings (Non - NPR Dial) settings? Resolution DIAL = TONE B0 F1 M1 X0 BAUD = 9600 PARITY = N WORDLEN = 8 &A0 &B1 &G0 &H0 &I0 &K0 &M0 &N6 &P1 &R1 &S0 &T5 &U0&Y1 S00=001 S02=043 S03=013 S04=010 S05=008 S06=004 S07=060 S08=002 S09=006 S10=014 S11=070 S12=050 S13=000 S15=000 S19=000 S21=010 S22=017 S23=019 S25=005 S27=000 S28=008 S29=020 S30=000 S31=128 S32=002 S33=000 S34=000 S35=000 S36=014 S38=000 S39=000 S40=001 S41=000 S42=000 Set the configuration at the Host Modem and site Modem to the same configuration as shown above. Take out any initialization strings you may have added in windows “ Phone and Extra Settings” dialogue. Select “Change Default Preferences” in the same dialogue and change the defaults to port speed 9600, Data Protocol to Standard EC, Compression disabled, and Flow Control to none. Make sure in the Modem properties dialogue to Maximum Post Speed is set to 9600 baud. This needs to be performed for the Host Modem and Site Modem. Switch settings 1, 5, 6, 7 are in the “UP” position. Note: Non - NPR Dial Note: US Robotics 56k faxmodem V92 and V90 standard technologies PN:USR5686E

Issue Serial Communication with Xenta Units (511, 527, 911, 913): Environment Xenta Servers Xenta 511, 527, 701, 711, 721, 731, 913 Cause Incorrect cables can cause improper ground references between the PC and the Xenta unit, which will disable serial communication. Resolution The Xenta units that utilize a web interface all have a certain amount of setup that is done with a direct serial connection via HyperTerminal. This communication however can be problematic at times due to grounding between the Xenta unit and the computer. If both devices do not share a common earth ground reference, then communication will not occur at all. There will be no indication that either side is receiving the transmissions from other device. This is most commonly encountered when using the incorrect cable since the proper cable provides a conductor for ground and thus a common ground reference. An OP panel cable is not the proper cable to use in such a situation. Instead you should be using the cables found in the TAC Xenta programming Serial Kit. If you are using a cable made by someone other then TAC the most likely cause is your cable having the improper or insufficient connections. When stuck in a situation where the proper cable is not available and working with a laptop computer we recommend that you plug the computer’s power supply in preferably to the same power supply as the controller to try to establish the common earth ground. Any other attempts to stabilize the differing grounds will be at your own risk.

Issue LonMaker 3.1 re-synch CPs causes the template configuration parameter settings & some Xenta 100s to be corrupted. Controllers subsequently modified by LonMaker can also be corrupted. Environment LonMaker 3.1 Xenta 100 series controllers, Revision 1.2X Cause LonMaker 3.1 handles this operation differently than 3.0. At one point we recommended that you avoid "Reset device to default values" and "Set device template defaults from device" commands, but "Upload values from device" was ok. We've since learned that any resynch CPs command can cause problems. Resolution Until this is changed in a future revision, don't do ANY resynch CPs command. (This does not refer to resynching the Lonmaker drawing and the database. Those operations work correctly and are necessary to construct your LNS network.)

Issue "Completion event failure" and/or "Waiting for unit to restart" errors are received when attempting to download a controller which has already been commissioned and contains an existing Menta application. Product Line TAC Vista Environment LNS Network Xenta Programmable controllers Xenta 280, 281, 282, 283, 300, 301, 302, 401, 401:B System Plug-in Cause The controller is busy responding to all other requests for communication and is not able to focus solely on the download. Resolution Before downloading, right-click on the controller and select Manage Set the node status to offline Download the controller Set the node status back to online. Alternatively, Before downloading, de-commission the unit. Select “Preserve neuron ID" to allow the plug-in to communicate with the controller and to avoid having to re-enter the ID or service pin. Download the controller Re-commission the device. This will prevent the controller from performing other communication while trying to receive the download and thus being unable to keep up.

Issue Problems finding all defined Holiday charts using the TAC Vista 4.20 editor Environment TAC Vista 4.2 Time Schedules Holiday Charts Cause Find all holiday charts to review scheduled holidays for the year. Resolution There is a feature in the time schedule editor that shows all schedules in a table format instead of a the calendar format. Press CTRL + SHIFT + D keys while the editor is open you will be able to edit all time schedules in one table.

Issue Intermittent "Completion Event Failure" Xenta controllers go offline and come back online randomly Environment Vista Workstation LNS Database LonMaker / NL220 Cause Completion event failure can occur for many reasons: not using Lon cable terminators, too much network traffic, "acknowledged" type SNVT bindings to a node, etc. Resolution "One to many" bindings set as acknowledged can cause data storms, download failures, completion event failures, X'ed values in graphics, and communication problems because controllers are busy re-sending information. The reason the controllers might be resending is because they did not get a response from one of the recipients or did not get a response in time. It then resends the packet to all of the recipients, not just the unresponsive node, and waits for acknowledgments from all of them. If one of them is offline, there will be a lot of unnecessary network traffic being generated. When "one to many" bindings are required it is almost always preferable to select unacknowledged or repeated as the binding type. Note that the default binding type for programmable controllers is acknowledged. If you still have problems with completion event failures after making sure that the network is correct, you can change the number of retries in the Network object. In TAC Vista Workstation, right click on the Lonworks Network object, go to Properties, select the Timer tab, under Networks timer change the retry from 2 (default) to 4. If using LonMaker, right click on the LNS Network Interface, go to Properties, select the time tab, set the Non Group Receive Timer to the recommended 6144ms. If NL220 is being used, double click the LNS Network Interface, go to the Network tab, change the Non Group Timer to the recommended selection 11 - 6.144s.

Issue Access Control Application Issues including: Using large number keys Translation tables - when and how Importing and converting existing I/NET 2000 databases Environment Access Control Application Cause Getting started with an access control application. Resolution Detailed information described in: I/NET Getting Started Guide (TCON298 Chapter 1) I/NET Technical Reference Guide (TCON300 Chapter 9) Upgrade.txt file included on I/NET Installation CD.

Issue Deny Entry Select transaction / message received when using Secondary Schedules. Environment I/NET Seven DPU Controllers 7910 7920 1284 Cause To use any of the features, listed below, requires that the DPU be a 7920 w/ MIP board or the SCU1284. 7910 and 7920 w/o MIP board will still work with the I/Net system but they cannot use these functions.  The host prevents the download of these features to any DPU revision prior to 3.10. Feature 1: Secondary schedule. Feature 2: Shift management. Feature 3: Extended elevator control to support up to 79 floors.   Resolution Secondary Schedules can only be implemented on 7920 (Mipped) 48K boards. If a Secondary Schedule is set up for an individual on doors that are controlled by a 7920 DPU that use the standard EPROM chip, a “Deny Entry Select Message” will be generated in the Transactions. If 7910s are present then the same above rule applies.

Issue File Equalization not working even though I/NET indicates Equalization is online. A balloon message pops up saying that Equalization is Online but the data is not shared between Client and File master. Environment Windows XP I/NET Revision1.10 - 1.14 Cause There is an issue with Equalization when using Windows XP as File Master and Clients with I/NET Seven Revision 1.14. Once a Client is connected to the file master, a balloon message pops up saying that Equalization is Online, but it never gets the snapshot from the File Master.  Resolution To correct this issue the following will apply: Verify that the user has full access right on their Windows user Password. Go to My Network Places, Right Click and select Properties. Select the Advanced Tab, verify that there are no checked boxes for the Firewall. Go to Administrative Tools, Local Security Settings. Local Policies, Security Options, Locate the policy "Network Access: Sharing and Security Model for local Accounts" Change the security setting to "Classic – local users authenticate as themselves". Apply changes, shut down and restart the PC.