Building Automation Knowledge Base

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 When viewing a meter consumption report, the values shown in the report does not match the values in the extended trendlog in SmartStruxure Environment SmartStruxure 1.5 and below Web Reports Cause Generally this will happen if the meter is reset and that time the last value of that meter will set a BaseValue. To calculate the total consumption of the meter we are adding the BaseValue to the offset. This means that the value shown will be the logged value + the offset. In some cases however you would want to completely reset the log and just show the same values that are represented in the extended trendlog. It has been identified, that a defect causing a trend logging a 0 after each restart triggers this reset. Request the latest hotfix for 1.5 from Product Support in order to avoid this happening in the future.   Note: This issue (Defect #26360) has been fixed in 1.6.1 release. Resolution 1. Open "SQL Management Studio" and connect to the database "StruxureWareReportsDB" 2. Locate the log you want to reset using this query: SELECT * FROM tbLoggedEntities 3. Note the ID of the log you want to reset 4. Reset the log using the following query, replacing xxxx with the ID of the log DECLARE @id INT SET @id = xxxx UPDATE tbLoggedEntities SET BaseValue = 0 WHERE ID = @id UPDATE tbLogTimeValues SET FloatValue = OdometerValue WHERE ParentID = @id ##WARNING## The above script will reset BaseValue to 0 this may impact on any previous Meter Readings.  Please contact Product Support to discuss this if you have concerns before applying this script.

Issue Search for all inputs and outputs in a system that are forced by operator Find IOs that are set in manual override Product Line TAC Vista Environment TAC Vista Workstation Cause Need to find all Inputs/outputs that are set to Forced by operator (manual override). Resolution In Workstation, right click on the Lonworks object and select search. In type of devices or objects select Analog/Digital input and/or Analog/Digital outputs.     Select property value 'Forced by operator' and Select equal to 1.     (To be able to set the property value 'Forced by operator' specify Analog/Digital input and/or Analog/Digital outputs, not just Points in 'type of devices or objects'.)

Issue If the WorkPlace Tech Tool application file has been modified when you attempt to monitor a controller containing that application, blank or incorrect monitor tag values will be displayed. Environment WorkPlace Tech Tool software versions 5.0 through 5.8.2 or 5.8.6 MNL or MNB controller loaded with an application downloaded from WPT Visio 2003, Visio 2007 or Visio 2010 Cause There are two causes: First, the WPT software, release 5.8.3, 5.8.4 or 5.8.5 will modify the application when it is opened making it appear to be different than the previously downloaded application Second, failure to observe the following three constraints, regarding the application .vsd file will make the application file appear different than the application previously downloaded: The application file (.vsd) must not have been modified and/or re-saved in any version of the WorkPlace Tech Software since the application was downloaded. The application file (.vsd) must not have been modified directly in Visio and re-saved. The application file (.vsd) must have been last saved, compiled and downloaded using any version of the WorkPlace Tech Tool software, 5.0 through 5.8.2 or 5.8.6, running in Visio 2003, 2007 or 2010.   Resolution An application downloaded to an MNL (or with the compatible WPT version, MNB) controller can be monitored provided that the application .vsd file has not been modified or re-saved after download and that the current version of the WorkPlace Tech Tool software, versions 5.0 through 5.8.2 or 5.8.6 (not versions 5.8.3, 5.8.4 or 5.8.5)  is being is being used with a compatible version of Visio (2003, 2007 or 2010). NOTE: For MNB controllers this applies only to WPT versions 5.7.0 through 5.8.2 and 5.8.6 as the earlier versions are not compatible with MNB application development.

Issue The value of DateTime will different depending on how the variable is declared Differences between DateTime declared as a local variable and as input, output or public in Script program Product Line EcoStruxure Building Operation Environment Building Operation WorkStation Script Editor Cause Local and bound variables will initialize differently Resolution Local DateTime variables are local and known only to the Script program or function, and are initialized to the current local date-time value of the sever in which they  execute. Binding variables, including Input, Output and Public variables, are not effected by the Script engine by default. The EBO system uses the 1/1/1970 date as default and the Script simply uses that. If a different initial value is required then one can be set in the script

Issue "No license available" message appears some while after having logged in to Webstation. Product Line TAC Vista Environment Vista 5.1.6 Windows 2008 Server Internet Information Services (IIS) IIS 7.0 or higher Cause This is most likely due to a corrupt IIS installation. Resolution Reinstall IIS Reinstall Webstation The steps for this are outlined in Problems installing Vista Webstation 5.1.5 or newer.

Issue When reloading a Net Controller II you receive an OMS error. A send to database doesn't complete Environment Continuum 1.92 Windows XP NetController 1/II Cause Programming Busy Controller Resolution First Method: Go to off line editing. Export the programs and save them to the desktop. Delete the programs. Go onLine. Reload the controller. Go to off line editing. Import the programs for the saved export file. Go onLine. Reload the controller. Second Method: Go to off line editing. Web over to the NCII  http://ip-address Select  "Clear Database Backup" Commit Changes. Go Online. Reload the Controller. Note: At times if the reload is still not working and is failing on certain objects, reloading class by class allows the reload to go through. Delete programming half of the code at a time to find out what code is causing the issue by process of elimination. Use a laptop with wireshark installed and a hub and connect to the NC directly and try the reload or send to db and examine the capture. Replace the controller and see if it works, if so, the controller may need to be permanently replaced.

Issue As a last resort when a Cyberstation is offline or there are difficulties connecting to a database, it is necessary to change the Workstation Initialization fields using the Windows registry. Environment Continuum Windows XP Windows Vista Windows 7 Windows Server 2003 Windows Server 2008 Cause Partial objects in a database and registry entries occasionally get out of sync. Resolution Caution! Editing of the registry can be potentially dangerous, make sure someone who is familiar with using regedit completes this procedure. It is best to get a restore point of the Windows PC, if the version allows, prior to taking the following steps. Shutdown Cyberstation From Windows, Start> Run> Regedit Expand the hives(folders) to HKEY_LOCAL_MACHINE\SOFTWARE\Andover Controls Right Click on Andover Controls and select export, name the file and save. (This file can be used to restore the original settings of this branch) Expand the folder to HKEY_LOCAL_MACHINE\SOFTWARE\Andover Controls\Continuum\Settings Double click on Workstation Name (Change this to the name required Ex. WS1) Double click on Network Id and select decimal (Change value data to the number needed Ex. 192) Double click on Device Node Id and select decimal (Change value data to the number needed Ex. 192) Double click on Container Name (Change this to the name required Ex. WS1folder) Close Regedit Go into database initialization and select Workstation and you will now see those settings there. Go to the database tab and enter in the password for andover97 and click Ok. If the database initialization screen comes back(resolves to the database)with no errors, then this new instance of the Workstation was successfully created in the database. Launch Continuum Note: On a 64- bit system the registry location is slightly different. HKEY_LOCAL_MACHINE\SOFTWARE\WoW6432Node\Andover Controls\Continuum\Settings   Continuum queries to get some of the Workstation Initialization parameters (Comments in parenthesis are not part of the query) select  * from device  (Device is the table name, uiname is the column where the Workstation Name can be found) select * from container (Container is the table name, uiname is the column where the Folder Name can be found) select * from device (Device is the table name, networkid is the column where the Network ID can be found) Device ID is not available, but is often the same as the Network ID

Issue Receiving "Deny Entry Sched." (Schedule) transaction message for all individuals on a single Interface (SLI). Receiving "Deny Entry Sel." (Select) transaction message for all individuals on a single Interface (SLI). Product Line TAC INET Environment I/NET Seven Traditional Elevator Control Cause In traditional elevator control, the Reader (Door Point) must have a schedule assigned for the Group / Individual to allow access to the Lift (reader) itself. Then in Floor Maps you can allocate access to the individual Floor Points. In the floor mapping you must also remember to allocate the associated floor points otherwise the Individual is not Scheduled to have access to the floor (Hence a Deny Entry Sched message is received). Recommendation is to migrate sites to Extended Elevator Control which makes this process much simpler. For details of this refer to Extended Elevator control (Step by step instructions). Resolution Under Access Elevators check that the Floor mapping is correctly set for each Floor DO point. If no DO 's are selected for that particular Tenant Schedule, the individual will receive a Denied Entry Sched when attempting to gain access to the floor. Deny Entry Sel (Selection) is received when the Elevator Reader is not selected for the Tenant / Group or Tenant / Individual. A schedule (Group or Personnel) must exists on the reader (door ) point for the Group or Individual in question. A list of all Event messages, and their descriptions, received in AMT is available in AMT Event message definitions.

Issue The Application Director output window displays an Engine Watchdog Timeout by issuing a thread dump and displaying App Failed.  This condition can occur when installing an upgraded station, after a reboot of the existing station, or during normal station operation. Environment I/A Series G3, Niagara Cause The software watchdog mechanism is designed to periodically report the station's engine cycle count to the platform daemon.  The main purpose is to detect and restart a "stalled" station when the control engine is believed to be in a deadlocked condition.  If the station’s engine cycle count stops changing and/or the station does not report a cycle count to the platform daemon within this defined period, the platform daemon causes the VM to generate a stack dump for diagnostic purposes, then takes the action defined by the Engine Watchdog Policy. Depending upon station operation, the watchdog timeout may need to be increased to compensate for transient conditions where the NRE engine thread is temporarily busy during a single execution cycle.  These conditions include simultaneous execution of multiple objects or point extensions that occur on the same time interval, archiving of log history, custom objects, etc. during normal operation.  The default timeout is 1 minute. Resolution Tuning may be required (increase of the default watchdog timeout value). Open the running station, expand Config, expand Services, right click PlatformServices - View - Platform Service Container Plugin, locate the Engine Watchdog Timeout property.  Increase the value by 30 second or 1 minute increments and monitor controller operation (adjust as required).  If the condition continues, contact Schneider Electric Product Support for further assistance. Watchdog policy selections include: Log Only — Generates stack dump and logs an error message in the system log.   Terminate — (Default) Kills the VM process. If “restart on failure” is enabled for the station (typical), the station is restarted.   Reboot — Automatically reboots the host JACE platform. If “auto-start” is enabled for the station, the station is restarted after the system reboots.   Engine Watchdog Timeout — Default is 1 minute, and range is from 0 ms to infinity.

Issue When sending BACnet devices to database the operation does not return an error but NO objects (or only some objects) are created in the DB. Inspection of ACCTrace shows the following... In the case at hand the device had 28 objects which the system identified correctly as seen below, but trying to add each object to the database resulted in error inserting the object in the dictionary. Error inserting a row into the object dictionary. [Microsoft][ODBC SQL Server Driver]Maximum stored procedure, function, trigger or view nesting level exceeded (limit 32) Product Line Andover Continuum Environment CyberStation Cause The ContinuumDB's recursive triggers property has somehow been changed to ON (1) from its default of OFF (0) The following query can be used to determine what the value of the property is using SQL Management Studio select DATABASEPROPERTYEX ('ContinuumDB', 'IsRecursiveTriggersEnabled) Resolution Close all Continuum workstations Reset recursive triggers to its default of OFF with the following query using SQL Management Studio ALTER DATABASE ContinuumDB SET RECURSIVE_TRIGGERS OFF

Issue Cardholder Nickname field is showing "Nickname" instead of data entered into 2nd cardholder when previewing badges. Product Line EcoStruxure Access Expert Environment Badge preview Nickname field Cause In Access Expert the cardholder Nickname field must have unique data within the database Resolution The Nickname field must have unique data for all card holders within an Access Expert database. Do not enter 'admin' in that field for one card holder and again for another cardholder.  What is the intended use for this field? In one case, the intended use was for Job Title and a better solution was to create a Custom Attribute of Job Title instead and to place that field in the badge layout. That way the field can have the same data in it for multiple cardholders.

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 1. Cyberstation PC Windows Application Event Logs showing SQL errors about being unable to allocate space for each of the event tables. Similar to the below errors. Could not allocate space for object 'dbo.AlarmEvent'.'PK_AlarmEvent' in database 'ContinuumDB' because the 'PRIMARY' filegroup is full. Create disk space by deleting unneeded files, dropping objects in the filegroup, adding additional files to the filegroup, or setting autogrowth on for existing files in the filegroup. Could not allocate space for object 'dbo.ExtendedLogReservation'.'IDX_EXTENDEDLOGRESERVATION' in database 'ContinuumDB' because the 'PRIMARY' filegroup is full. Create disk space by deleting unneeded files, dropping objects in the filegroup, adding additional files to the filegroup, or setting autogrowth on for existing files in the filegroup. 2. Controllers are online but unable to modify existing objects or create new ones. In addition; all events were not being logged to the database. This was seen by reviewing the AlarmEvent, ActivityEvent, AccessEvent, AlarmEvent, and ExtendedLog tables not having any new events being recorded at all. reviewing the distribution properties after performing tasks in Continuum showed no entries at all. Normally, user events initiated from the Workstation are shown in the distribution properties window as they occur. Product Line Andover Continuum Environment Continuum Cyberstation SQL Server Cause 1. One of the Database files is set to not grow with Autogrowth set to none. This stops any new data from being able to be entered into the database. One example of this is when the ContinuumDev file was modified by the end-user to inhibit its growth by changing this setting to none. Check all of the following databases files (both the DEV and LOG file) to ensure that they are all set to either autogrowth or to an adequate restricted value so that they are able to write new entries. ContinuumDB MSDB TempDB   2. The disk where the database resides does not have enough available disk space. Resolution 1. Change this database file growth setting to "by 10MB, unrestricted growth" or to an adequate restricted value. Use SQL Server Management Studio Express, see Move / Backup / Restore a database on a Single User SQL2005 Express system on where to get this if it is not already installed on your SQL Server. It is highly recommended to backup the ContinuumDB before attempting any changes to the database, steps on how to do this are in the above article. Start up SQL Server Management Studio, or in my example, Management Studio Express. Log in with your SQL SA password or windows administrator. Expand the server tree, expand the Databases tree. Right-click on ContinuumDB and select "Properties" from the menu; this will show the Database Properties window. Select the Files tab on the RH side of this window and you are now where you need to be to check the Autogrowth setting.   2. If the problem is due to disk out of space your options are; a) Make room on the disk, b) Shrink the ContinuumDB,  c) Install a larger disk in the machine.

Issue I/NET Seven System Log On Environment I/NET Seven Site Cause Knowledge on I/NET Seven System Log On steps Resolution If you are logging on to the system for the first time since rebooting, restarting the driver, selecting System Log Off, or using the Signoff on Quit option, you must enter your host password. Note: You can configure I/NET to allow operators to logon simply by swiping their key/card at a Wiegand reader connected to the host workstation. Refer to User Enrollment and Auto-logon for more information. If the system is not already displaying the Log On prompt, select System Log On from the main menu. Type your Operator Name. This name can contain up to 30 characters. The following characters cannot be used within the Operator Name:" / \ [ ] : ; | = , + * ? <> The default operator name is "tac". If the system has just been installed and no operator names have been assigned, this default name should still be available. After operator names have been defined, you may wish to remove the default operator name to prevent unauthorized users from gaining access. Type your password at the prompt. This password can contain up to 127 characters. All keyboard characters are valid for use within this password. The system displays an asterisk for each character you type. The default system password is "dacs". If the system has just been installed and no other host passwords have been assigned, this default password should still be available. After host passwords have been assigned to all authorized users, you may wish to remove the default password to prevent unauthorized users from gaining access. Select OK to continue. Caution: The database server should not be shut down while I/NET is running. Shutting down the database server drops all existing connections to the database, and can result in corrupted data displays. (Only users with administrative privileges on the workstation can stop or start the database server.)

Issue If a binding variable is commended out in the program when the line is put back the binding is gone. Consider the following program... TheOUT3 binding variable is commented out... If the comment is removed and the line restored, the corresponding binding is NOT restored. Environment Workstation Script Cause Documentation Resolution This is functioning as designed, if the binding variable is removed in the program code, the associated binding is removed to avoid leaving an orphan binding. When the comment is removed and the binding variable is put back, you will need to re-bind it as SBO does not keep track of deleted bindings and can't automatically restore it.

Issue TGML Graphic Alert: TypeError: Cannot call method "getAttribute" of null (cmd#52) TGML Graphic Alert: TypeError: Cannot call method "setAttribute" of null (cmd#52) Environment Vista 5 TGML Graphic Cause A Javascript tag in the TGML file has attempted to perform an action on a null pointer.  Oftentimes this is due to a component being deleted or renamed without realizing that a script elsewhere in the graphic was pointing to it. Resolution Determine which script tag is generating the error. When did the error occur?  When the page loaded?  When a value changed?  When the user clicked?  Did it happen once or multiple times?  These questions can help you narrow down which script has thrown the error. Save the graphic under a different name.  Delete portions of the graphic until the error clears.  The component that was removed holds the offending script. The cmd# syntax is indicating which line of the script has the error.  Launch the script editor by clicking the "..." button next to the script Content attribute.  In this example, go to line 52 of the code. The text in quotes tells which method was being used.  In this example "getAttribute."  Investigate what is in the parameters of the getAttribute() function.  Verify that object exists as defined. Edit the script to point to a valid object, rename or restore any deleted object.

Issue The Vista administrator user account (system manager) is created; however, that account does not have administrator rights such as add/edit/delete any user, cannot change time schedules, graphics, etc. Product Line TAC Vista Environment TAC Vista Workstation 5 Cause When adding a system manager account in Vista, that account also needs to be added into the administrator group ($Administrators). If the system manager account is not listed under the administrator group, it will not be able to behave as the administrator. Resolution Maker sure the user account is set as a “System manager” Log into Workstation as an administrator and click on the root project folder in the left panel, right click on the user account in the right panel, and then select property. Under “General/Authority level”, it should say “System manager”. If not, change to “System manager”.                             NOTE: If the textbox is grayed out, it means the current logged in account does not have the permission to make changes to that user account. Please read Cannot edit or delete a user account in TAC Workstation to add the control rights. If this articele fails also, please go to step 2.   Click on the root project folder in the left panel, and right click on the “$Administrators” in the right panel, then select “Properties”. Under “Users”, all administrators should be listed here. Make sure the desired user account name is listed. If not, use “Add” function to add the user account. If the text box is grayed out, log in as one of the system manager account listed under “Users” to process this step.                  NOTE: If all system managers listed under “Users” are no longer available. Please contact product support to unlock the database.

Issue Essex Pin Pad Reader Programming in I/Net Seven. Product Line TAC INET Environment Any Windows OS Version and I/Net Seven Version Cause Need to program an Essex Pin Pad reader in I/Net Seven. Resolution Here is the link to programming the Essex Pin Pad Reader Essex Pin Pad requires the site is not using Large Numbers The Essex Pin Pad is for site which wish to use Pin only for entry. Not Pox Card + Pin or Prox only. For information on a Prox card access which includes Pin Pad see HID PIN Pad reader for I/NET Part Number. For a higher security Pin Only option comparable to the Essex see Code-Guard Scramble Pin Pad Reader Programming.

Issue Is the Continuum Cyberstation a B-OWS (BACnet Operator Workstation)? Product Line Andover Continuum Environment Continuum Cyberstation BACnet Cause Can't find reference to Continuum Cyberstation being defined as a B-OWS. Resolution The Continuum Cyberstation is a B-OWS and complies with ANSI/ASHRAE standard 135-2004.  However, the Continuum Cyberstation has not been BTL tested, please see the Schneider Electric BTL Listing of Tested Products.    The following selection is taken from the Andover Continuum Family of User Interfaces document describing Continuum's Cyberstation capabilities. Native BACnet B-OWS CyberStation communicates with the BACnet devices using BACnet/IP in strict accordance with ANSI/ASHRAE standard 135-2004 and is designed to function as a BACnet Operator Workstation (B-OWS) and BACnet Broadcast Management Device (BBMD). The CyberStation can communicate to all Andover Continuum BACnet Devices as well as any third party BACnet Device on the BACnet network.

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.

Issue Import of BACnet/IP device is missing Device ID value. The device is indicated as offline and will not communicate. Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Automation Server Building Operation Automation Server Premium Building Operation Automation Server Bundled Building Operation Edge Server - Standard Cause A device instance number is not preserved in an export. An imported BACnet device must be associated with a device.  Resolution Use the Associate with Device option on the BACnet/IP device object, refer to: Associating a BACnet Instance Number with a Device (se.com). Specify the device instance number.