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 Can't see the Xenta Server Menta  program online in the browser Menta program is working but it is not possible to view it online All other viewers work correctly Product Line TAC Vista Environment Xenta 731 Xenta 711 Xenta 721 Xenta 701 Xbuilder Menta Cause One reason could be that there are texts (comments) in the Menta application that does not have any font specified. Resolution Edit the Menta file form Xbuilder Find any comment/texts Double click to edit Click on font Select a font and save Download the Xbuilder project again

Issue  Setting the values of the X Driver points that is set up for Function code 15 (Force Multiple Coils) does not send out data. Environment bCX1 4040, 9640 Netcontroller II with X Driver, XDriver, X-Driver. Cause As an array of bits has to be transmitted to the 3rd party system it has to come from the Annex point not the X Driver point itself. Resolution The data to be sent to the 3rd party Modbus device is held in a manual array in the AnnexPoint not the X Driver point itself. Create an X Driver point on the required Comm port and define: The correct slave number Function code 15. Define the Start channel address Enter the number of Bits to be written in the "Number Of Channels" In the AnnexPointName enter the name of the separate Numeric point that will hold the data to be written. Ensure that the Annex point has a manual array of at least the size of the number of channels (bits) to be written. Fill each of the array entries with 0 or 1 as required to be sent. This can be done through Command line or Plain English: For example if the system is writing to 4 relay outputs, through command line you would enter the data as: Annexpt = 1      'Relay 1 = On Annexpt[1] = 1 'Relay 2 = On Annexpt[2] = 1 'Relay 3 = On Annexpt[3] = 0 'Relay 4 = Off   Then change the value of the X Driver point to force the data to be sent.

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 Using a repeater to extend ACC LON bus. Environment CX9900 CX9940 CX9680 IOU Modules Cause Infilink repeater is designed for the Infinet field bus. Resolution The Infilink repeaters CAN NOT be used to extend ACC LON.

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 IC3-MODBUS, how is the TCP version connected. Environment Sigma, IC3-MODBUS Cause The modbus device has a TCP interface instead of a RS-232 or a RS-485 interface. Resolution The IC3-Modbus needs only 1 IP connection, this connection serves both the Sigma interface and Modbus interface. The Modbus TCP device will also need an IP connection and is also connected to the same network. The Modbus controllers and the Modbus TCP device IP address are mapped at the end of the gateway.txt file. Download Sigma Release 4.06 - Firmware IC3-Modbus Release Note for details on IC3-Modbus

Issue Create a schedule and attach a numeric to the occupancy point. Receiving error: "Cannot resolve object: in Object Property List. Please save BACnet device to database or make sure the object still exists." Click OK. Schedule opens up, but the occupancy point is empty under the configuration. However, the occupancy point that was attached is being controlled by the schedule. Environment CyberStation v1.74 SP2, 1.74SP2, 1.74 Cause Received error when editing schedule. Resolution For CyberStation v1.74 SP2, 1.74SP2, 1.74 Download Hotfix: CyberStation v1.74 TPA-BOST-08-0005.00 Hotfix For Cyberstation Above 1.74 Make sure there is no object created in the controller using a name that is the same as the name of the Network under which the controller reside. For example: If you have a controller - Root\BOC\MainCX which contains a controller user object named BOC you will see the schedule issue.

Issue Modifying alarm tripped text and reset alarm text on a Xenta programmable controller under a Xenta Server is not reflecting these changes. Environment Vista 5.x.x/4.5.0 Xbuilder 5.x.x/4.5.0 Cause When the Xenta programmable controller is added to the LonWorks network under a Xenta Server an alarm object is created in Xbuilder with the Tripped Alarm Text and Reset Alarm Text from the MTA file. Updates to the MTA file or alarm object in Vista server does not update the Xbuilder project. Resolution Edit the Xenta Server object and modify the Tripped Alarm Text and Reset Alarm Text for the in the Alarms folder under the programmable controller in the Network pane of Xbuilder.

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 Installing VisiView on Windows 7 Environment Windows 7 VisiView   Cause Supported operating systems Resolution VisiView will not work on Windows 7. Windows XP Pro is required. The upgrade path would be to use a Xenta 555 or Xenta 731.

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 Continuum analyzer reports errors in the IE Table Check. Environment Cyberstation Cause Errors need to be cleaned up using the Continuum analyzer. Resolution Clean up the errors using the Continuum analyzer then run the tests again to verify errors where corrected. If everything appears to work correctly then there is no need to reload the IE table to the controllers, otherwise: Send the IE table to CX level controllers. To send only the IE table select the 'Do not reload attached objects' in the 'Send To Controller Options' dialog window.

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 The Xbuilder device editor by default only allows 200 lines, and some integration efforts require more than 200 points to be programmed. Environment Xbuilder Device Editor Cause The device editor only has 200 rows by default. Resolution The device editor is designed with excel functionality meaning, new rows can be added to allow for more points to be programmed. To add rows to the device editor follow these steps: Open the device editor. Right click on the row number. Choose insert row. Type in the desired number of rows (up to 100) If more than 100 are needed repeat steps 2-4.