Building Automation Knowledge Base

Issue R2 UNC station fails to start and displays the following error message in its standard output window: FATAL: cannot boot station from sns java.lang.ClassNotFoundException: tridiumx.vlon.VlonService   Environment Niagara R2, UNC-520-2, Cause The station being installed requires the vlon service, but the vlon module in not installed in the UNC. Resolution Install the vlon module into the UNC and restart the UNC. Install the vlon module into the UNC: Use Admin Tool to connect to the UNC.  Go to the 'Installation' tab and click on 'Installation Wizard'. In the Select Distribution Directory dialog, highlight 'emb' and click the 'Install' button.  In the Niagara Remote Installation dialog, select 'Configure Modules Only' and click 'Next'. In the Configure Modules dialog box, select the vlon module by selecting in the 'Upgrade/Add' column. Click 'Next when finished. On the Database Backup dialog box, leave the red check mark next to the station database name and click 'Next' to continue. Enter the station user name and password when prompted. In the Niagara License dialog box, click Finish.  

Issue What does a DMS Loop Point send out when the setpoint and process variable are equal and only a Proportional constant is used? Environment DMS and Microsmart Cause Understanding how to apply a DMS Loop Point to a control application Resolution A proportional-only Loop Point assumes a 'midrange' output when the setpoint and process variable are equal. 'midrange' means midway between the loop output high range and low range (typically 100 and 0 respectively). For more information, see the DMS Operator Interface User's Guide (F-25467), chapter 13.  It is available for download from the Publication Zone.

Issue When starting the station, an error message is displayed in the Application Director window reporting a series of javax.baja.sys errors.  The errors are of the format: javax.baja.sys.ModuleException: Cannot resolve dependency xxxxx-Tridium-3.y.zz -> xxxxxx-Tridium-3.a.bb javax.baja.sys.ModuleIncompatibleException: yyyyy-Tridium-3.y.zz Environment I/A Series G3 installation, any versions Cause The modules reported in the first exception line are incompatible with each other. Resolution This issue is usually caused by installing an incompatible version of one of the modules used by the ENS station.  Delete the folder \niagara\niagara-3.x.xx\sw folder (where 3.x.xx is the G3 release number) Reinstall the required 3.x.xx version of the G3 software. Copy any additional required modules to the modules folder. Open the workbench and run the Software Manager to rebuild the "sw" folder. Restart the ENS station.

Issue Cannot open a Niagara G3 station with via a web browser Environment Niagara G3 all versions, ENC-520, ENC-410, ENS Cause The station’s HTTP port number was changed from it default port number of 80. Resolution If the station’s HTTP port number was changed to something other than the default port number 80, then the HTTP port number must be included with the station IP address in the web browser URL  Example:  A station’s HTTP port was changed from its default 80 to 8080.  The following will need to be entered into the web browser’s URL in order to gain access to the station:  http://<station IP address>:8080  

Issue The following error is displayed when attempting to start ad R2 station: ---------- Station Starting:   WED JAN 04 18:07:15 2012 ---------- Tridium Niagara Station, r2.301.514.v1 [LBV_Bldg_300] ERROR: Reading Ecdis210 [1371] Ecdis210 Subnet = 1 Node = 2 state = config_online#link: 983 *************************************************************** FATAL: Cannot boot station from sns java.io.UTFDataFormatException    at java.io.DataInputStream.readUTF (bytecode 211)    at java.io.DataInputStream.readUTF (bytecode 1)    at tridium.foundation.node.Link.readExternal (bytecode 59)    at tridium.foundation.node.Node.readExternal (bytecode 295)    at tridium.foundation.node.NodeSet.readExternal (bytecode 132)    at tridium.foundation.node.NodeSet.read (bytecode 43)    at tridium.foundation.prism.LoaderModule.loadFromSns (bytecode 48)    at tridium.foundation.prism.Prism.loadFromSns (bytecode 4)    at tridium.foundation.Sys.bootLocalSns (bytecode 11)    at tridium.tools.StationMain.bootSns (bytecode 0)    at tridium.tools.StationMain.doIt (bytecode 352)    at tridium.tools.StationMain.main (bytecode 10)    at java.lang.reflect.Method.invoke (Native Method)    at tridium.nre.Nre.mainImpl (bytecode 271)    at tridium.nre.Nre.main (bytecode 1) Environment Niagara R2, UNC-410, UNC-520 Cause Station database is corrupt. Resolution First make sure the correct Distech module is installed. If the correct module is installed and the error persist, then the station's database is corrupted. Use a backup copy of the station database.  

Issue An application created using WorkPlace Tech was working properly when created.  As many additional changes have been made to the application, unchanged portions of the application that were working no longer work correctly. Some observed examples of this issue are as follows: MNB-1000 application that includes the ADI interface worked when the first few ADI points were linked but after moving the application to another computer and linking the remaining ADI points, the ADI interface no longer worked. Hardware I/O points are not being properly handled after editing, compiling and downloading the application to the target controller.  This application was originally created on a different computer but with the same version of the WPT software. When downloading an application to the controller, WorkPlace Tech reports "Unknown error" but no errors were reported when compiling the application. Connecting lines that are a valid connection but are displayed as a red line. Application not correctly using configuration as specified by Hardware Wizard even though Hardware Wizard has been run and appeared to properly configure the application. Some internal program objects do not appear to operate as documented. Environment WorkPlace Tech Tool version 5.x.x Cause If the application data stored in the WorkPlace Tech application drawing file (vsd file) becomes corrupted, the application continues to compile correctly but does not operate.  This corruption is not observed on the drawing itself.  The application data and drawing data are independent of each other within the Visio file.  In some cases, an application created in WPT 4.x may contain application database information that is not correctly recognized by WPT 5.x.x. Resolution After opening the application in the WorkPlace Tech Tool software, run the "Rebuild Application" function to rebuild the internal representation of the application database.  The location of the "Rebuild Application" function in the Visio menu varies depending on the version of Visio that is running the WorkPlace Tech Tool software.  When starting the Rebuild function, a Windows WARNING dialog box is displayed.  To accept the displayed conditions of the Application Rebuild function, click the [Yes] button.  Further information on the information displayed in the dialog box is shown in the NOTE and Warning paragraphs, below. If using a version of Visio prior to Visio-2010, i.e., no ribbon bar, and WorkPlace Tech Tool version 5.6 or 5.7.x, the "Rebuild Application" function is found under the "Application" menu. If using Visio-2010 with WorkPlace Tech Tool version 5.8, the "Rebuild" function is found under the Application menu of the WorkPlace Tech ribbon bar. Note: After rebuilding the application database, the object order of any or all of the control objects may change.  If an attempt is made to monitor the controller containing this application, without downloading the rebuilt application to the controller, the monitor tags may display incorrect information. Warning:  Before running the "Rebuild Application" function on an application for a MNL-800 controller, confirm that index numbers have been properly assigned to ALL LON network variables and constants used in the application.  Failure to confirm that all LON network variables and constants have been manually indexed could result in changes to the LON application profile (XIF file).  This will result in binding issues between the controller LON network variables and other devices on the LON network.

Issue The documentation for the I/A Series G3 Schneider Electric (TAC) proprietary drivers are not included with the I/A Series G3 software documentation. Where can those documents be obtained? Product Line TAC IA Series Environment I/A Series G3 ASD Driver I/A Series G3 GCM Driver I/A Series G3 MicroSmart Driver I/A Series G3 DMS Driver Cause Documentation for these drivers is not included with the I/A Series G3 software release Resolution The documentation for the I/A Series G3 Schneider Electric (TAC) proprietary drivers can be downloaded from the Publication Zone (under Links) on iPortal (iPortal). The following documents are available: F-27522 -- I/A Series G3 ASD Driver F-27527 -- I/A Series G3 GCM Driver F-27523 -- I/A Series G3 MicroSmart Driver F-27541 -- I/A Series G3 DMS Driver

Issue When attempting to install the Signal-XP software on a Windows XPsp2 computer, the installation aborts without displaying any error messages. Environment Windows XP-sp2 computer Cause The installation of the Signal-XP software requires that the HASP security plug be connected to the computer and be recognized before the Signal-XP software can be installed.  Due to changes made by Microsoft in the Windows-XP service pack 2 upgrade, the HASP software included with the Signal-XP installation cannot read the HASP security plug. Resolution Download and install the updated HASP4 driver per the instructions include in Technical Alert TA06-03.  Please note that the referenced (Aladdin) web site may have changed its visual layout since the bulletin was published.  The noted version of the driver software may not be available.  Use the latest Win32 driver that is available on the Aladdin website.

Issue Cannot do a Save Runtime DB. - getting the following error:     java.net.ConnectException: Connection refused: connect      at java.net.PlainSocketImpl.socketConnect(Native Method)     at java.net.PlainSocketImpl.doConnect(Unknown Source)     at java.net.PlainSocketImpl.connectToAddress(Unknown Source)     at java.net.PlainSocketImpl.connect(Unknown Source)     at java.net.Socket.connect(Unknown Source)     at java.net.Socket.connect(Unknown Source)     at java.net.Socket. (Unknown Source)     at java.net.Socket. (Unknown Source)     at tridium.nre.drivers.SocketDriver$TcpSocketFactory.createSocket(SocketDriver.java:690)     at tridium.nre.drivers.SocketDriver.create(SocketDriver.java:216)     at tridium.nre.drivers.SocketDriver$ConnectThread.run(SocketDriver.java:510)   Environment Niagara R2, UNC-520, UNC-410 Cause The connection error typically occurs during a database backup when the port used by the UNC has been changed from the default port 80. Resolution If this is the case, a line must be added to the station.properties file to specify the new port value. Open the Admin Tool and log into the UNC (not the station database). Right-click on the station name that indicates "running" and select Edit > Properties. The station.properties window will open (typically indicates autoStart=true and autoRestart=true). Add a line to this file that specifies the new port. Example: If the station database was configured to use port 8080, the line would read ... httpPort=8080 Choose File > Close and save when prompted. Reboot the UNC for change to take place   You should now be able to successfully backup the database. The details of this procedure are located in the documentation (Niagara Networking and Connectivity Guide).  

Issue How do I request a new TIP license for the I/A Series G3 software? Environment I/A Series G3 software installation Cause I/A Series G3 License request process for field offices on the TIP program has changed. Resolution See Product Announcement PA-00186 for details. Please note that the demo license described in this document is only available to our partner offices that participate in the TIP program.  If your office does not participate in the program, please contact your regional sales manager for more information. As noted in the license forms, the completed request should be emailed directly to our I/A Series R2/G3 license team at IASeries.License@schneider-electric.com.

Issue I/A Series G3 ENC time of day clock runs slow.  Can this be corrected in the field? Product Line TAC IA Series Environment I/A Series G3 ENC (remanufactured replacement) Cause The time clock constant was incorrectly set in some remanufactured ENC-520 controller boards. The result is that the ENC-520 time clock (time of day clock) will not maintain proper time. Resolution Connect to the ENC using the Serial adapter and a Windows Terminal program such as HyperTerminal. If you need information on how to use the Serial Shell (terminal connection), refer to Chapter 1 (Recover Tips, Serial shell, page 26) of the "Jace Niagara -AX Install and Startup Guide," found in the Docs folder of your 3.5.34 installation directory. Make sure that you have installed a jumper on the outer pair of pins of the MODE connector (upper right corner of circuit board -- see photo at right). Reboot the ENC by disconnecting and reconnecting the power plug. Allow the ENC to reboot and wait for the login prompt to be displayed in your terminal program. Log in using the hardware user name and password. Wait for shell menu and the "Enter Choice" prompt to be displayed. Type sh and press enter. At the # prompt, type lfss -c and press enter. The current clock multiplier will be displayed. I expect that the current multiplier is 96000000. Type lfss -c 96065600 and press enter. Wait for the # prompt to be redisplayed. Verify that the entry was properly entered by typing lfss -c and pressing enter . The value 96065600 should be displayed. Type exit and press enter to return to shell menu. Press 7 to reboot the ENC. Press y to confirm the reboot and press enter. The ENC will reboot. Remove the mode jumper and disconnect the serial cable.

Issue UNC station in WorkPlace Pro is losing connection from the Enterprise Server periodically. During connection loss, it will not be possible to open the UNC station in WorkPlace Pro or the UNC in Admin Tool. The UNC's IP address continues to be reachable when using the ping command from the Enterprise Server computer. The following error is seen in the UNC station's ErrorLogService. java.io.IOException: Closedat tridium.datax.net.DxExchange.sendRequest (bytecode 13 at tridium.datax.net.DxExchange.sendAsync (bytecode 4) at tridium.foundation.prism.SubscriptionModule$DispatcherDaemon.run (bytecode 105) Environment I/A Series R2 UNC-520 Cause There is another device on the network with the same IP address as the UNC. Resolution Check and note all IP addresses within the system and rectify IP address conflict.

Issue Customer has requested and received the Unlock code for WorkPlace Tech 5.7.7 and does not know where to enter it in WorkPlace Tech. Environment WorkPlace Tech Tool version 5.7.x or 5.8 Cause Needs to enter an unlock code for WorkPlace Tech Tool software. Resolution This process is documented in the section "Installing Unlock Codes" of chapter 5 of the WIBS Installation and Configuration Guide, document, F-26641 and is summarized here.  The installation instructions can be downloaded from the Publication Zone on iPortal (https://iportal2.schneider-electric.com/). Run "Purchase Workplace Tech Software" icon on computer desktop (See below if the ICON has been removed). Click "Unlock" Click on license to be unlocked. Enter unlock code in appropriate field on form Click [Generate License] Click [Done] to exit the Unlock window Click [Done] to exit "Purchase..." program. If the  "Purchase Workplace Tech Software" icon has been removed from the desktop, and WPT 5.7.x or 5.8.x was the first version ever loaded on the computer, the program will be found at: C:\Program Files\WorkPlace Tech\Licensing\Core\WPTLPurchase.exe After opening the program continue with step 2, above.

Issue How do I request a replacement I/A Series R2 or G3 Enterprise Server license for a host ID change due to a failed computer or reload of the operating system? Product Line TAC IA Series Environment I/A Series R2 Enterprise Server / WorkPlace Pro * I/A Series G3 Enterprise Network Server / Workbench Cause Reload of the I/A Series R2 * or G3 Enterprise Server on a new computer or hard drive causes the host ID to no longer match the existing license. Resolution Replacement licenses are required for various reasons that include a failed computer and reload of the operating system.  In cases where the existing computer’s R2 or G3 Host ID has changed, a license form MUST be filled out and provided with the correct information in order to obtain a replacement license file.  The form must include the old host ID, new host ID, jobsite information, and reason for the change.  There is no charge for a host ID only change. Forms can be found on both the iPortal and The Exchange Download Center websites. iPortal iPortal - Login and navigate to Products and select Manage Forms. The Exchange Download Center - IA Series R2 License Forms v6.6 - 112013 and IASeries G3 License Forms v4.8 - 112013A The license request can be emailed to the following address.  IASeries.License@schneider-electric.com   * Update - I/A Series R2 has been discontinued as of Janaury 1, 2016. Schneider Electric can no longer provide replacement licenses for failed I/A Series R2 UNCs, Enterprise Servers, WorkPlace Pro, or Office Demos. Refer to PA-00459 for details. 

Issue The window used to change override time for an S-Link sensor is grayed out. How is the override time changed? Environment WorkPlace Tech 5.7.2, MN-S3, MN-S4, MN-S5 Cause Trying to change override time with Workplace Tech 5.7.2. Resolution The ability to change the S-Link sensor override time was corrected in WorkPlace Tech 5.7.5 Upgrade to WorkPlace Tech 5.7.5 or higher  

Issue I am running R2 529 and cannot find the right object to be able to write an analog value in the UNC to an AVSPP object in the MNB controller. Environment I/A Series R2 (niagara) UNC Cause I/A Series R2 (niagara) UNC Resolution If the analog value being shared is one that will be changing regularly it should be written to an AVSPP object in the MNB controller.  The AVSPP object requires a priority be provided with the analog value.  To accomplish this use the Fs2Fp object provided in the 532d version of the programlib jar.   Link the output of the analog value to the input of the Fs2Fp object.  Define the priority level you want to send it at in the Fs2Fp object.  Link the output of the Fs2Fp object to the priority input of the AVSPP and the value will be written to the controller.

Issue When trying to install the I/A Series Software (release 514 or later) on a new computer, an error is displayed that indicates Java is required.  Where do I get it and what version is required? Environment I/A Series R2 Software release 5.14 or later. Cause Microsoft can no longer distribute the Java JRE (Java Runtime Environment) with its operating systems.  The I/A Series R2 software, release 514 and later, requires the industry standard Java JRE to be installed on the computer before installing the I/A Series software. Resolution Download and install the latest available release of Java version 6 or 7, based on your version of Windows. The software can be downloaded from the web site http://www.java.com.  The site normally detects your operating system and provides the proper version when you click the [Free Java Download] button on that site. Java version 6 update 10 is the minimum recommended release for the I/A Series R2 software.

Issue In upgrading to WorkPlace Tech 5.x from 4.x, what is there to understand about the project files during this conversion? Environment WorkPlace Tech 4.x, 5.x Cause Host operating system changing from Windows XP to Windows 7 and WorkPlace Tech 4.x is not compatible with Windows 7. Resolution A few things to keep in mind: When a drawing from 4.x is opened in 5.x for the first time, the conversion may take awhile. Be patient and let it finish. Once the drawing is converted to 5.x, it cannot be converted back to 4.x. Keep a backup of the 4.x files just in case. Similarly, once a controller is downloaded with a database using 5.x, the controller will no longer work with WorkPlace Tech 4.x. If, for some reason, it needs to be used with WorkPlace Tech 4.x, then its database will have to be reloaded using 4.x first.  

Issue What is the default IP address configured with a new jace-nxt for Niagara G3? Environment Jace-nxt Jace-nxs Cause Initial powerup connection with Workbench Resolution A new JACE-NX controller with Niagara G3 has the following TCP/IP settings for its two Ethernet ports:   Primary (top) port: 192.168.1.19n (static IP) with subnet mask: 255.255.255.0      where the last numeral (n) matches the last numeral in the JACE's serial number   Secondary (bottom) port: disabled in BIOS, no assigned address   Usage of secondary port requires attaching a local console (keyboard, mouse, monitor) to the JACE-NX, rebooting the unit, then entering BIOS setup at power-on self test (POST) to enable the port.   Intended usage of the secondary port is for isolating a "driver's" Ethernet traffic from the primary port. Enabling the secondary port is generally discouraged, unless deemed absolutely necessary.   The primary factory-assigned IP address should also be listed on the packing slip that accompanied the JACE. If needed, change these IP network settings during your startup commissioning of the JACE.

Issue Attempting to "export" BACnet points from an I/A Series G3 ENC-410 or ENC-520 generates the following "Fault: Server capability is not licensed." Environment I/A Series G3, ENC-410, ENC-520 Cause By default, the ENC-410 and ENC-520 platform supports BACnet IP and BACnet Ethernet as a Client only.  Attempting to configure the BACnet IP or BACnet Ethernet to serve or export BACnet point data will generate the fault. Resolution BACnet export capability is enabled through the purchase of the Enterprise Connectivity Pack (P2P) option.  The part number for the ENC-410 is ENC-410-P2P.  This feature enables Peer-to-peer connectivity ENC-to-ENC and ENC-to-Enterprise Network Server communications links, as well as the BACnet Export capability. The part number for the ENC-520 is ENC-520-P2P.  This feature enables Peer-to-peer connectivity ENC-to-ENC and ENC-to-Enterprise Network Server communications links, as well as the BACnet Export capability.