Building Automation Knowledge Base

Issue Error number :      17040 Error description: Invalid format. (Subsystem: LNS, #40) Any tab except "Status" has some strange values. Trying to view or edit some values results in this error. Environment Xenta 102-AX Plug-in Xenta 104 Plug-in LonMaker NL220 Cause A value inside the device has been set with an invalid value.  It could be through an LNS browser, through an M/STAT or just through some glitch when setting a parameter. Resolution The device will need to be recommissioned using default values. CAUTION:  Recommissioning a device with default values will erase any user defined configuration parameters.  Record all important data for the box:  duct area, airflow setpoints, operating parameters, etc. Right-click on the device in the LNS Management tool.  In LonMaker, select Recommission. In NL220, select Repair. Choose "Manufacturer Defaults" for the initial values.  Click OK. Launch the plug-in again.  The values should now be able to be changed to the desired value.

Issue On a fresh install of LonMaker Turbo, inactivated, the first time trying to open a drawing you may get the error:  The object was not found (Subsystem: LNS, #6) Extensions ‘Echelon_LMW_Demo’ Environment LonMaker Vista LNS Cause If you specify a network name with trailing spaces, the LonMaker tool will report an LNS #6 error (object not found), and report an unexpected error. An object has been requested by name or index that could not be found in the databases.  Typically, this would be a request from a LNS collection object with a bad name or index. It should be noted that this error can also occur in some implicit assignments. For example, if the network interface to be used has not been explicitly assigned to the appropriate property, LNS will continue using the network interface previously assigned to the ActiveRemoteNI or NetworkInterface property, respectively. In such a scenario, this exception could occur even though no explicit assignment has been made, indicating that an implicit assignment maps to an unavailable object. A monitor set may be created while offnet (System.MgmtMode is set to lcaOffNet); however, a monitor set cannot be opened while offnet. Furthermore, attempts to query the MonitorSet.IsOpen property will get the error "The object is not found (Subsystem: LNS, #6)" when offnet Resolution Getting the activation code and activating the install should clear the error.

Issue Migrating from LonMaker to NL220 Environment LonMaker NL220 Cause Changing LNS management tools. Resolution If both Lon Maker and NL220 reside on the PC: Migrating from LonMaker (or other LNS management tool) to NL220, all that is required is the LNS database.  NL220 will recognize the LNS Databases which have already been created in LonMaker. Open the database in NL220. There is no need to recommission online devices, so no credits need to be re-purchased.   If the LNS must be transferred onto a PC that only has NL220 installed: Take a copy of the Folder located in the directory Lm/Db/[name of project]/files Place this folder in C:\NLPrj\[name of project]\files Create a new Project in NL220 Name the project Select 'open an existing database' Browse to the Project path (C:\NLPrj\ ) Select OK. NOTE: Migrating from NL220 (or other LNS management tool) back to LonMaker is a little less seamless because LonMaker utilizes proprietary Visio drawings for viewing the network, and these are not native to the LNS database.  Viewing the network may be difficult with the automatically generated Visio drawings.

Issue Could not initialize the LonTalk stack. Environment LNS NL220 LonMaker Vista Cause Could not initialize the LonTalk stack. Resolution First, close the LonMaker tool, then test your network interface using the LonWorks Plug 'n Play utility found in the Windows Control Panel. Once there, press the "Diagnostics" button and then press the "Test" button. If you get a "Failed" message similar to the following: ------------------------------------------------------------------------------ LonWorks® PCC10/PCLTA10/PCLTA20 Device Driver Version: 2.01 Card Type: PCLTA-20 / LMPA Driver Status:           Number of Free LTA Output Buffers-            Non-Priority: 0, Priority: 0           Loaded Image Size: 16384           Interrupt Count: 17333 ------ Network Interface Node Status ------ ** Failed ** ------------------------------------------------------------------------------ Then go back to the main LonWorks Plug 'n Play dialog and change your NI Application to something other than what is currently selected. Click on the "apply" button and do the test again. Don't forget to change it back to its original NI Application. Remember that the LonMaker tool can work with either the "NSI" or "VNI" NI Application images, although "VNI" is preferred due to higher performance. You may also want to try to "reset" and "restart" your network interface card and driver from the "Diagnostics" window. Once you stop getting the "Failed" message and see the network interface statistics, you should be able to open the network from the LonMaker tool. The following is an example of a successful "Test" result. Some of the counts may not be zero, but that should not be a problem unless it increases rapidly as you test again and again. If that happens, it can be due (most of the time) to one of three problems: wiring connections, excessive noise, or excessive traffic on the network. ------------------------------------------------------------------------------ LonWorks® PCC10/PCLTA10/PCLTA20 Device Driver Version: 2.01 Card Type: PCLTA-20 / LMPA Driver Status:           Loaded Image Size: 57344           Interrupt Count: 20345 ------ Network Interface Node Status ------ CRC Errors:                  [00000] TX Timeouts:                 [00000] Lost (APP) Messages:         [00000] Missed (NET) Messages:       [00000] Most recent error:           0 Reset Cause:                 External ------------------------------------------------------------------------------  

Issue Unable to add points or trends to a 7793 Controller, even after changing the address and redownloading the bin files to it. Applies to 7793, 7716, 7728, 7756 Environment Working on I/Net Seven system. Cause Unable to add points to controller. Resolution Using a HHC (Hand Held Console) plug it into the Com port on the board Select CTRL MEM 0 ENTR, 0 ENTR Hit the Red Reset button and clear the memory of the board. Go to Edit Host Computer, Network Configuration Penetrate the Link Summary, the device will show in the boot state Save it and then close out of this editor. Go to Edit Software Restore Select the device and download the bin file and sav file back to the controller again.

Issue During the boot sequence of a Xenta Server the message "Unmap block xxx at remount" occurs. Environment Xenta 511 Xenta 527 Xenta 555 Xenta 701 Xenta 711 Xenta 721 Xenta 731 Xenta 913 Cause Sections of the flash drive are being declared bad and are being removed from the accessible drive map. This can be a natural pruning process of bad sections due to drive damage or that section exceeding the maximum number of writes. The amount of lost space is: # of pages * 2 bytes All hardware 2 Xenta Servers have 16mb flash drives, so it takes a large number of pages to be lost before significant space is lost and will impact performance of the unit. Resolution If the number of pages is low and is not increasing then the unit should function normally without any additional action. If the number of pages is exceeding 50000 or increasing rapidly, then have the Xenta Server repaired or replaced depending on its age.

Issue MFC error on util.dll on Continuum startup or Continuum won't start when using an Hewlett Packard PC even though Antivirus software isn't installed and the Windows Firewall was turned off during Continuum installation. One of the symptoms of the interference of password protection software is to prompt to save passwords through a form. The Continuum database initialization has passwords, and a form with an image surrounded the database initialization dialog box. This made the dialog box look different than normal, and was the key that it was interfering with Continuum's normal operation. Product Line Andover Continuum Environment XP SP3 Windows Server 2003 Windows Server 2008 Cause HP Protect Tools are installed and interfering with the operation of Continuum Resolution Uninstall HP Protect Tools and reinstall Continuum. Disabling HP Protect and reinstalling did not correct the issue. There is a potential for other protection tools like Norton's password protect, McAfee Security Suite or a number of other password protection software that could interfere with the Continuum install.

Issue How to create a Continuum Cyber workstation Product Line Andover Continuum Environment Continuum Cyberstation / Workstation Andover Continuum Software and Firmware Compatibility Matrix Cause Creation of Continuum Cyber Workstation. Resolution Download the version of CyberStation Software from Exchange and follow the 'Setting Up Workstation Parameters' section of the Cyberstation Installation Guide included in the zip file.  

Issue How to automatically have b3 controller backup to flash. Product Line EcoStruxure Building Operation Environment b3 Script Program Cause Script program syntax is a bit different to how it was done in Continuum, specific details needed on how to set this up.  Resolution This is a sample script program to enable automatic backup to flash when the controller database is different to what is currently stored in Flash. Create the below Script Program in the b3 controller. Make sure to bind both the input and output variables to statusbackup/value. 'bind statusbackupin and statusbackupout to the systemvariable statusbackup/value. numeric input statusbackupin numeric output statusbackupout init: if ts >= 5 then goto checking checking: if statusbackupin = backupneeded Then   statusbackupout = backupnow Endif goto wait1day wait1day: if td >= 1 then goto init

Issue How to convert a B4-920 to a BCX4040 Environment BACnet B4-920 BCX4040 CyberStation Cause How to convert a B4-920 to a BCX4040 Resolution ASCII export the B4-920 then modify the dump file to change from the B4-920 to the BCX4040.  Delete the B4920 from both the Continuum view and the BACnet view in Continuum Explorer. Import the converted dump file into the system.   Reload the new BCX and all it's child objects.  Execute a Find New BACnet Device to pull all the devices back into the BACnet view.  Execute a Send to DB on the BACnet side to pull all the objects in. NOTE:   Another option if you are running version 1.90 CyberStation or greater is to change the model number through the controller editor in Continuum Explorer.

Issue Error during installation of Vista:  "Unable to Locate Microsoft Excel" or may say "Could not find Microsoft Excel which is needed to use Vista Reports." Environment Windows 7, XP Microsoft Excel Vista Cause Vista may not be compatible with the version of Excel that you have installed on your computer or Excel may not be installed. Resolution Download document TAC Vista Compatibility Matrix Use the matrix to compare the version of Vista you are trying to install and the software installed on the machine Correct any discrepancies by either purchasing a different version of Excel for the computer or using a different version of Vista.

Issue Can not connect a SCU controller directly to a Xenta Product Line TAC INET Environment I/NET controllers Xenta controllers Cause No Communication between a Xenta and a SCU controller. A SCU controller can not communicate directly to a Xenta because they speak different protocols. Resolution There must be an interface between an SCU and a Xenta controller, like a 7798C controller for example. The 7798C translates communications from a Sublan to a CLan. It also has a database that keeps track of rules set up by the admin. For a deeper understanding please review Explain and define I/NET Ethernet, C-LAN, and Sub-LAN communication.

Issue Upgraded CX9200 chips and not able to load Bacnet PTP xdriver Environment Continuum Cyberstation CX 9200 Bacnet Xdriver Cause Upgraded chips on CX9200 and cannot load the Bacnet PTP xdriver. Resolution Use the latest Bacnet PTP xdriver version BacnetPTP1.00001.xdr

Issue 1. The Sigma default user name TAC USER does not work with Sigma 4.05 SEB 2. Tried the user access password and could not logon Environment Sigma 4.05 SEB Cause The default user name changed at Sigma 4.05 SEB Resolution From Sigma 4.05 SEB onwards the default user name is SIGMA USER. The password remains unchanged.

Issue Is the I/A Series (Niagara) R2 WorkPlace Pro and Enterprise Server software compatible with the Microsoft Windows 7 operating system? Product Line TAC IA Series Environment I/A Series (Niagara) R2 software, any version (See specific version note in Resolution section) Microsoft Windows 7, all editions, 32-bit or 64-bit (See specific version note in Resolution section) Cause PCs upgraded to Windows 7 operating system. Resolution The I/A Series (Niagara) R2 software has not been certified for use with the Microsoft Windows 7 operating system. The I/A Series (Niagara) R2 releases 529 and 532 has been informally tested on the Microsoft Windows 7 Professional (32-bit) operating system, Windows 7 Professional (32-bit) XP-Mode and Windows 7 Professional (64-bit) XP-Mode.  No issues have been reported with the exception of R2 Niagara Application Tunneling.  The R2 Niagara Application Tunneling must be configured to run in "Silent Mode" when run in any Windows 7 environment.

Issue Loytec (LTA, lon port) offline in TAC Vista when running TACOS as a service Environment TAC Vista running as Service Loytec NIC device Lconfig/NIC legacy driver Cause For TAC Vista to use the legacy driver, it must be running before Vista starts. When running TACOS as a service, by default, it will start prior to the legacy driver and the LTA port will show offline. For this reason, the legacy driver must also run as a service.  Dependencies on the Vista Server service must also be configured to ensure that the legacy drivers starts first. Resolution First make sure that the legacy driver is set up to run as a service Open Lconfig and click on advanced. Select "run as service" and click ok.   Reboot computer From the  start menu, select run, and type regedit Go to  HKEY_LOCAL_MACHIN\SYSTEM\ControlSet001\Services\TACOS\ Double click on depend on service Type in LoytecSrv on a new line.   Reboot computer.

Issue Availability of IPSEC on older controllers which request higher security constraints on networksLAN sites which have Andover controllers and workstations on a "flat network" but want to merge the devices into the corporate network which has IPSEC enabled. Environment Network of IP level controllers communicating with Cyberstation Cause Higher Security constraints on networksLAN sites which has Andover controllers and workstations on a "flat network" but want to merge the devices into the corporate network which have IPSEC enabled. Resolution Older versions of Andover Continuum controllers do not support network security such as IPSEC. However, the new versions of CyberStation and the new controllers, such as NetController II 9680 and ACX57x0, can be configured to communicate with controllers that do not support network security.   Another point to take note of is whether or not your site has purchased the network security option for this NetController II 9680 or ACX 57x0 controller.   IPsec is an end-to-end security scheme operating in the Internet Layer of the Internet Protocol Suite. It can be used in protecting data flows between a pair of hosts (host-to-host), between a pair of security gateways (network-to-network), or between a security gateway and a host (network-to-host).   Network Security Configuration Guide (zip)

Issue Not generally available Product Line Field Devices Environment I/A series Field device Cause Information not provided with the documentation supplied. Resolution The STR800 Series User manual can be downloaded by selecting this link. The STR800 Temperature Sensor RoHS Certificate can be downloaded by selecting this link. The STR800 Wall Module Specification Sheet can be downloaded by selecting this link. Other STR800 documentation is available on the Schneider Download Center.

Issue Polling data from one Xenta Server to another can be accomplished over IP by importing XBuilder Projects. This will only bring over data points that reside in the Network Pane of the XBuilder Project.  If points are being calculated in a Menta object, for example, they would not be available following an import. Product Line TAC Vista Environment XBuilder Xenta Server 701, 711, 721, 731 Fixing Write Over IP Cause Importing another projects network brings over only data points that reside in the Network Pane of the XBuilder Project. In order to avoid a write over IP situation, data from the System pane sometimes needs to be browsed into the other controller's project. Resolution Expand the Network pane beneath the Xenta 700 and find the Variables folder. Right click on the Variables folder and select New Variable (if desired, choose New Folder to organize the points that need to be sent over IP). Create a variable for each point that needs to be imported into the receiving Xenta Server. Drag and drop Variables onto the Menta object outputs to associate them   Note: Only Menta object Outputs allow for this drag-and-drop functionality.  If they are public signals, then either: Add an RO, IO, BO point on the output of the signal Use a connection object in XBuilder to transfer the value to the Network Pane variable. In the receiving controller's XBuilder project, right-click on the IP Backbone and select New > Other Projects Network.  Now the Menta object variables are available.

Issue After the user have logged in to TAC Vista Workstation it hangs and the only option is to close it Product Line TAC Vista Environment TAC Vista Workstation 5.x.x Cause When users log in to TAC Vista workstation all events specified in the Event viewer window is retrieved. If too many events are retrieved to Vista Workstation it can cause Vista workstation to hang. Resolution Under the TAC Vista server object open properties for $Eventview Open the "Date and Time" tab and specify a shorter time period. Click OK