Building Automation Knowledge Base

Issue I/A Series G3 SMS Driver Part Number Environment I/A Series G3 Cause The SMS (Simple Message Service) driver is used for sending text messages to mobile / cellular phones. The SMS driver allows retransmitting alarm information and sending general text messages. The I/A Series G3 SMS driver is not listed in the datasheets for the Enterprise Network Server or Enterprise Network Controllers. Resolution ENC-DRV-SMS License an ENC-520, JACE 6 or JACE 7 to enable SMS alarms to be sent to any mobile phone via a GSM/GPRS modem connected to the RS-232 serial port * The SMS  Driver is no longer available in the Enterprise Network Server and Soft JACE. There is a technical issue and the driver has been removed from use on Windows based platforms.  If the driver is required for use in the ENC or Soft JACE, contact Schneider Electric Product Management via your local Schneider Electric sales office.  ENC-DRV-SMS License an ENC-520, JACE 6 or JACE 7 to enable SMS alarms to be sent to any mobile phone via a GSM/GPRS modem connected to the RS-232 serial port

Issue Customer desires to use newer release of the G3 software on his existing ENCs and  ENS. Environment I/A Series G3 ENC I/A Series G3 ENS I/A Series G3 NXT I/A Series G3 Soft JACE Cause New upgrade has been released and customer desires to use that version. Resolution To request an upgrade for an existing customer's ENC, complete the ENC-520 series or ENC-410 series I/A Series G3 Hardware License Request Form, checking the box for "Field Upgrade" and the box for the "Software Upgrade for ENC" (IA-LIC-G3-UPG1).  Make sure that the current license information shown on the form matches the existing license and include the device serial number in the appropriate field on the form. Submit the license request form along with your purchase order for the part number IA-LIC-G3-UPG1 to IASeries.License@schneider-electric.com. To request an upgrade for an existing customer's ENS, complete the Enterprise Network Server / Workbench I/A Series G3 Software License Request Form, checking the box for "Field Upgrade" and the box for the "Upgrade to latest Software Revision" (IA-LIC-G3-UPG2).  Make sure that the current license information shown on the form matches the existing license and include the device serial number in the appropriate field on the form. Submit the license request form along with your purchase order for the part number IA-LIC-G3-UPG2 to IASeries.License@schneider-electric.com. To request an upgrade for an existing customer's Soft-JACE, complete the Enterprise Network Controller (Soft JACE) Software only License Request Form, checking the box for "Field Upgrade" and the box for the "Software Upgrade for ENC" (IA-LIC-G3-UPG1).  Make sure that the current license information shown on the form matches the existing license and include the Software ENC HostID in the appropriate field on the form. Submit the license request form along with your purchase order for the part number IA-LIC-G3-UPG1 to IASeries.License@schneider-electric.com. To request an upgrade for an existing customer's JACE-NXT, complete the Soft-JACE I/A Series G3 Hardware License Request Form, checking the box for "Field Upgrade" and the box for the "Software Upgrade for JACE" (IA-LIC-G3-UPG1).  Make sure that the current license information shown on the form matches the existing license and include the ENC Serial Number (NXT Serial Number) and ENC HostID in the appropriate fields on the form. Submit the license request form along with your purchase order for the part number IA-LIC-G3-UPG1 to IASeries.License@schneider-electric.com.

Issue A Niagara R2 installation is being upgraded to the current revision.  What's the part number for ordering an upgraded license file? Environment Niagara R2 Cause Installation is being upgraded from 2.301.431 to the current revision Resolution IA-LIC-23G Upgrades the license file to the current revision IA-LIC-CHG Modifies other parameters in the license file like the projectId, orgId, hostId, etc.... Both part numbers apply to an Enterprise Server license and to an UNC license. The list price for both of these part numbers is available on iPortal.

Issue When compiling a WorkPlace Tech application created and successfully compiled with an earlier version of WPT and Visio, an error message may be displayed indicating an issue with an object in the application.  One of the observed errors is noted below: "Unhandled write error (app name) (object name)" Environment WPT 5.6.x WPT 5.7.x WPT 5.8.x Cause Internal consistency error in the internal application database. This issue will sometimes occur when the application was created in one version of Visio then updated to a newer version.  The actual causes are not fully understood.  Because the history of the actual application file is frequently unknown, having been created and modified by various engineers, these issues usually cannot be duplicated. Prior to WorkPlace Tech Tool version 5.x.x the application database was stored in the WPT project database.  In WPT version 5.x.x, the application database is stored internal to the WPT application drawing Visio file. Resolution Open the application file in the WorkPlace Tech Tool and allow it to be saved in the newer Visio file format, if prompted. From the "Application" menu of WPT, select "Rebuild Application" Click the [Yes] button to allow the application to be rebuilt.  A popup window will display the process of the application rebuild. If errors are detected, appropriate steps must be taken to correct them. If you are rebuilding an MNL-800 application and have not previously manually indexed all the Echelon network variables (SNVTs), the SNVT index numbers may change.  This change of SNVT index numbers can cause issues with existing network bindings to or from the controller.  If some or all SNVTs were not indexed, and they changed as a result of the rebuild, you will need to follow the list of sub-steps listed here. Using the WPT Hardware wizard, change the "Controller Program ID" then compile and download the application to the controller If the network is managed using LonMaker, perform a "Replace" on the controller object, reading the XIF file from the device. If the network is managed by an I/A Series R2 UNC and WorkPlace Pro, you will need to delete the existing device shadow object and re-learn the controller then recommission the device and recommission the Local Lon Device.. Update any binding links that were changed or moved due to the replacement of the controller shadow object. Compile and download the application. Rebind all links to the updated controller

Issue In Niagara G3, a BACnet proxy point was initially added to the database as Read only; how can it be change to a BACnet Writable proxy point? Environment Niagara G3 all versions Cause BACnet proxy point type (read only. writable, etc.) is selected when the proxy point is first added to the database. The BACnet Proxy Point was initially discovered and added to the database as Read Only Proxy Point. Resolution Unfortunately, once the BACnet Proxy Point is added to the database its Type value can not be changed. The Proxy Point will have to be deleted, rediscovered and re-added to the database. This time when adding the Proxy Point to the database, make sure to select writable for Type.

Issue ENC is licensed for DMS but gets error "Unlicensed: javax.baja.license.FeatureNotLicensedException: tac_llc:tacdms" when attempting to access the DMS Network property sheet. Environment I/A Series G3, ENC-520 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. 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.

Issue Trying to repair/restore a damaged Microsmart controller trunk.  The last controller on the trunk was removed and thrown out before the EOL module could be removed and placed in another controller.  Installing external resistors to mimic the EOL module is the only option.  What are the resistance values with the EOL module? Environment DMS (all models) Microsmart (all models) Cause Site construction/renovation removed the last controller and the EOL module was not removed before it was thrown out. Resolution Replacing the EOL module with external resistors is not a recommended alternative.  However, in an effort to stabilize controller communications until a proper EOL is installed, here are the resistance values within the module: It is an 8 pin module: Across pins 1-8, 3.3 kohm resistor Across pins 2-7, blank Across pins 3-6, 150 ohm resistor Across pins 4-5, 3.3 kohm resistor All resistors are 1/4 watt, 5%

Issue A condition can exist where the BACnet Ethernet adapter is lost upon a power cycle and restart of the computer (normal reboot, loss of commercial power, etc...) and restart of the ENC-SW (Soft JACE) station.  The BACnet Ethernet adapter option indicates "none." Typically a secondary reboot of the PC will correct the issue however, the Ethernet network port may remain disabled requiring a manual enable. Environment I/A Series G3, ENC-SW Cause An I/A Series G3 ENC-SW station utilizing BACnet Ethernet or BACnet IP starts before there is an available Ethernet adapter from the Windows operating system. Resolution The station mechanism related to the Ethernet adapter in I/A Series G3 version 3.6 and higher has been modified to maintain the list of adapters as disabled or disconnected where the adapter choice now remains consistent through a power cycle or reboot condition. Upgrade to I/A Series G3 version 3.6 or higher.

Issue Does the ECH-75010R (Echelon U-10 USB Adapter) come with the interface cable? Data sheet does not specify this information. Environment Echelon U-10 USB Adapter Cause Data sheet does not specify what interface cable, if any is included with the U-10 adapter. Resolution The Echelon U-10 LON Network adapter does not come with an interface cable. As documented in the Echelon data sheet, the adapter only comes with a USB extension cable. To use this adapter with the I/A Series LON controllers, the WPIA-CBL-1 is required.

Issue Using XPSI and PSI in a Virtual XP environment, need to transfer the uploaded files to another computer. Environment Windows 7 computer with a Windows XP Mode Virtual Machine Cause Need to transfer files to another computer for backup and storage. Resolution There are two methods that can be used to transfer files into or out of a Windows Virtual Machine. Access a shared folder on the host computer or on another computer on the network.  You may also map a drive letter to a shared folder.  These procedures are identical to the procedures used in any Windows XP computer system.  The procedure is as follows: Open the Start menu and select Run then type the full computer name and shared folder name using the format //computer-name/share-name then click [OK].  If the folder can be accessed, it will be opened in a Windows Explorer window within the virtual machine environment.   Access a USB Flash driver inserted into the host computer.  Once the flash drive has been connected to the host computer, it will be visible under the "USB" menu on the top bar of the Windows XP Virtual Machine.  Click on the name of the USB Flash drive to attach it to the computer.  When the flash drive has been attached, it will be displayed in Windows Explorer as a drive with the next available drive letter.  You can then access the flash drive in the same manner as you would on the host computer.  When done with the flash drive, it must be detached from the Virtual Machine before you can unmount it from the host computer.

Issue Niagara R2 Workplace Pro, installed on a Windows 7 computer, will not open localhost in admin tool.  The UNC stations open successfully. Environment Niagara R2 (any 2.301.529 or higher) Windows 7 (32 bit) Cause Missing the rassapi.dll file. Some distribution copies of Windows 7 do not include this file. Resolution Close Workplace Pro. Obtain a copy of the file named RASSAPI.DLL and paste it in the niagara\r2.*\nre\bin directory.  The file can come from any Internet website (just do a search for the filename) or from another copy of Windows. Restart Workplace Pro. Note:  At times, a restart of the Niagara Service may be required.

Issue Which Niagara R2 UNC products are no longer available and no longer repaired by the factory? Environment Niagara R2 UNC-6x0 and UNC-500, UNC-510 Cause Obsoletion of the UNC models. Resolution These models are obsolete and are no longer repaired by the factory: UNC-600-xx UNC-610-xx UNC-500-xx UNC-510-xx Product exchange/upgrade programs have also expired.

Issue When using an MNL controller to accumulate a usage total, the output appears to reset when the pulse rate gets too low. Environment MNL family of controllers Cause As designed, if the pulse rate is too low, the output goes to zero. The Pulse Counter function of the Binary Input object is designed to calculate a pulse rate value and a total pulse count value.  Due to mathematical restraints within the processor of the controller, if the interval between pulses is too low, the pulse rate output goes to zero.  Resolution The standard Lon controllers (MNL-50, 100, 110, 130, 150, 200, VAV) handle pulse rates down to a minimum pulse rate of 1 pulse per minute.  If the pulse rate falls below one pulse per minute, i.e., less than one OFF to ON transition per minute, the pulse rate output will go to zero until the next pair of OFF to ON transitions that occur within one minute. For the MNL-800 controller, the minimum pulse rate is one pulse every 4 minutes.

Issue Error javax.baja.sys.NoSuchSlotException: textOverride when activating KitPx "Export' button for pdf in G3 version 3.6. Environment I/A Series G3 (version 3.6) Cause KitPx 'Export' button included on a canvas as part of a ReportPx.  Activating the 'Export' button causes the export to pdf to fail with the following exception ... javax.baja.sys.NoSuchSlotException: textOverride. Resolution Upgrade the pdf module to 3.6.38 or higher. The zip file (pdf-3.6.38.zip) can be downloaded from The Exchange Download Center.

Issue Station was named incorrectly when first created.  Just copying the station folder or renaming the folder has no effect on the name of the station. Environment I/A Series R2 system (any version) Cause Station was named incorrectly when first created.  Did not realize name for the station did not match the desired naming convention used for the other stations in this facility. Resolution To rename a UNC station: Save the existing station database using the Admin Tool DbAdmin function. Use the Admin Tool DbAdmin function to get the station config.sys file and to convert it to an xml file (config.xml).  You will then have a config.sns and config.xml file in the existing station folder. Create the new named station folder under the stations folder under the current Niagara... installation folder. Copy the config.xml file from the existing station folder to the new station folder.  Copy any other folders that are under the existing station folder (graphics, etc) into the new station folder. Open the config.xml file (in the new station folder) with a TEXT or XML editor that can handle large files.  Two text editors that are know to work properly with large xml formatted text files are Notepad++ or EditPad.  These editors are both available for free via Internet. The existing station name typically first appears on lines 18 & 19 of the file.  Use the editor's Search and Replace function to globally change the existing station name to the new desired name.  Make sure that the there are no spaces or special characters in the new station name.  When specifying the existing station name, do not include the double-quote marks. Using the Admin Tool DbAdmin command, convert the edited config.xml file to config.sns. Use the Admin Tool "Install Station" function to load the edited station into the UNC.  

Issue The COM ports are defined and the communications works great but when the ENC is rebooted it is unable to start up the serial port (COM3), it says “COM3 is not a valid port”.  However, once the station is running COM3 can be typed in the drivers properties and it works fine.  Environment ENC, G3, Niagara Cause The station was loading the "Drivers" before the "Services".  The Services must come first to prepare the ports before the Drivers are loaded. Resolution Open the running station in Workbench, right click on Config and pull down to "Reorder".  Change the order to load the Services first, save the change and reboot the station. 

Issue How many DUIC-5P-12V units can be used simultaneously on a MNL-800? Environment MNL-800 Cause Application-specific requirement for multiple contact status monitoring Resolution According to Smartware Technologies (www.smartwaretech.com), the makers of the device, up to four DUIC-5P-12V units can be connected to a MNL-800 simultaneously. 

Issue Microsoft Hotfix changes the HostId on I/A Series (Niagara) R2 and G3 Enterprise Server or Engineering workstations. See TPA-IA-11-0007.00 for details. Product Line TAC IA Series Environment I/A Series R2 and G3: All 32-bit versions of software installed on 64-bit versions of Windows 7, or Windows Server 2008 R2. Cause Microsoft recently released a hotfix for an issue that affects machines running x64 versions of Windows 7 and Windows Server 2008 R2, described in knowledge base article 2603229. The Windows registry contains entries to designate the organization and owner name that correspond to the computer. Each of these registry entries has a 32-bit and 64-bit version. Prior to applying the hotfix, when the OS was installed and setup for the first time, only the 64-bit version of the registry entries were written, leaving the 32-bit registry entries at the factory default value. I/A Series software HostIds are generated from multiple pieces of information gathered from the registry and hardware components of the host platform. The changes made by this Microsoft hotfix will cause the HostId to change on Windows 7 x64 or Windows Server 2008 R2 x64 machines running 32-bit I/A Series G3 or R2 software. Resolution See TPA-IA-11-0007.00 for recommended solution. NOTE: The TPA indicates that the patch is in the I/A Series G3 "Recovery Files" folder.  The files are version dependent and are located in the Release 3.4.64, Release 3.4.67,  Release 3.5.34, Release 3.5.39 or Release 3.6.31 folder, as appropriate for the specified version.  For other versions, option #1 must be used.

Issue UNC was upgraded to R2 release 529 from an older version and when the station was started, the following error message was displayed in the Standard Output Window: ---------- Station Starting:   THU MAR 26 14:43:09 2009 ---------- Tridium Niagara Station, r2.301.529.v1 [GafbBldg857] ERROR: Reading FlexSnvtTempSetpt [3928] FlexSnvtTempSetpt#link: 60 *************************************************************** FATAL: Cannot boot station from sns java.io.UTFDataFormatException   Environment UNC-520 with release 522 or 529 software installed. Cause Incompatibility in the FlexSnvtTempSetpt object between the release 514 and release 529 versions of the jar file. Resolution The best way to correct this issue is to perform a manual upgrade of the existing version 514 station. Use the release 514 WorkPlace Pro "Admin Tool" DbAdmin function to backup the running station and get the station as a .sns file to the computer. Use the DbAdmin function to convert the station from .sns to .xml. In the release 529 installation folder, use the AdminInstall command to start the release 529 version of the NiagaraD service. Copy the station folder containing the station to be upgraded from the release 514 stations folder to the release 529 stations folder. Start the release 529 AdminTool and open the Localhost. Highlight the station to be converted. Select the DbAdmin tab and use the convert local function to convert the station from .xml to .sns The converted station is now ready to be installed into the UNC that has already been loaded with I/A Series R2 release 529 software. This same procedure can be used to convert a 514 station to 532 by substituting release 532 for the release 529 references. above.

Issue A jobsite of MNL controllers was done with WorkPlace Tech 4.x.  The original databases are no longer available.  Can they be uploaded with WorkPlace Tech 5.x and will the upload convert them from 4.x to 5.x? Environment WorkPlace Tech versions 4.x and 5.x MNL controllers Cause Loss of original controller databases Resolution Uploading a MNL controller's program does not change anything within the controller.  Only downloads do. If a MNL controller was programmed with WorkPlace Tech 4.x and is uploaded with WorkPlace Tech 5.x, the uploaded file can only work with version 5.x.  If the resulting file is then downloaded to the same controller, the program version in the controller will then be at 5.x.  It will no longer work with 4.x.