Building Automation Knowledge Base

Issue Error message: Unable to Read ATS DIR Environment TAC INET ATSDIR Cause The logged on user does not have read/write permissions for the I/NET Seven Directory. Resolution Go to Program Files (Right Mouse Click) Select the properties option Select the Security tab Highlight Administrators Select Advanced Select Add. Now add your account - You may have to browse it in. Note: You need to have Full Control as a minimum. Now apply and close all windows. Restart your operating system and launch I/NET. Caution: If you are not sure, please contact an IT Administrator or Schneider Electric Product Support.

Issue Running I/NET Seven with a case sensitive SQL collation causes errors. Environment I/NET Cause A collation issue has been identified with foreign language versions of Microsoft Windows. If InetDb is backed up from a PC using SQL_Latin1_General_CP1_CI_AS to a PC using a different collation then creating archives will fail. If I/NET is installed on a PC with any case sensitive collation (CS) then DbCreate will fail to create InetDb. This problem will be fixed in I/NET Seven 1.17 and 2.01 Resolution Upgrade to a version of I/NET Seven greater than 1.17 or 2.01

Issue Loading I/NET on a PC that has full SQL and the Password is not known. Environment I/NET Full SQL installation Cause If installing I/NET on a PC that has full SQL, MSDE does not get loaded and there is a conflict with the “sa” Password or an existing instance of SQL. Resolution Caution: Before proceeding with the following steps, call Product Support for an SQL SP script to re-attach the database files. Go into “C:\Program Files\Microsoft SQL Server\MSSQL\Data” and copy the InetDb.mdf and InetDb_log.ldf files to a location outside SQLs directories. Go to control panel & select the Add\remove program. Select the Microsoft SQL Desktop Engine program and remove it. Open Windows explorer again and go to C:\Program Files\Microsoft SQL Server file folder Highlight the Microsoft SQL Server file folder and delete it. IMPORTANT, go into the recycle bin and delete the Microsoft SQL folder from the BIN. Reboot the PC, and then place the I/NET CD into the PC to launch the installation. MSDE will install first using the “sa” password followed by I/NET. Once installed, verify that I/Net comes up and functions properly. Reload full SQL and select the upgrade radio button when prompted. Once it gets loaded, verify that it is functioning properly with all other applications. Copy the InetDb.mdf and InetDb_log.ldf files back to their original location (C:\Program Files\Microsoft SQL Server\MSSQL\Data). Call Product Support for a zip file that will reattach this file. Go into DbCreate and select the “Upgrade” option. Then force an upgrade to resynch the SQL database.

Issue Updating the UPD Files for MR-AHUs Environment I/NET Seven Site Cause How to download a different application to an MR-AHU in order to control the economizer damper  Resolution There are times when the user needs to download a different application to an MR-AHU in order to control the economizer damper in a different way. To do so you must configure I/NET for which specific .UPD file to load by editing ASC.cnf. It is located within the I/NET Seven Data subdirectory and the default path is I/NET Seven\Data\ASC.cnf. As a safety measure, save the default version of the ASC.cnf file, giving it a different name, such as “BackupASC.cnf”. Open the ASC.cnf text file with MS Notepad text editor. Find the line that reads "2-4-2.10=AHU_2210". Place a colon “:” and a space at the beginning of that line. (The colon and space act as a comment flag and I\NET ignores those lines when it's time to download.) Then find the line which reads ": 2-4-2.10=AHU_2100" and remove the colon at the beginning of that line. Save the modified ASC.cnf file and close notepad. This tells I\NET that you want to download the version which controls the economizer damper based on room temperature. The default setting causes I\NET to download the application which controls the damper based on mixed air temperature. The MR-AHU is shipped from the factory with the 2100 application so if you want to change to mixed air control (2210), just update ASC with no changes. To actually load the UPD file into the controller, open I/NET, connect to the SLI, choose edit-controller-ASC functions. Choose "Update ASC, then select which controllers you wish to change. Click OK and when prompted for the file path, click OK or hit enter. This causes I\NET to download from the default (data) directory. If this ASC has already been in use and it's point database updated to the SLI, one more step is necessary. The ASC, having just been loaded with the default application, has default designations for the station parameters and point types. The SLI may not have them in the same locations. To force them to be equalized: Open the MCU_configuration Select the ASCs in question Set them to internal Click OK Re-open MCU_configuration Set them back to ASC Click OK.

Issue Erasing NOVRAM from ASCs Environment I/NET Seven Site Cause How to erase the firmware and programming in the ASC  Resolution There is a way for users to erase the firmware and programming in the ASC by following the following steps: Note: take care that you do not clear the memory on a stand-alone ASC with no SLI or I/NET computer with which to perform step 6! This procedure does not just reset the parameters, it removes the entire application. Remove power from the ASC. Place DIP Switches 6-12 in the off (0) position. Apply power to the ASC, and then remove power again. Place DIP Switches 6-12 in the on (1) position. Apply power to the ASC. Download the UPD file by selecting Update ASC to restore it to defaults. On occasion, it may be necessary to repeat steps 1-5 twice.

Issue When Reports are opened and the user selects a Report then tries to run the report, an error comes up that says “Server Failed to Initialize” and nothing happens. Environment I/NET Seven Site Cause error comes up that says “Server Failed to Initialize" Resolution There is a fix for this but an IT individual will need to be present or the user must have admin rights to do this. Shut down I/NET and Seven Reports. Go to Start, Run and type Regedit at the prompt. Go to Local_Machine, Software, Microsoft, MSSQL Server, Super Socket Net Lib. Expand this and there should be two folders listed in here, NP and TCP. Highlight the Super Socket Net Lib and a Protocol file appears. Right Click this file and modify it to display the Hex addresses in there and verify that one exists for NP and TCP. Value data: 0000 74 00 63 00 70 00 00 00 t.c.p... 0008 6e 00 70 00 00 00 00 00 n.p..... 0010 Note: If you are not sure please contact an IT professional to assist you.  

Issue Synchronizing time with a DVR Environment DVR CCTV I/NET Cause PC time on the DVR is behind the PC time on the I/NET Seven system.   Resolution When an event occurs in a Digital Video Recorder that is interfaced with I/NET Seven and you want to see the associated video with this event it is possible that no video will appear without searching manually. This occurs when the PC time on the DVR is behind the PC time on the I/NET Seven system. During configuration of the interface it should be verified that both computers are using the same time settings to include current time and time zone. These can be set either manually or if additional precision is necessary through the use of a NTP server.  

Issue MRs going to Sleep Environment I/NET Seven site with MR's Cause When certain DDC Modules are being used in an MR it uses both the NOV RAM and RAM Memory Resolution When certain DDC Modules are being used in an MR it uses both the NOV RAM and RAM Memory. When writing DDC care should be taken so as to not exceed the amount of memory that is within the device itself. It has 130 Bytes of RAM and 1024 Bytes of NOVRAM. The MR supports six DDC module types and an interconnected control configuration up to 16, depending upon the types. It may appear that the memory is not maxed out, when it is all added up but it causes the MR to “go to sleep”. The user will have to go to the MCU Configuration and turn that MR Internal and then External again, to “wake it up”. Depending upon the application, if there are more than 4 PID modules, the first 4 work, but the others do not. This can also occur if there is a huge calculation on one of the points, the same symptom and result will apply. Please be selective as to which module and function you’re using for your application. Note: MR-resident DDC modules only reside in the MR (not in the MCI, MRI or I/Site LAN. Therefore, these modules are not available for use in any MR tagged as Internal in the MCU configuration editor.) The following table shows the amount of memory that each item uses:     Points   Point NOVRAM Bytes RAM Bytes DI Point 4 1 DA Point 4 1 DM Point 4 1 DO Point (Internal) 4 1 DO Point (External) 4 3 DC Point (Internal) 4 1 DC Point (External) 4 3 AI Point (Internal) 16 3 AI Point (External) 16 5 AO Point (Internal) 16 3 AO Point (External) 16 5 PI Point 4 2         Modules   Module NOVRAM Bytes RAM Bytes PID Module (Without Filter) 40 14 PID Module (With Filtering) 40 19 Floating Module (Without Filter) 40 12 Floating Module (With Filter) 40 17 Two Position Module (W F) 28 2 Two Position Module (W/O F) 28 7 Relay Module (Standard) 20 2 Relay Module (DBB, DBM, INT) 20 4 Reset Module 48 2         Calculations   Calculation NOVRAM Bytes RAM Bytes Calculation Modules Overhead Module (fixed) 6 2 Each Operator (+, -, *, /, etc) 1 N/A Each Point Address (P0, P1, etc) 2 N/A Each Constant (C0, C1, etc) 4 N/A Each Line (L0, L1, etc) 1 N/A Calculation Module Total * 2         Lines   Lines NOVRAM Bytes RAM Bytes MR-DDC Lines N/A 4 Note: Verify that you are using the most current EPROM for the revision of software that you are running.

Issue User upgraded their systems to I/NET Seven from I/NET 2000 rev X.XX and noticed that their databases cannot be downloaded to the controller anymore. Environment I/NET Seven upgraded from I/NET 2000 Cause If dial is not being used at this site, then the controller should be set up as a 779301. Resolution To check how the controller is configured: Use an HHC (Hand Held Console) Plug it into the port Press CODE 90 Enter. If it is set up for a 779301, the bytes available after the bin file is downloaded are 140439 and for a 779306 the bytes available are 95639. The reason for this difference is that the memory is allocated for the Messages Queue. If for some reason the database does not get downloaded then the problem lies in the database itself where there could be a lot of Trended Data that needs to be discarded or Archived to create more room.

Issue Input alarms in a 7797-15 Environment I/NET Seven Site Cause If a 7797-15 running revisions 1.01 of the binary file has alarming configured on an input point the alarm text will be sent to the message window in AMT every time the point is scanned. This can cause an enormous load on your controller LAN as well as flood your message window making it unusable depending on the number of input points being used.  Resolution If a 7797-15 running revisions 1.01 of the binary file has alarming configured on an input point the alarm text will be sent to the message window in AMT every time the point is scanned. This can cause an enormous load on your controller LAN as well as flood your message window making it unusable depending on the number of input points being used. The only current work around is to turn off the message masking and alarm priority for the input point that has the Modbus address associated with it. Then create a secondary point that has the alarming configured and use a P0 calculation to transfer the value. Any event definitions, trend sampling, or other controller functions can still operate on the original input point. These steps are not necessary for output points since they can be set as internal points and still communicate their values to the Modbus network while the inputs must be external to function.  

Issue Several doors need to be removed in an existing I/NET Seven System. What is the proper way to do this? Product Line TAC INET Environment I/NET Seven with Access Control Cause Steps to remove Doors in an existing I/NET Seven System Resolution It should be sufficient to just deselect the door from the tenant and then NETCON on one equalized client, the file master, or Standalone PC. If the door physically goes away, the next time an operator enters an individual or group that had that door it will display a * for the offline/deleted door. At that time just select "Unselected" option and that door will be removed from that list. If all trace of the door needs to be removed: Remove all access privileges from a door. Be sure to check System View to verify they are all removed. Remove the door from all tenants Connect to the Controller and select Edit>Controller>Doors Delete the Door Close of the Door editors and select Edit>Host Computer>Network Configuration Penetrate to the Door level and delete the door objects. Next, In the Resident I/O editor delete any points associated.

Issue Conversion utilities location on the I/NET Seven CD. Environment I/NET 2000 - I/NET Seven Cause Location of the Conversion utilities on the I/NET Seven CD. Resolution The location of these files are on the I/NET Seven CD in this location: Program Files > INET Seven > Conversion Files

Issue Data can be seen when previewing the report, but when printed nothing happens. Product Line TAC INET Environment I/NET Site Cause No printer is selected or the no printer option is checked. Resolution Open the I/NET Seven report that has the issue. Choose the Design yellow tab. Go into the Main REport area on the left side of this report. Place the mouse cursor in the white area below the Tree List. Right-click in the blank space to bring up the options menu. From the context menu select Designer > Printer Setup. In the upper left corner of the Printer Setup dialog confirm that the "No Printer" option is unchecked. This should allow you to select a printer. Remember to save this corrected report back in the I/NET Sven reports list.

Issue Interfacing with a Trane BCU panel with a 7797-12 ICI Environment I/NET Seven Site with 7797-12 ICI and TRANE BCU Cause The 7797-12 ICI is a PTP (Point to Point) RS232 BACnet device which can be used to interface with Trane systems using their BCU panel. The BCU panel can be equipped with an optional Ethernet card. However the presence of this card can modify the addressing structure of the Trane device disabling communication with the ICI. Resolution The 7797-12 ICI is a PTP (Point to Point) RS232 BACnet device which can be used to interface with Trane systems using their BCU panel. The BCU panel can be equipped with an optional Ethernet card. However the presence of this card can modify the addressing structure of the Trane device disabling communication with the ICI. To resolve this problem simply remove the Ethernet card from the BCU panel. If the Ethernet card is required then a alternative interface will have to be utilized.  

Issue Connecting to Controllers using Dial. Environment I/NET Seven Site Cause How to connect to remote sites using Integrated Dial Resolution If the user is connecting to remote sites using Integrated Dial and the site controllers are not visible, please check the following settings: Open I/O Server, modify the dial profile Uncheck the Dial Box Shut down and restart I/O server Connect again If the user is connecting to remote sites using ADAA and the site controllers are not visible, check the following setting: 1.DTE (Host)--------DCE (Modem)-------DTE (Controller)-----9600 (Baud) All these need to be at 9600 Baud, otherwise the lights on the I/O Server would only show Red and no Green. This indicates that there is a Transmit but no receive between one of the above components. For I/NET Seven, only the US Robotics 56K Modems are supported.

Issue Wildcard Filtering in AMT. Environment I/NET Seven Site Cause How to use Wild Card Filtering Resolution In AMT when filtering is being done on devices for data within the Device Name field, there are several characters that can be used to accomplish this task: % The % character is like the * character in windows find files. Searching for a device name of %device% would return any device name containing the string “device” _ The underscore character allows any single character. For example, searching for a device name of “device_” would return “device1”, “device2”, “devices” etc. () The left and right closed brackets allow a single character to be within a specified range (for example: (a-c) or within a set of characters (for example (abcd). Searching for a device name of “device (a-f) would return “device a” through to “device f” but not to “device g”. (^) This is the negation of the previous wildcard. It specifies that a single character should not be within a set of characters (for example, (^a-c) or (^abcd)).  

Issue Definable Tool Settings are not Transferable Environment I/NET Seven Cause With the introduction of I/NET Seven, the Definable Tools button is a new feature providing a useful shortcut for applications to be more user friendly. Resolution The two kinds of tools available are Events and Shortcuts. The definition below gives the description of their uses: Event - Use this tool to execute an event sequence defined in a controller. Shortcut - Use this tool to launch another application, open a file, visit a website, etc. There is a misconception though, that they can be created on a graphic page, saved and then re-applied at another location. This is not the case. These Tools and Buttons are PC Specific and cannot be transferred from one PC to another because the SQL database does not save these settings. If the user wants to set up these Tools (Events and Shortcuts) then they would have to do it for each PC, that is looking at the data or each page that it exists on. This is providing the user has rights to these buttons through the Host Passwords.

Issue Configuring Error Logging for Program Crashes Environment I/NET Seven Site Cause Dr. Watson is not the default debugging software then the following steps can be used to configure it to be used as the default debugger Resolution Dr. Watson is a debugging program that is installed with the Windows operating system that generates error reports when programs crash. These error reports are very useful in determining the cause and support personnel will typically request a Dr. Watson log file as the first step of troubleshooting the problem. If for some reason Dr. Watson is not the default debugging software then the following steps can be used to configure it to be used as the default debugger. In the Start menu Run command type "drwtsn32 -i" and select "Ok". You should receive notification that Dr. Watson has been installed as the default application debugger. In the Start menu Run command type "drwtsn32.exe" and select "Ok". You can configure the directory that log files will be placed in among other options. The default directory is "C:\Documents and Settings\All Users\Documents\DrWatson\". In the Start menu Run command type "regedit" and select "Ok". Browse to "HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\Current Version\AEDebug" and verify that the entry "Auto" is set to the value of 1. Dr. Watson log files should now be generated upon program crashes. The above steps should be valid for Windows 2000 operating system and newer

Issue MSDE Not Installing on a Windows 2000 Professional PC It gets to 98% and then quits without installing anything Environment MSDE Windows 2000 Professional Cause Microsoft network printer sharing settings are stopping the installation from completing. Resolution Open up My Network PlacesPrinter Go to Network and Dial up Connections Go to Local Area Connection Select the General Tab Uncheck the Files and Printer Sharing for Microsoft Networks Retry the install again. Once the software is installed, go back and check that box again so that Crystal Reports will run and print to a printer.  

Issue Printer Use with Emergin Software Emergin Software worked fine until I/NET 2000 was upgraded to I/NET Seven. Now the printer starts to print the Events and Alarms vertically instead of horizontally. Environment Emergin Software I/NET Seven upgraded from I/NET 2000 Cause Upgrade process requires that the COM port be added back again following the upgrade. Resolution Remove the COM Port from the Device Manager Reboot the PC so that it rediscovers it or re-adds it back again Restart I/NET Generate an Alarm and verify that it works correctly. If for some reason this does not work: Verify that you have the latest Emergin Build that is compatible with I/NET Seven, then try it again. You would have to go to the Emergin Website to get this information at www.emergin.com.