Building Automation Knowledge Base

Issue Where can I find an End User Guide for G3 that’s not written for developers? Environment G3, WorkBench (all versions) Cause N/A Resolution Each G3 release zip file includes a document folder.  The PDF file titled docNaxBag.pdf (Niagara AX-3.x Browser Access Guide) is an end users guide and can be found in this folder.

Issue Can a Niagara R2 Enterprise Server and Niagara G3 Enterprise Network Server be installed on the same computer? Environment Niagara R2 all versions Niagara G3 all versions Cause None Resolution The Niagara R2 ES software and Niagara G3 software can be installed on the same computer provided the following: The Windows operating system is supported by both platforms (e.g.  Windows XP) Only one Niagara service can run at anytime (so both platforms cannot run simultaneously)

Issue The error messages "Cannot open admin session.java.lang.NullPointerException" is displayed when attempting to open the WorkPlace Pro Admin Tool Environment R2, WorkPlace Pro (all versions) Cause Both R2 and G3 are on the same PC.  Niagara G3 was last run on the PC.  Error is caused by the failure to run R2 "Install Niagarad" after running G3.  The G3 service stays active even after G3 is closed and will continue to be active until R2 "Install Niagarad" is run. Resolution "Install Niagarad" must be run when switching from the G3, WorkBench to R2, WorkPlace Pro. Close all versions of Workplace Pro Click the Start button then click All Programs Select the Niagara R2 release to start then click "Install Niagarad" The Admin Tool can now be opened.

Issue I need to know hardware specifications for the BACnet controllers and cannot find it in any documents.  Environment The specifications given below are accurate as of 6/30/2011 but are subject to change without notice. Cause Not applicable Resolution The memory specifications below are also available in the MicroNet BACnet Wiring, Networking, and Best Practices Guide.  If a formal document for the CPU and I/O specifications is required contact your Regional Salesman or Product Marketing. MNB-V1 and MNB-V2 Processor: Atmel ATMEGA256-16AJ (8-bit) operating at 16 MHZ Memory: Flash 256KB, SRAM 8KB, EEPROM 4KB A/D and D/A resolution: UI inputs have a 12 bit resolution and UO outputs have an 8 bit resolution  MNB-70 Processor: Atmel ATMEGA256-16AJ (8-bit) operating at 16 MHZ Memory: Flash 256KB, SRAM 8KB, EEPROM 4KB A/D and D/A resolution: UI inputs have a 12 bit resolution and UO outputs have an 8 bit resolution MNB-300 Processor: Atmel ATMEGA256-16AJ (8-bit) operating at 16 MHZ Memory: Flash 256KB, SRAM 8KB, EEPROM 4KB, FRAM 8KB A/D and D/A resolution: UI inputs have a 12 bit resolution and UO outputs have an 8 bit resolution  MNB-1000 Main Control Processor: Freescale Coldfire MCF5485 (32-bit) operating at 200 MHZ Memory: Flash 16MB, SDRAM 64MB, EEPROM 1KB, Boot Flash 2MB Motherboard (Local I/O Processor) Processor: Atmel ATMEGA128 series 8-bit microcontroller running at 16 MHZ Memory: Processor Flash 128KB, SRAM 4KB, EEPROM 4KB.  Motherboard SRAM 256KB, EEPROM 128KB A/D and D/A resolution: UI inputs have a 12 bit resolution and UO outputs have an 8 bit resolution

Issue The .class files are related to a Cloudscape / Microsoft JVM memory leak eventually causing the hard drive to fill and become unusable.  The station will fail or exhibit slow response (e.g. station operation, opening remote or local library, etc.).  Versions prior to 514 require the use of a garbage collection feature to correct the issue. Environment I/A Series R2 UNC-600, UNC-610, and Enterprise Server Cause Cloudscape / Microsoft JVM memory leak Resolution Builds 330 or earlier - Enable the garbage collection by adding the garbage collection servlet to the root of the station database.  The GarbageCollectionServlet can be found in the tridiumx library (lib jar file - servlets). Copy and paste the servlet into the root of the station. Garbage collection for build 428 and 431 is enabled by modifying a parameter within the system.properties file. Stop the station database. Use the WorkPlace Pro admin tool to open the system.properties file and locate the following line: #gc.daemon=600000 Uncomment (remove leading #) to enable the feature. Save and close the system.properties file. Restart the station database. Builds 514 and higher will not exhibit the memory leak due to the change of the JVM from Microsoft to Sun Hotspot.

Issue Station sending SMTP server its LAN IP address instead of WAN IP address causing the SMTP server to block the connection. Environment I/A Series G3 (Niagara) Cause SMTP server is blocking the connection due to the LAN IP address being used. Resolution A new system property is available that can be used to define how the station identifies itself to remote SMTP servers. This can be done by setting the mail.smtp.localhost property in the system.properties to the station's external facing IP address or FQDN. Example: mail.smtp.localhost=12.34.56.78 Download the listed (or newer) email module from Exchange Extranet website.   email-3.3.34.1.zip email-3.4.65.zip email-3.5.34.2.zip email-3.6.33.zip email-3.6.48.zip

Issue When attempting to Discover devices on the Niagara Network getting the following message: java.net.socketException can't assign requested address. Environment G3 (Niagara) ENC Cause The address in the default gateway of the ENC is invalid. Resolution Under the station Platform open TCP/IP Configuration and enter the proper gateway address in the "IPv4 Gateway" field.

Issue Are the Universal Inputs (UI) common isolated from the Analog Outputs (AO) common on the MNL-800? Environment MNL-800 Cause N/A Resolution No, the commons for the MNL-800 Universal Inputs and Analog Outputs are not isolated from each other. 

Issue How can the information displayed in an alarm generated email message be controlled in R2? Environment Niagara R2 (all Version) Cause N/A Resolution What gets displayed in the body of an alarm generated email message is controlled by the AlarmFields property located in the MailRecipient Properties. 1. In WorkPlace Pro, right-click on the MailRecipient object and select Properties. 2. Select the Config tab.  3. Select the text fields to be displayed in the body of the email alarm to be sent to the MailRecipient. 4 Click Apply to save  The alarm generated email will contain only the selected text fields.

Issue Error starting the serial port on the I/A Series G3 Enterprise Network Server when the station is configured for SMS (Simple Message Service). The following error is seen in the station output. ERROR [11:26:17 19-Jul-11 SGT][sms] Error starting the serial port javax.baja.license.FeatureNotLicensedException: tridium:serial Environment I/A Series G3 Enterprise Network Server I/A Series G3 SMS driver [The SMS (Simple Message Service) driver is used for sending text messages to other cellular phones. The SMS driver allows transmitting alarm information and sending general text messages.] Cause The Enterprise Network Server license file was generated without the serial feature. The feature is required for the SMS module to work.  Resolution The serial feature needs to be linked to the part number. Schneider Electric is working to correct this so future licenses that has the SMS feature will also include the serial feature. Email the license file and error message(s) to Product Support to get the license corrected.

Issue Getting the error “relay access denied” when trying to send an email from an UNC with MailService installed. Environment R2 (all version), UNC, Enterprise Server Cause SMTP Server requires Authentication Resolution If the SMTP mail server requires authentication, the Niagara host's (UNC or Enterprise Server) must have the following line present in its system.properties file: mail.smtp.auth=true Add the above line if it’s missing from the host’s system.properties file.  If the line is present but commented out, remove the “#” from the front of the line for the line to apply.  The host must be rebooted for the change to its systems.properties file to apply.

Issue The hard drive was replaced and reloaded with OS/2.  UltiVist was re-installed on 😧 partition.  The UltiVist shortcut appears on the OS/2 desktop.  When it is executed, the background programs initiate as they should with no errors reported.  The primary UltiVist executable also starts but no operator views appear and the familiar "low beep-high beep" audio signal of a successful start to the program does not occur.  Again, no errors are reported. The UltiVist was re-installed over-top the existing installation with no change or improvement. Environment UltiVist version 1.22 and newer OS/2 all versions Cause The original hard drive failed and was replaced with a new one. Resolution At an OS/2 command prompt, type 'd:' then enter.  Type 'cd fi' then enter. In the d:\fi directory, find the ultivist.cmd file and look at its contents by typing "view ultivist.cmd".  The last two lines should read: STARTER.EXE FI.CFG START /PM UVUI.EXE %1 %2 Try typing each line at the command prompt a few seconds apart.  The first line starts all the background/support programs.  The second starts the actual interface program. If either line fails to properly execute, cut or rename the entire fi folder and re-install UltiVist from floppy disk (or CD). Do not install over-top the existing installation.

Issue The status of a Lon binding states locked.  How can it be changed to bound?    Environment R2, WorkPlace Pro Cause Binding is locked. This can be done at the time the node is learned or a network variable can be locked on the property sheet of the node. Resolution The Network Variable bound to the link will have to be unlocked to change the link to bound. Open the device property sheet that’s associated to the locked link Select the device tab and LonProps tab. Select and expanded the Snvt that’s associated with the locked link Unselect “Locked” and click Apply. Open LonDeviceManager under LonWorkService Highlight the device and select UpLoad Check boxes: “Upload binding info”, “Add links” and “Upload config data” and click Apply - DO NOT check “Lock existing bindings”   The link status now read bound.

Issue Enterprise Server not archiving to SQL Server database.  Getting the following Error in ErrorLogService:  “Failed to archive (1): tridium.datax.net.DxRemoteException: java.sql.SQLException: The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Parameter 2 (""): The supplied value is not a valid instance of data type real. Check the source data for invalid values. An example of an invalid value is data of numeric type with scale greater: than precision.  The SOW displays: at tridium.datax.net.DxExchange.doResponse (bytecode 107) at tridium.datax.net.DxExchange.run (bytecode 118) at java.lang.Thread.run (line 5) Environment R2, WorkPlace Pro 2.301.529, Enterprise Server Cause NA Resolution The coreRuntime-2.301.529a.v1 jar file corrects possible issues related to the archiving of data to a Microsoft SQL 2005 database.  This jar is only required by Enterprise Servers with the IA-SQL-DBS driver feature. Installation: Stop the running station and Niagara service Locate the existing coreRuntime-2.301.529.v1.jar file (e.g. ...\nre\modules) directory.  Rename the existing file to coreRuntime-2.301.529.v1.jar.old Copy in the coreRuntime-2.301.529a.v1.jar file. Restart the Niagara service and Enterprise Server station.

Issue Integrating a Proview display for the first time.  Which jar files are required in the UNC? Product Line TAC IA Series Environment Niagara R2 version 529 Cause Integrating a Proview display for the first time. Resolution Ensure the following jar files are installed in the UNC: lonDistech-2.307.529.v1.jar lonDistechWizards-2.306.515.v111.jar wizard-2.301.529.v1.jar lonworks-2.301.529.v1.jar

Issue The installation comprises of an UltiVist server and several DMS panels networked via ethernet.  When connected serially to one of the DMS panels, with Operator Interface software, symbolic points will not add to the DMS and Microsmart points will not link up to the DMS. Environment Ultivist all versions DMS350A, DMS3500 all firmware Operator Interface (OPRIF) all versions Cause Database changes required to HVAC I/O modifications. Resolution The PSWRD element must be modified so as to allow point additions and linking via a local (serial) connection.  When an UltiVist server is networked with a DMS panel, the PSWRD element will contain a "N" flag. For example,  PSWRD = 159 03 2 N means that the DMS panel is on a Network with UltiVist.  Commands for creating, linking, and deleting points as well as deleting the entire database are not permitted via OPRIF on a serial connection. PSWRD = 159 03 2     means that the DMS panel database can be thoroughly manipulated including  point additions, deletions, and linking. Review the PSWRD element in the Commands and Elements Reference (F-25469) available in the Publication Zone of the iPortal website.

Issue The setpoint values are displayed briefly and then change to 621.X on the Proview display? Environment All LON proview installations. Cause This occurs when the setpoints are being written into network variable inputs (nvi).  The nvi's default to using the receive heartbeat and will fallback to default after the timeout occurs.  Proview does not perform a send heartbeat function as the connection is an nv update and not an actual binding. The receive heartbeat mechanism in the MNL controllers cause the nvi values to fallback to NA upon heartbeat timeout. Resolution The heartbeat can be disabled for the setpoint nvi, however nvi values are stored in RAM (not EEPROM) and will return to default upon a controller power cycle.  The best solution is to use network configuration inputs (nci) for setpoint displays on the Proview.  These do not have the heartbeat issue and the values are maintained in EEPROM so they are not lost following a controller power cycle.

Issue The MNL-800 controller will not communicate with the WorkPlace Tech tool nor will it communicate with LON network management software tools such as LonMaker or the I/A Series (Niagara) R2/G3 LON Device Manager software. Symptom - Controller LEDs (top to bottom) Green Power and Transmit Data (Green) – on solid (normal power condition) Receive Data (Yellow) – may be flashing if data present on the bus Service (Red) – flashing a repeated abnormal pattern (long flash / short flash) Heartbeat (Green) – alternates on and off at a half second rate (normal) Environment MNL-800 on existing or new LON network WorkPlace Tech Tool software or LON Network Management software Cause An analysis of field returns has identified a condition where the MNL-800 fails to communicate and appears to be resetting continuously. The controller has entered a condition where the Neuron’s image has been deemed corrupted due to an application checksum error or signature inconsistency. When this occurs, the Neuron is unable to complete the startup sequence resulting in the MNL-800 continuously resetting. Resolution Follow the procedure documented in TPA-RKFD-09-0005.00 to reconfigure the communications processor in the MNL-800 controller. In the unlikely event that this procedure does not correct the communications issue, please contact Product Support Services for additional assistance.

Issue What resources are available to get more information on the M-Bus protocol? Product Line Andover Continuum, Field Devices, Other, Satchwell MicroNet, Satchwell Sigma, TAC IA Series, TAC INET, TAC Vista Environment M-Bus Cause The M-Bus protocol information is available on www.m-bus.com. Select The M-Bus: A Documentation Rev 4.8 Resolution The M-Bus protocol specifications is broken down in multiple chapters. Basics of Serial Bus System Overview of the M-Bus Physical Layer Data Link Layer Telegram Format, Meaning of Fields, Communication Process Application Layer Structure of fixed and variable data blocks. Network Layer Appendix Table of units, medium, data field codes, VIF extensions.

Issue Is there a way to keep resending alarm notifications until they get acknowledged in R2? Environment R2, WorkPlace Pro (all versions) Cause N/A Resolution R2 does not provide a way to resend an alarm, already in an alarm state, until it gets acknowledged.  Resending alarms is possible in G3