Building Automation Knowledge Base

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

Issue An end-customer purchased WorkPlace Tech 4.x several years ago and is retiring the computer.  The new computer will have the latest version of WorkPlace Tech.  Which part number applies to this upgrade from 4.x to 5.x? Environment WorkPlace Tech 5.x Cause Host computer is being replaced. Resolution In the "Purchase WorkPlace Tech software" program, choose the part number:  WP-TECH-50U. When submitting the unlock code request, ensure that the original order number and/or PO number is included so that Customer Service can confirm that it is an upgrade, and invoice using the lower cost upgrade cost.

Issue A Cisco Mediator controller is connected via BACnet/IP to a Niagara R2 UNC.  The UNC station provides data to and receives commands from the controller.  The Cisco Mediator controller can read BACnet values but when it attempts to overwrite setpoints and issue commands, they do not work. Environment Niagara R2 all versions Cause The installation contains 3rd party BACnet controllers that must share data and commands. Resolution To allow other BACnet controllers to write values or issue commands to exposed Niagara objects, a special "BACnet" user is required for the station. To create this special user, follow the steps listed on pages 4-6 & 4-7 of Tridium's BACnet Integration Guide.

Issue Procedure for obtaining a Return Authorization (RA) for a defective I/A Series (Niagara) G3 ENC Environment ENC-410, ENC-520 Cause Unknown - ENC is not functioning and needs to be repaired or replaced Resolution To request a Return Authorization for a defective ENC controller, the factory will need to know the following information: The product part number (ENC-???-?-?) Is the unit still under warranty? Warranty note: Warranty on a new UNC is 2 years from date of manufacture. The date code format is yyww. Example:  0815 is  2008 week 15 Serial number Job name (site name for unit) Factory order number Project ID Host ID (in the license file) The reason for return Network settings (IP, Subnet, name) Username and Password Station DB Username and Password Any special shipping instructions Have a purchase order number ready when you call. Note: Customer Support Services sends/bills for advance warranty replacement units. When the customer returns the correct unit within 30 days, a credit is then issued., Call Schneider-Electric at 888-444-1311 and select option 2 (Product Support). Product Support will enter a support case identifying the unit and that an attempt to troubleshoot was done prior to issuing the RA number. The caller should request the Product Support Case number and RA number for future reference. An RA will be issued based on the following criteria: Credit AWR (Advance Warranty Replacement). Customer is sending back an inoperable unit to the factory for credit and needs a replacement unit right away. OOWR&R (Out of Warranty Repair and Return). Customer sends back an inoperable unit to the factory for repair and return. IWR&R (In Warranty Repair and Return). Customer sends back an inoperable unit to the factory for repair and return. NOTE: When issuing an AWR, hold the defective unit and use the packaging from the replacement to return the UNC board. This will help guarantee that the units are not damaged during shipment. When the units are received damaged and improperly packed, they are returned as received and no credit issued.

Issue How to configure a Niagara G3 ENC serial port for dialup modem. Product Line TAC IA Series Environment ENC-520-2 ENC-410-1 Cause Dialup modem setup. Resolution In the Station, under Platform Services, go to the SerialPortService In the Port Config field, change the setting to Com1_232_com2_modem. Save this setting. Now, go to the Platform of the ENC, and go to Dialup Configuration The Init String should look something like this: ATE0S0=0Q0V1X4&D2&K3\N3%C2&C1&Q5W2 Change the 0 just after the "=" sign to a 2.  This will tell the modem to answer on the second ring. Make sure that the Port field says COM2 Check the Enabled box next to Listen for Calls In the Local IP Address field, type in the IP address of the ENC In the Remote IP Address field, type in an unused IP address on the same subnet as the ENC. Type in a User Name (eg. invensys) Type in a password (eg. niagara) Save your changes, then click the Start button at the bottom of the page.  This will start up the dialup daemon. Re-boot the station in Station Director.

Issue Unable to backup an R2 UNC-520 database, receive 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 I/A Series R2 UNC-520 I/A Series R2 WorkPlace Pro,  error reported in build r2.301.529 Cause The WorkPlace Pro cannot connect to the UNC-520 at the given IP address.  The error message stems from a bug in the Sun java, "The Socket constructor does not give an Exception on an unknown IP address. It just hangs."  http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=4232651 Resolution Verify that the UNC is capable of communicating at the IP address specified. For example, if the UNC is rebooting constantly, it will not be able to communicate.

Issue In a Niagara G3 station, the BACnet Service indicates "routing enabled = false", even though it had been set = true. What caused the change? Environment Niagara G3 station in an ENC with BACnet / IP enabled Cause The ENC has detected a routing loop and automatically stops routing BACnet / IP messages, and sets the "Routing Enabled" flag = false. Resolution This can be caused by having two or more devices routing to the same network number.  Network numbers must be unique throughout the entire BACnet network.    Locate and remove the cause of the routing loop, which is more than one path to a BACnet device.   Procedure Details: Open platform director Watch output for network number error.   (e.g. Bacnet Network Misconfiguration detected(3): Network number update frequency indicates possible router loop on network 20!!!)  Check BACnet devices with Routing enable and make sure all networks have a unique network ID. 

Issue Is there a way to display only points currently in alarm in the Alarm Console? Environment G3, Workbench (all versions) Cause Only want to display points currently in alarm in the Alarm Console? Resolution Yes, the Alarm Console’s filter is used to control what alarms are displayed in the Alarm Console window.      Double-click on the ConsoleRecipient object Click on Filter at bottom of window Check the Source State box. Click on the Source State chevron to show filter options Select the alarms states, Offnormal and Fault. Only alarms currently in the Offnormal and Fault states will be displayed in the alarm console window.  (Items not checked will not be displayed.)  Click OK and OK to save.  Click File from the menu and Refresh to update change. Only alarms that are currently in a Fault or a Offnormal state will be displayed in the Alarm Console window.

Issue Is part number 40-1758, end of line resistor, still available for purchase through Schneider Electric?   Environment Network 8000, IA Series BACnet Controller Cause Part is no longer available for purchase through Schneider Electric Resolution Part number (40-1758) specified for the 120 ohm EOL (end-of-line) termination resistor is no longer available for purchase through Schneider Electric.  The resistor is utilized for RS-485 communications trunks (e.g. Network 8000, BACnet, etc.).  This resistor is a common part and is readily available for purchase through electronic stores or catalogs.    The specification for the resistor is as follows: Nominal value: 120 ohm Tolerance: +/- 5% or better Power rating: 1/4watt metal film Temperature coefficient: +/- 200 PPM or better Maximum voltage: 250 volts