Issue Alarm email is not sent out and is discarded. The Last Discard Cause is 'BOutgoingAccount could not dequeue in-memory email: 501 Syntax error in parameters or arguments'.  Environment I/A Series G3 Cause 'Reply To' field in the Outgoing Account properties was left empty. This field specifies the contents of the 'From' field in the email that is sent. Resolution Configure the Outgoing Account 'Reply To' field with a valid email account. In the example below (G3 version 3.7), the valid account being used is my.account@gmx.com. 

Issue In SmartStruxure, how can Network 8000 objects be linked with non-Network 8000 objects?  For example, sharing an outside air temperature value from a LON integration on the same Automation Server with a Network 8000 integration Environment Network 8000 StruxureWare Building Operations Cause No outside air temperature reference is available in a Network 8000 integration.  Resolution Use APT (A=analog), DPT (D=digital), RnetAv, or RnetDv objects to bring non-Network 8000 data into the Network 8000 integration. These objects behave similar to a 'middle man'.  Each of these objects has a global reference on the 'Inputs' tab. Using the APT object as an example, the Inputs tab has an Analog Global Reference section with two settings: Analog global value & Analog global reference. Bind the output of a Function Block Program (for example) to the Analog global reference. Watch the Analog global value as it will display the value once the binding is done. The output of the APT object can now be linked to as many Network 8000 objects as required. Note: The Global Reference takes highest priority. Therefore, the order of input priority is as follows: 1st = global reference, 2nd = input constant, 3rd = input reference. The input constant and input reference are carry-overs from Network 8000 GCM blocks. The global reference was added for SmartStruxure integrations and took over 'top spot'. In order to use the input constant or input reference, the value of the global reference must equal NULL. This is only for inputs. Any output of a Network 8000 object can be bound directly to any non-Network 8000 object.  

Issue During the startup of an ENC-520 station, the following warning message appears in the application director output: Platform Service Access Platform Service Qnx will not be added, feature 'accessControl' is not licensed. How can this warning be corrected? Environment Niagara G3 Cause This service is for a product line, offered by Tridium, that is no longer available. Resolution Remove the platAccess module from the ENC and reboot.

Issue After upgrading systems to the latest I/A Series G3 Niagara maintenance builds 3.5.406, 3.6.406 or 3.7.106 some customers have noticed spikes in Heap and CPU usage. This behavior has been traced to the excessive creation of NiagaraNetwork worker threads. Customers may see spikes in CPU usage that randomly occur and persist until system appears to halt or in some cases triggers Engine Watchdog Timeout and restart of station.  Customers may also experience the Java Virtual Machine exit with the following exception in the standard output: java.lang.OutOfMemoryError: unable to create new native thread Environment I/A Series G3 versions 3.5.406, 3.6.406, and 3.7.106 Cause It is believed that excessive NiagaraNetwork workers are being spawned due to additional overhead required to encrypt and decrypt passwords from the new password store utilized in 3.5.406, 3.6.406 and 3.7.106. Excessive usage of CPU and creation of worker threads may be seen on both Enterprise Network Server and ENC/JACE platforms. Typically OutOfMemoryError will be seen on ENC/JACE platforms and not on PC based solutions due to the limited resources of the embedded platforms. The issue has only been observed on stations with five or more station devices in the NiagaraNetwork. Resolution Limit the number of NiagaraNetwork/workers that can be created by setting the property "Max Threads" on the NiagaraNetwork/workers property sheet. A good rule of thumb for the number of workers is six times the number of Niagara Network stations monitored by the station.

Issue Equipment lead lag rotation based on runtime Environment I/A Series G3 Cause Rotation of equipment using runtime.  Resolution A LeadLagRuntime object is available in the kitControl palette (HVAC folder). The LeadLagRuntime object can be configured to rotate 2 to 10 loads. An explanation of the usage can be found in the Niagara Ax kitControl Guide or the online help in Workbench. 

Issue I/A Series G3 BACnet Server (Export) Operation Environment I/A Series G3 Cause Integration to I/A Series G3 from a 3rd party BACnet system Resolution If the I/A Series host (ENS or ENC) is licensed as a BACnet server, you can export any number of selected types of objects in the station (regardless of location) to appear as BACnet objects. As such, these objects can service client requests from any networked BACnet devices. Exporting of Niagara schedules and calendars is included. Histories can be exported also, where they appear externally as BACnet Trend Log objects.  The following I/A Series G3 objects can be exported as BACnet objects (extracted from the Niagara Ax BACnet Guide).    You use the Bacnet Export Manager to export Niagara objects for BACnet. To access the Bacnet Export Manager, go to 'BacnetNetwork' > 'Local Device' and double click on the 'Export Table' under the Local Device.  You can find details on using the Bacnet Export Manager on pages 4-57 to 4-71 of the Niagara Ax BACnet Guide. The Niagara Ax BACnet Guide is installed with G3 and can be found in \niagara\niagara-3.x.xx\docs.   can be exported also, where they appear externally as BACnet Trend Log objects. from any networked BACnet devices. Exporting of Niagara schedules and calendars is included. Histories can be exported also, where they appear externally as BACnet Trend Log objects. (regardless of location) to appear as BACnet objects. As such, these objects can service client requests from any networked BACnet devices. Exporting of Niagara schedules and calendars is included. Histories can be exported also, where they appear externally as BACnet Trend Log objects.

Issue I/A Series R2 BACnet IP Device addressing Environment I/A Series R2 BACnet integration Cause When you manually add a BACnet IP shadow device object to a station, you will need to enter the BACnet IP addressing information for communications to work.  Resolution Right click on the BACnet IP device and go to its properties. Go to the 'Config' tab and set the following.  - The objectIdentifier > Instance Number. This is the BACnet instance number of the device (1 - 4194302).  - The address > Network Number. This is the BACnet network number of the device (1 - 65534). - The address > MAC Address. This is the IP address and BACnet UDP port of the BACnet IP device in HEX format.  Example: C0:A8:01:23:BA:C0 corresponds to 192.168.1.35:47808. 

Issue Although the current time is correctly displayed in a UNC, the Enterprise Server, and WorkPlace Pro, it is incorrect in the R2 Schedule Editor. The error in time is a multiple of one hour. Environment I/A Series R2 (Niagara), all versions. Cause The correct Time Zone is not synchronized in the Schedule Editor, which defaults to timezone=America/New_York. Resolution 1. Close WPPro 2. in Windows, go to Niagara / build / nre / lib /time.properties, open with a text editor 3. If it reads timezone=America/New_York, change it to timezone= (timezone corresponding to your location. Copy from Niagara / build / nre / lib /timezones.txt) 4. Save the change 5. Start WPPro, check the time in the Schedule Editor, should be correct.  

Issue Older I/A Series G3 stations will not connect to an Enterprise Server that has been upgraded to a release with the 2013 security updates.  Versions with the 2013 security updates include: 3.7.106 (AX-3.7u1) 3.6.406 (AX-3.6u4) 3.5.406 (AX-3.5u4) 3.8.37 (AX-3.8) Niagara Network Fox Connections State remains "Not Connected" and the Last Failure Cause indicates ...        com.tridium.fox.session.InvalidCommandException: Expecting 'challenge', not 'rejected' Environment I/A Series G3, Enterprise Server, ENC, SoftJace Cause To increase system security, the update releases significantly modified how I/A Series G3 station password storage is maintained.  Any system with an I/A Series G3 Enterprise Server that transitions to an update release for the first time has a few extra steps involving the Enterprise Server station. Schneider Electric strongly recommends reviewing your security situation and upgrading the latest I/A Series G3 software with updated security measures. Resolution The following is an excerpt from the NiagaraAX 2013 Security Update document included in the docs folder for each of the 2013 security update builds.  The steps detail how to modify the Legacy Authentication setting to relax security for stations operating at previous builds. Setting Legacy Authentication within the Fox Service: In Workbench, open the running Supervisor station (Fox connection). In the Supervisor station, open the property sheet of its NiagaraNetwork - Config > Drivers > NiagaraNetwork. Expand the FoxService and look for a new property Legacy Authentication. Change Legacy Authentication from the default “Strict” to “Relaxed Until” (shown below) and then Save.  For further details, see “Fox Service properties” in the NiagaraAX Drivers Guide. This should be a temporary setting only. Reset this to “Strict” in the Enterprise Server’s FoxService after you complete upgrading I/A Series G3 in the subordinate ENC/JACE hosts (represented in the Enterprise Server’s NiagaraNetwork).  Relaxed authentication in the Enterprise Server’s FoxService allows its subordinate ENC/JACEs to continue to communicate with the Enterprise Server until they have been upgraded.  This is necessary to continue operations like remote alarming, archiving histories, and so on. However, you should NOT leave the Enterprise Server in this state, as this negates much security (see Caution). Caution:  Unless set to “Strict”, either “Relaxed” option is effectively the same as setting the FoxService property Authentication Policy to “Basic”, as this is the only “common ground” authentication between a legacy Fox client (Workbench or another station) and this update release station. Thus, passwords for client connections to this station are passed in clear text. Obviously, this is not a desired operating state.  For this reason, you should seldom (if ever) set the Legacy Authentication property to “Always Relaxed”.

Issue Getting javax.baja.xml.XException: Error parsing value error message when attempting to add a new driver network to the I/A Series G3 station's Drivers container. Drag and Drop - drag network container from palette and drop onto the Drivers container Copy and Paste - copy network container from palette and paste into the Drivers container Drivers Manager (New selection) - wizard to add new driver Error details displayed:  com.tridium.fox.session.ServerException: javax.baja.xml.XException: Error parsing value [38:4] Environment Enterprise Network Server, ENS, ENC, JACE Cause The module associated with the driver has not been installed in the local modules folder or remote station. Resolution Enterprise Network Server Stop Workbench Copy the missing module directly into ~\modules directory for the version of I/A Series G3 being used. Restart Workbench ENC or JACE Open the platform for the ENC/JACE Install the module using the Software Manager. A station reboot may be required.

Issue The selection list only shows the IP address of 127.0.0.1 instead of the IP Address(es) assigned in the computer's network configuration, as shown in the following screen capture.  How do I assign / select the proper IP address? Environment WorkPlace Tech Tool software release 5.7.x or later. Cause Invalid computer name. According to the information displayed by running "IPConfig /all", the computer's "Host Name" is "localhost", as show in the following image.  This name is a reserved name that cannot be used as a  computer host name. Resolution Change the computer Host Name from "localhost" to any other valid unique Host Name.

Issue Customer has a Microsoft Office site license for the 2013 version of the Microsoft Office Suite of software.  How can they get and install a copy of Visio 2010 for use with the current version of the WorkPlace Tech Tool software? Environment WorkPlace Tech Tool software version 5.7.x or 5.8.x Visio 2013 installed by customer's IT department Cause Microsoft sells only the current version of their software products but allow some specific classes of users to install and use earlier versions of the software product. Resolution According to the Microsoft document "Microsoft Volume Licensing Product Use Rights (Worldwide English, April 2013)", the following conditions apply:  On page 9, "General License Terms", the following statement is shown:  Page 20 of the same document makes the following statements regarding the "Product-Specific License Terms" noted the "Rights..." paragraph, above:

Issue Wants to hide the Visio 2010 Ribbon bar selections that are not useful for normal WorkPlace Tech use. Environment WorkPlace Tech Tool 5.7 or newer (only versions that support Visio 2010) Visio 2010 Cause Microsoft changed the Visio user interface from a menu bar type interface to a "ribbon bar" type interface.  The ribbon bars not used for operations within the WorkPlace software are confusing to the users that are not trained in the use of Visio 2010 Resolution Visio Ribbon Bar selections not needed can be hidden from view by using the "Customize the Ribbon" Visio options screen.  Select the "File" menu and select "Options". In the left column menu of the Visio Options window, select "Customize Ribbon".  The "Customize the Ribbon" screen is displayed. In the selection box under "Customize the Ribbon:" (right side of window), make sure that "Main Tabs" is selected: Uncheck the Main Tab selections that you do not wish to see.  I suggest leaving the Home and View menu selections in addition to the WorkPlace Tech and Stencil menus.  The View menu should be left enabled because it contains the Zoom and Window selections.  Hiding the Stencil menu will cause the stencil selection window at the left side of the application window to be hidden and would prevent the selection of objects to be added to the application.  This image shows the minimum tabs needed:   Click the [OK] button at the bottom of the window to close the window, saving the selection changes.

Issue Backing up a GCM database in Tree Tech, but the system wasn't originally engineered using Tree Tech. Is there a documented procedure for doing so? Environment Tree Tech 3.1 or 3.2 Tree Tech Engineering Guide, F-26640-4 Network 8000 GCM-84000, GCM-86000, LNC-1000, SIM-x Cause Earlier versions of the Tree Tech Engineering Guide, F-26640, didn't include a step-by-step procedure for backing up a GCM that had not originally been engineered using Tree Tech. Resolution The latest edition, Tree Tech Engineering Guide, F-26640-4,  has been appended to include a step-by-step procedure for creating and configuring all Tree Tech components necessary for ultimately uploading a GCM database. A link to this revised edition is available through the "Help" menu:     See Appendix B, "Creating a GCM Database Backup". Topics include: 1. Creating a New Project Database 2. Adding the Equipment Segment 3. Adding the Network 8000 Object 4. Adding a GCM to the Network 5. Adding the Workstation Segment 6. Adding a Port 7. Configuring the NETWORK 8000 Network 8. Communicating with the GCM 9. Prepare for Backup (Upload) 10. Uploading the GCM Database

Issue How do you convert MicroNet 2000 controller filenames generated by the MicroNet Controller Interface "Get Multiple" function to integrator and controller addresses? Environment MN-2000, MN-CI, MicroNet Controller Interface Cause The "Get Multiple" function is used to upload application programs from multiple MicroNet controllers under one MicroNet Integrator or a series of MicroNet Integrators.  The application programs are stored as files with the integrator and controller addresses appended to the name. Resolution When uploading files from multiple MicroNet VAV Controllers, the CI creates unique filenames for each uploaded application file by appending the integrator number and device number to the prefix entered in the Enter File Prefix window. The integrator number and device number are appended in hex format. The file shown in the illustration above was uploaded from MicroNet controller 11 under MicroNet integrator 6.

Issue Unable to access the "Tools" menu item to configure options in the "standalone" version of I/A Series G3 Alarm Portal Environment I/A Series G3, Alarm Portal, ENS-ALM-CON-G3 Cause The "Tools" menu item was removed in I/A Series G3 versions 3.6 and higher to prevent any user from configuring Alarm Portal options (e.g. appearance and operational behavior). Resolution Configuration of the Alarm Portal options on a "standalone" version requires a set of files to be transferred from a full Workbench version of the Alarm Portal to the standalone version. Start Workbench and select Tools - Options Configure options (e.g. Alarm Console, Alarm Portal) Close Workbench and use Windows Explorer to locate the options subfolder for the user that modified the Alarm Portal options Copy the associated options files (alarm-AlarmConsoleOptions.options and alarm-AlarmPortalOptions.options) to the standalone Alarm Portal. Place the files under the appropriate user using the same path structure in an options subfolder.  The Alarm Portal will now use the options defined.

Issue The MnFlow shadow device, in Niagara R2, comes with six objects.  What do the inputs and outputs cross-reference to down in the Micronet 2000 VAV controller? Environment Niagara R2 (ASD driver) Micronet 2000 Cause Programming Niagara objects to control setpoints in the Micronet VAV Resolution Document F-25720 lists tables illustrating what each input and output is mapped to in the Micronet VAV. MnFloEmsDi object in Niagara R2: MnFloEmsAi object in Niagara R2: MnFloDvOuts & MnFloAvOuts objects in Niagara R2:

Issue OPC points status' shown as 'fault' and not updating after Matrikon OPC Server is restarted Environment I/A Series r2.301.529 Enterprise Server OPC Client integration to Matrikon OPC Server Cause The root cause for this issue has not been determined at this time, the following workaround currently resolve this issue.  Resolution The current workaround is to disable and then enable the OPC Server in WorkPlace Pro.  1. Right click on the OPCServer object and go to its properties. 2. Go to the Config tab. Change the serverEnable property to False and Apply. Change the serverEnable property back to True and Apply.      

Issue Dimensions for the ENCL-DOOR-PLA.  Environment DMS Cause They are not provided on the datasheet available via iPortal. Resolution Dimensions are illustrated below:

Issue How to extract the status of DI 01 from a Viconics thermostat for plotting on a web graphic in Niagara. Environment Niagara R2 Cause Integration requirement Resolution In the Se76PIR shadow object, use nvoSccStatus, bit 18 (see illustration below).   Link to a DynamicDemux object (located in the lonworks jar file, conversion folder) to gain access to bit 18.  Now it can be used in the Niagara station for graphics or logic programming.