Building Automation Knowledge Base

Issue There have been some reports of problems encountered when LonMaker is installed in locations other then the default directory. These problems can include failure of LonMaker .dll files to register as well as plug-in registration failure. Environment Echelon LonMaker Cause LonMaker is not installed in default directory. Typically this refers to the C:\ drive, but it doesn't necessarily have to. Resolution Restrict the LonMaker installation to the default directory and the default LonWorks folder. Example: C:\LonWorks

Issue Printing a recently modified badge results in an error message: "This is not an active card." Environment ID Works 4.0 I/NET rev 1.1x Cause Making a change to an existing badge, data, or picture. Resolution Any time an existing badge, data, or picture is changed, these changes must be saved to I/NET before printing the revised badge.

Issue Sunrise/Sunset Time Schedules I/NET Seven rev 1.xx and 7780 Lighting Controllers. Environment I/NET Seven 2.30 and lower Model 7780 DLCU Firmware 5.09 and below. Cause There was an issue in I/NET 2.3 and lower where the Time Schedule for Sunrise and Sunset would not work on 7780 Lighting Controllers. Resolution To work around this issue in 2.3, these steps should be followed: Go to the Resident IO Point that is controlling the Lights. Go to the TS Extension and Modify. Add a Start action on #3 at midnight. This would re-enforce the timer to start again. This has been corrected in firmware release 5.10 for the Model 7780 DLCU (Firmware release with I/NET Seven 2.31). To eliminate the issue, and upgrade will be required.

Issue Door Transactions defined in the Door Editor are not dialing back to the host Environment I/NET Cause Only distribution group 1 messages will cause a dial tap to dial out. Keep this in mind if your system is configured to use the 7806x tap to report to a remote host. Resolution Ensure that all doors and reader points use group 1 for messaging.

Issue Someone held a door open and the "Door open too long" did not report the alarm, what could cause this? Environment I/NET Cause If you are running I/NET 2.2x version there could be three reasons for this. In the door editor, there is a new alarm point defined for the "DOTL" that needs to be populated. The other possible cause is, if the door is in the unlock mode, the "DOTL" will not alarm.  The door sense switch is not working correctly. If you are running I/NET 1.xx then the "b & c" answers could be the problem. Resolution If you are running I/NET 2.2x version there could be three reasons for this. In the door editor, there is a new alarm point defined for the “DOTL” that needs to be populated. Connect to the controller Select Edit>Controller Doors Modify the Door Change the DOTL setting to "Alarm"  The other possible cause is, if the door is in the unlock mode, the “DOTL” will not alarm.  Check the state of the doors DO point Change the door schedule so that the door will be locked The door sense switch is not working correctly. If you are running I/NET 1.xx then the b & c answers could be the problem.

Issue I have door points defined in the I/NET system, but they do not show up in the Door Summary page. What is wrong? Environment I/NET Access Control Cause As part of the Access Control database process, before any Door configuration can be done they must be saved within the SQL database, and more specifically within I/NET's Network Configuration. Within the Network Configuration, the Door Names can be different to the Point Names, its these Door Names that are then used within the I/NET Access Control Database. Resolution In addition to meeting all the door point criteria, the points must also have been saved in the Network Configuration Editor before they will appear in the door summary list.

Issue I tried to modify a door point and I/NET gives me the following dialog box explaining that any changes to the door extension will be stored in the SLI. What would cause this dialog box to occur? Environment I/NET Cause If the communication between the SLI and the DPU is currently unavailable, this will cause the dialog box to occur. Please note that once the communications between the SLI and the DPU have been re-established the stored changes will be sent to the DPU. Resolution Select Edit MCU configuration to verify communication failure Not any Red text, as these addresses are offline Troubleshoot and repair physical communications

Issue How long will I/NET 2000 be sold? Is I/NET 2000 still supported? Environment All Revisions of I/NET 2000 Cause The last release of I/NET 2000 was Revision 2.34 which was released in April 2003. Microsoft has announced that it will terminate all Windows® 98 support in 2006. Resolution As of January 1, 2006, support for I/NET 2000 is no longer available. Please review the following Customer Advisory available on The Exchange Download Center which details support information for I/NET 2000. All I/NET 2000 customers should upgrade to the latest revision of I/NET.

Issue The Domain Name serves what purpose for the NPR? Environment I/NET NetPlus Router (NPR) Cause The Domain Name reflects the domain hierarchy. Domain names are written from the most specific (a host name) to the least specific (a top-level domain), with each part of the domain name separated by a dot. A fully qualified domain name (FQDN) starts with a specific host and ends with a top-level domain. For example, peanut.nuts.com. is the FQDN of workstation peanut, in the nuts domain, of the com domain. Resolution This field indicates the name of the internet or intranet domain the NPR is connected to. An example domain name is schneider-electric.com. If the NetPlus Router is connected to a private network, this field may be left blank.

Issue One of the established DPUs is now offline, but the other DPUs appear to be operating except the transactions have stopped coming to the host. Alarms and messages are still working. A DPU restore to the DPUs has been performed. QP has been checked, and the AC files have been repaired.. Environment DPU Cause In AMT, there is most likely a Failure to Download message. Resolution To correct the transaction symptom Go to the data directory of I/NET Look for a file named ACSAVE.TMC Delete it.

Issue Are the 012 NPR’s Broadcast UDP/IP packets utilized by the control network applications? Environment 012 NPR Cause The only Ethernet broadcasts that will be used are standard ARP broadcasts for normal MAC to IP address resolution. The NPR requires a static IP address assignment. Resolution No. The Broadcast UDP/IP packets are NOT utilized by the control network applications.

Issue Is there a specific type of printer used with a 7810 printer tap? Environment 7810 printer tap Cause 7810 printer tap is only compatible with serial dot-matrix or impact printers. Resolution It must be a serial dot-matrix or impact printer. If your printer is parallel, some manufacturers make and sell a serial conversion card.

Issue Is there a limit to the alarms, messages and transactions a printer tap will receive and print? Environment AMT Cause You cannot get them from another link that is Ethernet connected. Resolution It is limited to alarms, messages and transactions that originate on the same controller lan as the printer tap.

Issue NPR loses the program when AC power is Removed Environment I/NET NPR Cause On Board Battery Resolution You can either: Remove the cover and look at the green colored on board battery. It is located on the right side of the lower board, next to the upper board. Replace this battery Use a UPS power supply to prevent AC power loss Replace the device.

Issue Error: "Runtime Error 429.Active X Component Can't Create Object" While Running Exporter Reporter in I/NET 2000 Environment I/NET 2000 Cause OBDC Install Setup program has not been run. Resolution Run the ODBC Install setup program from the I/NET installation CD. \ODBCInstall\disk1\setup.exe.

Issue After Entering Password, an error message appears:"Inetw performed an illegal operation, causing an invalid page fault in mfc42.dll." Environment I/NET Cause Error in the Registry Resolution Warning! Improper use of regedit may damage PC’s operation. Using regedit, delete the tool bars from the registry. The I/NET toolbars are rebuilt automatically. Shut down I/NET Start the registry editor Go to Hkey_Current_User\Software\CSI-Controls Systems International\InetW\Toolbars Delete all Tool Bar entries

Issue Can not physically reach the ASC but the switch settings need to be changed. Environment I/NET Seven MRs ASCs Cause The units have been installed where they cannot be reached, or are otherwise difficult or impossible to physically reach. Resolution The settings can be altered through I/STAT or the Host's ASC parameters Editor. The latest modification to the configuration always takes precedence.

Issue ASC that has stop communicating The site lost and restored messages coming from this controller. ASC has had communication problems in the past. ASC will not take downloads. Environment I/NET ASC Cause These communication errors could result in corruption of the ASC's NOVRAM. Resolution Clear the memory in the ASC by doing the following: Remove power from the unit Set DIP switches 6 through 12 to the "ON" position and restore power. Remove power again. Set DIP switches 6 through 12 to the "OFF" position and restore power. Remove power again and rest the switches to their normal configuration. Perform a ASC update.

Issue I've designed Graphic Pages using a I/NET 2000, 2.XX host, and place them in an I/NET 2000, 1.XX system. Can you move Graphics among different revisions? Environment INET Site Cause Moving graphics among different versions of I/NET Resolution Unfortunately, the answer is no.

Issue Since the introduction of Integrated Access Control and the ability to monitor Supervised Inputs, Technical Support Services has received many inquiries on how to make supervised DI/DA points work in I/NET 7700. Questions range from "Can I run the wire 100 feet or 300 feet? Do I use 1% resistors or 5% resistors? Some of the controllers are more flexible than others with respect to these issues. Since there are many variables which affect the operation of supervised inputs, this document should give you enough information to make DI/DA supervised points work in almost any situation. Environment Supervised Input High Security Areas Cause There are 3 basic categories of I/NET 7700 controllers in regards to how they handle the supervision of inputs. The first group consists of the 7716 PCU, 7718 PCU, and 7756 PCU. The second is the DPU 7910, DIU 7930, and the DIO 7940. Finally the DPU 7920 is in a group by itself. None of the other CSI controllers were designed to handle supervised inputs. What distinguishes these groups is that they require different voltages to change from one state to the next. Resolution The following (Table 1) lists what voltage each controller expects to see at its input terminals in order to report the correct state. 7716, 7718, 7756 7910, 7930, 7940 7920 For 2-resistor supervision: State LOW HIGH LOW HIGH LOW HIGH STATE short 0 2.34 2.5 2.89 0 1.26 3 closed 2.03 3.12 2.89 3.59 1.26 2.94 1 open 2.81 3.90 3.59 4.35 2.94 4.19 0 cut 3.59 5.00 4.35 5.00 4.19 5.00 2 For 1-resistor supervision: State LOW HIGH LOW HIGH LOW HIGH STATE closed 0 2.34 2.50 2.94 0 1.27 1 open 2.03 3.12 2.94 4.15 1.27 3.75 0 cut 2.81 5.00 4.15 5.00 3.75 5.00 2 Table 1 As you can see, the voltage values for the first group (7716, 7718, 7756) overlap from one state to the next. In this case, the point will remain in the current state until its’ upper or lower limit is crossed, much the same as a temperature differential. The various installation guides for each of these DCU types differ as to what value of resistor and what length of wire can be used; but, if the end result of the circuit produces these voltages, the supervised DI/DA will work. Therefore, you can vary the resistor values and/or wire length but these voltage levels must still be achieved. Don’t let the order in which the state descriptions appear in Table 1 mislead you. The order you see in the table is not the order in which the system expects to find them. They should be entered as OPEN-CLSD-CUT-SHRT (in that order) in the State Description editor for a 2-resistor DI/DA point and OPEN-CLSD-CUT for a 1-resistor DI/DA point. For check out purposes, the STATE number can be viewed from the Hand Held Console when displaying the DI/DA point. The state values are 0-3, which are found in the last column of Table 1. Another useful technique for displaying these voltage values within I/NET 7700 is to temporarily assign the input as an AI. The conversion coefficient can be determined using the I/NET 7700 calculator (see Figure 1.). The Equipment counts high is 4095 for the 7716PCU, 7718PCU, and the upper board inputs of the 7756PCU; 32,767 for the lower board on the 7756PCU; and 255 for the 7910, 20,30, and 40. Engineering units low and high are 0 and 5 respectively for all controllers. The value of the point can now be viewed from the screen or the Hand Held Console. 05/23/95 14:21:31 Tue Conversion coefficients Host 00 (shm) Link 01 [020 link] DCU 02 [PCU 7716] Select (Linear Flow) # M B --+------------+------------ 0 0.001221 0 Conversion equation Linear 1 0 0 2 0 0 Equipment counts low 0 3 0 0 Equipment counts high 4095 4 0 0 Engineering units low 0 5 0 0 Engineering units high 5 6 0 0 7 0 0 8 0 0 9 0 0 10 0 0 11 0 0 12 0 0 13 0 0 14 0 0 15 0 0 Press ESC to copy to M & B Figure 1 Keep in mind that the 7718PCU is switchable for the pull up voltage to either 5 or 15 VDC. For the supervised DI/DA points to work properly, jumper J38 must be set to 5V. A simpler approach to ensure a DI/DA supervised point will work correctly is to limit the length of the wire and thus the resistance that the wire adds to the circuit. If you use 1% 1000 ohm resistors(as recommended), the maximum total resistance that your wire can add for the supervised point to work properly is listed below. DCU Type 1-resistor configuration 2-resistor configuration 7716, 18, 56 650 ohms 1250 ohms 7910, 30, 40 300 ohms 400 ohms 7920 325 ohms 325 ohms Table 2 Note: The value for 1 resistor configuration should be within +/-10 ohms and 2 resistor configuration should be within +/-20 ohms to account for resistor tolerances. These values include both conductors of the wire (shorted together at one end and measured from conductor to conductor at the other end). They allow for (in the case of 2-resistor supervision) the short to be detected at any point on the wire (all the way out to the contact). These are the maximum resistance values and the actual resistance should be kept as low as possible. These values were calculated using the voltages in Table 1 and assume that the supervision resistors are exactly 1k ohms. The values for the first group take into account the overlap of voltage levels between states and are intended to avoid those zones. These values might lead one to believe that a supervised DI/DA point can be wired with ten or twenty-thousand feet of wire. This is not the case due to the noise which wire can pick up and make the input unstable. So the distance should be kept as short as possible.