Building Automation Knowledge Base

Issue Space temperature sensor calibration using the Xenta 102-AX plug-in Environment Xenta 102-AX Plug-In Cause The space temperature of a 102-AX can be calibrated in three locations:   M/STAT, service menu OP > CSS, resolution 0.1° Vista Workstation, VAV_Controller.UCPTvavSelection.CSS, resolution as entered Xenta 102-AX Plug-in, Browser tab > UCPTvavSelection, resolution 1° The first two allow resolution at least as fine as 0.1° step sizes on the offset.  The LNS plug-in, however, by default only allows whole integer 1° step sizes. Resolution Read to the end before you try this.  NOTE:  It is recommended to make this fix prior to opening the plug-in on a VAV box that has already had the space temperature calibrated via the M/STAT.  Failure to do so may result in the desired calibration being rounded to the nearest whole degree. From the Xenta 102-AX plug-in, select the browser tab (or open the LonMaker browser if you wish). Navigate to and expand the VAV controller object and select "UCPTvavSelection.CSS". Past all of the "CALIBR_NOT_ACTIVE" statements, you'll find a couple of numbers - the second one being 32. Raising or lowering this value will raise or lower the space temp by the same amount. But, until now, if you try to enter 33 or 31 you'll find that only even numbered integers are accepted. What to do? Open c:\Lonworks\types\user\TAC\Xenta100.fmt in notepad. Locate line 172 which should appear as UCPTvavSelection#US: text("%m,%m,%m,%d,%d,%d,%m,%m,%m,%m,%m", Change the second "%d" to "%f" and save the file and restart the Xenta 102-AX plug-in. Now you can change that value in finer increments than is necessary.

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 Xenta Time Charts changes when clicking Edit in Vista 4.2.3 Environment TAC Vista 4.2.3 Time Schedules Cause In some cases Xenta Time Charts will change when clicking the Edit button. For example, if you have a time chart running Monday through Saturday and you click Edit the days will change to Tuesday through Sunday. Resolution Upgrade to the latest version of Vista to fix this issue. To work around this without upgrading: Change the First Day of week setting in your registry HKEY_CURRENT_USER\Control Panel\International\iFirstDayOfWeek If you change this to 0, the first day of the week will be considered Monday and editing Time Charts will work.

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 HASP Error when installing Privilege Licenser 2.01 on Windows XP Machine Service Pack 2 Environment Aladdin Privilege Administrator 2.01 Windows XP SP2 Vista IV Licensing Cause On the most recent versions of Windows XP with Service Pack 2 installed, there has been a problem installing Privilege Licenser 2.01. Upon installing the software a "HASP" error occurs. This is caused by the version of HASP on the computer not being compatible with one Privilege Licenser is trying to use. Resolution Aladdin does not officially support Windows XP SP2, but there is a fix that usually fixes the problem. Go to the following url and download the "HASP Device Driver Commandline Installation" https://supportportal.gemalto.com/csm/?id=kb_article&sys_id=f7055f20db6207c8fe0aff3dbf9619cc Download the file to your hard drive and use the following steps to install the fix: Unzip file to root of your C: drive. Go to Start/Run and type in ‘cmd’. In the DOS window type in ‘cd\’ This will take you to the root of the ‘C:\’ drive Type in ‘cd hinstall’ This will take you to the program folder Type in ‘hinstall.exe –i’ A window will pop up and let you know when the file has finished installing. Close out of DOS by typing in ‘exit’ Run setup for Privilege Licenser 2.01 Note: Beginning 2012, PSS will no longer support the Privilege License System. The Tamfs26 Server will be retired along with TAC License Server software. It would be wise to inform the customer of this important information to plan for future upgrade in the event that their site license has issues.

Issue If there is a " in any of the Xenta OP screens, the application will not compile/download correctly. Error message states "ERROR c":\program files\tac\tac menta 4.2.3\temp\opdoc.gop Error in line: xx " Environment Xenta programmable controllers Menta Xenta OP Tree (.dop) Cause The character " is not allowed in the Xenta OP. Resolution Do not use the character " in the Xenta OP tree.

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 Xenta 102-AX Heat cycling off even with rev. 1.11 Environment TAC Xenta 102-AX v1.11 Cause If nvi_applicmode is bound to another device, it will revert to hvac_cool for a split second every time it receives a packet. If the controller is in heat mode, this is long enough for the heat to turn off and the terminal load to go to 0 for about 3-5 seconds. If it is time to change modes anyway, this is not a problem but if the mode is re-enforced periodically, your heat output will turn off upon that period. Resolution There is no need to re-enforce this command, so make sure that the output is set to send ONLY on a change. Make sure period is set to 0.

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 Stroke time (throttling range) on Xenta 102-AX VAV controller Environment Xenta 102-AX Cause The stroke time of the actuator differs when the input power is 50Hz versus 60Hz. Since this is not an Imperial vs. Metric issue, LonMaker or Vista does not automatically change this for you according to your regional settings. Resolution The stroke time for the Xenta 102-AX is as follows: 2.4 seconds / degree rotation (50 Hz) 2.0 seconds / degree rotation (60 Hz)   Assuming the damper stroke is 90º: The default setting for damper stroke time is 230 seconds. This is the approximate stroke time when that AC motor is driven with a 50Hz supply. 185 seconds is the approximate time when using a 60Hz supply. The unit will control space temperature regardless but the damper position which is estimated in software will be off when it is anywhere other than 0% or 100%. This will make the damper more aggressive than the program thinks it is. This could make the calibration efforts take longer since the damper might take longer to stabilize the airflow reading. It is recommend to change the damper stroke time to 185 on any site fed by a 60Hz supply. (Unless the damper travel is other than 90°. In that case, set the physical screws accordingly and calculate a new appropriate stroke time based on the seconds per degree values above.)

Warning Potential for Data Loss: The steps detailed in the resolution of this article may result in a loss of critical data if not performed properly. Before beginning these steps, make sure all important data is backed up in the event of data loss. If you are unsure or unfamiliar with any complex steps detailed in this article, please contact Product Support Services for assistance. Issue Dependencies for Vista Server running as a service Product Line TAC Vista Environment Vista Server Cause The Vista server can run into issues if it starts up before other services. Resolution Ensure that Vista Server does not start up before Aladdin Privilege Server by making some changes to the registry. Select the start menu, select run, and type “regedt32”. Once the program opens you should browse to the following path: HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\TACOS\ The key named DependOnService should by default contain the value RPCSS. To add a dependency to this service just modify the value of the key and add the name of the service you wish to start before this one. In the case of Aladdin Privilege Server just add the text “Privilege Win32 Server” to the registry key. Close the registry editor and the dependency will be visible in the services properties window for TACOS. Note: If you need Vista to start late in the boot cycle but you do not have a specific service dependency, as explained above, then choose one of the services which startup last as the data value for the value "Depends on Service". Services commonly selected are Spooler and Messenger.

Issue Cannot register LonMaker plugins Product Line TAC Vista Environment LNS, LonMaker, NL220 Cause If you are having difficulty registering plug ins in LonMaker then you may have corrupted LNS credits. Resolution To check your LNS credit status, run the LNS Server License Wizard which is found at C:\LonWorks\bin\LnsLic.exe If you run the wizard and it displays the Max Credits at zero and Credits Available as zero as well, then your LNS credits have become corrupted. To correct this, select Next in the Wizard so that it displays the PC Key. The wizard provides a button titled "Copy to Clipboard" which when selected will allow you to paste a form letter into an email or text editor. After filling your specific contact information you will want to check the "No Charge" box and the "Replacement Use" box. Before you send the form via fax or email, you also need to provide evidence that your LNS credits have been corrupted. Select Start > Run > and type "cmd" to reach a command prompt. This command will check the status of the LNS credits: checklic nsseng.exe The output of this command should either be printed and sent with the fax or included in the email to the address or phone number shown at the top of the form letter. You should then receive instructions or an application key to correct the problem.