Issue When I/NET is installed for the first time and MSDE begins to install, it fails on the "renaming of the SQL folder" partly due to "Read Only" rights to the folder SQL is installed in. "The error message has this reference; SQL: MSSQL$MICROSOFTBCM cannot be renamed". The install of I/NET stops at this point. You do not have the option to use "Add Remove Programs" to uninstall the previous install of SQL.   Product Line TAC INET Environment DELL PC computers I/NET Seven Cause Loading I/NET on a new Dell PC with XP Pro as its OS that already has an instance of MSSQL installed.   Resolution The solution is to go to Manage\Services\Applications\Services... to Stop and or Disable (3) current instances of SQL running. Right click on "MSSQLSERVER" and click on Properties Click on the Startup type, then select "Disabled" Click Apply and then repeat for MSSQLSERVERAD Helper and SQLSERVERAGENT. Close the Manage window Begin the I/NET Seven install again. MSDE will install correctly as well as the rest of the I/NET Seven. This problem has only been seen on DELL PC computers.

Issue Do you have graphic pages and lines that do not update after an upgrade? Environment I/NET Seven Windows PC Graphic pages Cause The following is the minimum requirements for any PC that is going to run I/NET Seven. Pentium IV (2.500 MHz). 1 GB RAM. 3 GB of available hard drive space. The Hard Drive should be 120 GB or more. Resolution  There is one primary reason for this: Insufficient Memory: - Check the memory of the PC and verify that it is sufficient for the I/NET Seven Application. Explore into the hard drive C. Go to Properties and look at the physical description of the drive.

Issue If you do work with I/NET and Emergin and have an issue with the Alarms not getting cleared after it goes back to normal, this information might be helpful to you. Environment I/NET Seven Site Cause I/NET and Emergin and have an issue with the Alarms not getting cleared after it goes back to normal Resolution Successfully Implemented: Paging via snpp (corporate paging server) and SMTP (e-mail). Paging on alarms generated from DA points, as well as analog points that are out of range and giving the value at the time of the alarm. Escalating pages through to a list of people at certain times and canceling via "Return to normal" or "Alarm Acknowledged". This pages those on the list who have been paged the first time that the message has been cancelled. Issue Canceling alarms with specific cancellation keys. Within Emergin Alarms Messenger - each alarm has the opportunity to define a certain cancellation key. However the software scans all cancellation keys to see if it meets the criteria to cancel, NOT THE SPECIFIC ONE. EXAMPLE: Givens: 2 alerts with specific keys - AHU1 Fan Alrm & AHU2 Fan Alrm 1 general cancellation key for "Return to Normal" 1 general cancellation key for "Alarm Ack" AHU1 Fan Alrm alert is assigned the cancellation key for "Return to Normal" AHU2 Fan Alrm alert is assigned the cancellation key for "Alarm Ack" Execution Working as Planned: AHU1 Fan Alrm goes into alarm and sends pages. AHU1 Fan Alrm returns to normal and cancellation page sent to all previously paged. Execution not working with specific cancellation: AHU1 Fan Alrm goes into alarm and sends pages. AHU1 Fan Alrm is acknowledged in INET and sends a cancellation page to all previously paged. Then the point returns to normal and nothing pages. ***Because the "Alarm Ack" was setup for AHU2, it was lumped in the cancellation list with "Return to Normal." Therefore the first condition cancels - not the one specifically assigned. EMERGIN WORKS AS FOLLOWS: Emergin lumps ALL Cancellation together. Any alert is cancelled with the FIRST cancellation tag it matches - NOT the specific one assigned in the alert.

Issue Database Older than Expected error. Environment I/NET Seven Cause Do you see this balloon error message displayed after an upgrade from one revision to another in the System Tray? This is caused by the database that did not properly upgrade.  Resolution Shut down I/NET and the I/O Server. Go to Program Files, I/NET, Db Create Utility. Select Upgrade Database. Put the SQL Admin password that was created when I/NET was installed. Click Start, in the dialog box, a line would be displayed stating that you are upgrading from build X.XX to X.XX depending on the upgrade. Once finished, restart I/NET again and that message would not be displayed anymore.

Issue Setting Up I/NET Seven Trends Product Line TAC INET Environment I/NET Seven Cause Problems configuring Trend Data Resolution I/NET displays this window when you select Add Trend, Add Cell, or Modify from the Seven Trends Definitions window. You must define the following information: Trend Definition only Select the desired point from the Point Selection dialog. Only one point may be selected for a trend definition. This field cannot be edited once the trend definition is saved. This field is not available for cell definitions. Note: You may click the ... button to return to the Point Selection dialog at any time during a new trend definition. However, once the trend definition is saved, you cannot change the selected point. Enter a unique Name for this trend or cell definition, up to 30 characters. The default name for trends is in the format Point Name -- --Trend Type if you are connected to the controller, and Point Address -- Trend Type if you are not connected. The default name for cells is in the format Cell Number -- Trend Type. Note: If you do not enter a name, the default name will change automatically with the point (or cell number) and trend type selection when you are creating a new trend. You may change the name of a trend or cell definition at any time without loss of data. Choose a Type from the drop-down list. This field cannot be edited once the definition is saved. Discrete Sample — Store the discrete state of a point at regular sample intervals. The point can be a DI, DA, DM, DC, or DO point defined with a TR extension. Analog Sample — Store the analog value of a point at regular sample intervals. The point can be an AI, AO, GI, GO, or PI point defined with a TR extension. Runtime — Store the daily runtime minutes for a point or points. The points can be DI, DC, or DO points defined with an RT extension. Consumption — Store the daily-consumed value of an accumulator point or points. The points must be PI points defined with a CN extension. Demand — Store the KWH, Peak KW, and time of Peak KW values on a daily basis for a particular demand meter. The point must be a PI point defined with a DC extension. Override — Store individual KWH values, shared KWH values, and override runtime on a daily basis for a specific zone of a Model 7750 Building Manager. The point can be a DC or DO point defined with an OB extension.   Define Transient Duration in days. The trend can be configured to automatically discard the oldest trend data after a time period you specify (1 to 45 days). Note: If you wish to archive Seven Trends data, the transient duration must be set to zero (0), indicating that the data should not be discarded. Only samples with a transient duration of zero can be archived. Enter a Cell Number (1–1023). The cell number must be greater than zero (0) in order for Seven Trends to store sample information. This field is provided for backward-compatibility with older versions of I/NET, and can be used to group samples in reports. If you are creating a new cell definition, this field can be used to auto generate trend definitions (refer to Using Cells to Generate Trend Definitions for more information). This field cannot be changed once the cell definition is saved. Otherwise, this field is not used in I/NET Seven and can be any value. Note: For manually defined trends, the cell number in the DCU editor does not need to match the cell number for the trend definition. The cell number in the trend definition is the one that will appear on reports. Select OK to save your changes. The system returns you to the Seven Trends Definitions window.

Issue Invalid Page fault in mfc42.dll or error 429 for I/NET 2000 users Environment I/NET 2000 Cause Invalid Page fault in mfc42.dll or error 429 for I/NET 2000 users Resolution  The following steps will get this fixed really quickly: Go to the “Start” Button on the task bar at the bottom. Choose the “Run” Button. Type in REGEDIT, then hit Enter. Make sure that I/Net and I/O Server is not running. GO to HKEY_Current User. Scroll down to the “Software Tab”. Select the file folder “CSI-Control System International”. Select the “I/Net W” file folder. Select the “toolbars” file folder. Delete all the Tool Bar entries. Re-boot the PC, this will rebuild the new toolbars in the registry listing. Start I/NET again and you should be able to log on now.  

Issue TTS 100 Series Thermistor Sensor Environment I/NET Seven Site Cause Conversion coefficient is for a Thermistor for a particular controller, and can it be used with the new controllers such as MRs/Motorola and HID/Dorado card readers Resolution TTS100 SERIES THERMISTOR SENSORS Dale 1M1002-C3 Curve 1 Product Support Services continues to get calls asking what the conversion coefficient is for a Thermistor for a particular controller, and can it be used with the new controllers such as MRs. Therefore we have consolidated into this Tech Tip the variety of ways the Thermistor Series Temperature Sensors can be used with Schneider Electric's current family of controllers, including wiring, controller input range and conversion coefficients for both degrees Fahrenheit and Celsius. It makes for a great quick reference. Keep it handy.   MR123-210(A), 430(B), 032(C), 400(D) "I/STAT PORT ONLY" MR88 (F), MR632 (G), MR160 (H), MR88R (K) "I/STAT or UI Inputs" Resolution Counts Input Range Read Range M Slope B Intercept Temperature Range Span 0 - 255 0 - 5 vdc 0 - 5 vdc 0.018 -148 -40 - 176°F Normal   0.01 -100 -40 - 80°C Normal 102 - 204 2 - 4 vdc 2 - 4 vdc 0.018 -148 32 - 90°F Narrow   0.01 -100 0 - 32°C Narrow   MR55 / 55X (J) Resolution Counts Input Range Read Range M Slope B Intercept Temperature Range Span 0 - 255 1.5 - 4 vdc 1.5 - 4 vdc 0.018 -148 25 - 113°F Normal   0.01 -100 -4 - 45°C Normal   Look-up Table #1 if wired to the I/STAT Port Look-up Table #2 if wired to one of the Universal Input -Plug a 10K in B slot Red - Signal In, Green - Ground I/NET 7700 SERIES CONTROLLERS   Accuracy: +/- 0.2 DegC @ 25 DegC, Nominal Resistance: 10,000 Ohms @ 72 DegF Operating Range: TSS100WJ, D1, D2, I1, I2, S1, S2,SP, SS: 32 to 158 DegF ( 0 to 70 DegC) TSS100OA: -4 to 158 DegF ( -20 to 70 DegC ) TSS100W: 32 to 122 DegF ( 0 to 55 DegC) Power Requirements: 5 Volts excitation via 10K Ohm Resistor Negative Temperature Coefficient ( Dale 1M1002-C3 Curve 1 )   *7716 PCU, 7718 PCU, 7728 I/SITE I/O, 7756 PCU (Upper Board Only) Resolution Counts Input Range Read Range M Slope B Intercept Temperature Range 0 - 4095 0 - 5 vdc 0 - 5 vdc -0.1 300 -40 - 230°F   -0.05 150 -40 -110°C   819C/V (10K in B slot) Red - Signal In, Green - Ground, DegF / DegC - See LUT Chart *7716 PCU Rev. J boards ONLY   7756 PCU (Lower Board Only) Resolution Counts Input Range Read Range M Slope B Intercept Temperature Range 0 - 32767 0 - 10 vdc 0 -5 vdc 0.018 -148 -40 - 230°F   0.01 -100 -40 -110°C   6553.5C/V (10K in B slot) Red - Signal In, Green - Ground, DegF / DegC - See LUT Chart Thermistor Sensors Look-up Table Chart   7716, 7718, 7728, 7756 (Upper Board) Fahrenheit Thermistor   Celsius Thermistor # Count Adj Count   # Count Adj Count 1 153 521   1 153 601 2 344 1062   2 344 1202 3 816 1604   3 816 1804 4 1245 1875   4 1245 2105 5 1827 2146   5 1827 2406 6 1914 2182   6 194 2446 7 2003 2218   7 2003 2486 8 2048 2236   8 2048 2506 9 2093 2254   9 2093 2526 10 2183 2290   10 2183 2566 11 2274 2326   11 2274 2606 12 2366 2361   12 2366 2646 13 2457 2397   13 2457 2686 14 2548 2433   14 2548 2726 15 2637 2469   15 2637 2766 16 2725 2505   16 2725 2806 17 2812 2541   17 2812 2845 18 2897 2577   18 2897 2885 19 3209 2756   19 3209 3084 20 3577 2934   20 3577 3283 21 3923 3293   21 3923 3681   7756 (Lower Board) Fahrenheit/Celsius Thermistor # Count Adj Count 1 128 32846 2 2048 20039 3 4096 17584 4 6144 16185 5 8192 15180 6 10240 14373 7 11264 14016 8 12288 13681 9 13312 13363 10 14336 13058 11 15360 12191 12 16384 12474 13 17408 12191 14 18432 11910 15 19456 11629 16 20480 11346 17 21504 11058 18 22528 10762 19 23552 10455 20 24576 10132 21 28624 9412 22 28672 8514 23 30720 7161 24 32640 2438

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.