Building Automation Knowledge Base

Issue ENC / JACE is licensed for MS but gets error "Unlicensed: javax.baja.license.FeatureNotLicensedException:" when attempting to access the MS Network property sheet. Environment I/A Series G3, ENC-520 or JACE-645 with TAC-LLC license installed. Cause When displaying the I/A Series G3 Platform details via the Platform Administration screen in the Workbench, the display shows the following for licensing: Licenses Tridium.license (Tridium 3.5 - never expires) TAC_LLC.license (TAC_LLC 3.5 - never expires) Certificates Tridium.certificate (Tridium - never expires) This information shows that the Tridium and TAC_LLC licenses have been installed but only the Tridium certificate. The TAC_LLC license will not be recognized unless the TAC_LLC.certificate is also installed (as shown in the following platform details display. Licenses   TAC_LLC.license (TAC_LLC 3.6 - never expires)   TAC.license (Tridium 3.6 - never expires) Certificates   Tridium.certificate (Tridium - never expires)   TAC_LLC.certificate (TAC_LLC - never expires) Resolution There are two ways to resolve this issue depending on network connectivity of the G3 Workbench computer. If public ethernet connectivity is available, the licenses and certificates can be downloaded from the I/A Series G3 (Tridium) license server, using the Workbench "License Manager". Open Workbench and connect to the subject ENC / JACE. Open the Platform then select License Manager. In the License Manager, select [Import] then check "Import licenses from license server".  This process will download any available licenses for the selected device, along with any available certificates.  After the download is complete, the licenses and certificates downloaded will automatically be installed.   If public ethernet connectivity is not available or the certificate is not found, download the TAC_LLC certificate from The Exchange Download Center.  Use Workbench to import the downloaded file.  A reboot of the ENC / JACE may necessary.

Issue The difference between VWG-APP-1045 and  VWG-EPP-1045 option cards. Environment I/A Tridium SE7000 VWG-EPP-1045 VWG-APP-1045 Cause Different cards available. Resolution VWG-APP-1045:  option card  that fits directly into a Tridium JACE controller to provide communications between controllers and the gateway device. VWG-EPP-1045: option card that fits directly into the American IA range of controllers with an RS232 interface

Issue After powering down a Microzone II controller and powering it back up, the ENC will not immediately reconnect to the device. Environment I/A Series G3 ENC with tacASD 3.4.64.1 or earlier module (jar file). Any ASD devices under the ENC. Cause The existing tacAsd module, (release 3.4.64.1 or earlier) may exhibit excessive device initialization and recovery times upon a restart of the station or a power cycle of the ASD devices. Resolution Update the tacAsd module to release 3.4.64.4. File acAsd-3.4.64.4 can be downloaded from Ecobuildings Download Center.

Issue The message: WARNING: past fox.maxServerSessions limit: 100” WARNING [10:11:17 18-Jan-12 EST][fox] Closing session [1713201: Server 10.10.10.10:63818 doesn't match opened session [null]. How can the Max Server Session count be increased?   Environment Niagara G3, ENC-410, ENC-520, ENS Cause The Max Server Connection property limits the number of server connections that are allowed on the local station. When the maximum number of connections is reached, any successive attempts to logon to the station will fail. The default setting is 100 sessions. Resolution Right-click NiagaraNetwork of the local station and select Views and Property Sheet. Expand Fox Service. Increase Max Server Sessions count. Click the Save button to save change.  

Issue I/A Series G3 alarms acknowledgement via a SMS sent from a mobile device Environment I/A Series G3 version 3.5 or later Cause The ability to acknowledge alarms via a text SMS message sent from a mobile device is required. Resolution The SmsAlarmAcknowledger component (I/A Series G3 version 3.5 and later) provides a way for users to acknowledge alarms by sending a reply to a text message alarm notification. This component is available in the Sms palette. More details can be found in the section 'About the Sms Alarm Acknowledger' on pages 5-22 and 5-23 of the Niagara Ax 3.5 User Guide or the Niagara Ax 3.6 User Guide. The Niagara Ax User Guide is included with the installation of the I/A Series G3 ENS software if you have chosen to install documentation during the setup (\niagara\niagara-3.x.xx\docs\docUser).  

Issue The error diagnostic properties provided by the "diag" object are not defined anywhere. Environment I/A Series (Niagara) UNC ENC Cause These properties are present in the controller but were not shown at the GCM level and were deemed not necessary in diagnosing issues with the controller. Resolution Below are what the unnamed error properties represent: error8 [err8] - Real time Clock (RTC) installed error16 [err16] - RTC invalid error32 [err32] - Database is being downloaded error64 [err64] - Block frozen, will not run (not running) error512 [ err512] - Enhanced MZII hardware error1024 [ err1024] - not assigned error2048 [err2048] - not assigned

Issue I want to request a license for a new customer installation of the WorkPlace Tech Tool version 5.8 but the license request program only shows WP-TECH-50, not WP-TECH-58. Environment WorkPlace Tech Tool release 5.8 Cause Change in license part numbers. License Product Code now specifies the major version number only.  This was done to simplify the process of making the determination of when a license upgrade (WP-TECH-xxU) is required. This change was made as part of the license file change made to allow for up to fifteen consecutive 365-day expiring licenses. Resolution The license product code WP-TECH-50 will unlock any customer installation of the WorkPlace Tech Tool software, releases 5.x.x. i.e., where the first digit of the release number is 5.

Issue Where is the information on LVIS Display/Screen Environment Lon Bacnet Loytec LVIS L-VIS L-VIS Touch Panel for BACnet networks   Cause Information on Loytec L-VIS Resolution The L-VIS from Loytec uses bacnet MSTP or LON. See Product Announcement - LonWorks and BACnet Touch Panels release for more information. All support for this product is via Loytec

Issue Does not want to create his application from scratch if there are application templates available. Environment MNL series of standard LON controllers (MNL-50, 100, 110, 130, 150, 200, V1R, V2R, V3R series). Cause Wants to start with a pre-engineered application if one is available. Resolution Download WPT Micronet Applications Library v4.0.zip. Extract the files to the Solutions folder in WPT.

Issue Added the MSTP Status object to the MNB-1000 database and connected a constant tag to its network input and tested it with WorkPlace Tech and it functions as expected.  However, when doing a Device Learn of this MNB-1000 at the UNC it fails.  The messages is "Learn Device Failed. ObjectId [binary_value:589834]".   The instance number after the binary_value may be different depending on other status objects in the database. Environment I/A Series Niagara R2 Cause Cause is being investigated.  Resolution Use the Device Status object instead.  It will perform the same function and can be learned at the UNC without issue.

Issue Which Modbus driver is required for an I/A Series Niagara R2 UNC to support Modbus TCP? Environment I/A Series R2, UNC-520, JACE-NXT, Soft JACE Cause Selection of the proper driver depends upon the functionality required (e.g. UNC acting as Modbus TCP Client or Server). Resolution The part numbers are: IA-DRV-MOD-T   Operates as a Modbus client - Ethernet / TCP IA-DRV-MOD-R   Operates as a Modbus server - Ethernet / TCP    

Issue BACnet Controllers do not show up on the Server side nor the Client side in WorkPlace Tech Link Builder Environment WorkPlace Tech all versions Cause The Extended Data of the controllers has not been discovered. Resolution The extended data of the BACnet controllers must first be discovered in Workplace Tech Commissioning Tool before the controllers will show up in Link Builder. The extended data of the controllers can be discovered two ways: Highlight all of the controllers in the Commissioning Tool then right-click the selected controllers and select “Refresh” before launching Link Builder. Click on "Auto Acquire Extended Data" from the Commissioning Tool menu before launching Link Builder The controllers should now appear when Link Builder is launched.

Issue Can WorkPlace Tech Link Builder be used to link I/A BACnet controllers to third party BACnet devices? Environment WorkPlace Tech (all Version) Cause I/A controllers do not have the ability to write to third party BACnet devices. Resolution Link builder will only link data from a third party device to BACnet "COVs" in our IA controllers. Our I/A controllers can pull data into our controllers as a client, but they can not function as a server and push data to third party devices.  

Issue Can not edit the graphic pages of a Niagara G3 ENC station via a Web Browser Environment Niagara G3, ENC-410, ENC-520 Cause The PxEditor Module must be loaded on the ENC in order to edit PxViews via a browser. Resolution The PxEditor Module must be loaded on the ENC in order to edit PxViews via a browser. Open the Platform of the ENC Double-click on Software Manager Scroll down and highlight the PxEditor module (is will read “not installed”) Click the “Install” button and then “Commit” button at the bottom of the screen. The PxEditor module will now be installed to the ENC. Once the module installation is completed, the ENC’s graphics can then be edited via a web browser.  

Issue Getting warning " Received bit string (25) is longer than expected length (23)" in the standard output window.  Is this a problem?   Environment I/A Series R2 G3 BACnet Niagara Cause This warning is because the UNC was reading the list of object types supported from the device, and the device was implemented to a different protocol revision, in which there were a different number of object types defined. Resolution The UNC ignores this, and it has no negative impact.  

Issue Which products have been independently assessed by the BACnet International BTL labs? Environment BACnet approvals BACnet Building Controller (B-BC) BACnet Advanced Application Controller (B-AAC) BACnet Application Specific Controller (B-ASC) Other BACnet Device (B-Oth)  Cause The Continuum & I/A Datasheets define that the products are BTL approved, but where can more information be obtained? Resolution Go to the independent BACnet International BACnet Testing Laboratories web site and select Schneider Electric, This shows all of our BACnet approved products and will answer many typical BACnet related questions. See link:  http://www.bacnetinternational.net/btl/

Issue How do I request a new TIP license for the I/A Series R2 software? Environment I/A Series R2 software installation Cause I/A Series R2 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.

Issue Customer has previously purchased the WorkPlace Tech software release 4 and wants to know if there are any controllers available that can be programmed with the release 4. Environment WorkPlace Tech release 4.0 Existing MNL controllers of various releases. Cause WorkPlace Tech release 4.0 generates an error message when an existing application created for an old version of an MNL controller is downloaded into a new controller. Resolution See the section "Controller Firmware Revisions" in Chapter 1 of the WorkPlace Tech Tool 4.0 Engineering Guide for a explanation of the LON controller firmware versions.  If the controller application was programmed for use with an earlier version of the controller,  the application must be updated to the current version before the application can be downloaded into the controller.  Current production controllers contain revision 4.1 firmware.  The revision 4.1 controller model numbers are as follows:  MNL-5Rxx, MNL-10Rxx, MNL-15Rxx, MNL-20Rxx (where xx is F3, R3, H3 , S3 or S4), MNL-11RF3, MNL-13RF3 or MNL-VxRV3 (where x is 1, 2 or 3).    Older production controllers can be identified by the following model number series: MNL-10Rx1, MNL-20Rx1, MNL-VxRV1, MNL-5Rxx, MNL-10Rxx, MNL-15Rxx, MNL-20Rxx (where xx is F2, R2, H2 , S1 or S2), MNL-11RF2, MNL-13RF2 or MNL-VxRV2 To convert the application controller version, use the WorkPlace Tech "Hardware Wizard" after opening the application file. Open the Hardware Wizard. Click the [< Back] button at the bottom of the Hardware Wizard window to display the Controller Selection screen. Note that the current controller version for the application will be displayed in the box at the bottom of the window. If the old controller type is a MN V1, MN V2 or MN V3, select the [MN VAV] tab otherwise select the tab corresponding to the displayed controller type. On the controller selection page, select the model number of the new controller to be used for the application.  If the controllers are using the "Satellite" profile and the old controller was a "Satellite 1" profile, select the "Satellite 3" profile for the new controller.  Select "Satellite 4" if the old controller was a "Satellite 2" profile.  For all other controllers, select the new controller with the same profile type (Fan Coil, Heat Pump, Roof Top) as the original.  After selecting the controller profile for the replacement controller (in step 5), verify that the controller model number shown (MNL-xxxxx) matches the original controller, except for the last digit.  This is the model number of the controller that should be used for the replacement. Click the [Next] button to accept the new controller type selection then click the [Next] button to accept the controller configuration. Click the [Finish] button to exit the Hardware Wizard and apply the changes to the application. The application can then be compiled and downloaded to the new controller.

Issue Is there a way, within the MNB-1000 application program, to determine if communications has been lost between an MNB-1000 and an attached MNB-1000-15 RIO module? Environment MNB-1000 with attached MNB-1000 RIO module(s) Cause The WorkPlace Commissioning tool can display the status of the RIO modules attached to the MNB-1000 but this information is not available within the MNB-1000 application program. Resolution A proposed solution is to use a UO output and a UI input on the same RIO module to allow the MNB-1000 program to monitor the RIO module.  The concept is to drive the UO, 0-20ma with a binary signal from the program. The value would be programmed to change On/Off periodically -- once a minute for example.  The value of the UI would be compared and an internal application alarm generated if the value read from the UI does not agree with the value being written to the UO.

Issue Is there a document that gives the suggested controller to I/O device (field hardware) wiring information?  Wire Gauge, Type of Wire, etc. Environment I/A Series controllers and field hardware Cause Customer wants a document that provides Schneider-Electric's recommendation on controller field wiring. Resolution For the MNB family of controllers, refer to the MicroNet BACnet Wiring, Networking and Best Practices Guide, F-27360. For the MNL family of controllers, refer to the I/A Series MicroNet System Engineering Guide, F-26507. For the Network-8000 family of controllers, refer to the Network 8000 Hardware Installation Practices guide, F-23061. The Network 8000 Hardware Installation Practices guide is also a good guide for field device wiring for use with any family of controllers.