Building Automation Knowledge Base

Issue Received error 'IO Channel number out of range' when creating a door on AC1/AC1A/AC1Plus on an IO module.  The same door configured on a module with a lower IOU number saves successfully. Product Line Andover Continuum Environment Continuum CyberStation Netcontroller  AC Module Cause The IO module is configured with an IOU number that is above the MAX IOU modules supported by the NetController.  Note this is true even if there is only ONE module configured. Resolution Check the IOU module number entered in the door object (1) Check the Max IOU module supported (2)   Delete the IOU module and recreate it using an IOU number at or below the max IOU number supported by the Net Controller.

Issue Memory and System Memory in the AS Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Building Operation Automation Server Premium Building Operation Automation Server Bundled Cause What is the definition of the two different memory types shown in the AS? It is not clearly defined in the documentation. In various places, one can see Memory and System Memory, or even add a column to show.  Resolution For the AS, System Memory is the RAM used by the AS Linux OS. The rest of the memory is what is being used for the processes, such as programs, trends, etc. Memory is the amount of memory consumed by the AS (nsp_servers application), system memory is that used by the Linux OS, however there is much debate about how this is calculated and allocated, so too much should not be read into this, it is there primarily for developers.

Issue BACnet Schedule does not change the Digital Value when the Value attribute of the DV is bound to the Schedule Environment StruxureWare Building Operation BACnet controller B3xxx series. Cause When a user creates the BACnet Schedule object in the b3 controller, if the Default_Value attribute of the BACnet Schedule in the b3 is not configured, the schedule's default value is left as "NULL".   And later on, when the Schedule turns to True, it sets the bound DV value to Active. But when the Schedule turns to False, it tries to change the bound DV value to NULL (as it is the default value of the schedule),  which fails as it is not allowed to set the DV value to NULL.  As a result, the bound DV value cannot be changed and it keeps its previous value "Active" without being able to change it any longer. Resolution Set the Default Value attribute of the BACnet Schedule object from NULL to False as below: - Right click the BACnet Schedule object in the b3 controller and select the Properties. - In the Basic tab of the Properties window, scroll down all the way to the bottom and locate the Default Value attribute. - Click the setup icon on the right side of the attribute, it pops the Default Value window. - Uncheck the Null checkbox and confirm the Value now shows False. - Click OK from the attribute window, verify the Default value is False now, click OK from the Properties window.

Issue Access older I/NET 4.xx *.pag files from page markers in new pages made in I/NET 2000 Product Line TAC INET Environment I/NET 2000 Cause Access older files from new pages made in I/NET 2000. Resolution Go to the Graphic Editor, right click on the page-marker, then select Properties. The next screen is called Graphic Page Marker. In the File Details section check path of the file name of the file extension type If they are not correct then click on Destination page. Select and then open your file. (You may select *.pag or *.gpg files.) Make sure the correction is now in the File Details then click Okay. Save the graphic and close Graphic Editor. Test your page marker. Your page should appear. For conversion up to StruxureWare Building Operation, import the original pag files and convert to gpg. Then using the graphics converter from Building Operation, convert the graphics pages.

Issue Tam32 Illegal closed loop has been detected Product Line TAC Vista Environment Menta Cause Menta evaluates all expressions in parallel every program cycle. Because of this, the output of an expression cannot be looped directly back to the input of the expression. Resolution Any time a logic loop is created in Menta a unitary delay object must be inserted into the loop. These objects are labeled DELB, DELI, and DELR. The type used depends on the data type flowing through the loop. These objects in many cases do not contribute to the logic of control but they are essential for program execution and the application will not compile without them.

Issue As of EBO 4.0.1.86 it is not possible to bind to the "Restart" property of a b3/Infinet Script program Product Line EcoStruxure Building Operation Environment Building Operation - Continuum Interface Cause Unable to bind directly to the "Restart" property of b3 or Infinet Script program. Resolution While the issue may be resolved in a future version of EBO there is a simple workaround. The workaround consists of binding via an intermediate value object.   EXAMPLE: A b3/i2 program (MasterProg) needs to run a second b3/i2 program (SlaveProg).   Create a digital value in the device (ProgReStart), Instead of binding in MasterProg directly to the Restart property of SlaveProg, bind to the value of digital value ProgReStart, then bind the value of ProgReStart to the Restart property of SlaveProg.   Here are the resulting bindings for the intermediate value object (ProgReStart)     The sequence will then be as follows: 1. When MasterProg needs to run SlaveProg, it sets its output binding (bound to the value of ProgReStart) to 1. 2. Upon a change in its value from 0 to 1, ProgReStart will then set the Restart property of SlaveProg to 1 causing it to run.   NOTES 1. Do not use Active/Inactive, it won't work, must use 1/0 instead. 2. MasterProg will need to reset ProgReStart to 0 before running SlaveProg a second time

Issue Need Menta programming that can be used to monitor a pulse signal coming from a water meter, electric meter, or gas meter. Environment Menta Vista Cause A Menta program that can be used to monitor water, electric, or gas metering. Resolution The program below is set up to receive a pulse signal for three different meters. Click the picture of the Menta macro below to download the source file.

Issue Description of the file types and file extensions in Menta. Environment Menta Vista Lonmaker .AUT, .TLG, .MCB, .COD, .XLG, .ESP, .OPE, .OPC, .ESP, .BIN, .CHR, .COD, .XIF, .MTA, OPDOC.GOP, .SPT, .BIN, OPDOC.SPT, OPDOC.TMP, .BPR. Cause Description of the filetypes in Menta. Resolution The following data files are involved when creating a Menta application for a Xenta 280/300/401 device. .AUT Text file with application program source code and data including graphical block diagram. .TLG The trendlog definition. .MCB Macro block file (Group of blocks). .COD “Machine code” file in ASCII format for downloading to the TAC Xenta controller. .XLG The compiled trendlog definition. .ESP Specification file with public signals, their attributes etc. generated by TAC Menta. This file contains input data to the OP configuration tool. .OPE A file with an empty tree, i.e. an OP tree without a specification file. This is the kind of file that is created when the OP configuration tool is run from the program manager. .OPC A mix of an .OPE and an .ESP file. This file is created by the OP configuration tool when it has been invoked from TAC Menta. .BIN Binary file with OP menu tree data for downloading to the TAC Xenta controller together with the .COD file. .CHR National character set file for downloading to the TAC Xenta controller together with the .COD file. .XIF External interface file containing a standardized description of all network variables/ objects of the application program. The .XIF enables binding and communication with LonWorks nodes from other manufacturers. .MTA Menta project file, which can include all files (all types mentioned above except for .MCB and .OPE) related to a certain application. Once a file (for example .AUT or .OPC) has been inserted (saved) in the project file, it can be extracted (opened) anytime as an .MTA file. The .MTA file can be stored directly in the TAC Vista database. Note: The .MTA file can be stored in the TAC Vista database even though it can not be compiled. An .MTA file which is not compilable will not, of course, be possible to download into a TAC Xenta device. It must be correct and compilable before download is possible. In addition to the files listed above, the following data files are involved in the creation of the .BIN file. These files are placed in a specific directory for temporary files. OPDOC.GOP An ASCII file created by the OP configuration tool when the Generate command is executed. This file is converted to an .SPT file, which in turn is converted to a .BIN file OPDOC.SPT Intermediate ASCII file generated from the.GOP file. OPDOC.TMP Intermediate ASCII file generated from the.GOP file. BPR The Network Neighborhood file, describing the TAC Xenta device’s surrounding network nodes and groups. This information was taken from the TAC Menta Technical Manual.

Issue Cannot import lon Lon Device template. Field stays red after browsing in the correct XIF file. Import button does still grayed out after browsing the correct XIF file. Environment StruxureWare Building Operation 1.3 and earlier Cause There is a problem with some regional settings. We have seen this using Turkish regional settings so far but the are probably other languages that will also cause the issue. Resolution Stop Workstation Open control panel Go to Regional and Language Options Change standards and formats to English. Click ok Start workstation again and import the file. Add your devices Close workstation Open Regional and Language settings and change back to your language Open workstation

Issue Are examples available to show how to write Plain English programs and create points for a Modbus RTU X Driver linked to Schneider Electric Power meters? Environment Modbus RTU X Driver Schneider Electric PM700, PM750 Power meters. Cause Requirement for some examples to see how Modbus RTU programs can be written to poll for the data in a 3rd party Modbus device. Resolution The attached example was written by an application engineer in the UK to extract data from the Schneider Electric PM700 and PM750 meters. This example provides the mapping of data for these 2 specific meters, but the polling principle utilized in the Plain English programming can be applied to any Modbus RTU interface Download file here. 

Issue Problem with Continuum controller being used to poll EMon Class 3000 MODBUS RTU Meters The Controller was unable to poll all of the meters installed on the field bus. Environment Continuum controller being used to poll EMon Class 3000 MODBUS RTU Meters Cause When connecting multiple Class 3000 meters to a field bus, ONLY the last Class 3000 meter in the field bus string should have the biasing resistor pack installed. Having multiple termination resistors will load the bus down. Resolution All other biasing resistors should be removed from J17 on meters attached to the field bus. If there is still a problem Change the E-Mon "key2000" to the RS232 protocol. Using the E-Mon Repeater will provide a stronger RS-485 signal to drive their devices. Put the X-Driver on an RS-232 port of the controller.

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 How to setup automatic table truncation on Single-User SQL Express systems. Product Line Andover Continuum Environment Continuum Cyberstation Single-User SQL Express SQL Server 2005 Cause Only the ExtendedLog table is automatically truncated on an Single-User SQL Express Continuum system. The other tables that can fill up quickly and need to be truncated regularly are not catered for (accessevent, activityevent, alarmevent, and errorevent). Resolution IMPORTANT: Make sure to perform a full SQL Database backup before attempting to make any changes to the database. (See Move / Backup / Restore a database on a Single User SQL2005 Express system for details on how to backup your database and, if not already installed, where to get Management Studio from) Use the attached file SQLExpress to add table truncations.zip, to configure your Single-User SQL Express system to automatically truncate these tables when it does the ExtendedLog truncation. After downloading the file, follow the steps below. There are three files in the archive, these need to be copied to your Continuum folder on your Single-User system running SQLExpress as the database engine. LogTruncate.SQL This file is the SQL script that performs the truncation of the four tables (accessevent, activityevent, alarmevent, and errorevent) to the number of days you specify - I have selected 90 days as my default but you can change this to whatever you require for each table. CS_LogTruncate_OneOff.bat This batch file will run the LogTruncate.sql script once when manually executed. You will need to change the server name "PC3" to whatever your PC's name actually is on your system. CS_Hrly - with LogTruncat.bat This is the batch file that will be renamed and replace the existing "CS_Hrly.bat" file currently located in your Continuum folder. This is the same as your current file except it has added the LogTruncate.sql script so that this will now be executed every hour along with the rest. Backup "CS_Hrly.bat" file in Continuum folder by renaming the file to something like "CS_Hrly ORIGINAL.bat". Rename "CS_Hrly - with LogTruncat.bat" to "CS_Hrly.bat", copy into (overtop the existing file if you haven't renamed it) the Continuum folder, and change the server name "PC3" to your PC's name. This should now execute this table truncation script along with the other database maintenance scripts every hour.

Issue The database updates were successful, but one or more nodes were not updated because the node(s) rejected the update, for example due to an authentication failure.  A device encountered an operational or messaging error while its configuration was being updated. Environment LonMaker NL220 Vista LNS Cause This usually means that there is a configuration mismatch between the node and the LNS database.  The LNS will continue to try to update the nodes in the background if the UpdateInterval property of the System object is set to a non-zero value, and you can force a retry with the RetryUpdates method. This seems to have two origins – either in the LNS tool which commissioning or creating group bindings, etc., or in the System Plug-in while trying to download a programmable controller.  It has been observed when creating group bindings when most of the controllers were offline in an onnet connected network. It has been observed while creating and downloading a network in NL220.  All of the correct steps of creating a node, importing a Menta file, updating the network, and downloading were followed.  During a download, an error occurs: “A device encountered an operational or messaging error while its configuration was being updated” (Subsystem: NS, #4031).  After which an additional dummy device was created and inherited the neuron ID of the controller originally being downloaded. It has been observed on an engineering PC using a NIC USB running under Windows Vista which had been reverted to Windows XP.   Commissioning a router in a brand new NL220 Smart Channel results in this error.  Resolution This error occurs because LonMaker/LNS does not receive the device's response in a timely manner during the commissioning process. A new property (AppDevice::Delay) was introduced in LNS Turbo to resolve this issue. This Delay value will be added to any delays calculated by LNS based on the network topology. When this property contains the default value of 0, LNS will not calculate an extra delay for the device. For earlier versions of LNS, the workaround is to increase the channel delay.  Please note that this solution will affect all devices on that channel. Also note that the AppDevice::Delay property is not exposed in the LonMaker Turbo Edition. To modify this property, you must use another LNS application, such as the LNS Object Browser (lnsobjectbrowser.exe located in your LonWorks\bin folder). You can keep track of which devices are up to date using commissioning events, and by reading the CommissionStatus property of each AppDevice object.  If you are receiving persistent update failures on a device, you should re-commission the device with the Commission method. In some cases, switching to a PC using an Echelon LTA cleared the problem. It has been observed that in NL220, an incorrect Device Template was assigned to the Controller during the commission process. The workaround was found by deleting the controller, updating Vista, and then deleting the offending template (in this case Lonm401 assigned to a Xenta 282). The controller then was able to be added with the correct Template. In another case, the controller had to be decommissioned, the controller had to be deleted (including the IO modules if they exist), the TAC network tree inside the system plug-in was deleted, and then the Vista database was updated. A new controller was then added to the page and the commissioning process was started over. All bindings are lost in this process. 

Issue Distinguishing whether an xDriver-enabled commport on a controller is set for Modbus RTU or Modbus TCP/IP. Environment CX9900, CX9940 CX9680 bCX4040 Cause How does one know if the xDriver-enabled commport on a controller is for Modbus RTU or Modbus TCP/IP? Resolution Open the controller editor and go to the Options tab. At a minimum the Modbus RTU XDriver, like all Xdrivers, requires Bit 0 for the commport be Xdriver enabled. The most common example would look like this: Xdrvr Commx: 00000001(####). In the above example x = commport number. The four digit number in parentheses indicates whether an Xdriver file is loaded into the port. If it is 0000 then no Xdriver file is loaded into the port. A number such as 4767 corresponds to "Xdriver Valid" line at the end xdriver XDR file. You can edit the XDR file with a text editor and go to the bottom to see this.   In addition to Bit 0 being enabled for the commport, the Modbus TCP/IP Xdriver requires Bit 3 to be Xdriver enabled.  A common example of this would look like this: Xdrvr Commx: 00000009(####). The 00000009 is in hexadecimal format -  converting this to an 8-bit binary number you get 00001001. The furthest right bit is Bit 0 and the 4th from the right is Bit 3. Both are set to 1 which means they are Xdriver enabled. For a further explanation see page 15 of the linked Modbus TCP/IP Xdriver User Guide.   Note: Since Bit 0 is enabled in both of the above examples, the Modbus RTU Xdriver will work on either. But only the second example will load the Modbus TCP/IP Xdriver.      

Issue How to Logon / Logoff Continuum using a button on a Graphic or Menu page. Environment Continuum Cyberstation Cause Want to be able to Logon Continuum with the click of a button from Graphics or Menu page and also bring up the Logon prompt the same way. Resolution ** DISCLAIMER ** This application is not a supported part of Continuum and is provided as-is. 1. Copy the "Logoff.tx_" file in this archive, here, to the Continuum folder (c:\Program Files\Continuum). 2. Rename the .tx_ file extension to .exe. 3. Create hotspots / buttons as below to call the program with the two available command line arguments; 1 will logon, 2 will logoff. Suggested usage: On the Main Continuum Menu page create two buttons, one for logon, one for logoff. (Pinpoint could also be used for Logoff but would not work for Logging back on - Pinpoint closes when the user is logged off.) For the Logon Button:                 Set control to:        Execute                 Open:                     C:\ProgramFiles\Continuum\Logoff.exe                 Arguments:             1                   Button Text:           Logon   For Logoff Button:                 Set control to:        Execute                 Open:                     C:\ProgramFiles\Continuum\Logoff.exe                 Arguments:             2                   Button Text:           Logoff

Issue Is it possible to rebuild a  Continuum Database from the BACnet controllers in the field? Environment Continuum BACnet Cause The SQL server has failed and there are no acceptable backups of the ContinuumDB to restore once the server has been repaired. The controllers in the field are still functioning and have valid application programming. Resolution Although it is possible to recover the database from the field controllers, the best method of recovery is to have a recent backup of the ContinuumDB and to restore this once the Server gets fixed up. You can load the data from your field controllers into a new Database. Note that all objects will have their name now set the same as the alias, as this is what is stored in the controller. To load the bCX and attached b3's, do the following with a blank database. 1. Create and configure a network folder. 2. Create and configure you bCX1 device object to bring it online in the Infinet view. 3. Right-click on the bCX1 object in the Infinet view and select "Send to -> Database". 4. This will save the controllers database to a temporary dump file on the Workstation then load from this dump file, creating the objects and populating the database. 5. When done, this should have also found all b3's that were defined in the bCX1 and loaded their contents as well. 6. This will load the BACnet objects as well as the Infinet objects. Note: Recreating the Network from the field does not recreate any objects that were stored in Workstations or in folders off the root. These objects; such as listviews, programs, reports, etc...; are not stored in the controllers and will need to be recreated. 

Issue "Invalid attribute property" error when trying to create NetController II in Continuum v1.74 SP2 as Controller Type "9681". Environment Continuum v1.74 SP2 NetController II Cause Trying to create new NetController II device object with a "Controller Type" of "9681". "A Guide to Version 1.74 Support for NetController II and ACX 57xx" states that there is only one NetController model, the CX 9680. Please ignore references to the 9681. Resolution Create the Netcontroller II as  a Controller Type "9680" as stated on page 15 in document number 30-3001-1001 "A Guide to Version 1.74 Support for NetController II and ACX 57xx".

Issue I/NET Cold Case "Card Reader" Mystery. Product Line TAC INET Environment I/NET site with Access Control Cause There are some basic differences between the Indala/Motorola and HID/Dorado card readers. Resolution Please look at the attached link point for this information. Mystery of the card readers.doc

Issue Do extended logs have accurate entries for the spring and fall time change periods?   Environment CyberStation, all Continuum controllers, extended logs, controller logs. Cause What happens to extended log data during time changes? Resolution When the clocks are turned back, log data in the controllers will not be updated for the time interval of the change and therefore that data will not be collected by the extended logs. When the clocks are turned forward, log data in the controllers is logged twice for the time interval of the change and therefore that data is collected twice by the extended logs.   This occurs due to the fact that each log entry in the controller does not consist of a value and a timestamp. The timestamp we see in a report is calculated by the time of the last log entry (LastLogTime) in conjunction with the configured logging interval (LogIntervalSecs). This mathematical calculation saves memory in the controllers. Extended logging is the mechanism most sites use to store, and report on data that is in excess of the amount of data stored in a controller. The extended log engine automatically collects the controller log data before it is overwritten. An added benefit of using extended logging is that the data can be easily backed up via several strategies such as database backups and/or running extended log archiving applications. In the controllers, not only is the memory limited, but the data is stored in volatile RAM, so extended logging is a more robust and long term strategy of collecting and storing the data. Extended logs can be set up on any of the automatic log types (LogInstantaneous, LogAverage, LogMinimum, LogMaximum).  During a period when the clock is moved forward, (for example, 2:00am Sunday March 11, 2012 on the east coast of the US), reports may display timestamps that essentially never existed (in this example 2:00am to 2:59:59am). It is recommended that these entries are simply ignored or crossed out. The period when the clock is moved backward is more difficult, if it is critical that data be captured for the duplicated time. An example is Sunday November 4, 2012. At 2:00am on the east coast of the US the clock is set back one hour. This means that the times from 1:00am to 2:00am occur twice. However, extended log reports will only show one set of data for the reason described above. The reports will show the first 1:00am to 2:00am data; the second 1:00am to 2:00am data needs to be captured separately.  If point log data must be captured for the duplicated timeframe, additional point configuration and Plain English (PE) programming must be used to capture and timestamp the realtime data values for the duplicated timeframe. This involves creating a numeric with a manual log  for each critical point which mirrors the live data value of the affected InfinityInputs, InfinityOutputs and InfinityNumerics. In addition, an InfinityDatetime point with a manual log must be created, one in each controller for each different loginterval of the points being mirrored in that controller. The PE program(s) capturing the point values will write the controller's date system variable to this InfinityDatetime at the same time it writes the live point value, thereby creating a timestamp that will be used for reporting. The last step will be writing the mirrored points and their corresponding timestamps to a file on disk and then printing and/or backing up that file for redundancy.  Click here to download a zip file containing sample dump files and a readme. This is an example of one way to accomplish the above data capture. 

Issue How to view user login/logout information in TAC Vista Workstation Environment TAC Vista Workstation Cause User login/logout information is captured in the events log. Event viewer can be filtered for displaying just the login information. Resolution Sign in TAC Vista Workstation as an administrator. Open the Event Viewer.   Use event filter to filter out unnecessary information Open Event Filter window, and select “General” tab. Under “Type”, leave “Commands” to be checked and uncheck everything else. Under “Object type”, Type “Vista Server” After the filtering, the event viewer will only display user login, user logout, server start up information. Additional Information: Viewing only the login/logout information: In the Event Filter window, select “Event Specific” tab Under “Command”, type “LOGIN” or “LOGOUT   Viewing specific user login/logout information In the Event Filter window, select “General” tab Under “User”, type the user name NOTE: if the user is in a user group, need to include the user group name also. For example, user SYSTEM is also in the SYSTEM MANAGER group, need to type “SYSTEM (User Profile SYSTEM)” in "User" textbox.