Building Automation Knowledge Base

Issue How to change the IP address in the EC/ES software when it is grayed out. Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Central (EC) and Enterprise Server (ES) Building Operation WorkStation Cause The EC/ES IP address is grayed out in the Network Tab of the Server Properties and cannot be changed.  This setting is only used to view the IP address that the server is currently using - typically the IP of the network interface card of the PC running this.  To change this setting it must be done through the Communications TAB of the server as detailed in the resolution.  Resolution EcoStruxure Building Operation 2.0 and above EBO 2.0 and above now supports multiple NIC configurations, see 2.0.1 Release Notes for details, in particular, the following note.   Note: That from 2.0 the server will still listen for incoming requests on all network adapters so this setting is only used for choosing which communication settings that the server will use to communicate with child servers. This allows other IP protocols on different networks, e.g. BACnet, Modbus, etc. to communicate with the Server.    It is now possible to select which network adapter the Enterprise Central and the Enterprise Server use.  See the following WebHelp Topic Configuring Network Interface Card for an Enterprise Server or for an Enterprise Central StruxureWare Building Operation 1.9 and below  When the IP address of the computer changes the ES will automatically update the "IP/DNS Address" in the Properties, Network tab. If your computer has multiple network connections, ensure that the Network Interface Card (NIC) to be used for the SmartStruxure network is set to be at the top of the list in the Adapters and Bindings. Go to the computer's Control Panel > Network Connections Select "Advanced, Advanced Settings... " from the menu. In the "Connections:" section, select the Network Connection to be used and press the up arrow to move it to the top of the list. For Windows 7 / Server 2008 See the following link on how to change the order of protocol bindings: How to change the network connection priority in Windows 7 For Windows 8 and beyond, please refer to Adapter priority setting unavailable in Windows 10 In addition to the ES Network Properties, there is also the Communication tab in the ES that lists all of the Server IP addresses in the system. If these need to be changed this can be done by selecting the server and clicking on the "Show/ Hide Communication settings" button circled in red below.

Issue Various webstation or TGML issues Environment StruxureWare Web Station Vista Web Station Cause Java script may be causing problems with Webstation.  Resolution   How to turn on Java Debugging: Open Control Panel Select Java Chose the advanced tab Expand Debugging and check all boxes Expand Java console and select Show console When future errors occur you can capture the errors from the java console If you do not wish to have the console pop up, you can change the Java console back to Hide console and access the logs at this location:  C:\Users\CURRENTUSER\AppData\LocalLow\Sun\Java\Deployment\log

Issue Belkin Bluetooth adapter (F8T01n) on WIN 7 32-bit computer won't connect to MNB-ROAM-IA. Environment PC with Windows 7, 32-bit operating system Belkin Bluetooth adapter, model # F8T016 - F8T017 MNB-ROAM-IA WorkPlace Tech 5.x, configured for BACnet/ MSTP communications with MNB-ROAM-IA Cause The instructions for installing the Belkin Bluetooth adapter as documented in F-27578, TAC I/A Series ROAM-IA Quick Start Guide, "Windows XP-Specific Instructions for Bluetooth Installation", do not apply to installing the adapter on a computer with the Windows 7 operating system.  The procedure is substantially  different in "look and feel" on a Windows 7 computer than on a Windows XP machine - the instructions for Windows XP are not much help on a Windows 7 installation. Resolution The following series of screen captures will illustrate the procedure for installing a Belkin Bluetooth adapter on a Windows 7, 32-bit machine. 1. According to the Belkin FAQ shown, "Most Belkin Bluetooth USB adaptors install automatically without any extra software on Windows 7. Simply plug the device into a spare USB Slot. Windows 7 should automatically recognize the device and install the necessary drivers and software."  This was the case on the laptop PC tested, a Dell Latitude E5500. Screen prompts indicated that the drivers were loaded successfully, and the device was ready to use. 2. Open the Device manager, and there will be a folder for Bluetooth Radios. Expand the node, see the Generic Bluetooth Adapter. 3. Switch on the MNB-ROAM-IA. A Bluetooth icon will be added to the Windows Toolbar. 4. Click on the icon to bring up a menu. From the menu, select "Add a Device". The wizard will search for Bluetooth devices within range, should find the tac-RoamIA:nnnnnnn, where nnnnnnn is the serial number of the MNB-ROAM-IA. This should match the label on the back of the MNB-ROAM-IA 5. Pressing the "Next " button will bring up the "Select Pairing Option" screen. 6. Select the middle option, "Enter the device's pairing code", and press "Next". This brings up the following screen.  Type the pairing code "tac" in the box. The code is case-sensitive, must use lower-case as shown. 7. When the MNB-ROAM-IA has been successfully added and paired, the wizard will display the status. 8. Click on the hyperlink for Devices and Printers to verify that the device has finished installing properly, as follows. 9. In the Windows Device Manager, a Bluetooth Radios folder should be displayed. Expand the folder to see the Generic Bluetooth Adapter. 10. Right-click on the Generic Bluetooth Adapter, go to its Properties, Driver tab. The driver shown (6.1.7600.16385) was installed when the adapter was first plugged into the USB port   11. In the Device Manager, expand the ports folder, and two "Standard Serial over Bluetooth link" ports are shown, COM15 and COM5 12. Use the port with the lower number in the WorkPlace Tech communications setup for the MNB-ROAM-IA. In the example shown, COM5 is selected. Press the "Test and Configure Connection" button. 13. When communications are successfully established, the blue LED on the MNB-ROAM-IA will be ON continuously.

Issue Group object log viewer shows gaps in graph when viewing ExtendedLog data. Environment Continuum Cyberstation Group object Cause The Group Graph Logviewer can support up to 20000 data values being plotted at the same time, anything beyond this you will receive dropped blocks of data. Resolution This was increased to 40500 in Continuum v1.94. If you are plotting more than 40500 total data points then you may see this problem where some data is dropped. Unfortunately this is a limitation of the Logviewer control and it cannot be increased beyond this. Reduce the number of data points being plotted by reducing the time being viewed or the number of objects being plotted on the same graph. Using the Report object to graph this data may be another alternative.

Issue What are the locations where Controller configuration data is saved? Environment Continuum Cyberstation Continuum Controllers Cause Unsure as to where controller configuration information is stored and how to clear/reset this information if required. Resolution There are a number of different locations that a controllers database (configuration information) is stored - there are four locations for a BACnet controllers database and three for an Infinity controller. 1. Continuum SQL Database - Infinet tree In Continuum Explorer, this is where the controller is originally created as a Device object under a Network Folder and commissioned into the Database. This is the location where objects (inputs, outputs, programs, etc...) are created. When creating a new object, it is created in both the SQL Database and also sent out to the controllers database at the same time. The controllers information stored in the SQL Database can be sent out to the controller at any time by performing a reload of that controller (right-click Device object, Send to controller). This information can be removed from the database and the controller by deleting individual objects or by deleting the entire Device object. If the Workstation where this delete was performed is online to the field devices then the same object(s) will be removed from the live controller in the field as well as from the SQL Database. If the Workstation is offline to the field controllers  (Workstations can be taken offline for offline editing) then this delete is only applied to the objects in the SQL Database – the objects will still be located in the controllers though, creating a mismatch between the two until the controller is reloaded. 2. Controller RAM This is the active location of memory on the controller where the running database resides. On most controllers there is a backup battery that keeps this RAM alive with a trickle current when there is no power to the controller. When the controller is powered up it first tries to load its active database from RAM - this is the most current backup. The database in controller RAM can be cleared by pressing the Reset button on the Runtime tab of the controllers Device object in Continuum Explorer. 3. Controller FLASH This is the backup location of where the controllers configuration database resides. At any time the active RAM database can be saved to backup Flash by selecting "save to flash" from the controllers Device object in Continuum Explorer. This then makes an exact copy of the database in RAM (excluding point values) that can be restored at a later date either manually or automatically if the controller reboots and their is no valid database in RAM. For Netcontrollers and bCX's, this database saved to Flash can be deleted from the controllers configuration page (configuration webpage) select Clear Database Backup and then commit changes to controller. If the controllers webpage cannot be accessed, pushing and holding down the controller's reset IP switch for 30 seconds clears any backup in flash in addition to resetting the IP address and ACC node id to default. Another way to clear a controllers flash is to save a blank controller database to flash. Create a new controller Device object and then save that to flash. 4. Continuum SQL Database - BACnet tree The information stored in the BACnet tree is the BACnet side of our configured Infinet objects. This is the BACnet objects as seen in the controller and as third-party BACnet Devices will see them. When performing a "send to database" on the BACnet side, the Workstation goes out to the controller in the field, grabs all the BACnet objects and exposes them in the BACnet tree so that they can be used within Continuum. These can be deleted from the BACnet tree without harming those objects configuration in the controller or the Infinet tree. To recap:   To Create and save objects to the controller requires a two step process. Step 1: Create Database objects using Continuum Cyberstation. Objects are added to both the active RAM of the Controller and the SQL Database. Step 2: Save to Flash on the Controller. The objects in active RAM are backed up to the Flash RAM. If unsure, the only way to know that the Database in the RAM and Flash is the same as that in the SQL Database is to perform a reload of the Controller and then backup to Flash. Step 3: Send to Controller to reload configuration information from SQL Database to Controller RAM. After reload, redo Step 2 to backup to Flash. To completely wipe configuration information from a controller in the field you will need to clear its active RAM and its backed up Flash. If you want to clear all information of the controller from the field and the SQL Database then you will need to clear the RAM and Flash and delete the Device object from both the BACnet and Infinet sides of the tree. If you want to remove specific configured points from the controller but retain it in the tree, you will need to first delete the BACnet side of the controller from the BACnet tree, then you can delete individual objects (or make changes) from the Infinet tree.  

Issue After an OGC graphic is upgraded to TGML, some images or components are no longer in the desired location on the page. Some images may shift location on the page depending on how TGML performs certain tasks during the conversion. Product Line TAC Vista Environment TGML Graphics Editor OGC Graphics Editor Vista Cause When an OGC graphic is converted to TGML, it is possible for the position of an image to be converted incorrectly. The x,y axis of an image in OGC is relative to the origin on the page (The uppermost top, left corner on the page being 0,0). However, if you have used the Symbols feature in OGC, TGML may group this symbol as a during the conversion. This places the 0,0 axis position at the uppermost top, left corner of the component and not the page. This creates unwanted separation as the x.y position relative to the component moves the image to an undesired location on the graphics page. Resolution Open the new TGML file in the graphics editor Locate the component that has been moved in the object tree Change the top and left position to 0,0 on all s associated with that component. TGML may have created several groups for one OGC symbol and the image under each group will need to change. NOTE: It may be possible to use the find/replace function in the source code to replace all of the unwanted positions at once. You will need to be careful that this number is not being used anywhere else in your code before you save these changes. You may remove necessary code if this number has multiple functions.

Issue When swiping on reader of door 3 or door 4 on one SCU1284, door 1 or door 2 will be open instead. The transaction shows "Reader Exit". Environment I/NET Cause Door 1 or door 2 is set to dual direction entry. So the reader on door 3 or door 4 is regarded as the exit reader of door 1 or door 2. Resolution Set the "Exit Reader" option for the door to "None".

Issue When binding using templates at Release 1.1 the user is presented with the number of objects that were found, this count was missing in Release 1.2 and 1.3 Environment Site with official release 1.2 and 1.3 versions Cause When binding using templates at Release 1.1 the user is presented with the number of objects that were found:      this count was missing in Release 1.2: Resolution The Count feature will be available in upcoming release.   

Issue Using Database Initialization to add a workstation to an existing system results in an error. After inputting all required information on the Workstation dialog, the below error is seen and the Workstation is not initialized into the database. "Failed to initialize workstation" Environment Continuum Cyberstation BACnet Devices Cause Third-party (or our own) BACnet controllers are interfering with the creation of the workstation device object. The BACnet Device ID's are clashing. All workstations require an ID. If you have a BACnet system, in the Device Node ID field, enter the BACnet ID for the workstation. (Each workstation requires a unique BACnet ID number.) It can be any unique ID number between 1 and 4194302. Note: In a BACnet network, this ID is unique for workstations and controllers alike and is vendor-independent Each BACnet Device (including the Continuum workstation's) must have a unique ID that does not conflict with any other device on the same BACnet network.   Resolution You can identify BACnet Device ID's already used within the Continuum Database and then choose one that does not conflict. Create a Listview looking at Device class with a path type of AllPaths. As a minimum add the following columns; Name, InstanceId, NetworkId, NetworkNumber. Run the listview. The list it generates is all of the BACnet Devices defined within your Continuum Database. The last portion of the InstanceId (after the backslash) indicates that Devices BACnet Device ID.   You will need to identify a free number that is not being used and change the Device Node ID value you were trying to use in the Workstation Configuration dialog window. With this new Device Node ID that is not conflicting, you should now be able to initialize your workstation successfully.

Issue My I/A Series R2 UNC station idle time is about 5%.  How do I improve it? Environment I/A Series R2 UNC (410, 500, 510, 520, 600, 610) Cause Station processing was not optimized to maximize the processor idle time. Resolution Run the System Spy by entering http:// :3011/system/spy into browser and specifying the IPAddress of the UNC. When the display comes up, scroll to the bottom of the page and click the 'Reset Counters' link. Wait 45 seconds for the counters to be updated before clicking the link to return to the spy statistics screen. Note the displayed idle time.  If it is above 20% no further action is required.  If below 20%, continue with the steps below to optimize the timing.  Please be aware that these steps are only suggestions.   Increase the cycleTime on the UIEngine Service properties--config screen from the default of 500 ms to a value in the range of 2500 to 5000 ms.  This value controls the update frequency of point values on the WorkplacePro and Graphic screens, both locally and via web browser access.  This timing affects the update rate for points on graphic screens.  Remember that regardless of how fast the update rate is specified, updates will only occur when new values are received from point or device. All LOG objects that have a log interval of greater than 2 minutes should be configured with an execution frequency of "minutely".  In addition, any objects being logged or used in calculations for a logged value, if not being used for other purposes, should be configured for "minutely" execution. Any objects that are involved with passing or using low priority values such as outdoor air temperature/humidify (and using/passing any other low priority value objects) should be assigned an execution frequency of "slower". Verify that there are no "custom program" objects that could be replaced with standard objects or combinations of standard objects.  In any case where the station contains more than the recommended maximum number of program objects, an effort should be made to reduce the number of program objects by as much as possible. Repeat steps 2, 3 & 4, above.  If the idle time is still less than 20% continue with the steps below to optimize the execution frequency time intervals.   Review status screen for the Control Engine service noting the following four sets of corresponding values.  If any of the four "Overruns" counters shows a significant number of overruns, note this fact for use in step 15 below. Compare each of the four "...AverageExecuteTime" values to the corresponding execution frequency value (on config tab) and if the value exceeds 50% of the configured execution frequency note this for use in the step 14. Open the Config tab of the ControlEngineService Properties screen. Referring to the values noted in step 12, the "normal" execution frequency needs to be set to a time value that is at least double the value of the "normalAverageExecuteTime".  If this time value exceeds the setting for the "slower" execution frequency, the "slower" execution frequency should be increased so that it is at least 50% greater than the "normal" execution frequency.  Adjust the fastest and faster executionFrequencies proportionally to the change made in the normal execution frequency.  For example if the "normal" execution frequency was increased from 2 to 5 seconds, the "fastest" execution timer would be increased to 1.3 sec and the "faster" execution timer increased to 3 seconds.  If any corresponding "overruns" counter shows a significant percent of overruns, as compared to the corresponding cycle counter, and you did not already increase the corresponding execution frequency to at least double its original setting, increase it appropriately.  Refer to step 14, above, regarding the suggested changes for the other execution frequencies. Apply the settings, save the station and restart it to force the changes to become effective.

Issue The values from a script program are not showing up in Workstation in the correct format. For example, the values are Integers instead of a floating format that provides numbers down to the decimal. A second issue is that the data type icons are incorrect. The values used by the script program are not functioning because they are being calculated using the wrong units. The screen shot below shows a section of a binding page where the "Blr 1Failed" icon shows the correct data type (digital), but "Blr 2Failed and Blr 3Failed" do not. Environment Workstation Script Editor Cause The type of point and the units can be set inside the script program. This may cause a different format to be displayed in Workstation other than what is expected. When comparing values in a script program it may be required to set units to ensure that proper comparison is done. Resolution Check the settings of the points within the Script program.   Open up the Script program by right clicking on it in Workstation and going to Edit. With the script program open, look at the point and unit types in the Variables window at the bottom. Make sure that these are the desired settings and save the program.

Issue JACE-6 Application Director output indicates error: "Unable to init ndio device at ioPort".  After rebooting the JACE, the I/O modules work for a few hours and then appears to drop offline again. Environment I/A Series G3, JACE-6, IO-16 and IO-34 module Cause The ndio watchdog mechanism is used to return the NDIO outputs to known default conditions if the I/O module detects an issue or fails. When a JACE is booted, the NDIO processor starts and enters a default state.  At the same time, the NDIO daemon starts and establishes communications with the NDIO processor.  The mechanism monitors communications between the modules and the JACE and triggers a watchdog if the processor doesn't receive any messages from the daemon.  By default, this timeout is 30 seconds. Depending upon the NDIO Ping Monitor configuration, multiple resets of the watchdog will eventually cause the JACE to reboot. Resolution Depending upon the overall load of the JACE (other tasks and services utilizing the engine threads) the timeout may need to be increased to prevent a false watchdog condition. The first step is to increase the Keep Alive Timeout property within the ndio Monitor from 30s to 40s. Once increased, monitor the operation to see if this corrects the issue. If this does not correct, the timeout can be increased to 45 or 50 seconds maximum.  In addition, review services and tasks that may be consuming CPU usage and adjust as required.

Issue How to override a block output (DO or AO) in a MicroZone II controller on the ASD bus under a G3 ENC. Environment I/A Series ENC-520 with an ASD bus under it. Network 8000  ASD controller (LIM1, MicroFlow II, MicroZone II, PEM1) Cause Need to document the process for discovering controllers, the blocks they contain, and  adding the block attributes to the G3 station so that the desired points can be over-ridden. Resolution The complete process of discovering a MicroZone, the blocks it contains, and adding the block attribute to the database is illustrated in the following series of screen captures. While the DV of a DO block in a MicroZone II application is shown, the same procedure will work with other blocks in the other ASD controllers. NOTE*     Step 11 is not documented , and is commonly over-looked. 1. The MicroZone II is connected to the ASD bus, but it has not been added to the AsdNetwork in the station yet.   2. Right-click on the AsdNetwork, select Asd Device Manager from the menu.   3. In the Asd Device Manager, the 2 devices that have already been discovered are shown in the upper pane. To discover the MZ2, click on the Discover button at the bottom of the pane.   4. This brings up the Discovery Filter, where the type(s) of controller(s) and their address range(s) can be selected for discovery. In this case, only MZ2s will be searched for, in the default address range of 1 -32. 5. The Microzone II with address = 1 has been discovered by the Asd Device Manager, and "Success" is indicated in the status bar. The device has not been added to the database yet. 6. To add the MZ2 device to the database, click on the Mz2 device in the upper "discovered" pane, then click on the "+ Add" button at the bottom of the Database pane. 7. Pressing the "+ Add" button brings up the Add window, where the attributes of the device are displayed and can be edited.  In this case, the default values are all used. 8. A device object for the mz2_1 has been added to the AsdNetwork and is displayed in the tree on the left side pane. Expand the mz2_1 object, right-click on the "Points", and  select the Asd Block Manager from the Views menu. 9. In the Asd Block Manager, no blocks are shown yet for the mz2_1 device. Click on the Discover button at the bottom of the Database pane to discover the blocks in the MicroZone II controller. 10. When the blocks have been learned, "Success" is displayed in the Asd Learned Blocks status bar, and 25 objects have been discovered.  Expand DO 1 to expose the DV block attribute under it. This is the controller output that will eventually be over-ridden. 11. Click on the DV to highlight it, then press the "+Add" at the bottom of the database pane to add the DO 1 block's DV attribute to the station database. This will bring up the Add screen as shown below. Click OK to add the object. 12. Now the DO1 block and it's DV output have been added to the station database as a Boolean point. In the tree on the left expand the Points folder under the mz2_1 object. Right-click on the DO1_DV point, and select "override" from the Actions menu. 13. The override window is displayed, where the Time and Value of the override can be set. In this case, DO1_DV will be overridden ON (true) for 10 minutes when the OK button is pressed. Note: Entering a time of 0 minutes will result in a permanent override. 14. The block output has been overridden, and is displayed in the Database pane of the Asd Block Manager view.

Issue Values sent from a Xenta 121 FC/HP controller via SNVT bindings are not making it to the receiving controller. Viewing the outbound SNVT on the Xenta 121 shows a value, but the inbound SNVT on the receiving controller is invalid or a default value. Product Line TAC Vista Environment  Vista NL220 LonMaker ZBuilder Cause The Node Configuration parameters are set with a send heartbeat of 0 seconds, which tells the controller to never send an update on the output SNVT.  All Xenta 121 controllers come with a default send heartbeat of 0 seconds, so for them to function in an LNS network where they must send data to another controller, the send heartbeat must be set to something greater than 0 seconds. Resolution In order to adjust the send or receive heartbeat of a Xenta 121 controller, follow these steps: Right click on the controller and go to PlugIns > TAC ZBuilder Plug-In. In ZBuilder, click on the Configuration tab and go to LON > Node. Here the Send heartbeat and Receive heartbeat can be changed. The following nvo values will require the Send heartbeat be set to a value greater than zero in order to communicate with another controller using a SNVT binding. nvoSpaceTemp nvoUnitStatus nvoHeatPrimary nvoHeatSecondary nvoCoolPrimary nvoEffectOccup nvoTerminalLoad nvoEffectSetpt nvoFanSpeed nvoEnergyHoldOff nvoOccSensor nvoRawDOStatus   The following nvi values will default to invalid if they do not receive an update within a specified period of time. For most applications this should be left at zero. If the application must actively poll a SNVT then the receive heartbeat can be set to a value greater than zero. nviApplicMode nviSetPtOffset nviEnergyHoldOff nviFanProof nviOccSensor nviSpaceRH nviOutdoorRH nviSpaceIAQ nviOutdoorTemp nviSourceTemp nviAuxHeatEnable nviSourceFlow nviComprEnable

Issue An Enterprise Server or Automation Server is unsuccessful at sending email notifications to a Gmail recipient.  Email messages from ES are marked as spam by Gmail SMTP service. Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Automation Server (AS-P, AS-B or AS) Building Operation Workstation Gmail Cause Unable to successfully configure the ES to send an Alarm Notification to a Gmail recipient. Resolution The following describes how the ES can be set up to use Gmail for Email delivery. 1. Log into the ES; designate the Sender E-mail address and E-mail Host properties. 2. Create a notification on the ES; set the destination E-mail address and type of alarms to be included. 3. Log into destination E-mail account; notice there don’t appear to be any E-mails received. Select the “More” dropdown. 4. Select the “SPAM” folder. 5. Navigate to the E-mail Selection Tab and choose all E-mails from the correct sender. 6. Select the “Not Spam” button and from now on all email notifications will be sent to your inbox! 1. Log into the ES; designate the Sender E-mail address and E-mail Host properties. 2. Create a notification on the ES; set the destination E-mail address and type of alarms to be included. 3. Log into destination E-mail account; notice there don’t appear to be any E-mails received. Select the “More” dropdown. 4. Select the “SPAM” folder. 5. Navigate to the E-mail Selection Tab and choose all E-mails from the correct sender (SxW). 6. Select the “Not Spam” button and from now on all email notifications will be sent to your inbox!

Issue An attempt to flash the firmware in the controller results in error, "The UPREV code could not communicate with the specified controller." Product Line Andover Continuum Environment bCX CX9680 ACX5720 ACX5740 Cause Uprev operation attempted using the wrong flash file. Resolution Re-try the operation using the flash file that matches the model number in the controller. Note that regardless of what the model number reads from the InfinityController editor in CyberStation, the verification is done at the controller level. Do not go by what you see in the CyberStation as this user configured field could have been entered incorrectly. Verify the model number from the controller's web page configuration.

Issue All of the nodes are yellow and when they are clicked on the error below is displayed even though the database is attached to the network (OnNet), the network interface is on the correct channel, and the network interface passed all applicable tests. Environment NL220 Cause When the nodes appear yellow, this means that the LNS database has been corrupted. Resolution It can be attempted to repair the database using the Echelon LNS Database Validator. Follow these steps. If NL220 is still running, shut it down. Go to the Start menu > All Programs > Echelon LNS Utilities > LNS Database Validator. Select the corrupt database in the "Network to Validate" drop down box. Check the box next to Repair Database. Now click on the button called Validate.   If these steps do not repair the database, send the LNS database backup to Echelon support to see if they can correct the problem.

Issue On startup, OPRIF 11.6 does not reach the blue sign-on screen. The program locks up and the computer must be rebooted to terminate the program. Environment DMS OPRIF 11.6 Cause The COM port assigned in OPRIF cannot be located.  As the result, OPRIF remains suspended in a locked state waiting to initialize the COM port. This situation typically occurs when OPRIF was previously used for tunneling.  A virtual COM port is assigned for tunneling to work. Resolution Prior to starting OPRIF, locate the SETDMS.PAR file in the DMS folder on the hard drive.   Edit the file with Wordpad.  The contents will appear as follows:  A=3 B=9600 P=E S=1 W=7 M=N The first variable listed is the COM port number which OPRIF searches to initialize on startup.  Change the number from 3 to 1 (if 1 is the physical COM port on the computer). Save and close Wordpad. OPRIF will now start, initialize with COM port 1, and display the sign-on screen.

Issue When right clicking on the Xenta 100 device in Lonmaker or NL220 the Xenta 100 plug-in is not shown. Environment Lonmaker NL220 Xenta 104-A Xenta 101 Xenta 102 Xenta 103 Xenta 110 Cause The Xenta 100 plug-in is not accessible when launched from the physical device in Lonmaker or NL220 Resolution The plug-ins for all Xenta 100 controllers are only accessible when launched from the controller function block. They are not accessible when launched from the physical device. To launch the Xenta 104-A plug-in in Lonmaker, right click on the function block and choose plug-in:   To launch the Xenta 104-A plug-in in NL220, right click on the function block and choose plug-in:

Issue Want to view and change all COVIncrement values through one listview but the attribute is not showing up in the drop down list. Environment Continuum BACnet AnalogInput AnalogOutput AnalogValue Cause Selecting the wrong object class for the Listview. The COVIncrement attribute is only applicable to the BACnet points AnalogInput, AnalogOutput, and AnalogValue. Resolution In the ListView object, change the object class to one of the following: AnalogInput, AnalogOutput, or AnalogValue. Now the COVIncrement attribute can be selected from the attributes on the Columns tab. Note: If you need to change the COVIncrement values, you can do a mass change by selecting all the ones you want to change from the Listview and then right-click -> Set attributes.